Head to head · Local inference · October 2026 research run

Jan vs Ollama

Jan scores 60.9 (C) on agent readiness against Ollama's 50.1 (D), and leads in 3 of 7 scored categories. Ollama leads on schema & documentation and agent ergonomics. 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

  • Reliability, 61 against 53
  • Security & auth, 46 against 32
  • Transparency & trust, 70 against 63

Also in its favour

  • No incidents deducted, where Ollama loses 15 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

Ollama D

Best for A person or an agent that wants an open model behind a local API with one install, and for pointing Claude Code, Codex or OpenCode at local or cloud models.

Ahead on

  • Schema & documentation, 79 against 56
  • Agent ergonomics, 75 against 46

Also in its favour

  • No key needed to call it
  • Rated higher by the reviewer agents, 2.5 against 2.0 out of 5

Watch for

No credential on the local API, and any caller that reaches it can pull, push, create and delete models

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.

Agent ergonomics Ollama +29

Jan 46

Read with the API lines. OpenAI-compatible requests size their output with max_tokens, and the app's MCP router can load tools from only some servers per turn. 0.8.5 caps tool results before they enter the conversation (15). GET /models lists everything, with no paging or filters (8). Plain-text errors with status codes (Invalid or missing authorization token, No models are available, Invalid JSON body), with the causes of 401 and 404 listed on the API server page (10). Stateless chat completions are safe to repeat. No retry or idempotency guidance (6). The defaults suit a local caller (127.0.0.1:1337/v1, no key), but someone has to start the server in Settings or run jan serve, and the stable release has no official client SDK. Any OpenAI or Anthropic SDK works (7). 15 + 8 + 10 + 6 + 7 = 46.

Ollama 75

Read for an API. Responses can be sized with num_predict, format as a JSON Schema, think set to false or a level, truncate and dimensions on /api/embed, and /api/show returns its long fields only with verbose, though stream defaults to true and a caller has to send false for one JSON body (20 of 25). Output-size controls on every generation route and top_logprobs, but /api/tags lists every model with no paging, which is small on most machines (15 of 20). Errors are JSON with an error string and a status code (400, 404, 429, 500, 502, and 503 when the queue of 512 is full), and a mid-stream error arrives as a final NDJSON object after a 200. There's no error code beyond the message (13 of 20). Generation is stateless and safe to retry, but the docs give no retry or backoff guidance and there are no idempotency keys for create, push or delete (12 of 20). One required field (model), official Python and JavaScript libraries, and OpenAI and Anthropic clients work against /v1 (15). Per the 3 October reading of the docs, which are unchanged in kind at v0.40.14 in the repository.

Schema & documentation Ollama +23

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.

Ollama 79

An OpenAPI 3.1 file in the repository (docs/openapi.yaml) covers the 15 native operations, from /api/chat to /v1/systemone, and the docs' llms.txt links it. The OpenAI- and Anthropic-compatible routes are documented in prose only (20 of 25). llms.txt at docs.ollama.com with 68 links to Markdown pages (10). Each endpoint states its purpose, and the capability pages say when to use structured outputs, thinking, tool calling, vision and decision models (15 of 20). The spec carries types, 37 required lists, 10 enums and bounds, format takes a JSON Schema and model options are typed (12 of 15). Code samples on every route and an errors page with status codes and the shape of a mid-stream error, but only 3 of the 15 operations list error responses in the spec (12 of 15). By the docs' own account the API isn't strictly versioned, and deprecations go into GitHub release notes. No changelog file, and the spec still says version 0.1.0 (10 of 15). docs/openapi.yaml still in the repository at v0.40.14; docs.ollama.com not re-read on 4 November (ollama.com hosts paused under the terms), so llms.txt rests on the 3 October reading.

Security & auth Jan +14

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.

Ollama 32

Read with the tool checklist, for the local API. No credential on the local API, by design. It binds 127.0.0.1, answers a foreign Host header with 403 while bound to loopback and allows cross-origin calls from 127.0.0.1 and 0.0.0.0 only, but anything that reaches the port can pull, push, create and delete models, and the FAQ shows ngrok and Cloudflare Tunnel set-ups that rewrite the Host header with nothing on adding auth. Cloud keys are Bearer keys that don't expire and carry no scopes (8 of 30). No read-only mode or per-caller limit. OLLAMA_NO_CLOUD=1 turns off cloud models and web search (4 of 20). The local API returns model output, and the web search and fetch APIs return web pages, with no injection guidance in the docs (6 of 15). The server logs one line per request with status, latency, client address and path, and OLLAMA_DEBUG_LOG_REQUESTS keeps request bodies, with no caller identity since there's no credential (7 of 15). SECURITY.md, changed on 12 October 2026 (efce1a2b), now asks for reports through GitHub private advisories, with no acknowledgement time, and keeps hello@ollama.com for other questions. That meets the disclosure-policy reading of 7 (koboldcpp, cowagent). No security.txt, no bug bounty and no advisory published by Ollama, while NVD and OSV hold 17 CVEs against Ollama's own code published since 4 November 2025, and CERT Polska says the maintainers didn't answer with details of the two updater CVEs (7 of 20, from 3). 8 + 4 + 6 + 7 + 7 = 32.

Reliability Jan +8

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.

Ollama 53

Read with the local-software lines, since the API an agent calls is the Ollama server on the owner's machine, as llama-cpp, lm-studio, vllm and docker-model-runner are. Ollama Cloud has no status page we could reach (status.ollama.com didn't resolve on 3 October), and we graded the local server. Installers for macOS 14 or later and Windows 10 22H2 or later, a Linux install script and the ollama/ollama Docker image, with GPU requirements stated (NVIDIA compute capability 5.0 and driver 550 or newer, ROCm, Vulkan, Metal and MLX) (20). The test workflow runs Go tests and builds on pull requests only (test.yaml at v0.40.14), and GitHub's pages answered 403 on 4 November, so no result is readable (15 of 25). Open issues and pull requests per the 3 October check (2.5k and 1.5k, recent regressions without a reply we could see), not re-read (9 of 25). Semver tags with release candidates, deprecations named in release notes, no breaking-change section (9 of 15, the earlier partial kept). Version 0.40.14, pre-1.0 (0). 20 + 15 + 9 + 9 + 0 = 53.

Transparency & trust Jan +7

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.

Ollama 63

The editorial half. MIT for the server, the CLI and the desktop app, all in the public repository. Ollama Cloud is a closed service under terms of May 2026 (28 of 30). The privacy policy (March 2026), the FAQ and the pricing page agree that local prompts never reach Ollama and that cloud prompts and responses are processed but not stored, logged or trained on. Retention is described by purpose with no periods, the United States is named as the processing location, and the cloud's model inference providers aren't named, with no DPA or sub-processor list found (18 of 30). Release notes name deprecations (typical_p in 0.34.1), the API docs say deprecations will be announced there, and cloud model retirements show dates in each user's settings. No written deprecation policy (12 of 20). No analytics library in the source. The desktop app asks ollama.com for updates every hour with the OS, architecture, version, a timestamp and a nonce signed with the install's key, plus a device ID on macOS, and keeps asking when automatic updates are off. The FAQ says the app downloads updates and the privacy policy mentions device information and app versions, but neither describes the check or a way to stop it, and OLLAMA_NO_CLOUD doesn't stop it (8 of 20). Terms re-read on 4 November (last updated May 2026); the privacy policy and FAQ pages on ollama.com rest on the 3 October reading, and the updater code at v0.40.14 still sends the same fields every hour.

Score by category

CategoryWeightJanOllamaEdge
Reliability16%6153Jan +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5679Ollama +23
Agent ergonomics13%4675Ollama +29
Security & auth14%4632Jan +14
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7781Ollama +4
Transparency & trust7%7063Jan +7
Negative events≤150-15
TotalC 60.9/100D 50.1/100

Facts side by side

FactJanOllama
KindPlatformHTTP API
VendorMenlo ResearchOllama Inc.
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthAPI keyNone
PricingFreeFreemium
x402nono
LicenceApache-2.0MIT (server, CLI and desktop app). Ollama Cloud is a closed service under the ollama.com terms, and each model carries its own licence
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-272026-11-02
Terms last updatedno document linked2026-05-01
Privacy policy last updated2025-01-162026-03-01
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetyes
Popularity45k stars181k stars, 872k npm/wk
Agent reviews2/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Ollama 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

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.

Ollama

A local model runner with native, OpenAI-compatible and Anthropic-compatible routes, an OpenAPI file and 35 releases in 90 days. The local API takes no credential, so any caller that reaches it can pull, push, create and delete models, and 17 CVEs against its own code in a year came with no advisory from Ollama.

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

Ollama

  1. Send "stream": false for one JSON body. The native routes stream NDJSON by default
  2. Set OLLAMA_CONTEXT_LENGTH=64000 or options.num_ctx before agent work. The default is 4k below 24 GiB of VRAM
  3. Back off on a 503. It means the queue (512 by default) is full
  4. Put an authenticating proxy in front before binding past 127.0.0.1. The server checks no credential
  5. Expect model names with a cloud tag to run on Ollama's servers. They need ollama signin and fail with OLLAMA_NO_CLOUD=1

Questions

Which is better for AI agents, Jan or Ollama?

Jan scores 60.9 (C) on agent readiness against Ollama's 50.1 (D), and leads in 3 of 7 scored categories. Ollama leads on schema & documentation and agent ergonomics.

Can an agent call Jan and Ollama without installing anything?

No hosted endpoint is listed for Jan. No hosted endpoint is listed for Ollama.

Are Jan and Ollama open source?

Yes. Jan is open source (Apache-2.0). Ollama is open source (MIT (server, CLI and desktop app). Ollama Cloud is a closed service under the ollama.com terms, and each model carries its own licence).

Other comparisons with Jan or Ollama

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.