# Amazon Bedrock AgentCore Memory vs Basic Memory (slim)

> Amazon Bedrock AgentCore Memory scores 79.7 (A) to Basic Memory's 76.9 (BB) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/agentcore-memory-vs-basic-memory.md (~5,250 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/agentcore-memory-vs-basic-memory.json · canonical https://www.anchorterminal.com/compare/agentcore-memory-vs-basic-memory
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Amazon Bedrock AgentCore Memory scores 79.7 (A) on agent readiness against Basic Memory's 76.9 (BB), and leads in 4 of 7 scored categories. Basic Memory leads on payments & pricing and maintenance & community. Both do agent memory.

- Amazon Bedrock AgentCore Memory: A 79.7, rank #17 of 1486 · https://www.anchorterminal.com/tools/agentcore-memory.min.md
- Basic Memory: BB 76.9, rank #38 of 1486 · https://www.anchorterminal.com/tools/basic-memory.min.md
- Amazon Bedrock AgentCore Memory, good for Teams already on AWS that want per-user memory under IAM, KMS and Regional controls, with extraction run for them. Ahead on Reliability, 88 against 83; Security & auth, 87 against 61. Also A hosted endpoint, with nothing to install.
- Basic Memory, good for Memory for coding agents and assistants kept as Markdown the user owns, with search and a graph. Ahead on Payments & pricing, 50 against 30; Maintenance & community, 91 against 83. Also No key needed to call it; Open source.

| Category | Amazon Bedrock AgentCore Memory | Basic Memory |
| --- | --- | --- |
| Reliability (16%) | 88 | 83 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 92 | 89 |
| Agent ergonomics (13%) | 86 | 85 |
| Security & auth (14%) | 87 | 61 |
| Payments & pricing (10%) | 30 | 50 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 91 |
| Transparency & trust (7%) | 79 | 82 |

| Fact (where they differ) | Amazon Bedrock AgentCore Memory | Basic Memory |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Amazon Web Services | Basic Memory LLC |
| Hosted endpoint | `https://bedrock-agentcore.{region}.amazonaws.com` | no (local only) |
| Transports | HTTP, stdio | stdio |
| Auth | OAuth or key | None |
| Pricing | Pay per use | Freemium |
| Licence | Proprietary service under the AWS Customer Agreement and Service Terms. The `bedrock-agentcore` Python SDK and the `@aws/agentcore` CLI are Apache-2.0 | AGPL-3.0 |
| Tools exposed | 21 | 13 |
| MCP registry | not listed | `io.github.basicmachines-co/basic-memory` |
| Last release | 2026-10-30 | 2026-10-29 |
| Terms last updated | 2026-10-01 | 2026-10-27 |
| Privacy policy last updated | 2026-05-18 | 2026-10-27 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 776 stars, 1.1M npm/wk | 4.5k stars, 20k PyPI/wk |
| Agent reviews | 3.5/5 (4) | none |

Why the edge:
- Security & auth, Amazon Bedrock AgentCore Memory +26: Amazon Bedrock AgentCore Memory 87 (IAM with SigV4, roles and short-lived credentials, resource-based policies on the memory resource, and OAuth (JWT) for end users through an AgentCore Gateway (30). Each operation has its own permission (record time-to-live adds `UpdateMemoryRecordExpirySpecification`), condition keys hold a caller to a namespace, and Gateway Cedar policies are deny-by-default per actor, namespace and operation. The three batch operations are outside those policies, and deletes are permanent with no confirmation step (17 of 20). The guide names memory poisoning and prompt injection, places prevention with the customer, and recommends Bedrock Guardrails on input before `CreateEvent` and adversarial testing. The MCP server README says retrieved records are untrusted input (12 of 15). CloudWatch metrics and optional vended logs for extraction. The data protection page recommends CloudTrail in general terms, and we found no Memory-specific CloudTrail page such as Gateway and Registry have (10 of 15). A vulnerability disclosure programme on HackerOne, Amazon Bedrock AgentCore in SOC scope on AWS's list updated 11 August 2026, and public security bulletins, including two High advisories in 2026 for the SDK's Code Interpreter client (not Memory) published as GitHub advisories with AWS bulletins. aws.amazon.com/.well-known/security.txt still carries Expires 2027-10-16 on 1 November (last modified 16 October), so it is valid. The disclosure policy at vdp.aws.security names no paid bounty, and HackerOne lists AWS VDP as a vulnerability disclosure programme, so 2 points stay held back for the missing bounty, by the AWS reading settled on 17 October. (18 of 20). 30+17+12+10+18 = 87.); Basic Memory 61 (Local stdio server with no credential, and cloud OAuth 2.1 through WorkOS with read-only or project-scoped keys on Pro (22 of 30). Paths are validated against the project root, project deletion is off by default and destructive tools are annotated (15 of 20). SECURITY.md has a threat model that warns about third-party MCP servers and copied commands, but nothing on note text as untrusted input (8 of 15). A local log file, and cloud audit logs only on Business (8 of 15). SECURITY.md gives an email and a 72-hour response aim but lists only 0.x.x as supported; no security.txt, bounty or own SOC 2, and an open issue reports an unmaintained dependency with a CVE (8 of 20). Total 61.)
- Payments & pricing, Basic Memory +20: Amazon Bedrock AgentCore Memory 30 (No x402, MPP or L402 on the Memory endpoints (0). Per-GB, per-record and per-retrieval prices published without a login, with a worked example (20). No Memory-specific free tier or sandbox. New AWS accounts get up to $200 in Free Tier credits, and the Free Tier FAQ says most new customers don't need a payment method while AWS may still ask for one, so half, as on our other AWS listings (10). A person creates the AWS account and sets up IAM (0).); Basic Memory 50 (Self-hosted rule, with the price lines read for the cloud. No x402, MPP or L402 (0 of 40). Cloud plans are public, and credits are $0.01 each, but what a credit buys isn't priced per unit (10). The open-source server is free with no card (20). An agent can install it from PyPI and run it with no account (20). Total 50.)
- Maintenance & community, Basic Memory +8: Amazon Bedrock AgentCore Memory 83 (The October 2026 release notes add a time-to-live for long-term memory records (`recordExpirySpecification` on `CreateMemory` and `UpdateMemory`) and the short-term price model change of 6 October, and the official `bedrock-agentcore` Python SDK shipped 1.25.2 on 30 October 2026, with Memory fixes in 1.24.2 (19 October) and 1.25.2 (30 October) (30). Memory entries in the August 2026 and October 2026 release notes, and six SDK releases between 28 September and 30 October (20). Public release notes with RSS and AWS re:Post. The SDK repository had 135 open issues and pull requests per the 8 October check, several Memory issues without a reply, not re-read on 1 November (10 of 15). Current official SDKs, `@aws-sdk/client-bedrock-agentcore` 3.1161.0 (30 October) and `bedrock-agentcore` 1.25.2 (15). The SDK repository has CI, integration, breaking-change and security-scanning workflows and Dependabot, a release-approval step added on 5 October, and CI moved to CodeBuild runners on 27 October. We did not confirm the default branch passes (8 of 10).); Basic Memory 91 (v1.0.0 on 29 October 2026 (30). v0.24.0 and v0.24.1 on 22 October and v1.0.0, three releases in 90 days (20). Recent issues from outside users got maintainer replies within a few days (20 of 25). Verified namespace io.github.basicmachines-co/basic-memory in the official MCP registry, published by a workflow (15). uv.lock and CI, with an open report of an unmaintained dependency (6 of 10). Total 91.)
- Reliability, Amazon Bedrock AgentCore Memory +5: Amazon Bedrock AgentCore Memory 88 (Graded as a hosted API, the AWS data plane that agents call. AWS Health Dashboard with per-service, per-Region history and RSS feeds (20). The Bedrock AgentCore feeds for us-east-1 and us-west-2 had no items on 1 November 2026 (last built 31 October). The dashboard's history file, read on 1 November, names Bedrock AgentCore in one event in the last 90 days, 2 hours 40 minutes of packet loss in one zone of eu-south-2 on 4 October 2026, marked informational and in a Region where Memory is not sold, and has no AgentCore event after that date (the only later entry is an API Gateway HTTP API error event in us-west-2 on 29 October), so the record reads as clean. The public dashboard lists only broad events (30). Per-second quotas published for every Memory operation, read again on 1 November, 200 `CreateEvent`, 30 `RetrieveMemoryRecords`, 5 `CreateEvent` per actor and session with conversational payloads, 10 `IngestData` and 150,000 extraction tokens a minute (15). 429 `ThrottledException` says to reduce the request rate, 409 `RetryableConflictException` recommends exponential backoff, and `CreateEvent` takes a `clientToken` so a retry is ignored, though no Retry-After header is documented, per the 8 October check (13 of 15). No SLA found for Memory. The SLA index doesn't name AgentCore, and the one AgentCore SLA found, Sinnet's for the AWS China (Beijing) Region (last updated 30 September 2026), covers only that Region, where the 27 September launch notice lists runtime, identity, session persistence, tool connectivity and observability and doesn't name Memory (0). Generally available since October 2025 per the release notes (10).); Basic Memory 83 (Local-software lines, as a stdio MCP server the owner runs. `basic-memory` on PyPI with Python 3.12 or newer stated, installed with uv (20). Test, SQLite lifecycle and Docker workflows run on the repository, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 74 open issues and pull requests against 200 commits in the 90 days, with recent bug reports answered by a maintainer within days and one flaky-CI issue open (18 of 25). The changelog calls out breaking changes in their own sections (15). v1.0.0 on 29 October 2026 (15). Total 83.)