Apache 2.0 · open-source core
Your drawer.
Your infrastructure.
Run the core on your own machine or server. Keep a small, inspectable store for your agents without adding embeddings, a knowledge graph or a model to the storage layer.
Open-source core. Hosted Free plan. No card needed to start.
{
"key": "notes/project-brief",
"kind": "note",
"labels": [
"project"
],
"value": {
"text": "Build a simple, inspectable store for connected agents."
},
"searchable_text": "Build a simple inspectable store for connected agents"
}Illustrative object input—not a live account or tool result.
“put · get · list · search · delete”
notes/project-brief“MCP is an adapter. The objects are yours.”
SQLite core → one shared database or serverStart with the core, not a platform
The open-source core uses SQLite and exposes five operations: put, get, list, search and delete. Objects carry keys, kinds, labels, JSON values, versions and timestamps, with optional behavioral metadata. The MCP adapter lets compatible agents use that storage contract.
Follow the repository’s getting-started guide for the current Docker and local setup. Configure every client to use the same database or server if you want shared access. Two separate SQLite files are two separate stores, even if both clients call them AgentStore.
Self-hosted and managed are different paths
Self-hosting gives you direct control over the core and your data file. You operate the server, secure access and take backups. The core’s local single-user setup is not a turnkey multi-tenant SaaS, and a private local server should not be exposed publicly without appropriate protection.
Cloud manages the hosted infrastructure and provides account-scoped data, a web viewer, revocable access keys, remote MCP, REST and plan management. Cloud plan limits do not apply to your self-hosted core; your own infrastructure still has capacity and operating costs.
Keep integrations at the edge
MCP connects agents to the store, but it is not the canonical storage protocol. Keeping that boundary clear lets the deterministic core stay small while adapters handle client-specific setup and permissions.
The core is Apache 2.0 licensed. Read the repository, license and current documentation before adopting it. No signup is needed to run the open-source core. If you prefer not to operate the infrastructure, start with the hosted Free plan and connect clients to your Cloud account.
Three steps to a useful store.
- 01
Read and run the core
Use the GitHub getting-started guide for the current local or Docker setup.
- 02
Connect to one shared store
Point each compatible client at the same database or server and approve its tools.
- 03
Own the operations
Back up your data, restrict server access and test saving and retrieval from a fresh session.
A few practical questions.
Does self-hosting need a paid plan?
No. The open-source core is free to self-host under Apache 2.0. You pay your own infrastructure costs, not Cloud subscription fees.
Is the hosted SaaS repository also the open-source core?
No. The public core and managed Cloud application are separate projects. The public repository is the source for the self-hosted core.