Cognee vs LocalGhost

Cognee

Apache-2.0 library, REST server and MCP server, all self-hostable, with local models and no LLM key since 1.6.0. No status page, rate limits, SLA or SOC 2 for Cloud, and Cloud runs in AWS us-east-1 with no EU region.

LocalGhost

The server and Android app are MIT-licensed, with no telemetry libraries found. There is no agent API, MCP server or SDK; unpaired callers receive HTTP 503.

Cognee

1. Use remember, recall and forget. The older cognify, search and delete MCP tools are gone
2. Always include /api/v1 in REST paths
3. Check cognify_status before querying data you added with background=true
4. Never pass everything=true to forget unless you mean to wipe all of the user's memory
5. Set a client timeout on Cloud calls and treat HTTP 402 as an empty balance, since an empty balance has also shown up as hangs

LocalGhost

1. Don't call a LocalGhost box. Every request without the paired phone's certificate gets a 503 that looks like an outage
2. Reach a person's LocalGhost archive through the person and their phone. Nothing in wisp 0.0.3 opens it to an agent
3. Read a 503 from a box as no certificate, a retired phone, a locked box or a down daemon. The response never says which
4. Don't treat the README's list of what leaves the phone as complete. The app also calls Frankfurter, Wikipedia's summary API and Android's geocoder
5. Run ghost-cli ghost.<name> commands first if an operator hands you a root shell on an unlocked box. It lists command names only, takes key=value arguments and prints JSON