Governed memory for AI agents

Agents need memory they can trust.

Heartwood Memory gives AI agents provenance-first recall, policy-enforced retrieval, and deletion that leaves a key-destruction receipt — embedded beside your existing systems of record. Not a new database. Not “unlimited memory.” The control plane in between.

python -m pip install "heartwood-memory[recall,mcp]" · source-available core · your data stays put

python
from heartwood import Heartwood

hw = Heartwood(path="./heartwood.db", tenant="tenant:acme")

hw.remember(
    "Refunds over $500 require finance approval.",
    subject="policy:refunds",
    created_by="agent:support",
)

# recall under policy — signed, provenance-carrying, tenant-scoped
hits = hw.recall("what's our refund policy?",
                 principal_id="agent:support")
Evidence, not adjectives

Proven by gates you can re-run.

0.812
Benchmark — 56 queries, held-out
Typed-router MRR@10

Product-path enterprise retrieval over 56 queries (nDCG@10 0.818).

100%
Trust-suite gate
Provenance coverage

Every recalled memory carries its source chain, model version, and signature.

0
Trust-suite gate — adversarial probes
Policy leaks

Zero cross-tenant policy leakage under adversarial probes in the single-trust-domain trust suite.

30/30
Trust-suite gate
Trust gates passing

Retrieval, policy, faithfulness, deletion, egress, and resilience gates.

<500ms
Controlled benchmark — not a production SLO
Warm recall p95

The pre-registered Phase 1 gate, measured warm with the store, index, embedder, and reranker hot in one process. On our hosted gateway, real production p95 measured 795ms across 873 recalls over a 7-day window in July 2026. We publish the benchmark because it is the budget we design hook- and agent-loop integrations against — not a service level we commit to.

0.972
Benchmark — filtered-search evaluation
Filter-first MRR@10

Policy-before-ranking vs. 0.000 leakage when filtering after the vector search.

Every figure above states how it was measured. Gate results come from executable gates in the Heartwood core with pre-registered thresholds and paired-bootstrap confidence intervals; figures marked as benchmarks are controlled measurements and are not production service levels.

What makes it governed

Five guarantees other memory layers leave to the prompt.

Memory is typed

Source, episodic, semantic, procedural, profile, and generated memory are distinct kinds — so agents retrieve the right context on purpose instead of treating every chunk the same.

Policy comes before ranking

Tenant, classification, scope, denied subjects, and effective time filter the candidate set before results are ranked. The agent never sees a record it is not cleared for, then relies on a prompt to behave.

Provenance by construction

Every memory is signed at write and re-verified at read. Each recall result carries its source chain, the model version that produced it, and a valid signature.

Generated memory is not canonical

LLM-written summaries stay derived artifacts. They must carry source support and pass faithfulness checks before they become useful, trusted memory.

Deletion that leaves a proof

Crypto-shred erasure follows source-to-memory lineage into projections, indexes, caches, and exports — and leaves a tamper-evident audit record behind.

Who it’s for

For agents where being wrong is expensive.

Built for teams running high-stakes agents over support tickets, customer records, operational Postgres, internal policy and knowledge bases, and compliance-sensitive workflows — teams that already have agents but need stronger answers for provenance, policy, deletion, and auditability.

Regulated support agents

Answer from policy and customer evidence, cite where every claim came from, and get a key-destruction receipt — key destroyed, derived artifacts purged — when a customer is deleted.

Operations & workflow assistants

Carry workflow memory and audit trails across long-running tasks without leaking one tenant’s state into another.

Research & synthesis agents

Produce source-grounded summaries that are gated on faithfulness before they are trusted as memory.

Compliance-sensitive copilots

Keep restricted material behind classification clearance; on governed generation paths, egress is evaluated before the external-model call — by policy, not by prompt.

The control plane between your agents and your systems of record — not a replacement for your database, and not “unlimited memory.”

The path in

Review, provision, build.

1

Review

Read the docs and the executable proof. Run the trust suite yourself — every governance claim is a gate you can re-run.

2

Provision

Pick a tier and provision a license, or start free and self-host. Keys are issued to your email; your data never leaves your environment.

3

Build

Install the library, point it at your data, and ship agents that retrieve under policy, cite their sources, and emit a key-destruction receipt on deletion.

Pricing

Source-available core. Pay when you need governance backed by a team.

Community

Free
Source-available core, self-hosted

Engineering teams proving the fit.

Free to read, run, and self-host for non-production use at any size. Organizations that qualify as a Small Organization under the licence — fewer than 100 employees and contractors, and under $1,000,000 in total revenue in the prior tax year — may also run it in production at no charge. See the LICENSE for the controlling definition.

  • Embedded library (Python) + MCP server
  • Provenance, typed memory, policy-gated recall
  • Crypto-shred deletion + tamper-evident audit
  • Run the governance test suite yourself
  • Community support
Start free

Team

$349/mo
Per organization, billed monthly

Organizations taking governed memory from a laptop into production.

Team is sold through a short conversation — we scope the deployment before it starts.

  • Everything in Community
  • Production recall gateway, hosted by us — serve recall to your app, authenticated and remote (or self-host it from the source-available core)
  • Supported production deployment configuration
  • Commercial-use license for production
  • Email support (no SLA)

On the roadmap

Not shipped — not part of this subscription.

  • Signed release distribution — signed wheels and manifest
Talk to us
Most popular

Professional

$6,000/year
Per organization, billed annually

Organizations governing agent memory under compliance pressure.

Professional is available now. Annual subscription, billed once per year, renews automatically until cancelled.

  • Everything in Team
  • Dedicated isolated tenant — your own instance, volume, and hostname; per-credential principal binding enforced server-side
  • Per-answer evidence — every recall returns a hash-chained audit row and an explain_recall rationale you can re-run
  • Priority support with a one-business-day response target (defined in Terms of Service §15.E.4) and security advisories

On the roadmap

Not shipped — not part of this subscription.

  • Managed key custody with external KMS/HSM
  • Signed audit export — auditor-verifiable trail
  • SSO — SAML / OIDC for the control plane
  • TypeScript SDK
Buy Professional

Enterprise

Let’s talk
Scoped per organization, custom quote

Regulated organizations with auditors in the room.

Enterprise is scoped by conversation and billed by custom quote.

  • Everything in Professional
  • Self-hosted and air-gapped deployment, scoped with you
  • Custom framework adapters and audit consulting

On the roadmap

Not shipped — not part of this subscription.

  • Bring-your-own-HSM / customer-managed keys
  • WORM audit retention + SIEM streaming
Contact sales

Professional is billed annually through Edukas Solutions and renews automatically until cancelled. Team and Enterprise are scoped by conversation. Roadmap items are listed separately and are not included in today’s subscription. Prices are per organization, in USD. Subscriptions are currently offered to organizations in the United States only.

Point it at your hardest agent.

We’re onboarding a small group of design partners shipping high-stakes agents who need real answers for provenance, policy, deletion, and audit. Bring a use case; leave with a plan.