Agent-readable comparison

Dust vs Open WebUI

Name: Dust vs Open WebUI: agent-readable comparison
Creator: onAI

Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI.

This comparison has 44 criteria with sourced findings for both products, including 44 that a second agent cross-checked for both. 51 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. No winner is declared. A missing sourced finding is not evidence that a capability is absent.

Dust source checks: 2026-10-21. Website: https://dust.tt
Open WebUI source checks: 2026-10-21 to 2026-10-26. Website: https://openwebui.com
Generated 2026-10-27; next source check due 2026-12-20.

Same facts as Markdown and JSON. Methodology.

Models

MOD-01 Model catalogue and providers

Judgment rule: List each available model by provider and plan, including reasoning, fast and multimodal variants. Record whether the user picks the model, the product routes automatically, or both. A provider counts only if at least one of its current models is selectable on the scoped plan.

Dust

Agent cross-checked Support: partial

Dust offers per-message model choice and ordered auto-model lists, with access-tier and region controls.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit plan (Free/Pro/Max); Enterprise model access inherits the published catalogue; model-tier and EU eligibility separately constrained; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.
The catalogue finding is restricted to named documentation entries; conflicting Gemini4 Argon EU eligibility is an explicit gap.

providers Which model providers are available? [supported]: Docs list OpenAI, Anthropic, Google, Mistral and Fireworks-served models; exact enabled models depend on workspace and tier. Sources: dust:dust:models, dust:dust:eu-models.
current_models Which current models are selectable on this plan? [partial]: The model-selection document lists GPT6.1 Sol, Claude Opus5.5/Sonnet5.5, Gemini3.8 Flash and Mistral models. Gemini4 Argon is excluded from this current-EU availability finding: its release note conflicts with the EU table, and the documented authoritative picker flag was not observed. No complete current tenant catalogue is claimed. Sources: dust:dust:models, dust:dust:changelog, dust:dust:eu-models, dust:dust:pricing.
user_choice Can users pick the model per chat? [supported]: The composer chooses a model for the next message; Agent Builder sets a persistent agent default. Sources: dust:dust:models.
auto_routing Does the product route between models automatically, and is the chosen model shown? [supported]: Basic/Standard/Premium use ordered candidate lists and availability fallback, not prompt-dependent task routing. A replacement indicator names the fallback during a detected outage. Sources: dust:dust:models.
multimodal_input Which models accept images, audio or files? [partial]: Conversation files support images, documents and audio transcripts; the exact input capability for every current model is not fully tabulated. Sources: dust:dust:files.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:models, dust:dust:eu-models, dust:dust:changelog, dust:dust:pricing, dust:dust:files.

Open WebUI

Agent cross-checked Support: partial

Customers connect local servers and cloud model endpoints and choose models in chat. The available catalog depends on their endpoints and credentials.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected code pinned to v0.12.3 / 91ea4e3421d1d8069f13d4a463fcb5986d94ea60; plan=Standard self-hosted with original branding intact; Enterprise only where explicitly stated; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure country; external inference, extraction, search and support locations require separate configuration and contracts; os=not specified.

Limitations

providers: Documented routes include OpenAI, Anthropic, Azure OpenAI, Mistral, DeepSeek and gateways such as OpenRouter; models must be enabled in the connected account. No endpoint was exercised.
current_models: Which current models are selectable on this plan? The provider guide contains example model names rather than an observed current endpoint catalog. Automatic routing and a current per-model modality matrix were not verified.
auto_routing: Does the product route between models automatically, and is the chosen model shown? The provider guide contains example model names rather than an observed current endpoint catalog. Automatic routing and a current per-model modality matrix were not verified.
multimodal_input: Vision and file context depend on the chosen model and configured extraction. No model-by-model audio/image acceptance matrix or fixture run was established.

providers Which model providers are available? [partial]: Documented routes include OpenAI, Anthropic, Azure OpenAI, Mistral, DeepSeek and gateways such as OpenRouter; models must be enabled in the connected account. No endpoint was exercised. Sources: open-webui:open-webui:provider, open-webui:open-webui:compat.
current_models Which current models are selectable on this plan? [unknown]: current_models: Which current models are selectable on this plan? The provider guide contains example model names rather than an observed current endpoint catalog. Automatic routing and a current per-model modality matrix were not verified.
user_choice Can users pick the model per chat? [supported]: Users select connected models in the chat selector and can compare several models. Sources: open-webui:open-webui:provider.
auto_routing Does the product route between models automatically, and is the chosen model shown? [unknown]: auto_routing: Does the product route between models automatically, and is the chosen model shown? The provider guide contains example model names rather than an observed current endpoint catalog. Automatic routing and a current per-model modality matrix were not verified.
multimodal_input Which models accept images, audio or files? [partial]: Vision and file context depend on the chosen model and configured extraction. No model-by-model audio/image acceptance matrix or fixture run was established. Sources: open-webui:open-webui:rag, open-webui:open-webui:extraction.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:provider, open-webui:open-webui:compat, open-webui:open-webui:rag, open-webui:open-webui:extraction.

MOD-02 Model freshness

Judgment rule: Measure the days from a provider's general release to availability in the product for the last three major releases from OpenAI, Anthropic and Google (and Mistral where offered). Use dated changelogs or observation. Record deprecation notice for retired models.

Dust

Agent cross-checked Support: partial

The public changelog and exact agent model selection are documented; release-lag and removal notice remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

release_lag_days What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? The dated changelog and model-selection docs were checked; last-three-release/provider lag measurements and a fixed advance deprecation-notice period were not established.
changelog Is there a dated public model changelog? [supported]: The public changelog contains dated model releases including Gemini 4 Argon on October 14, 2026. Sources: dust:dust:changelog.
deprecation_notice How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? The dated changelog and model-selection docs were checked; last-three-release/provider lag measurements and a fixed advance deprecation-notice period were not established.
version_pinning Can an admin keep an older model version? [partial]: An agent can select a specific model and keeps it until changed, subject to continued provider/workspace availability. No indefinite old-version entitlement is established. Sources: dust:dust:models.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:changelog, dust:dust:models.

Open WebUI

Agent cross-checked Support: partial

Dated upstream releases are public. A measured three-release availability lag and model retirement notice remain unknown.

Limitations

release_lag_days: What was the lag for each of the last three major releases, per provider? No matched dates for the last three major provider releases and endpoint availability were collected; no binding model-removal notice period was found in the release and provider guides.
changelog: GitHub release notes are dated and sometimes mention model/protocol changes; they are not a complete provider model availability timeline.
deprecation_notice: How much notice is given before a model is removed? No matched dates for the last three major provider releases and endpoint availability were collected; no binding model-removal notice period was found in the release and provider guides.
version_pinning: An admin can list explicit provider model/deployment IDs and keep a chosen local model. Provider removal still controls remote model availability.

release_lag_days What was the lag for each of the last three major releases, per provider? [unknown]: release_lag_days: What was the lag for each of the last three major releases, per provider? No matched dates for the last three major provider releases and endpoint availability were collected; no binding model-removal notice period was found in the release and provider guides.
changelog Is there a dated public model changelog? [partial]: GitHub release notes are dated and sometimes mention model/protocol changes; they are not a complete provider model availability timeline. Sources: open-webui:open-webui:releases.
deprecation_notice How much notice is given before a model is removed? [unknown]: deprecation_notice: How much notice is given before a model is removed? No matched dates for the last three major provider releases and endpoint availability were collected; no binding model-removal notice period was found in the release and provider guides.
version_pinning Can an admin keep an older model version? [partial]: An admin can list explicit provider model/deployment IDs and keep a chosen local model. Provider removal still controls remote model availability. Sources: open-webui:open-webui:openai, open-webui:open-webui:provider.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:releases, open-webui:open-webui:openai, open-webui:open-webui:provider.

MOD-03 Bring-your-own keys and provider contracts

Judgment rule: Record customer-held API keys, customer cloud accounts (Azure OpenAI, Bedrock, Vertex), and aggregator routes (OpenRouter, LiteLLM) as separate routes. Record what still works without a vendor-provided model, whether prices change with BYO, and documented restrictions. API-key support does not imply support for the customer's own Azure contract.

Dust

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Open WebUI

Agent cross-checked Support: partial

Customer-held keys, Azure deployments and compatible endpoints are documented. The standard software licence does not include provider usage.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected code pinned to v0.12.3 / 91ea4e3421d1d8069f13d4a463fcb5986d94ea60; plan=Standard self-hosted with original branding intact; Enterprise only where explicitly stated; add_ons=Customer provider accounts or separately operated compatible gateway; deployment_mode=on-premise; region=Customer-selected infrastructure country; external inference, extraction, search and support locations require separate configuration and contracts; os=not specified.

Limitations

byo_restrictions: Compatibility and tools depend on the provider protocol and model. The sources do not promise identical functionality across all BYO endpoints.

own_api_keys Can the customer use its own provider API keys? [supported]: Administrators supply customer provider keys in Connections. Sources: open-webui:open-webui:openai, open-webui:open-webui:compat.
own_cloud_contract Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [supported]: Azure OpenAI is documented using the customer Azure endpoint, deployment names and API key. Bedrock is also documented through a compatible route; Vertex contract behavior was not separately verified. Sources: open-webui:open-webui:openai, open-webui:open-webui:compat.
custom_endpoint Can an admin add any OpenAI-compatible endpoint? [supported]: Administrators can set an OpenAI-compatible base URL and credentials. Sources: open-webui:open-webui:compat.
byo_pricing Does BYO change the licence price? [supported]: Branding-intact standard use is free; external provider bills and optional Enterprise rights are separate. Sources: open-webui:open-webui:enterprise.
byo_restrictions Which features stop working with BYO? [partial]: Compatibility and tools depend on the provider protocol and model. The sources do not promise identical functionality across all BYO endpoints. Sources: open-webui:open-webui:compat, open-webui:open-webui:models.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:openai, open-webui:open-webui:compat, open-webui:open-webui:enterprise, open-webui:open-webui:models.

MOD-04 Local and self-hosted models

Judgment rule: Record support for models running in the customer's environment (vLLM, Ollama, TGI or similar) and which features work with them: chat, RAG, tools, embeddings. Distinguish a documented, supported route from a generic endpoint that happens to work.

Dust

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Open WebUI

Agent cross-checked Support: partial

Ollama, llama.cpp and vLLM are documented local inference routes; local retrieval requires local embedding and extraction services.

Limitations

feature_parity: Local chat and RAG are possible. Tool reliability depends on model support, and online search, remote providers or cloud OCR require network access. No parity fixture was run.
vendor_hosted_open_models: Does the vendor host open-weight models in EU/CH? No first-party commitment to vendor-operated open-weight inference in EU or Switzerland was established in the deployment and provider guides.

self_hosted_chat Can chat use a customer-hosted model? [supported]: Chat can use customer-operated Ollama, llama.cpp or vLLM endpoints. Sources: open-webui:open-webui:provider.
self_hosted_embeddings Can retrieval use customer-hosted embeddings? [supported]: Retrieval can use local embedding models; the offline guide requires these assets to be downloaded before disconnecting. Sources: open-webui:open-webui:rag, open-webui:open-webui:offline.
feature_parity Which features fail with self-hosted models? [partial]: Local chat and RAG are possible. Tool reliability depends on model support, and online search, remote providers or cloud OCR require network access. No parity fixture was run. Sources: open-webui:open-webui:offline, open-webui:open-webui:memory.
vendor_hosted_open_models Does the vendor host open-weight models in EU/CH? [unknown]: vendor_hosted_open_models: Does the vendor host open-weight models in EU/CH? No first-party commitment to vendor-operated open-weight inference in EU or Switzerland was established in the deployment and provider guides.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:provider, open-webui:open-webui:rag, open-webui:open-webui:offline, open-webui:open-webui:memory.

MOD-05 Model control and usage limits

Judgment rule: Record admin allow-lists per group, default models, restrictions on which models may see which data, and per-user rate or fair-use limits. Test one restriction with two users in different groups. Record limits as enforced stops, warnings or undocumented fair use.

Dust

Agent cross-checked Support: partial

Admins cap models by workspace, group and member, with explicit published-agent exceptions and credit limits.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

No two-user enforcement test. Published agents can run above member tiers if the separate admin setting permits it.

model_allowlist_by_group Can admins limit models per group? [supported]: Model access ceilings apply to the workspace, groups or individuals and cover reasoning efforts as well as auto selections. Sources: dust:dust:tiers.
data_bound_models Can admins restrict which models receive connector or knowledge content? [partial]: EU-only mode restricts all active agents and pickers to EU-hosted models. Spaces bound knowledge and agent access; arbitrary per-data-class model rules were not established. Sources: dust:dust:eu-models, dust:dust:spaces.
default_model Can admins set the default model? [supported]: Builders configure an agent default, which may be exact or Basic/Standard/Premium. Composer changes do not edit it for others. Sources: dust:dust:models.
user_limits What per-user message or token limits apply, and are they published? [supported]: Free seats have 500 lifetime credits, Pro 8,000/month and Max 40,000/month, plus applicable shared-pool rules and member spend limits. Sources: dust:dust:credits, dust:dust:credit-management.
limit_behaviour What happens when a limit is reached? [supported]: Members block when applicable sources/caps are exhausted. A message begun under a cap can finish above it; new messages then block. A separate root-task checkpoint can pause at 600 AWU. Sources: dust:dust:credit-management, dust:dust:credits.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:tiers, dust:dust:eu-models, dust:dust:spaces, dust:dust:models, dust:dust:credits, dust:dust:credit-management.

Open WebUI

Agent cross-checked Support: partial

User/group model grants are documented. Optional custom filters can limit request rates; built-in recurring token/message quotas and monetary budgets remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=New extension/locale findings inspected at v0.12.4 / 33c1978d5bad52a31df75ea55143025dfad18d16; earlier accepted documented facts retained; plan=Standard self-hosted with original branding intact; Enterprise only where explicitly stated; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure country; external inference, extraction, search and support locations require separate configuration and contracts; os=not specified.

Limitations

data_bound_models: Knowledge attached to a model scopes its retrieval, while user/resource grants control access. This does not establish a hard policy binding each source to an allowed outbound provider.
user_limits: What per-user message or token limits apply, and are they published? No configured quota or bounded two-user enforcement test was run; budget controls remain in progress on the public roadmap.
limit_behaviour: What happens when a limit is reached? No configured quota or bounded two-user enforcement test was run; budget controls remain in progress on the public roadmap.

model_allowlist_by_group Can admins limit models per group? [supported]: Private model grants can be assigned to users and groups. Permissions accumulate, so a second group may grant access. Sources: open-webui:open-webui:groups.
data_bound_models Can admins restrict which models receive connector or knowledge content? [partial]: Knowledge attached to a model scopes its retrieval, while user/resource grants control access. This does not establish a hard policy binding each source to an allowed outbound provider. Sources: open-webui:open-webui:knowledge, open-webui:open-webui:privacy.
default_model Can admins set the default model? [supported]: The groups guide documents default models per group. Sources: open-webui:open-webui:groups.
user_limits What per-user message or token limits apply, and are they published? [partial]: An optional official Filter example implements configurable requests per user per minute. It is customer-installed code with process-local counters, not an enabled recurring message/token allowance or monetary budget. No configured deployment was tested. Sources: open-webui:open-webui:r4-rate-limit-example, open-webui:open-webui:r4-filter-implementation.
limit_behaviour What happens when a limit is reached? [partial]: The optional rate-limit example rejects an inlet request by raising an exception at its per-minute threshold; the inspected backend propagates inlet failures. Distributed enforcement, persistent quota balances and monetary overshoot behavior remain unverified. Sources: open-webui:open-webui:r4-rate-limit-example, open-webui:open-webui:r4-filter-implementation.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: open-webui:open-webui:groups, open-webui:open-webui:knowledge, open-webui:open-webui:privacy, open-webui:open-webui:r4-rate-limit-example, open-webui:open-webui:r4-filter-implementation.

Company knowledge

KNOW-01 Files in chat

Judgment rule: Record supported formats, size and count limits, scanned-PDF OCR, tables and spreadsheets, images inside documents, and whether a file is read in full or retrieved in chunks. Upload the shared fixture set (long German PDF, scanned contract, Excel with formulas, PowerPoint) and record failures.

Dust

Agent cross-checked Support: partial

Conversation files and code/OCR handling are documented; conflicting effective upload caps are explicitly unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

No common PDF/scan/Excel/PowerPoint fixture run.
Do not use either disputed cap set as the effective Business upload limit.

formats Which formats are accepted? [supported]: Conversation uploads accept documents/PDF, text/code, Excel/CSV/TSV, images and supported audio. Direct video uploads are explicitly excluded by the limits FAQ. Sources: dust:dust:files, dust:dust:file-limits.
limits What size and count limits apply per file and chat? [unknown]: Effective image/audio/tabular maximums and file counts are unknown: Conversation Files lists5/25/50MB while File size limits lists20/100/350MB. Both mention50MB general data files, but neither resolves the actual current per-plan upload route. No logged-in upload test was performed.
ocr Are scanned PDFs read? [partial]: Computer documents OCR for English, French and mixed scans with page-level caveats. Drive connector itself ignores image-only files; upload to a conversation is the documented route. Sources: dust:dust:computer, dust:dust:drive.
spreadsheets Are Excel tables read with structure intact? [partial]: Computer can read, calculate and edit uploaded Excel with code. Formula/style preservation must be checked; no fixture fidelity result is available. Sources: dust:dust:computer.
full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [partial]: Conversation uploads are not indexed in workspace sources. Computer can inspect full files, while knowledge search retrieves relevant context; complete chunk visibility was not verified. Sources: dust:dust:files, dust:dust:computer, dust:dust:search.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:files, dust:dust:file-limits, dust:dust:computer, dust:dust:drive, dust:dust:search.

Open WebUI

Agent cross-checked Support: partial

Documents can be attached and parsed for RAG or full-context injection. Scans depend on extraction configuration; spreadsheet fidelity was not tested.

Limitations

formats: PDF and common text/Office documents are documented; parser choice controls formats. Temporary browser-only extraction has DOCX limitations.
ocr: Scanned PDFs can use a configured OCR-capable engine. No scanned fixture was tested.
spreadsheets: Are Excel tables read with structure intact? The shared Excel/formula, scanned contract and long-document fixtures were not uploaded, so structure preservation and observed failures are unknown.

formats Which formats are accepted? [partial]: PDF and common text/Office documents are documented; parser choice controls formats. Temporary browser-only extraction has DOCX limitations. Sources: open-webui:open-webui:extraction, open-webui:open-webui:rag.
limits What size and count limits apply per file and chat? [supported]: Administrators configure maximum document MB, upload count and allowed extensions with RAG_FILE_MAX_SIZE, RAG_FILE_MAX_COUNT and RAG_ALLOWED_FILE_EXTENSIONS; these are instance settings rather than a universal vendor allowance. Sources: open-webui:open-webui:env.
ocr Are scanned PDFs read? [partial]: Scanned PDFs can use a configured OCR-capable engine. No scanned fixture was tested. Sources: open-webui:open-webui:extraction.
spreadsheets Are Excel tables read with structure intact? [unknown]: spreadsheets: Are Excel tables read with structure intact? The shared Excel/formula, scanned contract and long-document fixtures were not uploaded, so structure preservation and observed failures are unknown.
full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [supported]: Users can select focused chunk retrieval or entire-document context; attached model knowledge has mode-specific behavior described in the guide. Sources: open-webui:open-webui:knowledge, open-webui:open-webui:rag.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:extraction, open-webui:open-webui:rag, open-webui:open-webui:env, open-webui:open-webui:knowledge.

KNOW-02 Knowledge bases and shared collections

Judgment rule: Record curated document collections that persist across chats, who can create and share them, size limits, and how they attach to assistants. Distinguish personal, group and organisation-wide scope.

Dust

Agent cross-checked Support: partial

Spaces persist shared knowledge and bind it to agent tools.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

persistent_collections Can users keep document collections across chats? [supported]: Open and restricted Spaces retain connected sources, folders and other data across conversations. Sources: dust:dust:spaces.
sharing_scope Can collections be shared with users, groups or the whole organisation? [supported]: Open Spaces are workspace-wide; restricted Spaces have explicit members or provisioned groups. Sources: dust:dust:spaces.
size_limits What are the collection limits? [partial]: Business supports five Spaces and Enterprise 100. Complete per-Space storage/document quotas were not established. Sources: dust:dust:spaces.
assistant_binding Can collections be bound to an assistant? [supported]: An agent tool can use selected Space data; Space membership governs agent visibility and use. Sources: dust:dust:spaces.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:spaces.

Open WebUI

Agent cross-checked Support: partial

Knowledge bases persist across chats and can attach to a model or conversation, with user/group/public sharing.

Limitations

size_limits: What are the collection limits? No fixed collection capacity was established; limits depend on operator configuration, storage and the selected database.

persistent_collections Can users keep document collections across chats? [supported]: Knowledge bases store reusable document collections across chats. Sources: open-webui:open-webui:knowledge.
sharing_scope Can collections be shared with users, groups or the whole organisation? [supported]: Private knowledge resources can grant read/write access to named users and groups, or be public within the instance. Sources: open-webui:open-webui:groups, open-webui:open-webui:knowledge.
size_limits What are the collection limits? [unknown]: size_limits: What are the collection limits? No fixed collection capacity was established; limits depend on operator configuration, storage and the selected database.
assistant_binding Can collections be bound to an assistant? [supported]: A model preset can bind one or more knowledge bases. Sources: open-webui:open-webui:models, open-webui:open-webui:knowledge.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:knowledge, open-webui:open-webui:groups, open-webui:open-webui:models.

KNOW-03 Enterprise connectors

Judgment rule: List each connector separately with plan, availability and setup owner: SharePoint, OneDrive, Outlook, Teams, Google Drive, Gmail, Confluence, Jira, Notion, Box, Salesforce, ServiceNow, file shares. Record whether the vendor or a third party (or the customer via MCP) provides it, and whether it needs admin consent. A connector listed on a roadmap or partner page is `announced`. An on-prem connector or gateway proves access to local data, not a self-hosted platform (DATA-02).

Dust

Agent cross-checked Support: partial

Managed content connectors coexist with MCP tools and beta imports; Microsoft content indexing is account-scoped.

Availability: generally-available · Delivery: official-integration
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business: up to3 connections and5 remote MCP servers; Enterprise: unlimited connection/MCP packaging; beta imports identified separately; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.
Managed sources, metadata/table-query connections, MCP tools and beta imports are separate routes; no all-systems managed-index promise.

microsoft_365 Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: The Microsoft connection syncs selected SharePoint drives/documents within the connecting account permissions. Teams-associated SharePoint content is described; this does not establish Outlook mail or all Teams messages as indexed sources. Sources: dust:dust:microsoft.
google_workspace Which Google sources are connected? [partial]: Drive documents, Sheets, Slides and text PDFs can sync. Gmail is separately available as an MCP tool in the credits/tool catalog, not established as the same managed content index. Sources: dust:dust:drive, dust:dust:credits.
atlassian Confluence and Jira? [partial]: Confluence indexes selected global spaces, excluding restricted pages. Jira has a beta custom import and MCP tool route; do not count the beta import as a general managed connector. Sources: dust:dust:confluence, dust:dust:jira, dust:dust:credits.
other_systems Which other business systems? [partial]: Documented routes include managed Slack/Notion/GitHub and Salesforce/Zendesk/Snowflake sources/tools. BigQuery specifically uses a dedicated-service-account table-query connection: Dust keeps metadata, not a synchronized table-content index; queries stay within the chosen BigQuery dataset location and Space admins select tables. General Business/Enterprise connection limits apply; a BigQuery-specific commercial add-on is not separately specified. Sources: dust:dust:sources, dust:dust:credits, dust:dust:r2-bigquery, dust:dust:pricing.
on_prem_sources Can on-prem file shares or databases be connected? [partial]: Admins can connect a customer-hosted MCP server at a reachable secured URL. This is tool access, not evidence of a native SMB/file-share connector or on-premises Dust deployment. Sources: dust:dust:tools.
connector_provider Who builds and maintains each connector? [supported]: Dust manages built-in connections; external MCP servers can be vendor/community/customer hosted and authenticated separately. Sources: dust:dust:permissions, dust:dust:tools.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:microsoft, dust:dust:drive, dust:dust:credits, dust:dust:confluence, dust:dust:jira, dust:dust:sources, dust:dust:r2-bigquery, dust:dust:pricing, dust:dust:tools, dust:dust:permissions.

Open WebUI

Agent cross-checked Support: partial

Native file pickers and the separately operated official oikb companion provide different connector paths, including oikb Teams and Gmail sync. Source permission preservation remains untested.

Availability: generally-available · Delivery: official-integration
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected code pinned to v0.12.3 / 91ea4e3421d1d8069f13d4a463fcb5986d94ea60; plan=Standard self-hosted with original branding intact; Enterprise only where explicitly stated; add_ons=Microsoft/Google application registration for native file pickers, Separately deployed official oikb, Open WebUI 0.9.6+ and a user API key, Source credentials: Teams tenant/client/secret; Gmail Google credentials and the optional gmail extra; deployment_mode=on-premise; region=Customer-selected infrastructure country; external inference, extraction, search and support locations require separate configuration and contracts; os=not specified.

Limitations

Teams/Gmail are oikb companion connectors, not native per-user live file pickers.
Operator setup, source credentials and source-specific consent are required; permissions after indexing/revocation were not tested.

microsoft_365 Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: Native OneDrive for Business/SharePoint pickers require delegated application permissions and admin consent. Separately, oikb lists SharePoint and Teams; Teams uses TEAMS_TENANT_ID, TEAMS_CLIENT_ID and TEAMS_CLIENT_SECRET. This is a companion sync path. Outlook, exact Teams consent scopes and source-ACL preservation were not verified. Sources: open-webui:open-webui:onedrive, open-webui:open-webui:sync-connectors-r2.
google_workspace Which Google sources are connected? [partial]: The native Drive picker imports selected files. Separately, official oikb lists Google Drive and Gmail using GOOGLE_APPLICATION_CREDENTIALS; Gmail has an optional installation extra. Mailbox delegation/consent scope and continuing source-ACL preservation were not tested. Sources: open-webui:open-webui:rag, open-webui:open-webui:sync-connectors-r2.
atlassian Confluence and Jira? [partial]: Official companion oikb lists Confluence and Jira. Its separate credentials, runtime and source-specific configuration are required; source-permission sync was not verified. Sources: open-webui:open-webui:sync.
other_systems Which other business systems? [partial]: oikb lists GitHub, Notion, Slack and S3 among its sources; these are copied-content integrations rather than native per-user live search. Sources: open-webui:open-webui:sync.
on_prem_sources Can on-prem file shares or databases be connected? [supported]: A local folder can be mirrored using directory sync or the separate oikb tool. Sources: open-webui:open-webui:knowledge, open-webui:open-webui:sync.
connector_provider Who builds and maintains each connector? [supported]: Open WebUI documents the native file pickers and maintains the official, separately installed oikb companion. MCP/OpenAPI connectors depend on their own maintainers and credentials. Sources: open-webui:open-webui:onedrive, open-webui:open-webui:rag, open-webui:open-webui:sync-connectors-r2, open-webui:open-webui:mcp.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:onedrive, open-webui:open-webui:sync-connectors-r2, open-webui:open-webui:rag, open-webui:open-webui:sync, open-webui:open-webui:knowledge, open-webui:open-webui:mcp.

KNOW-04 Permission-aware retrieval

Judgment rule: Using two test users, verify that a restricted document in the fixture tenant is never cited or summarised for the user without access, including after a permission change. Record whether permissions are enforced at query time by the source system, mirrored into an index, or not enforced. Record the propagation delay of a revocation.

Dust

Agent cross-checked Support: partial

Knowledge access is documented through connection-account scope and Dust Spaces; per-user source-ACL mirroring is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Connector access through one account is not counted as demonstrated per-user source permission preservation.

source_permissions_respected Are source permissions enforced per user? [partial]: Drive and Microsoft content available to Dust follows the connecting account and admin-selected data. Users then access agent knowledge through Space membership. Individual source ACL inheritance for each querying user was not established. Sources: dust:dust:drive, dust:dust:microsoft, dust:dust:permissions.
enforcement_point Does the source system, a mirrored index or nothing enforce them? [supported]: Managed content is synchronized under the connection identity and gated through open/restricted Spaces; personal tool credentials are a separate per-user route. Sources: dust:dust:permissions, dust:dust:credentials.
revocation_delay How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? No two-user restricted-document or revocation fixture was run. Checked connector/Space docs did not establish per-query source ACL mirrors, a source-permission revocation SLA, or Microsoft Purview-label enforcement.
admin_scope_controls Can admins exclude sites, folders or labels? [supported]: Admins choose connector folders/documents/sites and control restricted Space membership. Sources: dust:dust:spaces, dust:dust:microsoft.
sensitivity_labels Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? No two-user restricted-document or revocation fixture was run. Checked connector/Space docs did not establish per-query source ACL mirrors, a source-permission revocation SLA, or Microsoft Purview-label enforcement.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:drive, dust:dust:microsoft, dust:dust:permissions, dust:dust:credentials, dust:dust:spaces.

Open WebUI

Agent cross-checked Support: partial

Open WebUI knowledge-resource grants are documented. Enforcement of the original enterprise source permissions after copying has not passed the required test.

Limitations

source_permissions_respected: Are source permissions enforced per user? No two-user restricted-document, grant/revoke or Purview-label fixture was run. Knowledge-resource ACLs and file-picker consent do not establish continuing source permission enforcement or revocation delay.
enforcement_point: Open WebUI resource grants govern access to its knowledge bases. Microsoft delegated permission limits the picker at import time; continuing source-system checks for the copied content were not established.
revocation_delay: How quickly does a removed permission take effect? No two-user restricted-document, grant/revoke or Purview-label fixture was run. Knowledge-resource ACLs and file-picker consent do not establish continuing source permission enforcement or revocation delay.
admin_scope_controls: Admins choose knowledge grants and which collections a model uses. Source site/folder/label exclusion and label propagation need connector-specific verification.
sensitivity_labels: Are Microsoft Purview or similar labels respected? No two-user restricted-document, grant/revoke or Purview-label fixture was run. Knowledge-resource ACLs and file-picker consent do not establish continuing source permission enforcement or revocation delay.

source_permissions_respected Are source permissions enforced per user? [unknown]: source_permissions_respected: Are source permissions enforced per user? No two-user restricted-document, grant/revoke or Purview-label fixture was run. Knowledge-resource ACLs and file-picker consent do not establish continuing source permission enforcement or revocation delay.
enforcement_point Does the source system, a mirrored index or nothing enforce them? [partial]: Open WebUI resource grants govern access to its knowledge bases. Microsoft delegated permission limits the picker at import time; continuing source-system checks for the copied content were not established. Sources: open-webui:open-webui:groups, open-webui:open-webui:onedrive.
revocation_delay How quickly does a removed permission take effect? [unknown]: revocation_delay: How quickly does a removed permission take effect? No two-user restricted-document, grant/revoke or Purview-label fixture was run. Knowledge-resource ACLs and file-picker consent do not establish continuing source permission enforcement or revocation delay.
admin_scope_controls Can admins exclude sites, folders or labels? [partial]: Admins choose knowledge grants and which collections a model uses. Source site/folder/label exclusion and label propagation need connector-specific verification. Sources: open-webui:open-webui:knowledge, open-webui:open-webui:groups.
sensitivity_labels Are Microsoft Purview or similar labels respected? [unknown]: sensitivity_labels: Are Microsoft Purview or similar labels respected? No two-user restricted-document, grant/revoke or Purview-label fixture was run. Knowledge-resource ACLs and file-picker consent do not establish continuing source permission enforcement or revocation delay.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:groups, open-webui:open-webui:onedrive, open-webui:open-webui:knowledge.

KNOW-05 Freshness and sync model

Judgment rule: Record live (federated) search versus a copied index, sync interval, deletion propagation, and where the index is stored. Edit and delete one fixture document and record when answers change. A copied index adds storage location to DATA-01.

Dust

Agent cross-checked Support: partial

Managed connectors copy and synchronize content, with source-specific refresh and deletion timing.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

live_or_indexed Is content searched live or copied into an index? [supported]: Connections synchronize content into Dust; conversation uploads remain scoped to the chat. MCP tools can access live services separately. Sources: dust:dust:permissions, dust:dust:files, dust:dust:tools.
sync_interval How often does an index refresh? [supported]: Microsoft describes five-minute sync cycles; Drive says a few minutes; Confluence describes event updates plus an approximate hourly check. Sources: dust:dust:microsoft, dust:dust:drive, dust:dust:confluence.
deletion_propagation How quickly does a deleted document disappear? [partial]: Microsoft changes/deletions appear on a subsequent sync and large batches can take longer. Drive deletions occur during its sync. No measured end-to-end bound was tested. Sources: dust:dust:microsoft, dust:dust:drive.
index_location Where is indexed content stored? [partial]: Dust markets EU or US hosting; exact per-index country, cloud provider and backup location were not established. Sources: dust:dust:security.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:permissions, dust:dust:files, dust:dust:tools, dust:dust:microsoft, dust:dust:drive, dust:dust:confluence, dust:dust:security.

Open WebUI

Agent cross-checked Support: partial

Uploaded knowledge is copied into an operator-selected index. Manual directory sync or a separate daemon updates it.

Limitations

sync_interval: Directory sync runs when invoked; oikb offers scheduled/on-demand synchronization. No universal connector interval or SLA applies.
deletion_propagation: Directory sync removes files missing from the local manifest during cleanup. Elapsed propagation time was not measured.

live_or_indexed Is content searched live or copied into an index? [supported]: Uploaded documents are parsed and indexed; an experimental external-vector-source mode queries a pre-existing customer index without re-ingestion. Sources: open-webui:open-webui:rag, open-webui:open-webui:knowledge.
sync_interval How often does an index refresh? [partial]: Directory sync runs when invoked; oikb offers scheduled/on-demand synchronization. No universal connector interval or SLA applies. Sources: open-webui:open-webui:knowledge, open-webui:open-webui:sync.
deletion_propagation How quickly does a deleted document disappear? [partial]: Directory sync removes files missing from the local manifest during cleanup. Elapsed propagation time was not measured. Sources: open-webui:open-webui:knowledge.
index_location Where is indexed content stored? [supported]: The operator selects the database or external vector source and its deployment location; there is no fixed vendor region for this self-hosted scope. Sources: open-webui:open-webui:rag, open-webui:open-webui:privacy.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:rag, open-webui:open-webui:knowledge, open-webui:open-webui:sync, open-webui:open-webui:privacy.

KNOW-06 Grounding and retrieval quality

Judgment rule: Run the shared question set over the fixture corpus: factual lookups, cross-document questions, German document with an English question, a question with no answer in the corpus. Record citation presence, link accuracy, correct answers and refusals to invent. Disclose model, settings, attempt count and failures. Single runs support a case study, not a ranking.

Dust

Agent cross-checked Support: partial

Knowledge and research tools cite sources; observed retrieval quality remains unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

citations Are answers linked to specific sources? [supported]: Deep-dive documents citations to documents, web pages and data queries. Sources: dust:dust:deep.
citation_accuracy Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test.
cross_language Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test.
no_answer_behaviour Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test.
observed_accuracy How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep.

Open WebUI

Agent cross-checked Support: partial

Citations are documented; citation accuracy and multilingual retrieval outcomes are untested.

Limitations

citation_accuracy: Do the cited passages support the answer? The shared DE/FR/EN corpus and factual/no-answer question set were not run. No citation-link accuracy, cross-language result, refusal rate or numerical accuracy is claimed.
cross_language: Does a question in one language find documents in another? The shared DE/FR/EN corpus and factual/no-answer question set were not run. No citation-link accuracy, cross-language result, refusal rate or numerical accuracy is claimed.
no_answer_behaviour: Does it say when the corpus has no answer? The shared DE/FR/EN corpus and factual/no-answer question set were not run. No citation-link accuracy, cross-language result, refusal rate or numerical accuracy is claimed.
observed_accuracy: How many of the question set were answered correctly? The shared DE/FR/EN corpus and factual/no-answer question set were not run. No citation-link accuracy, cross-language result, refusal rate or numerical accuracy is claimed.

citations Are answers linked to specific sources? [supported]: RAG answers can include source references; chunk metadata may add details such as page numbers. Sources: open-webui:open-webui:rag.
citation_accuracy Do the cited passages support the answer? [unknown]: citation_accuracy: Do the cited passages support the answer? The shared DE/FR/EN corpus and factual/no-answer question set were not run. No citation-link accuracy, cross-language result, refusal rate or numerical accuracy is claimed.
cross_language Does a question in one language find documents in another? [unknown]: cross_language: Does a question in one language find documents in another? The shared DE/FR/EN corpus and factual/no-answer question set were not run. No citation-link accuracy, cross-language result, refusal rate or numerical accuracy is claimed.
no_answer_behaviour Does it say when the corpus has no answer? [unknown]: no_answer_behaviour: Does it say when the corpus has no answer? The shared DE/FR/EN corpus and factual/no-answer question set were not run. No citation-link accuracy, cross-language result, refusal rate or numerical accuracy is claimed.
observed_accuracy How many of the question set were answered correctly? [unknown]: observed_accuracy: How many of the question set were answered correctly? The shared DE/FR/EN corpus and factual/no-answer question set were not run. No citation-link accuracy, cross-language result, refusal rate or numerical accuracy is claimed.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:rag.

KNOW-07 Memory and personal context

Judgment rule: Record personal custom instructions, cross-chat memory, project or workspace context, and user controls to view, edit, delete or disable memory. Record whether admins can disable memory organisation-wide.

Dust

Agent cross-checked Support: partial

Agent-specific private memory persists across chats and can be viewed or deleted.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

custom_instructions Can users set persistent instructions? [partial]: Agent instructions persist in the agent configuration and saved memory can contain user preferences; a separate personal global-instructions setting was not established. Sources: dust:dust:builder, dust:dust:memory.
cross_chat_memory Does the product remember facts across chats? [supported]: The Memory tool retains user-specific information across conversations per agent. Sources: dust:dust:memory.
user_memory_controls Can users view, edit and delete memories? [partial]: Users can view and delete agent memories, which persist until deletion. Direct editing or a global personal off switch was not established. Sources: dust:dust:memory.
admin_memory_controls Can admins turn memory off? [unknown]: Can admins turn memory off? The Agent Memory and governance guides were checked; an admin-wide switch to disable all memory was not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:memory.

Open WebUI

Agent cross-checked Support: partial

Users can manage persistent memory and admins can disable or group-restrict it.

Limitations

custom_instructions: Model presets provide persistent system instructions and users can save instructions as memory. A separate personal-instructions setting was not inspected here.

custom_instructions Can users set persistent instructions? [partial]: Model presets provide persistent system instructions and users can save instructions as memory. A separate personal-instructions setting was not inspected here. Sources: open-webui:open-webui:models, open-webui:open-webui:memory.
cross_chat_memory Does the product remember facts across chats? [supported]: User-scoped memories carry facts and preferences between conversations. Sources: open-webui:open-webui:memory.
user_memory_controls Can users view, edit and delete memories? [supported]: Settings permits adding, editing and deleting memories. Sources: open-webui:open-webui:memory.
admin_memory_controls Can admins turn memory off? [supported]: Global and per-group switches disable memory access and server-side context use. Sources: open-webui:open-webui:memory.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:models, open-webui:open-webui:memory.

Assistants and agents

AGT-01 Custom assistants

Judgment rule: Record creation of assistants with instructions, model, knowledge and tools; who can create; sharing scope; versioning; and an internal catalogue or directory. Build one HR policy assistant on the fixture and share it with one group. Prompt templates and a prompt library are recorded here.

Dust

Agent cross-checked Support: partial

Custom agents have instructions, models, knowledge and tools with group-governed creation and sharing.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

create_assistants Can users create assistants with instructions, knowledge and tools? [supported]: Agent Builder configures instructions, models, knowledge and tools. Sources: dust:dust:builder.
creator_permissions Can admins limit who creates them? [supported]: Create/publish agent and skill permissions can be Everyone, Groups or Admin only. Sources: dust:dust:governance.
sharing_scope Can assistants be shared with users, groups or everyone? [supported]: Agents and their knowledge access are controlled by sharing and Space memberships; group governance regulates publishing. Sources: dust:dust:builder, dust:dust:spaces, dust:dust:governance.
catalogue Is there an internal assistant directory? [partial]: Published/shared agents and default agents are discoverable in the workspace; exact catalog configuration was not observed. Sources: dust:dust:builder, dust:dust:models.
prompt_library Are shared prompt templates available? [partial]: Reusable agents and skills package instructions, knowledge and tools. A separate legacy prompt-library feature is not assumed. Sources: dust:dust:governance, dust:dust:builder.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:governance, dust:dust:spaces, dust:dust:models.

Open WebUI

Agent cross-checked Support: supported

Model presets are reusable assistants combining instructions, a base model, knowledge and tools.

create_assistants Can users create assistants with instructions, knowledge and tools? [supported]: The Models workspace creates presets with instructions, knowledge, tools, skills and parameters. Sources: open-webui:open-webui:models.
creator_permissions Can admins limit who creates them? [supported]: Workspace permission toggles control who can create resources. Sources: open-webui:open-webui:permissions.
sharing_scope Can assistants be shared with users, groups or everyone? [supported]: Model grants may target users, groups or public instance visibility. Sources: open-webui:open-webui:groups, open-webui:open-webui:models.
catalogue Is there an internal assistant directory? [supported]: The Models workspace lists available presets and model selectors expose those the user can access. Sources: open-webui:open-webui:models.
prompt_library Are shared prompt templates available? [supported]: Workspace prompt permissions cover creating and sharing reusable prompt resources. Sources: open-webui:open-webui:permissions.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:models, open-webui:open-webui:permissions, open-webui:open-webui:groups.

AGT-02 Tools, actions and MCP

Judgment rule: Record built-in tools, custom actions (OpenAPI), MCP client support (local and remote servers), authentication model per tool (shared service account or per-user OAuth), and admin approval of tools. Verify one external-tool call and its access boundary.

Dust

Agent cross-checked Support: partial

Dust supports built-in tools, customer MCP servers and personal or shared credentials.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

No external-tool call or access-boundary fixture was run.

builtin_tools Which tools are built in? [supported]: Documented tools include knowledge search, table queries, web search, Computer, images, speech and agent orchestration. Sources: dust:dust:credits, dust:dust:computer.
custom_actions Can admins add API actions? [supported]: Admins can connect customer-written MCP tools over secured publicly reachable URLs. Sources: dust:dust:tools.
mcp_client Can it use remote MCP servers, and with what admin control? [supported]: Admins add remote MCP servers with automatic/static OAuth or bearer-token authentication and can restrict tools to skills. Sources: dust:dust:tools.
tool_auth Do tools act as the user or as a shared account? [supported]: Shared credentials act as one service account; personal credentials use each user OAuth after initial admin setup. Sources: dust:dust:credentials.
tool_approval Can admins approve or block tools, and can users confirm actions before they run? [partial]: Computer network domains can require user approval; dated connector releases describe approval for writes. A universal confirmation rule for every tool and unattended trigger was not established. Sources: dust:dust:computer, dust:dust:changelog.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:credits, dust:dust:computer, dust:dust:tools, dust:dust:credentials, dust:dust:changelog.

Open WebUI

Agent cross-checked Support: partial

Native/custom tools and MCP are documented. The optional interactive Tool Permissions approval mode is experimental and off by default; automations and channel replies bypass it.

Availability: beta · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Current Tools/MCP documentation retrieved 2026-10-21; beta availability qualifies the optional experimental approval mode, not all tool integrations; plan=Standard self-hosted with original branding intact; Enterprise only where explicitly stated; add_ons=Optional separately operated MCP/OpenAPI tool servers or stdio bridge; deployment_mode=on-premise; region=Customer-selected infrastructure country; external inference, extraction, search and support locations require separate configuration and contracts; os=not specified.

Limitations

The row uses beta for the experimental approval subfeature; ordinary tool integrations are documented separately.
Approval is opt-in for interactive chats and is bypassed in automations/channel replies; no mandatory side-effect policy was established.

builtin_tools Which tools are built in? [supported]: Knowledge, memory, web and other built-in tool categories are configured per model. Sources: open-webui:open-webui:models.
custom_actions Can admins add API actions? [supported]: Admins can install Python tools or connect OpenAPI tool servers. Sources: open-webui:open-webui:tools.
mcp_client Can it use remote MCP servers, and with what admin control? [supported]: The dedicated current guide documents admin-configured Streamable HTTP MCP. Local stdio requires a separately deployed bridge such as mcpo. Sources: open-webui:open-webui:mcp, open-webui:open-webui:tools.
tool_auth Do tools act as the user or as a shared account? [supported]: Configured modes include bearer credentials and user OAuth/OAuth 2.1; the resulting access depends on the server and granted scopes. Sources: open-webui:open-webui:mcp.
tool_approval Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins control tool access and may enable experimental Tool Permissions (off by default). Interactive users can select Ask for approval with sequential Allow/Deny prompts; Full access remains the default. Automations and channel replies always use full access. A mandatory policy for every side effect and an external-call boundary fixture were not verified. Sources: open-webui:open-webui:approvals-r2, open-webui:open-webui:groups.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:models, open-webui:open-webui:tools, open-webui:open-webui:mcp, open-webui:open-webui:approvals-r2, open-webui:open-webui:groups.

AGT-03 Web search and deep research

Judgment rule: Record web search on/off control per organisation and group, search provider, citation of web sources, deep or multi-step research, and whether queries leave the residency boundary. Admins of regulated companies often need web search off.

Dust

Agent cross-checked Support: partial

Agents can search the web and run multi-step Deep-dive research.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

web_search Is web search available? [supported]: Web Search & Browse runs Google queries and reads result pages. Sources: dust:dust:web.
admin_toggle Can admins disable it per organisation or group? [partial]: Web tools are selected in agent configuration; default Deep-dive can be disabled by admins. A universal per-group web-off rule was not established. Sources: dust:dust:web, dust:dust:deep.
search_provider Which search provider handles queries, and where? [partial]: The guide calls the search a Google query. The intermediary provider and countries handling queries/crawling were not established. Sources: dust:dust:web.
deep_research Is multi-step research with a report available? [supported]: Deep-dive plans, spawns parallel specialists and produces a research report. It searches Company Data and cannot use Table Query. Sources: dust:dust:deep.
web_citations Are web sources cited? [supported]: Deep-dive promises citations to web and company sources. Sources: dust:dust:deep.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:web, dust:dust:deep.

Open WebUI

Agent cross-checked Support: partial

Search and multi-step page research are documented and require an external search provider or local metasearch deployment.

Limitations

search_provider: Provider choice includes external search services and self-operated options. The actual provider region and query processing contract depend on the chosen service.
deep_research: Native function calling can perform repeated search and URL fetching. No bounded research-report task was exercised.

web_search Is web search available? [supported]: Admins configure web search and users can enable it in a chat. Sources: open-webui:open-webui:web.
admin_toggle Can admins disable it per organisation or group? [supported]: Feature permissions grant web search per group; global configuration can turn it off. Sources: open-webui:open-webui:permissions, open-webui:open-webui:web.
search_provider Which search provider handles queries, and where? [partial]: Provider choice includes external search services and self-operated options. The actual provider region and query processing contract depend on the chosen service. Sources: open-webui:open-webui:web, open-webui:open-webui:offline.
deep_research Is multi-step research with a report available? [partial]: Native function calling can perform repeated search and URL fetching. No bounded research-report task was exercised. Sources: open-webui:open-webui:agent-search.
web_citations Are web sources cited? [supported]: Retrieved web sources are exposed as conversation references/citations. Sources: open-webui:open-webui:agent-search.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:web, open-webui:open-webui:permissions, open-webui:open-webui:offline, open-webui:open-webui:agent-search.

AGT-04 Workflows and automation

Judgment rule: Record no-code or low-code workflows, scheduled prompts, triggers from email, forms or business systems, and multi-step chains. Name where they run and who can build them. A shared prompt template is not a workflow.

Dust

Agent cross-checked Support: partial

Agents support schedules and webhook automation with admin-created event sources.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

workflow_builder Is there a workflow or chain builder? [partial]: Agents orchestrate tools and sub-agents; external n8n and trigger workflows are documented. A separate visual multi-step chain canvas was not established. Sources: dust:dust:deep, dust:dust:triggers, dust:dust:changelog.
scheduled_tasks Can prompts or assistants run on a schedule? [supported]: Agents can run on recurring schedules. Sources: dust:dust:schedules.
event_triggers Can external events start a workflow? [supported]: Built-in webhook sources include GitHub, Jira, Linear, Zendesk and Fathom; signed custom webhooks are supported. Sources: dust:dust:webhooks.
builder_audience Is building aimed at business users, IT or developers? [supported]: Admins connect event sources; builders/members attach filtered triggers in Agent Builder and can use natural-language trigger creation through Dust Default. Sources: dust:dust:webhooks, dust:dust:changelog.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep, dust:dust:triggers, dust:dust:changelog, dust:dust:schedules, dust:dust:webhooks.

Open WebUI

Agent cross-checked Support: partial

Recurring prompts execute on the operator’s server. Developer extensions can add chains; a business workflow builder was not established.

Limitations

workflow_builder: Is there a workflow or chain builder? The automation, tool and webhook documentation did not establish a complete business workflow builder or incoming email/form event trigger contract.
event_triggers: Can external events start a workflow? The automation, tool and webhook documentation did not establish a complete business workflow builder or incoming email/form event trigger contract.
builder_audience: Schedules use a user-facing editor; custom Python tools and integrations require technical operators. No general no-code multi-system workflow designer was verified.

workflow_builder Is there a workflow or chain builder? [unknown]: workflow_builder: Is there a workflow or chain builder? The automation, tool and webhook documentation did not establish a complete business workflow builder or incoming email/form event trigger contract.
scheduled_tasks Can prompts or assistants run on a schedule? [supported]: Automations support hourly/daily/weekly/monthly and RRULE schedules, manual runs, pause and execution history. Sources: open-webui:open-webui:automation.
event_triggers Can external events start a workflow? [partial]: A token-validated channel webhook publishes a message-created event that configured Python Event functions can handle. Developers must supply the downstream workflow logic; an incoming email/form connector or no-code multi-system workflow contract was not established. Sources: open-webui:open-webui:r4-incoming-channel-webhook, open-webui:open-webui:r4-event-dispatch.
builder_audience Is building aimed at business users, IT or developers? [partial]: Schedules use a user-facing editor; custom Python tools and integrations require technical operators. No general no-code multi-system workflow designer was verified. Sources: open-webui:open-webui:automation, open-webui:open-webui:tools.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: open-webui:open-webui:automation, open-webui:open-webui:tools, open-webui:open-webui:r4-incoming-channel-webhook, open-webui:open-webui:r4-event-dispatch.

AGT-05 Agentic task execution

Judgment rule: Record an agent mode that plans and carries out multi-step tasks with tools (browser, files, connectors), with visible steps, user confirmation of side effects and stop control. Run one fixture task (gather three documents, draft a summary, propose an email). Record interventions and what ran. A final claim of success is not proof.

Dust

Agent cross-checked Support: partial

Multi-step agent work and visible Deep-dive progress are documented; safety controls depend on tool and trigger.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

No shared gather/documents/email fixture or side-effect audit was run.

agent_mode Is there an agent mode for multi-step tasks? [supported]: Deep-dive plans, delegates and synthesizes, and Computer can execute deterministic file/code work. Sources: dust:dust:deep, dust:dust:computer.
visible_steps Are steps and tool calls shown? [supported]: Deep-dive documentation shows reasoning and sub-agent progress in real time. Sources: dust:dust:deep.
side_effect_confirmation Must the user confirm actions with side effects? [partial]: Computer domains may require user approval and selected connector write actions ask for approval. Pods agents can also act without a human, so universal write confirmation is not claimed. Sources: dust:dust:computer, dust:dust:changelog, dust:dust:pods.
stop_control Can the user stop a running task? [partial]: The 600-AWU root-task checkpoint offers Stop or Continue. A complete general stop/rollback behavior was not tested. Sources: dust:dust:credits.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep, dust:dust:computer, dust:dust:changelog, dust:dust:pods, dust:dust:credits.

Open WebUI

Agent cross-checked Support: partial

Native tool calls and optional Open Terminal support agent tasks. Interactive tool approval is experimental and off by default, and never gates scheduled automations or channel replies.

Availability: beta · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Current Tools/Open Terminal documentation retrieved 2026-10-21; beta availability qualifies optional experimental approvals; plan=Standard self-hosted with original branding intact; Enterprise only where explicitly stated; add_ons=Optional separately deployed Open Terminal; Terminals orchestration is a separate component with unverified pinned licence terms; deployment_mode=on-premise; region=Customer-selected infrastructure country; external inference, extraction, search and support locations require separate configuration and contracts; os=not specified.

Limitations

Beta availability refers to optional experimental approvals; the documented native tool mode is separate.
Automations and channel replies always use full access.
No gather-documents, draft-summary and propose-email fixture or background cancellation test was run.

agent_mode Is there an agent mode for multi-step tasks? [supported]: Tool-capable models can use knowledge and external tools; separately connected Open Terminal adds file and command execution. Sources: open-webui:open-webui:models, open-webui:open-webui:terminal.
visible_steps Are steps and tool calls shown? [supported]: Interactive tool calls display their results and, when experimental Ask for approval is enabled, pending/allowed/denied state. Sources: open-webui:open-webui:approvals-r2.
side_effect_confirmation Must the user confirm actions with side effects? [partial]: Experimental Tool Permissions is disabled by default and users must select Ask for approval. Full access executes immediately; automations and channel replies always bypass approval. The documented control is not a mandatory confirmation policy for every side effect. Sources: open-webui:open-webui:approvals-r2.
stop_control Can the user stop a running task? [partial]: In an interactive reply waiting for approval, Stop finalizes the reply and denies pending calls. This is a pending-call control; cancellation of background tasks and effects already executed was not tested. Sources: open-webui:open-webui:approvals-r2.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:models, open-webui:open-webui:terminal, open-webui:open-webui:approvals-r2.

AGT-06 Programmable access

Judgment rule: Record a public API for chat, assistants and knowledge, SDKs, API authentication, rate limits and whether API use counts against the same governance (audit, budgets, model restrictions). Being an MCP client is different from exposing the product over MCP.

Dust

Agent cross-checked Support: supported

Dust offers conversation/knowledge APIs, enforceable API-key caps and OAuth MCP access.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust APIs and MCP server; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business conversation API; Enterprise adds Data Source API per pricing; MCP subject to workspace enablement; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

chat_api Is there an API for chat and assistants? [supported]: Documented APIs retrieve/create conversations and messages with scoped API keys. Sources: dust:dust:get-conversation, dust:dust:api-keys.
knowledge_api Can documents be loaded through an API? [supported]: The data-source API upserts documents into scoped data sources. Sources: dust:dust:upsert.
api_governance Do audit, budgets and model rules apply to API use? [supported]: Per-key caps reject further API usage at the limit. Model overrides obey workspace/tier rules; programmatic usage uses the workspace pool and does not count toward beta pooled group budgets. Sources: dust:dust:api-keys, dust:dust:models, dust:dust:credit-management.
mcp_server Does the product expose itself to other agents over MCP? [supported]: Global and EU MCP URLs expose authorized Dust knowledge, conversations, agents, files and Pods via OAuth; admins can disable access and control redirects. Sources: dust:dust:mcp-server.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:get-conversation, dust:dust:api-keys, dust:dust:upsert, dust:dust:models, dust:dust:credit-management, dust:dust:mcp-server.

Open WebUI

Agent cross-checked Support: partial

Authenticated APIs cover chat, models and knowledge ingestion; product RBAC applies to API users.

Limitations

api_governance: API users use their account permissions; optional audit capture can log requests. Enforced spend budgets and full API/UI parity were not demonstrated.
mcp_server: Does the product expose itself to other agents over MCP? No supported native MCP server exposing the whole product was established in the API and MCP-client guides.

chat_api Is there an API for chat and assistants? [supported]: OpenAI-compatible chat completion and model management endpoints accept API keys or session JWTs. Sources: open-webui:open-webui:api.
knowledge_api Can documents be loaded through an API? [supported]: File upload and knowledge attachment are documented APIs. Sources: open-webui:open-webui:api, open-webui:open-webui:knowledge.
api_governance Do audit, budgets and model rules apply to API use? [partial]: API users use their account permissions; optional audit capture can log requests. Enforced spend budgets and full API/UI parity were not demonstrated. Sources: open-webui:open-webui:api, open-webui:open-webui:hardening.
mcp_server Does the product expose itself to other agents over MCP? [unknown]: mcp_server: Does the product expose itself to other agents over MCP? No supported native MCP server exposing the whole product was established in the API and MCP-client guides.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:api, open-webui:open-webui:knowledge, open-webui:open-webui:hardening.

Daily work

WORK-01 Clients and access points

Judgment rule: List web, desktop (Windows, macOS), iOS, Android, mobile browser and browser extension separately. For each, record login with company SSO, feature gaps against web, and MDM/Intune deployability. An installable app is different from a mobile website.

Dust

Agent cross-checked Support: partial

Web, browser extension and Teams access are documented; native desktop/mobile availability remains unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust browser extension; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

web Is a full web client available? [supported]: Dust provides the hosted web workspace, including the EU region. Sources: dust:dust:pricing, dust:dust:models.
desktop_apps Windows and macOS apps? [unknown]: Windows and macOS apps? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established.
mobile_apps iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established.
browser_extension Is there a browser extension or sidebar? [supported]: The extension guide covers Chrome, Firefox and Chromium browsers. Sources: dust:dust:browser.
managed_deployment Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established.
client_feature_gaps Which features are missing on mobile? [unknown]: Which features are missing on mobile? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:models, dust:dust:browser.

Open WebUI

Agent cross-checked Support: partial

The web/PWA client is complemented by a separate native Desktop distribution for macOS, Windows and Linux. Desktop is explicitly Early Alpha; SSO/MDM and cross-client parity were not tested.

Availability: beta · Delivery: native
Scope: surfaces=Customer-operated web application and server, Open WebUI Desktop native distribution (Early Alpha); version=Web/PWA documentation retrieved 2026-10-21; Desktop v0.0.20 / 601137c5dec2967cfe173a6bf071fbbb460852be (released 2026-05-06, labelled Early Alpha); plan=Customer-operated web/PWA plus the separately packaged Open WebUI Desktop distribution; production Quick Start recommends Docker or Python; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure country; external inference, extraction, search and support locations require separate configuration and contracts; os=Windows, macOS, Linux, iOS (PWA), Android (PWA).

Limitations

Beta availability reflects the Early Alpha desktop distribution; the browser/PWA route is separate.
Native mobile clients, corporate SSO, MDM/Intune deployment and client parity were not tested.

web Is a full web client available? [supported]: The deployed server supplies the full browser client; Quick Start also links the separate desktop distribution. Sources: open-webui:open-webui:desktop-quickstart-r2.
desktop_apps Windows and macOS apps? [partial]: Open WebUI Desktop v0.0.20 provides native macOS (Apple Silicon/Intel), Windows (x64/ARM64) and Linux installers. It can run locally without Docker or connect to an existing server. It is labelled Early Alpha; first launch requires internet. Enterprise SSO and managed rollout were not tested. Sources: open-webui:open-webui:desktop-readme-r2, open-webui:open-webui:desktop-release-r2, open-webui:open-webui:desktop-quickstart-r2.
mobile_apps iOS and Android apps with SSO? [partial]: Android browsers and iOS Safari can install the PWA. Native mobile app-store clients and mobile company-SSO/MDM behavior were not verified. Sources: open-webui:open-webui:pwa-r2.
browser_extension Is there a browser extension or sidebar? [unknown]: browser_extension: Is there a browser extension or sidebar? No first-party managed MDM/Intune deployment policy or Office/browser sidebar extension was established in the client guide.
managed_deployment Can IT deploy and configure clients through MDM? [unknown]: managed_deployment: Can IT deploy and configure clients through MDM? No first-party managed MDM/Intune deployment policy or Office/browser sidebar extension was established in the client guide.
client_feature_gaps Which features are missing on mobile? [partial]: PWA notifications need the app to remain open. Desktop is Early Alpha and Quick Start recommends Docker/Python for production; no desktop/mobile feature-parity or enterprise SSO matrix was verified. Sources: open-webui:open-webui:pwa-r2, open-webui:open-webui:desktop-readme-r2, open-webui:open-webui:desktop-quickstart-r2.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:desktop-quickstart-r2, open-webui:open-webui:desktop-readme-r2, open-webui:open-webui:desktop-release-r2, open-webui:open-webui:pwa-r2.

WORK-02 Office suite and Teams integration

Judgment rule: Record presence inside Word, Excel, PowerPoint, Outlook and Teams (and Google Docs, Gmail), with what the assistant can do in each: read the open document, write into it, act on mail. Record extra licences and admin consent needed. A connector that searches Office files is KNOW-03, not WORK-02.

Dust

Agent cross-checked Support: partial

An official Teams integration runs agents in Teams; document connectors do not imply Office add-ins.

Availability: generally-available · Delivery: official-integration
Scope: surfaces=Dust in Microsoft Teams; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

word_excel_powerpoint Does it work inside Word, Excel and PowerPoint? [unknown]: Does it work inside Word, Excel and PowerPoint? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately.
outlook Does it work inside Outlook? [unknown]: Does it work inside Outlook? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately.
teams Is there a Teams app or bot? [supported]: Dust in Teams has an official integration guide and admin setup. Sources: dust:dust:teams.
google_workspace_apps Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately.
licence_prerequisites Which licences or consents are needed? [partial]: The Teams guide requires integration/admin authorization in a Dust workspace. Extra Microsoft/Dust licence charges were not established. Sources: dust:dust:teams.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:teams.

Open WebUI

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

WORK-03 Translation and writing

Judgment rule: Record document translation preserving layout, the translation engine (LLM or dedicated such as DeepL), glossaries, formality control, supported languages including Swiss German conventions (no ß), and rewriting/proofreading tools. Translate the shared German contract into French and Italian and record layout and glossary results.

Dust

Agent cross-checked Support: partial

Agents can perform language work, but document-translation fidelity and controlled terminology are untested.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

document_translation Can whole documents be translated with formatting kept? [unknown]: Can whole documents be translated with formatting kept? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established.
translation_engine Which engine translates? [unknown]: Which engine translates? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established.
glossaries Are company glossaries supported? [unknown]: Are company glossaries supported? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established.
formality_and_variants Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established.
writing_tools Are dedicated rewrite and proofreading tools available? [partial]: Configurable agent instructions and Computer document editing support writing workflows; a separate dedicated proofreading product was not established. Sources: dust:dust:builder, dust:dust:computer.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:computer.

Open WebUI

Agent cross-checked Support: partial

AI editing is documented in Notes. Dedicated layout-preserving translation and glossary behavior remain unknown.

Limitations

document_translation: Can whole documents be translated with formatting kept? No DE-to-FR/IT contract translation fixture, de-CH/formality acceptance test, company glossary or layout-preserving translator was verified in the Notes and document guides.
translation_engine: Notes sends rewrite requests to the selected model. A dedicated translation service or whole-document translation workflow was not established.
glossaries: Are company glossaries supported? No DE-to-FR/IT contract translation fixture, de-CH/formality acceptance test, company glossary or layout-preserving translator was verified in the Notes and document guides.
formality_and_variants: Can formality and regional variants (de-CH) be set? No DE-to-FR/IT contract translation fixture, de-CH/formality acceptance test, company glossary or layout-preserving translator was verified in the Notes and document guides.

document_translation Can whole documents be translated with formatting kept? [unknown]: document_translation: Can whole documents be translated with formatting kept? No DE-to-FR/IT contract translation fixture, de-CH/formality acceptance test, company glossary or layout-preserving translator was verified in the Notes and document guides.
translation_engine Which engine translates? [partial]: Notes sends rewrite requests to the selected model. A dedicated translation service or whole-document translation workflow was not established. Sources: open-webui:open-webui:notes.
glossaries Are company glossaries supported? [unknown]: glossaries: Are company glossaries supported? No DE-to-FR/IT contract translation fixture, de-CH/formality acceptance test, company glossary or layout-preserving translator was verified in the Notes and document guides.
formality_and_variants Can formality and regional variants (de-CH) be set? [unknown]: formality_and_variants: Can formality and regional variants (de-CH) be set? No DE-to-FR/IT contract translation fixture, de-CH/formality acceptance test, company glossary or layout-preserving translator was verified in the Notes and document guides.
writing_tools Are dedicated rewrite and proofreading tools available? [supported]: The Notes editor supports AI rewriting and improving selected text. Sources: open-webui:open-webui:notes.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:notes.

WORK-04 Image generation and editing

Judgment rule: Record available image models, editing (inpainting, reference images), admin control and per-image cost visibility, and licence or usage terms for generated images.

Dust

Agent cross-checked Support: partial

Image tools use reference images and parallel generation; exact model and output-right terms need further evidence.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

image_generation Can users generate images, with which models? [partial]: Image Generation is a configurable agent capability with SynthID-marked output. The exact current model identifier is not named in the checked guide. Sources: dust:dust:images.
image_editing Can users edit uploaded images? [partial]: Uploaded and prior generated images can be used as references, with up to 14 references. Precise inpainting/masking controls were not established. Sources: dust:dust:images.
admin_control Can admins restrict image generation? [partial]: Builders enable image tools in an agent, while group governance controls who creates/publishes agents. A separate organization/group image-off switch was not established. Sources: dust:dust:images, dust:dust:governance.
usage_terms What usage rights apply to output? [unknown]: What usage rights apply to output? The image guide and legal entry points were checked. Current model identifier, per-image tariff and contractual output usage rights were not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:images, dust:dust:governance.

Open WebUI

Agent cross-checked Support: partial

Configured image engines generate and edit uploaded images, subject to feature permissions.

Limitations

usage_terms: What usage rights apply to output? Output rights and actual per-image costs depend on the chosen image service and were not established as a single Open WebUI entitlement.

image_generation Can users generate images, with which models? [supported]: OpenAI, Gemini, ComfyUI and AUTOMATIC1111 are documented engine routes; exact models are operator-configured. Sources: open-webui:open-webui:images.
image_editing Can users edit uploaded images? [supported]: The usage guide documents uploaded-image edits and multi-image compositing with an enabled editing engine. Sources: open-webui:open-webui:image-usage.
admin_control Can admins restrict image generation? [supported]: Global image configuration, feature permission and model capability govern availability. Sources: open-webui:open-webui:image-usage.
usage_terms What usage rights apply to output? [unknown]: usage_terms: What usage rights apply to output? Output rights and actual per-image costs depend on the chosen image service and were not established as a single Open WebUI entitlement.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:images, open-webui:open-webui:image-usage.

WORK-05 Voice and meetings

Judgment rule: Record dictation, read-aloud, live voice conversation, meeting transcription and summarisation, supported languages including Swiss German speech, and where audio is processed.

Dust

Agent cross-checked Support: partial

Speech generation and meeting-transcript integrations are documented; live voice and Swiss German recognition remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

dictation Can users dictate prompts? [unknown]: Can users dictate prompts? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established.
read_aloud Can answers be read aloud? [partial]: Speech Generator converts written text to MP3 audio with selectable voices/languages; a one-click read-aloud mode for all responses was not established. Sources: dust:dust:speech.
voice_conversation Is a live voice mode available? [unknown]: Is a live voice mode available? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established.
meeting_summaries Are meetings transcribed and summarised? [supported]: Connected Granola/Fathom/Gong/Praiz transcripts can feed summaries; private Gong transcripts are excluded. This is not a native meeting recorder claim. Sources: dust:dust:meetings.
swiss_german_speech Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:speech, dust:dust:meetings.

Open WebUI

Agent cross-checked Support: partial

Dictation, read-aloud and voice conversation use configured audio services. Swiss German recognition and a meeting workflow were not tested.

Limitations

meeting_summaries: Are meetings transcribed and summarised? No meeting-transcription fixture or Swiss German speech evaluation was run. Audio location depends on the chosen browser, local, Azure or other provider engine.
swiss_german_speech: Is Swiss German speech recognised? No meeting-transcription fixture or Swiss German speech evaluation was run. Audio location depends on the chosen browser, local, Azure or other provider engine.

dictation Can users dictate prompts? [supported]: Audio configuration supports speech-to-text for prompts. Sources: open-webui:open-webui:env.
read_aloud Can answers be read aloud? [supported]: Standard voice reads replies using the configured TTS engine, including browser options. Sources: open-webui:open-webui:voice.
voice_conversation Is a live voice mode available? [supported]: Standard STT/TTS voice mode and separately configured realtime API calls are documented. Sources: open-webui:open-webui:voice.
meeting_summaries Are meetings transcribed and summarised? [unknown]: meeting_summaries: Are meetings transcribed and summarised? No meeting-transcription fixture or Swiss German speech evaluation was run. Audio location depends on the chosen browser, local, Azure or other provider engine.
swiss_german_speech Is Swiss German speech recognised? [unknown]: swiss_german_speech: Is Swiss German speech recognised? No meeting-transcription fixture or Swiss German speech evaluation was run. Audio location depends on the chosen browser, local, Azure or other provider engine.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:env, open-webui:open-webui:voice.

WORK-06 Data analysis and document output

Judgment rule: Record code execution for data analysis, charts, and generation of downloadable Word, Excel, PowerPoint and PDF files. Analyse the fixture Excel and request a PowerPoint summary. Record where code runs and whether files are editable.

Dust

Agent cross-checked Support: supported

Computer executes analysis and creates real Office files; Frames provide editable interactive output.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

No Excel/PowerPoint fixture or artifact fidelity test. File Generation is deprecated in favor of Computer as of October 14, 2026.

data_analysis Can it analyse spreadsheets with executed code? [supported]: Computer executes code to inspect and transform Excel/CSV, compute every-row results and return edited workbooks. Sources: dust:dust:computer.
charts Can it produce charts? [supported]: Computer documents chart generation from spreadsheet data and inclusion in reports/decks. Sources: dust:dust:computer.
office_file_output Can it create Word, Excel or PowerPoint files? [supported]: Computer creates/edits Word, Excel and PowerPoint files and returns downloadable artifacts, with fidelity caveats. Sources: dust:dust:computer.
canvas_editing Is there a document or canvas editor for iterating on output? [supported]: Frames are persistent interactive content that can be revised through agents and shared. Sources: dust:dust:frames.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:computer, dust:dust:frames.

Open WebUI

Agent cross-checked Support: partial

Optional Open Terminal runs analysis code and creates artifacts; Notes provides document editing.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected code pinned to v0.12.3 / 91ea4e3421d1d8069f13d4a463fcb5986d94ea60; plan=Standard self-hosted with original branding intact; Enterprise only where explicitly stated; add_ons=Separately operated Open Terminal and document libraries; Enterprise Terminals optional; deployment_mode=on-premise; region=Customer-selected infrastructure country; external inference, extraction, search and support locations require separate configuration and contracts; os=not specified.

Limitations

office_file_output: The runtime can process Office files and create downloadable files through code and installed packages. Editable DOCX/XLSX/PPTX output was not verified with the shared fixture.

data_analysis Can it analyse spreadsheets with executed code? [supported]: Open Terminal documents spreadsheet/CSV inspection and code-based data analysis on the separately deployed runtime. Sources: open-webui:open-webui:terminal.
charts Can it produce charts? [supported]: Its data-analysis workflow includes generated charts and report artifacts. Sources: open-webui:open-webui:terminal.
office_file_output Can it create Word, Excel or PowerPoint files? [partial]: The runtime can process Office files and create downloadable files through code and installed packages. Editable DOCX/XLSX/PPTX output was not verified with the shared fixture. Sources: open-webui:open-webui:terminal.
canvas_editing Is there a document or canvas editor for iterating on output? [supported]: Notes offers a rich text and Markdown editor with AI rewrites. Sources: open-webui:open-webui:notes.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:terminal, open-webui:open-webui:notes.

WORK-07 Sharing and team spaces

Judgment rule: Record chat sharing (link, user, group), shared projects or team spaces, channels or group chat with AI, and commenting. Test sharing a chat with a colleague in another group and record what the recipient sees, including knowledge they lack access to.

Dust

Agent cross-checked Support: partial

Pods provide shared team conversations, files and tasks; source-sharing effects still need testing.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

No cross-group sharing fixture. Do not infer source-ACL propagation from Pod membership.

share_chats Can chats be shared inside the organisation? [supported]: Pod conversations are visible to all members, who can contribute. Sources: dust:dust:pod-chats.
team_spaces Are shared projects or workspaces available? [supported]: Open/Restricted Pods group conversations, files and tasks; restricted access is invite-only. Sources: dust:dust:pods.
group_chat Can several people chat together with the AI? [supported]: Teammates and agents participate in the same Pod thread and can be mentioned. Sources: dust:dust:pod-chats.
share_permission_boundary Does sharing respect the recipient's access to sources? [partial]: All Pod members read conversation contents. Spaces restrict source/agent use and personal tools act under their user; recipient-safe redaction of previously generated text was not established. Sources: dust:dust:pod-chats, dust:dust:permissions, dust:dust:credentials.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pod-chats, dust:dust:pods, dust:dust:permissions, dust:dust:credentials.

Open WebUI

Agent cross-checked Support: partial

Chats, shared resources and multi-person channels are documented. Recipient source-access boundaries were not tested.

Limitations

team_spaces: Groups organize shared models/knowledge and channels organize collaboration. This is not evidence of separate legal-entity tenancy.
share_permission_boundary: Does sharing respect the recipient's access to sources? No colleague-in-another-group chat-sharing fixture was run; transcript sharing may reveal already included content independently of original source access.

share_chats Can chats be shared inside the organisation? [supported]: Chat sharing is a configurable permission and users can manage shared chats. Sources: open-webui:open-webui:permissions, open-webui:open-webui:export.
team_spaces Are shared projects or workspaces available? [partial]: Groups organize shared models/knowledge and channels organize collaboration. This is not evidence of separate legal-entity tenancy. Sources: open-webui:open-webui:groups, open-webui:open-webui:channels.
group_chat Can several people chat together with the AI? [supported]: Channels support multiple members and AI participation. Sources: open-webui:open-webui:channels.
share_permission_boundary Does sharing respect the recipient's access to sources? [unknown]: share_permission_boundary: Does sharing respect the recipient's access to sources? No colleague-in-another-group chat-sharing fixture was run; transcript sharing may reveal already included content independently of original source access.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:permissions, open-webui:open-webui:export, open-webui:open-webui:groups, open-webui:open-webui:channels.

WORK-08 Interface languages and accessibility

Judgment rule: Record UI languages, focusing on German, French, Italian and English, with translation quality observed (complete, partial, machine-translated). Record response language handling and WCAG conformance statements.

Dust

Agent cross-checked Support: partial

German and French UI releases are documented alongside English, with remaining English areas.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

ui_languages Which UI languages are offered? [supported]: October 21, 2026 release adds German; October 16 adds French alongside English US/UK, across product, Frames, extension, Sidekick and Slack/Teams. Sources: dust:dust:changelog.
dach_language_quality Are German, French and Italian UIs complete and natural? [partial]: Release notes explicitly leave agent/skill names and instructions in English. German/French naturalness and completeness were not observed; Italian UI was not established. Sources: dust:dust:changelog.
accessibility_statement Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? The dated locale announcements were checked; Italian UI and a WCAG conformance statement/report were not established.
admin_ui_languages Is the admin interface available in German? [partial]: Admins can set a workspace default language. A complete German admin-screen walkthrough was not observed. Sources: dust:dust:changelog.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:changelog.

Open WebUI

Agent cross-checked Support: partial

English, German, French and Italian locales are present in the pinned client. Completeness, naturalness and WCAG conformance are unknown.

Limitations

dach_language_quality: Are German, French and Italian UIs complete and natural? Locale registration is not a UI-quality test. No full German admin-screen walkthrough or WCAG conformance report was reviewed; broader i18n and accessibility remain roadmap topics.
accessibility_statement: Is there a WCAG conformance statement? Locale registration is not a UI-quality test. No full German admin-screen walkthrough or WCAG conformance report was reviewed; broader i18n and accessibility remain roadmap topics.
admin_ui_languages: Is the admin interface available in German? Locale registration is not a UI-quality test. No full German admin-screen walkthrough or WCAG conformance report was reviewed; broader i18n and accessibility remain roadmap topics.

ui_languages Which UI languages are offered? [supported]: The locale registry includes en-US/en-GB, de-DE, fr-FR and it-IT among other languages. Sources: open-webui:open-webui:i18n-pin.
dach_language_quality Are German, French and Italian UIs complete and natural? [unknown]: dach_language_quality: Are German, French and Italian UIs complete and natural? Locale registration is not a UI-quality test. No full German admin-screen walkthrough or WCAG conformance report was reviewed; broader i18n and accessibility remain roadmap topics.
accessibility_statement Is there a WCAG conformance statement? [unknown]: accessibility_statement: Is there a WCAG conformance statement? Locale registration is not a UI-quality test. No full German admin-screen walkthrough or WCAG conformance report was reviewed; broader i18n and accessibility remain roadmap topics.
admin_ui_languages Is the admin interface available in German? [partial]: The pinned German locale includes Admin Panel, user-management and settings labels. Full admin-screen translation coverage and naturalness were not observed; the public roadmap still lists full internationalization as planned. Sources: open-webui:open-webui:r4-german-admin-translations.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: open-webui:open-webui:i18n-pin, open-webui:open-webui:r4-german-admin-translations.

Administration and governance

ADM-01 Single sign-on and authentication

Judgment rule: Record SAML, OIDC, Microsoft Entra ID, Google, LDAP, MFA enforcement, conditional-access compatibility, domain verification and plan restrictions. Test one SSO login on a trial where possible.

Dust

Agent cross-checked Support: partial

SAML SSO can be enforced; Business offers it from five seats on demand.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

No self-serve SSO login test.

sso_protocols Which SSO protocols and identity providers work? [supported]: SAML SSO is documented, with Okta, Entra ID and JumpCloud named on pricing. Enterprise marketing also names OIDC; a full provider/protocol matrix was not verified. Sources: dust:dust:sso, dust:dust:pricing, dust:dust:enterprise.
sso_plan Which plan includes SSO? [supported]: Business pricing lists SSO for 5+ seats on demand; Enterprise includes it. Sources: dust:dust:pricing.
mfa Can MFA be enforced? [partial]: Enforced SAML routes sign-in through the IdP. Specific MFA enforcement behavior was not tested or established in the checked setup guide. Sources: dust:dust:sso.
conditional_access Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? SSO and plan guides were checked; conditional-access compatibility and verified-domain capture/migration semantics were not established.
domain_capture Can the company claim its email domain? [unknown]: Can the company claim its email domain? SSO and plan guides were checked; conditional-access compatibility and verified-domain capture/migration semantics were not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:sso, dust:dust:pricing, dust:dust:enterprise.

Open WebUI

Agent cross-checked Support: partial

OAuth/OIDC, trusted-header and directory authentication are documented; standard self-hosting includes configuration access.

Limitations

conditional_access: The privacy guide recommends enforcing MFA, conditional access and device posture at the identity provider. No Entra sign-in fixture was run.
domain_capture: Can the company claim its email domain? Email-domain filtering settings do not establish enterprise domain ownership capture; this was not verified.

sso_protocols Which SSO protocols and identity providers work? [supported]: OAuth/OIDC includes Microsoft, Google and generic providers; trusted-header proxies and LDAP are documented. Direct SAML was not established. Sources: open-webui:open-webui:sso, open-webui:open-webui:roles.
sso_plan Which plan includes SSO? [supported]: The public self-hosted authentication configuration is available under standard use, with no separately listed SSO charge. Sources: open-webui:open-webui:sso, open-webui:open-webui:enterprise.
mfa Can MFA be enforced? [supported]: Admins can enable built-in authenticator-based MFA and choose whether OAuth may bypass it. Sources: open-webui:open-webui:mfa.
conditional_access Do Entra conditional-access policies apply? [partial]: The privacy guide recommends enforcing MFA, conditional access and device posture at the identity provider. No Entra sign-in fixture was run. Sources: open-webui:open-webui:privacy.
domain_capture Can the company claim its email domain? [unknown]: domain_capture: Can the company claim its email domain? Email-domain filtering settings do not establish enterprise domain ownership capture; this was not verified.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:sso, open-webui:open-webui:roles, open-webui:open-webui:enterprise, open-webui:open-webui:mfa, open-webui:open-webui:privacy.

ADM-02 User provisioning and lifecycle

Judgment rule: Record SCIM, just-in-time provisioning, group sync from the identity provider, deprovisioning effects (chats, assistants, knowledge ownership transfer) and licence assignment. Deprovision a test user and record what happens to their content.

Dust

Agent cross-checked Support: partial

Enterprise SCIM and group roles are documented, with specific annual-seat reclaim behavior.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Enterprise for SCIM; seat-management differences stated; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

scim Is SCIM provisioning supported? [supported]: SCIM 2.0 creates, updates and deactivates users from an IdP as an Enterprise feature. Sources: dust:dust:provision.
group_sync Are identity-provider groups synced? [supported]: Provisioned IdP groups govern Space access and can map to Admin/Manager roles. Sources: dust:dust:provision, dust:dust:spaces.
jit_provisioning Are users created at first login? [unknown]: Are users created at first login? Provisioning and seat docs were checked. First-login JIT creation and complete leaver-data transfer were not established.
deprovisioning What happens to a removed user's data and shared assets? [partial]: SCIM deactivates users; removal/reassignment affects seats but exact chat/agent/knowledge ownership transfer was not tested. Sources: dust:dust:provision, dust:dust:seats.
seat_assignment Can admins assign and reclaim seats? [supported]: Admins assign seat types independent of roles. Unassigned members cannot interact with agents; annual seats return to stock, and already-granted credits can persist to period end. Sources: dust:dust:seats.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:provision, dust:dust:spaces, dust:dust:seats.

Open WebUI

Agent cross-checked Support: partial

SCIM and login-time identity groups are documented; content ownership after removing a user needs further verification.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=SCIM bearer-token authentication rechecked at v0.12.4 / 33c1978d5bad52a31df75ea55143025dfad18d16 and current guide on 2026-10-26; other accepted identity facts retain their own cited versions; plan=Standard self-hosted with original branding intact; Enterprise only where explicitly stated; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure country; external inference, extraction, search and support locations require separate configuration and contracts; os=not specified.

Limitations

deprovisioning: SCIM active=false maps ordinary users to pending and disconnects live sessions. Asset transfer and retained shared content were not fixture-tested.
seat_assignment: Administrators control user accounts and roles. Standard use has no paid per-seat licence assignment mechanism to price; Enterprise entitlements were not reviewed.
No user-selectable token-scope control was established from the current SCIM guide or pinned authentication path.

scim Is SCIM provisioning supported? [supported]: SCIM 2.0 provisions/deactivates users and manages groups when enabled through SCIM_ENABLED and authenticated with the configured SCIM_TOKEN bearer token. The documented configuration does not expose user-selectable token scopes. Sources: open-webui:open-webui:r7-scim-bearer-doc, open-webui:open-webui:r7-scim-bearer-code.
group_sync Are identity-provider groups synced? [supported]: OAuth group management syncs claims at sign-in; SCIM also manages memberships. Sources: open-webui:open-webui:sso, open-webui:open-webui:scim.
jit_provisioning Are users created at first login? [supported]: OAuth account creation and optional JIT group creation can be enabled. Sources: open-webui:open-webui:sso.
deprovisioning What happens to a removed user's data and shared assets? [partial]: SCIM active=false maps ordinary users to pending and disconnects live sessions. Asset transfer and retained shared content were not fixture-tested. Sources: open-webui:open-webui:scim.
seat_assignment Can admins assign and reclaim seats? [partial]: Administrators control user accounts and roles. Standard use has no paid per-seat licence assignment mechanism to price; Enterprise entitlements were not reviewed. Sources: open-webui:open-webui:roles, open-webui:open-webui:enterprise.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: open-webui:open-webui:scim, open-webui:open-webui:sso, open-webui:open-webui:roles, open-webui:open-webui:enterprise, open-webui:open-webui:r7-scim-bearer-doc, open-webui:open-webui:r7-scim-bearer-code.

ADM-03 Roles, groups and feature permissions

Judgment rule: Record admin roles, delegated admins, groups, per-feature permissions (web search, image generation, connectors, file upload, agents), separation of subsidiaries or departments, and enforcement. Test one disabled feature for one group.

Dust

Agent cross-checked Support: partial

Dust separates Admin, Manager, Member and group-manager permissions and supports restricted knowledge spaces.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

admin_roles Which admin roles exist, and can admin rights be delegated? [supported]: Admins control all governance; Managers delegate member/group/usage administration; group managers administer selected groups. Sources: dust:dust:governance.
groups Can permissions be set per group? [supported]: Permissions go to manual or provisioned groups using Everyone, Groups or Admin-only modes. Multiple grants combine additively. Sources: dust:dust:governance.
feature_toggles Which features can be switched on or off per group? [partial]: Group controls cover agent/skill creation and publishing, automation charging, billing/security and model ceilings. An exhaustive per-feature toggle matrix for uploads/web/images was not established. Sources: dust:dust:governance, dust:dust:tiers.
multi_entity Can subsidiaries or departments be separated within one contract? [partial]: Restricted Spaces and Pods separate audiences inside a workspace; separate legal/subsidiary tenant boundaries within one contract were not established. Sources: dust:dust:spaces, dust:dust:pods.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:governance, dust:dust:tiers, dust:dust:spaces, dust:dust:pods.

Open WebUI

Agent cross-checked Support: partial

Roles and additive groups provide feature and resource permissions; separate instances remain the documented stronger trust boundary.

Limitations

admin_roles: Admin, User and Pending are system roles. Admin access can be reduced by product flags, but a least-privilege delegated-admin role matrix was not established.
multi_entity: Groups can organize departments; the privacy guide recommends separate instances/databases/operators for distinct trust boundaries. A multi-entity commercial contract was not reviewed.

admin_roles Which admin roles exist, and can admin rights be delegated? [partial]: Admin, User and Pending are system roles. Admin access can be reduced by product flags, but a least-privilege delegated-admin role matrix was not established. Sources: open-webui:open-webui:roles.
groups Can permissions be set per group? [supported]: User/group resource grants and additive feature permissions are documented. Sources: open-webui:open-webui:groups.
feature_toggles Which features can be switched on or off per group? [supported]: Permissions cover web search, images, files, model creation, tools, knowledge, memories and other features. Sources: open-webui:open-webui:permissions.
multi_entity Can subsidiaries or departments be separated within one contract? [partial]: Groups can organize departments; the privacy guide recommends separate instances/databases/operators for distinct trust boundaries. A multi-entity commercial contract was not reviewed. Sources: open-webui:open-webui:groups, open-webui:open-webui:privacy.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:roles, open-webui:open-webui:groups, open-webui:open-webui:permissions, open-webui:open-webui:privacy.

ADM-04 Usage and adoption analytics

Judgment rule: Record dashboards for active users, usage by feature, model, group and assistant, export, and privacy controls (aggregation, pseudonymisation, works-council-friendly settings). Distinguish aggregate adoption metrics from per-person monitoring.

Dust

Agent cross-checked Support: partial

Consumption analytics has detailed attribution and exports without message content.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

adoption_dashboard Is there an adoption dashboard? [partial]: Pricing lists usage/adoption reporting; the Analytics guide focuses on credit consumption and attribution rather than a complete active-user adoption scorecard. Sources: dust:dust:pricing, dust:dust:analytics.
breakdowns Can usage be broken down by group, model, feature and assistant? [supported]: Analytics filters/ranks agents, members, groups, models, tools, sources, API keys, skills and Pods. Group attribution may count a member in several groups. Sources: dust:dust:analytics.
export Can usage data be exported? [supported]: Raw CSV consumption export and API analytics export are documented, with workspace enablement and key-scope restrictions. Sources: dust:dust:analytics.
privacy_modes Can per-person reporting be limited or pseudonymised? [partial]: Analytics exports omit message content, but contain member/message/conversation identifiers. Pseudonymous or works-council privacy modes were not established. Sources: dust:dust:analytics.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:analytics.

Open WebUI

Agent cross-checked Support: partial

Admin analytics provides user/model/group activity and token reports, with API export.

Limitations

breakdowns: User, model and group views are documented. Complete feature/assistant breakdowns were not established.
privacy_modes: Admins can disable analytics and product-level chat access. Pseudonymized reporting was not established; the default user table identifies users.

adoption_dashboard Is there an adoption dashboard? [supported]: The dashboard reports messages, chats, token usage and user activity by date range. Sources: open-webui:open-webui:analytics.
breakdowns Can usage be broken down by group, model, feature and assistant? [partial]: User, model and group views are documented. Complete feature/assistant breakdowns were not established. Sources: open-webui:open-webui:analytics.
export Can usage data be exported? [supported]: Analytics API endpoints can be exported into JSON or external BI tooling. Sources: open-webui:open-webui:analytics.
privacy_modes Can per-person reporting be limited or pseudonymised? [partial]: Admins can disable analytics and product-level chat access. Pseudonymized reporting was not established; the default user table identifies users. Sources: open-webui:open-webui:analytics, open-webui:open-webui:privacy.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:analytics, open-webui:open-webui:privacy.

ADM-05 Spend controls and cost allocation

Judgment rule: Record cost visibility per user, group and cost centre, budgets and their behaviour (alert, block, downgrade model), pooled credits, and chargeback exports. Test a small budget on a trial where possible. Distinguish billed amounts, estimates and unavailable amounts.

Dust

Agent cross-checked Support: partial

Credit plans offer consumption visibility, member limits and plan-specific pooled budgets, with programmatic exceptions.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Group budgets are beta and exclude programmatic usage. No budget fixture test.

cost_visibility Can admins see cost or consumption per user and group? [supported]: Analytics and Credits show consumed credits by member, group, model, tool and agent. Credits are not assumed to be invoice currency. Sources: dust:dust:analytics, dust:dust:credit-management.
budgets Can budgets be set per user or group? [supported]: Members have shared-pool spend limits; beta group budgets require Enterprise Pooled. Programmatic monthly and API-key caps are separate. Sources: dust:dust:credit-management, dust:dust:api-keys.
budget_enforcement Does reaching a budget alert, block or downgrade? [supported]: Pool limits/group budgets block further requests; an in-progress message can finish above its starting cap. API calls reject at per-key caps. Optional automatic seat upgrades may increase billed subscriptions. Sources: dust:dust:credit-management, dust:dust:api-keys.
chargeback Can costs be exported per cost centre? [partial]: Consumption CSV includes groups and identifiers, but group attribution can duplicate usage and is not a guaranteed invoice-ready cost-center chargeback. Sources: dust:dust:analytics.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:analytics, dust:dust:credit-management, dust:dust:api-keys.

Open WebUI

Agent cross-checked Support: partial

Token usage supports cost estimation; enforced monetary budgets and cost-centre exports remain unverified.

Limitations

cost_visibility: Analytics exposes provider-reported input/output tokens by user/model/group; billed currency requires multiplying by external provider prices.
budgets: Can budgets be set per user or group? The analytics and roadmap sources were checked. Numeric user/group budgets, block/downgrade behavior and cost-centre chargeback exports were not established; a low-budget test was not run.
budget_enforcement: Does reaching a budget alert, block or downgrade? The analytics and roadmap sources were checked. Numeric user/group budgets, block/downgrade behavior and cost-centre chargeback exports were not established; a low-budget test was not run.
chargeback: Can costs be exported per cost centre? The analytics and roadmap sources were checked. Numeric user/group budgets, block/downgrade behavior and cost-centre chargeback exports were not established; a low-budget test was not run.

cost_visibility Can admins see cost or consumption per user and group? [partial]: Analytics exposes provider-reported input/output tokens by user/model/group; billed currency requires multiplying by external provider prices. Sources: open-webui:open-webui:analytics.
budgets Can budgets be set per user or group? [unknown]: budgets: Can budgets be set per user or group? The analytics and roadmap sources were checked. Numeric user/group budgets, block/downgrade behavior and cost-centre chargeback exports were not established; a low-budget test was not run.
budget_enforcement Does reaching a budget alert, block or downgrade? [unknown]: budget_enforcement: Does reaching a budget alert, block or downgrade? The analytics and roadmap sources were checked. Numeric user/group budgets, block/downgrade behavior and cost-centre chargeback exports were not established; a low-budget test was not run.
chargeback Can costs be exported per cost centre? [unknown]: chargeback: Can costs be exported per cost centre? The analytics and roadmap sources were checked. Numeric user/group budgets, block/downgrade behavior and cost-centre chargeback exports were not established; a low-budget test was not run.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:analytics.

ADM-06 Audit logs and compliance export

Judgment rule: Record which events are logged (logins, admin changes, prompts, responses, file access, connector queries), retention, export or SIEM streaming, and eDiscovery/legal hold. Use the word audit only with a defined retention and integrity model.

Dust

Agent cross-checked Support: partial

Enterprise has documented event logs and SIEM delivery; content logging and legal hold remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust APIs and MCP server; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Enterprise; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

admin_events Are admin and security events logged? [supported]: Enterprise Audit Logs record significant admin/security, user, API-key, system and tool events with timestamps, targets and actor metadata. Sources: dust:dust:audit.
content_logging Can prompts and answers be retained for compliance, and is it configurable? [unknown]: Can prompts and answers be retained for compliance, and is it configurable? Audit, analytics and public legal entry points were checked. Prompt/response compliance capture, eDiscovery/legal hold and detailed log-integrity implementation/retention contract were not established.
siem_export Can logs stream to a SIEM or be exported? [supported]: CSV export and continuous destinations include Datadog, Splunk, S3, GCS and custom HTTPS. Sources: dust:dust:audit.
ediscovery Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Audit, analytics and public legal entry points were checked. Prompt/response compliance capture, eDiscovery/legal hold and detailed log-integrity implementation/retention contract were not established.
log_retention How long are logs kept? [partial]: Enterprise marketing states 365-day audit retention; no underlying report/contract or configurable retention details were retrieved. Sources: dust:dust:enterprise.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:audit, dust:dust:enterprise.

Open WebUI

Agent cross-checked Support: partial

Optional request logging can capture metadata or content and stream to operator log infrastructure. It is not a verified immutable compliance archive.

Limitations

ediscovery: Are eDiscovery and legal hold supported? No eDiscovery/legal-hold contract or immutable retention/integrity model was verified.
log_retention: File rotation is configurable and operators own log storage and retention. No universal retention period or tamper-evident archive was established.

admin_events Are admin and security events logged? [supported]: Configured request logging can include authentication and administrative API paths. Sources: open-webui:open-webui:hardening.
content_logging Can prompts and answers be retained for compliance, and is it configurable? [supported]: REQUEST and REQUEST_RESPONSE levels add bodies, subject to path exclusions and a body-size cap; metadata-only capture is also available. Sources: open-webui:open-webui:hardening.
siem_export Can logs stream to a SIEM or be exported? [supported]: File or stdout output can feed an operator-managed log collector. Sources: open-webui:open-webui:hardening.
ediscovery Are eDiscovery and legal hold supported? [unknown]: ediscovery: Are eDiscovery and legal hold supported? No eDiscovery/legal-hold contract or immutable retention/integrity model was verified.
log_retention How long are logs kept? [partial]: File rotation is configurable and operators own log storage and retention. No universal retention period or tamper-evident archive was established. Sources: open-webui:open-webui:hardening, open-webui:open-webui:security.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:hardening, open-webui:open-webui:security.

ADM-07 Data loss prevention and personal data

Judgment rule: Record detection and handling of personal and confidential data before it reaches a model: redaction, masking, blocking, warning. Record integration with Purview, Netskope or similar, and whether filtering runs locally or at a third party. Send a fixture prompt with a Swiss AHV number and IBAN and record the outcome.

Dust

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Open WebUI

Agent cross-checked Support: partial

Custom request filters provide an extension point for PII policies; a configured detection/redaction product and Swiss fixture result were not established.

Availability: generally-available · Delivery: manual-workaround
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected code pinned to v0.12.3 / 91ea4e3421d1d8069f13d4a463fcb5986d94ea60; plan=Standard self-hosted with original branding intact; Enterprise only where explicitly stated; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure country; external inference, extraction, search and support locations require separate configuration and contracts; os=not specified.

Limitations

pii_detection: Is personal data detected in prompts and files? The filter framework was reviewed, not a configured PII/DLP deployment. No AHV/IBAN/file fixture, Purview/Netskope connector or default detection coverage was verified.
pii_action: An installed custom Python filter can modify or reject requests before model processing. No built-in AHV/IBAN policy is claimed.
custom_patterns: Custom filter code can implement customer rules; ready-made managed pattern libraries were not verified.
dlp_integration: Does it integrate with an existing DLP product? The filter framework was reviewed, not a configured PII/DLP deployment. No AHV/IBAN/file fixture, Purview/Netskope connector or default detection coverage was verified.

pii_detection Is personal data detected in prompts and files? [unknown]: pii_detection: Is personal data detected in prompts and files? The filter framework was reviewed, not a configured PII/DLP deployment. No AHV/IBAN/file fixture, Purview/Netskope connector or default detection coverage was verified.
pii_action Is it redacted, masked, blocked or only warned? [partial]: An installed custom Python filter can modify or reject requests before model processing. No built-in AHV/IBAN policy is claimed. Sources: open-webui:open-webui:filter.
custom_patterns Can admins add custom patterns or terms? [partial]: Custom filter code can implement customer rules; ready-made managed pattern libraries were not verified. Sources: open-webui:open-webui:filter.
dlp_integration Does it integrate with an existing DLP product? [unknown]: dlp_integration: Does it integrate with an existing DLP product? The filter framework was reviewed, not a configured PII/DLP deployment. No AHV/IBAN/file fixture, Purview/Netskope connector or default detection coverage was verified.
filter_location Where does filtering run? [supported]: Python filters execute in the customer-operated backend unless their implementation calls an external service. Sources: open-webui:open-webui:filter.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:filter.

ADM-08 AI policy and guardrails

Judgment rule: Record organisation-wide system instructions, acceptable-use notices and acknowledgement, content filters, topic restrictions, AI-output labelling, and admin visibility of policy violations. Separate enforced policy from instructions the model is expected to follow.

Dust

Agent cross-checked Support: partial

Agents have persistent instructions and workspace governance; broad enforced content-policy administration is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

org_instructions Can admins set organisation-wide instructions? [partial]: Admins/builders configure agent instructions; an enforced single organization-wide instruction applied to every agent/message was not established. Sources: dust:dust:builder, dust:dust:governance.
usage_notice Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? Agent, governance and security pages were checked. Mandatory usage-policy acknowledgement and administrator policy-violation reporting were not established.
content_filters Are content filters configurable? [partial]: Image Generation documents NSFW/celebrity safety filtering. Custom organization-wide topic/content rules were not established. Sources: dust:dust:images.
violation_reporting Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Agent, governance and security pages were checked. Mandatory usage-policy acknowledgement and administrator policy-violation reporting were not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:governance, dust:dust:images.

Open WebUI

Agent cross-checked Support: partial

Model defaults, prompts, banners and custom filters can express policy. Recorded acceptance and violation reporting remain unknown.

Limitations

org_instructions: Admins can configure model/default system prompts; sources explicitly warn that instructions do not guarantee model behavior.
usage_notice: Banners can display policy text, but a required recorded acknowledgement was not established.
content_filters: Operators can install custom request/response filters. Actual policy enforcement depends on that code and configuration.
violation_reporting: Are policy hits visible to admins? The models, banner and filter guides did not establish an organization-wide violation dashboard or mandatory acceptable-use acknowledgement.

org_instructions Can admins set organisation-wide instructions? [partial]: Admins can configure model/default system prompts; sources explicitly warn that instructions do not guarantee model behavior. Sources: open-webui:open-webui:models, open-webui:open-webui:env.
usage_notice Can users be required to accept a usage policy? [partial]: Banners can display policy text, but a required recorded acknowledgement was not established. Sources: open-webui:open-webui:banners.
content_filters Are content filters configurable? [partial]: Operators can install custom request/response filters. Actual policy enforcement depends on that code and configuration. Sources: open-webui:open-webui:filter.
violation_reporting Are policy hits visible to admins? [unknown]: violation_reporting: Are policy hits visible to admins? The models, banner and filter guides did not establish an organization-wide violation dashboard or mandatory acceptable-use acknowledgement.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:models, open-webui:open-webui:env, open-webui:open-webui:banners, open-webui:open-webui:filter.

Data protection and sovereignty

DATA-01 Hosting location and data residency

Judgment rule: Record country or region separately for chat storage, files and indexes, model inference, backups, logs and telemetry, and support access. Name the cloud provider. Record whether residency is default, a paid option or plan-dependent. "EU data boundary" programmes are recorded with their documented exceptions.

Dust

Agent cross-checked Support: partial

EU workspace and EU model controls are distinct from general hosting and global subprocessing.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

storage_region Where are chats, files and indexes stored? [partial]: Pricing/security advertise EU or US workspace hosting. Exact cloud provider, storage country and index location were not established. Sources: dust:dust:pricing, dust:dust:security.
inference_region Where do model calls run, per provider? [supported]: EU credit-priced workspaces using Dust-hosted models can enable EU-hosted models only after all active agents comply. BYOK is outside this setting; not every model is eligible. Sources: dust:dust:eu-models.
backups_logs_region Where are backups, logs and telemetry? [unknown]: Where are backups, logs and telemetry? Hosting, EU-model and privacy pages were checked. Backup/log/telemetry countries, customer-content support-access geography and Swiss hosting were not established.
support_access_region From where can vendor staff access data? [partial]: The controller privacy policy permits non-EEA access/processing including the US; it does not establish customer-content support access by staff country. Sources: dust:dust:privacy.
swiss_hosting Is Swiss hosting available? [unknown]: Is Swiss hosting available? Hosting, EU-model and privacy pages were checked. Backup/log/telemetry countries, customer-content support-access geography and Swiss hosting were not established.
residency_plan Which plan or option provides residency? [supported]: Business and Enterprise list EU/US residency; EU-only model restrictions additionally require EU region and credit pricing with Dust model hosting. Sources: dust:dust:pricing, dust:dust:eu-models.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:security, dust:dust:eu-models, dust:dust:privacy.

Open WebUI

Agent cross-checked Support: partial

The operator chooses data locations; external services can receive prompts or documents independently of where Open WebUI is hosted.

Limitations

backups_logs_region: The operator controls backups and logging locations. A concrete installation and its telemetry/egress were not audited.
support_access_region: Operators and support recipients with host/database access can read data; there is no reviewed geographic enterprise support-access commitment.
swiss_hosting: An organization can deploy the self-hosted stack on Swiss infrastructure. This is not a bundled vendor-managed Swiss service or guaranteed Swiss inference.

storage_region Where are chats, files and indexes stored? [supported]: Chats, files and indexes reside in configured customer storage/database locations. No vendor-chosen region applies to this self-hosted instance. Sources: open-webui:open-webui:privacy.
inference_region Where do model calls run, per provider? [supported]: The selected provider endpoint runs inference; local, private or external endpoints must be scoped separately. Sources: open-webui:open-webui:provider, open-webui:open-webui:privacy.
backups_logs_region Where are backups, logs and telemetry? [partial]: The operator controls backups and logging locations. A concrete installation and its telemetry/egress were not audited. Sources: open-webui:open-webui:privacy.
support_access_region From where can vendor staff access data? [partial]: Operators and support recipients with host/database access can read data; there is no reviewed geographic enterprise support-access commitment. Sources: open-webui:open-webui:privacy.
swiss_hosting Is Swiss hosting available? [partial]: An organization can deploy the self-hosted stack on Swiss infrastructure. This is not a bundled vendor-managed Swiss service or guaranteed Swiss inference. Sources: open-webui:open-webui:privacy, open-webui:open-webui:quickstart.
residency_plan Which plan or option provides residency? [supported]: Self-hosting gives the operator infrastructure placement control under standard use; provider contracts and optional enterprise services are separate. Sources: open-webui:open-webui:privacy, open-webui:open-webui:enterprise.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:privacy, open-webui:open-webui:provider, open-webui:open-webui:quickstart, open-webui:open-webui:enterprise.

DATA-02 Deployment options

Judgment rule: Record multi-tenant SaaS, dedicated single-tenant instance, deployment in the customer's cloud account, on-premise and air-gapped as separate options with plan and availability. Record which features are missing in each mode, who operates it, and the documented seat or contract threshold for each mode, which can differ from the enterprise plan threshold (e.g. dedicated SaaS from 2,000 seats, own cloud from 5,000). A local-network connector or gateway that reaches on-prem data from a vendor-hosted platform is KNOW-03, not on-premise deployment.

Dust

Agent cross-checked Support: partial

Hosted Business and Enterprise single-tenant offers are public; supported customer-operated whole-platform modes are unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust Enterprise single-tenant deployment; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=not specified; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

multi_tenant_saas Is a shared SaaS offered? [partial]: Business is a self-serve hosted workspace; exact shared-infrastructure isolation architecture is not documented in the checked pages. Sources: dust:dust:pricing, dust:dust:privacy.
dedicated_instance Is a dedicated single-tenant instance offered, from what size? [supported]: Enterprise pricing advertises single-tenant deployment. Numerical seat/spend minimum, supported countries and operating terms were not established. Sources: dust:dust:pricing.
customer_cloud Can it run in the customer's own cloud account, from what size? [unknown]: Can it run in the customer's own cloud account, from what size? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment.
on_premise Can the whole platform run on customer infrastructure, from what size? [unknown]: Can the whole platform run on customer infrastructure, from what size? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment.
air_gapped Can it run without internet access? [unknown]: Can it run without internet access? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment.
mode_feature_gaps Which features are missing outside SaaS? [partial]: Business/Enterprise packaging differs in connectors, MCP, Spaces, APIs and governance. No customer-operated hosting feature-parity contract was established. Sources: dust:dust:pricing.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:privacy.

Open WebUI

Agent cross-checked Support: partial

Customer-operated cloud and on-premise installs are documented, with offline operation requiring all dependencies to be local.

Limitations

multi_tenant_saas: Is a shared SaaS offered? A vendor-operated shared SaaS, dedicated managed instance and contractual minimum for managed service were not established in the enterprise and installation sources.
dedicated_instance: Is a dedicated single-tenant instance offered, from what size? A vendor-operated shared SaaS, dedicated managed instance and contractual minimum for managed service were not established in the enterprise and installation sources.

multi_tenant_saas Is a shared SaaS offered? [unknown]: multi_tenant_saas: Is a shared SaaS offered? A vendor-operated shared SaaS, dedicated managed instance and contractual minimum for managed service were not established in the enterprise and installation sources.
dedicated_instance Is a dedicated single-tenant instance offered, from what size? [unknown]: dedicated_instance: Is a dedicated single-tenant instance offered, from what size? A vendor-operated shared SaaS, dedicated managed instance and contractual minimum for managed service were not established in the enterprise and installation sources.
customer_cloud Can it run in the customer's own cloud account, from what size? [supported]: Docker/Python installs can run in customer infrastructure; no standard-use seat minimum is stated. Sources: open-webui:open-webui:quickstart, open-webui:open-webui:enterprise.
on_premise Can the whole platform run on customer infrastructure, from what size? [supported]: The complete application can run on customer servers with local inference/extraction services. Sources: open-webui:open-webui:quickstart, open-webui:open-webui:offline.
air_gapped Can it run without internet access? [supported]: The offline guide describes preparing cached models/assets and local services before disconnecting. Sources: open-webui:open-webui:offline.
mode_feature_gaps Which features are missing outside SaaS? [supported]: External model APIs, internet search, remote extraction and other online tools require network access; they are not made local by self-hosting the UI. Sources: open-webui:open-webui:offline.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:quickstart, open-webui:open-webui:enterprise, open-webui:open-webui:offline.

DATA-03 Training use and provider retention

Judgment rule: Record whether customer content trains vendor or provider models, by plan and default; zero-data-retention arrangements with model providers; abuse-monitoring retention and human review; and the model provider's terms that apply. A "no training" claim on a marketing page is `vendor-claimed` until the contract or DPA says so.

Dust

Agent cross-checked Support: partial

Dust publishes no-training and provider-retention claims; the customer DPA was not retrieved.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Controller privacy-policy scope is distinct from processor DPA coverage.

vendor_training Does the vendor train on customer content? [partial]: The security page claims customer data is never used for model training. This remains vendor-claimed because no customer DPA/contract clause was retrieved. Sources: dust:dust:security.
provider_training Do model providers train on it under this product's contracts? [partial]: The privacy policy names OpenAI, Anthropic, Mistral, Google and Fireworks as prohibited from training on customer/personal content; BYOK arrangements need separate confirmation. Sources: dust:dust:training-policy.
provider_retention How long do model providers keep prompts, including for abuse monitoring? [partial]: The policy states providers do not log Customer Content for human review or save it to disk. Exception/abuse-retention periods were not established from customer contracts. Sources: dust:dust:training-policy.
zero_retention Is zero data retention available, and on which plan? [partial]: Security and privacy pages assert provider zero retention, but applicable plan/model exceptions were not contract-verified. Sources: dust:dust:security, dust:dust:training-policy.
human_review Can provider staff review content? [partial]: The published policy says listed providers do not log Customer Content for human review. This is a vendor assertion, not an independently reviewed model-provider contract. Sources: dust:dust:training-policy.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:training-policy.

Open WebUI

Agent cross-checked Support: partial

Self-hosting controls the application data path; training and retention obligations depend on the chosen external model contract.

Limitations

vendor_training: The self-hosted data path runs on customer infrastructure; this is architecture evidence, not a reviewed contractual no-training promise covering support or optional services.
provider_training: Do model providers train on it under this product's contracts? No executed provider agreement, abuse-monitoring retention, zero-retention entitlement or human-review policy was verified for a configured endpoint. Local inference is a separate deployment choice, not a blanket promise for cloud-connected use.
provider_retention: How long do model providers keep prompts, including for abuse monitoring? No executed provider agreement, abuse-monitoring retention, zero-retention entitlement or human-review policy was verified for a configured endpoint. Local inference is a separate deployment choice, not a blanket promise for cloud-connected use.
zero_retention: Is zero data retention available, and on which plan? No executed provider agreement, abuse-monitoring retention, zero-retention entitlement or human-review policy was verified for a configured endpoint. Local inference is a separate deployment choice, not a blanket promise for cloud-connected use.
human_review: Can provider staff review content? No executed provider agreement, abuse-monitoring retention, zero-retention entitlement or human-review policy was verified for a configured endpoint. Local inference is a separate deployment choice, not a blanket promise for cloud-connected use.

vendor_training Does the vendor train on customer content? [partial]: The self-hosted data path runs on customer infrastructure; this is architecture evidence, not a reviewed contractual no-training promise covering support or optional services. Sources: open-webui:open-webui:privacy, open-webui:open-webui:offline.
provider_training Do model providers train on it under this product's contracts? [unknown]: provider_training: Do model providers train on it under this product's contracts? No executed provider agreement, abuse-monitoring retention, zero-retention entitlement or human-review policy was verified for a configured endpoint. Local inference is a separate deployment choice, not a blanket promise for cloud-connected use.
provider_retention How long do model providers keep prompts, including for abuse monitoring? [unknown]: provider_retention: How long do model providers keep prompts, including for abuse monitoring? No executed provider agreement, abuse-monitoring retention, zero-retention entitlement or human-review policy was verified for a configured endpoint. Local inference is a separate deployment choice, not a blanket promise for cloud-connected use.
zero_retention Is zero data retention available, and on which plan? [unknown]: zero_retention: Is zero data retention available, and on which plan? No executed provider agreement, abuse-monitoring retention, zero-retention entitlement or human-review policy was verified for a configured endpoint. Local inference is a separate deployment choice, not a blanket promise for cloud-connected use.
human_review Can provider staff review content? [unknown]: human_review: Can provider staff review content? No executed provider agreement, abuse-monitoring retention, zero-retention entitlement or human-review policy was verified for a configured endpoint. Local inference is a separate deployment choice, not a blanket promise for cloud-connected use.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:privacy, open-webui:open-webui:offline.

DATA-04 Retention and deletion

Judgment rule: Record default retention for chats, files, indexes and logs; admin-configured retention; user deletion; deletion after contract end; and deletion confirmation.

Dust

Agent cross-checked Support: partial

Some user deletion and memory retention behavior is documented; tenant-wide retention schedules remain open.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

default_retention What is retained and for how long by default? [partial]: Agent memories persist until manually deleted. This does not define default retention for all conversations, files, indexes or logs. Sources: dust:dust:memory.
admin_retention Can admins set retention periods? [partial]: Enterprise pricing offers custom data retention; periods, deletion mechanics and exceptions were not retrieved. Sources: dust:dust:pricing.
user_deletion Can users delete their chats and files permanently? [partial]: Users can delete conversations and agent memories. Backup erasure timing and all attached-file deletion behavior were not established. Sources: dust:dust:delete-chat, dust:dust:memory.
contract_end_deletion What is deleted at contract end, and when? [unknown]: What is deleted at contract end, and when? Conversation/memory docs, Enterprise pricing and unreadable legal entry points were checked. Contract-end erasure timing and complete storage/index/log retention defaults remain unknown.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:memory, dust:dust:pricing, dust:dust:delete-chat.

Open WebUI

Agent cross-checked Support: partial

Users can remove chats/files subject to permissions, and temporary-chat enforcement can avoid saving new conversations. Complete purge and contract-end schedules remain unverified.

Limitations

default_retention: Normal history persists in the operator’s database; temporary chats reduce saved history. A uniform default duration across chats, files, indexes, logs and backups was not established.
admin_retention: Operators control database and backup retention; enforced temporary-chat permissions stop saving new chats. A general time-based retention scheduler was not established.
user_deletion: Permissions allow chat deletion and file management removes files and related embeddings. Backup purge and irreversible-deletion timing were not verified.
contract_end_deletion: What is deleted at contract end, and when? No enterprise termination deletion deadline or deletion confirmation was reviewed.

default_retention What is retained and for how long by default? [partial]: Normal history persists in the operator’s database; temporary chats reduce saved history. A uniform default duration across chats, files, indexes, logs and backups was not established. Sources: open-webui:open-webui:privacy, open-webui:open-webui:quickstart.
admin_retention Can admins set retention periods? [partial]: Operators control database and backup retention; enforced temporary-chat permissions stop saving new chats. A general time-based retention scheduler was not established. Sources: open-webui:open-webui:privacy.
user_deletion Can users delete their chats and files permanently? [partial]: Permissions allow chat deletion and file management removes files and related embeddings. Backup purge and irreversible-deletion timing were not verified. Sources: open-webui:open-webui:permissions, open-webui:open-webui:rag.
contract_end_deletion What is deleted at contract end, and when? [unknown]: contract_end_deletion: What is deleted at contract end, and when? No enterprise termination deletion deadline or deletion confirmation was reviewed.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:privacy, open-webui:open-webui:quickstart, open-webui:open-webui:permissions, open-webui:open-webui:rag.

DATA-05 Sub-processors and foreign-law exposure

Judgment rule: Record the published sub-processor list with countries, change-notification rules, the vendor's and parent company's jurisdiction, transfer mechanisms (EU-US Data Privacy Framework, Swiss-US DPF, SCCs) and the vendor's documented position on foreign government access requests (e.g. US CLOUD Act). Record facts, not a legal assessment.

Dust

Agent cross-checked Support: partial

Dust identifies a French operating entity; customer subprocessor inventory and notice rules remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

subprocessor_list Is a dated sub-processor list published? [unknown]: Is a dated sub-processor list published? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established.
subprocessor_countries Which countries do sub-processors operate in? [unknown]: Which countries do sub-processors operate in? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established.
change_notification Are customers notified of sub-processor changes? [unknown]: Are customers notified of sub-processor changes? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established.
parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: The public policy identifies Permutation Labs at a Paris, France address. A separate parent company or controlling entity was not established. Sources: dust:dust:privacy.
transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [partial]: For its controller processing, the privacy policy describes adequacy or EU SCC safeguards for non-EU transfers, including the US. Customer processor transfer terms were not retrieved. Sources: dust:dust:privacy.
government_access_policy Is there a published government-access or transparency policy? [partial]: The controller policy allows legally required disclosure to authorities; a dedicated government-request transparency policy for customer content was not established. Sources: dust:dust:privacy.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:privacy.

Open WebUI

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

DATA-06 Contracts and regulatory coverage

Judgment rule: Record DPA availability and form (click-through, negotiable), reference to Swiss revDSG and GDPR, governing law and court, EU AI Act documentation (provider or deployer role, transparency materials), and sector-specific materials (FINMA outsourcing, banking secrecy, public sector). No compliance verdict.

Dust

Agent cross-checked Support: partial

Enterprise offers custom MSA/DPA terms, while the underlying legal materials were inaccessible.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

dpa Is a DPA available, and is it negotiable? [partial]: Enterprise pricing explicitly offers custom MSA/DPA terms. The form, sign-up incorporation and negotiability boundaries were not inspected. Sources: dust:dust:pricing.
revdsg_gdpr Does the DPA cover revDSG and GDPR? [partial]: Marketing and privacy materials reference GDPR; explicit Swiss revDSG coverage in the customer DPA was not established. Sources: dust:dust:security, dust:dust:privacy.
governing_law Which law and court govern the contract? [unknown]: Which law and court govern the contract? Official Terms & Policies redirects to a Notion page that returned no readable terms; trust.dust.com also exposed no report text. Governing law/court and EU AI Act technical/role materials were not established.
ai_act_materials Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? Official Terms & Policies redirects to a Notion page that returned no readable terms; trust.dust.com also exposed no report text. Governing law/court and EU AI Act technical/role materials were not established.
sector_materials Are FINMA or other sector materials provided? [partial]: Security marketing says the service enables HIPAA compliance. A BAA, FINMA or banking-secrecy outsourcing pack was not retrieved. Sources: dust:dust:security.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:security, dust:dust:privacy.

Open WebUI

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

DATA-07 Certifications and attestations

Judgment rule: Record each certificate or report separately: ISO 27001, 27017, 27018, 27701, 42001; SOC 2 Type I/II with period; BSI C5; TISAX; national schemes. Record issuer, scope (which product and entity), validity and access route. A cloud provider's certificate does not certify the product.

Dust

Agent cross-checked Support: partial

SOC 2 Type II is claimed publicly, without a verified report or certificate.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

iso_27001 ISO 27001 with scope and validity? [unknown]: ISO 27001 with scope and validity? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified.
soc2 SOC 2 type, period and covered service? [partial]: Dust security/pricing claim SOC 2 Type II. Auditor, reporting period and exact service scope were not verified. Sources: dust:dust:security, dust:dust:pricing.
c5 BSI C5 attestation? [unknown]: BSI C5 attestation? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified.
other_certifications Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified.
report_access How can customers obtain reports? [partial]: The security page directs customers to trust.dust.com; underlying reports were not accessible in this public source pass. Sources: dust:dust:security.
pentest Are independent penetration test summaries available? [unknown]: Are independent penetration test summaries available? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:pricing.

Open WebUI

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

DATA-08 Encryption and key control

Judgment rule: Record encryption at rest and in transit, customer-managed keys (BYOK/HYOK), key location, and private networking (private link, IP allow-lists, VPN).

Dust

Agent cross-checked Support: partial

Dust claims AES-256/TLS and advertises Enterprise single tenancy; customer key custody is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

encryption_at_rest Is data encrypted at rest? [supported]: The security page states AES-256 at rest and TLS in transit; this is a vendor claim. Sources: dust:dust:security.
customer_managed_keys Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Security, pricing and network/MCP docs were checked. Customer-managed/held data-encryption keys and key-location guarantees were not established. Provider API BYOK is not encryption-key custody.
private_networking Is private connectivity or IP restriction available? [partial]: Custom MCP servers can restrict access and use documented static egress on verified domains. This is tool connectivity, not proof of private connectivity to the whole service. Sources: dust:dust:tools.
tenant_isolation How are customers separated in shared SaaS? [partial]: Enterprise offers single tenancy; shared Business tenancy and lower-level isolation mechanics were not established. Sources: dust:dust:pricing.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:tools, dust:dust:pricing.

Open WebUI

Agent cross-checked Support: partial

Encryption and private networking are operator responsibilities; product flags do not remove host-operator access.

Limitations

encryption_at_rest: The privacy guide recommends encrypted PostgreSQL volumes/backups or encrypted SQLite filesystems. SQLCipher is explicitly unsupported since v0.9.0. It is not automatic application-level encryption of all content.
customer_managed_keys: The customer can operate infrastructure encryption keys. A product HYOK/key-escrow protocol was not established.
tenant_isolation: How are customers separated in shared SaaS? Shared vendor SaaS tenant isolation was not established for the scoped customer-operated product.

encryption_at_rest Is data encrypted at rest? [partial]: The privacy guide recommends encrypted PostgreSQL volumes/backups or encrypted SQLite filesystems. SQLCipher is explicitly unsupported since v0.9.0. It is not automatic application-level encryption of all content. Sources: open-webui:open-webui:privacy.
customer_managed_keys Can the customer manage or hold the keys? [partial]: The customer can operate infrastructure encryption keys. A product HYOK/key-escrow protocol was not established. Sources: open-webui:open-webui:privacy.
private_networking Is private connectivity or IP restriction available? [supported]: The application and local services can run inside customer networks and disconnected environments; TLS/reverse-proxy setup remains operator work. Sources: open-webui:open-webui:privacy, open-webui:open-webui:offline.
tenant_isolation How are customers separated in shared SaaS? [unknown]: tenant_isolation: How are customers separated in shared SaaS? Shared vendor SaaS tenant isolation was not established for the scoped customer-operated product.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:privacy, open-webui:open-webui:offline.

DATA-09 Professional secrecy

Judgment rule: For professional secrecy holders (Berufsgeheimnisträger: lawyers, doctors, auditors, tax advisers) under § 203 StGB (DE) and Art. 321 StGB (CH), record whether the vendor signs a contractual secrecy undertaking or a § 203 agreement that binds its staff and its sub-processors; whether this comes as a dedicated offering or a paid add-on, and on which plan; who can access content in plain text (vendor staff, sub-processors, model providers); and the documentation provided. A DPA or a no-training clause alone is not a secrecy undertaking. Banking secrecy and FINMA outsourcing belong to DATA-06, not here. Record contract facts, not a legal assessment.

Dust

Agent cross-checked Support: partial

Public personnel/model handling statements exist; an explicit professional-secrecy contract and subprocessor flow-down remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Dust Business/Enterprise public policy; Enterprise and BYOK routes differ; add_ons=none stated; deployment_mode=multi-tenant-saas; region=EU/US storage and provider routes; no DE/CH-specific secrecy contract verified; os=not specified.

Limitations

No-training, ZDR marketing/policy assertions, EU hosting and a general privacy policy do not establish a professional-secrecy undertaking.
No legal suitability or compliance conclusion.

secrecy_undertaking Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: The public security and platform privacy pages do not establish a signed §203 StGB/Art321 StGB professional-secrecy undertaking covering Dust staff. The Terms/Policies link did not expose readable contractual text in this pass.
subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The privacy policy describes service-provider data-protection agreements and model no-training/retention conditions, but no dedicated professional-secrecy undertaking or its binding subprocessor flow-down was retrieved.
secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: No publicly documented German/Swiss professional-secrecy-specific plan or paid add-on was established. Enterprise single-tenancy/EU model options are not treated as such a contractual undertaking.
content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: The platform privacy policy limits personnel access to authorized staff and says customer context is processed by selected foundation-model providers; it asserts no provider disk retention/human-review logging. This vendor statement does not establish the complete customer-content plaintext access matrix, support countries, private contracts or every BYOK/MCP/tool route. Sources: dust:dust:privacy, dust:dust:training-policy, dust:dust:eu-models.
secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Reviewed public security, privacy, EU-hosted model documentation and Enterprise plan scope plus targeted first-party secrecy search. Trust Center content was not available and Terms/Policies routed to unreadable external content. No public §203/Art321 template or professional-body guidance was retrieved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:privacy, dust:dust:training-policy, dust:dust:eu-models.

Open WebUI

Agent cross-checked Support: partial

The self-hosted content-access boundary is documented. A vendor secrecy undertaking under § 203 StGB or Art. 321 StGB, its staff/sub-processor coverage and any plan-specific offering remain unverified.

Availability: unknown · Delivery: unknown
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; standard self-hosted server and separately described Enterprise support; plan=Standard branded self-hosted use; Enterprise licensing/support checked separately, with no professional-secrecy contract or add-on verified; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected application/model infrastructure; no DE/CH secrecy-contract variant or vendor/support access jurisdiction verified; os=not specified.

Limitations

The secrecy undertaking, sub-processor coverage, offering and professional-secrecy-specific documentation remain unknown.
content_access: A concrete deployment, support-access grant, sub-processor permissions and model-provider staff access were not audited.
Technical data controls, a DPA, privacy wording and no-training statements do not establish the requested contractual undertaking. No legal compliance assessment is made.

secrecy_undertaking Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: The public Enterprise, support, security and law-firm pages did not establish a signed or signable professional-secrecy undertaking binding Open WebUI staff. No § 203 StGB / Art. 321 StGB agreement was obtained; informational security guidance is not recorded as one. Sources: open-webui:open-webui:enterprise, open-webui:open-webui:secrecy-support.
subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [unknown]: No professional-secrecy undertaking or annex identifying covered sub-processors and their secrecy obligations was found in the reviewed public materials. Customer-selected hosting, model and support arrangements need their own document review.
secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: Enterprise licensing and advisory support are documented, but their public descriptions did not establish a professional-secrecy package, paid add-on, eligible plan or contractual scope. No sales contact was made. Sources: open-webui:open-webui:enterprise, open-webui:open-webui:secrecy-support.
content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: For self-hosted AI chats, Open WebUI documents the running application, live-query database administrators, host/backup operators and configured external model providers as part of the content-access boundary. Admin UI restrictions and at-rest encryption do not exclude those operators. The law-firm page says self-hosted data is not sent to Open WebUI as a managed service; vendor support grants, sub-processor staff permissions and provider human access were not verified for a concrete deployment. Sources: open-webui:open-webui:secrecy-access, open-webui:open-webui:secrecy-legal.
secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: The law-firm page provides general deployment/privacy guidance and links US ABA materials. No product-scoped DE/CH secrecy contract template, staff/sub-processor annex or professional-body confirmation was located in the reviewed public pages or targeted searches. Sources: open-webui:open-webui:secrecy-legal.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:enterprise, open-webui:open-webui:secrecy-support, open-webui:open-webui:secrecy-access, open-webui:open-webui:secrecy-legal.

Commercials and vendor

VEN-01 Pricing model and list prices

Judgment rule: Record pricing unit (per seat, per active user, usage-based, platform fee, hybrid), list prices per plan in original currency with date, included usage and credits, add-on prices (connectors, agents, image generation) and overage rates. Cite public prices or dated quotes. Per-seat versus usage is a fact, not a quality judgment.

Dust

Agent cross-checked Support: partial

Business seat prices are public; only the documented prepaid route is described here, while conflicting Business overage eligibility remains unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business Free/Pro/Max seat list pricing; Enterprise quoted pool and programmatic contracts are separate; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.
Do not present Business PAYG as established; retain list seat prices separately from the unresolved overage route.

pricing_unit What is the pricing unit? [partial]: Business publishes per-seat subscriptions and included credits. Detailed Credit management describes prepaid Business top-ups and Enterprise PAYG; pricing FAQ separately describes enabled Business workspace overage, so Business post-allocation billing eligibility is unverified. Sources: dust:dust:pricing, dust:dust:credit-management.
list_prices What are list prices per plan, with date and currency? [supported]: As retrieved 2026-10-21, ex-VAT Business Free is EUR 0; Pro EUR 30/month or EUR 24/month annually; Max EUR 150/month or EUR 120/month annually. Enterprise is quote-only. Sources: dust:dust:pricing.
included_usage What usage is included? [supported]: Free has 500 lifetime credits, Pro 8,000/month and Max 40,000/month. Monthly credits do not roll over; Workspace seats draw from a contracted pool. Sources: dust:dust:credits, dust:dust:seats.
add_ons Which features cost extra? [partial]: Business limits include three connectors, five remote MCP servers and five Spaces. Enterprise adds unlimited connector/MCP packaging, SCIM, audit, retention and support. Individual add-on tariffs are not published. Sources: dust:dust:pricing.
overage What do usage beyond limits and premium models cost? [unknown]: Effective Business post-allocation billing is unknown: current pricing FAQ allows Pro/Max workspace overage, while Credit management reserves PAYG for Enterprise and describes prepaid Business top-ups. The USD0.01/credit Business programmatic rate does not resolve whether interactive overage is PAYG or prepaid. No account/contract test resolved this.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:credit-management, dust:dust:credits, dust:dust:seats.

Open WebUI

Agent cross-checked Support: partial

Branding-intact standard use is free; Enterprise and external infrastructure/model services cost separately.

Limitations

list_prices: Standard internal use is listed as Free on 2026-10-21. No numeric Enterprise tariff was published in the reviewed offer.
add_ons: Branding changes outside licence exceptions and enterprise-exclusive offerings such as Terminals require Enterprise rights; service rates were not established.
overage: External providers charge under their own accounts; no universal Open WebUI inference overage tariff applies to standard self-hosting.

pricing_unit What is the pricing unit? [supported]: Standard software use has no per-seat fee with original branding intact. Enterprise rights/support are separately licensed. Sources: open-webui:open-webui:enterprise.
list_prices What are list prices per plan, with date and currency? [partial]: Standard internal use is listed as Free on 2026-10-21. No numeric Enterprise tariff was published in the reviewed offer. Sources: open-webui:open-webui:enterprise.
included_usage What usage is included? [supported]: A software licence does not supply model inference or hosting; customers configure those services. Sources: open-webui:open-webui:enterprise, open-webui:open-webui:provider.
add_ons Which features cost extra? [partial]: Branding changes outside licence exceptions and enterprise-exclusive offerings such as Terminals require Enterprise rights; service rates were not established. Sources: open-webui:open-webui:enterprise, open-webui:open-webui:terms.
overage What do usage beyond limits and premium models cost? [partial]: External providers charge under their own accounts; no universal Open WebUI inference overage tariff applies to standard self-hosting. Sources: open-webui:open-webui:provider, open-webui:open-webui:enterprise.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:enterprise, open-webui:open-webui:provider, open-webui:open-webui:terms.

VEN-02 Scenario cost

Judgment rule: Price three workloads for 12 months: 200, 1,000 and 5,000 users with a disclosed light/regular/power usage mix, in CHF and EUR excluding VAT. Include licences, platform fees, add-ons, model usage and, for self-hosted options, a stated operating assumption. Separate fixed, variable, included and unknown costs. No invented discounts.

Dust

Agent cross-checked Support: partial

ALM-14 shared cost assumptions v1.4, 2026-10-21 apply; all three target seat counts require unpriced Enterprise terms.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

cost_200 Year-one cost at 200 users? [unknown]: Year-one cost at 200 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope.
cost_1000 Year-one cost at 1,000 users? [unknown]: Year-one cost at 1,000 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope.
cost_5000 Year-one cost at 5,000 users? [unknown]: Year-one cost at 5,000 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope.
variable_share Which part depends on usage? [supported]: Consumption adds token and action credits, including sub-agent work. Programmatic use and Enterprise PAYG draw from workspace pools separately from personal seat allocations. Sources: dust:dust:credits, dust:dust:credit-management.
unknown_parts Which costs could not be priced? [supported]: Business is scoped to 100 people, so 200/1,000/5,000 seat Enterprise fees, committed pool and PAYG tariffs are unknown. The default Standard auto list is published, but a complete token-to-credit tariff is not, so no proxy replaces vendor-billed usage. Sources: dust:dust:pricing, dust:dust:models, dust:dust:credits.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:credits, dust:dust:credit-management, dust:dust:pricing, dust:dust:models, dust:dust:fx-ecb.

Open WebUI

Agent cross-checked Support: partial

ALM-14 shared cost assumptions v1.4, 2026-10-21: zero standard licence plus a disclosed Swiss infrastructure/operations and direct-BYO-model budget. Annual CHF/EUR figures are floors plus named unknown costs.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected code pinned to v0.12.3 / 91ea4e3421d1d8069f13d4a463fcb5986d94ea60; plan=Standard self-hosted with original branding intact; Enterprise only where explicitly stated; add_ons=Analyst-selected direct OpenAI API proxy, not a bundled model, Assumed operations staffing; optional commercial services excluded; deployment_mode=customer-cloud; region=Azure Switzerland North for the reference application infrastructure; standard OpenAI API inference has no Swiss/EU residency assumption; os=not specified.

Limitations

ALM-14 shared cost assumptions v1.4, 2026-10-21 are analyst inputs, not vendor sizing or an uptime promise.
The budget is a floor because named infrastructure and service costs are unpriced.

cost_200 Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 200 users, 12 months excluding VAT: from CHF 34778.28 / EUR 37651.06 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 4749.26, operations CHF 30000.00, and BYO model usage USD 475.20. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: open-webui:open-webui:enterprise, open-webui:open-webui:cost-vm, open-webui:open-webui:cost-pg, open-webui:open-webui:cost-fx, open-webui:open-webui:cost-model, open-webui:open-webui:cost-effort.
cost_1000 Year-one cost at 1,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 1,000 users, 12 months excluding VAT: from CHF 88600.40 / EUR 95919.02 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 12605.23, operations CHF 75000.00, and BYO model usage USD 2376.00. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: open-webui:open-webui:enterprise, open-webui:open-webui:cost-vm, open-webui:open-webui:cost-pg, open-webui:open-webui:cost-fx, open-webui:open-webui:cost-model, open-webui:open-webui:cost-effort.
cost_5000 Year-one cost at 5,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 5,000 users, 12 months excluding VAT: from CHF 189541.24 / EUR 205197.83 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 32214.49, operations CHF 150000.00, and BYO model usage USD 11880.00. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: open-webui:open-webui:enterprise, open-webui:open-webui:cost-vm, open-webui:open-webui:cost-pg, open-webui:open-webui:cost-fx, open-webui:open-webui:cost-model, open-webui:open-webui:cost-effort.
variable_share Which part depends on usage? [partial]: Shared mix is 60% light at 100, 30% regular at 400 and 10% power at 1,500 messages/user/month, or 330 weighted messages. Each message is 3,000 input and 600 output tokens. Direct BYO proxy is gpt-6-luna, reasoning effort none, Standard short-context uncached rates USD 0.10/0.50 per million input/output tokens. It costs USD 2.376/user/year before optional tools, embedding, caching or regional processing. This proxy is an analyst assumption, not the product default. Sources: open-webui:open-webui:cost-model, open-webui:open-webui:cost-effort.
unknown_parts Which costs could not be priced? [partial]: Unpriced additions are file/object storage beyond the assumed 500 GB PostgreSQL storage, VM OS/data disks, backup excess, egress/load balancers, Redis or additional database services, high availability, embeddings, OCR, search, audio/images, integration work and optional commercial services. Open WebUI Enterprise, branding rights outside standard exceptions and Terminals production licences are quote-only. The shared VM/PG sizes have not been load-tested and do not replace each product’s documented runtime dependencies. Sources: open-webui:open-webui:cost-vm, open-webui:open-webui:cost-pg, open-webui:open-webui:enterprise.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:enterprise, open-webui:open-webui:cost-vm, open-webui:open-webui:cost-pg, open-webui:open-webui:cost-fx, open-webui:open-webui:cost-model, open-webui:open-webui:cost-effort.

VEN-03 Evaluation access

Judgment rule: Distinguish free tier, self-serve trial, sales-led pilot, paid proof of concept and open-source self-install. Record card requirement, duration, seat limit, and which features (SSO, connectors, admin) the trial includes. Map which shared scenarios can be run without sales approval.

Dust

Agent cross-checked Support: partial

A limited Business free option enables self-serve evaluation; Enterprise features remain contract-scoped.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

free_tier Is there a free tier for business use? [supported]: Business free supports up to five members with 500 lifetime credits per Free seat. Credits do not reset and a user cannot return to Free after upgrading. Sources: dust:dust:seats.
self_serve_trial Is a self-serve business trial available? [partial]: The public site offers self-serve free workspace access, not a documented time-limited fully featured Enterprise trial. No card requirement was established. Sources: dust:dust:pricing, dust:dust:seats.
trial_scope Do trials include SSO, connectors and admin features? [partial]: Business lists up to three connectors/five Spaces/five remote MCP servers and SSO at 5+ seats on demand. SCIM, audit and custom retention are Enterprise. Sources: dust:dust:pricing.
sales_gate Does meaningful evaluation require sales contact? [supported]: Enterprise terms, pooled credits, advanced governance and support are sales-led; a small-team free evaluation is self-serve. Sources: dust:dust:pricing.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:seats, dust:dust:pricing.

Open WebUI

Agent cross-checked Support: partial

Standard self-installation permits evaluation without sales contact; Enterprise rights and services have a separate sales path.

Limitations

self_serve_trial: Docker/Python self-installation is available without a licence payment or trial clock; it is an install path rather than a vendor-operated business trial.
sales_gate: Standard self-install evaluation is possible without sales. Enterprise licensing is offered to registered entities via the sales path.

free_tier Is there a free tier for business use? [supported]: The current enterprise page permits free standard use with branding intact, including organizations. Sources: open-webui:open-webui:enterprise.
self_serve_trial Is a self-serve business trial available? [partial]: Docker/Python self-installation is available without a licence payment or trial clock; it is an install path rather than a vendor-operated business trial. Sources: open-webui:open-webui:quickstart, open-webui:open-webui:enterprise.
trial_scope Do trials include SSO, connectors and admin features? [supported]: Self-hosted authentication, administration and knowledge features can be configured for evaluation with the customer’s own infrastructure and credentials. Sources: open-webui:open-webui:quickstart, open-webui:open-webui:sso, open-webui:open-webui:knowledge.
sales_gate Does meaningful evaluation require sales contact? [partial]: Standard self-install evaluation is possible without sales. Enterprise licensing is offered to registered entities via the sales path. Sources: open-webui:open-webui:enterprise.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:enterprise, open-webui:open-webui:quickstart, open-webui:open-webui:sso, open-webui:open-webui:knowledge.

VEN-04 Contract terms and pricing transparency

Judgment rule: Record minimum seats or commitment, contract length, monthly versus annual billing, price-change rules, cancellation and downgrade terms, and invoicing in CHF/EUR. Classify pricing as transparent, partially specified, quote-only or unknown, naming the missing fields. Quote-only pricing is a disclosed constraint.

Dust

Agent cross-checked Support: partial

Business monthly and annual subscriptions are public; Enterprise seats are annual and prices contractual.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

minimum_commitment What seat or spend minimum applies? [partial]: The free option has up to five members and Business targets up to 100 people; Enterprise numerical seat/spend minimum was not established. Sources: dust:dust:pricing, dust:dust:seats.
contract_length What contract lengths are offered? [supported]: Business offers monthly and annual seats together; Enterprise seats are annual only. Sources: dust:dust:seats.
cancellation How can the contract be cancelled or reduced? [supported]: Monthly seats unassign immediately with a prorated credit; annual seats return to stock for reassignment and are not refunded when someone leaves. Sources: dust:dust:seats.
local_invoicing Can it be invoiced in CHF or EUR from a European entity? [partial]: Prices are displayed in EUR and the privacy policy identifies a French entity; CHF invoicing and the actual invoicing entity/currency were not contract-verified. Sources: dust:dust:pricing, dust:dust:privacy.
transparency_class Is pricing transparent, partial, quote-only or unknown? [supported]: Partially specified: Business seat prices/credit allowances are public, while Enterprise pricing, complete usage conversion and negotiated terms require a quote. Sources: dust:dust:pricing, dust:dust:credits.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:seats, dust:dust:privacy, dust:dust:credits.

Open WebUI

Agent cross-checked Support: partial

Standard-use licence terms are public; Enterprise pricing and negotiated contract details remain quote-only.

Limitations

minimum_commitment: No paid standard-use seat commitment is listed. The 50-user rolling window is a branding exception, not a cap on branded deployment size; Enterprise is available to registered entities.
contract_length: What contract lengths are offered? Enterprise duration, monthly/annual billing, cancellation, price-change clauses and CHF/EUR invoicing from a European entity were not established.
cancellation: How can the contract be cancelled or reduced? Enterprise duration, monthly/annual billing, cancellation, price-change clauses and CHF/EUR invoicing from a European entity were not established.
local_invoicing: Can it be invoiced in CHF or EUR from a European entity? Enterprise duration, monthly/annual billing, cancellation, price-change clauses and CHF/EUR invoicing from a European entity were not established.

minimum_commitment What seat or spend minimum applies? [partial]: No paid standard-use seat commitment is listed. The 50-user rolling window is a branding exception, not a cap on branded deployment size; Enterprise is available to registered entities. Sources: open-webui:open-webui:license-pin, open-webui:open-webui:enterprise.
contract_length What contract lengths are offered? [unknown]: contract_length: What contract lengths are offered? Enterprise duration, monthly/annual billing, cancellation, price-change clauses and CHF/EUR invoicing from a European entity were not established.
cancellation How can the contract be cancelled or reduced? [unknown]: cancellation: How can the contract be cancelled or reduced? Enterprise duration, monthly/annual billing, cancellation, price-change clauses and CHF/EUR invoicing from a European entity were not established.
local_invoicing Can it be invoiced in CHF or EUR from a European entity? [unknown]: local_invoicing: Can it be invoiced in CHF or EUR from a European entity? Enterprise duration, monthly/annual billing, cancellation, price-change clauses and CHF/EUR invoicing from a European entity were not established.
transparency_class Is pricing transparent, partial, quote-only or unknown? [supported]: Standard-use licence is disclosed; Enterprise price and service terms are quote-only in the reviewed public offer. Sources: open-webui:open-webui:enterprise.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:license-pin, open-webui:open-webui:enterprise.

VEN-05 Source licence

Judgment rule: Record licence per component (client, server, connectors, hosted extensions) and revision. Distinguish OSI open source, source-available with restrictions (branding clauses, user caps), and closed. Repository visibility is not a licence classification. Licences change between releases: record the current terms, and never carry a fork's historical licence over to the upstream product or the reverse.

Dust

Agent cross-checked Support: partial

The pinned public repository has an MIT root licence; hosted licensing and complete component coverage are separate.

Availability: generally-available · Delivery: native
Scope: surfaces=Public dust-tt/dust repository root licence; version=dust-tt/dust commit2b1a4973af824f8ff970d585c5eb1f40ae76186c; root LICENSE only; plan=Public source component, not Business/Enterprise hosted-service rights; add_ons=none stated; deployment_mode=not specified; region=Repository licence has no deployment-region entitlement; os=not specified.

Limitations

MIT applies to the pinned repository root grant only; dependencies, supported self-host deployment, hosted terms and any closed Enterprise boundary remain unverified.

licence_type Which licence applies to each component? [partial]: dust-tt/dust root LICENSE is MIT at commit 2b1a4973af824f8ff970d585c5eb1f40ae76186c. This does not classify every dependency or the contracted hosted service. Sources: dust:dust:licence.
branding_restrictions Do licence terms restrict branding or user counts? [supported]: The MIT root grant requires preserving copyright and permission notices and does not itself impose branding or user-count caps. Sources: dust:dust:licence.
enterprise_features_closed Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? The pinned root LICENSE and README were retrieved; a complete nested-component licence inventory and separate closed Enterprise edition boundary were not established. Hosted terms were inaccessible.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:licence.

Open WebUI

Agent cross-checked Support: partial

The core server at v0.12.3 uses a licence with branding restrictions. The separate Desktop v0.0.20 repository distributes GNU AGPL v3. Terminals and proprietary Enterprise component terms remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server, Open WebUI Desktop native distribution (Early Alpha); version=Core v0.12.3 / 91ea4e3421d1d8069f13d4a463fcb5986d94ea60; Desktop v0.0.20 / 601137c5dec2967cfe173a6bf071fbbb460852be; plan=Pinned core server and Desktop component licences only; no executed Enterprise agreement or pinned Terminals licence verified; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure country; external inference, extraction, search and support locations require separate configuration and contracts; os=not specified.

Limitations

The claim follows pinned component licence texts and excludes unverified Enterprise/Terminals feature-licensing assertions.
No executed branding exception or proprietary Enterprise agreement was reviewed.

licence_type Which licence applies to each component? [partial]: Core v0.12.3 is distributed under the Open WebUI License with branding conditions, so its source availability has restrictions. The separate Desktop v0.0.20 LICENSE is GNU AGPL version 3. Other component licences were not established by these two texts. Sources: open-webui:open-webui:license-pin, open-webui:open-webui:desktop-license-r2.
branding_restrictions Do licence terms restrict branding or user counts? [supported]: Core LICENSE clause 4 restricts branding changes, with exceptions for no more than 50 natural-person users in a rolling 30 days, specific prior written permission, or an executed Enterprise licence expressly permitting changes. It does not impose a 50-user cap on branded use. This answer follows that pinned text, not the FAQ contribution qualifier. Sources: open-webui:open-webui:license-pin.
enterprise_features_closed Are enterprise features in a separate closed edition? [unknown]: The core text mentions an Enterprise branding-permission exception but does not establish a separate closed edition or Terminals production terms. No relevant pinned Terminals component licence or executed Enterprise contract was reviewed; those details remain unknown.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:license-pin, open-webui:open-webui:desktop-license-r2.

VEN-06 Data export and exit

Judgment rule: Record admin export of chats, assistants, knowledge bases, prompts and audit logs, formats, export completeness, user self-export, and what survives contract end. Run an admin export on a trial. Exported chats alone do not make assistants and knowledge portable.

Dust

Agent cross-checked Support: partial

Business Conversation API and Enterprise Data Source API provide scoped data retrieval; agent export entitlement and complete tenant exit remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust APIs and MCP server, Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business Conversation API and web analytics; Enterprise adds Data Source API. Agent-YAML endpoint entitlement is unverified.; add_ons=API keys with appropriate workspace/resource permissions; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Conversation and document retrieval require the corresponding plan and resource permissions. Complete organization coverage, agent-export entitlement and the post-termination retrieval window remain unknown.

chat_export Can admins export all chats? [partial]: Business pricing includes Conversation API; authorized API users retrieve accessible conversation messages with pagination. This does not establish one-click all-tenant admin export. Sources: dust:dust:get-conversation, dust:dust:pricing.
assistant_export Can assistants and prompts be exported in a reusable format? [unknown]: The agent-YAML endpoint and public pricing were checked on 2026-10-21. Neither establishes its Business or Enterprise entitlement. Reusable assistant/prompt export for a named plan remains unknown.
knowledge_export Can knowledge bases and their sources be exported? [partial]: Enterprise pricing adds Data Source API; the documented endpoint retrieves accessible data-source documents as JSON. Complete source/credential/permission portability and an all-tenant export are unverified. Sources: dust:dust:get-document, dust:dust:pricing.
export_format Are formats documented and machine-readable? [partial]: Business Conversation API and Enterprise Data Source API return JSON for accessible resources. Web analytics separately exports CSV. These formats do not establish complete tenant export; no plan-scoped agent-YAML export is claimed. Sources: dust:dust:get-conversation, dust:dust:get-document, dust:dust:analytics, dust:dust:pricing.
post_termination_window How long can data be retrieved after termination? [unknown]: How long can data be retrieved after termination? No trial admin exit/export was run; complete tenant coverage and the post-termination retrieval window were not established from the accessible API docs or unreadable contract route.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:get-conversation, dust:dust:pricing, dust:dust:get-document, dust:dust:analytics.

Open WebUI

Agent cross-checked Support: partial

User chats, admin chat records and model definitions have machine-readable export paths. Knowledge ZIP export converts source files to text.

Limitations

assistant_export: Models have JSON export/import and sync APIs. Full portability of all bound tools, skills, external secrets and shared prompts was not tested.
knowledge_export: Admins can export a knowledge base as ZIP containing .txt conversions. Original binary fidelity and full index/configuration restoration were not established.
post_termination_window: How long can data be retrieved after termination? No admin export fixture or Enterprise post-termination retrieval period was tested/reviewed; customer-owned backups remain the operator’s responsibility.

chat_export Can admins export all chats? [supported]: Users export their history as JSON. The pinned admin all/db route returns database chat records if ENABLE_ADMIN_EXPORT is enabled. Sources: open-webui:open-webui:export, open-webui:open-webui:chats-pin.
assistant_export Can assistants and prompts be exported in a reusable format? [partial]: Models have JSON export/import and sync APIs. Full portability of all bound tools, skills, external secrets and shared prompts was not tested. Sources: open-webui:open-webui:api.
knowledge_export Can knowledge bases and their sources be exported? [partial]: Admins can export a knowledge base as ZIP containing .txt conversions. Original binary fidelity and full index/configuration restoration were not established. Sources: open-webui:open-webui:knowledge.
export_format Are formats documented and machine-readable? [supported]: Chat/model JSON schemas and APIs and knowledge text ZIP output are documented. Sources: open-webui:open-webui:export, open-webui:open-webui:api, open-webui:open-webui:knowledge.
post_termination_window How long can data be retrieved after termination? [unknown]: post_termination_window: How long can data be retrieved after termination? No admin export fixture or Enterprise post-termination retrieval period was tested/reviewed; customer-owned backups remain the operator’s responsibility.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:export, open-webui:open-webui:chats-pin, open-webui:open-webui:api, open-webui:open-webui:knowledge.

VEN-07 Support and service levels

Judgment rule: Record support channels, languages (German, French, Italian), hours and time zone, local or regional presence, documented response times, uptime SLA and credits, public status page and incident history. Popularity is not a reliability score.

Dust

Agent cross-checked Support: partial

Business email support and Enterprise priority/SLA service are advertised; credit terms and local-language support remain open.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

support_channels Which support channels are available on each plan? [supported]: Pricing lists Business email and Enterprise priority support with dedicated CSM; public support/community resources are available. Sources: dust:dust:pricing, dust:dust:support.
support_languages Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Support/pricing/Enterprise pages and the official status URL were checked. German/French/Italian staffed support and detailed credited SLA terms were not established.
regional_presence Is there a DACH or Swiss entity, team or partner? [partial]: The public policy identifies a Paris, France entity. A DACH/Swiss support team or named regional partner was not established. Sources: dust:dust:privacy.
uptime_sla Is there an uptime SLA with credits? [partial]: Enterprise marketing claims 99.9% uptime and pricing includes an SLA; service-credit amounts, exclusions and claim rules were not retrieved. Sources: dust:dust:enterprise, dust:dust:pricing.
status_page Is there a public status page with history? [partial]: Model-selection docs link https://dust.statuspage.io for incidents. Direct retrieval timed out, so incident history was not verified. Sources: dust:dust:models.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:support, dust:dust:privacy, dust:dust:enterprise, dust:dust:models.

Open WebUI

Agent cross-checked Support: partial

Enterprise support advertises dedicated channels, account management and engineering office hours; public response/credit terms were not established.

Limitations

support_languages: Is support available in German, French or Italian? DE/FR/IT support coverage, support hours/time zone, CH/DACH contracting/partner presence and a product status-history page were not established in the support/enterprise and roadmap pass.
regional_presence: Is there a DACH or Swiss entity, team or partner? DE/FR/IT support coverage, support hours/time zone, CH/DACH contracting/partner presence and a product status-history page were not established in the support/enterprise and roadmap pass.
uptime_sla: The support page refers to negotiated SLAs, but publishes no reviewed uptime percentage, response commitment or service-credit schedule.
status_page: Is there a public status page with history? DE/FR/IT support coverage, support hours/time zone, CH/DACH contracting/partner presence and a product status-history page were not established in the support/enterprise and roadmap pass.

support_channels Which support channels are available on each plan? [supported]: Enterprise customers can obtain dedicated support channels and an account manager; community development/support uses public GitHub and community channels. Sources: open-webui:open-webui:support, open-webui:open-webui:roadmap.
support_languages Is support available in German, French or Italian? [unknown]: support_languages: Is support available in German, French or Italian? DE/FR/IT support coverage, support hours/time zone, CH/DACH contracting/partner presence and a product status-history page were not established in the support/enterprise and roadmap pass.
regional_presence Is there a DACH or Swiss entity, team or partner? [unknown]: regional_presence: Is there a DACH or Swiss entity, team or partner? DE/FR/IT support coverage, support hours/time zone, CH/DACH contracting/partner presence and a product status-history page were not established in the support/enterprise and roadmap pass.
uptime_sla Is there an uptime SLA with credits? [partial]: The support page refers to negotiated SLAs, but publishes no reviewed uptime percentage, response commitment or service-credit schedule. Sources: open-webui:open-webui:support.
status_page Is there a public status page with history? [unknown]: status_page: Is there a public status page with history? DE/FR/IT support coverage, support hours/time zone, CH/DACH contracting/partner presence and a product status-history page were not established in the support/enterprise and roadmap pass.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:support, open-webui:open-webui:roadmap.

VEN-08 Onboarding, training and adoption

Judgment rule: Record vendor-led onboarding, admin training, end-user training (live, e-learning, languages), use-case libraries, champion programmes, change-management materials and their cost. Distinguish included services from paid professional services and partner offerings.

Dust

Agent cross-checked Support: partial

Dust has rollout and training material, with hands-on support packaged for Enterprise.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Public learning material (no paid entitlement required to read); contracted CSM/onboarding is Enterprise; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

Documented findings only; unestablished atomic questions remain explicit gaps.

onboarding_service Is guided onboarding included? [supported]: Enterprise pricing includes dedicated CSM and onboarding; exact hours and scope are contractual. Sources: dust:dust:pricing.
user_training Is end-user training offered, in which languages? [partial]: Public team onboarding and education resources are available. Course/live-session language coverage was not established. Sources: dust:dust:training, dust:dust:rollout.
use_case_library Are role-based use cases and templates provided? [supported]: The public Use Cases and Guides index lists departmental guides for Sales, Support, Marketing, Engineering, Data Analytics, Knowledge, People, Product and Collaboration; the Sales guide supplies concrete agent examples and build links. This establishes public role-based guidance, not a separately verified in-product template entitlement. Sources: dust:dust:r2-department-guides, dust:dust:r2-sales-guide.
adoption_programme Is there a champion or adoption programme? [partial]: The rollout guide covers launch, builder community, education and expansion; a contracted champion programme entitlement was not established. Sources: dust:dust:rollout.
service_cost Which services cost extra? [partial]: Hands-on CSM/onboarding is Enterprise packaging; a numerical professional-services tariff was not established. Sources: dust:dust:pricing.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:training, dust:dust:rollout, dust:dust:r2-department-guides, dust:dust:r2-sales-guide.

Open WebUI

Agent cross-checked Support: partial

Enterprise guidance includes onboarding and engineering advice. Paid hands-on implementation and training terms need separate scoping.

Limitations

onboarding_service: Enterprise account management advertises onboarding guidance, with package inclusion and cost unspecified.
user_training: Is end-user training offered, in which languages? No vendor training languages/curriculum, champion programme or priced change-management package was established.
use_case_library: Documentation provides assistant examples and Open Terminal use cases. A full workforce training/adoption curriculum was not established.
adoption_programme: Is there a champion or adoption programme? No vendor training languages/curriculum, champion programme or priced change-management package was established.
service_cost: Enterprise support is separately arranged; the team describes guidance rather than implementation services and recommends a systems integrator or internal team for hands-on work. Public rates were not established.

onboarding_service Is guided onboarding included? [partial]: Enterprise account management advertises onboarding guidance, with package inclusion and cost unspecified. Sources: open-webui:open-webui:support.
user_training Is end-user training offered, in which languages? [unknown]: user_training: Is end-user training offered, in which languages? No vendor training languages/curriculum, champion programme or priced change-management package was established.
use_case_library Are role-based use cases and templates provided? [partial]: Documentation provides assistant examples and Open Terminal use cases. A full workforce training/adoption curriculum was not established. Sources: open-webui:open-webui:models, open-webui:open-webui:terminal.
adoption_programme Is there a champion or adoption programme? [unknown]: adoption_programme: Is there a champion or adoption programme? No vendor training languages/curriculum, champion programme or priced change-management package was established.
service_cost Which services cost extra? [partial]: Enterprise support is separately arranged; the team describes guidance rather than implementation services and recommends a systems integrator or internal team for hands-on work. Public rates were not established. Sources: open-webui:open-webui:support.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:support, open-webui:open-webui:models, open-webui:open-webui:terminal.

Sources

Auto models and the model picker dust:dust:models
Users select a model per message or agent; auto choices use maintained ordered lists rather than task-based routing.
Auto model lists; availability; API overrides · documented · Source date not stated · Retrieved 2026-10-21
EU-hosted models dust:dust:eu-models
EU credit-plan workspaces using Dust model hosting can restrict agents and auto choices to EU-hosted models; BYOK is excluded from this setting.
Availability; supported/excluded model table · documented · Source date not stated · Retrieved 2026-10-21
Dust changelog dust:dust:changelog
Recent dated changes include German/French UI, Gemini 4 Argon and migration from File Generation to Computer.
October 21, 16 and 14, 2026 entries · documented · Source date 2026-10-21 · Retrieved 2026-10-21
Conversation Files dust:dust:files
Conversation uploads are scoped to one conversation and support documents, tabular data, images and audio.
Formats; size table; generating files · documented · Source date not stated · Retrieved 2026-10-21
Dust Pricing dust:dust:pricing
Business supports up to 100 people with Free/Pro/Max seats; Enterprise pricing is sales-led and adds pooled credits, SCIM, audit, single tenancy and support.
Business/Enterprise table and FAQ · documented · Source date not stated · Retrieved 2026-10-21
Connect local and cloud models open-webui:open-webui:provider
Administrators connect model endpoints; the selected endpoint determines inference location, including for attached context.
How it works; Cloud Providers; Local Servers · documented · Source date not stated · Retrieved 2026-10-21
OpenAI-compatible providers open-webui:open-webui:compat
The guide documents compatible cloud gateways and local inference servers, with provider-specific capability differences.
Provider configuration and provider examples · documented · Source date not stated · Retrieved 2026-10-21
Retrieval augmented generation open-webui:open-webui:rag
Document retrieval uses configured embeddings and chunks or full context, with citations and a Google Drive file picker.
Embedding support; Citations; Google Drive integration; per-file retrieval mode · documented · Source date not stated · Retrieved 2026-10-21
Document extraction open-webui:open-webui:extraction
Configurable extraction engines can process scanned documents; browser-only temporary extraction has format limitations.
Available extraction methods; temporary chat limitation · documented · Source date not stated · Retrieved 2026-10-21
OpenAI and Azure OpenAI connections open-webui:open-webui:openai
Customers configure their own OpenAI keys or Azure endpoint, deployment IDs and API version.
Azure OpenAI tab; Advanced Configuration · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI release notes open-webui:open-webui:releases
Dated releases document shipped changes, including v0.12.3 Drive scope reduction and encrypted private-channel chats.
v0.12.3, 2026-10-16; v0.12.2; v0.12.1 · documented · Source date 2026-10-16 · Retrieved 2026-10-21
Models workspace open-webui:open-webui:models
Model presets combine instructions, model, knowledge, tools and skills, with access grants and saved versions.
Presets; Access; Builtin Tools; System prompts · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI for enterprise open-webui:open-webui:enterprise
Branding-intact internal use is free; enterprise branding rights, support and exclusive offerings require a separate licence.
Licence requirements; Deployment; Support · documented · Source date not stated · Retrieved 2026-10-21
Memory and personalization open-webui:open-webui:memory
Users manage persistent memories; administrators can disable the feature or restrict groups, including server-side use.
Manual management; Administrative controls; Privacy · documented · Source date not stated · Retrieved 2026-10-21
Run Open WebUI offline open-webui:open-webui:offline
Disconnected operation requires prepared local models, embeddings and extraction; internet APIs and tools remain external dependencies.
Local prerequisites; disabled online functionality; verification · documented · Source date not stated · Retrieved 2026-10-21
Model access tiers dust:dust:tiers
Admins restrict models and reasoning efforts at workspace, group or member level, with a separate published-agent bypass setting.
Workspace, group and individual ceilings · documented · Source date not stated · Retrieved 2026-10-21
Spaces management dust:dust:spaces
Spaces control knowledge and agent access; Business allows five and Enterprise 100 spaces.
Open/restricted spaces; limits; visibility · documented · Source date not stated · Retrieved 2026-10-21
Credits dust:dust:credits
Consumption adds token and tool credits; a 600-AWU checkpoint can pause user-started root tasks, with exceptions.
Token/action credits; checkpoints · documented · Source date not stated · Retrieved 2026-10-21
Credit management dust:dust:credit-management
Credit sources and block behavior vary by plan; beta Enterprise Pooled group budgets exclude programmatic consumption.
Personal caps; group budgets; programmatic use · documented · Source date not stated · Retrieved 2026-10-21
Knowledge bases and document chat open-webui:open-webui:knowledge
Persistent knowledge bases support scoped access, model attachment, incremental directory sync and admin text-file ZIP export.
Retrieval modes; Sharing; Syncing; Export; API · documented · Source date not stated · Retrieved 2026-10-21
Groups open-webui:open-webui:groups
User and group grants control resources; permissions accumulate across groups rather than deny access.
Additive permissions; Resource Access; Nested Groups · documented · Source date not stated · Retrieved 2026-10-21
Chat data privacy and encryption open-webui:open-webui:privacy
The deployer controls storage, encryption, logs, backups and provider connections; product admin restrictions do not prevent host-operator access.
Controls by concern; encryption; operators; model providers · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI v0.12.4 filter implementation open-webui:open-webui:r4-filter-implementation
The backend dispatches installed filter handlers with user context and propagates inlet failures. It does not itself provide a configured recurring quota or managed PII policy.
process_filter_function; process_filter_functions; inlet exception propagation · source-inspected · Source date 2026-10-25 · Retrieved 2026-10-26
Commit 33c1978d5bad52a31df75ea55143025dfad18d16, path backend/open_webui/utils/filter.py
Open WebUI filter functions open-webui:open-webui:r4-rate-limit-example
The official optional Python example counts requests per user and raises at its configurable per-minute threshold. This sample uses in-process state and is not an enabled product-wide quota or monetary budget.
Example: Rate Limiting for All Requests · documented · Source date not stated · Retrieved 2026-10-26
File size limits dust:dust:file-limits
The dedicated limits FAQ gives different image, audio and tabular caps than Conversation Files and excludes direct video uploads.
Upload caps; audio-only restriction · documented · Source date not stated · Retrieved 2026-10-21
Computer dust:dust:computer
Computer executes code in temporary workspaces, handles Office/PDF files, performs documented OCR and restricts network access by allowlist.
File work; OCR; network control; secrets · documented · Source date not stated · Retrieved 2026-10-21
Google Drive dust:dust:drive
Drive sync follows a dedicated connection account and selected content; scanned documents need conversation upload for OCR and Excel table queries need conversion to Sheets.
Connection identity; refresh; OCR; spreadsheet limitations · documented · Source date not stated · Retrieved 2026-10-21
Search data sources dust:dust:search
Agents search selected knowledge sources and retrieve relevant document context.
Document selection; retrieval · documented · Source date not stated · Retrieved 2026-10-21
Environment variable configuration open-webui:open-webui:env
Administrators configure document limits, accepted extensions, audio engines and instance settings.
RAG_FILE_MAX_SIZE; RAG_FILE_MAX_COUNT; RAG_ALLOWED_FILE_EXTENSIONS; audio; system prompt · documented · Source date not stated · Retrieved 2026-10-21
Access Controls and Permissions dust:dust:permissions
Knowledge access is organized through admin-selected connection content and membership of open/restricted Spaces.
Access policy; connection account; Spaces · documented · Source date not stated · Retrieved 2026-10-21
Microsoft dust:dust:microsoft
Microsoft data is scoped to the connecting account and selected SharePoint sources; changes synchronize on a five-minute cycle.
Connection account; delegated and service-principal setup; sync · documented · Source date not stated · Retrieved 2026-10-21
Confluence dust:dust:confluence
Confluence sync covers selected global spaces, excluding private spaces and pages with view restrictions.
Scope; restricted pages; refresh · documented · Source date not stated · Retrieved 2026-10-21
Beta: Import Jira issues dust:dust:jira
A separately documented beta route imports Jira issues as a custom connection.
Import path · documented · Source date not stated · Retrieved 2026-10-21
What data sources can be connected to Dust? dust:dust:sources
Official guides identify managed connections and custom API/import routes.
Named sources · documented · Source date not stated · Retrieved 2026-10-21
Adding an MCP Server dust:dust:tools
Admins add remote MCP servers with OAuth or bearer credentials and can restrict tools to skills.
Remote/custom servers; auth; tool restriction · documented · Source date not stated · Retrieved 2026-10-21
Dust BigQuery connection dust:dust:r2-bigquery
Dust stores BigQuery metadata and runs table queries through a dedicated service account; dataset content is not synchronized into the index.
No content sync; service-account setup, one location and Space table selection · documented · Source date not stated · Retrieved 2026-10-21
OneDrive and SharePoint open-webui:open-webui:onedrive
Users attach Microsoft files through a delegated file picker; the guide requires tenant app registration and admin consent.
Work/school app registration; delegated API permissions; admin consent · documented · Source date not stated · Retrieved 2026-10-21
Knowledge base sync, oikb open-webui:open-webui:sync
The separate official CLI and daemon copies sources into Open WebUI knowledge bases and propagates changes during sync.
Overview; connectors; scheduling; incremental sync · documented · Source date not stated · Retrieved 2026-10-21
Model Context Protocol open-webui:open-webui:mcp
Native remote MCP is administrator-configured Streamable HTTP with shared credentials or user OAuth modes.
Streamable HTTP; Why admins only; Authentication modes · documented · Source date not stated · Retrieved 2026-10-21
oikb connector credentials and deployment boundary open-webui:open-webui:sync-connectors-r2
The separate official oikb program lists Teams and Gmail with source credentials; it writes into knowledge bases using an Open WebUI user API key.
Install; Sources and connectors: SharePoint, Microsoft Teams, Google Drive, Gmail; Access is your access · documented · Source date not stated · Retrieved 2026-10-21
Personal vs Shared Credentials for Tools & MCP Servers dust:dust:credentials
Tools can use a shared account or each user OAuth identity; even personal auth needs initial admin setup.
Shared versus personal authentication · documented · Source date not stated · Retrieved 2026-10-21
Dust Security dust:dust:security
Dust claims EU/US hosting, AES-256/TLS, no model training, provider zero retention and SOC 2 Type II.
Hosting, training, encryption and certification statements · vendor-claimed · Source date not stated · Retrieved 2026-10-21
Deep-dive Agent dust:dust:deep
Deep-dive plans, delegates and writes cited reports, using Company Data knowledge and selected tools; Table Query is excluded.
Research flow; citations; limitations · documented · Source date not stated · Retrieved 2026-10-21
Agent Memory dust:dust:memory
Enabled agents retain user-private memory across conversations; users can view and delete it and it persists until deletion.
Adding the tool; viewing/deleting; privacy · documented · Source date not stated · Retrieved 2026-10-21
Create your first agent dust:dust:builder
Agents combine instructions, models, knowledge and tools with controlled sharing.
Instructions; tools; sharing · documented · Source date not stated · Retrieved 2026-10-21
Workspace Governance: Roles, Groups & Permissions dust:dust:governance
Admins delegate manager/group permissions for agents, skills, models, billing and security; grants are additive.
Roles; permission matrix; additive access · documented · Source date not stated · Retrieved 2026-10-21
Permissions open-webui:open-webui:permissions
Feature and resource permissions cover models, knowledge, prompts, tools, search, images, files and memories.
Workspace and feature permission tables · documented · Source date not stated · Retrieved 2026-10-21
Tools open-webui:open-webui:tools
Tools may run through Python, OpenAPI or MCP, and an optional approval mode stops calls until the user allows or denies them.
Native tools and OpenAPI; Tool call approval · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI experimental tool permissions open-webui:open-webui:approvals-r2
Tool Permissions is experimental and disabled by default; interactive approvals can wait, but automations and channel replies always use full access.
Tool Approval: ENABLE_TOOL_PERMISSIONS, Full access, Ask for approval, Stop, saved/temporary chats and exceptions · documented · Source date not stated · Retrieved 2026-10-21
Web Search & Browse dust:dust:web
The tool runs Google queries and browses results, with agent-level configuration and format options.
Search and browsing flow · documented · Source date not stated · Retrieved 2026-10-21
Web search open-webui:open-webui:web
Search uses an administrator-configured provider and can add external sources to a conversation.
Enabling and using web search; providers · documented · Source date not stated · Retrieved 2026-10-21
Agentic web search and URL fetching open-webui:open-webui:agent-search
Tool-capable models can repeatedly search and fetch pages, with results and citations in the conversation.
Native function calling; search and fetch tools · documented · Source date not stated · Retrieved 2026-10-21
Triggers dust:dust:triggers
Agents can run automatically from schedule or event triggers.
Schedules and events · documented · Source date not stated · Retrieved 2026-10-21
Schedules dust:dust:schedules
Agents can run on recurring schedules.
Schedule setup · documented · Source date not stated · Retrieved 2026-10-21
Webhooks dust:dust:webhooks
Admins configure webhook sources; members attach filtered triggers to agents, with optional signature verification for custom sources.
Built-in and custom event sources · documented · Source date not stated · Retrieved 2026-10-21
Automations open-webui:open-webui:automation
Recurring prompts run on the customer server through the normal chat pipeline and remain private to their owner.
Schedules; Access Control; Runtime behavior · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI v0.12.4 event dispatch open-webui:open-webui:r4-event-dispatch
Configured Event functions receive published system events and can run developer-written handlers. Event payload field sanitization is not a general prompt/file PII detection service.
build_event; dispatch_event_functions; EventFunctionSink · source-inspected · Source date 2026-10-25 · Retrieved 2026-10-26
Commit 33c1978d5bad52a31df75ea55143025dfad18d16, path backend/open_webui/events.py
Open WebUI v0.12.4 channel webhooks open-webui:open-webui:r4-incoming-channel-webhook
A token-validated incoming webhook creates a channel message and publishes MESSAGE_CREATED with source channel_webhook. A configured Event handler can respond to this external input; no no-code workflow engine is implied.
post_webhook_message, lines 2283-2361 · source-inspected · Source date 2026-10-25 · Retrieved 2026-10-26
Commit 33c1978d5bad52a31df75ea55143025dfad18d16, path backend/open_webui/routers/channels.py
Pods overview dust:dust:pods
Pods combine shared conversations, tasks and files; open Pods are workspace-browsable and restricted Pods require invitation.
Shared workspace and visibility · documented · Source date not stated · Retrieved 2026-10-21
Open Terminal open-webui:open-webui:terminal
The separately deployed Open Terminal gives agents file, shell and code tools, including analysis and chart creation.
Agent loop; Data analysis; Document processing · documented · Source date not stated · Retrieved 2026-10-21
API keys dust:dust:api-keys
Dust API keys have read/admin scopes, data access and enforceable per-key monthly caps.
Scopes; Space access; caps · documented · Source date not stated · Retrieved 2026-10-21
Dust MCP Server dust:dust:mcp-server
Dust exposes workspace knowledge, agents, conversations, files and Pods to OAuth MCP clients under the authenticated user permissions.
Region URLs; OAuth; user permissions · documented · Source date not stated · Retrieved 2026-10-21
Upsert a document in a data source dust:dust:upsert
The API loads or updates documents in a scoped data source.
Endpoint and authentication · documented · Source date not stated · Retrieved 2026-10-21
Get a conversation dust:dust:get-conversation
The API retrieves accessible conversation messages with pagination.
Response schema · documented · Source date not stated · Retrieved 2026-10-21
API endpoints open-webui:open-webui:api
Authenticated APIs expose chat, tool use, file ingestion, knowledge attachment and model configuration export.
Authentication; chat completions; tools; files; models export · documented · Source date not stated · Retrieved 2026-10-21
Hardening Open WebUI open-webui:open-webui:hardening
Optional request logging has configurable bodies, path exclusions, file rotation and stdout output; deployment operators own log handling.
Audit logging; output; path filtering; reverse proxy · documented · Source date not stated · Retrieved 2026-10-21
Browser Extension dust:dust:browser
An official extension supports Chrome, Firefox and Chromium-based browsers.
Browsers and capabilities · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI Desktop installation route open-webui:open-webui:desktop-quickstart-r2
Quick Start links the native desktop distribution as a route without Docker/manual setup and recommends Docker or Python for production.
Desktop App section and production-install note · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI Desktop v0.0.20 documentation open-webui:open-webui:desktop-readme-r2
The pinned Desktop README labels the app Early Alpha, lists macOS/Windows/Linux installers and describes local execution or a connection to an existing server.
Early Alpha; Download table; How It Works; System Requirements · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI Desktop v0.0.20 release assets open-webui:open-webui:desktop-release-r2
The 2026-05-06 release includes macOS and Windows x64/ARM64 installers plus Linux packages; its notes describe a Linux blank-webview fix.
published_at; assets[].name; release body · documented · Source date 2026-05-06 · Retrieved 2026-10-21
Open WebUI browser PWA installation open-webui:open-webui:pwa-r2
The web interface can also be installed as a desktop/mobile browser PWA; PWA notifications require it to stay open.
Desktop browser installation; Android; iOS; notification limitation · documented · Source date not stated · Retrieved 2026-10-21
Dust in Teams dust:dust:teams
An official Teams integration runs Dust agents within Microsoft Teams after admin setup.
Setup and usage · documented · Source date not stated · Retrieved 2026-10-21
Notes open-webui:open-webui:notes
Notes provide rich text and Markdown editing with AI rewrites and full-content attachment to chats.
Rich editor; AI editing · documented · Source date not stated · Retrieved 2026-10-21
Image Generation dust:dust:images
Agents generate images from text or references, up to 14 reference images, with SynthID and content restrictions.
Reference images; parallel generation; safety · documented · Source date not stated · Retrieved 2026-10-21
Image generation open-webui:open-webui:images
Image providers include OpenAI, Gemini, ComfyUI and AUTOMATIC1111.
Provider list · documented · Source date not stated · Retrieved 2026-10-21
Generate and edit images in chat open-webui:open-webui:image-usage
Image generation and editing require configured providers, feature permissions and model capability toggles.
Availability conditions; Editing; Compositing · documented · Source date not stated · Retrieved 2026-10-21
Voice and sound generation dust:dust:speech
The speech tool generates MP3 narration or multi-speaker dialogue with selectable languages and styles.
Speech Generator · documented · Source date not stated · Retrieved 2026-10-21
Meeting transcripts dust:dust:meetings
Dust consumes transcripts from connected notetaker and sales tools; Gong private transcripts are excluded.
Providers and scope · documented · Source date not stated · Retrieved 2026-10-21
Voice mode open-webui:open-webui:voice
Voice mode combines configured STT and TTS or a separately configured OpenAI-compatible realtime service.
Standard mode; Realtime calls; Audio settings · documented · Source date not stated · Retrieved 2026-10-21
Frames overview dust:dust:frames
Frames provide persistent interactive agent output that can be refined and shared.
Creating and editing interactive content · documented · Source date not stated · Retrieved 2026-10-21
Pod conversations dust:dust:pod-chats
All Pod members can read and contribute to Pod conversations, which are automatically indexed.
Visibility; indexing; participation · documented · Source date not stated · Retrieved 2026-10-21
Channels open-webui:open-webui:channels
Channels support multi-person collaboration and AI participation, with channel access controls.
Shared channels and direct messages · documented · Source date not stated · Retrieved 2026-10-21
Import and export open-webui:open-webui:export
Users export their conversation history in documented JSON and can import compatible records.
Exporting all chats; JSON schema · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI locale registration open-webui:open-webui:i18n-pin
The pinned client registers English, German, French and Italian interface locales; this does not establish translation quality.
src/lib/i18n/locales/languages.json, en-US, de-DE, fr-FR, it-IT entries · source-inspected · Source date not stated · Retrieved 2026-10-21
Commit 91ea4e3421d1d8069f13d4a463fcb5986d94ea60, path src/lib/i18n/locales/languages.json
Open WebUI v0.12.4 German translations open-webui:open-webui:r4-german-admin-translations
The distributed German translation file includes administrator and user-management labels. This establishes partial German admin localization, not completeness, naturalness or accessibility conformance.
Admin Panel, Admin, Add User, Change User Role and settings entries · source-inspected · Source date 2026-10-25 · Retrieved 2026-10-26
Commit 33c1978d5bad52a31df75ea55143025dfad18d16, path src/lib/i18n/locales/de-DE/translation.json
Single Sign-On dust:dust:sso
Admins configure and enforce SAML SSO, which disables other social sign-in paths for the workspace.
Setup; enforcement · documented · Source date not stated · Retrieved 2026-10-21
Dust for Enterprise dust:dust:enterprise
The Enterprise marketing page claims 365-day audit retention, 99.9% uptime and support for 10,000+ users.
Security and scale · vendor-claimed · Source date not stated · Retrieved 2026-10-21
Roles open-webui:open-webui:roles
Admins can manage the system and normally bypass resource grants; environment controls can restrict product-level chat access.
Admin; User; Pending; privacy controls · documented · Source date not stated · Retrieved 2026-10-21
SSO, OAuth, OIDC and trusted header open-webui:open-webui:sso
OAuth/OIDC providers and trusted authentication proxies support account creation and login-time group synchronization.
Provider setup; OAuth group management; account creation · documented · Source date not stated · Retrieved 2026-10-21
Two-factor sign-in open-webui:open-webui:mfa
Built-in authenticator-based sign-in can be required, with explicit configuration for OAuth bypass.
Administrative configuration; OAuth bypass · documented · Source date not stated · Retrieved 2026-10-21
Users and groups provisioning dust:dust:provision
Enterprise SCIM creates, updates and deactivates users and syncs groups; groups can grant Admin/Manager roles.
SCIM 2.0; group role mapping · documented · Source date not stated · Retrieved 2026-10-21
Seat management dust:dust:seats
Admins assign independent roles and Free/Pro/Max seats; annual stock and already-allocated credits have specific reclaim rules.
Seat assignments; billing cycles; leaving · documented · Source date not stated · Retrieved 2026-10-21
SCIM 2.0 support open-webui:open-webui:scim
SCIM provisions users and groups; deactivation maps ordinary accounts to pending and ends live connections.
Overview; User Operations; Deprovisioning; Group Operations · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI SCIM bearer authentication recheck open-webui:open-webui:r7-scim-bearer-doc
The guide configures SCIM through environment variables, including SCIM_ENABLED and SCIM_TOKEN bearer authentication. It documents no user-selectable token-scope control; account visibility rules are distinct from token scopes.
Configuration; Environment Variables; SCIM API Configuration; Security Considerations · documented · Source date not stated · Retrieved 2026-10-26
Open WebUI v0.12.4 SCIM authentication open-webui:open-webui:r7-scim-bearer-code
The pinned authentication function checks Bearer header format, whether SCIM is enabled, and a constant-time comparison with the configured SCIM_TOKEN. The inspected authentication path exposes no per-token selectable scopes.
get_scim_auth, lines 251-297 · source-inspected · Source date 2026-10-25 · Retrieved 2026-10-26
Commit 33c1978d5bad52a31df75ea55143025dfad18d16, path backend/open_webui/routers/scim.py
Analytics dust:dust:analytics
Consumption reports break down users, groups, models, tools, agents and Pods; exports omit message content and can double-attribute group usage.
Attribution; CSV; content exclusion · documented · Source date not stated · Retrieved 2026-10-21
Analytics open-webui:open-webui:analytics
Admin analytics reports messages and provider-reported tokens by users, models and groups and exposes an export API.
User and model tables; Group filters; Export; Privacy · documented · Source date not stated · Retrieved 2026-10-21
Audit Logs dust:dust:audit
Enterprise logs distinguish users, API keys and system actors with CSV and continuous SIEM delivery.
Enterprise scope; actor types; SIEM · documented · Source date not stated · Retrieved 2026-10-21
Enterprise security open-webui:open-webui:security
The page describes deployment controls and states that compliance responsibility remains with the deploying organization.
Regulatory frameworks; data governance · documented · Source date not stated · Retrieved 2026-10-21
Filter functions open-webui:open-webui:filter
Administrators can install custom Python filters in the model request path; behavior depends on the installed filter.
Filter lifecycle and extension examples · documented · Source date not stated · Retrieved 2026-10-21
Customizable banners open-webui:open-webui:banners
Admins can display instance banners; a banner is not evidence of a mandatory recorded policy acknowledgement.
Configuration and dismissible banners · documented · Source date not stated · Retrieved 2026-10-21
Dust Platform Privacy Policy dust:dust:privacy
The policy identifies Permutation Labs in Paris and distinguishes its controller processing from customer processor processing, with non-EEA transfer safeguards.
About Us; sections 2, 6 and 7 · documented · Source date not stated · Retrieved 2026-10-21
Quick start open-webui:open-webui:quickstart
The software is self-installable with Docker or Python and keeps state in customer-controlled storage.
Docker; pip; data volume · documented · Source date not stated · Retrieved 2026-10-21
Dust Platform Privacy Policy dust:dust:training-policy
The policy asserts listed providers do not train, retain or log Customer Content for human review; this source pass did not retrieve the customer DPA.
Section 6, Foundational Model Providers · vendor-claimed · Source date not stated · Retrieved 2026-10-21
Can I delete or rename a conversation? dust:dust:delete-chat
Users can delete or rename their conversations.
Conversation actions · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI chat data access boundary open-webui:open-webui:secrecy-access
The privacy guide identifies application, infrastructure operators and configured model providers as content-access trust boundaries; admin UI controls do not remove infrastructure access.
Who Can Read Chat Data?; What Encryption Protects; informational-content disclaimer · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI for law firms open-webui:open-webui:secrecy-legal
The law-firm page describes customer-operated storage/routing and links technical guidance and US ABA materials; it is general product guidance.
Materials for risk, KM, security, and legal ops review; FAQ: confidential matter information and uploaded files · vendor-claimed · Source date not stated · Retrieved 2026-10-21
Open WebUI enterprise support open-webui:open-webui:secrecy-support
Enterprise support describes advisory engineering access, dedicated channels and SLAs, with contractual commitments dependent on applicable terms.
Support Capabilities; Consulting Topics; For Procurement & Legal; informational-content disclaimer · documented · Source date not stated · Retrieved 2026-10-21
Terminals orchestrator open-webui:open-webui:terms
The separate per-user terminal orchestration layer requires an Open WebUI Enterprise licence for production.
Prerequisites; Licensing · documented · Source date not stated · Retrieved 2026-10-21
ECB historical euro reference rates dust:dust:fx-ecb
EUR 1 = USD 1.1215 = CHF 0.9237 on October 20, 2026.
Cube time=2026-10-20, USD and CHF · documented · Source date 2026-10-20 · Retrieved 2026-10-21
Azure Retail Prices, Switzerland North Linux VMs open-webui:open-webui:cost-vm
EUR hourly PAYG rates retrieved 2026-10-21 are 0.2226, 0.4453 and 0.8905 for D4s, D8s and D16s v5 respectively.
Consumption; Virtual Machines Dsv5 Series; Standard_D4s_v5/D8s_v5/D16s_v5 · documented · Source date not stated · Retrieved 2026-10-21
Azure Retail Prices, PostgreSQL Flexible Server open-webui:open-webui:cost-pg
EUR hourly PAYG GP compute is 0.2288, 0.4576 and 0.9152 for 2/4/8 vCore; storage is EUR 0.1325 per GB-month.
General Purpose Ddsv5 Series Compute, 2/4/8 vCore; Flex Server Storage · documented · Source date not stated · Retrieved 2026-10-21
ECB euro reference rate history open-webui:open-webui:cost-fx
The 2026-10-20 reference rates are EUR 1 = USD 1.1215 and CHF 0.9237.
Cube time=2026-10-20; USD and CHF · documented · Source date 2026-10-20 · Retrieved 2026-10-21
OpenAI API pricing open-webui:open-webui:cost-model
Standard gpt-6-luna API price is USD 0.10 per million input tokens and USD 0.50 per million output tokens; caching, batch and regional premiums are separate.
Standard, short-context gpt-6-luna row · documented · Source date not stated · Retrieved 2026-10-21
GPT-6 Luna model documentation open-webui:open-webui:cost-effort
The model accepts reasoning effort none, the lowest documented effort, and lists the same standard text-token rates.
Reasoning effort and text-token pricing · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI v0.12.3 licence open-webui:open-webui:license-pin
The pinned licence preserves notices and restricts branding changes, with exceptions for up to 50 rolling-30-day users, prior written permission or enterprise permission.
LICENSE, clauses 1-4; prior-licence reservation · documented · Source date not stated · Retrieved 2026-10-21
Dust repository LICENSE at pinned commit dust:dust:licence
The pinned public repository root licence is MIT; hosted service terms and third-party components are separate.
Root LICENSE, MIT permission grant · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI Desktop v0.0.20 licence open-webui:open-webui:desktop-license-r2
The separately packaged Desktop repository distributes GNU AGPL version 3 licence text at its v0.0.20 revision.
LICENSE heading and GNU Affero General Public License version 3 text · documented · Source date not stated · Retrieved 2026-10-21
Retrieve a document from a data source dust:dust:get-document
The API retrieves a source document; this does not establish a complete one-click tenant export.
Endpoint and response · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI admin chat export implementation open-webui:open-webui:chats-pin
The admin-only all/db route returns chat records when ENABLE_ADMIN_EXPORT is enabled.
backend/open_webui/routers/chats.py, get_all_user_chats_in_db, lines 1113-1117 · source-inspected · Source date not stated · Retrieved 2026-10-21
Commit 91ea4e3421d1d8069f13d4a463fcb5986d94ea60, path backend/open_webui/routers/chats.py
Dust Support dust:dust:support
The vendor provides public support entry points and community/documentation resources.
Support channels · documented · Source date not stated · Retrieved 2026-10-21
Support and SLAs open-webui:open-webui:support
Enterprise support advertises account management and engineering guidance, while hands-on implementation remains with the customer or integrator.
Account manager; Office hours; Consulting; guidance scope · documented · Source date not stated · Retrieved 2026-10-21
Open WebUI roadmap open-webui:open-webui:roadmap
Budget controls, broader localization and accessibility appear on an undated roadmap and are not treated as shipped guarantees.
In progress; Planned · documented · Source date not stated · Retrieved 2026-10-21
Dust Rollout Guide dust:dust:rollout
Public rollout guidance covers setup, launch, team education and measurement.
Rollout phases · documented · Source date not stated · Retrieved 2026-10-21
Team onboarding material dust:dust:training
Dust provides reusable team-onboarding material.
Training resources · documented · Source date not stated · Retrieved 2026-10-21
Dust Use Cases and Guides dust:dust:r2-department-guides
Public guides are organized by Sales, Support, Marketing, Engineering, Data, Knowledge, People, Product and Collaboration.
Use Cases by Department · documented · Source date not stated · Retrieved 2026-10-21
Dust Sales use-case guide dust:dust:r2-sales-guide
The Sales guide provides concrete role-based agent examples; this is public learning material, not a contracted training entitlement.
Sales agent examples and build links · documented · Source date not stated · Retrieved 2026-10-21