Skip to content

Agent-readable comparison

Open WebUI vs Unique AI

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 46 criteria with sourced findings for both products, including 46 that a second agent cross-checked for both. 50 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.

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.

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

Unique AI

Agent cross-checked Support: partial

The platform catalogue supports several providers, subject to tenant credentials, contracts and validation status.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number.
  • providers Which model providers are available? [partial]: Catalogue includes Azure OpenAI/OpenAI, Anthropic, Google Gemini/Vertex, Together AI and xAI. Provider use must be agreed with each client; a catalogue row is not proof every tenant has it. Sources: unique-ai:unique-ai:models.
  • current_models Which current models are selectable on this plan? [partial]: Release 2026.42, hosted 14 October, explicitly adds Azure GPT-6.1 Sol and Claude Opus/Sonnet 5.5 through Anthropic/Vertex. Availability overview also lists Gemini3.8 Flash; provider/tenant credentials and validation differ. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:models.
  • user_choice Can users pick the model per chat? [partial]: Space admins set enabled models; release notes describe chat model switching and API per-message model selection under the same rules. Conduct choices depend on administrator configuration. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct.
  • auto_routing Does the product route between models automatically, and is the chosen model shown? [unknown]: Does the product route between models automatically, and is the chosen model shown? Unknown. Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number.
  • multimodal_input Which models accept images, audio or files? [unknown]: Which models accept images, audio or files? Unknown. Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:models, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct, unique-ai:unique-ai:release42.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Unique publishes dated model additions and retirement/migration notes; a complete provider-release lag series remains unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented.
  • 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? Unknown. A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented.
  • changelog Is there a dated public model changelog? [supported]: Availability overview has a dated Recent changes table through 13 October 2026, with provider retirement sources. Sources: unique-ai:unique-ai:models.
  • deprecation_notice How much notice is given before a model is removed? [partial]: Dated 14 October release announces migrations ahead of o-series provider retirement on 19 November 2026. No guaranteed Unique contractual notice period is established. Sources: unique-ai:unique-ai:release42.
  • version_pinning Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unknown. A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:models, unique-ai:unique-ai:release42.

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.

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

Unique AI

Agent cross-checked Support: partial

Operators can configure customer model endpoints and credentials through GraphQL.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • BYO licence discounts, provider-by-provider contract onboarding and a full tool/RAG/embedding parity matrix are not public.
  • own_api_keys Can the customer use its own provider API keys? [supported]: ExternalLanguageModel accepts provider API credentials stored encrypted as immutable write-only values; OAuth2 is also documented. Sources: unique-ai:unique-ai:customllm.
  • own_cloud_contract Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Custom Azure OpenAI deployment examples specify customer endpoint, deployment, API version and token. Compliance docs mention Bedrock; exact supported Bedrock/Vertex contract routes need deployment scoping. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:compliance.
  • custom_endpoint Can an admin add any OpenAI-compatible endpoint? [partial]: Documents self/cloud-hosted LXM endpoints and an Azure-compatible connection object. Universal support for any OpenAI-compatible endpoint is not guaranteed. Sources: unique-ai:unique-ai:customllm.
  • byo_pricing Does BYO change the licence price? [unknown]: Does BYO change the licence price? Unknown. BYO licence discounts, provider-by-provider contract onboarding and a full tool/RAG/embedding parity matrix are not public.
  • byo_restrictions Which features stop working with BYO? [partial]: Azure Chat Code Execution requires compatible Azure Responses models; switching a custom model group name/deleting an in-use group can break configured assistants. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:code.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:compliance, unique-ai:unique-ai:code.

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.

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.

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

The platform documents custom model and embedding connections. Tool parity depends on the selected route: Code Execution lists Azure and LiteLLM OpenAI compatibility, while arbitrary self-hosted model parity is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform; custom-model/embedding connectors and optional Code Execution availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Code Execution has a listed Responses-capability/model matrix, not universal support for every custom-hosted model. Azure sandbox controls are not extended to every LiteLLM route.
  • No customer runtime or feature-parity fixture was used; QA-only Phoeniqs is not presented as GA.
  • self_hosted_chat Can chat use a customer-hosted model? [supported]: Custom LXM and on-premises architecture allow customer-hosted model connections. Models, endpoint compatibility and enabled modules are selected for the contracted deployment. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:onpremsecurity.
  • self_hosted_embeddings Can retrieval use customer-hosted embeddings? [partial]: An instance maintainer can configure embedding endpoint, key and deployment; the operator overview allows self-hosted embeddings. Supported non-Azure runtimes and a particular customer configuration were not verified. Sources: unique-ai:unique-ai:embeddings, unique-ai:unique-ai:operators.
  • feature_parity Which features fail with self-hosted models? [partial]: Changing embeddings requires re-embedding existing files. The Code Execution compatibility section explicitly lists Azure Responses-capable IDs and LiteLLM OpenAI IDs, so no blanket Azure-only restriction is asserted. Its introduction/security section describes an Azure sandbox; the actual LiteLLM execution route and parity for arbitrary self-hosted models remain unverified. Sources: unique-ai:unique-ai:embeddings, unique-ai:unique-ai:review2-code.
  • vendor_hosted_open_models Does the vendor host open-weight models in EU/CH? [partial]: The model catalogue describes Swiss Phoeniqs open models in QA only, not the UAT01/Prod offer. Production entitlement to a vendor-hosted Swiss open model was not established. Sources: unique-ai:unique-ai:review2-models.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:embeddings, unique-ai:unique-ai:operators, unique-ai:unique-ai:review2-code, unique-ai:unique-ai:review2-models.

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.

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

Unique AI

Agent cross-checked Support: partial

Models and knowledge/tools are configured per access-controlled Space; optional beta daily spending caps block calls.

Availability: beta · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • No two-group restriction fixture was run. Exact contract token/message limits, platform-wide model allow-lists and provider data-routing policy remain unverified.
  • model_allowlist_by_group Can admins limit models per group? [partial]: Admins bind deployed/approved models to Spaces and grant people/groups space access. Direct per-group model lists across all chats are not documented. Sources: unique-ai:unique-ai:agent.
  • data_bound_models Can admins restrict which models receive connector or knowledge content? [partial]: A Space binds one model, selected KB sources and tools, and people/group access. A global connector-content model policy is not established. Sources: unique-ai:unique-ai:agent.
  • default_model Can admins set the default model? [supported]: Administrators select the model for each Space. Sources: unique-ai:unique-ai:agent.
  • user_limits What per-user message or token limits apply, and are they published? [partial]: Off-by-default beta cost management supports daily USD limits at company/group/user levels, reset at user-local midnight. Public fixed token/message quotas are not established. Sources: unique-ai:unique-ai:cost.
  • limit_behaviour What happens when a limit is reached? [supported]: With limits enabled, the next model call is blocked when daily spend reaches the cap. Most permissive group limit wins unless a user override exists. Sources: unique-ai:unique-ai:cost.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:cost.

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.

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.

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Chat upload defaults are 512 MB/file and 30 files/batch, with source retrieval for large documents.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Configured scanned-PDF OCR is documented: MDI supports image-based PDFs, Docling has partial support, and Base Unique Ingestion does not support them. MDI must be provisioned and enabled for the folder or chat Space.
  • Scanned-PDF accuracy, formula preservation, embedded-figure extraction and shared fixture outcomes were not measured. Older general ingestion limits differ from current production chat defaults.
  • formats Which formats are accepted? [supported]: Chat supports PDF, DOCX, XLSX, PPTX, CSV, HTML, MD and TXT; PNG/JPEG when enabled per Space. Sources: unique-ai:unique-ai:files.
  • limits What size and count limits apply per file and chat? [partial]: Production Chat defaults 512 MB/file, 30 files/upload. Code Execution has separate 100 MB and 10-file limits. Environment overrides and aggregate chat caps need tenant confirmation. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:code.
  • ocr Are scanned PDFs read? [partial]: The file-ingestion guide explicitly distinguishes methods: Base Unique Ingestion does not support image-based scanned PDFs, MDI supports them, and Docling has partial support. MDI must be provisioned and enabled for the folder or in the chat Space ingestion settings. Experimental image-content extraction and deprecated agentic ingestion are separate. No scanned-document fixture or accuracy measurement was run. Sources: unique-ai:unique-ai:file-ingestion-20261026.
  • spreadsheets Are Excel tables read with structure intact? [partial]: Chat guide says default extraction can fail beyond 5,000 rows x 100 columns. General format guide lists 1,000 x 40; formulas and structure retention were not tested. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:filetypes.
  • full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [supported]: Checked uploads force retrieval each turn. Large files contribute selected chunks, not necessarily the full file, and users do not see full coverage. Experimental full-PDF mode is separate. Sources: unique-ai:unique-ai:files.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:code, unique-ai:unique-ai:filetypes, unique-ai:unique-ai:file-ingestion-20261026.

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.

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.

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Knowledge folders persist and can be scoped to users/groups and bound to Spaces.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Public total collection/document/token caps and organisation-wide sharing defaults are not specified; chat-only uploads are separately private and expiring.
  • persistent_collections Can users keep document collections across chats? [supported]: Ingested content lives in knowledge-base folders/scopes beyond a chat. Sources: unique-ai:unique-ai:kbpermissions.
  • sharing_scope Can collections be shared with users, groups or the whole organisation? [supported]: ScopeAccess grants users or groups read/write access. A flat folder permission does not automatically grant subfolder access. Sources: unique-ai:unique-ai:kbpermissions.
  • size_limits What are the collection limits? [unknown]: What are the collection limits? Unknown. Public total collection/document/token caps and organisation-wide sharing defaults are not specified; chat-only uploads are separately private and expiring.
  • assistant_binding Can collections be bound to an assistant? [supported]: Space Internal Search binds selected folders/files and further narrows user permissions. Sources: unique-ai:unique-ai:agent.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:agent.

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

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

Unique AI

Agent cross-checked Support: partial

Indexed SharePoint and Confluence are documented. Current architecture also names Google Drive/Salesforce, and release notes describe Salesforce/Yahoo Finance MCP connector dashboards; detailed entitlements and source permissions remain connector-specific.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Architecture labels and release examples do not prove that every source is enabled or included in every contract.
  • Future items on the roadmap are not promoted to current connector support.
  • No source-connection or two-user permission fixture was run.
  • microsoft_365 Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: SharePoint Online connector copies selected content with application consent and optional permission sync. Platform documentation also exposes Teams and Outlook MCP operator guides, but their exact contracted scope and OneDrive coverage were not verified. Sources: unique-ai:unique-ai:sharepoint.
  • google_workspace Which Google sources are connected? [partial]: The current Platform Overview names Google Drive as a Knowledge Source feeding the Knowledge Base. It does not establish Gmail/Calendar coverage, a deployment guide, source consent scopes or inclusion in a particular customer contract. This is a documented architecture listing, not an observed enabled connector. Sources: unique-ai:unique-ai:platform-overview-20261026.
  • atlassian Confluence and Jira? [partial]: Official Confluence connector supports Cloud and Data Center; Jira connector coverage was not established. Sources: unique-ai:unique-ai:confluence.
  • other_systems Which other business systems? [partial]: Release 2026.40 names Salesforce and Yahoo Finance as examples in GA MCP connector dashboards that admins can list, enable and sign in to. Platform Overview also names Salesforce as a Knowledge Source. Exact origin implementation, connector rights, credentials and commercial inclusion vary by configured connector and contract. Sources: unique-ai:unique-ai:release40-20261026, unique-ai:unique-ai:platform-overview-20261026.
  • on_prem_sources Can on-prem file shares or databases be connected? [partial]: Confluence Data Center sources are supported via REST. Generic file-share/database connector scope was not established. Sources: unique-ai:unique-ai:confluence.
  • connector_provider Who builds and maintains each connector? [supported]: Unique publishes Kubernetes operator guides for SharePoint and Confluence; client IT supplies source credentials, consent, scope and deployment configuration. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:platform-overview-20261026, unique-ai:unique-ai:release40-20261026.

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.

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.

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

SharePoint permission mirroring is optional; Confluence does not synchronise source permissions.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • No two-user restricted-document/revocation fixture was run. End-to-end revocation SLA and label enforcement are not established. Older folder-permissions documentation says SharePoint never mirrors permissions, conflicting with the newer optional-sync guide.
  • source_permissions_respected Are source permissions enforced per user? [partial]: SharePoint content_and_permissions mirrors source rights, while content_only uses Unique scope rules. Confluence explicitly has no source-permission sync, so Unique folder access needs configuration. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence.
  • enforcement_point Does the source system, a mirrored index or nothing enforce them? [supported]: Indexed content is filtered through Unique user/group ScopeAccess. This is not source-system live query-time enforcement. Sources: unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:sharepoint.
  • revocation_delay How quickly does a removed permission take effect? [partial]: SharePoint source rights refresh periodically, default scans 15 minutes. Internal gatekeeper changes usually propagate under one second but have no hard upper bound; degraded/missed broadcasts can leave old rules active. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:permissioncache.
  • admin_scope_controls Can admins exclude sites, folders or labels? [supported]: Admins allow SharePoint sites/libraries and require a sync flag, Confluence labels, and Space KB restrictions. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:agent.
  • sensitivity_labels Are Microsoft Purview or similar labels respected? [partial]: July SharePoint connector explicitly excludes sensitivity/classification-level detection. Separately, release2026.42 documents experimental Purview-protected-file decryption using uploader rights, gated by MIP_DECRYPTION_ENABLED and Entra/operator changes. This is not proof of general label-policy enforcement. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:sharepoint.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:permissioncache, unique-ai:unique-ai:agent, unique-ai:unique-ai:release42.

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.

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.

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

SharePoint and Confluence copy content to Unique indexes on configurable scans, default every 15 minutes.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • No source-edit/delete fixture was run. Actual sync duration, strict deletion SLA and index/backup region per contract remain unverified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:retention, unique-ai:unique-ai:keys.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:rag.

Unique AI

Agent cross-checked Support: partial

Unique documents source-linked answers and reference limits, without a shared-corpus accuracy result.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results.
  • citations Are answers linked to specific sources? [supported]: Chat retrieval cites sources; Conduct links source facts, with PDF/Word page-level references and other formats at document level. Generated files are not citation-linked or hallucination-checked. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:conduct.
  • citation_accuracy Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results.
  • cross_language Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results.
  • no_answer_behaviour Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results.
  • observed_accuracy How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:conduct.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:models, open-webui:open-webui:memory.

Unique AI

Agent cross-checked Support: partial

Context Memory provides a private cross-chat user profile with edit and opt-out controls.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • No authenticated memory fixture or permanent deletion test was run. The guide explicitly contradicts the settings deletion promise.
  • custom_instructions Can users set persistent instructions? [partial]: Admins configure Space instructions; memory learns preferences. A separate persistent user-authored global instruction field was not established. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:memory.
  • cross_chat_memory Does the product remember facts across chats? [supported]: One per-user profile is loaded across enabled spaces/chats and updated after answers; stored in a private unindexed KB folder. Sources: unique-ai:unique-ai:memory.
  • user_memory_controls Can users view, edit and delete memories? [partial]: Users view/edit the profile and disable updates/loading. Docs explicitly say disabling does not delete the profile despite contrary settings text; a delete control is not established. Sources: unique-ai:unique-ai:memory.
  • admin_memory_controls Can admins turn memory off? [supported]: Release2026.42 makes Context Memory GA, with per-company enable/disable feature flag and per-Space activation. Users can opt out; Web Search combinations remain restricted by default. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:memory.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:memory, unique-ai:unique-ai:release42.

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.

Open WebUI

Agent cross-checked Support: supported

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

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.

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Admins configure Spaces with instructions, models, knowledge, tools, prompts and group access.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Assistant versioning, organisation-wide directory discovery and unrestricted end-user creation were not established.
  • create_assistants Can users create assistants with instructions, knowledge and tools? [supported]: Space setup includes model, instructions, knowledge sources and tools. Sources: unique-ai:unique-ai:agent.
  • creator_permissions Can admins limit who creates them? [supported]: Space creation/management requires delegated role permissions; Can manage grants space configuration access. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent.
  • sharing_scope Can assistants be shared with users, groups or everyone? [supported]: Share through Access with people/groups as Can chat or Can manage. Sources: unique-ai:unique-ai:agent.
  • catalogue Is there an internal assistant directory? [partial]: Space Management lists configured workspaces; a dedicated employee assistant-discovery directory is not described. Sources: unique-ai:unique-ai:agent.
  • prompt_library Are shared prompt templates available? [supported]: Admins publish Suggested Prompts with a Space; users also have personal saved prompts. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:chat.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:roles, unique-ai:unique-ai:chat.

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.

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

Unique AI

Agent cross-checked Support: partial

Built-in tools and beta MCP connectors are governed at organisation and Space levels.

Availability: beta · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique AI Conduct, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted platform with MCP beta feature flag and configured connectors; add_ons=MCP entitlement and enablement per contract; deployment_mode=not specified; region=Tenant plus downstream connector/provider regions; os=not specified.

Limitations

  • Arbitrary OpenAPI action import, local stdio MCP support, each connector auth mode and universal side-effect approval are not established. Hub planned DLP/elicitation pipeline is not treated as released.
  • builtin_tools Which tools are built in? [supported]: Internal search, web search, Deep Research and Code Execution are documented; Deep Research is experimental and code has model restrictions. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:code, unique-ai:unique-ai:deepresearch.
  • custom_actions Can admins add API actions? [unknown]: Can admins add API actions? Unknown. Arbitrary OpenAPI action import, local stdio MCP support, each connector auth mode and universal side-effect approval are not established. Hub planned DLP/elicitation pipeline is not treated as released.
  • mcp_client Can it use remote MCP servers, and with what admin control? [supported]: MCP Tools for Spaces is beta, off until enabled for the organisation; connector admins and space managers can selectively expose connectors/tools. Sources: unique-ai:unique-ai:mcp.
  • tool_auth Do tools act as the user or as a shared account? [supported]: MCP Hub maps user hub tokens to downstream per-user OAuth tokens; secrets are injected server-side. Sources: unique-ai:unique-ai:hub.
  • tool_approval Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins restrict origin/connector/tool exposure. Conduct can pause for approve/deny of configured sensitive actions; it is not a universal confirmation guarantee. Sources: unique-ai:unique-ai:hub, unique-ai:unique-ai:conduct.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:code, unique-ai:unique-ai:deepresearch, unique-ai:unique-ai:mcp, unique-ai:unique-ai:hub, unique-ai:unique-ai:conduct.

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.

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.

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Web search has provider/strategy controls; separate Deep Research is experimental.

Availability: beta · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • No search/report fixture was run. Exact query/provider regions, contract enablement and current Deep Research production readiness remain unverified.
  • web_search Is web search available? [supported]: Real-time web search/read is a Space tool, with stable V1/V2 modes and experimental V3. Sources: unique-ai:unique-ai:websearch.
  • admin_toggle Can admins disable it per organisation or group? [supported]: Admins enable/disable tools per Space shared with groups. Deep Research tools are configured separately; disabling ordinary Web Search is not a universal external-search block. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:deepresearch.
  • search_provider Which search provider handles queries, and where? [partial]: Configured engines can include Google, Bing, Brave, Jina, Tavily, Firecrawl, Vertex or custom API; query context can leave the tenant. Exact provider region must be set per contract. Sources: unique-ai:unique-ai:websearch.
  • deep_research Is multi-step research with a report available? [supported]: Experimental tool creates multi-source research and reports. Unique engine can use internal/web sources; OpenAI-native engine requires direct OpenAI-hosted models and lacks internal sources/hosting-location control. Sources: unique-ai:unique-ai:deepresearch.
  • web_citations Are web sources cited? [supported]: Web answers include source references; Deep Research documents citation-linked reports. Sources: unique-ai:unique-ai:websearch, unique-ai:unique-ai:deepresearch.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:websearch, unique-ai:unique-ai:agent, unique-ai:unique-ai:deepresearch.

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.

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.

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Recurring Scheduled Tasks run with user permissions; current release notes label the feature experimental.

Availability: beta · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • No general no-code workflow/chain builder or complete event-source trigger catalogue was established. Automated runs may stop for manual approval/questions and are subject to normal usage limits.
  • workflow_builder Is there a workflow or chain builder? [unknown]: Is there a workflow or chain builder? Unknown. No general no-code workflow/chain builder or complete event-source trigger catalogue was established. Automated runs may stop for manual approval/questions and are subject to normal usage limits.
  • scheduled_tasks Can prompts or assistants run on a schedule? [partial]: User guide labels recurring Chat/Conduct tasks beta and off by default; release2026.42 instead labels Scheduled Tasks experimental, off by default, enabled on request, and describes scheduling/eligibility fixes. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:scheduled.
  • event_triggers Can external events start a workflow? [partial]: SDK documents webhook-driven applications, which require developer-hosted modules; a packaged no-code external-event builder was not established. Sources: unique-ai:unique-ai:sdk.
  • builder_audience Is building aimed at business users, IT or developers? [partial]: Business users author recurring tasks in the UI or Conduct; developers host webhook-driven SDK modules. Availability and scheduling behaviour depend on deployed release. Sources: unique-ai:unique-ai:scheduled, unique-ai:unique-ai:sdk.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:scheduled, unique-ai:unique-ai:sdk, unique-ai:unique-ai:conduct, unique-ai:unique-ai:release42.

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.

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

Unique AI

Agent cross-checked Support: partial

Contract-enabled Conduct plans and executes multi-step tasks with visible tools and stop controls. Sensitive actions can ask for approval; separately enabled Experimental Scheduled Tasks offer automatic approval.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Conduct; version=Conduct 2026.40+; scheduling status/flags per 2026.42; plan=Contracted Unique AI platform; Conduct; Scheduled Tasks separately enabled per contract and feature flag availability and deployment/provider configuration depend on the customer agreement; add_ons=Conduct; optional Scheduled Tasks feature flag; deployment_mode=not specified; region=Configured tenant/models/tools; scheduled actions run with the owner permissions and configured approval policy; os=not specified.

Limitations

  • No agent fixture was run. Interactive sensitive-action approval and separately enabled unattended automatic approval are different execution modes.
  • Actual tools, entitlement, approval policy and deployed release depend on the customer contract/configuration.
  • agent_mode Is there an agent mode for multi-step tasks? [supported]: Plans and executes Python/Bash, files, internal search and configured MCP tools in an autonomous workspace. Sources: unique-ai:unique-ai:conduct.
  • visible_steps Are steps and tool calls shown? [supported]: Shows checklist, progress, code/tool inputs and outputs, and waiting/working indicators. Sources: unique-ai:unique-ai:conduct.
  • side_effect_confirmation Must the user confirm actions with side effects? [partial]: Conduct shows approve/deny for actions configured as sensitive. The separate Scheduled Tasks guide offers Automatic or Manual approval for Chat/Conduct unattended runs. Release 2026.42 labels scheduling Experimental and feature-flagged. Mandatory human approval of every side effect is therefore not established for all configured runs. Sources: unique-ai:unique-ai:conduct, unique-ai:unique-ai:review2-scheduled, unique-ai:unique-ai:review2-release42.
  • stop_control Can the user stop a running task? [supported]: Stop ends the turn within seconds; completed steps/files remain and interrupted work can be resumed. Sources: unique-ai:unique-ai:conduct.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:conduct, unique-ai:unique-ai:review2-scheduled, unique-ai:unique-ai:review2-release42.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Public API/Python SDK and Knowledge Base MCP are documented.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique API and Python SDK, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted APIs and KB MCP deployment; model tracking requires enablement; add_ons=KB MCP and usage-tracking enablement per contract; deployment_mode=not specified; region=Configured deployment and external client region; os=not specified.

Limitations

  • No API/SDK fixture was run; complete endpoint catalogue, rate limits, budget enforcement and all-services audit parity remain unverified.
  • chat_api Is there an API for chat and assistants? [partial]: SDK exposes the Unique public API, personal/app keys and webhook signatures. Exact endpoint entitlements/rate limits require the contracted deployment. Sources: unique-ai:unique-ai:sdk.
  • knowledge_api Can documents be loaded through an API? [partial]: Connector/operator docs describe ingestion and knowledge APIs; public SDK supports platform integrations. Sources: unique-ai:unique-ai:sdk, unique-ai:unique-ai:sharepoint.
  • api_governance Do audit, budgets and model rules apply to API use? [partial]: Feature-flagged model-use tracking covers public API/SDK/agentic and Azure SDK calls with company/user/app metadata. Complete budget/model-rule enforcement across all internal services is not established. Sources: unique-ai:unique-ai:api-usage.
  • mcp_server Does the product expose itself to other agents over MCP? [supported]: Knowledge Base MCP lets external assistants search/read the Unique KB with the user permissions and admin scope restrictions. The documentation-only MCP endpoint is distinct. Sources: unique-ai:unique-ai:mcpkb.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sdk, unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:api-usage, unique-ai:unique-ai:mcpkb.

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.

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

Unique AI

Agent cross-checked Support: partial

A web workspace is documented; native-client and managed-deployment coverage is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown.
  • web Is a full web client available? [supported]: Public documentation describes browser chat, Space Management and administration. Sources: unique-ai:unique-ai:chat, unique-ai:unique-ai:agent.
  • desktop_apps Windows and macOS apps? [unknown]: Windows and macOS apps? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown.
  • mobile_apps iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown.
  • browser_extension Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown.
  • managed_deployment Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown.
  • client_feature_gaps Which features are missing on mobile? [unknown]: Which features are missing on mobile? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:chat, unique-ai:unique-ai:agent.

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.

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.

Unique AI

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:notes.

Unique AI

Agent cross-checked Support: partial

A beta Translator Space translates Office files and text with configurable glossaries.

Availability: beta · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • No translated-contract fixture was run. Exact engine/model, formality/de-CH controls, supported glossary language pairs and layout fidelity need verification.
  • document_translation Can whole documents be translated with formatting kept? [partial]: DOCX, XLSX and PPTX document translation is documented, with possible layout disruption. PDF input is explicitly excluded in this Translator mode. Sources: unique-ai:unique-ai:translation.
  • translation_engine Which engine translates? [partial]: Translator V2 is a standalone AI module configured with a model; no dedicated DeepL engine was established. Sources: unique-ai:unique-ai:translation.
  • glossaries Are company glossaries supported? [supported]: Admins can configure glossary pre/postprocessing. Sources: unique-ai:unique-ai:translation.
  • formality_and_variants Can formality and regional variants (de-CH) be set? [partial]: Postprocessing can change regional spelling, exemplified by US-to-UK English. Formality or de-CH-specific support was not verified. Sources: unique-ai:unique-ai:translation.
  • writing_tools Are dedicated rewrite and proofreading tools available? [partial]: Chat generates and iterates on text; no distinct proofreading/rewriting tool scope was established. Sources: unique-ai:unique-ai:chat.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:translation, unique-ai:unique-ai:chat.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:images, open-webui:open-webui:image-usage.

Unique AI

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

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.

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

  • 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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:env, open-webui:open-webui:voice.

Unique AI

Agent cross-checked Support: partial

Voice dictation is documented with Azure Speech prerequisites; recording use is separately described in the DPA.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone.
  • dictation Can users dictate prompts? [supported]: Microphone transcribes into the prompt field, with audio discarded after live transcription. Requires configured Azure AI Speech Services; EN/DE/FR/IT are listed. Sources: unique-ai:unique-ai:voice, unique-ai:unique-ai:voice-user.
  • read_aloud Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone.
  • voice_conversation Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone.
  • meeting_summaries Are meetings transcribed and summarised? [partial]: DPA recording use case covers audio/transcripts, optional video and GPT summaries/follow-up emails. This is a contracted recording use case, not proof every Chat plan includes meeting capture. Sources: unique-ai:unique-ai:dpa.
  • swiss_german_speech Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:voice, unique-ai:unique-ai:voice-user, unique-ai:unique-ai:dpa.

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.

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:terminal, open-webui:open-webui:notes.

Unique AI

Agent cross-checked Support: partial

Enabled Chat Code Execution and Conduct can analyse data and produce downloadable files. Selected KB documents can be preloaded into the code container; ordinary unrestricted KB retrieval is separate.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique AI Conduct; version=not specified; plan=Contracted Unique AI platform; Chat Code Execution or Conduct; model compatibility and flags configured separately availability and deployment/provider configuration depend on the customer agreement; add_ons=Code Execution / Conduct enablement per contract; deployment_mode=not specified; region=Documented Azure code container for the Azure route; LiteLLM execution region unverified; Conduct sandbox per contracted deployment; os=not specified.

Limitations

  • Selected admin-preloaded KB files are supported; this is not arbitrary sandbox retrieval of the whole Knowledge Base.
  • The page lists Azure and LiteLLM-compatible model IDs but describes Azure-specific container controls. Actual provider execution routing and entitlement require deployment configuration.
  • No generated-file quality/editability fixture was run.
  • data_analysis Can it analyse spreadsheets with executed code? [partial]: Chat Code Execution runs Python for CSV/XLSX analysis. The general limitation says KB files are not directly accessible, but admin configuration additionalUploadedDocuments preloads selected KB content_ids, for example templates, into the container. The documented Azure route has no outbound internet/runtime installs and a ten-file/100 MB per-file limit. The compatibility table also lists LiteLLM OpenAI models; that does not establish the same execution-region controls for every route. Conduct separately runs Python/Bash. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct.
  • charts Can it produce charts? [supported]: The Code Execution guide documents matplotlib PNG/SVG and inline charts. Its described Azure container lacks kaleido, limiting Plotly static exports; no statement about every alternative runtime is inferred. Sources: unique-ai:unique-ai:review2-code.
  • office_file_output Can it create Word, Excel or PowerPoint files? [partial]: The guide documents DOCX/XLSX generation and PPTX from supplied templates, with variable presentation quality. KB templates can be supplied by the admin preload setting. Generated files remain outside Conduct source-citation/hallucination checks. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct.
  • canvas_editing Is there a document or canvas editor for iterating on output? [unknown]: No dedicated canvas editor or editable spreadsheet-to-PowerPoint fixture result was established. Downloadable file generation does not establish in-product canvas editing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Shared Chats is GA in release 2026.42, with company settings and a per-Space toggle. Simultaneous group conversation and recipient source-permission handling remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=2026.42 or later; plan=Contracted Unique AI platform; Shared Chats and Spaces; sharing settings and deployed release availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • A shared conversation is not evidence of simultaneous group participation or recipient access to every source.
  • No cross-group shared-chat permission fixture was run.
  • share_chats Can chats be shared inside the organisation? [supported]: Release 2026.42 makes whole-chat sharing GA and on by default for companies, while each Space still needs its Shared chat toggle. Explicit existing company preferences are preserved. Owners can search recipients and copy share links. Sources: unique-ai:unique-ai:review2-release42.
  • team_spaces Are shared projects or workspaces available? [partial]: Admins publish shared Spaces with people/group Can chat and Can manage roles. These share agent configuration/knowledge, not necessarily a conversation. Sources: unique-ai:unique-ai:agent.
  • group_chat Can several people chat together with the AI? [unknown]: Whole-chat sharing is documented. A simultaneous multi-person AI conversation, collaborative commenting or live co-editing mode was not established or tested.
  • share_permission_boundary Does sharing respect the recipient's access to sources? [unknown]: Whole-chat sharing is documented, but whether a recipient can open every cited source or inherits source permissions was not established in the retrieved release/Space documentation. No cross-group fixture was run.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:review2-release42.

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.

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.

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Current release notes document German, French and Swiss German UI language behaviour; completeness and accessibility remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Release notes describe locale fixes, not a full UI audit or conformance statement. No authenticated UI was reviewed.
  • ui_languages Which UI languages are offered? [partial]: Release2026.42 describes German/French label translations and selected-language login/notices/errors/side-panels, including Swiss German spellings. A complete language matrix was not provided. Sources: unique-ai:unique-ai:release42.
  • dach_language_quality Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained.
  • accessibility_statement Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained.
  • admin_ui_languages Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:release42.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Zitadel supports Entra OIDC, generic OIDC and SAML across documented deployment types.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented.
  • sso_protocols Which SSO protocols and identity providers work? [supported]: Setup guides explicitly cover Entra ID OIDC, generic OIDC and SAML, including IdP metadata for closed networks. Sources: unique-ai:unique-ai:sso.
  • sso_plan Which plan includes SSO? [partial]: Compliance matrix lists SSO for multi-tenant, single-tenant, client-hosted and on-premise modes. Numeric tariff prerequisites are not public. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance.
  • mfa Can MFA be enforced? [partial]: Hosted compliance matrix lists enforced 2FA; SSO setup delegates authentication to the external IdP. Exact customer MFA policy controls need verification. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance.
  • conditional_access Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? Unknown. Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented.
  • domain_capture Can the company claim its email domain? [unknown]: Can the company claim its email domain? Unknown. Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance.

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.

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

Unique AI

Agent cross-checked Support: partial

SCIM, group sync and SAML automatic user creation are documented.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run.
  • scim Is SCIM provisioning supported? [supported]: Unique supplies SCIM URL/key for IdP synchronisation, with an Entra guide. Sources: unique-ai:unique-ai:scim.
  • group_sync Are identity-provider groups synced? [supported]: SCIM syncs users/groups; SSO group claims can also sync on login, requiring optional Graph group permission/admin consent. Sources: unique-ai:unique-ai:scim, unique-ai:unique-ai:sso.
  • jit_provisioning Are users created at first login? [supported]: SAML setup explicitly enables automatic creation/update and account creation. Sources: unique-ai:unique-ai:sso.
  • deprovisioning What happens to a removed user's data and shared assets? [unknown]: What happens to a removed user's data and shared assets? Unknown. Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run.
  • seat_assignment Can admins assign and reclaim seats? [unknown]: Can admins assign and reclaim seats? Unknown. Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:scim, unique-ai:unique-ai:sso.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Four role/access layers separate identity, feature, Space and knowledge controls.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • No two-user disabled-feature test was run. Full cross-Space per-group controls and legal-entity separation require contracted setup.
  • admin_roles Which admin roles exist, and can admin rights be delegated? [supported]: IAM owner/viewer/org-manager plus Unique application roles delegate administration; Space Can manage grants local configuration. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent.
  • groups Can permissions be set per group? [supported]: Users/groups receive Space and ScopeAccess permissions. Sources: unique-ai:unique-ai:roles.
  • feature_toggles Which features can be switched on or off per group? [partial]: Tools and upload settings are configured per Space, then Spaces shared to groups. A global group-feature matrix is not established. Sources: unique-ai:unique-ai:agent.
  • multi_entity Can subsidiaries or departments be separated within one contract? [partial]: Compliance docs describe workspace isolation for departments/client engagements. Multi-subsidiary contractual/billing boundaries are not specified. Sources: unique-ai:unique-ai:compliance.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent, unique-ai:unique-ai:compliance.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:analytics, open-webui:open-webui:privacy.

Unique AI

Agent cross-checked Support: partial

Analytics exports cover adoption, assistants, models and tools with privacy controls.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Exact group breakdowns, every dashboard entitlement and suppression beyond exported identifiers need verification.
  • adoption_dashboard Is there an adoption dashboard? [supported]: Reports cover daily/weekly/monthly active users, assistant interactions and document reference statistics. Sources: unique-ai:unique-ai:analytics.
  • breakdowns Can usage be broken down by group, model, feature and assistant? [partial]: Detailed exports include assistant/model, tool calls, skills, cost and tokens. Group and cost-centre breakdowns were not established. Sources: unique-ai:unique-ai:analytics.
  • export Can usage data be exported? [supported]: Admins request and download reports with date/assistant filtering; model usage supports CSV. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost.
  • privacy_modes Can per-person reporting be limited or pseudonymised? [supported]: Environment flags anonymise export emails, optionally with stable pseudonyms; detailed exports respect organisation settings. Sources: unique-ai:unique-ai:analytics.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:analytics.

Unique AI

Agent cross-checked Support: partial

Off-by-default beta cost management offers estimated spend and enforced daily caps.

Availability: beta · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • No small-budget fixture was run. Estimates are configurable cost-sheet values, not a public billing tariff; cost-centre and full invoice reconciliation remain gaps.
  • cost_visibility Can admins see cost or consumption per user and group? [partial]: Tracks estimated USD/input/output tokens by user, model, assistant/app; a billed invoice reconciliation or group cost view is not established. Sources: unique-ai:unique-ai:cost.
  • budgets Can budgets be set per user or group? [supported]: Company fallback, group and user daily USD caps; user override first, highest applicable group limit next. Sources: unique-ai:unique-ai:cost.
  • budget_enforcement Does reaching a budget alert, block or downgrade? [supported]: Before the next call, accumulated daily spend at cap blocks the model call; resets at local midnight. Docs warn caps may break background-job SLAs. Sources: unique-ai:unique-ai:cost.
  • chargeback Can costs be exported per cost centre? [partial]: CSV exports contain user/app/assistant/model/token/cost metadata, with privacy controls. Cost-centre attribution is not documented. Sources: unique-ai:unique-ai:cost.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:cost.

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.

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.

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

  • 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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:hardening, open-webui:open-webui:security.

Unique AI

Agent cross-checked Support: partial

API audit events, detailed interaction exports and Single-Tenant security-event streaming are documented. A single authoritative retention period for the customer's audit records is not established.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; Audit Logs, Analytics and Single-Tenant Security Events Export availability and deployment/provider configuration depend on the customer agreement; add_ons=SEE for the contracted Single-Tenant deployment; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • API security-event records, detailed prompt/answer interaction exports, SEE replay and generic operational logging are separate sources/data flows. Their public retention figures are not substituted for each other.
  • No executed customer retention override or legal-hold/eDiscovery fixture was inspected.
  • admin_events Are admin and security events logged? [supported]: Event logging covers privileged public/internal API interactions; many self-identity/chat operations are excluded. Basic mode is default; verbose content mode is opt-in. Sources: unique-ai:unique-ai:audit.
  • content_logging Can prompts and answers be retained for compliance, and is it configurable? [supported]: Detailed chat interaction exports contain prompts/answers for authorised admins and respect configured privacy. Verbose event logging can include CID but is discouraged. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:audit.
  • siem_export Can logs stream to a SIEM or be exported? [supported]: SEE offers Single-Tenant Azure Defender and Activity events via Event Hub to Sentinel/Splunk, seven-day replay. It excludes tenant-level Entra events and is not a prompt-content audit stream. Sources: unique-ai:unique-ai:security-export.
  • ediscovery Are eDiscovery and legal hold supported? [unknown]: No public legal-hold/eDiscovery workflow or complete event-log immutability design was established.
  • log_retention How long are logs kept? [unknown]: Different sources describe different record scopes. The API event guide gives basic-mode MT events 90 days and ST events five years, including post-termination ST retention. DPA 3.15 says audit logs ten years without mapping its audit-log category to those API events. The generic hosted policy says logging up to one year after termination or longer if legally required. SEE has a separate seven-day Event Hub replay window, not the lifetime of all audit records. No customer agreement or authoritative record-class/precedence mapping was retrieved; the applicable audit retention period is unknown.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-audit, unique-ai:unique-ai:analytics, unique-ai:unique-ai:security-export, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:review2-retention.

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.

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:filter.

Unique AI

Agent cross-checked Support: partial

DLP is primarily customer infrastructure and integration; it is not a verified default native redaction feature.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking.
  • pii_detection Is personal data detected in prompts and files? [unknown]: Is personal data detected in prompts and files? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking.
  • pii_action Is it redacted, masked, blocked or only warned? [unknown]: Is it redacted, masked, blocked or only warned? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking.
  • custom_patterns Can admins add custom patterns or terms? [unknown]: Can admins add custom patterns or terms? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking.
  • dlp_integration Does it integrate with an existing DLP product? [partial]: Documents customer HTTPS proxy/interceptor DLP and post-chat Analytics API scanning; Compliance Layer says pre-LLM calls can be implemented. Multi-Tenant matrix explicitly excludes DLP integration. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance.
  • filter_location Where does filtering run? [partial]: Proxy inspection runs in customer egress infrastructure; Analytics API supports customer post-chat inspection. A deployment-specific pre-LLM service may be implemented. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Space instructions/banners and customer-specific login terms are documented.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Org-wide instruction enforcement, customer content-filter policy controls and administrator violation reports are not established. Prompt guidance is not guaranteed enforcement.
  • org_instructions Can admins set organisation-wide instructions? [partial]: Admins set Space-level system instructions and persistent banners. A mandatory organisation-wide instruction hierarchy is not specified. Sources: unique-ai:unique-ai:agent.
  • usage_notice Can users be required to accept a usage policy? [supported]: First login requires terms acceptance; custom terms/editing/deactivation depend on MSA eligibility and admin GraphQL role. Acceptance/version data can be exported. Sources: unique-ai:unique-ai:policy.
  • content_filters Are content filters configurable? [partial]: Single-tenant Azure prompts pass through Azure content filters; Compliance matrix marks hosted modes with content filtering. Customer filter configuration and scope remain unspecified. Sources: unique-ai:unique-ai:single, unique-ai:unique-ai:compliance.
  • violation_reporting Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. Org-wide instruction enforcement, customer content-filter policy controls and administrator violation reports are not established. Prompt guidance is not guaranteed enforcement.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:policy, unique-ai:unique-ai:single, unique-ai:unique-ai:compliance.

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.

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.

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Documentation offers CH North multitenant hosting and selectable single/customer-hosted regions, with model processing configured separately. The customer's binding residency schedule and full backup/log/support map remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; hosted or customer-hosted platform; separately selected model/tool routes availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Documented options: CH North hosted MT; selected ST/customer region; provider/SKU/tool inference region separately configured; actual contracted boundaries unverified; os=not specified.

Limitations

  • Available architecture/region options are not a signed residency schedule. Storage, model inference, backups/logs, support access and external tools must be scoped separately.
  • DPA CH-storage and chosen-location statements are not reconciled by silently treating one as the current customer contract.
  • storage_region Where are chats, files and indexes stored? [partial]: The deployment matrix documents Azure Switzerland North for hosted multitenant and chosen supported regions for Single Tenant. Tenant storage includes PostgreSQL, documents and vector data. These are configuration options; no customer-specific storage schedule was inspected. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-keys.
  • inference_region Where do model calls run, per provider? [partial]: The model catalogue separates Azure regional/Data Zone/Global SKUs and external provider routes, with some Swiss deployments and some global-only services. Actual selected provider/SKU/tool routing must be configured for the contracted deployment. CH storage is not a verified CH inference guarantee. Sources: unique-ai:unique-ai:review2-models, unique-ai:unique-ai:deepresearch.
  • backups_logs_region Where are backups, logs and telemetry? [partial]: Single-tenant backup resources follow the configured landing-zone design and SEE sends events to a separately selected consumer region. An exhaustive physical replica/backup/log/telemetry country matrix was not retrieved. Sources: unique-ai:unique-ai:review2-single, unique-ai:unique-ai:security-export.
  • support_access_region From where can vendor staff access data? [unknown]: The public DPA gives need-to-know access controls and customer-controlled on-premises support, but not an exhaustive physical country list for vendor/subprocessor support access. Office addresses are not used as support-access locations.
  • swiss_hosting Is Swiss hosting available? [partial]: CH North is a documented hosted-MT option, and selected-region ST can be Swiss. This records available deployment options, not the customer's end-to-end storage/inference/support contract. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-models.
  • residency_plan Which plan or option provides residency? [unknown]: DPA 6.1 says storage stays in Switzerland, while its Appendix A allows a client-chosen Microsoft location and current platform docs offer selected jurisdictions. No current customer MSA, precedence clause or deployment schedule was inspected to resolve the binding scope. A contractual CH-wide residency commitment is not asserted.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-models, unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:security-export, unique-ai:unique-ai:deepresearch.

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.

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.

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Current docs offer shared SaaS, dedicated instances, customer cloud and customer-operated on-premise/air-gapped modes.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • No deployed tenant was inspected. Seat/contract thresholds and an exhaustive offline feature-parity matrix remain unknown; docs establish an option, not universal entitlement.
  • multi_tenant_saas Is a shared SaaS offered? [supported]: Installation overview lists Multi Tenant on Unique cloud. Sources: unique-ai:unique-ai:install.
  • dedicated_instance Is a dedicated single-tenant instance offered, from what size? [partial]: Unique-managed Single Tenant has its own Azure landing zone separated from other customers. Minimum seats/contract value are unpublished. Sources: unique-ai:unique-ai:single.
  • customer_cloud Can it run in the customer's own cloud account, from what size? [partial]: Operator guide documents deployment in customer cloud account with Unique software/support; cloud-specific rollout is contracted. Sources: unique-ai:unique-ai:operators.
  • on_premise Can the whole platform run on customer infrastructure, from what size? [partial]: Customer provisions/manages infrastructure on own premises, may run own models and can exclude Unique access. Minimum commitment not published. Sources: unique-ai:unique-ai:onpremsecurity.
  • air_gapped Can it run without internet access? [partial]: IT-operator overview explicitly offers a full air-gapped on-premise deployment. Compatibility and feature limitations depend on customer setup. Sources: unique-ai:unique-ai:operators, unique-ai:unique-ai:onpremsecurity.
  • mode_feature_gaps Which features are missing outside SaaS? [partial]: Compliance matrix separates SSO/content filter/DLP/PAM/key capabilities by mode. Azure Chat Code Execution/voice and external web/providers require those services and cannot be assumed in an isolated environment. Sources: unique-ai:unique-ai:compliance, unique-ai:unique-ai:code, unique-ai:unique-ai:voice.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:install, unique-ai:unique-ai:single, unique-ai:unique-ai:operators, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:compliance, unique-ai:unique-ai:code, unique-ai:unique-ai:voice.

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.

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.

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

  • 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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:privacy, open-webui:open-webui:offline.

Unique AI

Agent cross-checked Support: partial

Hosted Azure documentation says no model training and disabled Microsoft prompt storage/human review; other provider routes require separate terms.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • No signed Azure amendment was inspected. Retention and review conditions for Anthropic, Gemini, Together, xAI and direct OpenAI research remain unverified; do not generalise the Azure-only policy.
  • vendor_training Does the vendor train on customer content? [supported]: Hosted retention policy says no customer data is used for AI/neural-network training. Public terms allow service development and anonymised metadata use; that is not a blanket prohibition of all secondary processing. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:terms.
  • provider_training Do model providers train on it under this product's contracts? [partial]: Hosted Azure deployment is separate from public OpenAI and training is excluded. Other catalogue providers/direct OpenAI research need their applicable customer terms. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:models, unique-ai:unique-ai:deepresearch.
  • provider_retention How long do model providers keep prompts, including for abuse monitoring? [supported]: For hosted Azure OpenAI, documents/prompts/answers process in memory only, with logging/human-review opt-out. Ordinary application chats persist in Unique databases. Sources: unique-ai:unique-ai:retention.
  • zero_retention Is zero data retention available, and on which plan? [partial]: Hosted Azure model calls use no provider content storage per opt-out; this is not zero retention of Unique application history, logs or other provider routes. Sources: unique-ai:unique-ai:retention.
  • human_review Can provider staff review content? [partial]: Hosted Azure guide says Microsoft prompt/response human review is disabled. Vendor staff need-to-know access and alternate model-provider review conditions are separate. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:terms, unique-ai:unique-ai:models, unique-ai:unique-ai:deepresearch, unique-ai:unique-ai:dpa.

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.

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.

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Chat content clearing, chat uploads, KB documents, contract-end content deletion, recoverable files, backups and audit records have separate policies. No common purge deadline is established for all copies.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; Chat, Knowledge Base and hosted retention configuration; customer-hosted policy separately controlled availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Contracted storage/provider region; hosted-policy timings not extended to every customer-hosted system; os=not specified.

Limitations

  • Hosted content policy expressly permits contract-specific variation. Its timings do not define API/DPA audit-record retention.
  • No tenant configuration, customer MSA, final backup purge or external-provider deletion fixture was inspected.
  • default_retention What is retained and for how long by default? [partial]: The chat-upload guide describes an admin-configured expiry, typically two weeks, for chat uploads. Hosted policy lists no minimum for KB/blob/vector/database content. Neither figure defines audit-event retention or proves a tenant's configured default. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:review2-retention.
  • admin_retention Can admins set retention periods? [supported]: DATA_RETENTION_IN_DAYS drives the daily midnight chat-content clearing job; unset/zero disables it. This clears the content categories named by the redaction guide, not all uploads, KB, external tool records or audit events. Sources: unique-ai:unique-ai:redaction.
  • user_deletion Can users delete their chats and files permanently? [partial]: The redaction guide says deleting a chat removes its Unique chat-content copy and marks the chat record deleted. Separate upload, KB, external-tool, soft-delete, backup and audit policies are not collapsed into that action. Sources: unique-ai:unique-ai:redaction.
  • contract_end_deletion What is deleted at contract end, and when? [partial]: For Unique-hosted ordinary content, the published policy states a standard 30-day post-termination period unless the customer contract differs. It separately describes recoverable files for 30 days after deletion and database backups for two further weeks. DPA 6.1 requires return/deletion subject to legal record-keeping. Audit-log classes and their contractual lifetime remain unknown under ADM-06; this is not a deadline for deletion of every copy. Sources: unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:redaction, unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-dpa.

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.

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.

Unique AI

Agent cross-checked Support: partial

The dated public DPA lists Microsoft, but a complete applicable current subprocessor/country schedule for all contracted model/tool routes was not retrieved. A technical provider catalogue is not substituted for that legal schedule.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; current platform infrastructure and enabled model/tool integrations availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Actual customer provider/country/transfer schedule unverified; os=not specified.

Limitations

  • The provider catalogue establishes technical choices, not each party's processor role or the legal schedule for a customer contract.
  • No sales contact, executed current MSA or nonpublic schedule was obtained.
  • subprocessor_list Is a dated sub-processor list published? [unknown]: The July 2025 public DPA Appendix A lists Microsoft for infrastructure, Cognitive/Azure OpenAI and email. The current technical catalogue offers other provider/tool routes, which may have different contractual roles. No applicable complete current legal schedule or executed customer supplement was retrieved; the Microsoft-only list is not presented as complete.
  • subprocessor_countries Which countries do sub-processors operate in? [unknown]: DPA Appendix A names CH or a client-chosen Microsoft location; technical model routes separately include regional and global processing. A complete current legal provider/country and support-access schedule for the chosen deployment was not retrieved.
  • change_notification Are customers notified of sub-processor changes? [unknown]: No applicable current processor-change notification/objection clause for the customer's full provider schedule was retrieved from the DPA or current contract-access documentation.
  • parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: The current contact page identifies Unique AI AG in Switzerland and regional entities. The public DPA uses Unique AG. Ultimate parent/beneficial-owner jurisdiction and a customer-specific contracting entity were not independently established. Sources: unique-ai:unique-ai:contact, unique-ai:unique-ai:review2-dpa.
  • transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [unknown]: No complete customer-content transfer-instrument mapping per non-CH/EU provider was retrieved. The website visitor privacy policy is not substituted for customer-content terms.
  • government_access_policy Is there a published government-access or transparency policy? [unknown]: No current customer-content government-request/transparency policy was retrieved for the complete contracted provider chain. General banking/DPA assurances do not establish such a policy.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:review2-models, unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:contact.

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.

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.

Unique AI

Agent cross-checked Support: partial

A public DPA and finance-specific compliance material are available; actual contractual amendments were not inspected.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • DPA negotiability and signed sector amendments, product-specific EU AI Act roles and exact sector assurance scope remain unverified. This records materials, not a compliance verdict.
  • dpa Is a DPA available, and is it negotiable? [partial]: DPA accepts click-through/use or signature and defines Unique as processor for hosted MT/ST. Negotiability is not specified. Sources: unique-ai:unique-ai:dpa.
  • revdsg_gdpr Does the DPA cover revDSG and GDPR? [partial]: DPA addresses GDPR, Swiss FDPIC oversight and MSA-defined laws; Compliance Layer identifies nFDAP/Swiss M329 amendment. Exact signed revDSG/GDPR scope requires MSA. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:compliance.
  • governing_law Which law and court govern the contract? [supported]: DPA 7 specifies Swiss substantive law and Zürich 1 courts unless mandatory GDPR/MSA otherwise. Public ToS similarly names Swiss law. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:terms.
  • ai_act_materials Is EU AI Act documentation provided? [partial]: Trust centre describes per-use-case conformity assessments; ISO42001 and AI governance material are public. A complete provider/deployer AI Act technical file is not established. Sources: unique-ai:unique-ai:trust, unique-ai:unique-ai:compliance.
  • sector_materials Are FINMA or other sector materials provided? [partial]: Compliance Layer names Microsoft M453 FINMA audit-rights amendment, M744 professional/banking secrecy and M329 CH-DPA for Unique-hosted deployments. Actual annexes and current signed scope are not public. Sources: unique-ai:unique-ai:compliance.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:compliance, unique-ai:unique-ai:terms, unique-ai:unique-ai:trust.

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.

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.

Unique AI

Agent cross-checked Support: partial

New public 2026 ATTESTA renewals establish ISO27001 and ISO9001 validity to 31 May 2029; the public TÜV SÜD ISO42001 certificate runs to 6 March 2028. SOC2 Type2 is vendor-documented, with full report evidence NDA-gated.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=ATTESTA 10 June 2026 renewals; TÜV SÜD 7 March 2025 certificate; plan=Contracted Unique AI platform; platform assurance; certificates cover the named legal entity and stated scopes, not every module/provider availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Certificates name Unique AG, Zurich, Switzerland; module/provider coverage depends on the stated audit scope; os=not specified.

Limitations

  • Current ISO27001/9001 evidence is the 2026 renewal plus matching register entries; the stale website-linked PDF is not used to deny current certification.
  • SOC chronology and access process are vendor-documented, not a reviewed independent SOC report. Certificate scopes are entity-specific and not a universal module/provider assurance.
  • iso_27001 ISO 27001 with scope and validity? [supported]: Inspected the 2026 ATTESTA Schweizer Zertifizierungsgesellschaft AG ISO27001:2022 certificate for Unique AG, registration 223-06-018.I. It covers software development/operation/trading/distribution and IT services, is issued 10 June 2026 after 4 June surveillance and expires 31 May 2029. The certificate-linked public register matches the number and expiry. The marketing-linked 2025 PDF is an older artifact, not the current renewal. Sources: unique-ai:unique-ai:review2-iso27001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:review2-iso-docs.
  • soc2 SOC 2 type, period and covered service? [partial]: The dedicated SOC page documents Type1 in December 2023 followed by Type2 in January 2025. This explains the historical Type1 references rather than proving an ongoing Type1-only state. Current Type2 status is a vendor claim; the auditor, actual report period and service/control scope were not inspected because the full report is NDA-gated. Sources: unique-ai:unique-ai:review2-soc.
  • c5 BSI C5 attestation? [unknown]: No public BSI C5 attestation was retrieved from the certification pages/trust centre or targeted first-party search.
  • other_certifications Which other certificates (27701, 42001, TISAX)? [partial]: Inspected ATTESTA ISO9001:2015 renewal 223-06-017.Q for the same Unique AG software/IT scope, expiring 31 May 2029, matched in the public register. Separately inspected TÜV SÜD South Asia ISO42001:2023 certificate 99 420 00001, valid 7 March 2025 to 6 March 2028, for development/deployment of financial-services SaaS using foundation or client models. Current full ISAE/FINMA report scope was not inspected. Sources: unique-ai:unique-ai:review2-iso9001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:iso42001.
  • report_access How can customers obtain reports? [supported]: The ISO documentation provides public certificate downloads. It says the ISO27001 Statement of Applicability requires a valid NDA. The dedicated SOC page likewise makes the audit report/certificate available on request after NDA. No NDA or sales request was made. Sources: unique-ai:unique-ai:review2-iso-docs, unique-ai:unique-ai:review2-soc.
  • pentest Are independent penetration test summaries available? [partial]: The public DPA describes internal/external security testing and the trust page describes tests/bug bounty. An independent penetration-test report, current scope or summary was not inspected. Sources: unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:trust.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-iso27001, unique-ai:unique-ai:review2-iso9001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:review2-iso-docs, unique-ai:unique-ai:iso42001, unique-ai:unique-ai:review2-soc, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:trust.

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

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:privacy, open-webui:open-webui:offline.

Unique AI

Agent cross-checked Support: partial

Deployment guides document encryption, isolated Single Tenant resources and optional IP filtering. Exact current MT PMK/CMK/HSM configuration and key sizes are not established across the conflicting pages.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; hosted MT/ST encryption and optional customer-controlled self-hosting availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Contracted Azure tenant/storage/backup region; actual key-vault/HSM location unverified; os=not specified.

Limitations

  • No exact RSA/HSM key size or actual MT PMK/CMK design is asserted. A customer-specific deployment/key diagram and key-vault region were not inspected.
  • Customer-generated imported keys held by Unique do not establish customer-exclusive key custody; full control is a separate self-hosting option.
  • encryption_at_rest Is data encrypted at rest? [partial]: The compliance matrix documents encryption at rest and in transit across deployment options, with AES256/TLS1.2+ in its controls text. No exact current RSA key size is asserted: the ST architecture says 2048-bit RSA-HSM while the hosted retention page says 4096-bit. An implementation-specific key design was not retrieved. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-retention.
  • customer_managed_keys Can the customer manage or hold the keys? [partial]: The infrastructure key guide allows a customer-generated key to be imported for a Unique-hosted Single Tenant, with Unique holding/managing it. It directs clients needing exclusive control of all storage keys to customer self-hosting. This is not HYOK or exclusive customer custody in Unique hosting. Actual MT PMK/CMK/HSM configuration is unknown because the key guide and hosted retention matrix disagree. Sources: unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:review2-retention.
  • private_networking Is private connectivity or IP restriction available? [partial]: The Single-Tenant WAF supports optional IP blocking. The separate SEE consumer endpoint is public TLS with optional allow-list and no standard private endpoint/peering. These are distinct scopes; other private-link options for the customer deployment were not verified. Sources: unique-ai:unique-ai:review2-single, unique-ai:unique-ai:security-export.
  • tenant_isolation How are customers separated in shared SaaS? [supported]: The Single-Tenant architecture describes a separate customer landing zone under Unique's subscription, isolating its storage/processing from other customers. This documents that ST architecture, not the isolation configuration of every hosted or customer-managed instance. Sources: unique-ai:unique-ai:review2-single.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:security-export.

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.

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

Unique AI

Agent cross-checked Support: partial

Unique documents general staff/external-party access controls and customer-controlled on-premises access. A professional-secrecy undertaking under § 203 StGB or Art. 321 StGB, its subprocessor flow-down and qualifying plan/add-on remain unverified. Financial-sector banking-secrecy amendments are recorded separately under DATA-06.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI; profession-specific eligibility and fees unpublished; add_ons=none stated; deployment_mode=not specified; region=Contracted hosting jurisdiction; customer-controlled on-premises access described separately from Unique-hosted access; os=not specified.

Limitations

  • No executed professional-secrecy undertaking or § 203 / Art. 321 contract was inspected. General DPA confidentiality is not treated as such an undertaking.
  • The M744 professional-secrecy wording appears in a banking-secrecy/financial-services framework; no inference is made to lawyers, doctors, auditors or tax advisers.
  • Customer-controlled on-premises access does not establish the same access conditions for Unique-hosted deployments or all model-provider routes. Full plaintext-access mapping remains unknown.
  • secrecy_undertaking Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: No public Unique AI-specific § 203 StGB or Art. 321 StGB secrecy undertaking covering staff was located in the DPA, compliance documentation or targeted first-party search on 21 October 2026. The DPA confidentiality commitment alone does not establish a professional-secrecy undertaking. No executed or negotiated customer agreement was inspected.
  • subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The DPA says employees, contractual subprocessors and other service providers are bound to confidentiality of sensitive information. A professional-secrecy-specific obligation extending through the subprocessor/model-provider chain was not verified. The Microsoft M744 banking-secrecy amendment mentioned in the financial-services framework is not counted as evidence of § 203 / Art. 321 coverage for professional secrecy holders.
  • secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: No qualifying professional-secrecy plan, dedicated offering, add-on tariff or named eligibility rule was located. The documented financial-services amendments and general deployment choices do not establish a separate § 203 / Art. 321 offering. Contract-specific terms and fees remain unknown.
  • content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: DPA Appendix B permits employees or external parties access to personal/confidential information on a need-to-know basis. For on-premises support, customers control remote connections and Unique staff cannot access a customer system without customer knowledge or full active participation. The on-premises architecture also allows operation without any Unique access under customer control. These sources do not exhaustively identify plaintext access at each hosted subprocessor/model provider or profession-specific access conditions. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:onpremsecurity.
  • secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: A public DPA and on-premises architecture describe confidentiality and access controls, but no profession-specific secrecy template or professional-body guidance was located. The compliance page describes Microsoft M453/M744/M329 in a financial-services context; those banking/FINMA disclosures belong to DATA-06 and do not establish the missing professional-secrecy contract.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:compliance.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Applicable current platform pricing unit, list tariff, included usage and overages remain unknown. A separately documented Single-Tenant SEE consumption/engineering charge is retained; legacy sales-conversation terms are excluded.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; platform subscription and separately enabled Single-Tenant SEE availability and deployment/provider configuration depend on the customer agreement; add_ons=SEE scope only where contracted; deployment_mode=not specified; region=Vendor currency and applicable invoicing terms not established for the platform; SEE guide separately quotes indicative CHF consumption; os=not specified.

Limitations

  • The SEE cost finding is scoped only to that Single-Tenant integration. It does not price the platform subscription or all modules.
  • The 2023 sales-conversation ToS is excluded as evidence of current Unique AI commercial terms; no sales quote or private contract was requested.
  • pricing_unit What is the pricing unit? [unknown]: No applicable current platform MSA/order form or tariff establishing seat, active-user, platform or usage pricing units was retrieved. The public 18 October 2023 ToS defines a sales-conversation intelligence service, so its subscription/Order Form clauses are not applied to current Unique AI.
  • list_prices What are list prices per plan, with date and currency? [unknown]: No applicable current platform list tariff, tier names or primary invoicing currency was retrieved from platform/contract documentation or targeted first-party search.
  • included_usage What usage is included? [unknown]: No applicable current platform agreement specifying included model tokens, storage or module allowances was publicly retrieved.
  • add_ons Which features cost extra? [partial]: Single-Tenant SEE passes through Azure consumption without markup; guide observes CHF20-50/month/environment, not a fixed quote, with initial engineering at agreed rates. Other module charges are unpublished. Sources: unique-ai:unique-ai:security-export.
  • overage What do usage beyond limits and premium models cost? [unknown]: No applicable current platform overage or premium-model sales tariff was retrieved. Cost-management model estimates are not substituted for a customer sales tariff.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:security-export, unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin.

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.

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.

Checked ; 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.

Unique AI

Agent cross-checked Support: partial

ALM-14 shared cost assumptions v1.4, 2026-10-21. Public enterprise pricing is insufficient for the required 200/1,000/5,000-user annual totals.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate.
  • cost_200 Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate.
  • cost_1000 Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate.
  • cost_5000 Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate.
  • variable_share Which part depends on usage? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate.
  • unknown_parts Which costs could not be priced? [supported]: Subscription/order pricing, usage billing, provider contracts, deployment operation, connectors, execution, training and support charges are not publicly priced. SEE consumption example alone cannot price the platform. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:platform, unique-ai:unique-ai:security-export.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:platform, unique-ai:unique-ai:security-export, unique-ai:unique-ai:ecb-fx.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

The public route is demo/evaluation by arrangement; self-service trial conditions were not established.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used.
  • free_tier Is there a free tier for business use? [unknown]: Is there a free tier for business use? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used.
  • self_serve_trial Is a self-serve business trial available? [unknown]: Is a self-serve business trial available? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used.
  • trial_scope Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used.
  • sales_gate Does meaningful evaluation require sales contact? [partial]: Current platform CTA requests a demo; public baseline ToS says Unique may offer evaluation at its discretion. This does not prove every meaningful evaluation is sales-gated. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:terms.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:terms.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:license-pin, open-webui:open-webui:enterprise.

Unique AI

Agent cross-checked Support: partial

Current platform minimums, term, cancellation and local invoicing remain unknown because the applicable agreement was not publicly retrieved. Current documentation makes legal contracts available on request; legacy sales-conversation renewal clauses are excluded.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; platform commercial agreement; actual agreement not inspected availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CHF/EUR invoicing and legal entity for a specific platform contract unverified; os=not specified.

Limitations

  • No current customer agreement or sales quote was requested. Contract availability on request does not establish price, term or cancellation conditions.
  • minimum_commitment What seat or spend minimum applies? [unknown]: No current platform seat/spend minimum was established from the public contract-access and platform pages.
  • contract_length What contract lengths are offered? [unknown]: No applicable current Unique AI agreement establishing subscription duration, renewal term or notice period was retrieved. The 2023 sales-conversation service term is not applied.
  • cancellation How can the contract be cancelled or reduced? [unknown]: Current Unique AI cancellation, refund, seat-reduction and nonrenewal rules were not retrieved. The 30-day renewal notice and quantity restrictions from the sales-conversation ToS are excluded.
  • local_invoicing Can it be invoiced in CHF or EUR from a European entity? [unknown]: CHF/EUR invoice currency, billing entity and local invoicing eligibility for a current platform contract were not established.
  • transparency_class Is pricing transparent, partial, quote-only or unknown? [partial]: The current governance framework says legal contracts and end-user T&Cs are available on request. No applicable public platform list tariff or complete commercial agreement was retrieved. This records an access/transparency gap, not a price or a customer-specific commitment. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin.

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.

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

Unique AI

Agent cross-checked Support: partial

The public reference repository uses restricted Unique License v1, while the Python SDK has an explicit MIT exception. Hosted platform component terms and enterprise-edition boundaries remain unverified.

Availability: source-only · Delivery: native
Scope: surfaces=Unique API and Python SDK, Unique AI Chat and administration; version=Unique-AG/ai commit afa596c9b4b0231895ff70f44029a9a525f746e9; plan=Public reference-code and Python SDK licences; current contracted Unique AI client/server/connector agreement remains unavailable; add_ons=none stated; deployment_mode=not specified; region=Public Unique License v1 specifies Swiss law and Zurich venue; this is not a hosted-service residency claim; os=not specified.

Limitations

  • The MIT exception applies to unique_sdk, not every directory or the hosted platform.
  • Root reference-code terms are not substituted for customer platform branding, seat or enterprise-edition conditions.
  • The 2023 sales-conversation service ToS remains excluded.
  • licence_type Which licence applies to each component? [partial]: The public Unique-AG/ai repository at afa596c9b4b0231895ff70f44029a9a525f746e9 defaults to Unique License v1, which restricts commercial use, distribution and modification without written approval. The unique_sdk directory is an explicit MIT exception, confirmed by LICENSE and package metadata. This is a component-level source-available/MIT distinction; current hosted client/server/connector customer terms and a full dependency inventory remain unknown. Sources: unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026, unique-ai:unique-ai:sdk-package-20261026.
  • branding_restrictions Do licence terms restrict branding or user counts? [partial]: Unique License v1 requires written approval to modify or redistribute covered reference code; the MIT SDK exception requires retention of copyright/licence notices. A current hosted-platform white-label/logo-removal obligation or a numerical user cap is not established by these public component licences. Sources: unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026.
  • enterprise_features_closed Are enterprise features in a separate closed edition? [unknown]: Current closed/open enterprise-edition boundaries were not established from an applicable component licence inventory. Public SDK/repository availability is not proof of the whole platform licence. Rechecked 2026-10-26 in Unique AI governance framework: contract access, Terms and Conditions Administration. No current customer MSA, quote, private schedule or gated contract was requested. The differently scoped 2023 sales-conversation ToS remains excluded.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin, unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026, unique-ai:unique-ai:sdk-package-20261026, unique-ai:unique-ai:review2-governance-20261026, unique-ai:unique-ai:review2-terms-admin-20261026.

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.

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.

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

Authorised content/report export exists, but full assistant/knowledge portability is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run.
  • chat_export Can admins export all chats? [partial]: Detailed interaction export includes user prompts/answers over a chosen period with privacy settings. Completeness across files, agent state and all historical chats was not tested. Sources: unique-ai:unique-ai:analytics.
  • assistant_export Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unknown. Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run.
  • knowledge_export Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? Unknown. Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run.
  • export_format Are formats documented and machine-readable? [partial]: Model usage CSV and detailed analytics exports are documented. DPA promises return in existing format, not a universal reusable assistant/knowledge format. Sources: unique-ai:unique-ai:cost, unique-ai:unique-ai:analytics, unique-ai:unique-ai:dpa.
  • post_termination_window How long can data be retrieved after termination? [partial]: Baseline ToS 11.4 offers recorded-call download/export on written request within 30 days; that does not establish a chat/assistant/KB exit window. DPA return is within reasonable time. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost, unique-ai:unique-ai:dpa, unique-ai:unique-ai:terms.

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.

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.

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

  • 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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: open-webui:open-webui:support, open-webui:open-webui:roadmap.

Unique AI

Agent cross-checked Support: partial

Enterprise support and a public multitenant status page are available; response times are contracted.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Guaranteed DE/FR/IT support, numeric hours/response times, dedicated uptime/credits and complete incident-history export were not established.
  • support_channels Which support channels are available on each plan? [supported]: Enterprise email and three-layer dedicated support escalation through customer team, CS and engineering. Hours/responses depend on SLA; extended-hours contract is extra. Sources: unique-ai:unique-ai:support.
  • support_languages Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. Guaranteed DE/FR/IT support, numeric hours/response times, dedicated uptime/credits and complete incident-history export were not established.
  • regional_presence Is there a DACH or Swiss entity, team or partner? [supported]: Unique AI AG lists Zürich, Unique Germany GmbH Berlin, plus UK/US/Singapore entities. Sources: unique-ai:unique-ai:contact.
  • uptime_sla Is there an uptime SLA with credits? [partial]: Support docs defer hours and response times to SLA contract; no public uptime/credit schedule was obtained. Baseline terms only promise commercially reasonable availability efforts. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:terms.
  • status_page Is there a public status page with history? [supported]: status.prod.unique.app publicly shows component/uptime history. Support docs scope it to multitenant accounts, not every dedicated environment. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:status.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:contact, unique-ai:unique-ai:terms, unique-ai:unique-ai:status.

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.

Open WebUI

Agent cross-checked Support: partial

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

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

  • 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 ; 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.

Unique AI

Agent cross-checked Support: partial

The vendor markets forward-deployed delivery and structured training; inclusion and cost remain unpriced.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

  • Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published.
  • onboarding_service Is guided onboarding included? [partial]: Homepage markets embedded forward-deployed experts helping business/IT ship use cases; exact licence-included rollout scope is contracted. Sources: unique-ai:unique-ai:homepage.
  • user_training Is end-user training offered, in which languages? [partial]: Vendor homepage describes structured programmes teaching users to use/build/scale; current languages and course entitlement are not specified. Sources: unique-ai:unique-ai:homepage.
  • use_case_library Are role-based use cases and templates provided? [supported]: Public documentation has finance-role workflows, Chat/Conduct guidance, configurable Suggested Prompts and agent examples. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct.
  • adoption_programme Is there a champion or adoption programme? [unknown]: Is there a champion or adoption programme? Unknown. Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published.
  • service_cost Which services cost extra? [unknown]: Which services cost extra? Unknown. Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:homepage, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct.

Sources

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

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

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

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

  5. Unique LLM availability overview unique-ai:unique-ai:models

    Lists contract-dependent provider/model availability, region SKUs, dated additions and retirements; CH Phoeniqs remains QA-only.

    Per-client availability; Azure/LiteLLM/Phoeniqs matrices; Recent changes · documented · Source date 2026-10-12 · Retrieved 2026-10-21

  6. Unique AI space configuration unique-ai:unique-ai:agent

    Documents admin instructions, configured model/tools, knowledge binding, prompts and people/group Can chat/Can manage access.

    Models; sources/tools; sharing; publishing · documented · Source date 2026-06-18 · Retrieved 2026-10-21

  7. Unique AI Conduct unique-ai:unique-ai:conduct

    Documents autonomous Python/Bash work, visible steps, approvals and stop, with per-chat files and restricted egress.

    GA release 2026.40; execution UI; limitations · documented · Source date 2026-09-30 · Retrieved 2026-10-21

  8. Unique release 2026.42 unique-ai:unique-ai:release42

    Hosted release 14 October 2026 makes chat sharing and Context Memory GA, labels Scheduled Tasks experimental, changes protected-file ingestion and documents current model additions/migrations.

    Release Overview; Chat Platform; RAG; Unique AI; Language Model · documented · Source date 2026-10-14 · Retrieved 2026-10-21

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

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

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

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

  13. Custom LXM connection unique-ai:unique-ai:customllm

    Documents operator-created external model endpoints, API/OAuth credentials and model groups.

    Technical insight; Create and Connect; Security · documented · Source date 2026-05-07 · Retrieved 2026-10-21

  14. Code Execution unique-ai:unique-ai:code

    Documents Azure Responses API Python execution, downloadable outputs, no outbound internet and model/file restrictions.

    Compatibility; output; limitations; governance · documented · Source date 2026-07-30 · Retrieved 2026-10-21

  15. Compliance Layer 3.0 unique-ai:unique-ai:compliance

    Describes FINMA/bank-secrecy/CH-DPA Microsoft amendments and deployment-specific assurance limitations.

    Legal framework; FSI amendments; deployment feature matrix · documented · Source date 2026-05-27 · Retrieved 2026-10-21

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

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

  18. Custom embedding models unique-ai:unique-ai:embeddings

    Documents custom embedding endpoints, one model per organisation and mandatory re-embedding after model/dimension changes.

    Setup; configuration; re-embedding · documented · Source date 2026-05-07 · Retrieved 2026-10-21

  19. On-premises security architecture unique-ai:unique-ai:onpremsecurity

    Documents full customer control and possible operation without Unique access, with customer models/infrastructure.

    Overview; custom setup · documented · Source date 2026-05-08 · Retrieved 2026-10-21

  20. IT operator documentation overview unique-ai:unique-ai:operators

    Describes dedicated Unique-managed, customer-cloud and full air-gapped on-premise modes.

    Supported deployment models · documented · Source date not stated · Retrieved 2026-10-21

  21. Code Execution unique-ai:unique-ai:review2-code

    The page allows selected Knowledge Base files to be preloaded with additionalUploadedDocuments. Its compatibility list includes Azure and LiteLLM OpenAI Responses-capable IDs despite Azure-only introduction/limitations. Azure sandbox controls are not proof of the LiteLLM execution region.

    Functionality; Limitations; All available models; Security & Governance; additionalUploadedDocuments · documented · Source date 2026-07-30 · Retrieved 2026-10-21

  22. Unique LLM availability overview unique-ai:unique-ai:review2-models

    The model catalogue separates provider routes, region/SKU choices and QA-only Swiss Phoeniqs. It is a technical availability inventory, not a complete legal subprocessor schedule.

    Provider and region matrices; Phoeniqs Model Service; recent changes · documented · Source date 2026-10-12 · Retrieved 2026-10-21

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

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

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

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

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

  28. Model usage and cost management unique-ai:unique-ai:cost

    Documents off-by-default estimated usage dashboards and enforced daily company/group/user model-call limits.

    Beta flags; daily limits; cost calculation; CSV · documented · Source date 2026-07-21 · Retrieved 2026-10-21

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

  30. Upload and Chat limits unique-ai:unique-ai:files

    Specifies 512 MB/file, 30 files/batch, default forced retrieval for selected uploads and configurable expiry.

    Production limits; retrieval; expiry · documented · Source date 2026-06-28 · Retrieved 2026-10-21

  31. Supported file types unique-ai:unique-ai:filetypes

    Lists common Office/PDF/text formats and general ingestion limitations that differ from the newer chat-specific limits.

    Types; exceptions; ingestion quality · documented · Source date 2026-05-09 · Retrieved 2026-10-21

  32. Unique file ingestion administration unique-ai:unique-ai:file-ingestion-20261026

    Base ingestion lacks scanned-PDF OCR. MDI supports image-based PDFs; Docling has partial support. MDI must be provisioned and enabled per folder or chat Space, and the guide distinguishes experimental image-content extraction and deprecated agentic ingestion.

    Ingestion overview capability table; Enable MDI; Enable MDI for Upload in Chat · documented · Source date not stated · Retrieved 2026-10-26

  33. Knowledge scope permissions unique-ai:unique-ai:kbpermissions

    Describes query filtering by user/group scopes, but older SharePoint permission statements differ from the newer connector guide.

    Scopes; source integration limits · documented · Source date 2026-05-07 · Retrieved 2026-10-21

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

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

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

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

  38. SharePoint connector unique-ai:unique-ai:sharepoint

    Documents periodic indexed sync, optional content-and-permissions mode, site selection and absent label-level detection.

    Modes; permission sync; limitations · documented · Source date 2026-07-06 · Retrieved 2026-10-21

  39. Confluence connector unique-ai:unique-ai:confluence

    Documents Cloud/Data Center content sync without source-permission synchronisation.

    Requirements; sync; limitations · documented · Source date 2026-06-28 · Retrieved 2026-10-21

  40. Unique platform overview unique-ai:unique-ai:platform-overview-20261026

    The platform architecture names Google Drive and Salesforce among knowledge sources, alongside SharePoint/OneDrive, Confluence and Teams/Outlook. It does not provide per-connector consent, rollout or price entitlements.

    Connectors and Knowledge Sources diagram · documented · Source date not stated · Retrieved 2026-10-26

  41. Unique release 2026.40 unique-ai:unique-ai:release40-20261026

    GA HTML dashboards can list, enable and sign in to MCP connectors, with Salesforce and Yahoo Finance named examples. Contract/module enablement and personal connection state still apply.

    Hosted September 30 2026; Chat Experience, GA HTML connector dashboards · documented · Source date 2026-09-30 · Retrieved 2026-10-26

  42. Permission cache timing unique-ai:unique-ai:permissioncache

    Describes usual subsecond internal permission propagation without a hard upper bound, and stale rules after a missed broadcast.

    Expected timing; degraded scenarios · documented · Source date 2026-09-22 · Retrieved 2026-10-21

  43. Single-tenant key management unique-ai:unique-ai:keys

    Explains why client-held keys are unavailable across all Single Tenant data stores and directs full key control to self-hosting.

    Big picture; BYOK/CYOK/HYOK; storage locations · documented · Source date 2026-05-27 · Retrieved 2026-10-21

  44. Retention and deletion at Unique unique-ai:unique-ai:retention

    Documents no training, Azure abuse-monitoring opt-out, post-termination retention and backup exceptions.

    Hosted-only scope; Azure provider retention; deletion; encryption · documented · Source date 2026-05-04 · Retrieved 2026-10-21

  45. Context Memory in Unique AI Chat unique-ai:unique-ai:memory

    Documents private per-user cross-chat memory, edit/disable controls and an explicit warning that disabling does not delete the stored profile.

    Private profile; edit and disable; web-search restriction · documented · Source date 2026-09-15 · Retrieved 2026-10-21

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

  47. Unique AI Chat unique-ai:unique-ai:chat

    Describes the user chat workspace and configurable tools.

    Features and access · documented · Source date 2026-09-03 · Retrieved 2026-10-21

  48. Access role concept unique-ai:unique-ai:roles

    Defines identity, application, space and knowledge-scope permissions, including delegated management roles.

    Four access layers · documented · Source date 2026-05-07 · Retrieved 2026-10-21

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

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

  51. MCP tools for spaces unique-ai:unique-ai:mcp

    Describes feature-flagged beta MCP clients with organisation and per-space connector/tool controls.

    Beta warning; flags; selective tool enablement · documented · Source date 2026-05-21 · Retrieved 2026-10-21

  52. MCP Hub security governance unique-ai:unique-ai:hub

    Documents per-user token routing, approved origin restrictions and tool-call correlation; some DLP/elicitation pipeline measures are planned.

    Authentication; governance; planned request pipeline · documented · Source date 2026-08-26 · Retrieved 2026-10-21

  53. Deep Research tool unique-ai:unique-ai:deepresearch

    Documents experimental research/report engine, with separate external OpenAI-engine data flows and limited current tools.

    Experimental warning; engines; user flow · documented · Source date 2026-05-09 · Retrieved 2026-10-21

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

  55. Web Search tool unique-ai:unique-ai:websearch

    Documents multiple search engines, source citations and experimental query review/screening; conversation context may leave through queries.

    Modes; engines; external-query warning · documented · Source date 2026-05-20 · Retrieved 2026-10-21

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

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

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

  59. Python SDK documentation unique-ai:unique-ai:sdk

    Documents SDK/public API access and customer-operated modules with event-driven webhook integration.

    Public API; webhook verification; personal/app keys · documented · Source date 2026-05-08 · Retrieved 2026-10-21

  60. Scheduled Tasks unique-ai:unique-ai:scheduled

    Documents off-by-default recurring tasks running with user permissions; unattended approvals/questions can stop a run.

    Beta warning; task settings; runs and limits · documented · Source date 2026-10-12 · Retrieved 2026-10-21

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

  62. Scheduled Tasks unique-ai:unique-ai:review2-scheduled

    Scheduled Chat/Conduct tasks offer Automatic or Manual approval. The newer release labels scheduling Experimental and feature-flagged; unattended automatic approval is not mandatory human confirmation.

    At a glance; task Approval setting; unattended runs · documented · Source date 2026-10-12 · Retrieved 2026-10-21

  63. Unique release 2026.42 unique-ai:unique-ai:review2-release42

    Release 2026.42 makes Shared Chats GA, on by default per company with a per-Space toggle and preservation of explicit settings. Scheduled Tasks remain Experimental and feature-flagged.

    Highlights; Chat Platform; Conduct scheduling flag · documented · Source date 2026-10-14 · Retrieved 2026-10-21

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

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

  66. Knowledge Base MCP user guide unique-ai:unique-ai:mcpkb

    Documents external-assistant search/read with user permissions, citations and optional KB scope restrictions.

    Connecting; access; limitations · documented · Source date 2026-10-05 · Retrieved 2026-10-21

  67. API model usage tracking unique-ai:unique-ai:api-usage

    Documents public API/SDK model-call usage tracking; some other internal-service calls are outside scope and REST usage retrieval is planned.

    Coverage; flags; limitations · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

  73. Translator space unique-ai:unique-ai:translation

    Documents beta Office-file/text translation with glossary pre/postprocessing and potential layout disruption.

    Beta; glossary; document types; limitations · documented · Source date 2026-05-06 · Retrieved 2026-10-21

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

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

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

  77. Voice administration unique-ai:unique-ai:voice

    Requires Azure AI Speech Services and describes potential public/backbone audio routing.

    Dependencies; networking; limitations · documented · Source date 2026-05-07 · Retrieved 2026-10-21

  78. Unique data processing addendum unique-ai:unique-ai:dpa

    Public DPA covers hosted chat/recordings, lists Microsoft, Swiss storage, return/deletion, confidentiality and ten-year audit-log retention.

    Sections 2-3, 6-7; Appendices A-B; July 2025 footer · documented · Source date not stated · Retrieved 2026-10-21

  79. Using Voice unique-ai:unique-ai:voice-user

    Documents prompt dictation with EN/DE/FR/IT, immediate audio discard and dialect/recognition limitations.

    Prompt dictation; privacy note; supported languages · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

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

  87. Single sign-on setup unique-ai:unique-ai:sso

    Documents Zitadel SSO across deployment types, group claims and automatic SAML account creation/update.

    Entra ID OIDC; SAML; managed-tenant setup · documented · Source date 2026-05-07 · Retrieved 2026-10-21

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

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

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

  91. SCIM provisioning unique-ai:unique-ai:scim

    Documents Unique SCIM endpoint/key for IdP user/group synchronisation.

    Prerequisites and Entra setup · documented · Source date 2026-05-07 · Retrieved 2026-10-21

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

  93. Analytics interface unique-ai:unique-ai:analytics

    Documents adoption reports, detailed chat/model/tool exports and randomised or stable pseudonymous identifiers.

    Reports; anonymisation; detailed interactions · documented · Source date 2026-09-03 · Retrieved 2026-10-21

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

  95. Audit logs unique-ai:unique-ai:audit

    Defines privileged API event logging with self-service exclusions, deployment-specific retention and request-based export.

    Scope; exclusions; default basic mode; retention and export · documented · Source date 2026-05-07 · Retrieved 2026-10-21

  96. Security Events Export unique-ai:unique-ai:security-export

    Documents Single-Tenant-only Azure Activity/Defender Event Hub export with seven-day replay, client-region selection and consumption cost.

    Availability; delivered events; retention; cost · documented · Source date not stated · Retrieved 2026-10-21

  97. Audit logs unique-ai:unique-ai:review2-audit

    API audit-event guide specifies basic/verbose modes and MT 90-day/ST five-year operational retention. It does not reconcile those event classes to DPA audit logs or a customer-specific contractual override.

    About audit logs; modes; Single and Multi Tenant Clients · documented · Source date 2026-05-07 · Retrieved 2026-10-21

  98. Unique data processing addendum unique-ai:unique-ai:review2-dpa

    The public July 2025 DPA specifies ten-year audit logs and CH storage, while Appendix A lists Microsoft and a client-chosen location. No signed current provider schedule, retention override or contract-precedence mapping was inspected.

    Sections 3.15 and 6.1; Appendix A; July 2025 footer · documented · Source date not stated · Retrieved 2026-10-21

  99. Retention and deletion at Unique unique-ai:unique-ai:review2-retention

    Hosted-only policy separates ordinary post-termination content retention, recoverable files and backups and permits contract customisation. Its log/key statements are not reconciled to audit-event/DPA/key-management scopes.

    Purpose; Data retention; Deletion after termination; Backups; Encryption in Place · documented · Source date 2026-05-04 · Retrieved 2026-10-21

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

  101. Data leakage prevention integration unique-ai:unique-ai:dlp

    Describes customer-operated HTTPS/DLP proxy and post-chat analytics scanning rather than a default native PII-redaction feature.

    Proxy; analytics API; compatibility · documented · Source date 2026-05-07 · Retrieved 2026-10-21

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

  103. Single-tenant security architecture unique-ai:unique-ai:single

    Documents separate Azure landing zone, network restrictions, retention and Unique-managed infrastructure keys.

    Azure resources; SSO; encryption; monitoring · documented · Source date 2026-05-28 · Retrieved 2026-10-21

  104. Terms and conditions administration unique-ai:unique-ai:policy

    Documents first-login acceptance, custom terms under an MSA and version/agreement export through GraphQL.

    First-login acceptance; MSA condition; API export · documented · Source date 2026-05-07 · Retrieved 2026-10-21

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

  106. Single-tenant key management unique-ai:unique-ai:review2-keys

    May 2026 key guide distinguishes imported customer-generated keys held by Unique from customer-exclusive key control via self-hosting. Its MT/ST CMK statement differs from the hosted retention page; actual MT configuration is unverified.

    Infrastructure-only scope; PMK; BYOK/CYOK/HYOK; Summary · documented · Source date 2026-05-27 · Retrieved 2026-10-21

  107. Single-tenant security architecture unique-ai:unique-ai:review2-single

    Single-tenant guide documents separate landing zone, WAF/IP controls and Unique-managed encryption. Its 2048-bit RSA-HSM description differs from the hosted retention page; this does not establish an exact current key design.

    Overview; Encryption; Data classification · documented · Source date 2026-05-28 · Retrieved 2026-10-21

  108. Compliance Layer 3.0 unique-ai:unique-ai:review2-compliance

    The deployment matrix documents CH North multitenant hosting and selectable single/client-hosted regions, with deployment-specific controls. These are options, not proof of a particular customer contract or current key configuration.

    Digital Sovereignty; Feature overview matrix · documented · Source date 2026-05-27 · Retrieved 2026-10-21

  109. Unique installation models unique-ai:unique-ai:install

    Enumerates multi-tenant, single-tenant, customer-managed and on-premise deployments.

    Overview · documented · Source date 2025-08-06 · Retrieved 2026-10-21

  110. Unique terms of service unique-ai:unique-ai:terms

    Describes a sales-conversation service with Order Form subscription fees, nonrenewal notice, recording export and proprietary rights; applicability to the current AI MSA needs confirmation.

    Sections 1-2, 4-6, 11, 17-18 · documented · Source date not stated · Retrieved 2026-10-21

  111. Chat data redaction and retention unique-ai:unique-ai:redaction

    Documents scheduled clearing of chat content and workspace records, with separate upload/KB retention rules.

    What is cleared; exclusions; administrator settings · documented · Source date 2026-10-18 · Retrieved 2026-10-21

  112. Unique AI contact unique-ai:unique-ai:contact

    Lists Unique AI AG in Zürich, Unique Germany GmbH in Berlin and other regional entities.

    Office addresses · documented · Source date not stated · Retrieved 2026-10-21

  113. Unique AI governance framework: contract access unique-ai:unique-ai:review2-governance

    The current governance framework says legal contracts and end-user T&Cs are available on request; the public page does not expose platform subscription or component licence clauses.

    Individual standards; Legal contracts; End-User Terms and Conditions · documented · Source date 2026-04-12 · Retrieved 2026-10-21

  114. Unique AI trust centre unique-ai:unique-ai:trust

    Describes CH Azure storage separately from globally routed inference and claims ISO/SOC assurances, with differing SOC types in the FAQ.

    Enterprise security; compliance standards; FAQ · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  115. Unique ISO/IEC 42001 certificate unique-ai:unique-ai:iso42001

    TÜV SÜD certificate covers development/deployment SaaS for financial services using pretrained foundation models or client-provided models, valid to 6 March 2028.

    One page; registration 99 420 00001; scope and dates · certificate-verified · Source date 2025-03-07 · Retrieved 2026-10-21
    Issuer: TÜV SÜD South Asia Private Limited. Scope: Unique AG, Stockerstr.34, Zurich. Development and deployment of SaaS for financial-services clients based on pretrained AI foundation models using Azure OpenAI or client-provided models, including client on-premise models.. Valid 2025-03-07 to 2028-03-06

  116. ISO Certifications and current downloads unique-ai:unique-ai:review2-iso-docs

    The ISO documentation links 2026 English/German ATTESTA ISO27001 and ISO9001 renewals, plus the 2025 ISO42001 certificate; ISO27001 SoA requires an NDA.

    Certificate ISO27001; ISO9001; ISO42001; Statement of Applicability · documented · Source date 2026-08-05 · Retrieved 2026-10-21

  117. Unique AG ISO27001 ATTESTA 2026 renewal unique-ai:unique-ai:review2-iso27001

    Inspected ATTESTA ISO27001:2022 renewal for Unique AG, registration 223-06-018.I, issued 10 June 2026 after 4 June surveillance, valid until 31 May 2029. The certificate-linked public register lists the same number and expiry.

    One-page 2026 English certificate; scope, registration, surveillance, printed expiry · certificate-verified · Source date 2026-06-10 · Retrieved 2026-10-21
    Issuer: ATTESTA Schweizer Zertifizierungsgesellschaft AG. Scope: Unique AG, Stockerstrasse 34, 8002 Zürich: development, operation, trading and distribution of software and provision of IT/information-technology services; ISO27001:2022 information security management. Valid from an unstated date to 2029-05-31

  118. Unique AG ISO9001 ATTESTA 2026 renewal unique-ai:unique-ai:review2-iso9001

    Inspected ATTESTA ISO9001:2015 renewal for Unique AG, registration 223-06-017.Q, issued 10 June 2026 after 4 June surveillance, valid until 31 May 2029. The certificate-linked public register lists the same number and expiry.

    One-page 2026 English certificate; scope, registration, surveillance, printed expiry · certificate-verified · Source date 2026-06-10 · Retrieved 2026-10-21
    Issuer: ATTESTA Schweizer Zertifizierungsgesellschaft AG. Scope: Unique AG, Stockerstrasse 34, 8002 Zürich: development, operation, trading and distribution of software and provision of IT/information-technology services; ISO9001:2015 quality management. Valid from an unstated date to 2029-05-31

  119. Certificate-linked public register: Unique AG unique-ai:unique-ai:review2-iso-register

    Public certificate-linked register lookup for Unique AG lists registrations 223-06-018.I and 223-06-017.Q, Zurich, software/IT scope and expiry 31 May 2029. Standard/status text fields are blank; certificate PDFs supply the standards.

    Unique AG result rows; registration, scope, expiry · documented · Source date not stated · Retrieved 2026-10-21

  120. SOC2 Type2: chronology and report access unique-ai:unique-ai:review2-soc

    The dedicated SOC page explains Type1 in December 2023 followed by Type2 in January 2025; audit report and certificate are available only on request after NDA. Auditor, service scope and actual reporting period were not publicly inspected.

    SOC2 Type2 timeline; Certificates/report access · vendor-claimed · Source date 2026-04-12 · Retrieved 2026-10-21

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

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

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

  124. Terms and Conditions Administration unique-ai:unique-ai:review2-terms-admin

    Current platform T&C administration refers to a customer MSA and gated admin export; it does not publish the vendor platform agreement or determine subscription/IP/branding clauses.

    Overview; MSA exceptions; Modifying/Exporting Terms and Conditions · documented · Source date 2026-05-08 · Retrieved 2026-10-21

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

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

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

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

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

  130. Unique AI platform unique-ai:unique-ai:platform

    Markets a modular finance platform with governed connectors, frontend, financial agents and APIs.

    Frontend, financial agents, MCP Hub; deployment section · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  131. ECB euro foreign exchange reference rates, 20 October 2026 unique-ai:unique-ai:ecb-fx

    ECB records EUR 1 = USD 1.1215 and CHF 0.9237 on 20 October 2026; derived USD to EUR is 1/1.1215 and CHF to EUR is 1/0.9237.

    Cube time="2026-10-20": USD and CHF · documented · Source date 2026-10-20 · Retrieved 2026-10-21

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

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

  134. Unique AI governance framework: contract access unique-ai:unique-ai:review2-governance-20261026

    The current governance framework says legal contracts and end-user T&Cs are available on request; the public page does not expose platform subscription or component licence clauses.

    Individual standards; Legal contracts; End-User Terms and Conditions · documented · Source date 2026-04-12 · Retrieved 2026-10-26

  135. Unique public reference repository licence unique-ai:unique-ai:reference-licence-20261026

    The public repository defaults to Unique License v1 unless an explicit licence says otherwise; commercial use, distribution and modifications require prior approval. The default is restricted source-available, not an OSI open-source licence.

    LICENSE, repository-wide disclaimer and exceptions · documented · Source date not stated · Retrieved 2026-10-26

  136. Unique License v1 unique-ai:unique-ai:unique-licence-v1-20261026

    The published full licence permits personal noncommercial use and requires prior written approval for commercial use, distribution and modification, with separate component-licence exceptions. Swiss law and Zurich venue are specified.

    Grant, Restrictions, Open Source Components, Governing Law · documented · Source date 2024-09-24 · Retrieved 2026-10-26

  137. Unique Python SDK MIT licence unique-ai:unique-ai:sdk-licence-20261026

    The Python SDK directory has an explicit MIT licence permitting commercial use and modification subject to notice requirements; this exception does not license the hosted platform.

    unique_sdk/LICENSE, explicit component exception · documented · Source date not stated · Retrieved 2026-10-26

  138. Unique SDK package metadata unique-ai:unique-ai:sdk-package-20261026

    At the pinned October 23 repository commit, unique_sdk package metadata declares MIT, consistent with its component licence. Repository/package version is not treated as the hosted release date.

    project name/version and licence · documented · Source date not stated · Retrieved 2026-10-26

  139. Terms and Conditions Administration unique-ai:unique-ai:review2-terms-admin-20261026

    Current platform T&C administration refers to a customer MSA and gated admin export; it does not publish the vendor platform agreement or determine subscription/IP/branding clauses.

    Overview; MSA exceptions; Modifying/Exporting Terms and Conditions · documented · Source date 2026-05-08 · Retrieved 2026-10-26

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

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

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

  143. Enterprise support unique-ai:unique-ai:support

    Provides public multitenant status link, enterprise email and a contract-specific dedicated support model.

    Contact; dedicated support model; hours · documented · Source date not stated · Retrieved 2026-10-21

  144. Unique public system status unique-ai:unique-ai:status

    Public status page displays service/API/collector components and historical uptime panels; dedicated environments are outside the documented status scope.

    Component and 90-day uptime panels · documented · Source date not stated · Retrieved 2026-10-21

  145. Unique AI finance platform unique-ai:unique-ai:homepage

    Markets embedded experts and structured training programmes for finance users and IT.

    Forward-Deployed Engineers and training section · vendor-claimed · Source date not stated · Retrieved 2026-10-21