Virex Memory vs Letta
Letta approaches memory as part of how an agent is built: agents that hold state across time, with memory as an architectural property. That is a different starting point from wanting the coding agent already on your machine to remember your codebase.
The short answer
The question is whether you are building the agent. If you are, a stateful-agent framework gives you memory as part of the agent design, and Virex is not competing for that. If your agents are Claude Code, Cursor, or another client somebody else built, Virex Memory gives them shared organization memory over MCP without you designing a memory architecture at all.
What each one is.
Stated at the level both companies state it publicly, without guessing at anyone internals.
Virex Memory
A memory service for coding agents you did not build. Agents write what they learn while working and retrieve it by meaning later, scoped to your organization. Reached over MCP, plus SDKs, a CLI, and a portal.
Letta
A framework and server for building stateful agents that persist state and memory over time, aimed at developers constructing their own agents. For current architecture, interfaces, and pricing, see their site.
Where they actually differ.
Only dimensions we can state accurately for both. Anything that changes often, including pricing and feature lists, belongs on the vendor own site.
| Dimension | Virex Memory | Letta |
|---|---|---|
| What you bring | Agents somebody else built, already running on your machines. | An agent you are building yourself. |
| What it provides | A memory service the agent calls, with scope, ranking, and expiry already decided. | A framework for agent state and memory as part of agent design. |
| Primary buyer | A software team running AI coding agents. | A developer or team building agents. |
| Integration | Model Context Protocol, so Claude Code, Cursor, Codex, Gemini CLI, opencode, and Cowork all reach the same corpus. | See vendor site for current interfaces. |
| Agent state | Out of scope. Session state belongs to the agent, and for Claude Code sessions to Virex Remote. | Central to the model. |
| Sharing model | Organization-scoped by default so teammates agents benefit from each other. | See vendor site. |
| Pricing | $15 per seat, per month, per product, flat across both products. | See vendor site. We do not publish other companies pricing. |
Architecture you own, or a service you call.
Both are legitimate. They ask for different amounts of work and give back different amounts of control.
Memory as design against memory as dependency
A stateful-agent framework makes memory part of how your agent thinks, which is powerful when you control the agent. Virex Memory is a service an existing agent calls, which is the only option when you do not.
The work you are signing up for
Building agents means owning their memory model, retention, and failure behaviour. Buying memory means accepting our decisions on those and getting value the same week.
What the team gets
Organization scope is a product decision here: a memory one developer agent writes is retrievable by a teammate agent. In a framework, cross-user sharing is something you design and operate yourself.
When Letta is the better choice.
We would rather you find us when we are the right answer than talk you into the wrong product.
- You are building your own agents and want memory to be part of their architecture.
- You need to control how state is compacted, retained, and reasoned over.
- Your agents do not speak MCP and you would rather not use an SDK.
- Your use case is not coding, which is what Virex Memory is shaped around.
Virex Memory and Letta questions
Is Letta a competitor to Virex Memory?
They appear in the same searches and solve different problems. Letta is a framework for building stateful agents that carry their own persistent memory. Virex Memory is a memory service for the coding agents you already run and did not build.
I want agents with long-term memory. Which do I need?
If you are building the agent, a stateful-agent framework gives you the memory architecture as part of the agent design. If the agent is Claude Code or Cursor and you just want it to remember your codebase, that is what Virex Memory does.
Can I use Virex Memory with agents I built myself?
Yes, through first-party SDKs and REST and gRPC on one host, with the same tenancy and access rules. The product is shaped around coding agents and team workflows, so weigh it on that fit.
Does Virex Memory manage agent state?
No, and it does not try to. It stores and retrieves memories your agents choose to write. Session and conversation state belongs to the agent and, for Claude Code sessions, to Virex Remote.
How is Virex Memory priced?
$15 per seat, per month, per product. Your organization holds one subscription with a line item per product.
Memory for agents you did not build.
Subscribe to Virex Memory, assign a seat, and connect the clients your team already runs.