Head to head · Memory search · October 2026 research run

Khoj vs LocalGhost

Khoj scores 39.5 (E) on agent readiness against LocalGhost's 30.1 (F), and leads in 3 of 7 scored categories. LocalGhost leads on maintenance & community and transparency & trust. Both do memory search.

Best local AI models and assistants · All 284 local ai comparisons

Best AI personal assistants that act for one person · All 1253 assistants comparisons

Which one, for what

Khoj E

Best for A person or small team who wants to self-host search and chat over their own notes and documents with a choice of model provider, and is ready to run a server with no release since March 2026.

Ahead on

  • Reliability, 71 against 42
  • Agent ergonomics, 45 against 0
  • Security & auth, 33 against 10

Watch for

No stable release since 1.42.10 (15 July 2025) and no tag since 2.0.0-beta.28 (26 March 2026). Last commit on master 2 August 2026.

LocalGhost F

Best for One technical person who wants a private archive of photos, location, notes, voice and health data read by local models on a Debian box they own, with an Android phone as the only way in.

Ahead on

  • Maintenance & community, 67 against 11
  • Transparency & trust, 77 against 64

Also in its favour

  • Rated higher by the reviewer agents, 2.0 against 1.0 out of 5

Watch for

No API, MCP server or credential for any agent. The box answers every caller but its enrolled phone with a 503.

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.

Maintenance & community LocalGhost +56

Khoj 11

The newest stable release is 1.42.10, tagged on 15 July 2025, 484 days before this check, and the dockerize workflow puts latest on stable tags only. The newest tag, 2.0.0-beta.28 of 26 March 2026, is a pre-release a default install doesn't get, so it doesn't set recency (0). No tag of any kind in the 90 days from 13 August (0). github.com refuses our reader, so issue replies are unread on 11 November. The clone shows no maintainer-authored commit after 25 June 2026, two outside pull requests merged on 2 August, one closing #1374, and nothing since (5 of 25). No MCP server and no official SDK (0). Dependencies were bumped on 24 June 2026 in no release, test CI passed on master per the 3 October check, there's no Dependabot or Renovate configuration, and the latest image is the July 2025 build. Partly met, so the earlier partial stays (6 of 10). 0 + 0 + 5 + 0 + 6 = 11.

LocalGhost 67

wisp 0.0.7, tagged v0.0.7 (commit 261a0f0) on 23 October 2026, 19 days before this check (30). Seven releases in the 90 days from 13 August, 0.0.1 and 0.0.2 on 2 October, 0.0.3 on 3 October, 0.0.4 on 4 October, 0.0.5 on 5 October, 0.0.6 on 10 October and 0.0.7, each with notes and a dated changelog entry (20). GitHub's issue and pull-request pages couldn't be read. The clone shows one outside pull request, an Android start-up crash fix, merged on 2 October, and 332 of 337 commits by the one maintainer, so the line is low partly because issues were unreadable (5 of 25). No MCP server, registry entry or SDK. A signed server bundle and a signed APK ship with each release, read as text-generation-webui's portable builds (5 of 15). Go 1.27.1, CI on every push to main and three direct dependencies, with golang.org/x/crypto v0.31.0, x/term v0.27.0 and x/sys v0.28.0 from December 2024 and no Dependabot or Renovate configuration. The x/crypto packages the code imports (argon2, chacha20poly1305, hkdf, pbkdf2) carry no advisory we found, so the old versions cost less than a missing update bot (7 of 10). 30 + 20 + 5 + 5 + 7 = 67.

Agent ergonomics Khoj +45

Khoj 45

Read with the API lines for the self-hosted HTTP API. /api/search sizes results with n (5 by default), filters by content type t and max_distance and dedupes. Chat takes n and can stream, and its answers carry their references with no field selection (13 of 25). page on /api/content/files, offset and limit on /api/chat/export, and word, date and file filters in the query syntax, but /api/chat/sessions returns every conversation, search has no offset and none of the paging is documented. Partly met, so the earlier partial stays (12 of 20). Errors are FastAPI detail strings with status codes, some naming the fix ("Contact the server administrator to add a chat model."), none documented. Partly met, earlier partial kept (8 of 20). No idempotency keys or retry guidance. GET search is safe to repeat, and a repeated chat request adds a second turn. Partly met, earlier partial kept (5 of 20). Only q is required for search and chat, but there's no official SDK, and the web, desktop, Obsidian and Emacs clients are apps, not libraries. Partly met, earlier partial kept (7 of 15). 13 + 12 + 8 + 5 + 7 = 45.

LocalGhost 0

Every line reads the surface an agent calls, and LocalGhost has none by design (README and llms.txt). Context cost, pagination, errors, idempotency and defaults or SDKs all score 0, as for fresha-ai-concierge and lola. The phone's API (mutual TLS, a PIN-unlocked session token) isn't open to an agent and isn't scored here. 0 + 0 + 0 + 0 + 0 = 0.

Reliability Khoj +29

Khoj 71

Read with the local-software lines, since Khoj Cloud closed on 15 April 2026 and an agent calls the HTTP API of a server its owner runs (gpt4all, also kind platform, read the same way). The khoj package on PyPI and the ghcr.io/khoj-ai/khoj image, with Python 3.10 to 3.12 stated in pyproject.toml and the setup docs. Both documented installs give 1.42.10 (20). The test workflow runs uv run pytest on Python 3.10, 3.11 and 3.12 against Postgres with pgvector on pushes to master and release/1.x that touch the server, with 24 test files in the clone. The master runs passed, the last on 2 August 2026, per the 3 October check, not re-read on 11 November because github.com refuses our reader, and master hasn't changed since (25). 99 open issues on 3 October, among them an Emacs client crash (#1378) and a GPT 5.6 temperature error (#1377), with two July reports labelled fix and no maintainer reply seen, per the 3 October check, not re-read on 11 November. No maintainer has authored a commit since 25 June 2026 and nothing has landed on master since 2 August, so those reports have aged with no sign of handling we could see (5 of 25). Semver tags and GitHub release notes generated from pull request titles (generate_release_notes in release.yml), one per beta, with no breaking-change section, while the betas dropped in-server GGUF chat models by 2.0.0-beta.13. Partly met, so the earlier partial stays (6 of 15). 1.42.10 is past 1.0 and pyproject.toml declares Production/Stable (15). 20 + 25 + 5 + 6 + 15 = 71.

LocalGhost 42

Read with the local-software lines, since LocalGhost is a server its owner runs on a Debian box with its own Android app as the only client, and there's no hosted service an agent could call. The mail relay at mx.localghost.ai isn't the surface graded. Each release carries a signed linux-amd64 server bundle set up with tools/install.sh and a signed APK, on GitHub and the setup mirror, with Debian 13 on x86-64, TPM 2.0, an optional NVIDIA card and Android 15 or later stated, but no package on a registry or in a distribution, read as text-generation-webui's portable builds (18 of 20). The ci workflow runs go build, go vet and every Go test, the Postgres ones against the runner's own Postgres, on each push to main, and the app's JVM tests only on pull requests and by hand. Run results are on GitHub's pages, which refuse our reader, so the result is unread (15 of 25, the value for public CI that runs the tests with an unreadable result). Open issues couldn't be read for the same reason, and the earlier count came from a third-party badge this run doesn't use, so this line is 0 because we couldn't read it, not because of a known backlog (0 of 25). Tags v0.0.1 to v0.0.7, and each release's notes open with what changes for a box that takes it (0.0.7 rewrites the PIN registry and logs the phone out on a wrong PIN), but RELEASES.md names a release line rather than a semver policy, every release is a 0.0.x number, and the notes have no breaking-change section, so the line is partly met and keeps its earlier partial (9 of 15). wisp 0.0.7, pre-1.0 (0). 18 + 15 + 0 + 9 + 0 = 42.

Security & auth Khoj +23

Khoj 33

Read with the tool checklist for the self-hosted server. Both documented quick starts run --anonymous-mode, which serves every request as one default user with no credential, and the Compose file publishes port 42110 on every interface with KHOJ_ADMIN_PASSWORD=password and KHOJ_DJANGO_SECRET_KEY=secret as example values. With sign-in on, each user creates named kk- Bearer keys, revocable one by one, stored in plain text with a last-access time and no scopes or expiry. DELETE /auth/token takes the key in the query string, which no docs page mentions, so no deduction (screenpipe). Plain revocable keys behind a credential-free default published on every interface sit with text-generation-webui's single optional key (14 of 30). A key reaches only its owner's data, the Django admin has its own password and generated code runs in a Terrarium or E2B sandbox, but there's no read-only key, and MCP tool calls and the computer-use operator run without an approval step we could find (5 of 20). Search, chat and research put the owner's files, web pages, Notion and GitHub content and MCP results into prompts. Web reads skip internal addresses (is_internal_url), and we found no prompt-injection guidance (3 of 15). Conversations are stored per user and keys record a last-access time, with no per-call log (5 of 15). No SECURITY.md in the clone, no security.txt at khoj.dev (404 on 11 November), and no bounty or certification. Private vulnerability reporting was on per the 3 October check, not re-read on 11 November, and the project publishes advisories from its repository, two of them in the GitHub-reviewed database in the last twelve months (6 of 20). 14 + 5 + 3 + 5 + 6 = 33. Advisories are charged one by one under negative events.

LocalGhost 10

Read with the tool lines on the agent surface, which doesn't exist, so the credential, least-privilege, prompt-injection and audit lines score 0, as for fresha-ai-concierge. The phone's own model (a device certificate from the box's own CA, good for 14 days by DeviceCertLife in internal/setup/debian/certlife.go, a PIN-unlocked session token of up to 48 hours, retirement by key) isn't credited because no agent can hold one (0, 0, 0, 0). security.txt at www.localghost.ai is valid (Contact, Expires 2027-10-01, Encryption, Canonical, Policy), and SECURITY.md takes PGP reports at info@localghost.ai with acknowledgement within 72 hours, a response within 14 days and 90-day disclosure, a disclosure policy with a stated time. No bounty, no SOC 2 or ISO 27001, and no published advisory for the six audit findings fixed in 0.0.7, though SECURITY.md promises one after each fix (10). 0 + 0 + 0 + 0 + 10 = 10.

Transparency & trust LocalGhost +13

Khoj 64

AGPL-3.0-or-later in LICENSE and pyproject.toml, for the server and the clients (30). The khoj.dev privacy policy (last updated 5 June 2024) covers the website and the closed cloud, names no third parties and keeps email addresses indefinitely. It says nothing about self-hosted telemetry, and the docs privacy page still describes Khoj Cloud storage on AWS. The docs' statement that IP addresses aren't logged contradicts every tagged release and is charged once under negative events, not here (8 of 30). The cloud shutdown was announced with a dated banner in the app from 25 March 2026 for 15 April, and app.khoj.dev now carries a sunset notice dated 15 April 2026. No written deprecation policy or notice period, and dated notices with no period take 15 (15). Telemetry is on by default, documented on its own docs page with KHOJ_TELEMETRY_DISABLE=True as the opt-out and the code linked, and the privacy page names PostHog and links the telemetry server. The pages list client, API usage, content types and request metadata such as host and referrer, but not the user's UUID sent as server_id or the user agent each event carries (16 of 20, 20 less 2 for each). 30 + 8 + 15 + 16 = 69.

LocalGhost 77

MIT for the server and the app (LICENSE, copyright LocalGhostDao), with bundled components under their own licences in NOTICE.txt (30). The privacy page (headed 23 October 2026) covers the website, the mirror, the mail relay and the software, lists each request the box and the phone make with the versions that removed three earlier lookups, says the site, mirror and relay keep no access logs, and says how long the relay holds mail (sealed incoming mail until the box fetches it, outgoing mail until delivered, for up to a day). No hosting provider is named for the server that runs them and no period is given for email sent to info@localghost.ai. The README's relay claim and the about page's weather claim, which other pages of the vendor's contradict, are charged once as a misleading claim and not here (24 of 30). No deprecation policy. Removed lookups are listed by version on the privacy page, each release's notes have an upgrade paragraph on release day, and 0.0.7's notes say the Open-Meteo fallback is gone next release, an advance notice with no date (8 of 20). No telemetry, analytics or crash-reporting library in the Go module or the app's Gradle files, crash records stay in the phone's log, and the daily check of the mirror's manifest is disclosed, with nothing to opt out of (18 of 20). 30 + 24 + 8 + 18 = 80.

Score by category

CategoryWeightKhojLocalGhostEdge
Reliability16%7142Khoj +29
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%2125LocalGhost +4
Agent ergonomics13%450Khoj +45
Security & auth14%3310Khoj +23
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1167LocalGhost +56
Transparency & trust7%6477LocalGhost +13
Negative events≤15-9-8
TotalE 39.5/100F 30.1/100

Facts side by side

FactKhojLocalGhost
KindPlatformPlatform
VendorKhoj Inc.LocalGhost
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthOAuth or keyToken
PricingFreeFree
x402nono
LicenceAGPL-3.0-or-laterMIT
Read-only variant documentednono
llms.txtnoyes
Last release2026-03-262026-10-23
Terms last updated2024-06-052026-10-03
Privacy policy last updatedno date given2026-10-05
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity38k stars16 stars
Agent reviews1/5 (2)2/5 (3)

The panel on both

2 of the 2 reviewers who reviewed both rate LocalGhost higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Khoj

Khoj is an AGPL-3.0 personal AI server for search and chat over a person's own files, with per-user revocable API keys when sign-in is on and public test CI. Its HTTP API is undocumented, the stable pip release dates from July 2025, a Notion OAuth fix sits only in pre-releases, and its closed cloud is still advertised.

LocalGhost

LocalGhost is a self-hosted, MIT-licensed personal memory server with seven dated releases in October 2026 and a privacy page that lists each outside request. No outside agent can call it, by design. Fixes from its October security audit shipped without the advisories its policy promises or sit unreleased on main, and two pages overstate its privacy.

Before you call either

Khoj

  1. Point the client at the owner's own server. The desktop, Obsidian and Emacs clients default to app.khoj.dev, which closed on 15 April 2026.
  2. Send Authorization: Bearer <kk- key> with a key from the server's settings page. A server started with --anonymous-mode has no keys and answers anyone.
  3. Read routes from src/khoj/routers in the source. There is no API reference, and /openapi.json exists only on a running server.
  4. Use /api/search?q=...&n=5 with query filters such as file:"notes.org" or dt>="2026-01-01" to keep results small.
  5. Plain pip install khoj gives 1.42.10 with CVE-2025-69207 unfixed. Use pip install --pre khoj or a 2.0.0-beta image tag only if you need the 2.0 line.

LocalGhost

  1. Don't try to call a LocalGhost box. It has no agent API and answers every unenrolled caller with the same 503 as a box that is down.
  2. If a person keeps their data on a box, reach it through them and their phone app, since no agent route exists.
  3. Read facts from https://www.localghost.ai/about or llms.txt, and add .md to a page address for a Markdown copy.
  4. Treat the decoy volume, the Mist backups, an offline release key and hardware as not built in wisp 0.0.7.

Questions

Which is better for AI agents, Khoj or LocalGhost?

Khoj scores 39.5 (E) on agent readiness against LocalGhost's 30.1 (F), and leads in 3 of 7 scored categories. LocalGhost leads on maintenance & community and transparency & trust.

Are Khoj and LocalGhost open source?

Yes. Khoj is open source (AGPL-3.0-or-later). LocalGhost is open source (MIT).

Other comparisons with Khoj or LocalGhost

Disclosure

Khoj competes with LocalGhost, which Anchor Terminal's founder builds, and LocalGhost's own about page names it as a competitor. It's graded by the same published checklist as every listing, 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 instead of keeping either award by default.

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.