About
The context layer is permanent. Nobody built it for teams.
Mneia is the shared project memory and handoff layer for teams working with AI agents. Three operations: checkpoint, rehydrate, handoff. Everything else serves them.
The bet
In five sentences.
- Long-running agent sessions degrade. Context windows fill, compaction is lossy, and recall drops well before the window is full. This is measured, not anecdotal.
- Every provider has responded by externalising context: memory tools, compaction, project instruction files. Which means the context layer is a permanent architectural component, not a temporary hack.
- The existing products are built for one user and one agent. Nobody has built the layer for several humans and several agents working the same project over weeks.
- Our wedge is the artifact nobody ships: a handoff. Not a memory store you query, but an object a person or an agent receives when picking work up.
- What keeps a team is not the feature list. It is becoming the record of what the team decided and why, which is not something a competitor can copy, because it is the customer's own history.
The thesis
“The unit of value is not memory. It is the handoff.”
Every competitor built a place to store context and a way to query it. That is a database posture. The actual job is a transfer: work stops with one actor and resumes with another.
Two things follow. Once work is transferred between people, the store has to handle several writers, which forces provenance, conflict resolution, and permissions, and those cannot be bolted onto a single-user product without changing its thesis. And a handoff has to survive crossing tools. Model providers are structurally incentivised against that kind of neutrality. The gap is permanent.
Who it is for
Built for a company, landed through engineering.
Context does not stop at a team boundary. A decision made in the payments team changes what sales can promise; an open question in platform blocks three feature teams. So the data model assumes the company from the first migration: teams as a first-class entity, a visibility hierarchy, function on the team. The sales motion does not.
Living in Claude Code, Cursor, or Codex daily. Cross-session context loss, compaction damage, re-explaining. Free tier, permanently.
Especially mid-migration or mid-refactor. Context sits in individual heads, onboarding onto in-flight work is expensive, and agents contradict decisions that were already settled.
No record of what agents decided or why. No audit trail. No governance over what context an agent is allowed to see.
Support, sales, and operations people build with agents too. They have a real question with no trustworthy current answer: is this on the roadmap, who owns it, what is the state?
Licensing
Open clients, hosted service.
The client packages are Apache 2.0: the CLI, the MCP server, and the core, which holds the schema definitions, the handoff format, the extraction prompts, and the ranking algorithm. The hosted API, the store, billing, and the review surfaces are proprietary.
Being straight about what that means: Mneia runs as a hosted service. The clients require an account and do not function without it. We would rather say so here than have you find out after installing.
Scope
Three operations, done properly.
Checkpoint, rehydrate, handoff. We sit beside the frameworks and the observability tools you already run, never above them, and everything we build serves those three operations rather than competing with the rest of your stack.