Named after the river
of forgetting.
Built so nothing is.
User-owned memory for AI agents — stored on Walrus, anchored on Sui, portable across apps.
Tell Lethe your crypto style. It remembers across sessions, not just this chat.
Every memory is Seal-encrypted end-to-end on Walrus — even Lethe’s servers can’t read it. Decryption needs on-chain approval you control.
Your memory is not trapped in one app. Open another Lethe agent and it already knows you.
The loop, in three frames
- → the fact settles here
- → model — switch mid-chat
- → import / export
- → verify on Suiscan ↗
- → a second app, your grant
- → revoke → it forgets
Why Walrus needs Lethe
Archives pay once; a memory layer is designed to renew every epoch — recurring WAL demand per user.
A few hundred bytes that know you — people pay for identity, not gigabytes.
Google login, no wallet, no gas — the only Walrus write path a normal person can walk through.
And because every memory is a Sui object, Lethe is a primitive other apps — and other contracts — build on. Demand compounds across the ecosystem, not inside one app.
“Remove Walrus and Lethe breaks. Ship Lethe and Walrus gets what it’s missing: users who come back.”
Pricing
“Your memory is free forever. We charge for the intelligence on top.”
Premium models, higher limits, unlimited memory.
Bring your own model keys — your memory plane stays the same.
Coming soonEverything in Pro, premium models included, early access.
Coming soon“We lock you in with value, not custody — export and leave any day.”
Pricing in preview · validating with early users
Free $0 | Recommended Pro $9/mo | Premium $19/mo | |
|---|---|---|---|
| Memory | |||
| Memories stored | 100 | Unlimited | Unlimited |
| Recall history | 30 days | Unlimited | Unlimited |
| Derive · recall | ✓ | ✓ | ✓ |
| Verifiable export | — | ✓ | ✓ |
| Agents & portability | |||
| Connected agents | 1 | 10 | Unlimited |
| Grant / revoke on-chain | ✓ | ✓ | ✓ |
| Portable across apps | ✓ | ✓ | ✓ |
| Privacy | |||
| Seal end-to-end encryption | ✓ | ✓ | ✓ |
| Formally verified (19/19) | ✓ | ✓ | ✓ |
| Models | |||
| Free models · daily limits | ✓ | ✓ | ✓ |
| Switch model mid-chat | ✓ | ✓ | ✓ |
| Premium models | — | Add-on | ✓ |
| Bring your own keys | — | ✓ | ✓ |
| Early access | — | — | ✓ |
Embed verifiable, user-owned memory in your own agent or app. Grant/revoke on-chain, Seal-encrypted, formally verified.
Usage-based · pay per memory operation
- Derive · recall · export
- Grant · revoke
- Portable across apps
- Seal end-to-end encryption
- Formally verified (19/19)
- Continue with Lethe handoff
More models as they ship — your memory works with all of them.
How Lethe is different
| ChatGPT memory | Mem0 | Lethe | |
|---|---|---|---|
| Who owns the memory | The app | The app | You — an on-chain object |
| Privacy | Policy | Policy | Cryptographic (Seal) |
| Portable across apps | No | SDK (vendor cloud) | Yes — grant/revoke on-chain |
| Leave with your data | Limited | Export | Export, one click |
| Model lock-in | Tied to the platform | Vendor cloud | Switch models, memory follows |
Memory you own, not memory an app stores
Your memory is a Sui object, and access is a grant you issue to an agent’s address — and revoke the same way, on-chain and verifiable. It doesn’t live in any one app’s database, so it isn’t trapped there. Pulse reads it only while it holds a grant; revoke and Pulse forgets.
Ownership is an object you hold; access is a transaction anyone can verify. These aren’t policy commitments a company can quietly change — they’re properties of where the memory lives.
Lethe’s unit economics are denominated in WAL and SUI by design: every user action is sponsored Sui gas; every memory is a Walrus blob Lethe pays for. As users grow, Lethe drives real, recurring WAL demand — storage plus renewals, for every user, every epoch.
Revenue covers costs, funds storage and renewals for all users, and scales Walrus consumption with adoption.
Every Lethe user = a paying Walrus customer · verifiable on-chain
Three rings around one vault
Most roadmaps ask you to believe. This one is mostly receipts — verify any line.
The whole loop, shipped — derive, encrypt, recall, revoke, export. Formally verified (19/19).
RevenueFree — live today.
This ring is finished — it is the proof the others stand on.
Live on Sui testnet — vault birth, Seal-encrypted writes, cross-app recall, revoke, export. Formally verified (19/19).
The product crypto-natives can use end to end, on testnet today.
One unlock awayMainnet (Q3–Q4 2026) — Pro switches on and starts funding WAL storage and renewals.
RevenueMainnet. Seal-gated selective sharing — share one memory, not the vault.
Pay for Pro in stablecoins — USDC, no card.
The SDK wraps the paths Pulse runs in production — cross-app memory works now.
One unlock awayA shared-registry policy lets any Sui app run its own decrypt sessions.
RevenueShared-registry policy: third-party apps run their own decrypt sessions.
On the horizon: memory other Sui contracts can read — a lending market that honors your no-leverage history, on-chain. Impossible without the object model.
Google login and ChatGPT import — a normal person walks in today.
One unlock awayBYOK brings any frontier model; memory from usage, not just chains.
RevenueMemory editing; MemWal adapter the day @mysten/memwal ≥0.0.4 publishes.
The inner ring is the biggest one — and it already shipped. The rings ahead are smaller.