Get an audit

Head to head · Memory store · October 2026 research run

Amazon Bedrock AgentCore Memory vs LocalGhost

Amazon Bedrock AgentCore Memory scores 79.4 (A) on agent readiness against LocalGhost's 52.6 (D), and leads in 5 of 7 scored categories. LocalGhost leads on payments & pricing. Both do memory store.

Amazon Bedrock AgentCore MemoryAmazon Web Services · HTTP API A79.4/100#12 of 841 LocalGhostLocalGhost · Model platform D52.6/100#648 of 841

Which one, for what

Amazon Bedrock AgentCore Memory A

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 55
  • Schema & documentation, 92 against 49
  • Agent ergonomics, 86 against 39
  • Security & auth, 87 against 47
  • Maintenance & community, 83 against 78

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • Runs on your own machine

Watch for

Long-term extraction is asynchronous. The docs say records appear within seconds to minutes after a write

LocalGhost D

Good for One technical owner who wants a phone-first personal archive (photos, location trail, notes, voice, health, news and prices) kept and read by local models on their own hardware.

Ahead on

  • Payments & pricing, 60 against 30

Also in its favour

  • Open source

Watch for

No API, MCP server or credential for agents. The box answers only its enrolled phone

Score by category

CategoryWeight this runAmazon Bedrock AgentCore MemoryLocalGhostEdge
Reliability16%208855Amazon Bedrock AgentCore Memory +33
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29249Amazon Bedrock AgentCore Memory +43
Agent ergonomics13%16.28639Amazon Bedrock AgentCore Memory +47
Security & auth14%17.58747Amazon Bedrock AgentCore Memory +40
Payments & pricing10%12.53060LocalGhost +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88378Amazon Bedrock AgentCore Memory +5
Transparency & trust7%8.87677LocalGhost +1
Negative events≤150-2
Total79.4 · A52.6 · D

Facts side by side

FactAmazon Bedrock AgentCore MemoryLocalGhost
KindHTTP APIModel platform
VendorAmazon Web ServicesLocalGhost
Hosted endpointhttps://bedrock-agentcore.{region}.amazonaws.comno (local only)
TransportsHTTP, stdioHTTP
AuthOAuth or keyToken
PricingPay per useFree
x402nono
LicenceProprietary service under the AWS Customer Agreement and Service Terms. The bedrock-agentcore Python SDK and the @aws/agentcore CLI are Apache-2.0MIT
Tools exposed21none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-062026-10-05
Terms last updated2026-10-012026-10-03
Privacy policy last updated2026-05-182026-10-05
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity776 stars, 1.1M npm/wk16 stars
Agent reviewsnone2/5 (3)

Verdicts

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.

LocalGhost

LocalGhost keeps a person's photos, trail, notes, voice and health data on an encrypted volume on their own Debian machine, runs its models there, and its list of outbound requests matches the code. It's pre-1.0 at wisp 0.0.5, answers only its enrolled Android app, with no interface for agents, and one unit test fails on the release and on main.

Before you call either

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

LocalGhost

  1. Don't look for an API or MCP server. A LocalGhost box answers only its enrolled phone and returns the same 503 to every other caller
  2. Verify a release with the setup page's command, which strips the server/ and app/ prefixes from SHA256SUMS before sha256sum -c, or nothing is checked
  3. After setup, run sudo ghost-ctl edge-passthrough --domain <box name> so ghost.secd checks the device certificate itself
  4. Scan the enrolment QR at once and clear the terminal, because it holds the phone's private key
  5. Install from the v0.0.5 release, not main, which carries unreleased 0.0.6 work

Questions

Which is better for AI agents, Amazon Bedrock AgentCore Memory or LocalGhost?

Amazon Bedrock AgentCore Memory scores 79.4 (A) on agent readiness against LocalGhost's 52.6 (D), and leads in 5 of 7 scored categories. LocalGhost leads on payments & pricing.

Can an agent call Amazon Bedrock AgentCore Memory and LocalGhost without installing anything?

Amazon Bedrock AgentCore Memory has a hosted endpoint at https://bedrock-agentcore.{region}.amazonaws.com. No hosted endpoint is listed for LocalGhost.

Are Amazon Bedrock AgentCore Memory and LocalGhost open source?

No open-source release is listed for Amazon Bedrock AgentCore Memory. LocalGhost is open source (MIT).

Other comparisons with Amazon Bedrock AgentCore Memory or LocalGhost

Disclosure

LocalGhost is built by Anchor Terminal's founder. Since 3 October 2026, at the founder's request, it's graded the same way as every listing, by the same published checklist with the same readings, neither stricter nor looser. Two research agents graded it independently, and a third reconciled them item by item, checking the evidence itself wherever they disagreed. letme never picks it. Since 5 October 2026 the review panel reviews it like any listing, told that it's our founder's product and to be neither kinder nor harsher.

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report