The blockchain isn’t just a trust layer.
It’s the full stack —
storage, verification, and proof.
Recall is a Rust-native vector database with cryptographic memory proofs. Every write is client-side encrypted with AES-256-GCM, persisted to Shadow Drive, and Merkle-rooted to a Solana Anchor program — so your agent’s memory is yours, auditable, and tamper-evident by construction.
AI agents have amnesia.
We gave them a spine.
Today's agents either lose everything between sessions or hand their memory to a vendor that owns it. Neither is acceptable for software meant to remember on your behalf.
Most “Web3 memory” projects write embeddings onchain — which is slow, expensive, and structurally wrong. Shadow Drive handles storage. The Anchor program handles proof. Hot reads live in cache. Each layer does exactly one job well.
01 · Sovereignty
Keys are derived from your Solana wallet. If you lose us, you don't lose your memory.
02 · Verifiability
Every write produces a SHA-256 leaf. Every batch produces a root. Every root lives on Solana.
03 · Speed, still
A Rust HNSW index under everything. 4.7ms P99 at 100K vectors. Trust doesn't have to be slow.
Four layers.
One contract.
Each layer is independently replaceable, independently auditable, and does exactly one thing. Compose them, run them yourself, or use our hosted API.
Common mistake
“Web3 vector DBs” that put embeddings onchain are doing it wrong. Chain blockspace is the most expensive storage on earth.
Two lines to remember.
One line to verify.
Install, configure with your wallet, write. Shadow Drive persistence and Anchor proofs happen in the background. Python and TypeScript are feature-complete and behaviorally identical.
If your agent can’t prove what it remembered,
it didn’t really remember at all.
The row
nobody else has.
Vector search is table stakes in 2026. The question isn't 'how fast.' It's who owns the index.
| Recall | Pinecone | Chroma | Weaviate | |
|---|---|---|---|---|
| Storage Ownership | Yours (Shadow Drive) | Vendor cloud | Self / vendor | Self / vendor |
| Encryption at Rest | AES-256-GCM, client-side | Server-side | Optional | Server-side |
| Cryptographic Proofs | Merkle → Solana Anchor | — | — | — |
| Key Sovereignty | Solana keypair-derived | Vendor-managed | Vendor-managed | Vendor-managed |
| Query Latency (P99) | ~4.7 ms | ~30 ms | ~18 ms | ~48 ms |
| Core Open Source | Apache-2.0 (Rust) | Closed | Apache-2.0 | BSD |
| Tamper-Evident Audit | Built-in | — | — | — |
Fair rails.
Open core.
The Rust core is Apache-2.0 forever. The hosted API is metered; you're paying for low-latency cache, Shadow Drive provisioning, and Anchor gas — not for owning your own memory.
- +Rust crate + local SDK
- +Self-hosted Shadow Drive
- +Direct Anchor writes
- +Memory Inspector UI
- +Community support
- +Hosted API + managed cache
- +Shadow Drive provisioning
- +1M vectors · 100k writes/mo
- +Dashboard + usage analytics
- +Email support
- +10M vectors · 2M writes/mo
- +Team keys + RBAC
- +Priority queue + SLA
- +Verified proof export
- +Slack-connected support
- +On-prem or dedicated cluster
- +Custom Anchor program
- +Dedicated solutions engineer
- +Compliance (SOC 2, HIPAA path)
- +24/7 on-call