Your company already has a memory.
It's just scattered.
Give your team and its AI agents one shared memory, in plain files your company owns.
Part of the story lives in your software.
The rest lives with your people.
- 01
Your systems record what happened.
Invoices, contracts, tickets, customer records, project updates. Each system holds one useful piece of the story.
- 02
Your people remember why.
Exceptions, judgment, commitments, and the reasoning behind decisions still live in conversations, or in someone's head.
- 03
Your AI agents start from zero.
Every new chat, coding session, or automated job begins without any of it, so someone pastes the context back in. Again.
You can't own the model.
You can own the memory.
The model your team uses will change, and so will the agents built on it. The knowledge your company builds with them is the asset. Keep it readable, inspectable, and portable, so it works with Claude, ChatGPT, Codex, or whatever comes next.
One memory for your people
and every agent they use.
When someone captures a decision or asks their AI to write context back, it becomes part of the team's memory. Everyone else, and every agent, works from it next time instead of starting over.
People
Read, write, and organize in the web app: a real editor, comments and suggested edits, a knowledge graph, and an activity feed of who changed what. Changes from agents and teammates appear without reloading.
Your AI tools
Claude, ChatGPT, Codex, Cursor, and any MCP client sign in once and work from the same knowledge. Headless agents and scripts use API keys you can scope to read-only or to specific projects.
Basic Memory agents
Hosted agents (in beta) maintain the knowledge for you: follow up on meetings, link related notes, and summarize what changed, with every edit open to review.
“Claude is the back-office secretary that runs everything... before Basic Memory I'd have been working 120 hours a week.”
Share broadly.
Restrict where it matters.
Most team knowledge should be easy to find and add to. Sensitive work, and the agents touching it, need tighter limits.
Roles
Owner, Admin, User Admin, Editor, and Viewer. Decide who manages the workspace and who can change what.
All team plans
Invite-only projects
Keep sensitive work in projects only some members can see or edit, with access set per member.
Business
Audit log
A record of who did what in the workspace, for the questions that come after a change.
Business
Scoped agent keys
Give an agent a read-only key that can't even see write tools, or a key that only reaches the projects you pick.
Pro and Business
Safe agent edits
Lock a note and no agent can change it. Agents can only overwrite the version they read, and every note records which person or agent last edited it.
Every plan
Your own database
Each workspace gets its own isolated database and storage, not rows in a shared table.
Every Cloud plan
Nothing your team writes
is ever really lost.
When people and agents both edit, mistakes happen. Every layer of recovery is there so you can undo them, and you can always take the whole thing with you.
- Every version of every note, with compare and restore
- Automatic daily snapshots, kept 30 days on Pro and Business
- Restore a file, a folder, or a whole project
- Verified daily backups to a second provider
- Export anytime as plain Markdown
One price for the workspace.
No charge per person.
Every plan includes usage credits for the work your workspace and its agents do, with a spending limit on from day one. Agents use credits, but they never count as members.
For a small crew and its agents. Scoped API keys, 30-day snapshots, 9,900 credits a month.
For the whole team. Invite-only projects, per-member access, audit log, 24,900 credits a month. SSO and a BAA available as add-ons.
More than 25 people, or need a security review? Talk to us about Enterprise.
What would you like your AI to know or do?
No architecture diagram required.
Start with the outcome.
Just connecting an AI tool to Basic Memory? Start with integrations →
Running Basic Memory for clients? The partner program for MSPs and agencies →