Agent Engine Memory Bank: what it remembers, who owns it, and what it costs
thecontinuitylayer.com/memory-systems/google-memory-bankA managed Google Cloud service that generates, consolidates and retrieves long-term user memories from agent sessions, keyed by a scope such as a user id.
- 1No
Is Agent Engine Memory Bank open source?
No, by Google Cloud's own page.
A managed Google Cloud service with no open-source core.
Yes means: The core is under an open-source license.
- 2No
Can you run Agent Engine Memory Bank yourself?
No, by Google Cloud's own page.
Runs in Google Cloud regions; no self-hosted option is described.
Yes means: It runs on your own machine or server.
- 3Partly
Can you take your memory out of Agent Engine Memory Bank?
Partly, by Google Cloud's own page.
Retrieving with a scope returns all memories for a user; no bulk export is described.
Yes means: An export, or the data sits in a standard store you own.
- 4Not stated
Does Agent Engine Memory Bank work with more than one model provider?
Google Cloud's pages do not say.
The service uses generative models to produce memories, without naming which; the SDK can be used with frameworks other than Google's, but nothing is said about non-Google models.
Yes means: It is not tied to one provider's models.
- 5Yes
Is there a hosted Agent Engine Memory Bank?
Yes, by Google Cloud's own page.
A fully managed Agent Engine service.
Yes means: A cloud or managed option exists.
- 6Partly
Does Agent Engine Memory Bank have a free tier, and what is the entry price?
Partly, by Google Cloud's own page.
No free tier is mentioned; the pricing document lists per-thousand-memories storage and retrieval rates.
Yes means: A free tier exists and the entry paid price is published.
- 7Yes
Does Agent Engine Memory Bank scope memory per user and per session?
Yes, by Google Cloud's own page.
The scope defaults to the session's user id and accepts custom keys such as a session id; only memories with the same scope are consolidated together.
Yes means: Both per-user and per-session or per-agent memory are supported.
- 8Partly
Can you delete a user's memories from Agent Engine Memory Bank?
Partly, by Google Cloud's own page.
A memory can be deleted by name; no delete-all-for-scope call is documented on the pages checked.
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: Proprietary cloud service. Every grade above is read from Google Cloud's own page on the day shown. If a page has changed, tell us.