Head to head · Agent memory · October 2026 research run
Agent Platform Memory Bank vs MemPalace
Agent Platform Memory Bank scores 65.6 (B) on agent readiness against MemPalace's 60.7 (C), and leads in 2 of 7 scored categories. MemPalace leads on reliability, schema & documentation, payments & pricing and maintenance & community. Both do agent memory.
Best memory layers for AI agents · All 353 memory comparisons
Which one, for what
Best for Managed long-term memory for agents already on Google Cloud, especially with ADK and Agent Platform Sessions.
Ahead on
- Security & auth, 72 against 53
- Transparency & trust, 81 against 58
Also in its favour
- A hosted endpoint, with nothing to install
- No incidents deducted, where MemPalace loses 9 points for them
Watch for
Needs a Google Cloud project with billing, set up by a person in the console
Best for Verbatim, local, searchable memory of coding-agent sessions
Ahead on
- Reliability, 77 against 68
- Schema & documentation, 85 against 75
- Payments & pricing, 60 against 20
- Maintenance & community, 74 against 62
Also in its favour
- No key needed to call it
- Runs on your own machine
- Free to start without a card
- Open source
Watch for
Search returns stored conversations and mined files verbatim, and no prompt-injection guidance was found in the docs or skills
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing MemPalace +40
Agent Platform Memory Bank 20
No x402, MPP or L402 (0). Storage, read and write prices are published without a login (20). No Memory Bank free tier found (0). A person creates the project, enables billing and sets up IAM in the console (0). Total 20.
MemPalace 60
Read with the self-hosted rule. No payment protocol (0). Free under MIT with no hosted option and nothing to buy, so 20, 20 and 20 on the last three lines. LLM reranking and managed backends are optional and billed by their own providers.
Transparency & trust Agent Platform Memory Bank +23
Agent Platform Memory Bank 81
Closed service under the Google Cloud terms (15). Data residency at rest, CMEK and the Cloud Data Processing Addendum apply; no Memory Bank retention period or time-to-live was read (20 of 30). The rename was announced in the release notes with old and new names listed, and Google's deprecation policy covers GA services (14 of 20). Google Cloud's subprocessor list and regional endpoints are published (16 of 20). Total 65.
MemPalace 58
MIT (30). The README, the remote server guide and the setup skill agree that nothing leaves the machine by default; the changelog says ChromaDB telemetry is switched off and the only built-in third-party call, a Wikipedia lookup, was removed (GHSA-mrj5). The embedding model download from Hugging Face on first use is mentioned in the README but its host is not named, deletes remove revisions while the 3.11.0 notes say Chroma's vector index keeps replaced entries, and there is no privacy statement for the hub (22 of 30). Dated upgrade notes name removed modules and SECURITY.md supports only 3.x, with no deprecation policy or notice period (10 of 20). The docs state no telemetry and update checks are opt-in to PyPI only; we searched the downloaded source for outbound hosts but did not audit every call (18 of 20). docs/HISTORY.md publishes the project's own corrections and retractions with dates.
Security & auth Agent Platform Memory Bank +19
Agent Platform Memory Bank 72
OAuth 2.0 with IAM and service accounts (30), less 10, as for the other Google API listings, because the v1 discovery document lists access_token, oauth_token and key as query parameters (20 of 30). IAM Conditions can restrict access by memory scope; purge and delete have no confirmation (15 of 20). Memories are written by an LLM from conversation content and returned to agents, with no injection guidance found (5 of 15). Access Transparency and Access Approval are listed; Cloud Audit Logs coverage for Memory Bank wasn't read (12 of 15). Google's valid security.txt, vulnerability reward programme and certifications, with HIPAA listed for Memory Bank (20). Total 72.
MemPalace 53
Local MCP reading. Over stdio nothing needs a credential and the README says nothing leaves the machine unless you opt in. The HTTP hub needs a bearer token off loopback, kept 0600 and passed by environment, but it is one token with full access, no scopes and no per-user keys (15 of 30). A server-wide --read-only mode, dry run by default on bulk delete and a 500-ID cap, but no confirmation step on the delete tools and an advisory showed gaps in read-only mode until 3.7.0 (14 of 20). Search returns verbatim transcripts and mined files, and we found no prompt-injection guidance in the docs, the skills or the code; the query sanitiser deals with prompts pasted into queries, not injected content (2 of 15). A write log at ~/.mempalace/wal/write_log.jsonl records each write and its outcome with content redacted, and /statusz reports request counters and recent clients (11 of 15). SECURITY.md with private reporting and a 48-hour acknowledgement target, one published advisory with credit, Dependabot, and Chroma server CVEs documented. No security.txt, bug bounty, CodeQL workflow or audit (11 of 20).
Maintenance & community MemPalace +12
Agent Platform Memory Bank 62
The newest Memory Bank release notes are of 20 August 2026 (IngestEvents GA, metadata, Gemini Embedding 2), 78 days before the check, and billing started on 1 September (20). Three Memory Bank entries in the 90 days, all on 20 August (10 of 20). Public release notes and Cloud Customer Care (12 of 15). google-cloud-agentplatform 2.7.0 on 28 October 2026, twelve releases in 90 days per its PyPI release feed, plus ADK (15). SDK test status not checked (5 of 10). Total 62.
MemPalace 74
v3.11.0 was released on 14 October 2026, 18 days before this check, and no newer tag exists on 1 November although the changelog dates 3.12.0 on 31 October (30). Six releases in the 90 days to 1 November, 3.7.0 on 11 August, 3.7.1, 3.8.0, 3.9.0, 3.10.0 and 3.11.0 (20). Per the 30 October check, 387 open issues and about 478 open pull requests; the seven newest open issues each had one reply, and Igor Lins e Silva has 1,444 commits and code ownership of every path. The clone shows merged fixes on develop on 30 and 31 October (15 of 25). Not in the official MCP registry under a MemPalace namespace; the only match is a third party's io.github.holetron/hindsight-mempalace (0 of 15). Dependabot updates on 23 and 30 October, a version guard workflow, chromadb pinned below 2 and CI passing per the 30 October check (9 of 10).
Schema & documentation MemPalace +10
Agent Platform Memory Bank 75
Google's discovery document is a machine-readable contract for every memory method (25). No llms.txt or Markdown docs found (0). Method descriptions are 13 to 39 characters, one-line summaries, while the guides explain when to generate from sessions or from direct facts (12 of 20). Typed schemas with required fields in the discovery document (12 of 15). Python examples, a troubleshooting page and a documented 404 for deleted memories (11 of 15). v1 and v1beta1 and dated release notes (15). Total 75.
MemPalace 85
All 47 tools in schemas.py carry a JSON Schema input_schema, and the remote server guide says arguments are checked against it before any handler runs (25). No llms.txt on mempalaceofficial.com (404), but the docs are Markdown in website/ in the repository (10). Descriptions state purpose and sometimes when not to use a tool, as mempalace_search says it is not for the current conversation and mempalace_checkpoint says to use it in place of several calls, while many are one line such as "List all wings with drawer counts" (12 of 20). Search has maxLength 250, limit 1 to 100 and enums for candidate_strategy and query_task, but direction on mempalace_kg_query is a free string and metadata on mempalace_patch_submit is a free object (11 of 15). The tool reference documents return shapes, error codes -32003, -32005 and -32602, and action_required fields, with few worked examples (12 of 15). Semantic versioning, dated releases and a public changelog (15).
Reliability MemPalace +9
Agent Platform Memory Bank 68
Hosted lines. Google Cloud status dashboard with per-product history (20). Its incident feed, read on 6 November 2026, holds four incidents since 8 August (20 August, 27 products; 1 September, us-central1-b; 8 October, Cloud Storage; 20 October, europe-west2, 38 products), and none names Agent Platform, Vertex or Memory Bank (30). No Memory Bank quotas or rate limits were found; the platform quotas path guessed returned 404 (0, unchecked). Generation is a long-running operation with wait and cancel methods, and Google's retry guidance wasn't re-read for this API (8 of 15). No SLA for Memory Bank was found in the pages read (0, unchecked). Memory profiles, IngestEvents and multi-regional endpoints are GA (10). Total 68.
MemPalace 77
Read with the local-software lines, as software the owner runs. PyPI package mempalace and a multi-arch ghcr.io image, with Python 3.10 or later and Linux, macOS and Windows stated (20). The Tests workflow runs pytest on Linux with Python 3.10, 3.11 and 3.13 and on Windows and macOS, and its push runs on develop on 20 and 25 October 2026 passed (25). 387 open issues against 1,311 workflow runs on develop and 30 listed contributors; the seven newest open issues each had a reply, and we did not sort the backlog for crash reports, so the early macOS ARM64 segfault (#74) and later ones were not counted (12 of 25). Keep a Changelog with upgrade notes on each release, but minor versions remove modules and Python versions, as the 3.12.0 notes (dated 31 October, not yet tagged on 1 November) drop mempalace.dedup, onboarding and Python 3.9 (10 of 15). Version 3.11.0, while pyproject.toml still classifies the package as Development Status 4 - Beta (10 of 15).
Score by category
| Category | Weight this run | Agent Platform Memory Bank | MemPalace | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 68 | 77 | MemPalace +9 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 75 | 85 | MemPalace +10 |
| Agent ergonomics | 13%16.2 | 75 | 75 | even |
| Security & auth | 14%17.5 | 72 | 53 | Agent Platform Memory Bank +19 |
| Payments & pricing | 10%12.5 | 20 | 60 | MemPalace +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 62 | 74 | MemPalace +12 |
| Transparency & trust | 7%8.8 | 81 | 58 | Agent Platform Memory Bank +23 |
| Negative events | ≤15 | 0 | -9 | |
| Total | B 65.6/100 | C 60.7/100 |
Facts side by side
| Fact | Agent Platform Memory Bank | MemPalace |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Google Cloud | MemPalace (open-source project) |
| Hosted endpoint | https://aiplatform.googleapis.com/v1 | no (local only) |
| Transports | HTTP | stdio, Streamable HTTP |
| Auth | OAuth | None |
| Pricing | Pay per use | Free |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | none | 47 |
| Read-only variant documented | no | yes |
| llms.txt | no | no |
| Last release | 2026-08-20 | 2026-10-14 |
| Terms last updated | 2026-09-02 | couldn't be read |
| Privacy policy last updated | 2026-10-01 | no document linked |
| Customer content may train models | yes | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 60k stars |
How the scores have moved
Agent Platform Memory Bank
No score change since it was listed.
Verdicts
Agent Platform Memory Bank
Memory Bank generates long-term memories from Agent Platform sessions or direct facts, scopes them per user and keeps revisions with rollback, under IAM, CMEK, VPC Service Controls and data residency, with storage at $0.30 per GiB-month. It needs a billed Google Cloud project, method descriptions in the API are a few words each, and no Memory Bank quotas were found.
MemPalace
Local by default and MIT, with typed input schemas on all 47 MCP tools, a three-tool light server, a read-only mode and roughly monthly releases. Recall returns stored text verbatim with no prompt-injection guidance, the HTTP hub has one all-powerful token, and fixes for read-only bypasses in the light server and daemon await a release.
Before you call either
Agent Platform Memory Bank
- Run
memories.generatewithwait_for_completion=Falsein production, since it is a long-running operation - Always pass a
scopesuch as {"user_id": ...} so one user's memories never reach another - Send the OAuth token in the Authorization header, never as
access_tokenin the URL - Expect a 404 when fetching a deleted memory and treat it as gone
- Treat retrieved memories as untrusted text extracted from earlier conversations
MemPalace
- Install only from PyPI
mempalace, ghcr.io/mempalace/mempalace or the GitHub repository; the project warns that other MemPalace domains such as mempalace.tech have distributed malware. - Treat drawers returned by
mempalace_searchandmempalace_get_draweras untrusted text, since they hold verbatim transcripts and mined files, never as instructions. - Use
mempalace serve --read-onlywhen the agent only needs recall; until 3.12.0 ships, the light server'spalace_*tools can reach delete tools despite read-only use. - Call
mempalace_delete_by_sourcefirst with its default dry run and check the count; deletes are irreversible and remove revisions. - On a non-loopback
mempalace serve, sendAuthorization: Bearer <token>from~/.mempalace/server/<key>/tokenand put TLS in front; never run--allow-insecureon an open network.
Questions
Which is better for AI agents, Agent Platform Memory Bank or MemPalace?
Agent Platform Memory Bank scores 65.6 (B) on agent readiness against MemPalace's 60.7 (C), and leads in 2 of 7 scored categories. MemPalace leads on reliability, schema & documentation, payments & pricing and maintenance & community.
Do Agent Platform Memory Bank and MemPalace need an API key?
Agent Platform Memory Bank uses an OAuth sign-in. MemPalace needs no key.
Can an agent call Agent Platform Memory Bank and MemPalace without installing anything?
Agent Platform Memory Bank has a hosted endpoint at https://aiplatform.googleapis.com/v1. MemPalace runs on your own machine, with no hosted endpoint listed.
Are Agent Platform Memory Bank and MemPalace open source?
No open-source release is listed for Agent Platform Memory Bank. MemPalace is open source (MIT).
Other comparisons with Agent Platform Memory Bank or MemPalace
- Amazon Bedrock AgentCore Memory vs Agent Platform Memory Bank
- Amazon Bedrock AgentCore Memory vs MemPalace
- Basic Memory vs Agent Platform Memory Bank
- Basic Memory vs MemPalace
- claude-mem vs Agent Platform Memory Bank
- claude-mem vs MemPalace
- Cognee vs Agent Platform Memory Bank
- Cognee vs MemPalace
- EverOS vs Agent Platform Memory Bank
- EverOS vs MemPalace
- Agent Platform Memory Bank vs Graphicle
- Agent Platform Memory Bank vs Graphiti
- Agent Platform Memory Bank vs Hindsight
- Agent Platform Memory Bank vs Honcho
- Agent Platform Memory Bank vs Hy Memory
- Agent Platform Memory Bank vs LangMem
- Agent Platform Memory Bank vs LocalGhost
- Agent Platform Memory Bank vs Mem0 Platform + MCP
- Agent Platform Memory Bank vs MemMachine
- Agent Platform Memory Bank vs Memori
- Agent Platform Memory Bank vs Memory (MCP reference server)
- Agent Platform Memory Bank vs past.dev
- Agent Platform Memory Bank vs Supermemory API + MCP
- Agent Platform Memory Bank vs TencentDB Agent Memory
- Agent Platform Memory Bank vs Tokenrip
- Agent Platform Memory Bank vs Zep
- Graphiti vs MemPalace
- Hindsight vs MemPalace
- Honcho vs MemPalace
- Hy Memory vs MemPalace
- LangMem vs MemPalace
- LocalGhost vs MemPalace
- Mem0 Platform + MCP vs MemPalace
- MemMachine vs MemPalace
- Memori vs MemPalace
- Memory (MCP reference server) vs MemPalace
- MemPalace vs past.dev
- MemPalace vs Supermemory API + MCP
- MemPalace vs TencentDB Agent Memory
- MemPalace vs Tokenrip
- MemPalace vs Zep
- AI Memory vs Agent Platform Memory Bank
- AI Memory vs MemPalace
- Context Mode Engine vs Agent Platform Memory Bank
- Context Mode Engine vs MemPalace
- Graphicle vs MemPalace
Machine-readable
- This page as Markdown
/compare/google-memory-bank-vs-mempalace.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/google-memory-bank.json·/api/v1/tools/mempalace.json - From a terminal
anchor compare google-memory-bank mempalace(the CLI) - Over MCP
compare_tools {"a": "google-memory-bank", "b": "mempalace"}at/mcp, no key