Memobase: what it remembers, who owns it, and what it costs
thecontinuitylayer.com/memory-systems/memobaseUser-profile memory for chatbots: per-user profiles and event memory, as a dockerized server or Memobase Cloud.
- 1Yes
Is Memobase open source?
Yes, by memodb-io's own page.
The repository is Apache-2.0.
Yes means: The core is under an open-source license.
- 2Yes
Can you run Memobase yourself?
Yes, by memodb-io's own page.
Fully dockerized, with server setup docs and a default local address.
Yes means: It runs on your own machine or server.
- 3Partly
Can you take your memory out of Memobase?
Partly, by memodb-io's own page.
Profiles are retrievable as JSON and the data API can return all of a user's records; no bulk export is documented.
Yes means: An export, or the data sits in a standard store you own.
- 4Not stated
Does Memobase work with more than one model provider?
memodb-io's pages do not say.
The README shows OpenAI and Ollama tutorials; no provider list appears on the pages checked.
Yes means: It is not tied to one provider's models.
- 5Yes
Is there a hosted Memobase?
Yes, by memodb-io's own page.
Memobase Cloud offers a free tier for testing.
Yes means: A cloud or managed option exists.
- 6Partly
Does Memobase have a free tier, and what is the entry price?
Partly, by memodb-io's own page.
A free tier is stated; no paid prices were found on official pages.
Yes means: A free tier exists and the entry paid price is published.
- 7Partly
Does Memobase scope memory per user and per session?
Partly, by memodb-io's own page.
Per-user by design (memory for the user, not the agent); no session scoping is described.
Yes means: Both per-user and per-session or per-agent memory are supported.
- 8Yes
Can you delete a user's memories from Memobase?
Yes, by memodb-io's own page.
Users, their records and individual profile entries can be deleted through the API.
Yes means: A documented way to delete everything for one user.
What these grades say about continuity, and what they do not.
Every grade on this site is read from the maker's own pages. The Continuity Framework asks five things of any system that carries state: that it carry, govern, evolve, prove and forget. These tests reach carry, govern and forget; they do not reach evolve or prove, which no maker's page documents in a gradeable way. A high letter is a good memory system, not a continuity layer.
- M1 Open sourceCarry
- Open source means the memory engine can outlive the vendor; the state is not hostage to a contract.
- M2 Self-hostCarry
- Self-hosting puts the store under the owner's control, which is the precondition for every other obligation.
- M3 ExportCarry
- An export is question C3: can the state leave in a form another system reads? A standard store you own answers it; a proprietary dump only partly.
- M4 Any modelCarry
- Working with more than one model provider is question C2: the memory, not the model, holds the state.
- M7 ScopingGovern
- Scoping per user, agent and session is question G2: who may read and write each item. It is the floor of governance, not the ceiling.
- M8 DeleteForget
- A documented delete for one user is rung 5 of the erasure ladder: the record leaves the store. Derived memories, the index and backups are not covered unless the maker says so. Rung 5 of the erasure ladder: delete the record.
License as stated: Apache-2.0. Every grade above is read from memodb-io's own page on the day shown. If a page has changed, tell us.