Community Edition
$0self-hosted
For individuals, researchers, and community operators who want sovereign local memory.
- Local substrate and filesystem surfaces
- Open reference cartridges
- Content and basic graph export
- Community support
Pricing anchors
Pay for operation and assurance, not token drama
The substrate is inexpensive to run; reliability, isolation, transduction, upgrades, and support are what cost attention. These anchors open pilot conversations and are finalized against your real workload.
Engagement paths
Start local, move to managed, scale to enterprise
The same substrate and evidence model run across every tier. No tier makes your knowledge captive.
Founding pilot
$250per workspace / month
For the first cohort of 3–5 design partners. A learning engagement, not an unlimited production SLA.
- Isolated managed workspace
- Deployment, upgrades, and health monitoring
- Baseline transduction allowance
- Field-report partnership for 90 days
- Best-effort support during the founding window
Managed workspace
$500per workspace / month
For teams making the substrate part of daily operations.
- Isolated multi-user workspace
- Backups and restore drills
- Upgrade and drift management
- Support response during business hours
- Transduction allowance sized by workload
Enterprise instance
$1–2Kstarting range / month
For organizations that need governance, support boundaries, and a defined control plane.
- Dedicated instance or customer-controlled deployment
- Governance and retention controls
- Support SLA and named escalation
- Audit and export packaging
- Custom cartridge and experience-pack engagement
What the price buys
Operation, not inference markup
We do not build margin by reselling model tokens. Bring your own inference where practical; pass-through costs stay transparent.
Isolation
Each managed workspace runs as a separate substrate deployment with its own data boundary.
Durability
Backups, restore drills, and workspace export are part of the operating service.
Transduction
Managed document and audio conversion with an allowance sized to the workload. Measured quotas and service limits are stated before engagement.
Operations
Deployment, monitoring, upgrades, drift detection, incident response, and support.
Sovereignty
Your content and marker-authored graph organization remain exportable; leaving is technically possible by design.
Assurance
Scope, controls, backup evidence, and security-program status are documented as they are completed—never inferred from a badge.
Sizing
Workload questions we ask before quoting
| Dimension | Why it matters | Pilot output |
|---|---|---|
| Corpus size and types | Determines storage, indexing, and transduction work. | Measured footprint and ingestion profile |
| Domains and cartridges | Determines ontology configuration and cross-domain edges. | Proposed scope map |
| Agent and user count | Determines concurrency, isolation, and support load. | Workspace and access design |
| Evidence workflow | Determines review, approval, and audit requirements. | Acceptance-evidence template |
| Deployment boundary | Determines whether managed, customer-cloud, or local operation fits. | Deployment plan and price |
Next step
Request your workload estimate
Send the basics. We will propose a bounded pilot, measured acceptance evidence, and a written estimate.