Three tiers. One shared memory.
Free through four seats. Team starts at the fifth. Enterprise runs self-hosted in your own infrastructure.
| Seats | Monthly | Annual |
|---|---|---|
| 1 to 4 seats | $0 | $0 |
| 5 seats or more | $15 | $12 |
For teams getting started
Free
1 to 4 seats
$0
Free forever
The whole product, for a team of up to four.
Show 12 included capabilitiesHide 12 included capabilities
- Preserve decisions, constraints, failed approaches, and review outcomes
- Share one memory layer across supported coding agents
- Retrieve context by file, function, and line
- Keep branch and commit provenance on every memory
- Anchor new commits with the post-commit hook
- Connect Cursor, Claude Code, Windsurf, Codex, and Zed over MCP
- Match memory access to repository permissions
- Connect repositories through the GitHub App
- Use scoped API tokens that can be revoked
- Sign in from terminals with a device code
- Use up to 4 seats without a credit card
- Get community support
- Preserve decisions, constraints, failed approaches, and review outcomes
- Share one memory layer across supported coding agents
- Retrieve context by file, function, and line
- Keep branch and commit provenance on every memory
- Anchor new commits with the post-commit hook
- Connect Cursor, Claude Code, Windsurf, Codex, and Zed over MCP
- Match memory access to repository permissions
- Connect repositories through the GitHub App
- Use scoped API tokens that can be revoked
- Sign in from terminals with a device code
- Use up to 4 seats without a credit card
- Get community support
For teams of 5 or more
For growing engineering teams
Team
5 seats or more
$12
Per user / month, billed annually
One plan for every team above four seats.
Show 3 plan additionsHide 3 plan additions
Everything in Free, plus:
- Use 5 or more seats
- Choose monthly or annual card billing
- Get support by email
Everything in Free, plus:
- Use 5 or more seats
- Choose monthly or annual card billing
- Get support by email
For organizations with regulatory requirements
Enterprise
Self-hosted deployment
Custom
Annual retainer, set for the rollout
A deployment Memkith configures in your own infrastructure, supported on an annual retainer.
Show 10 plan additionsHide 10 plan additions
Everything in Team, plus:
- Run the database and compute inside your own infrastructure
- Keep memories in your network for HIPAA and similar regulatory requirements
- Have Memkith engineers configure and validate the deployment
- Retain hands-on support for operations and upgrades
- Sign in through your identity provider
- Get answers during your security review
- Agree on pricing for the rollout
- Pay by invoice or purchase order
- Use net payment terms
- Work with a named contact
Everything in Team, plus:
- Run the database and compute inside your own infrastructure
- Keep memories in your network for HIPAA and similar regulatory requirements
- Have Memkith engineers configure and validate the deployment
- Retain hands-on support for operations and upgrades
- Sign in through your identity provider
- Get answers during your security review
- Agree on pricing for the rollout
- Pay by invoice or purchase order
- Use net payment terms
- Work with a named contact
Security you can check
If your procurement process needs a SOC 2 report or a signed business associate agreement today, Memkith is not ready for you yet, and this page is not going to imply otherwise. Here is what is actually running, and what is not.
Running today
Six mechanisms in the product now. Every row names something you can go and check.
- Repository permissions
- Memory inherits the access rules the code already has. Memkith keeps no second permission model to drift out of sync with your repository's.
- Git and branch scope
- The local boundary. A memory belongs to the branch and the commit its code lives on, so its scope is checkable rather than asserted.
- Row-level security
- Memories are read and written over an authenticated API that runs every query under a role Postgres row-level security applies to. Identity is the bearer token, and no caller passes a user id.
- Encrypted in transit and at rest
- TLS on every connection, and encryption at rest on the managed Postgres the memories are stored in.
- Scoped, revocable API tokens
- Each token carries explicit scopes and an expiry, and can be revoked from settings at any time.
- GitHub App, not a personal token
- Installation and repository access run through an app you install and can uninstall, rather than through a long-lived personal access token.
Not yet
Four things a procurement process will ask for and not find. None of them carries a date.
- SOC 2 Type II
- Planned and undated. No audit has begun and no report exists. Nothing on this site claims one.
- HIPAA business associate agreement
- Planned and undated. Memkith does not sign a BAA today, and the hosted product should not be used with protected health information. Teams with HIPAA obligations run the Enterprise deployment in their own infrastructure, where memories never reach Memkith's servers.
- Written security overview
- Planned. The mechanisms running today are real, and a formal overview, a subprocessor list, and a disclosure process are not written yet.
- Published data processing terms
- Planned. Retention, deletion, and model training are not covered by a written policy yet, so this page does not summarise one.
One email when the SOC 2 Type II report exists. No audit has begun, so this is not a short wait.
The mechanisms running today are described in more detail on the security page. Nothing in either register carries a date. A published compliance date that slips costs more credibility than the silence it replaced.
Read this before you propose it
What counts as a seat?
A person whose agents read or write memory in your workspace. Agents are not seats. Running Claude Code and Cursor against the same codebase is one seat, which is the entire point of memory that outlives the tool.
Monthly or annual?
Either. Team is $15 per user with monthly billing or $12 per user per month, billed once for the year. Moving from monthly to annual is prorated.
When should we talk about Enterprise?
When memories cannot leave your infrastructure. Enterprise runs the database and compute inside your network, which is usually a HIPAA or similar regulatory requirement. Memkith engineers configure the deployment with you and support it on an annual retainer, and the agreement covers invoice or purchase-order billing, net payment terms, and a named contact.
What happens if we stop paying?
The account returns to Free. Memories are retained and stay readable, and writes pause above four seats until seats are removed or billing resumes. Nothing is deleted because an invoice lapsed.
What if our agent is not one of the four?
Any MCP-capable agent can be pointed at the Memkith server by hand.
memkith integrate writes native configuration for Claude Code, Cursor, Codex, and Zed, and those four are what the command knows, not the limit of what connects.Do you train models on our memories?
No, we do not. Your codebase memories are for you to own.