Head to head · Local inference · October 2026 research run

AnythingLLM vs Open WebUI

Open WebUI scores 52.8 (D) on agent readiness against AnythingLLM's 45.9 (E), and leads in 5 of 7 scored categories. AnythingLLM leads on reliability. 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

  • Reliability, 70 against 60

Also in its favour

  • Open source

Watch for

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

Open WebUI D

Best for A team or a person who wants a self-hosted chat front end over Ollama or OpenAI-compatible models with users, groups, retrieval and tools, and an API an agent can call on that instance.

Ahead on

  • Schema & documentation, 65 against 57
  • Agent ergonomics, 57 against 46
  • Security & auth, 65 against 38
  • Maintenance & community, 86 against 78
  • Transparency & trust, 67 against 62

Also in its favour

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

Watch for

129 reviewed advisories cover flaws fixed from 24 November 2025 to 25 August 2026, 1 Critical and 56 High among them, with 19 more fixed in 0.11.4.

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.

Security & auth Open WebUI +27

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.

Open WebUI 65

Read with the tool checklist. One API key per user, sk- plus 32 hexadecimal characters, carrying that user's role and group permissions, revoked by deletion and rotated by generating a new one. Keys are off by default (ENABLE_API_KEYS), a group permission decides who may create one, and an administrator can limit them instance-wide to listed endpoints. They're stored in plain text, can be read back through GET /api/v1/auths/api_key, and have no scopes of their own and no expiry. The api_key table has expires_at and last_used_at columns that no code path sets. Tokens travel in the Authorization header, an x-api-key header or the session cookie, never a query string (20 of 30, plain revocable keys). Admin, user and pending roles with group permissions, per-model and per-knowledge access, workspace tools off for non-administrators, and tool permission modes (Ask for approval, and since 0.13.1 Auto with a review model) that are experimental and off by default. Workspace tools and functions are Python run with exec and the server's rights, which the security policy calls intended behaviour (14 of 20, read as localai's role scoping). Chats bring in web pages, files and tool output. The accepted-risks pages on model output and agentic applications name injected content in fetched pages and documents, say which injection reports count as vulnerabilities, and list the mitigations (per-user scoping, permissions, filters and confirmation prompts) (9 of 15). AUDIT_LOG_LEVEL records metadata, requests or requests with responses, NONE by default, and logs key calls under the key's owner, and API key creation and deletion raise events (12 of 15). The security policy takes reports only through GitHub Security Advisories, supports main only, gives no acknowledgement time ("Expect several weeks") and no bounty, and accepted reports become public advisories with patched versions. security.txt per the 3 October check, not re-read. No SOC 2 or ISO 27001. The route with no stated time is 7, and advisories handled in public add 3, as anythingllm's (10 of 20). 20 + 14 + 9 + 12 + 10 = 65. Advisories are charged one by one under negative events.

Agent ergonomics Open WebUI +11

AnythingLLM 46

Read with the tool lines for the developer API. Vector search takes topN and scoreThreshold, query mode skips the model when nothing relevant is found, and the OpenAI-compatible endpoints keep responses in a shape clients already parse, but chat answers carry full source chunks and there's no field selection (15 of 25). offset and limit on folder listings and limit and orderBy on workspace chats. Workspace, document and user lists return everything (10 of 20). Missing or wrong keys get 403 with {"error": "No valid api key found."}, chat failures return type: abort with an error string, and some routes answer 500 with an empty body (10 of 20). No idempotency keys or retry guidance, and repeating an upload stores a second copy (3 of 20). A chat needs only a message and a workspace slug, and any OpenAI SDK can call the compatible endpoints, but there's no official SDK (8 of 15).

Open WebUI 57

Read with the API lines. Chat requests pass max_tokens and the other request parameters through to the provider, knowledge base writes return only the affected files since 0.12.5, file reads by line range stop at a size limit since 0.13.1, and Tool Search (experimental, off by default) keeps deferred tool definitions out of a request until the model asks for them. No field selection (17 of 25, read as text-generation-webui's). page, skip or limit on file, knowledge, chat and model lists, while GET /api/v1/models/all returns every model in one list. Partly met, so the earlier partial is held (13 of 20). Errors are FastAPI detail strings, many from a shared ERROR_MESSAGES table, with status codes, and the API page explains a handful (400 for unprocessed files and for content already in a knowledge base, 401 causes, the provider's 429 with Retry-After). Partly met, earlier partial held (12 of 20). No idempotency keys or retry guidance. /api/v1/models/import is an upsert by id and /sync a declarative reconcile, both safe to repeat, and a knowledge base refuses content it already holds, while repeating a file upload stores a second copy. Partly met, earlier partial held (5 of 20). A chat needs only model and messages, and the docs show OpenAI and Anthropic SDKs and Claude Code pointed at an instance, but API keys stay off until an administrator turns them on and grants the permission, and there's no Open WebUI SDK. Partly met, earlier partial held (10 of 15). 17 + 13 + 12 + 5 + 10 = 57.

Reliability AnythingLLM +10

AnythingLLM 70

Read with the local-software lines, because an agent calls the developer API on an instance the owner runs, on the desktop or in Docker. AnythingLLM Cloud exists, and isn't what's graded here. Desktop builds for macOS, Windows and Linux, Docker images for amd64 and arm64 on Docker Hub and GHCR built on every release, Node 18 or later stated in package.json, and a system requirements page (16 GB of RAM and an 8-core CPU recommended) (20). 77 test files under server and collector, but the test workflow runs only on pull requests that touch server or collector code (on Node 24 since 29 October), never on master, and the runs we loaded showed approval waits and durations, not results. That is public CI that runs the tests with an unreadable result, read as ollama's pull-request-only test workflow (15 of 25). Per the 3 October check, not re-read on 4 November, 297 open issues and 21 open pull requests for a project with 206 commits since 5 July. Bug reports from 29 September were fixed in v1.17.0 two days later, though the issues stayed open, and the Windows backend crash in #6481 (24 September) had only a contributor's proposed fix when we looked (15 of 25). Semver tags and a changelog page per release with sections for new work, improvements and bug fixes, but no breaking-change section, and v1.14.1, a patch release, removed the DPAIS and Hugging Face providers (5 of 15). Version 1.19.0 (15). 20 + 15 + 15 + 5 + 15 = 70.

Open WebUI 60

Read with the local-software lines, since an agent calls an Open WebUI instance its owner runs, with no hosted Open WebUI service. The open-webui package on PyPI states Python 3.11 or 3.12 (requires-python >= 3.11, < 3.13.0a1 in pyproject.toml), and GHCR images, Docker Compose, Kustomize and Helm ship with each release (20). The frontend workflow runs npm run test:frontend on every push to main and dev, the backend workflow on push only lints, and the regression suite in the open-webui/tests repository runs on release pull requests to or from dev. Run results are on GitHub's pages, which our reader can't open, so this is public CI that runs the tests with an unreadable result (15 of 25). Per the 3 October check, not re-read on 11 November, 234 open issues and 72 open pull requests, with bug reports labelled within a day. Changelog entries since then link fixes to issues filed days earlier, but reply times couldn't be read, so the line is read as anythingllm's and jan's (15 of 25). CHANGELOG.md follows Keep a Changelog and states semantic versioning, with dated entries, Changed sections and migration warnings, but patch releases carry breaking changes (0.12.4 stops using saved tool-server connections while Direct Integrations is off, 0.13.1 turns off file preloading), and 0.11.4, a patch release, removed POST /api/v1/utils/pdf with no changelog entry. The line is partly met, so the earlier partial is held (10 of 15). 0.13.3, before 1.0, and the API page calls the API an experimental setup (0). 20 + 15 + 15 + 10 + 0 = 60.

Schema & documentation Open WebUI +8

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).

Open WebUI 65

Read with the API lines for the HTTP API an agent calls on an instance. FastAPI generates the OpenAPI document from the routes, and main.py serves /docs and /openapi.json only when ENV=dev. ENV defaults to dev in the backend (env.py), so a pip install serves both, while the Docker image sets ENV=prod and the docs say to set ENV=dev to reach Swagger. No spec file is published, and chat completions take a free-form dict. The line is partly met, so the earlier partial is held (12 of 25). The docs repository ships llms.txt and agents.txt and generates llms-full.txt and a Markdown copy of every page at build, and llms.txt was read on the docs host on 3 October. docs.openwebui.com wasn't requested on 11 November (see openQuestions) (10). The API Endpoints page says when to use each documented route, such as /import for additive updates against /sync to reconcile, and waiting for file processing before adding a file to a knowledge base, but covers selected routes of 584 (12 of 20). Pydantic request models with 54 Literal types across routers and models, while chat completions and many other routes take a plain dict (7 of 15, read as localai's). curl and Python examples on most documented routes, with 400 cases for unprocessed and duplicate files, 401 causes, 404, 502 and 504 on tool specs and the provider's 429 with Retry-After passed through, and no error reference page (11 of 15). Routes under /api/v1 apart from the chat routes, and a dated changelog per release (13 of 15). 12 + 10 + 12 + 7 + 11 + 13 = 65.

Maintenance & community Open WebUI +8

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).

Open WebUI 86

0.13.3, dated 8 November 2026 in the changelog and tagged on 9 November (30). 14 releases in the 90 days from 13 August, from 0.11.1 (25 August) to 0.13.3, each with a dated changelog section, dates from the changelog and the tags in a clone (20). Issues and pull requests per the 3 October check, not re-read on 11 November because GitHub's pages refuse our reader. The changelog links fixes to issues reported days before each release, but reply times couldn't be read (15 of 25, read as anythingllm's and jan's). No official SDK and no MCP server. The PyPI package and GHCR images ship with each release, and the API is OpenAI- and Anthropic-compatible. Partly met, so the earlier partial is held (13 of 15). CI on every push to main and dev, Actions pinned through an actions lockfile, and a Dependabot configuration for uv, pip, npm and Actions, now on a yearly schedule (monthly on 3 October). Partly met, earlier partial held (8 of 10). 30 + 20 + 15 + 13 + 8 = 86.

Transparency & trust Open WebUI +5

AnythingLLM 62

The repository is MIT, but the desktop app ships under terms of use that call its source code a trade secret and forbid reverse engineering, while the docs call both versions open source (22 of 30). TERMS_SELF_HOSTED.md says Mintplex Labs never sees a self-hosted instance's documents or chats. The desktop privacy policy (effective 14 July 2025) names PostHog and Cloudflare and says telemetry is kept briefly, with no period. The Cloud privacy policy deletes an instance's data at cancellation. The self-hosted terms call telemetry optional where it's on by default (18 of 30). No deprecation policy. Provider removals appear in release notes without notice dates, and SECURITY.md supports only the current major and its two newest minors (5 of 20). Telemetry is on by default and documented with an in-app switch and DISABLE_TELEMETRY. The privacy policy points to a code search of every sendTelemetry call as the full list, which is complete by construction, but the README lists five kinds of event while the source sends 33 event types, including agent tool names and login events, and tool-call events skip the log line the README says every event gets. We counted that here rather than as a deduction, since the code search is disclosed and the events carry no content (13 of 20).

Open WebUI 67

The Open WebUI License is BSD-3-Clause terms plus a clause that bars altering or removing the Open WebUI branding in deployments with more than 50 end users in a rolling 30 days, unless the licensee has written permission or an enterprise licence. LICENSE_HISTORY keeps earlier code under MIT or BSD-3-Clause, and contributors sign a CLA. The source is public, the terms are short and commercial use is allowed, but the licence isn't OSI-approved. It sits above source-available licences that bar competing use, such as n8n's and nango's (20), and below the OSI 30 (22 of 30). The Chat Data Privacy page sets out where chat data lives, what administrators can see and which settings reduce retention. The openwebui.com privacy policy (31 December 2025, per the 3 October check, not re-read) covers the website only with no retention periods, and the docs advise keeping community sharing off while ENABLE_COMMUNITY_SHARING defaults to true (15 of 30). No deprecation policy, and the supported-versions table lists main only. Removals and changed defaults appear in release notes on release day, /api/chat/completed is marked deprecated without a date, and the PDF route's removal reached the API page but not the changelog (6 of 20). No analytics library in the source. The Docker image sets SCARF_NO_ANALYTICS, DO_NOT_TRACK and ANONYMIZED_TELEMETRY=false, Chroma's telemetry is off in code, OpenTelemetry is opt-in, and the release check to api.github.com is on by default and documented with ENABLE_VERSION_UPDATE_CHECK and OFFLINE_MODE as the switches (17 of 20). 22 + 15 + 6 + 17 = 60.

Score by category

CategoryWeightAnythingLLMOpen WebUIEdge
Reliability16%7060AnythingLLM +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5765Open WebUI +8
Agent ergonomics13%4657Open WebUI +11
Security & auth14%3865Open WebUI +27
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7886Open WebUI +8
Transparency & trust7%6267Open WebUI +5
Negative events≤15-15-15
TotalE 45.9/100D 52.8/100

Facts side by side

FactAnythingLLMOpen WebUI
KindPlatformPlatform
VendorMintplex LabsOpen WebUI Inc.
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthAPI keyAPI 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 engineeringOpen WebUI License. BSD-3-Clause terms plus a clause that forbids changing or removing the Open WebUI branding in deployments with more than 50 end users in a rolling 30 days, unless the licensee has written permission or an enterprise licence. Code from before set commits stays under MIT or BSD-3-Clause (LICENSE_HISTORY), and contributors sign a CLA
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-252026-11-08
Terms last updatedno date given2026-07-07
Privacy policy last updatedno date given2025-12-31
Customer content may train modelsnot found in the textyes, with an opt-out
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 textyes
Popularity67k stars153k stars
Agent reviews2/5 (2)2.5/5 (2)

The panel on both

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

Open WebUI

Open WebUI is self-hosted software with OpenAI- and Anthropic-compatible routes, API keys off by default that carry the owner's role and group permissions, and 14 releases in 90 days. Its limits are a pre-1.0 API with breaking changes in patch releases, keys stored in plain text, and 148 security advisories in twelve months, one without a listed fix.

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

Open WebUI

  1. Ask the administrator to set ENABLE_API_KEYS=true and grant the API key permission, then send the sk- key as Authorization: Bearer.
  2. Point OpenAI clients at http://<host>/api and Anthropic clients at the same base, not /api/v1, since the Anthropic SDK appends /v1/messages.
  3. Wait for a file's processing to finish before adding it to a knowledge base, or the call returns 400.
  4. Back off on a 429 using the provider's Retry-After, which Open WebUI passes through. There's no idempotency key, so don't repeat uploads blindly.
  5. Read the route list from the instance's /openapi.json on a pip install. A Docker instance serves it only after ENV=dev is set.

Questions

Which is better for AI agents, AnythingLLM or Open WebUI?

Open WebUI scores 52.8 (D) on agent readiness against AnythingLLM's 45.9 (E), and leads in 5 of 7 scored categories. AnythingLLM leads on reliability.

Are AnythingLLM and Open WebUI open source?

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). No open-source release is listed for Open WebUI.

Other comparisons with AnythingLLM or Open WebUI

Disclosure

Open WebUI 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.