Head to head · Local inference · October 2026 research run

Jan vs Khoj

Jan scores 60.9 (C) on agent readiness against Khoj's 39.5 (E), and leads in 5 of 7 scored categories. Khoj leads on reliability. Both do local inference.

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

Which one, for what

Jan C

Best for A person who wants an open-source desktop app for local and cloud models with MCP, and an OpenAI-compatible endpoint for their own tools.

Ahead on

  • Schema & documentation, 56 against 21
  • Security & auth, 46 against 33
  • Maintenance & community, 77 against 11
  • Transparency & trust, 70 against 64

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 2.0 against 1.0 out of 5
  • No incidents deducted, where Khoj loses 9 points for them

Watch for

0.8.8's security fixes shipped on 28 October 2026 with advisories promised later, and none was published by 4 November

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 61

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 Jan +66

Jan 77

0.8.8, tagged on 27 October 2026 and dated 28 October in the changelog, 8 days before this check (30). Four releases since 6 August, 0.8.5 on 8 October, 0.8.6 on 9 October, 0.8.7 on 19 October and 0.8.8 on 27 October, each with a dated changelog entry (20). New issues get labels and milestones, per the 3 October check, and reply times couldn't be read (15). No MCP registry entry read and no SDK in the stable release. The 0.8.5 notes say agent work stays in the nightly channel (3). A Dependabot config, CI on pushes to main and a pinned Rust toolchain (1.98.0) (9). 30 + 20 + 15 + 3 + 9 = 77.

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 Jan +35

Jan 56

Read with the API lines. The server serves an OpenAPI 3.0 file at /openapi.json with a Swagger page at /, covering 4 paths (models, chat completions, messages, orchestrations) with typed schemas and a bearer scheme, but only 200 responses, and /completions, /embeddings and /messages/count_tokens aren't in it. The spec on the docs site is the retired Cortex API (12). No llms.txt at jan.ai or www.jan.ai (404 on 3 October), and no Markdown copies of pages found (0). The API server page explains each setting and when to change it (127.0.0.1 or 0.0.0.0, the key, CORS for browser clients, server-side tool execution) (12). Request schemas in the spec mark required fields and use enums, while the extra llama.cpp parameters and errors are described only in prose (10). One curl example, and a troubleshooting list for connection refused, 401, 404 and CORS errors. Error bodies are plain text (9). A /v1 prefix, semver releases and a dated changelog with GitHub release notes (13). No llms.txt at www.jan.ai on 4 November (404). 12 + 0 + 12 + 10 + 9 + 13 = 56.

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 Jan +13

Jan 46

Read with the tool checklist. One optional key typed into Settings, empty by default, accepted as Authorization: Bearer or X-Api-Key, with no scopes, names or keys per client. jan serve --api-key defaults to empty too (10). The app asks before each MCP tool call by default, with an allow-all switch, and server-side tool execution through the API is off by default for every endpoint. The key can't be limited. The 0.0.0.0 bind that dropped Trusted Hosts in 0.8.4 was fixed in 0.8.5 on 8 October 2026, and 0.8.8 checks the Origin of browser requests (11). The docs advise a key when binding to 0.0.0.0 but say nothing on injected instructions in tool results. 0.8.5 caps tool-result size, and 0.8.8 opens links from replies and tool results in the system browser (5). Verbose server logs are on by default with a Server Logs view (10). SECURITY.md, added on 26 October 2026, takes reports through GitHub Security Advisories or security@jan.ai, promises acknowledgement within 3 business days and credits researchers. No bounty and no security.txt at jan.ai. CVE-2026-66005, published by VulnCheck, records the 0.0.0.0 flaw, and the 0.8.8 notes say advisories for its fixes will follow (10). 10 + 11 + 5 + 10 + 10 = 46.

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.

Reliability Khoj +10

Jan 61

Read with the local-software lines, since Jan runs on the owner's machine with no hosted service behind its API. Installers for macOS 13.6 or later, Windows 10 or later and Linux (.deb and AppImage), plus Flathub and the Microsoft Store, with requirements in the README and the install guides (20). The Linter & Test workflow runs make test-ts and make test-ci-rust on pushes to main that touch the app's code. Its run results are on GitHub's pages, which our reader can't open, so the result is unread and the line takes 15 of 25. 409 open issues and 133 open pull requests on 3 October, with labels, milestones and a stale bot that closes issues after 180 days without activity, not re-read on 4 November (15). Semver tags and a dated changelog per release with Migration notes, but 0.8.5 renamed the desktop executable and stopped bundling the jan CLI in a patch release (11, held as a partial). 0.8.8, pre-1.0 (0). 20 + 15 + 15 + 11 + 0 = 61.

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.

Transparency & trust Jan +6

Jan 70

Apache-2.0 for the app, the server and the CLI (30). The privacy policy (Menlo Research Pte Ltd, last updated 16 January 2025) says analytics are opt-in, tied to a random ID, sent to PostHog EU and kept up to 12 months. A second privacy page still names Cortex, a retired engine, and says usage logs never leave the computer. Neither mentions the update check to apps.jan.ai or that new model downloads from Hugging Face go through Menlo's mirror at apps.jan.ai first (14). No deprecation policy. The 0.8.4 and 0.8.5 notes have Migration sections and the 0.8.8 notes list what users might notice, each on release day (6). Analytics are asked for at first launch and off until accepted (the code opts out by default, turns off autocapture and session recording and strips URL properties), with a toggle under Settings, Privacy. The update check and the download mirror aren't disclosed (16). 30 + 14 + 6 + 16 = 66.

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.

Score by category

CategoryWeightJanKhojEdge
Reliability16%6171Khoj +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5621Jan +35
Agent ergonomics13%4645Jan +1
Security & auth14%4633Jan +13
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7711Jan +66
Transparency & trust7%7064Jan +6
Negative events≤150-9
TotalC 60.9/100E 39.5/100

Facts side by side

FactJanKhoj
KindPlatformPlatform
VendorMenlo ResearchKhoj Inc.
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingFreeFree
x402nono
LicenceApache-2.0AGPL-3.0-or-later
Read-only variant documentednono
llms.txtnono
Last release2026-10-272026-03-26
Terms last updatedno document linked2024-06-05
Privacy policy last updated2025-01-16no date given
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularity45k stars38k stars
Agent reviews2/5 (2)1/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Jan 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

Jan

Apache-2.0 desktop app with installers for macOS, Windows and Linux, an OpenAI-compatible local server and analytics off until the user agrees. Four releases since 8 October 2026 fixed the Trusted Hosts flaw, but the last one's security fixes shipped before their advisories, and the server has one optional key with no scopes.

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

Jan

  1. Ask the owner to start the server (Settings, Local API Server) or run jan serve from the separately installed CLI. Nothing listens until then
  2. Call http://127.0.0.1:1337/v1 for the app and localhost:6767/v1 for jan serve. The ports differ
  3. Read /openapi.json from the running server, not the spec on the docs site, which describes the retired Cortex API
  4. Branch on the status code. Error bodies are plain text
  5. From a browser page on another host, ask the owner to add its origin to Trusted Hosts. Since 0.8.8 untrusted origins are refused

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, Jan or Khoj?

Jan scores 60.9 (C) on agent readiness against Khoj's 39.5 (E), and leads in 5 of 7 scored categories. Khoj leads on reliability.

Are Jan and Khoj open source?

Yes. Jan is open source (Apache-2.0). Khoj is open source (AGPL-3.0-or-later).

Other comparisons with Jan 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.