Pricing
Priced per seat, metered on one thing.
There is exactly one action in the product with a real marginal cost. Everything else is a database query, and we do not think you should be counting those.
Free, and not a trial. Individual use is how the product spreads, so charging for it would be charging for our own distribution.
- ·Your own workspace
- ·Checkpoint and rehydrate
- ·MCP server and CLI
- ·Capped checkpoints per day
One person, working across as many projects as you like. No teammates - that is what Team is for.
- ·Everything in Solo
- ·Unlimited projects
- ·Higher checkpoint allowance
- ·A single seat, not a shared workspace
The difference that matters: more than one person writing to the same project memory.
- ·Everything in Solo
- ·Invite colleagues into one workspace
- ·Owner, admin, and member roles
- ·Shared projects across the team
- ·Higher checkpoint allowance
For organisations that need a contract, not a card.
- ·Everything in Team
- ·SSO through your identity provider
- ·Support SLA
- ·Invoicing and a signed DPA
What gets metered
One line item, not a bill you have to parse.
A checkpoint runs an extraction pass over your session. That call is the cost. The seat price includes an allowance set at several times ordinary use, so a normal month never touches it. The ceiling exists so a runaway loop in CI cannot quietly invert the economics.
| Action | Marginal cost | Metered |
|---|---|---|
| Checkpoint | The extraction call, effectively the entire marginal cost | Metered |
| Contradiction detection | Small, runs on a higher-tier model | Rolled into the checkpoint |
| Rehydrate | One indexed query. Fractions of a cent | Not metered |
| Handoff, log, status, search | Negligible | Not metered |
| Storage | Meaningful only at extremes | Fair-use ceiling only |
No key required
We pay for inference, not you.
You will not be asked for a model provider key. Charging a seat price and then asking you to fund the model calls on top would be charging for the same product twice, and it would put our costs on your monthly bill.
The consequence is ours to carry: the seat price has variable cost inside it, which is exactly why the included allowance is a real number rather than a formality.
Questions
What people ask about the bill.
- How much does Mneia cost?
- Solo is free. Pro is $15 a month for one person: unlimited projects and a higher checkpoint allowance, but no teammates. Team is $25 per user per month, adds shared projects and roles, and includes an allowance sized well above ordinary use. Enterprise is custom priced, for organisations that need a contract rather than a card. Two caveats worth stating plainly: self-serve billing is not live yet, so nothing is charged today and we set teams up directly; and the seat price is not final until we have measured what a real checkpoint costs to run. If it moves, it moves before anyone is billed.
- Is the free tier a trial?
- No. Solo is free and stays free. Individual use is how the product spreads, so charging for it would be charging for our own distribution. It covers your own workspace, checkpoint and rehydrate, the MCP server and the CLI, with a daily checkpoint cap.
- What exactly is metered?
- Only the checkpoint, because the extraction call it runs is effectively the entire marginal cost. Contradiction detection is rolled into the checkpoint. Rehydrate is one indexed query costing fractions of a cent and is not metered. Handoff, log, status, and search are not metered. Storage carries a fair-use ceiling only.
- Do I need to bring my own model provider API key?
- No. We pay for inference, not you. Charging a seat price and then asking you to fund the model calls on top would be charging for the same product twice. The seat price carries the variable cost, which is why the included checkpoint allowance is a real number rather than a formality.
- What does the Team plan add over Solo?
- The thing the product is actually for: more than one person writing to the same project memory. You invite colleagues into one workspace, they land in yours rather than a new one of their own, projects are shared across the team, and roles are owner, admin, and member. Conflict resolution, team handoffs, and the review app are on the roadmap and are not in the plan yet.