Want to use Open WebUI in your organization without setting it up and maintaining it yourself?
We run Open WebUI as a managed service and AI platform: your own instance with models operated in Germany by German providers, SSO and a Section 203 supplementary agreement, from EUR 149.90 net per month. If your own model should run on a dedicated GPU, the Managed GPU Server includes Open WebUI, from EUR 699 net per month plus EUR 499 net one-time setup. For data that must not leave the building, the AI Cube brings Open WebUI preconfigured into your own network.
View Open WebUI hosting and pricing · Schedule an initial consultation
Open WebUI and AnythingLLM are two self-hosted interfaces for language models that answer questions about documents, run agents and address local as well as external models. They target different forms of use: Open WebUI the central server operation for many users, AnythingLLM getting started with a desktop app and small teams on a Docker instance.
This article compares both by the criteria that matter in operation: license, deployment form, sign-in and permissions, knowledge base, models and agents, telemetry, security advisories and cost. The information comes from the GitHub API, license files and vendor documentation as of 21 October 2026.
Table of contents
- Short answer
- Brief overview of both tools
- Basic data at a glance
- License and branding
- Operation: server, desktop and architecture
- Sign-in, SSO and permissions
- Knowledge base and RAG
- Models, agents and MCP
- Telemetry and data flow
- Security advisories of the last twelve months
- Vendor, support and cost
- Which tool for which use
- AnythingLLM alternatives
- Combining both
- GDPR and data protection
- Common misconceptions
- Data and methodology
- How WZ-IT works
- Further guides
- Sources
Short answer
| Open WebUI | AnythingLLM | |
|---|---|---|
| License | Open WebUI License (BSD-3-Clause plus branding clause), not OSI-compliant | MIT (repository, Docker), no additional clauses; desktop app under its own terms of use |
| Changing the branding | only with at most 50 end users, written permission or an enterprise license | free (according to the docs, white-labeling only in the Docker version) |
| Deployment form | server (Docker, Helm, pip); desktop app at alpha stage | desktop app for individuals, Docker server for teams |
| Data storage | SQLite or PostgreSQL, embedded ChromaDB | SQLite and LanceDB embedded, PostgreSQL optional |
| Sign-in | OAuth/OIDC, LDAP, trusted header, SCIM; SAML via proxy | local accounts; Simple SSO Passthrough; OIDC, LDAP, SAML, SCIM not documented |
| Permissions | roles, permissions, nested groups, ACLs per model and knowledge base | Admin, Manager, Default; assignment per workspace; no groups |
| Knowledge base | hybrid search, reranking, 13 vector databases | 9 vector databases, reranking only with LanceDB, connectors according to the code |
| Agents and MCP | tools, functions; MCP client (Streamable HTTP, administrators only) | @agent skills, Agent Flows; MCP client (not in the vendor cloud) |
| Vendor | Open WebUI Inc. | Mintplex Labs Inc. |
Rule of thumb: Open WebUI for a central platform with many users, SSO, groups and knowledge bases. AnythingLLM for getting started with the desktop app, small teams without a connection to identity management, and free branding under MIT (Docker version).
Brief overview of both tools

Open WebUI (formerly Ollama WebUI) is a self-hosted web interface that originally emerged for connecting to Ollama and now also addresses OpenAI-compatible servers and other providers. Features and deployment options are described on the page Open WebUI at WZ-IT. How Open WebUI can be connected to Nextcloud with file permissions is shown in the article Connecting Open WebUI to Nextcloud: RAG with ACLs.

AnythingLLM describes itself as an all-in-one application for chat with documents, agents and RAG, as a desktop app and as a Docker server. The page AnythingLLM at WZ-IT describes installation and operation.
Basic data at a glance
| Open WebUI | AnythingLLM | |
|---|---|---|
| Repository | open-webui/open-webui | Mintplex-Labs/anything-llm |
| Latest version | 0.12.3 (16 Oct 2026) | 1.18.0 (13 Oct 2026) |
| GitHub stars | around 156,400 | around 67,400 |
| Archived | no | no |
| Vendor | Open WebUI Inc. | Mintplex Labs Inc. |
| Desktop app | own repository, AGPL-3.0, early alpha | part of the product (Windows, macOS, Linux) |
License and branding
AnythingLLM is under the MIT license. The file has 20 lines and contains no branding requirement and no user limit; the repository has no ee or enterprise directory. The terms for self-hosted operation describe only the core as MIT and provide for service levels for self-hosted operation only through a separate enterprise agreement. The desktop subscription AnythingLLM Pro (lifts daily limits of the Magic features) and the hosted cloud are paid. The desktop app is governed by its own terms of use (as of 14 July 2025): use for personal and internal business purposes, no redistribution, no derivatives, no SaaS.
Open WebUI has been under the Open WebUI License since version 0.6.6: BSD-3-Clause plus clause 4. The clause prohibits changing, removing, obscuring or replacing the "Open WebUI" branding. Exempt are at most 50 end users within any rolling 30-day period, prior written permission from the rights holder or a signed enterprise license. With unchanged branding, commercial use is also permitted according to the license page, with no cap for internal deployments. White-label and co-branding require an enterprise license. The Terminals service for Open Terminal is in a separate repository under the Open WebUI Enterprise License.
The license history of Open WebUI: MIT up to version 0.5.4, BSD-3-Clause for 0.5.5 to 0.6.5, and the Open WebUI License from 0.6.6 (release of 5 May 2025); the code up to and including 0.6.5 remains under BSD-3-Clause. License history, the 50-user threshold and the enterprise license are explained in the article Open WebUI License and Branding.
Operation: server, desktop and architecture
| Open WebUI | AnythingLLM | |
|---|---|---|
| Recommended way | Docker, one container | Docker (port 3001) for teams, desktop app for individuals |
| Other ways | Compose, Podman, Docker Swarm, pip/uv, Helm chart | bare metal, cloud templates (AWS CloudFormation, GCP, DigitalOcean, Render, Railway), Helm chart in the repository |
| Additional services | none by default: SQLite and embedded ChromaDB | none: SQLite and LanceDB embedded; PostgreSQL optional |
| Minimum values per docs | not stated for operation (development environment: at least 4 GB RAM) | 2 GB RAM, 2 cores with AVX2, 5 GB storage |
| Multiple instances | PostgreSQL, external vector database, Redis, shared file storage | the docs advise against horizontal scaling with SQLite and recommend the pg image (PostgreSQL, PGVector); Redis is not provided |
The multi-user mode of AnythingLLM is available only in the Docker version and cannot be undone after it is switched on. AVX2 is a requirement on x86 hosts because of LanceDB; with another vector database it does not apply. The Helm chart in the repository carries appVersion 1.85.0 and therefore does not match version 1.18.0. For Open WebUI, the default vector database ChromaDB is not suitable for multiple workers or replicas according to the scaling documentation.
Sign-in, SSO and permissions
| Open WebUI | AnythingLLM | |
|---|---|---|
| Email and password | yes, first account becomes administrator | multi-user mode: accounts with invitations; single user: optional password protection |
| OAuth/OIDC | Google, Microsoft, GitHub, generic OIDC | not described in the docs |
| LDAP/Active Directory | yes | not described in the docs |
| SAML | via trusted header proxy | not described in the docs |
| SCIM 2.0 | yes, via environment variables | not described in the docs |
| Other | trusted header, authenticator app (MFA) | Simple SSO Passthrough: one-time login link per user via API key, valid for 10 minutes, session 30 days |
| Roles | admin, user, pending | Admin, Manager, Default |
| Groups | yes, nested, additive permissions | none |
| Access per model and knowledge base | ACLs for groups and users | assignment per workspace; a document applies to all users of the workspace |
| Audit log | AUDIT_LOG_LEVEL, default NONE |
event logs: logins, messages, settings, uploads |
| Usage statistics | admin analytics | no usage statistics described (the docs mention only "logs, analytics" for admins in general) |
According to the docs, the Manager role in AnythingLLM manages everything except the settings for LLM, embedder and vector database; in the code, event logs, API keys, agent and MCP configuration, embed widgets and further system settings are additionally reserved for admins. For the Enterprise cloud tier, the vendor lists "SSO, RBAC, and more" without details. In Open WebUI, the documentation does not label any of the sign-in methods as an enterprise feature; the README lists LDAP, SSO and SCIM under "Enterprise Authentication & Provisioning".
Knowledge base and RAG
| Open WebUI | AnythingLLM | |
|---|---|---|
| Vector databases | 13 according to the environment variable docs (README: 9), default ChromaDB | 9: LanceDB (default), PGVector, Astra DB, Pinecone, Chroma (with ChromaCloud), Weaviate, Qdrant, Milvus, Zilliz |
| Search | hybrid of BM25 and vector, reranking with CrossEncoder | vector search; reranking ("Accuracy Optimized") only with LanceDB; hybrid search not described |
| Extraction | Tika, Docling, Document Intelligence, Mistral OCR, PaddleOCR-vl | text formats, PDF, DOCX, PPTX, XLSX, CSV, EPUB, MBOX; audio and video via transcription; images |
| Connecting sources | Google Drive, OneDrive/SharePoint; with oikb 40+ sources | connectors according to the source code: Confluence, Drupal Wiki, Obsidian, Paperless-ngx, GitHub/GitLab/Gitea, website crawler, YouTube |
| Web search | dozens of providers (SearXNG, Brave, Tavily, Kagi etc.) | via agent skill, default DuckDuckGo |
| Permissions from source systems | not documented | no permission sync |
AnythingLLM assigns documents to a workspace; whoever sees the workspace sees all embedded documents. For sources with file permissions, the permission check belongs before the vector search, see Connecting Open WebUI to Nextcloud.
Models, agents and MCP
| Open WebUI | AnythingLLM | |
|---|---|---|
| Local models | Ollama (also bundled), vLLM, llama.cpp, LM Studio | Ollama, LM Studio, LocalAI; desktop default for new installations since 1.18.0 Lemonade/llama.cpp |
| Cloud providers | OpenAI, Azure OpenAI; Anthropic, Gemini and Bedrock via compatible interfaces | 38 providers per README, including OpenAI, Azure, Bedrock, Anthropic, Gemini, Mistral, OpenRouter, LiteLLM |
| Agents | agent models with instructions, tools and knowledge; Filters, Actions, Pipes, Tools, Skills | @agent with skills (web search, scraping, SQL agent, Gmail, calendar, file system), no-code Agent Flows, custom skills |
| MCP | client since 0.6.31; only administrators add servers | client in Docker and desktop, not in the vendor cloud; only administrators add MCP servers |
| Code | Open Terminal; Pyodide and Jupyter are considered legacy | code interpreter as a separate feature not documented |
| API | OpenAI-compatible, the docs call it "experimental" | REST API with Swagger at /api/docs, OpenAI-compatible subset |
| Other features | artifacts, voice, image generation, memory | image generation via /img, speech output, memories (off), embed widget (Docker only), browser extension, Telegram, scheduled tasks (single-user mode only) |
The plugin ecosystems are built differently: Open WebUI is extended on the server with Python, AnythingLLM is extended through MCP, Agent Flows and custom JavaScript skills.
Telemetry and data flow
| Open WebUI | AnythingLLM | |
|---|---|---|
| Default | The Docker image sets SCARF_NO_ANALYTICS=true, DO_NOT_TRACK=true, ANONYMIZED_TELEMETRY=false; update check on |
Telemetry on (PostHog); according to the README: installation type, documents added or removed, vector database, LLM provider and model, "chat sent" without content; the code sends further event types without chat content |
| Switching off | OFFLINE_MODE disables the update check, model downloads and plugin installation |
DISABLE_TELEMETRY=true |
| Still outbound | Connections to the selected model providers | cdn.anythingllm.com (model mirror), GitHub (context window cache) and the selected providers |
Security advisories of the last twelve months
Published GitHub security advisories from 21 Oct 2025 to 21 Oct 2026:
| Open WebUI | AnythingLLM | |
|---|---|---|
| Advisories in total | 163 | 23 |
| critical | 1 (LDAP sign-in with empty password, CVE-2026-44551) | 1 (XSS to remote code execution via an LLM response, CVE-2026-32626) |
| high | 70 | 5 (including RCE via ripgrep, SQL injection in the SQL agent, path traversal) |
| medium and low | 92 | 17 |
| Focus areas | XSS, sign-in, SSRF, hangs | multi-user permissions: access to other users' data, bypassing the Manager role |
The number says nothing about the quality of a project. It shows how much was reported and published. For both: apply updates promptly and do not expose the instance to the internet without sign-in. The AnythingLLM security policy excludes, among others, SSRF via web scraper and collector against internal hosts, SSRF via service URLs configured by the administrator, reports about agent tools enabled by the administrator and reports without password protection or multi-user mode as valid reports.
Vendor, support and cost
| Open WebUI | AnythingLLM | |
|---|---|---|
| Self-hosting | free with unchanged branding | free (MIT; desktop app under its own terms of use) |
| Commercial offering | enterprise license for white-label and Terminals, price not public | Cloud: Basic USD 50, Pro USD 99 per month; Enterprise on request; desktop subscription Pro |
| Support | account manager and office hours for licensees, no implementation services | Pro with 72-hour support SLA (cloud); self-hosted SLA only via enterprise agreement |
| Licensees | registered organizations only | - |
The AnythingLLM cloud instance runs isolated per customer, has no built-in model and supports neither MCP nor custom agents. Vendor prices: as of 21 October 2026.
Which tool for which use
| Use | Best fit | To note |
|---|---|---|
| Central platform for many users with SSO and groups | Open WebUI | branding clause; multi-instance operation needs PostgreSQL, Redis, vector database |
| Single-seat entry without a server | AnythingLLM Desktop | no multi-user operation |
| Small team, few workspaces, local accounts | AnythingLLM (Docker) | no groups, no OIDC/LDAP/SAML in the docs |
| Access per model and knowledge base by group | Open WebUI | audit log off by default |
| Free branding under your own brand without a vendor license | AnythingLLM (Docker) | MIT; desktop app under its own terms of use |
| Knowledge base with hybrid search and reranking | Open WebUI | configure extraction and reranking |
| Connectors to Confluence, GitHub, Paperless-ngx | AnythingLLM | no permission sync; oikb complements Open WebUI |
| Agents with MCP and skills on a team server | both | AnythingLLM cloud without MCP |
AnythingLLM alternatives
AnythingLLM reaches its limits for teams in three places: sign-in and permissions (local accounts, three fixed roles, no groups; OIDC, LDAP, SAML and SCIM are not described in the docs), sources with document permissions (no permission sync) and operating several instances (the docs advise against horizontal scaling with SQLite). Depending on the case, these alternatives come into question:
| Case | Alternative | Reason |
|---|---|---|
| OIDC, LDAP or SCIM, groups, access per model and knowledge base | Open WebUI | described in the docs without an enterprise label; observe the branding clause |
| SAML, native connection of Anthropic, Bedrock and Vertex AI, MCP agents | LibreChat | SAML, OIDC and LDAP in the application, native provider clients; MongoDB as a required service |
| Search across Confluence, SharePoint, Jira and Slack with document permissions | Onyx | permission sync for 14 connectors as a license part of the Enterprise Edition |
| Agent and skill store | LobeHub | observe the license terms for derivative works |
| RAG API for your own applications | PrivateGPT | API layer without user management |
The detailed comparisons: Open WebUI vs LibreChat, LibreChat vs AnythingLLM and Open WebUI vs Onyx. All six platforms are in the overview Open WebUI alternatives.
Combining both
In some environments both run in parallel: Open WebUI as the central platform for many users, AnythingLLM Desktop as a single-seat tool for analyses on the laptop. Both address the same model servers, for example Ollama or vLLM, and therefore share the GPU resources. Credentials and documents stay separate.
Should Open WebUI answer questions about your own documents, with sources and per-person permissions?
In the RAG Proof of Value we make one prioritized knowledge source usable and review the answers for subject-matter accuracy. This becomes the internal AI assistant for the whole team.
GDPR and data protection
With self-hosting, accounts, chats and documents stay in your own infrastructure, in a data center in the EU or in Germany. Whether prompts and document excerpts leave the premises is decided by the choice of models: local models via Ollama or vLLM and models at providers in Germany keep the data path in the country, connections to US providers send prompts there. In addition there are the outbound connections from the section Telemetry and data flow, which can be switched off or limited by firewall. On professional secrecy and Section 203 of the German Criminal Code (StGB), see the overview AI platforms for businesses compared; this article is not legal advice.
Common misconceptions
- "Open WebUI is MIT-licensed." No. Since version 0.6.6 the Open WebUI License with a branding clause applies; only AnythingLLM is under MIT (repository and Docker version; the desktop app has its own terms of use).
- "AnythingLLM is only a desktop app." No. There is a Docker version with multi-user operation, roles and invitations.
- "AnythingLLM offers SSO via OIDC or LDAP." Not in the documentation. There are local accounts and Simple SSO Passthrough, in which an upstream system generates login links.
- "Open WebUI needs Ollama." No, Open WebUI also talks to OpenAI-compatible servers, and Ollama is optional.
- "Self-hosted means no outbound connection." AnythingLLM sends telemetry to PostHog and downloads models from a CDN, Open WebUI checks for updates. Both can be switched off.
- "Both take over file permissions from the source systems." No. AnythingLLM has no permission sync, and for Open WebUI it is not documented.
Data and methodology
As of: 21 October 2026. The data basis is the GitHub API (license, version, stars, published security advisories), the LICENSE files of the repositories, the documentation of Open WebUI and AnythingLLM, and the AnythingLLM pricing page. Stars are rounded and change daily. Statements with "not described in the docs" mean that the documentation does not describe the feature; the function may exist in the code. The connector list of AnythingLLM comes from the source code, not from an official list. The advisories cover the period from 21 October 2025 to 21 October 2026.
Tables and figures may be reused with attribution and a link to this article.
How WZ-IT works
WZ-IT runs Open WebUI as an AI platform: your own instance with models operated in Germany by German providers, SSO and a Section 203 supplementary agreement, from EUR 149.90 net per month. The Open WebUI branding stays visible, WZ-IT does not present Open WebUI as its own product; we clarify license questions such as the branding clause before rollout. WZ-IT runs AnythingLLM as managed hosting in German data centers, with a data processing agreement. We also install both platforms in your infrastructure, for example on Hetzner or Proxmox, and connect sign-in to Keycloak or Authentik (LDAP, SAML, OAuth). Monitoring runs with Uptime Kuma and Grafana.
Further guides
- Open WebUI vs LibreChat, the comparison with the third widely used platform.
- LibreChat vs AnythingLLM, the comparison without Open WebUI.
- Open WebUI vs Onyx, chat interface versus enterprise search.
- Open-source AI chat platforms compared, all platforms at a glance.
- Open WebUI License and Branding, the clause in detail.
- Managed services for open-source software
- GDPR-compliant AI inference with GPU servers
- Business process automation with n8n and AI agents
Still unclear which tool fits? The AI opportunity check tests which approach holds up on a concrete process and ends with a pilot recommendation. From EUR 3,900 net.
Next step
Deploying local AI in your company?
We make you AI-ready: your own hardware, full data sovereignty and open-source models without vendor lock-in. From consulting and setup to ongoing operations.
Read next: Ollama vs vLLM · Running GPT-OSS-120B on the AI Cube · DGX Spark vs AI Cube
Choose Open WebUI or AnythingLLM, or have them operated? We assess number of users, sign-in, permissions and models, and run Open WebUI and AnythingLLM in Germany. Book an appointment · [email protected]
Sources
- Open WebUI, repository
- Open WebUI, LICENSE
- Open WebUI Docs, License
- Open WebUI Docs, Enterprise
- Open WebUI Docs, Single Sign-On
- Open WebUI Docs, Roles and permissions
- Open WebUI Docs, Scaling
- Open WebUI Docs, Environment variables
- Open WebUI Docs, MCP
- Open WebUI, Security Advisories
- AnythingLLM, repository
- AnythingLLM, LICENSE
- AnythingLLM, terms for self-hosted operation
- AnythingLLM Docs, System requirements
- AnythingLLM Docs, Security and access
- AnythingLLM Docs, Configuration (Simple SSO Passthrough)
- AnythingLLM Docs, Desktop app terms of use
- AnythingLLM, SECURITY.md
- AnythingLLM Docs, Event logs
- AnythingLLM Docs, Vector databases
- AnythingLLM Docs, Agents
- AnythingLLM Docs, MCP
- AnythingLLM Docs, API
- AnythingLLM, Cloud and pricing
- AnythingLLM, Security Advisories













