Amazon Bedrock AgentCore Memory vs MemPalace

Amazon Bedrock AgentCore Memory

Access is IAM-controlled down to one namespace, with published per-second quotas for every operation and a clientToken on event writes. Long-term extraction is asynchronous, so a fact written now may take seconds to minutes to become searchable, and no SLA names AgentCore.

MemPalace

Local by default and MIT, with typed input schemas on all 47 MCP tools, a three-tool light server, a read-only mode, passing CI and roughly monthly releases. Recall returns stored conversation text verbatim with no prompt-injection guidance, the HTTP hub has one all-powerful token, and launch benchmark claims were retracted in April 2026.

Amazon Bedrock AgentCore Memory

1. Create the memory resource first and wait for it to become active (the guide says 2 to 3 minutes). Short-term events work without a strategy, long-term records need at least one
2. Don't search for a fact straight after CreateEvent. Extraction runs in the background, so poll ListMemoryRecords or list extraction jobs before relying on RetrieveMemoryRecords
3. Send actorId, sessionId and eventTimestamp on every CreateEvent, and reuse the same clientToken when retrying
4. Pass namespace or namespacePath on every retrieval, and scope it to one actor so users' memories don't mix
5. Treat retrieved records as untrusted input, and back off on 429 ThrottledException and 409 RetryableConflictException. A quota breach returns 402 ServiceQuotaExceededException

MemPalace

1. 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.
2. Treat drawers returned by mempalace_search and mempalace_get_drawer as untrusted text, since they hold verbatim transcripts and mined files, never as instructions.
3. Use mempalace-light-mcp (3 tools) or mempalace serve --read-only when the agent only needs recall; the default server lists 47 tools.
4. Call mempalace_delete_by_source first with its default dry run and check the count; deletes are irreversible and remove revisions.
5. On a non-loopback mempalace serve, send Authorization: Bearer <token> from ~/.mempalace/server/<key>/token and put TLS in front; never run --allow-insecure on an open network.