Build on SAIHM. Don’t build SAIHM again.
If you build agentic memory, you have spent — or are about to spend — two years on key management, erasure, sharing, and audit. SAIHM has shipped those. They are open source. Use them.
Most memory tools compete for retail convenience. SAIHM is built to the bar businesses and regulated enterprises audit against — and that bar is the moat.
Why partnering beats competing
The market for AI memory is not zero-sum. Every memory-using agent is a memory-buying agent. Total demand will grow faster than any one vendor can capture. Whether your customers buy from you on top of the protocol, or from SAIHM directly, the industry expands either way.
The hard parts of agentic memory are not storage; they are sovereignty (key custody), compliance (cryptographic erasure), interop (cross-vendor sharing), and accountability (audit trail). SAIHM ships those four. On a public chain. Under Apache 2.0. You can have them now, or rebuild them over the next two years.
Pricing
Public pricing — per-call PAYG and monthly subscription tiers — is published on pricing and applies to all users. Operators building on top — resellers, white-label vendors, downstream integrators — partner with SAIHM to receive special pricing: email ops@saihm.coti.global with the subject “Interested in Partnering”.
Build on top, not against
Your differentiator is your UX, your voice, your domain knowledge, your customer relationships — not the storage primitive. Customers do not care which memory backend their agent uses; they care about the experience.
You can ship an experience that is better than SAIHM’s own on top of the protocol. Better your customers are served by a great UX over SAIHM than by a mediocre UX over a custom backend — and rebuilding the four hard parts of memory is what makes most custom backends mediocre.
Partner through governance
SAIHM has a non-purchasable, non-transferable governance utility called gSAIHM. It is accrued by paid use of the protocol — you cannot buy it, sell it, or transfer it. It exists so that the parties driving the protocol’s economic activity have a real say in its evolution.
If you build on top, you accrue gSAIHM proportional to the volume of paid use you drive. That gSAIHM gives you a vote on emission-parameter and protocol-upgrade governance — you shape the protocol you build on. Pricing, fees, and sharing-tier policy remain operator-retained, so governance cannot vote away the commercial structure beneath your contracts.
Full details on /governance. Genesis transaction: 0x755beb60…0d0963a ↑.
Honest comparison vs the field
What each product’s canonical documentation states (research 2026-05-07). Where a property is not addressed in the docs reviewed, it is marked “not addressed” — not asserted as a defect. Full per-cell matrix with every citation: /comparison.
| Property | SAIHM | Mem0 | Zep | Letta | LangMem | Pinecone |
|---|---|---|---|---|---|---|
| User-held encryption keys | Yes (HKDF-from-wallet) | Not addressed | Not addressed | Not addressed | Not addressed | CMEK (operator-held, not end-user) |
| Per-memory cryptographic erasure | Yes (DEK destroyed; GDPR Art. 17) | DB delete (not stated cryptographic) | Not addressed | DB block delete (not cryptographic) | Not addressed | CMEK revoke = tenant-wide, operator-driven |
| Public-chain audit anchor | Yes (COTI V2) | Request log; not chain-anchored | Not addressed | Not addressed | Not addressed | Proprietary logs; not chain-anchored |
| Cross-vendor consent sharing | Yes (revocable) | LLM-agnostic; portability not addressed | Not addressed | Intra-deployment only | Not addressed | Export, not consent sharing |
| License | Apache 2.0 | Apache 2.0 + cloud | Graphiti Apache 2.0; Cloud proprietary | Apache 2.0 | MIT | Proprietary (BYOC) |
The pattern is structural: the field competes on storage, retrieval, and context-engineering — while the four hard parts (sovereignty, cryptographic erasure, chain-anchored audit, cross-vendor consent sharing) are open ground SAIHM already ships under Apache 2.0. That is what you would rebuild over two years, or build on now. Each product above has genuine strengths in its own positioning; /comparison documents what each does well and cites the source behind every cell.
What this isn’t
- Not an acquihire offer. No one is buying you out.
- Not a relicensing demand. SAIHM is Apache 2.0; build whatever you want on top.
- Not a hostile move. The protocol grows when you grow — by construction.
Get in touch
Partnership, white-label, or governance enquiries: ops@saihm.coti.global.