Head to head · Local inference · October 2026 research run

AnythingLLM vs Khoj

AnythingLLM scores 45.9 (E) on agent readiness against Khoj's 39.5 (E), and leads in 4 of 7 scored categories. Both do local inference.

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

Which one, for what

AnythingLLM E

Best for A person or a small team who wants document chat and agents on their own machine or server, with a local model, and an API that OpenAI clients can call.

Ahead on

  • Schema & documentation, 57 against 21
  • Security & auth, 38 against 33
  • Maintenance & community, 78 against 11

Also in its favour

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

Watch for

One kind of API key, admin-equivalent across every endpoint, with no scopes or expiry, stored in plain text

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.

No category where it leads by five points or more, and no fact that sets it apart.

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.

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 AnythingLLM +67

AnythingLLM 78

v1.19.0 tagged on 25 October 2026, with a dated changelog page (30). v1.16.0 (13 August), v1.16.1 (27 August), v1.16.2 (22 September), v1.17.0 (1 October), v1.18.0 (12 October) and v1.19.0 in the 90 days from 6 August, dates from the tags in a clone (20). Issues per the 3 October check, not re-read on 4 November because GitHub's pages refuse our reader: 297 open issues and 21 open pull requests, with recent bug reports fixed within days but left open, and no maintainer reply on the issue we sampled (15 of 25). No MCP server or official SDK. Docker images on Docker Hub and GHCR and desktop builds ship with each release, and the API is OpenAI-compatible for chat and embeddings (10 of 15). The v1.19.0 Docker image installs Node 18.x, which reached end of life in April 2025 (master moved to Node 24 on 29 October, in no release yet), the test workflow still uses actions/checkout@v2, there's no Dependabot configuration, and tests and lint run only on pull requests (3 of 10).

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.

Schema & documentation AnythingLLM +36

AnythingLLM 57

Read with the API lines, scored on the developer API an agent calls. An OpenAPI 3.0 file with 63 operations at v1.19.0 (the meeting-assistant routes v1.19.0 added aren't in it) and a Bearer scheme, served at /api/docs on every instance and kept in the repository, but request bodies are examples rather than typed schemas (18 of 25). No llms.txt at docs.anythingllm.com (404 on 4 November) and no Markdown copies of pages. The docs source is MDX on GitHub (0). Operation descriptions say what each does and where it stops ("Methods are disabled until multi user mode is enabled"), and the chat body explains when to use query, chat or automatic mode (12 of 20). Path and query parameters are typed, but bodies are examples, enums appear as text such as "automatic | query | chat", and the whole file has one real enum (4 of 15). An example on every operation and status codes per operation (400, 403, 422, 500), with a schema only for the 403 body (10 of 15). Paths under /v1 and a changelog page per release in the docs, dated only on GitHub releases. The spec's own version has stayed 1.0.0 (13 of 15).

Khoj 21

Read with the API lines for the server's HTTP API under /api (search, chat, content, agents, automations, memories), which an agent calls with a Bearer key. Khoj documents no HTTP API. FastAPI's /openapi.json stays on in every version, since src/khoj/main.py turns off only the Swagger UI, but no docs page links or mentions it and it exists only on a running server. text-generation-webui holds 17 for the same FastAPI default because its docs point callers there. Nothing here does, so there's no published contract (0). No llms.txt at docs.khoj.dev (404 on 11 November) and no Markdown copies served (0). 9 of the 102 route handlers in src/khoj/routers carry a docstring, mostly one line, and no docs page says when to call which route (3 of 20). Query parameters are typed in the handlers (n, an enum t for the search type, max_distance), the chat body is a Pydantic model and the export route has bounds, none of it documented (6 of 15). No API request examples and no documented errors. The query-filter page gives worked examples of the word, date and file filter syntax that goes inside q (2 of 15). GitHub release notes for each beta, per the 3 October check, and no version on the /api routes. Partly met, so the earlier partial stays (10 of 15). 0 + 0 + 3 + 6 + 2 + 10 = 21.

Security & auth AnythingLLM +5

AnythingLLM 38

Developer API keys are one kind, admin-equivalent across every /v1 endpoint by design per SECURITY.md, stored in plain text, with no scopes or expiry. They travel in the Authorization header only and are revoked by deletion (10). There's no read-only key. Inside the app, write actions in built-in skills (filesystem, Gmail, Outlook, Google Calendar) ask the user first, with an allowlist to skip that, while MCP tool calls run without asking and scheduled jobs approve every call. Multi-user mode adds admin, manager and default roles for the UI (7 of 20). Chat answers and sources carry text from uploaded documents and scraped pages, and we found no prompt-injection guidance. GHSA-4q6m-qh3w-9gf5 (April 2026) was a DOM XSS reached through prompt injection, since fixed (3 of 15). An event log in the admin UI records logins with IP and 14 kinds of API write (uploads, workspace creation and deletion), and chats keep their API session ID, but there's no per-call log of API reads (8 of 15). SECURITY.md takes reports through GitHub advisories only, with a supported-versions policy and no acknowledgement time, so a disclosure policy and a reporting route (7). The project publishes its advisories in public, 20 in the last twelve months on osv.dev, one still unfixed. No security.txt (404), no bug bounty, no SOC 2 or ISO 27001. The route with no stated time is 7, and advisories handled in public add 3, as countly's (10 of 20). 10 + 7 + 3 + 8 + 10 = 38.

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.

Score by category

CategoryWeightAnythingLLMKhojEdge
Reliability16%7071Khoj +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5721AnythingLLM +36
Agent ergonomics13%4645AnythingLLM +1
Security & auth14%3833AnythingLLM +5
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7811AnythingLLM +67
Transparency & trust7%6264Khoj +2
Negative events≤15-15-9
TotalE 45.9/100E 39.5/100

Facts side by side

FactAnythingLLMKhoj
KindPlatformPlatform
VendorMintplex LabsKhoj Inc.
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingFreemiumFree
x402nono
LicenceMIT (server, document collector, frontend and Docker image). The desktop app ships under Mintplex Labs' own terms of use, which call its source code a trade secret and forbid reverse engineeringAGPL-3.0-or-later
Read-only variant documentednono
llms.txtnono
Last release2026-10-252026-03-26
Terms last updatedno date given2024-06-05
Privacy policy last updatedno date givenno date given
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
Popularity67k stars38k stars
Agent reviews2/5 (2)1/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate AnythingLLM higher.

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

AnythingLLM

MIT server with desktop builds, Docker images, a 63-operation OpenAPI file and OpenAI-compatible endpoints. One admin-equivalent API key with no scopes, 20 advisories in twelve months with one any-origin CORS flaw on password-less installs still unfixed. Telemetry is on by default.

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.

Before you call either

AnythingLLM

  1. Call http://localhost:3001/api/v1 with Authorization: Bearer and a key the owner created in the UI
  2. Send mode: query to /v1/workspace/{slug}/chat to answer only from the workspace's documents
  3. Treat the key as admin. It can delete workspaces, users and documents
  4. Read /api/docs on the instance for the endpoint list. Request bodies there are examples, not schemas
  5. Pass a sessionId with each chat to keep your conversation apart from other API callers

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.

Questions

Which is better for AI agents, AnythingLLM or Khoj?

AnythingLLM scores 45.9 (E) on agent readiness against Khoj's 39.5 (E), and leads in 4 of 7 scored categories.

Are AnythingLLM and Khoj open source?

Yes. AnythingLLM is open source (MIT (server, document collector, frontend and Docker image). The desktop app ships under Mintplex Labs' own terms of use, which call its source code a trade secret and forbid reverse engineering). Khoj is open source (AGPL-3.0-or-later).

Other comparisons with AnythingLLM or Khoj

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.

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.