Start free. Upgrade when governance gets serious.
The core is source-available and self-hosted. Paid tiers add the support, assurances, and key custody that regulated teams need in production.
Community
Engineers and teams proving the fit.
- Embedded library (Python) + MCP server
- Provenance, typed memory, policy-gated recall
- Crypto-shred deletion + tamper-evident audit
- Run the full trust suite yourself
- Community support
Team
Teams taking the trust suite from a laptop to production.
- Everything in Community
- Production recall gateway — serve recall to your app, authenticated & remote (in development)
- Signed release distribution — signed wheels + manifest (in development)
- Supported production deployment config + migration tooling (incl. Postgres)
- Commercial-use license for production
- Email support (no SLA)
Professional
Teams with compliance pressure governing memory at scale.
- Everything in Team
- Multi-tenant at scale — per-tenant isolation & authz (in development)
- Managed KMS/HSM key custody — AWS, GCP, Azure, Vault (in development)
- Signed audit export — auditor-verifiable trail (in development)
- SSO — SAML / OIDC for the control plane (in development)
- Full governed TypeScript SDK — recall parity with Python (in development)
- Priority support, security advisories & SLA
Enterprise
Regulated organizations with auditors in the room.
- Everything in Professional
- On-prem / air-gapped deployment
- Bring-your-own-HSM / customer-managed keys
- WORM audit retention + SIEM streaming
- Custom framework adapters + audit consulting
Team and Professional are in early access — features marked “in development” are on the roadmap, not shipped today, and CTAs route to the design-partner program rather than a live checkout. Enterprise is scoped by conversation and billed by custom quote.
Questions
Is the core open source?
The core is source-available, not OSI "open source." From version 0.2.0 it is licensed under the Business Source License 1.1: you can read the source, run it locally, develop against it, and evaluate and self-host it for non-production use at no charge — and small organizations can run it in production at no charge too. Larger organizations need a commercial license for production use. Each release becomes Apache-2.0 licensed four years after it ships. (Versions 0.1.0–0.1.2 remain MIT-licensed and always will.)
Where does my data live?
In your environment. Heartwood is embedded and runs beside your systems of record. Self-hosted by default; nothing is shipped to us.
How is this billed?
Team and Professional are in early access right now, so there’s no live checkout yet — joining routes you to our design-partner program. Team will be self-serve monthly and Professional annual-prepaid (through Edukas Solutions’ existing Stripe infrastructure) once billing opens. Enterprise is sales-led and billed by custom quote.
What do paid tiers actually add?
Team adds the production recall gateway, signed releases, supported deployment config, and a commercial-use license. Professional adds multi-tenant-at-scale, managed KMS/HSM key custody, signed audit export, SSO, the full governed TypeScript SDK, and an SLA. Enterprise adds on-prem deployment, customer-managed keys, WORM/SIEM audit, and consulting. Features marked “in development” are on the roadmap during early access — not shipped today.