--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/anythingllm-vs-omnifact/" data_url: "https://onaihq.com/compare/agents/anythingllm-vs-omnifact/data.json" generated_at: 2026-10-27 last_checked_at: 2026-10-26 last_cross_checked_at: 2026-10-26 next_check_at: 2026-12-20 publisher: "onAI" --- # AnythingLLM vs Omnifact > Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI. This comparison has 44 criteria with sourced findings for both products, including 44 that a second agent cross-checked for both. 51 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. It does not declare a winner. A missing sourced finding is not evidence that a capability is absent. - AnythingLLM source checks: 2026-10-21 to 2026-10-26. - Omnifact source checks: 2026-10-21. - Canonical HTML: https://onaihq.com/compare/agents/anythingllm-vs-omnifact/ - Machine-readable JSON: https://onaihq.com/compare/agents/anythingllm-vs-omnifact/data.json - Methodology: https://onaihq.com/compare/agents/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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The customer selects provider/model combinations at system, workspace and Agent level; optional routing can choose per message. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - providers: Documented integrations include OpenAI, Azure, Anthropic, Google, Bedrock, Mistral, Cohere, OpenRouter, LiteLLM and local servers. Actual selectable models require configured accounts/endpoints; no endpoint was exercised. - current_models: Which current models are selectable on this plan? A complete current selectable-model catalog was not captured from configured provider accounts. - auto_routing: Model Router supports ordered rules and a fallback model, including LLM-classified rules. A complete chosen-model display/test was not established. - multimodal_input: System/workspace routes can accept image input with compatible models; exact audio/file and per-model behavior was not tested. - providers — Which model providers are available? [partial]: Documented integrations include OpenAI, Azure, Anthropic, Google, Bedrock, Mistral, Cohere, OpenRouter, LiteLLM and local servers. Actual selectable models require configured accounts/endpoints; no endpoint was exercised. Sources: anythingllm:anythingllm:models, anythingllm:anythingllm:llmconfig. - current_models — Which current models are selectable on this plan? [unknown]: current_models: Which current models are selectable on this plan? A complete current selectable-model catalog was not captured from configured provider accounts. - user_choice — Can users pick the model per chat? [supported]: System/workspace/Agent selections are configurable; the current built-in provider also has a chat model picker. Sources: anythingllm:anythingllm:llmconfig, anythingllm:anythingllm:built-in. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [partial]: Model Router supports ordered rules and a fallback model, including LLM-classified rules. A complete chosen-model display/test was not established. Sources: anythingllm:anythingllm:router. - multimodal_input — Which models accept images, audio or files? [partial]: System/workspace routes can accept image input with compatible models; exact audio/file and per-model behavior was not tested. Sources: anythingllm:anythingllm:models, anythingllm:anythingllm:constants-pin. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:models, anythingllm:anythingllm:llmconfig, anythingllm:anythingllm:built-in, anythingllm:anythingllm:router, anythingllm:anythingllm:constants-pin #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Manual selection spans OpenAI, Anthropic, Google and Mistral with EU/direct routes and tier controls. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise managed model catalogue; customer API keys and custom/self-hosted endpoints require Enterprise BYOK; add_ons=Enterprise BYOK for custom provider endpoints; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - current_models: Public text catalogue: GPT6Sol/Luna,5.6Sol/Terra/Luna,5.5,5.4/mini,5.2,5.1,5/mini/nano,4.1/mini/nano,4o/mini,4,3.5; Claude Opus5.5/5/4.8/4.7/4.6/4.5/4.1/4, Sonnet5.5/5/4.6/4.5/4, Haiku5.5/4.5; Gemini4Argon,3.8/3.7/3.6/3.5Flash,3.5Flash Lite,3.1Pro/Flash Lite,3Pro,2.5Pro/Flash,2.0Flash/Flash Lite; Mistral Medium3.5/3, Large3, Small4, Nemo, Ministral8B, Pixtral Large, Codestral, Devstral Small. Each is subject to admin enablement, tier, route and provider availability; not independently tested in picker. - multimodal_input: Image input only for capable selected models; experimental audio uploads need audio-capable models. Extracted document text and code tools are separate paths; no complete model-by-model native audio matrix was established. - Unverified auto_routing: No documented automatic cross-model routing strategy or chosen-model display after automatic routing was established; autonomous tool selection is separate from model routing. - providers — Which model providers are available? [partial]: Pro/Enterprise managed provider options include OpenAI/AzureOpenAI, Anthropic, Google/Vertex and Mistral subject to workspace configuration. Customer API keys, custom OpenAI-compatible endpoints and self-hosted model connections require Enterprise BYOK. Optional DPA-listed Groq is not treated as a currently selectable managed model. Sources: omnifact:omnifact:providers-rev2, omnifact:omnifact:pricing-rev2, omnifact:omnifact:models. - current_models — Which current models are selectable on this plan? [partial]: Public text catalogue: GPT6Sol/Luna,5.6Sol/Terra/Luna,5.5,5.4/mini,5.2,5.1,5/mini/nano,4.1/mini/nano,4o/mini,4,3.5; Claude Opus5.5/5/4.8/4.7/4.6/4.5/4.1/4, Sonnet5.5/5/4.6/4.5/4, Haiku5.5/4.5; Gemini4Argon,3.8/3.7/3.6/3.5Flash,3.5Flash Lite,3.1Pro/Flash Lite,3Pro,2.5Pro/Flash,2.0Flash/Flash Lite; Mistral Medium3.5/3, Large3, Small4, Nemo, Ministral8B, Pixtral Large, Codestral, Devstral Small. Each is subject to admin enablement, tier, route and provider availability; not independently tested in picker. Sources: omnifact:omnifact:models. - user_choice — Can users pick the model per chat? [supported]: Picker changes before/within a conversation and shows provider logo, model name and region flag. Reasoning effort has Low/Medium/High/Extra High depending on model. Sources: omnifact:omnifact:select. - 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. No documented automatic cross-model routing strategy or chosen-model display after automatic routing was established; autonomous tool selection is separate from model routing. - multimodal_input — Which models accept images, audio or files? [partial]: Image input only for capable selected models; experimental audio uploads need audio-capable models. Extracted document text and code tools are separate paths; no complete model-by-model native audio matrix was established. Sources: omnifact:omnifact:files, omnifact:omnifact:groups-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:providers-rev2, omnifact:omnifact:dpa-rev2, omnifact:omnifact:models, omnifact:omnifact:select, omnifact:omnifact:files, omnifact:omnifact:groups-rev2, omnifact:omnifact:pricing-rev2 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dated releases and version-specific changelogs are public, but the three-release lag benchmark was not measured. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - release_lag_days: What was the lag for each of the last three major releases, per provider? No paired last-three-major-release availability dates or guaranteed model-deprecation notice window was established. The built-in Desktop engine migration removes old downloaded models when accepted. - deprecation_notice: How much notice is given before a model is removed? No paired last-three-major-release availability dates or guaranteed model-deprecation notice window was established. The built-in Desktop engine migration removes old downloaded models when accepted. - version_pinning: Operators choose remote model IDs or download local GGUF models. Provider retention of old remote snapshots is outside the application’s control. - 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 paired last-three-major-release availability dates or guaranteed model-deprecation notice window was established. The built-in Desktop engine migration removes old downloaded models when accepted. - changelog — Is there a dated public model changelog? [supported]: GitHub releases and Desktop changelogs document dated changes; v1.18.0 was published 2026-10-13. Sources: anythingllm:anythingllm:releases, anythingllm:anythingllm:changelog. - 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 paired last-three-major-release availability dates or guaranteed model-deprecation notice window was established. The built-in Desktop engine migration removes old downloaded models when accepted. - version_pinning — Can an admin keep an older model version? [partial]: Operators choose remote model IDs or download local GGUF models. Provider retention of old remote snapshots is outside the application’s control. Sources: anythingllm:anythingllm:generic, anythingllm:anythingllm:built-in. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:releases, anythingllm:anythingllm:changelog, anythingllm:anythingllm:generic, anythingllm:anythingllm:built-in #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dated model/feature changelog exists; exact release lag and fixed deprecation policy are unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Unverified release_lag_days, deprecation_notice, version_pinning: Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established. - 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. Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established. - changelog — Is there a dated public model changelog? [supported]: Monthly release notes updated2026-10-20; individual feature posts date Gemini4Argon October 13, Haiku5.5 October 8, Sonnet5.5 September 28 and GPT6/Opus5.5 September 22. Sources: omnifact:omnifact:changes, omnifact:omnifact:blog. - deprecation_notice — How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? Unknown. Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established. - version_pinning — Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unknown. Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:changes, omnifact:omnifact:blog ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial BYO provider keys, customer cloud contracts and generic compatible endpoints are documented; provider spend is separate from software licensing. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - byo_restrictions: Tool use and modalities depend on provider/model support; Cloud has additional explicit platform limits. No universal BYO feature-parity guarantee was established. - own_api_keys — Can the customer use its own provider API keys? [supported]: Customers configure credentials for their selected cloud providers. Managed Cloud also asks customers to bring an LLM API key. Sources: anythingllm:anythingllm:models, anythingllm:anythingllm:cloud. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [supported]: Azure OpenAI, AWS Bedrock and Vertex have distinct documented configuration routes using customer accounts. Sources: anythingllm:anythingllm:azure, anythingllm:anythingllm:bedrock, anythingllm:anythingllm:vertex. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [supported]: Generic OpenAI supports an operator-configured compatible provider URL and settings. Sources: anythingllm:anythingllm:generic. - byo_pricing — Does BYO change the licence price? [supported]: The self-hosted repository is MIT with no per-seat fee; customer provider/hosting costs remain separate. Cloud charges for the managed instance and still uses BYO inference. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cloud. - byo_restrictions — Which features stop working with BYO? [partial]: Tool use and modalities depend on provider/model support; Cloud has additional explicit platform limits. No universal BYO feature-parity guarantee was established. Sources: anythingllm:anythingllm:cloud-limits, anythingllm:anythingllm:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:models, anythingllm:anythingllm:cloud, anythingllm:anythingllm:azure, anythingllm:anythingllm:bedrock, anythingllm:anythingllm:vertex, anythingllm:anythingllm:generic, anythingllm:anythingllm:license, anythingllm:anythingllm:cloud-limits #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise BYOK supports own provider accounts and custom OpenAI-compatible connections. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise BYOK, customer provider contracts; add_ons=Customer provider charges separate; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - own_cloud_contract: Supported environments include Azure OpenAI, Vertex Anthropic/Vertex Google; model settings mention AWSBedrock via custom endpoints. Customer deployment/contract setup details not fully specified. - byo_pricing: BYOK moves model costs to customer account/negotiated rates; Enterprise licence adjustment is quote-only. - Unverified byo_restrictions: No complete BYOK-specific feature failure/parity matrix or public licence discount was established. - own_api_keys — Can the customer use its own provider API keys? [supported]: Enterprise only; connects own provider API keys, charges provider account and bypasses standard Omnifact rate limits. Sources: omnifact:omnifact:providers. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Supported environments include Azure OpenAI, Vertex Anthropic/Vertex Google; model settings mention AWSBedrock via custom endpoints. Customer deployment/contract setup details not fully specified. Sources: omnifact:omnifact:providers, omnifact:omnifact:model-settings. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [supported]: Custom provider supports OpenAI-compatible endpoints; self-hosted connection enabled with support. Sources: omnifact:omnifact:providers, omnifact:omnifact:terms. - byo_pricing — Does BYO change the licence price? [partial]: BYOK moves model costs to customer account/negotiated rates; Enterprise licence adjustment is quote-only. Sources: omnifact:omnifact:providers. - byo_restrictions — Which features stop working with BYO? [unknown]: Which features stop working with BYO? Unknown. No complete BYOK-specific feature failure/parity matrix or public licence discount was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:providers, omnifact:omnifact:model-settings, omnifact:omnifact:terms ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Local chat and local CPU embeddings are documented; built-in-engine availability differs by client and release. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - feature_parity: Chat/RAG are local-capable, but tools and vision depend on model support and optional online services. Cloud explicitly has no bundled built-in LLM. No full offline fixture was run. - vendor_hosted_open_models: Does the vendor host open-weight models in EU/CH? No vendor-hosted open-weight model service with verified EU/Swiss inference was established. - self_hosted_chat — Can chat use a customer-hosted model? [supported]: Ollama and other local providers work as configured endpoints. Desktop’s current built-in engine uses Lemonade/llama.cpp; Docker built-in is opt-in on the latest images and releases after v1.18.0 according to current docs. Sources: anythingllm:anythingllm:ollama, anythingllm:anythingllm:built-in. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [supported]: The built-in all-MiniLM-L6-v2 embedder runs locally on CPU; other local embedding routes are configurable. Sources: anythingllm:anythingllm:local-embed, anythingllm:anythingllm:embed. - feature_parity — Which features fail with self-hosted models? [partial]: Chat/RAG are local-capable, but tools and vision depend on model support and optional online services. Cloud explicitly has no bundled built-in LLM. No full offline fixture was run. Sources: anythingllm:anythingllm:models, anythingllm:anythingllm:cloud-limits, anythingllm:anythingllm:built-in. - 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 vendor-hosted open-weight model service with verified EU/Swiss inference was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:ollama, anythingllm:anythingllm:built-in, anythingllm:anythingllm:local-embed, anythingllm:anythingllm:embed, anythingllm:anythingllm:models, anythingllm:anythingllm:cloud-limits #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise can integrate customer-hosted models; embedding and tool parity remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise self-hosted model connection; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - vendor_hosted_open_models: Mistral family appears with EU flags; the operating party and infrastructure for every open-weight route are not fully mapped. It is not proof of Swiss hosting. - Unverified self_hosted_embeddings, feature_parity: No documented customer-hosted embedding route or exhaustive feature-parity matrix was established; on-premise platform availability alone does not prove either. - self_hosted_chat — Can chat use a customer-hosted model? [supported]: Enterprise lists self-hosted LLMs; terms6.4 requires coordination with support and custom provider endpoints are documented. Sources: omnifact:omnifact:pricing, omnifact:omnifact:providers, omnifact:omnifact:terms. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [unknown]: Can retrieval use customer-hosted embeddings? Unknown. No documented customer-hosted embedding route or exhaustive feature-parity matrix was established; on-premise platform availability alone does not prove either. - feature_parity — Which features fail with self-hosted models? [unknown]: Which features fail with self-hosted models? Unknown. No documented customer-hosted embedding route or exhaustive feature-parity matrix was established; on-premise platform availability alone does not prove either. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [partial]: Mistral family appears with EU flags; the operating party and infrastructure for every open-weight route are not fully mapped. It is not proof of Swiss hosting. Sources: omnifact:omnifact:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:providers, omnifact:omnifact:terms, omnifact:omnifact: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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workspace models and admin roles control settings; non-admin multi-user message quotas have a source-inspected blocking path. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - model_allowlist_by_group: Can admins limit models per group? A group-based model allow-list and hard source-data/provider-binding policy were not established in the role and workspace guides. No two-group quota or model restriction fixture was run. - data_bound_models: Can admins restrict which models receive connector or knowledge content? A group-based model allow-list and hard source-data/provider-binding policy were not established in the role and workspace guides. No two-group quota or model restriction fixture was run. - model_allowlist_by_group — Can admins limit models per group? [unknown]: model_allowlist_by_group: Can admins limit models per group? A group-based model allow-list and hard source-data/provider-binding policy were not established in the role and workspace guides. No two-group quota or model restriction fixture was run. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [unknown]: data_bound_models: Can admins restrict which models receive connector or knowledge content? A group-based model allow-list and hard source-data/provider-binding policy were not established in the role and workspace guides. No two-group quota or model restriction fixture was run. - default_model — Can admins set the default model? [supported]: The system LLM is the default, overridden by workspace and Agent model configuration. Sources: anythingllm:anythingllm:llmconfig. - user_limits — What per-user message or token limits apply, and are they published? [supported]: A dailyMessageLimit may be set per user, is system-wide across workspaces, uses a trailing 24-hour count and exempts admins; null means no limit in the inspected function. Sources: anythingllm:anythingllm:user-pin. - limit_behaviour — What happens when a limit is reached? [supported]: Pinned chat endpoints send an abort/quota message and return before generation when the user cannot send another chat. Sources: anythingllm:anythingllm:chat-pin. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:llmconfig, anythingllm:anythingllm:user-pin, anythingllm:anythingllm:chat-pin #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Groups add model-tier/capability permissions while organization settings control concrete models/routes. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - model_allowlist_by_group: Groups add Base/Standard/Premium-tier and US-hosted-model access. Everyone and overlapping groups union grants; no deny overrides. Concrete model enablement is organization-wide, not an arbitrary per-group model list. - data_bound_models: Admins disable providers/models globally; DPA annexes also describe per-Space provider approval. No tested classifier routes knowledge content to distinct allowed models automatically. - default_model: October notes set Haiku5.5 as fast default for new organizations. Image default and Published Space model are configurable; universal organization text-default setting not established. - user_limits: Plan-determined per-user24-hour rolling message quotas show remaining count/reset. Numeric plan quotas are not public; pooled credit and page limits are separate. - model_allowlist_by_group — Can admins limit models per group? [partial]: Groups add Base/Standard/Premium-tier and US-hosted-model access. Everyone and overlapping groups union grants; no deny overrides. Concrete model enablement is organization-wide, not an arbitrary per-group model list. Sources: omnifact:omnifact:groups, omnifact:omnifact:model-settings. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [partial]: Admins disable providers/models globally; DPA annexes also describe per-Space provider approval. No tested classifier routes knowledge content to distinct allowed models automatically. Sources: omnifact:omnifact:model-settings, omnifact:omnifact:dpa. - default_model — Can admins set the default model? [partial]: October notes set Haiku5.5 as fast default for new organizations. Image default and Published Space model are configurable; universal organization text-default setting not established. Sources: omnifact:omnifact:changes, omnifact:omnifact:model-settings, omnifact:omnifact:published. - user_limits — What per-user message or token limits apply, and are they published? [partial]: Plan-determined per-user24-hour rolling message quotas show remaining count/reset. Numeric plan quotas are not public; pooled credit and page limits are separate. Sources: omnifact:omnifact:chat. - limit_behaviour — What happens when a limit is reached? [supported]: Daily message exhaustion disables new sends until reset. Monthly credit exhaustion greys premium models and chat falls back; Gateway returns credit error for all models without fallback. Sources: omnifact:omnifact:chat, omnifact:omnifact:limits, omnifact:omnifact:gateway. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:groups, omnifact:omnifact:model-settings, omnifact:omnifact:dpa, omnifact:omnifact:changes, omnifact:omnifact:published, omnifact:omnifact:chat, omnifact:omnifact:limits, omnifact:omnifact:gateway ## 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Files can enter full context or workspace RAG; converters and a PDF OCR fallback are present, with fidelity untested. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - limits: What size and count limits apply per file and chat? No universal file/count limit was established across these deployments. Cloud documents CPU/memory limits, but they do not define a tested per-file allowance. Shared long/scanned/Excel/PowerPoint fixtures were not uploaded. - ocr: The PDF implementation attempts OCR when initial text extraction returns no pages. No scanned contract or mixed-content PDF was tested. - spreadsheets: XLSX conversion is registered and v1.18.0 reports spreadsheet parsing fixes; preservation of formula semantics and layout was not tested. - formats — Which formats are accepted? [supported]: Pinned converters register PDF, DOCX, PPTX, XLSX, EPUB, text/CSV/JSON, image and audio formats. Legacy DOC is not in the active registered converter map. Sources: anythingllm:anythingllm:constants-pin. - limits — What size and count limits apply per file and chat? [unknown]: limits: What size and count limits apply per file and chat? No universal file/count limit was established across these deployments. Cloud documents CPU/memory limits, but they do not define a tested per-file allowance. Shared long/scanned/Excel/PowerPoint fixtures were not uploaded. - ocr — Are scanned PDFs read? [partial]: The PDF implementation attempts OCR when initial text extraction returns no pages. No scanned contract or mixed-content PDF was tested. Sources: anythingllm:anythingllm:pdf-pin. - spreadsheets — Are Excel tables read with structure intact? [partial]: XLSX conversion is registered and v1.18.0 reports spreadsheet parsing fixes; preservation of formula semantics and layout was not tested. Sources: anythingllm:anythingllm:constants-pin, anythingllm:anythingllm:changelog. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [supported]: Current attachment mode injects full extracted text. On context overflow the UI offers cancellation, pruning or embedding; embedded documents retrieve chunks and become workspace-wide. Sources: anythingllm:anythingllm:docchat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:constants-pin, anythingllm:anythingllm:pdf-pin, anythingllm:anythingllm:changelog, anythingllm:anythingllm:docchat #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Broad attachment formats and published limits exist; indexing uses OCR/chunks while workbook fidelity is untested. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - limits: 10 attachments/message;8000 text characters/message;20MB/image;25MB/audio. Space Uploaded Files FAQ says no individual/aggregate file-size limit; ordinary document/chat count ceilings not fully specified. - ocr: Space upload pipeline documents Apache Tika OCR for scanned PDFs/images; no accuracy fixture. - spreadsheets: Spreadsheet inputs can be processed with executed Python and native XLSX formulas; structure/merged cells/formula preservation not tested. - full_vs_chunked: Space documents are extracted/chunked/embedded and relevant sections retrieved with progress/citation displays. Exact direct-attachment full-text thresholds were not established. - formats — Which formats are accepted? [supported]: PDF, Word, Excel, Power Point, Open Document text/presentation, TXT, JSON, Markdown, CSV, SVG; images PNG/JPEG/Web P/HEIC/HEIF/AVIF/BMP/GIF/ICO/TIFF/SVG; audio examples MP3/WAV/AAC/FLAC with group/model restriction. Sources: omnifact:omnifact:files. - limits — What size and count limits apply per file and chat? [partial]: 10 attachments/message;8000 text characters/message;20MB/image;25MB/audio. Space Uploaded Files FAQ says no individual/aggregate file-size limit; ordinary document/chat count ceilings not fully specified. Sources: omnifact:omnifact:files, omnifact:omnifact:uploads. - ocr — Are scanned PDFs read? [partial]: Space upload pipeline documents Apache Tika OCR for scanned PDFs/images; no accuracy fixture. Sources: omnifact:omnifact:uploads. - spreadsheets — Are Excel tables read with structure intact? [partial]: Spreadsheet inputs can be processed with executed Python and native XLSX formulas; structure/merged cells/formula preservation not tested. Sources: omnifact:omnifact:documents. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [partial]: Space documents are extracted/chunked/embedded and relevant sections retrieved with progress/citation displays. Exact direct-attachment full-text thresholds were not established. Sources: omnifact:omnifact:uploads, omnifact:omnifact:retrieval. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:files, omnifact:omnifact:uploads, omnifact:omnifact:documents, omnifact:omnifact:retrieval ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workspace embeddings persist across chats and are shared with every authorized workspace user. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - size_limits: What are the collection limits? No fixed collection storage allowance was established; capacity depends on local hardware or managed-instance tier. - persistent_collections — Can users keep document collections across chats? [supported]: Embedding a document into a workspace makes it reusable across that workspace’s threads. Sources: anythingllm:anythingllm:docchat. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: In Docker multi-user mode, assigned workspace users can use its embedded documents. Admin/Manager roles have broader access; per-original-source ACLs were not established. Sources: anythingllm:anythingllm:docchat, anythingllm:anythingllm:security. - size_limits — What are the collection limits? [unknown]: size_limits: What are the collection limits? No fixed collection storage allowance was established; capacity depends on local hardware or managed-instance tier. - assistant_binding — Can collections be bound to an assistant? [supported]: Each workspace has configurable chat/Agent models and its embedded knowledge. Sources: anythingllm:anythingllm:llmconfig, anythingllm:anythingllm:docchat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:docchat, anythingllm:anythingllm:security, anythingllm:anythingllm:llmconfig #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Spaces persist and share uploaded/connected knowledge. The applicable Pro page quota remains unknown; Enterprise advertises unlimited pages. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro up to50users and Enterprise Spaces; actual Pro page quota unverified; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Pro page quota is excluded from verified limits until the applicable offer is identified. Connected-source and manual-upload accounting are separate. - persistent_collections — Can users keep document collections across chats? [supported]: Uploaded Files and connected folders persist in a Space for multiple conversations; message attachments remain specific to their conversation. Sources: omnifact:omnifact:spaces. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: Organization users/groups including Everyone; Admin/Editor manage, Member queries. Groups receive view-only membership; edit grants are individual. Sources: omnifact:omnifact:share. - size_limits — What are the collection limits? [partial]: Enterprise pricing advertises unlimited knowledge pages. Actual Pro page quota is unknown because pricing says25000 while Billing says5000; neither is asserted as an independently applicable limit. The Connected Sources documentation says synced files currently do not count against the manual-upload page quota. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing, omnifact:omnifact:sync. - assistant_binding — Can collections be bound to an assistant? [supported]: Space agent uses its own instructions and isolated Uploaded Files/Connected Sources knowledge. Sources: omnifact:omnifact:spaces. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:spaces, omnifact:omnifact:share, omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing, omnifact:omnifact:sync ### 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). #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The source registers import connectors and SQL tools. Mail integrations are single-user features, not verified enterprise multi-user content search. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=Source-specific credentials/registrations, Mail skills require single-user mode; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - microsoft_365: An Outlook skill searches/reads/modifies the connected mailbox, but is explicitly single-user only. SharePoint, OneDrive and Teams connectors were not verified for the multi-user deployment. - google_workspace: The Gmail skill is single-user only. A maintained Google Drive enterprise connector and source ACL sync were not verified. - atlassian: The pinned connector catalog includes Confluence import. Jira was not established and Confluence per-user permission synchronization was not tested. - other_systems: The connector catalog includes GitHub/GitLab/Gitea, websites, YouTube, Obsidian and other import sources; registration does not establish tested source access controls. - on_prem_sources: Self-hosted deployments can upload files and connect the SQL Agent to a reachable database. Automatic local-file watching is Desktop-only, not Docker browser upload. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: An Outlook skill searches/reads/modifies the connected mailbox, but is explicitly single-user only. SharePoint, OneDrive and Teams connectors were not verified for the multi-user deployment. Sources: anythingllm:anythingllm:outlook. - google_workspace — Which Google sources are connected? [partial]: The Gmail skill is single-user only. A maintained Google Drive enterprise connector and source ACL sync were not verified. Sources: anythingllm:anythingllm:gmail. - atlassian — Confluence and Jira? [partial]: The pinned connector catalog includes Confluence import. Jira was not established and Confluence per-user permission synchronization was not tested. Sources: anythingllm:anythingllm:connectors-pin, anythingllm:anythingllm:sync. - other_systems — Which other business systems? [partial]: The connector catalog includes GitHub/GitLab/Gitea, websites, YouTube, Obsidian and other import sources; registration does not establish tested source access controls. Sources: anythingllm:anythingllm:connectors-pin. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Self-hosted deployments can upload files and connect the SQL Agent to a reachable database. Automatic local-file watching is Desktop-only, not Docker browser upload. Sources: anythingllm:anythingllm:sql, anythingllm:anythingllm:sync, anythingllm:anythingllm:localdocker. - connector_provider — Who builds and maintains each connector? [supported]: These are built-in Mintplex project skills/import modules; third-party MCP servers remain separately maintained integrations. Sources: anythingllm:anythingllm:connectors-pin, anythingllm:anythingllm:outlook, anythingllm:anythingllm:gmail, anythingllm:anythingllm:mcp. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:outlook, anythingllm:anythingllm:gmail, anythingllm:anythingllm:connectors-pin, anythingllm:anythingllm:sync, anythingllm:anythingllm:sql, anythingllm:anythingllm:localdocker, anythingllm:anythingllm:mcp #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Cloud document sync and live first-party MCP integrations cover different system/action scopes. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise cloud document connectors; separately run API-enabled XWiki importer documented at pinned revision; add_ons=Customer-run XWiki sync tool; API access and source credentials required; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - XWiki behavior is documented in a pinned README, with no support/guarantee. It was not implementation-inspected or executed in this pass. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: SharePoint, OneDrive Business and personal OneDrive document access/sync. No verified native Outlook/Teams connector in current catalogue. Sources: omnifact:omnifact:integrations. - google_workspace — Which Google sources are connected? [supported]: Drive document sync plus MCP Drive, Docs, Sheets, Slides, Gmail, Calendar, Chat tools. Sources: omnifact:omnifact:integrations. - atlassian — Confluence and Jira? [supported]: Atlassian official MCP for Jira/Confluence search and updates. Sources: omnifact:omnifact:directory. - other_systems — Which other business systems? [partial]: Slack, Zoom, Notion, Hub Spot, Zendesk, Box, Egnyte, Asana, Click Up, Linear, Airtable, Canva, Miro, Lucid, Stripe, Pay Pal, Git Hub/Git Lab, Sentry, PostHog, Supabase, Neon, Webflow, Todoist; official XWiki importer is separate unsupported CLI. Sources: omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Custom MCP can expose internal systems but cloud deployment blocks private IP/loopback/subnets by default. XWiki REST importer runs where customer executes it; native file-share/database network support is not established. Sources: omnifact:omnifact:mcp-rev2, omnifact:omnifact:xwiki-sync-rev2. - connector_provider — Who builds and maintains each connector? [partial]: Catalogue MCP servers are supplied by listed software vendors; Omnifact manages installation/governance. Document connectors and XWiki tool are Omnifact; support scope varies. Sources: omnifact:omnifact:directory, omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:integrations, omnifact:omnifact:directory, omnifact:omnifact:xwiki-sync-rev2, omnifact:omnifact:mcp-rev2 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workspace access is enforced as the product sharing boundary; original source permissions after copying remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - source_permissions_respected: Are source permissions enforced per user? No restricted-document two-user fixture or grant/revocation propagation test was run. Purview label enforcement and source ACL fidelity remain unknown. - enforcement_point: Default users only access assigned workspaces, and an embedded file becomes available to every user assigned to its workspace. Continuing source-system ACL checks were not established. - revocation_delay: How quickly does a removed permission take effect? No restricted-document two-user fixture or grant/revocation propagation test was run. Purview label enforcement and source ACL fidelity remain unknown. - admin_scope_controls: Admins control workspace membership and selected documents. Source site/folder/sensitivity-label exclusion was not established. - sensitivity_labels: Are Microsoft Purview or similar labels respected? No restricted-document two-user fixture or grant/revocation propagation test was run. Purview label enforcement and source ACL fidelity remain unknown. - source_permissions_respected — Are source permissions enforced per user? [unknown]: source_permissions_respected: Are source permissions enforced per user? No restricted-document two-user fixture or grant/revocation propagation test was run. Purview label enforcement and source ACL fidelity remain unknown. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [partial]: Default users only access assigned workspaces, and an embedded file becomes available to every user assigned to its workspace. Continuing source-system ACL checks were not established. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:docchat. - revocation_delay — How quickly does a removed permission take effect? [unknown]: revocation_delay: How quickly does a removed permission take effect? No restricted-document two-user fixture or grant/revocation propagation test was run. Purview label enforcement and source ACL fidelity remain unknown. - admin_scope_controls — Can admins exclude sites, folders or labels? [partial]: Admins control workspace membership and selected documents. Source site/folder/sensitivity-label exclusion was not established. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:docchat. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [unknown]: sensitivity_labels: Are Microsoft Purview or similar labels respected? No restricted-document two-user fixture or grant/revocation propagation test was run. Purview label enforcement and source ACL fidelity remain unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:docchat #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Personal OAuth tools honor source-account rights; synced content is scoped to Space membership, without a verified per-user ACL mirror. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - source_permissions_respected: OAuth MCP executes only within each user account rights. Space indexed knowledge is available under shared Space membership; per-recipient source ACL enforcement was not established. - enforcement_point: Live OAuth uses source account access. Space retrieval is indexed and checks Space membership; this is not documented as a source-ACL recheck on every query. - revocation_delay: Removing Space/group membership immediately revokes those grants; source document/ACL revocation timing beyond deletion sync was not tested. - admin_scope_controls: Space admins select connected folders; organization enables/removes connectors and tools. No sensitivity-label classifier was established. - Unverified sensitivity_labels: No cross-group source-ACL/revocation fixture or Microsoft Purview sensitivity-label implementation was established. - source_permissions_respected — Are source permissions enforced per user? [partial]: OAuth MCP executes only within each user account rights. Space indexed knowledge is available under shared Space membership; per-recipient source ACL enforcement was not established. Sources: omnifact:omnifact:mcp, omnifact:omnifact:retrieval, omnifact:omnifact:sync. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [partial]: Live OAuth uses source account access. Space retrieval is indexed and checks Space membership; this is not documented as a source-ACL recheck on every query. Sources: omnifact:omnifact:mcp, omnifact:omnifact:retrieval, omnifact:omnifact:sync. - revocation_delay — How quickly does a removed permission take effect? [partial]: Removing Space/group membership immediately revokes those grants; source document/ACL revocation timing beyond deletion sync was not tested. Sources: omnifact:omnifact:share, omnifact:omnifact:groups. - admin_scope_controls — Can admins exclude sites, folders or labels? [partial]: Space admins select connected folders; organization enables/removes connectors and tools. No sensitivity-label classifier was established. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? Unknown. No cross-group source-ACL/revocation fixture or Microsoft Purview sensitivity-label implementation was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:mcp, omnifact:omnifact:retrieval, omnifact:omnifact:sync, omnifact:omnifact:share, omnifact:omnifact:groups, omnifact:omnifact:integrations ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Knowledge is a copied index. Automatic source refresh is preview and differs between remote sources and Desktop local files. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=Live document sync preview explicitly enabled for automatic refresh; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - Automatic sync is a preview, not a guaranteed freshness SLA. - No source edit/delete timing fixture was run. - live_or_indexed — Is content searched live or copied into an index? [supported]: Embedded knowledge copies parsed chunks into the selected vector store; attachments instead inject extracted text. Sources: anythingllm:anythingllm:docchat, anythingllm:anythingllm:vector. - sync_interval — How often does an index refresh? [partial]: Preview watched remote sources are checked hourly for staleness, defined as no refresh in seven days; Desktop local watched files are checked every ten minutes while running. No latency fixture was run. Sources: anythingllm:anythingllm:sync. - deletion_propagation — How quickly does a deleted document disappear? [partial]: Deleting a watched local original marks it Not Found and unwatches it while retaining existing content/embeddings. System deletion must be explicit; remote-source deletion timing was not established. Sources: anythingllm:anythingllm:sync, anythingllm:anythingllm:privacy. - index_location — Where is indexed content stored? [supported]: Self-hosting selects the configured local or external vector store and its country. Default local storage is distinct from any selected cloud database. Sources: anythingllm:anythingllm:vector, anythingllm:anythingllm:localdocker. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:docchat, anythingllm:anythingllm:vector, anythingllm:anythingllm:sync, anythingllm:anythingllm:privacy, anythingllm:anythingllm:localdocker #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Connected documents are indexed on a five-minute cycle; live MCP queries remain separate. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise cloud document connectors; separately run API-enabled XWiki importer documented at pinned revision; add_ons=Customer-run XWiki sync tool; API access and source credentials required; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - XWiki behavior is documented in a pinned README, with no support/guarantee. It was not implementation-inspected or executed in this pass. - live_or_indexed — Is content searched live or copied into an index? [supported]: Connected Sources index selected cloud files; MCP tools query source systems live. XWiki CLI uploads converted Markdown on customer-run sync. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2. - sync_interval — How often does an index refresh? [supported]: Connected Sources checks every five minutes; initial indexing may take minutes. XWiki tool is one-shot and requires external cron/systemd/Kubernetes scheduling. Sources: omnifact:omnifact:sync, omnifact:omnifact:xwiki-sync-rev2. - deletion_propagation — How quickly does a deleted document disappear? [supported]: Cloud deletions removed on next five-minute cycle; disconnect permanently removes that source index from Space. XWiki importer tracks deleted/excluded pages on next run. Sources: omnifact:omnifact:sync, omnifact:omnifact:xwiki-sync-rev2. - index_location — Where is indexed content stored? [partial]: DPA maps prefilter files/indexing to Azure Saa S Germany/Frankfurt storage; model embeddings/summaries have provider-dependent paths not fully mapped. Sources: omnifact:omnifact:dpa-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2, omnifact:omnifact:dpa-rev2 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The client renders source citations and Query mode documents a no-relevant-content response; quality is untested. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - citation_accuracy: Do the cited passages support the answer? The shared DE/FR/EN factual/cross-document/no-answer corpus was not run. Citation correctness, link accuracy, cross-language retrieval and numerical observed accuracy remain unknown; the default embedder is primarily English-trained. - cross_language: Does a question in one language find documents in another? The shared DE/FR/EN factual/cross-document/no-answer corpus was not run. Citation correctness, link accuracy, cross-language retrieval and numerical observed accuracy remain unknown; the default embedder is primarily English-trained. - no_answer_behaviour: Query mode documentation says it reports when no relevant information is found. This is documented behavior, not a passed no-answer fixture. - observed_accuracy: How many of the question set were answered correctly? The shared DE/FR/EN factual/cross-document/no-answer corpus was not run. Citation correctness, link accuracy, cross-language retrieval and numerical observed accuracy remain unknown; the default embedder is primarily English-trained. - citations — Are answers linked to specific sources? [supported]: Pinned client code renders document/link citation details and source metadata. Sources: anythingllm:anythingllm:citation-pin. - citation_accuracy — Do the cited passages support the answer? [unknown]: citation_accuracy: Do the cited passages support the answer? The shared DE/FR/EN factual/cross-document/no-answer corpus was not run. Citation correctness, link accuracy, cross-language retrieval and numerical observed accuracy remain unknown; the default embedder is primarily English-trained. - 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 factual/cross-document/no-answer corpus was not run. Citation correctness, link accuracy, cross-language retrieval and numerical observed accuracy remain unknown; the default embedder is primarily English-trained. - no_answer_behaviour — Does it say when the corpus has no answer? [partial]: Query mode documentation says it reports when no relevant information is found. This is documented behavior, not a passed no-answer fixture. Sources: anythingllm:anythingllm:chatmodes. - 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 factual/cross-document/no-answer corpus was not run. Citation correctness, link accuracy, cross-language retrieval and numerical observed accuracy remain unknown; the default embedder is primarily English-trained. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:citation-pin, anythingllm:anythingllm:chatmodes #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Passage citations and controllable strict grounding are documented; retrieval quality remains unmeasured. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - no_answer_behaviour: Space instructions can require answers only from uploaded documents and explicit missing-information statements; default guaranteed abstention is not established. - Unverified citation_accuracy, cross_language, observed_accuracy: No DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run. - citations — Are answers linked to specific sources? [supported]: Source references identify uploaded document or cloud filename/provider and direct original link; progress shows retrieved document count. Sources: omnifact:omnifact:retrieval, omnifact:omnifact:sync. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run. - 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 DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run. - no_answer_behaviour — Does it say when the corpus has no answer? [partial]: Space instructions can require answers only from uploaded documents and explicit missing-information statements; default guaranteed abstention is not established. Sources: omnifact:omnifact:retrieval. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:retrieval, omnifact:omnifact:sync ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: supported Opt-in personalization stores private global/workspace memories with user controls and admin enablement. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. - custom_instructions — Can users set persistent instructions? [supported]: Workspaces keep model/system instructions and may include user/time variables. Sources: anythingllm:anythingllm:systemprompt, anythingllm:anythingllm:llmconfig. - cross_chat_memory — Does the product remember facts across chats? [supported]: User memories apply across chats within a workspace or globally; limits are 20 workspace and five global memories per user. Sources: anythingllm:anythingllm:memory. - user_memory_controls — Can users view, edit and delete memories? [supported]: Users can add, edit, delete and move memories; selected memories are sent to the configured model in the system prompt. Sources: anythingllm:anythingllm:memory. - admin_memory_controls — Can admins turn memory off? [supported]: Memories are off by default; in multi-user mode only admins enable/disable personalization. Sources: anythingllm:anythingllm:memory. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:systemprompt, anythingllm:anythingllm:llmconfig, anythingllm:anythingllm:memory #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Persistent personal instructions exist; automatic cross-chat memory was not established. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - user_memory_controls: Users edit/remove their supplied personalization fields. This is not documentation of viewing/deleting automatically learned memories. - Unverified cross_chat_memory, admin_memory_controls: No automatic fact-memory feature or administrator memory-disable setting was established in account, Space and release documentation. Conversation history is not itself cross-chat memory. - custom_instructions — Can users set persistent instructions? [supported]: Personalization stores role/context and response tone/style/format and sends them in every conversation. These fields bypass the Privacy Filter. Sources: omnifact:omnifact:account. - cross_chat_memory — Does the product remember facts across chats? [unknown]: Does the product remember facts across chats? Unknown. No automatic fact-memory feature or administrator memory-disable setting was established in account, Space and release documentation. Conversation history is not itself cross-chat memory. - user_memory_controls — Can users view, edit and delete memories? [partial]: Users edit/remove their supplied personalization fields. This is not documentation of viewing/deleting automatically learned memories. Sources: omnifact:omnifact:account. - admin_memory_controls — Can admins turn memory off? [unknown]: Can admins turn memory off? Unknown. No automatic fact-memory feature or administrator memory-disable setting was established in account, Space and release documentation. Conversation history is not itself cross-chat memory. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:account ## 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workspaces combine instructions, a model, knowledge and configured Agent skills; a distinct shareable assistant object/catalog was not fully established. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - creator_permissions: Admin/Manager roles manage workspaces; Default users only chat in assigned workspaces. A separate assistant-creator permission matrix was not established. - sharing_scope: Docker workspaces can be assigned to users; Desktop is single-user. Group/everyone assistant-sharing and versioned assistant publishing were not established. - catalogue: Is there an internal assistant directory? A complete internal assistant directory/versioning contract and the HR assistant fixture were not verified. - prompt_library: Workspace prompts and no-code Agent Flows can be reused, but a separate organization prompt-template catalog was not verified. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Workspace and Agent settings combine a model, instructions, embedded knowledge and enabled skills/tools. Sources: anythingllm:anythingllm:llmconfig, anythingllm:anythingllm:agent-setup, anythingllm:anythingllm:docchat. - creator_permissions — Can admins limit who creates them? [partial]: Admin/Manager roles manage workspaces; Default users only chat in assigned workspaces. A separate assistant-creator permission matrix was not established. Sources: anythingllm:anythingllm:security. - sharing_scope — Can assistants be shared with users, groups or everyone? [partial]: Docker workspaces can be assigned to users; Desktop is single-user. Group/everyone assistant-sharing and versioned assistant publishing were not established. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:desktop. - catalogue — Is there an internal assistant directory? [unknown]: catalogue: Is there an internal assistant directory? A complete internal assistant directory/versioning contract and the HR assistant fixture were not verified. - prompt_library — Are shared prompt templates available? [partial]: Workspace prompts and no-code Agent Flows can be reused, but a separate organization prompt-template catalog was not verified. Sources: anythingllm:anythingllm:flow, anythingllm:anythingllm:systemprompt. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:llmconfig, anythingllm:anythingllm:agent-setup, anythingllm:anythingllm:docchat, anythingllm:anythingllm:security, anythingllm:anythingllm:desktop, anythingllm:anythingllm:flow, anythingllm:anythingllm:systemprompt #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Space agents combine custom instructions, knowledge and shared access with starter prompts. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - creator_permissions: Member role includes Space creation; group permissions control file/code/features. An explicit deny-Space-creation privilege was not established. - prompt_library: Space Starters/template previews and example prompts provide shared starting points; a separate centrally managed standalone prompt-library product was not established. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Members create Spaces, become Space Admin and set instructions/examples/knowledge. Workspace-level tool availability is governed separately. Sources: omnifact:omnifact:create, omnifact:omnifact:users. - creator_permissions — Can admins limit who creates them? [partial]: Member role includes Space creation; group permissions control file/code/features. An explicit deny-Space-creation privilege was not established. Sources: omnifact:omnifact:users, omnifact:omnifact:groups. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Users or organization groups including Everyone; group membership grants Member only. Sources: omnifact:omnifact:share. - catalogue — Is there an internal assistant directory? [supported]: All/Favorite Spaces directory shows accessible agents with pin/favorite navigation. Sources: omnifact:omnifact:spaces. - prompt_library — Are shared prompt templates available? [partial]: Space Starters/template previews and example prompts provide shared starting points; a separate centrally managed standalone prompt-library product was not established. Sources: omnifact:omnifact:create, omnifact:omnifact:changes. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:create, omnifact:omnifact:users, omnifact:omnifact:groups, omnifact:omnifact:share, omnifact:omnifact:spaces, omnifact:omnifact:changes ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Self-hosted/desktop supports built-in skills, API-call flows and MCP. Managed Cloud explicitly excludes custom coded Agents and MCP. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=Separate MCP servers or custom skill configuration, Mail integrations require single-user mode; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - Cloud does not support MCP or custom coded Agents. - Single-user mail approvals do not establish a complete multi-user side-effect policy. - builtin_tools — Which tools are built in? [supported]: Skills include RAG/document search, web browsing, chart/document generation and SQL; single-user mail skills have a narrower scope. Sources: anythingllm:anythingllm:agent-setup, anythingllm:anythingllm:sql, anythingllm:anythingllm:docgen, anythingllm:anythingllm:chart, anythingllm:anythingllm:outlook. - custom_actions — Can admins add API actions? [supported]: No-code flows provide an API-call block and custom skills can be developed for self-hosted/desktop; Cloud excludes custom coded Agents. Sources: anythingllm:anythingllm:flow-api, anythingllm:anythingllm:cloud-limits. - mcp_client — Can it use remote MCP servers, and with what admin control? [partial]: Self-hosted/desktop supports stdio, SSE and Streamable remote MCP with management controls. Managed Cloud explicitly does not support MCP. Sources: anythingllm:anythingllm:mcp, anythingllm:anythingllm:cloud-limits. - tool_auth — Do tools act as the user or as a shared account? [partial]: MCP accepts environment variables/HTTP headers; single-user Outlook uses delegated Entra authorization. A general per-user OAuth model for every multi-user tool was not established. Sources: anythingllm:anythingllm:mcp, anythingllm:anythingllm:outlook. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Outlook/Gmail modifying actions explicitly require approval in single-user mode. A mandatory approval policy for every custom/MCP action was not verified. Sources: anythingllm:anythingllm:outlook, anythingllm:anythingllm:gmail, anythingllm:anythingllm:mcp. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:agent-setup, anythingllm:anythingllm:sql, anythingllm:anythingllm:docgen, anythingllm:anythingllm:chart, anythingllm:anythingllm:outlook, anythingllm:anythingllm:flow-api, anythingllm:anythingllm:cloud-limits, anythingllm:anythingllm:mcp, anythingllm:anythingllm:gmail #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Remote MCP has explicit tool policies, personal OAuth and teamwide static-credential access. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise managed remote MCP; workspace-admin setup and chosen tool policy required; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Configured policies are documented; initial-discovery defaults remain unknown. Static credentials are shared teamwide as documented and do not provide personal source authorization. - Experimental code/output entitlement is unknown; generic Enterprise early-access wording does not identify an eligible Execute code tier. - builtin_tools — Which tools are built in? [partial]: Web search/browse, Space retrieval, image tools and curated MCP business actions are documented for the scoped workspace. Eligibility for the separate Experimental Execute code and its Python/Office outputs is unknown because the documentation does not map it to Pro or Enterprise. Sources: omnifact:omnifact:web, omnifact:omnifact:retrieval, omnifact:omnifact:images, omnifact:omnifact:documents, omnifact:omnifact:integrations, omnifact:omnifact:groups-rev2. - custom_actions — Can admins add API actions? [partial]: Admins add custom remote MCP URL and discovered tools. Arbitrary non-MCP REST wrappers require an external server. Sources: omnifact:omnifact:mcp-rev2. - mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: Remote HTTP MCP supports OAuth, APIkey, Bearer, customheader ornone. Destination validation blocks private/subnet/metadata endpoints by default. Sources: omnifact:omnifact:mcp-rev2. - tool_auth — Do tools act as the user or as a shared account? [partial]: OAuth requires personal sign-in; static APIkey/Bearer/header/none is central and immediately available teamwide, with no current per-user/group permission for those types. Sources: omnifact:omnifact:mcp-rev2. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins explicitly configure each tool as Always, Approval or Disable. Approval displays the exact request payload with Allow/Deny; later refresh adds new tools disabled. Initial-discovery default is unknown because setup and security sections disagree, so no safe or permissive initial default is asserted. Sources: omnifact:omnifact:mcp-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:web, omnifact:omnifact:retrieval, omnifact:omnifact:images, omnifact:omnifact:documents, omnifact:omnifact:integrations, omnifact:omnifact:mcp-rev2, omnifact:omnifact:groups-rev2 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The web-browsing skill supports explicit search-provider configuration. This claim covers the pinned self-hosted DuckDuckGo route; it makes no assertion about an unconfigured default. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Self-hosted v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba, explicitly configured agent_search_provider=duckduckgo-engine; plan=MIT self-hosted deployment with an explicitly selected DuckDuckGo provider; auto-selected defaults, Desktop and managed Cloud defaults are outside this claim; add_ons=Enabled web-browsing skill; explicit agent_search_provider=duckduckgo-engine setting; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - The scope is an explicitly configured provider at one release pin, not an assertion about default routing in other installations. - Search queries leave the application for the selected external endpoint; processing region and a per-group enforcement fixture were not established. - Dedicated research-report quality and citation completeness remain untested. - web_search — Is web search available? [supported]: The Agent web-browsing skill can search the web; this scoped self-hosted configuration explicitly selects the DuckDuckGo engine. Sources: anythingllm:anythingllm:browsing, anythingllm:anythingllm:search-configured-r2. - admin_toggle — Can admins disable it per organisation or group? [partial]: The documented Agent Skills settings and chat prompt controls toggle skills. Separate per-group web-search enforcement under the standard role model was not established. Sources: anythingllm:anythingllm:agent-skills-r2, anythingllm:anythingllm:security. - search_provider — Which search provider handles queries, and where? [partial]: At the pinned v1.18.0 revision, explicit agent_search_provider=duckduckgo-engine invokes _duckDuckGoEngine and sends the query to html.duckduckgo.com/html. Query processing country and a CH/EU residency commitment were not verified. Unconfigured defaults are outside this finding. Sources: anythingllm:anythingllm:search-configured-r2. - deep_research — Is multi-step research with a report available? [partial]: Agent tools/flows can chain research steps; a dedicated tested report workflow and accuracy result were not established. Sources: anythingllm:anythingllm:flow, anythingllm:anythingllm:agent-usage. - web_citations — Are web sources cited? [partial]: The client renders source citations including links; correctness and completeness of web-source citations were not tested. Sources: anythingllm:anythingllm:citation-pin. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:browsing, anythingllm:anythingllm:search-configured-r2, anythingllm:anythingllm:agent-skills-r2, anythingllm:anythingllm:security, anythingllm:anythingllm:flow, anythingllm:anythingllm:agent-usage, anythingllm:anythingllm:citation-pin #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web research is cited and group-controlled; Brave handles public search. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - search_provider: DPA names Brave Software US as web-search processor; exact request-processing datacentre is not specified. Masked-sensitive queries are blocked before search. - deep_research: Agents can perform multi-step browsing/research; no separately bounded Deep Research report product or benchmark was established. - web_search — Is web search available? [supported]: Automatically triggered when needed or explicitly requested; URL reader caps2MB and excludes login/paywall/captcha pages. Sources: omnifact:omnifact:web. - admin_toggle — Can admins disable it per organisation or group? [supported]: Groups grant web search/browsing additively; remove grant from Everyone/allgroups to disable for targeted users. Sources: omnifact:omnifact:groups. - search_provider — Which search provider handles queries, and where? [partial]: DPA names Brave Software US as web-search processor; exact request-processing datacentre is not specified. Masked-sensitive queries are blocked before search. Sources: omnifact:omnifact:dpa, omnifact:omnifact:web. - deep_research — Is multi-step research with a report available? [partial]: Agents can perform multi-step browsing/research; no separately bounded Deep Research report product or benchmark was established. Sources: omnifact:omnifact:changes, omnifact:omnifact:web. - web_citations — Are web sources cited? [supported]: Numbered citations and original source links accompany search/browse results. Sources: omnifact:omnifact:web. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:web, omnifact:omnifact:groups, omnifact:omnifact:dpa, omnifact:omnifact:changes ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial No-code Agent Flows are available on Docker/Desktop. Scheduled Jobs are explicitly single-user only. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=Scheduled Jobs require single-user mode; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - scheduled_tasks: Scheduled Jobs run recurring Agent prompts with cron, tool allow-lists and saved traces in single-user mode. They are unavailable in self-hosted multi-user mode. - event_triggers: Can external events start a workflow? A maintained incoming email/form/business-system event-trigger contract was not established; an API call alone is not a named trigger integration. - workflow_builder — Is there a workflow or chain builder? [supported]: The visual flow editor builds reusable agentic skills with steps such as API calls, scraping and file operations. Sources: anythingllm:anythingllm:flow. - scheduled_tasks — Can prompts or assistants run on a schedule? [partial]: Scheduled Jobs run recurring Agent prompts with cron, tool allow-lists and saved traces in single-user mode. They are unavailable in self-hosted multi-user mode. Sources: anythingllm:anythingllm:job. - event_triggers — Can external events start a workflow? [unknown]: event_triggers: Can external events start a workflow? A maintained incoming email/form/business-system event-trigger contract was not established; an API call alone is not a named trigger integration. - builder_audience — Is building aimed at business users, IT or developers? [supported]: Flows target non-coders; custom skill code targets technical users and developers. Sources: anythingllm:anythingllm:flow. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:flow, anythingllm:anythingllm:job #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial External n8n nodes support automation; a native scheduled workflow builder is not established. Availability: generally-available Delivery: official-integration Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise Published Spaces/Documents API when enabled; AI Gateway nodes require Enterprise; external n8n runs separately; add_ons=External n8n community-node installation; customer-run scheduler/XWiki importer; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - These integrations are pinned README documentation, not executed or source-inspected implementation. A native Omnifact workflow builder/scheduler is not established. - workflow_builder — Is there a workflow or chain builder? [partial]: Vendor-owned repository publishes n8n community nodes for Gateway completions/model list, Published Space chat and document CRUD. The visual builder is external n8n, not an established native Omnifact builder. Sources: omnifact:omnifact:n8n-nodes-omnifact-rev2. - scheduled_tasks — Can prompts or assistants run on a schedule? [partial]: XWiki importer explicitly uses external cron/systemd/Kubernetes Cron Job. Native scheduled prompts/agents were not established. Sources: omnifact:omnifact:xwiki-sync-rev2. - event_triggers — Can external events start a workflow? [unknown]: Can external events start a workflow? Unknown. Native schedule/webhook/event-trigger support was not established from docs, index, changelog and automation integrations. - builder_audience — Is building aimed at business users, IT or developers? [partial]: n8n community-node/API integrations and CLI sync target technical integrators; Space instructions target business users. Sources: omnifact:omnifact:n8n-nodes-omnifact-rev2, omnifact:omnifact:create. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:n8n-nodes-omnifact-rev2, omnifact:omnifact:xwiki-sync-rev2, omnifact:omnifact:create ### 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. #### AnythingLLM Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agentic chat plans tools and streams progress with configurable approvals and Stop. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - visible_steps: Tool/search/retrieval progress and expandable reasoning show activity; exact full execution trace was not independently inspected. - side_effect_confirmation: Curated actions wait for confirmation by default; admins choose Always/Approval/Disable. It is not unconditional confirmation for every write under all configurations. - stop_control: Send becomes Stop while response generates; clicking halts generation. Cancellation of already committed external side effects is not established. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: August release rebuilt chat around multi-step agents with automatic tool selection; API optionally enables agentic workflow. Sources: omnifact:omnifact:changes, omnifact:omnifact:api-chat. - visible_steps — Are steps and tool calls shown? [partial]: Tool/search/retrieval progress and expandable reasoning show activity; exact full execution trace was not independently inspected. Sources: omnifact:omnifact:select, omnifact:omnifact:retrieval, omnifact:omnifact:web. - side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Curated actions wait for confirmation by default; admins choose Always/Approval/Disable. It is not unconditional confirmation for every write under all configurations. Sources: omnifact:omnifact:directory, omnifact:omnifact:mcp. - stop_control — Can the user stop a running task? [partial]: Send becomes Stop while response generates; clicking halts generation. Cancellation of already committed external side effects is not established. Sources: omnifact:omnifact:stop. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:changes, omnifact:omnifact:api-chat, omnifact:omnifact:select, omnifact:omnifact:retrieval, omnifact:omnifact:web, omnifact:omnifact:directory, omnifact:omnifact:mcp, omnifact:omnifact:stop ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Instance APIs manage workspaces, upload/embed content and run chats using provisioned API keys. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - api_governance: API keys are provisioned by authorized accounts and confer access to their holder. Full UI/API quota, model, audit and per-user boundary parity was not tested. - mcp_server: Does the product expose itself to other agents over MCP? A native product-wide MCP server was not established from the client-MCP and API guides. - chat_api — Is there an API for chat and assistants? [supported]: The documented developer API supports workspace management and chat, with instance OpenAPI docs at /api/docs. Sources: anythingllm:anythingllm:api. - knowledge_api — Can documents be loaded through an API? [supported]: The developer API documents embedding/document management alongside workspace operations. Sources: anythingllm:anythingllm:api. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: API keys are provisioned by authorized accounts and confer access to their holder. Full UI/API quota, model, audit and per-user boundary parity was not tested. Sources: anythingllm:anythingllm:api, anythingllm:anythingllm:config. - 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? A native product-wide MCP server was not established from the client-MCP and API guides. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:api, anythingllm:anythingllm:config #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Spaces/document API and Enterprise Gateway use organization keys with different filtering/credit behavior. Availability: generally-available Delivery: native Scope: surfaces=Omnifact Published Spaces, Public API and Enterprise AI Gateway; version=Public documentation checked 2026-10-21; plan=Pro published Spaces advertised but support enablement needed; Gateway Enterprise opt-in; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - chat_api: Published Spaces chat JSON/SSE with source/agentic headers; Enterprise Gateway OpenAI-compatible completions. Gateway V1 explicitly lacks tool calls and structured outputs. - knowledge_api: Document upload, list, inspect, rename/delete with Space scope and async ingestion; no agent-configuration CRUD endpoint established. - api_governance: Org-level revocable key, enabled-modelcontrols and shared credit budget apply. Gateway hard-stops on exhaustion; Published Space API disables Privacy Filter. Fine-grained API-key scopes/end-user identities/audit parity were not established. - Unverified mcp_server: No first-party Omnifact MCP server exposing platform agents was established; inbound MCP client integrations are distinct. - chat_api — Is there an API for chat and assistants? [partial]: Published Spaces chat JSON/SSE with source/agentic headers; Enterprise Gateway OpenAI-compatible completions. Gateway V1 explicitly lacks tool calls and structured outputs. Sources: omnifact:omnifact:api-chat, omnifact:omnifact:gateway. - knowledge_api — Can documents be loaded through an API? [partial]: Document upload, list, inspect, rename/delete with Space scope and async ingestion; no agent-configuration CRUD endpoint established. Sources: omnifact:omnifact:api-docs. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: Org-level revocable key, enabled-modelcontrols and shared credit budget apply. Gateway hard-stops on exhaustion; Published Space API disables Privacy Filter. Fine-grained API-key scopes/end-user identities/audit parity were not established. Sources: omnifact:omnifact:developer, omnifact:omnifact:gateway, omnifact:omnifact:published, omnifact:omnifact:model-settings. - mcp_server — Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? Unknown. No first-party Omnifact MCP server exposing platform agents was established; inbound MCP client integrations are distinct. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:api-chat, omnifact:omnifact:gateway, omnifact:omnifact:api-docs, omnifact:omnifact:developer, omnifact:omnifact:published, omnifact:omnifact:model-settings ## 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Docker serves a browser client, Desktop has native installers and Mobile is Android-only; these are different access/governance modes. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Mobile for Android, AnythingLLM browser content collection extension; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=Windows, macOS, Linux, Android. Limitations: - mobile_apps: A separate free Android app can run local models or pair with Desktop/Cloud/self-hosted servers. iOS and a tested native company-SSO flow were not established. - managed_deployment: Windows silent installer switches are documented for scripted/MDM packaging. Current User install is required; all-users install is unsupported and Enterprise/Server OS use has caveats. No Intune deployment was tested. - web — Is a full web client available? [supported]: Docker provides the browser-accessible multi-user UI; Desktop network discovery exposes API endpoints rather than a web UI. Sources: anythingllm:anythingllm:desktop, anythingllm:anythingllm:docker. - desktop_apps — Windows and macOS apps? [supported]: Desktop installers support Windows, macOS and Linux; the app is single-user rather than a shared company-login client. Sources: anythingllm:anythingllm:desktop. - mobile_apps — iOS and Android apps with SSO? [partial]: A separate free Android app can run local models or pair with Desktop/Cloud/self-hosted servers. iOS and a tested native company-SSO flow were not established. Sources: anythingllm:anythingllm:mobile. - browser_extension — Is there a browser extension or sidebar? [supported]: A content collection extension supports Chrome/Edge/Brave/Firefox and connects with an instance API key. Sources: anythingllm:anythingllm:ext. - managed_deployment — Can IT deploy and configure clients through MDM? [partial]: Windows silent installer switches are documented for scripted/MDM packaging. Current User install is required; all-users install is unsupported and Enterprise/Server OS use has caveats. No Intune deployment was tested. Sources: anythingllm:anythingllm:windows. - client_feature_gaps — Which features are missing on mobile? [supported]: Desktop lacks multi-user/workspace administration; Android is a separate local/pairing client; Desktop-only meeting features currently target Windows/macOS. Sources: anythingllm:anythingllm:desktop, anythingllm:anythingllm:mobile, anythingllm:anythingllm:meeting-intro. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:desktop, anythingllm:anythingllm:docker, anythingllm:anythingllm:mobile, anythingllm:anythingllm:ext, anythingllm:anythingllm:windows, anythingllm:anythingllm:meeting-intro #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Browser and mobile web access are advertised; native and managed clients remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - mobile_apps: Pricing lists Mobile Web App and model picker adapts to small screens; no native i OS/Android app with SSO was established. - client_feature_gaps: Mobile effort picker is inline rather than flyout; broader mobile feature parity is not specified. - Unverified desktop_apps, browser_extension, managed_deployment: No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment. - web — Is a full web client available? [supported]: Full Saa S browser client provides chat and Spaces. Sources: omnifact:omnifact:home. - desktop_apps — Windows and macOS apps? [unknown]: Windows and mac OS apps? Unknown. No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment. - mobile_apps — iOS and Android apps with SSO? [partial]: Pricing lists Mobile Web App and model picker adapts to small screens; no native i OS/Android app with SSO was established. Sources: omnifact:omnifact:pricing, omnifact:omnifact:select. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? Unknown. No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment. - client_feature_gaps — Which features are missing on mobile? [partial]: Mobile effort picker is inline rather than flyout; broader mobile feature parity is not specified. Sources: omnifact:omnifact:select. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:home, omnifact:omnifact:pricing, omnifact:omnifact:select ### 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. #### AnythingLLM Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Office files and live Google connectors exist; embedded office/Teams apps are unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - word_excel_powerpoint: Generates DOCX/XLSX/PPTX and modifies uploaded files, but this does not establish in-Word/Excel/Power Point add-ins. - google_workspace_apps: Google Docs/Sheets/Slides/Gmail/Calendar/Chat MCP actions run from Omnifact after personal OAuth; embedded add-ons were not established. - licence_prerequisites: Microsoft document access may require tenantwide admin consent; all OAuth integrations need individual authorized source accounts and third-party entitlements. Exact office-suite licence matrix not established. - Unverified outlook, teams: No current native Outlook add-in or Teams chat app/bot was established in documentation/catalogue. - word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [partial]: Generates DOCX/XLSX/PPTX and modifies uploaded files, but this does not establish in-Word/Excel/Power Point add-ins. Sources: omnifact:omnifact:documents. - outlook — Does it work inside Outlook? [unknown]: Does it work inside Outlook? Unknown. No current native Outlook add-in or Teams chat app/bot was established in documentation/catalogue. - teams — Is there a Teams app or bot? [unknown]: Is there a Teams app or bot? Unknown. No current native Outlook add-in or Teams chat app/bot was established in documentation/catalogue. - google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [partial]: Google Docs/Sheets/Slides/Gmail/Calendar/Chat MCP actions run from Omnifact after personal OAuth; embedded add-ons were not established. Sources: omnifact:omnifact:integrations. - licence_prerequisites — Which licences or consents are needed? [partial]: Microsoft document access may require tenantwide admin consent; all OAuth integrations need individual authorized source accounts and third-party entitlements. Exact office-suite licence matrix not established. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:documents, omnifact:omnifact:integrations, omnifact:omnifact:sync ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Optional Desktop Magic tools support system-wide rewriting, but layout-preserving translation and company glossary controls remain unverified. Availability: generally-available Delivery: native Scope: surfaces=AnythingLLM Desktop; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=Desktop free Magic allowances; optional Desktop Pro; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=Windows, macOS. Limitations: - document_translation: Can whole documents be translated with formatting kept? No whole-contract DE-to-FR/IT formatting test, company glossary, formality/de-CH control or dedicated layout-preserving translation service was verified. - translation_engine: Generative rewrite work uses the selected model. A dedicated document translation engine/workflow was not established. - glossaries: Are company glossaries supported? No whole-contract DE-to-FR/IT formatting test, company glossary, formality/de-CH control or dedicated layout-preserving translation service was verified. - formality_and_variants: Can formality and regional variants (de-CH) be set? No whole-contract DE-to-FR/IT formatting test, company glossary, formality/de-CH control or dedicated layout-preserving translation service was verified. - document_translation — Can whole documents be translated with formatting kept? [unknown]: document_translation: Can whole documents be translated with formatting kept? No whole-contract DE-to-FR/IT formatting test, company glossary, formality/de-CH control or dedicated layout-preserving translation service was verified. - translation_engine — Which engine translates? [partial]: Generative rewrite work uses the selected model. A dedicated document translation engine/workflow was not established. Sources: anythingllm:anythingllm:pro, anythingllm:anythingllm:llmconfig. - glossaries — Are company glossaries supported? [unknown]: glossaries: Are company glossaries supported? No whole-contract DE-to-FR/IT formatting test, company glossary, formality/de-CH control or dedicated layout-preserving translation service was verified. - 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 whole-contract DE-to-FR/IT formatting test, company glossary, formality/de-CH control or dedicated layout-preserving translation service was verified. - writing_tools — Are dedicated rewrite and proofreading tools available? [supported]: Desktop Magic Echo/Beacon/Tab offer dictation cleanup, selected-text revision and writing completion, with free allowances and optional Desktop Pro. Sources: anythingllm:anythingllm:pro. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:pro, anythingllm:anythingllm:llmconfig #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Persistent style instructions support writing; specialized document translation is unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - formality_and_variants: Personal response instructions can request formal/casual tone and style. Specific de-CH controls or terminology enforcement were not documented. - writing_tools: Chat supports drafting and rewriting via instructions and document generation; a dedicated proofreading/translation toolbar was not established. - Unverified document_translation, translation_engine, glossaries: Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations. - document_translation — Can whole documents be translated with formatting kept? [unknown]: Can whole documents be translated with formatting kept? Unknown. Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations. - translation_engine — Which engine translates? [unknown]: Which engine translates? Unknown. Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations. - glossaries — Are company glossaries supported? [unknown]: Are company glossaries supported? Unknown. Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations. - formality_and_variants — Can formality and regional variants (de-CH) be set? [partial]: Personal response instructions can request formal/casual tone and style. Specific de-CH controls or terminology enforcement were not documented. Sources: omnifact:omnifact:account. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Chat supports drafting and rewriting via instructions and document generation; a dedicated proofreading/translation toolbar was not established. Sources: omnifact:omnifact:account, omnifact:omnifact:documents. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:account, omnifact:omnifact:documents ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Configured image providers generate pictures and can edit references where supported. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - image_editing: OpenAI/OpenRouter and compatible Lemonade models use reference-image editing. The documented Ollama route drops image references and generates from text only. - admin_control: Admins configure provider credentials and model. A separate per-group image-generation cost/permission policy was not established. - usage_terms: What usage rights apply to output? Output rights and complete per-image cost visibility depend on the model/provider contract and were not established here. - image_generation — Can users generate images, with which models? [supported]: The /img command uses configured OpenAI, OpenRouter, Ollama or Lemonade providers and an operator-selected model. Sources: anythingllm:anythingllm:images. - image_editing — Can users edit uploaded images? [partial]: OpenAI/OpenRouter and compatible Lemonade models use reference-image editing. The documented Ollama route drops image references and generates from text only. Sources: anythingllm:anythingllm:images. - admin_control — Can admins restrict image generation? [partial]: Admins configure provider credentials and model. A separate per-group image-generation cost/permission policy was not established. Sources: anythingllm:anythingllm:images, anythingllm:anythingllm:security. - usage_terms — What usage rights apply to output? [unknown]: usage_terms: What usage rights apply to output? Output rights and complete per-image cost visibility depend on the model/provider contract and were not established here. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:images, anythingllm:anythingllm:security #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Image generation and edits use configured OpenAI/Google models under group permission. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - image_generation: Model Settings lists GPTImage2/1.5/1/1Mini, Nano Banana/Pro/2; September notes add GPTImage2.5Flare/Sunburst and October Nano Banana2.1 direct Google. EU generation remains Nano Banana2 because2.1 is not on Google Cloud EU. - admin_control: Generate Images is group-granted; model enablement/default is organization-wide. Image/audio contents bypass PII masking and retain route constraints. - Unverified usage_terms: Model-specific output licence/commercial rights were not established; general software rights do not define image-output ownership. - image_generation — Can users generate images, with which models? [partial]: Model Settings lists GPTImage2/1.5/1/1Mini, Nano Banana/Pro/2; September notes add GPTImage2.5Flare/Sunburst and October Nano Banana2.1 direct Google. EU generation remains Nano Banana2 because2.1 is not on Google Cloud EU. Sources: omnifact:omnifact:model-settings, omnifact:omnifact:changes. - image_editing — Can users edit uploaded images? [supported]: Uploaded reference images can be transformed with text instructions; results appear in gallery and download. Sources: omnifact:omnifact:images. - admin_control — Can admins restrict image generation? [partial]: Generate Images is group-granted; model enablement/default is organization-wide. Image/audio contents bypass PII masking and retain route constraints. Sources: omnifact:omnifact:groups, omnifact:omnifact:model-settings, omnifact:omnifact:privacy. - usage_terms — What usage rights apply to output? [unknown]: What usage rights apply to output? Unknown. Model-specific output licence/commercial rights were not established; general software rights do not define image-output ownership. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:model-settings, omnifact:omnifact:changes, omnifact:omnifact:images, omnifact:omnifact:groups, omnifact:omnifact:privacy ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Audio transcription/read-aloud are configurable. Free meeting capture and local transcription are Desktop-only on Windows/macOS. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=Desktop-only Meeting Assistant; downloaded transcription models, Optional provider-specific audio services; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - dictation: Transcription providers and Desktop Magic Echo support spoken input; exact supported dialects and a shared dictation fixture were not verified. - voice_conversation: Is a live voice mode available? No continuous live conversational voice mode or Swiss German recognition quality was verified. - swiss_german_speech: Is Swiss German speech recognised? No continuous live conversational voice mode or Swiss German recognition quality was verified. - dictation — Can users dictate prompts? [partial]: Transcription providers and Desktop Magic Echo support spoken input; exact supported dialects and a shared dictation fixture were not verified. Sources: anythingllm:anythingllm:stt, anythingllm:anythingllm:pro. - read_aloud — Can answers be read aloud? [supported]: System-native, local/browser Piper, self-hosted Kokoro and cloud TTS routes are documented; the chosen engine determines processing. Sources: anythingllm:anythingllm:tts. - voice_conversation — Is a live voice mode available? [unknown]: voice_conversation: Is a live voice mode available? No continuous live conversational voice mode or Swiss German recognition quality was verified. - meeting_summaries — Are meetings transcribed and summarised? [supported]: Desktop Meeting Assistant records/imports meetings, transcribes locally and summarizes with the chosen local/cloud model. A cloud summary sends the transcript to that provider; Linux is not currently supported. Sources: anythingllm:anythingllm:meeting-intro, anythingllm:anythingllm:meeting. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: swiss_german_speech: Is Swiss German speech recognised? No continuous live conversational voice mode or Swiss German recognition quality was verified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:stt, anythingllm:anythingllm:pro, anythingllm:anythingllm:tts, anythingllm:anythingllm:meeting-intro, anythingllm:anythingllm:meeting #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Experimental dictation/audio input exists; meeting bot/live voice coverage is unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - dictation: Experimental Dictate Messages requires enabled Azure OpenAI; audio bypasses filtering and speech is converted to text. - meeting_summaries: Uploaded meeting transcripts can be summarized and Zoom integration searches/recaps recordings; no native automatic meeting-joining/transcription bot was established. - Unverified read_aloud, voice_conversation, swiss_german_speech: No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established. - dictation — Can users dictate prompts? [partial]: Experimental Dictate Messages requires enabled Azure OpenAI; audio bypasses filtering and speech is converted to text. Sources: omnifact:omnifact:groups. - read_aloud — Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established. - meeting_summaries — Are meetings transcribed and summarised? [partial]: Uploaded meeting transcripts can be summarized and Zoom integration searches/recaps recordings; no native automatic meeting-joining/transcription bot was established. Sources: omnifact:omnifact:directory, omnifact:omnifact:documents. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:groups, omnifact:omnifact:directory, omnifact:omnifact:documents ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Built-in Agent skills generate charts and downloadable Office/PDF documents; executed spreadsheet analysis and iterative canvas editing were not tested. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - data_analysis: Can it analyse spreadsheets with executed code? No shared spreadsheet execution/formula analysis, editable PowerPoint fidelity or document-canvas fixture was run. Built-in chart creation does not establish a general code interpreter. - canvas_editing: Is there a document or canvas editor for iterating on output? No shared spreadsheet execution/formula analysis, editable PowerPoint fidelity or document-canvas fixture was run. Built-in chart creation does not establish a general code interpreter. - data_analysis — Can it analyse spreadsheets with executed code? [unknown]: data_analysis: Can it analyse spreadsheets with executed code? No shared spreadsheet execution/formula analysis, editable PowerPoint fidelity or document-canvas fixture was run. Built-in chart creation does not establish a general code interpreter. - charts — Can it produce charts? [supported]: An enabled chart skill creates charts from prompts or workspace data. Sources: anythingllm:anythingllm:chart. - office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: The built-in Document Generation skill lists text, PDF, Excel, DOCX and PowerPoint outputs; the guide recommends capable models for PowerPoint. Sources: anythingllm:anythingllm:docgen. - canvas_editing — Is there a document or canvas editor for iterating on output? [unknown]: canvas_editing: Is there a document or canvas editor for iterating on output? No shared spreadsheet execution/formula analysis, editable PowerPoint fidelity or document-canvas fixture was run. Built-in chart creation does not establish a general code interpreter. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:chart, anythingllm:anythingllm:docgen #### Omnifact Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Docker workspaces share knowledge with assigned users; shared live conversation behavior remains unverified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - share_chats: Can chats be shared inside the organisation? Authenticated chat-share links, simultaneous multi-person AI conversation and recipient transcript/source visibility were not established by the workspace and chat-log guides. - group_chat: Can several people chat together with the AI? Authenticated chat-share links, simultaneous multi-person AI conversation and recipient transcript/source visibility were not established by the workspace and chat-log guides. - share_permission_boundary: Embedded files become accessible to every assigned workspace user; this does not preserve an arbitrary original source ACL. A cross-group chat-sharing fixture was not run. - share_chats — Can chats be shared inside the organisation? [unknown]: share_chats: Can chats be shared inside the organisation? Authenticated chat-share links, simultaneous multi-person AI conversation and recipient transcript/source visibility were not established by the workspace and chat-log guides. - team_spaces — Are shared projects or workspaces available? [supported]: Multi-user workspaces can be assigned to users, who share the embedded knowledge available there. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:docchat. - group_chat — Can several people chat together with the AI? [unknown]: group_chat: Can several people chat together with the AI? Authenticated chat-share links, simultaneous multi-person AI conversation and recipient transcript/source visibility were not established by the workspace and chat-log guides. - share_permission_boundary — Does sharing respect the recipient's access to sources? [partial]: Embedded files become accessible to every assigned workspace user; this does not preserve an arbitrary original source ACL. A cross-group chat-sharing fixture was not run. Sources: anythingllm:anythingllm:docchat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:docchat #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared Spaces organize agents/knowledge; multi-user conversations and complete source-safe redistribution are unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - share_permission_boundary: Space members can see referenced uploaded knowledge. Personal OAuth MCP follows each source account, but Space source-ACL rechecking and generated-answer resharing boundaries were not tested. - Unverified share_chats, group_chat: Sharing individual chat links and simultaneous group conversation were not explicitly established; shared Space access alone is insufficient evidence. - share_chats — Can chats be shared inside the organisation? [unknown]: Can chats be shared inside the organisation? Unknown. Sharing individual chat links and simultaneous group conversation were not explicitly established; shared Space access alone is insufficient evidence. - team_spaces — Are shared projects or workspaces available? [supported]: Space instructions, knowledge and membership are shared with users/groups; conversations remain organized under the Space. Sources: omnifact:omnifact:spaces, omnifact:omnifact:share. - group_chat — Can several people chat together with the AI? [unknown]: Can several people chat together with the AI? Unknown. Sharing individual chat links and simultaneous group conversation were not explicitly established; shared Space access alone is insufficient evidence. - share_permission_boundary — Does sharing respect the recipient's access to sources? [partial]: Space members can see referenced uploaded knowledge. Personal OAuth MCP follows each source account, but Space source-ACL rechecking and generated-answer resharing boundaries were not tested. Sources: omnifact:omnifact:share, omnifact:omnifact:mcp, omnifact:omnifact:sync. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:spaces, omnifact:omnifact:share, omnifact:omnifact:mcp, omnifact:omnifact:sync ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The pinned frontend registers English, German, French and Italian, with fallback behavior; translation quality and WCAG conformance remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=New code findings at v1.19.0 / 9b1fcab141000eaba9f78ed131151de04904454b (published 2026-10-26); earlier accepted facts retain their own pins; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - German administrator labels are present in pinned source; full German/French/Italian screen coverage and naturalness were not observed. - No WCAG conformance statement or full accessibility walkthrough was verified. - ui_languages — Which UI languages are offered? [supported]: The locale implementation registers en, de, fr and it among other resources. Sources: anythingllm:anythingllm: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? No full DE/FR/IT UI walkthrough, German admin-screen completeness review or WCAG conformance report was verified. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: accessibility_statement: Is there a WCAG conformance statement? No full DE/FR/IT UI walkthrough, German admin-screen completeness review or WCAG conformance report was verified. - admin_ui_languages — Is the admin interface available in German? [partial]: The pinned German locale includes user management, invitations, event logs and administrator settings labels. Complete admin-screen coverage, translation quality and WCAG conformance were not observed. Sources: anythingllm:anythingllm:r4-german-admin. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: anythingllm:anythingllm:i18n-pin, anythingllm:anythingllm:r4-german-admin #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial English and German UI are documented; language quality and accessibility are untested. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - admin_ui_languages: A separate German admin documentation tree is published; this does not verify complete German in-app admin translation. - Unverified dach_language_quality, accessibility_statement: No DE/FR/IT UI-quality fixture or WCAG conformance statement was obtained. French/Italian UI is not in the documented EN/DE selector. - ui_languages — Which UI languages are offered? [supported]: Account language selector offers English/German, otherwise browser-language default. Sources: omnifact:omnifact:account. - dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. No DE/FR/IT UI-quality fixture or WCAG conformance statement was obtained. French/Italian UI is not in the documented EN/DE selector. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No DE/FR/IT UI-quality fixture or WCAG conformance statement was obtained. French/Italian UI is not in the documented EN/DE selector. - admin_ui_languages — Is the admin interface available in German? [partial]: A separate German admin documentation tree is published; this does not verify complete German in-app admin translation. Sources: omnifact:omnifact:account. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:account ## 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The standard Docker project documents a privileged simple-SSO passthrough; the commercial Enterprise offer advertises SSO without public protocol details. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=Custom trusted login integration for Simple SSO, Quote-only Enterprise for the advertised SSO offer; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - sso_protocols: Simple SSO generates one-use temporary links for existing users through an API key. It is not evidence of built-in SAML/OIDC/LDAP federation; those protocol details were not verified. - sso_plan: Simple passthrough is documented for self-hosted multi-user mode. Quote-only Enterprise separately advertises SSO, with public protocol/feature scope unspecified. - mfa: Can MFA be enforced? MFA enforcement, conditional-access compatibility and company-domain capture were not established from the standard authentication or public Enterprise offer. - conditional_access: Do Entra conditional-access policies apply? MFA enforcement, conditional-access compatibility and company-domain capture were not established from the standard authentication or public Enterprise offer. - domain_capture: Can the company claim its email domain? MFA enforcement, conditional-access compatibility and company-domain capture were not established from the standard authentication or public Enterprise offer. - sso_protocols — Which SSO protocols and identity providers work? [partial]: Simple SSO generates one-use temporary links for existing users through an API key. It is not evidence of built-in SAML/OIDC/LDAP federation; those protocol details were not verified. Sources: anythingllm:anythingllm:config. - sso_plan — Which plan includes SSO? [partial]: Simple passthrough is documented for self-hosted multi-user mode. Quote-only Enterprise separately advertises SSO, with public protocol/feature scope unspecified. Sources: anythingllm:anythingllm:config, anythingllm:anythingllm:cloud. - mfa — Can MFA be enforced? [unknown]: mfa: Can MFA be enforced? MFA enforcement, conditional-access compatibility and company-domain capture were not established from the standard authentication or public Enterprise offer. - conditional_access — Do Entra conditional-access policies apply? [unknown]: conditional_access: Do Entra conditional-access policies apply? MFA enforcement, conditional-access compatibility and company-domain capture were not established from the standard authentication or public Enterprise offer. - domain_capture — Can the company claim its email domain? [unknown]: domain_capture: Can the company claim its email domain? MFA enforcement, conditional-access compatibility and company-domain capture were not established from the standard authentication or public Enterprise offer. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:config, anythingllm:anythingllm:cloud #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise SAML2.0 uses identity-provider MFA and conditional-access policies; nativeTOTP entitlement is outside this finding. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise SAML/SSO only; nativeTOTP entitlement excluded; add_ons=Enterprise SSO enablement; identity-provider MFA/conditional access; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - The supported MFA path here is the Enterprise identity provider. Native password/TOTP accounts require separate plan verification. - sso_protocols — Which SSO protocols and identity providers work? [supported]: SAML2.0 via SSO Ready; Entra ID, Okta, Keycloak and SAML-compatible Id Ps. OIDC was not established. Sources: omnifact:omnifact:users, omnifact:omnifact:sso-blog, omnifact:omnifact:public-sector. - sso_plan — Which plan includes SSO? [supported]: SSO/SCIM exclusive to Enterprise and support-enabled configuration. Sources: omnifact:omnifact:users. - mfa — Can MFA be enforced? [partial]: For Enterprise SAML/SSO users, authentication and MFA are controlled by the identity provider; Omnifact native2FA setup is hidden. No nativeTOTP entitlement for Pro or Enterprise is asserted. Sources: omnifact:omnifact:security-rev2, omnifact:omnifact:sso-blog. - conditional_access — Do Entra conditional-access policies apply? [partial]: SSO announcement says existing Id P conditional access/MFA/password rules apply; Entra device/location combinations were not tested. Sources: omnifact:omnifact:sso-blog. - domain_capture — Can the company claim its email domain? [unknown]: Can the company claim its email domain? Unknown. No verified company-domain capture/ownership process was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:users, omnifact:omnifact:sso-blog, omnifact:omnifact:public-sector, omnifact:omnifact:security-rev2, omnifact:omnifact:auth ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Admins or API clients create users and assign workspaces; provisioning standards and leaver asset transfer remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - scim: Is SCIM provisioning supported? SCIM and identity-provider group synchronization were not established in the public configuration and Enterprise offer. - group_sync: Are identity-provider groups synced? SCIM and identity-provider group synchronization were not established in the public configuration and Enterprise offer. - jit_provisioning: Simple SSO explicitly requires a user to exist before login; an external system can create the user through the API. This is custom provisioning, not a verified automatic IdP JIT flow. - deprovisioning: Admin routes implement user deletion and log the event. A fixture verifying chat/knowledge ownership transfer and active-session revocation was not run. - scim — Is SCIM provisioning supported? [unknown]: scim: Is SCIM provisioning supported? SCIM and identity-provider group synchronization were not established in the public configuration and Enterprise offer. - group_sync — Are identity-provider groups synced? [unknown]: group_sync: Are identity-provider groups synced? SCIM and identity-provider group synchronization were not established in the public configuration and Enterprise offer. - jit_provisioning — Are users created at first login? [partial]: Simple SSO explicitly requires a user to exist before login; an external system can create the user through the API. This is custom provisioning, not a verified automatic IdP JIT flow. Sources: anythingllm:anythingllm:config. - deprovisioning — What happens to a removed user's data and shared assets? [partial]: Admin routes implement user deletion and log the event. A fixture verifying chat/knowledge ownership transfer and active-session revocation was not run. Sources: anythingllm:anythingllm:admin-pin. - seat_assignment — Can admins assign and reclaim seats? [supported]: Admins create/manage users and workspace membership under the no-seat-fee self-hosted licence. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:admin-pin, anythingllm:anythingllm:license. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:config, anythingllm:anythingllm:admin-pin, anythingllm:anythingllm:security, anythingllm:anythingllm:license #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise SCIM synchronizes users/groups; deactivation blocks login while detailed asset disposition remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - jit_provisioning: Provisioned status includes SSO/SCIM-created accounts before first login; invitations are skipped for SSO. Exact just-in-time account trigger not specified. - deprovisioning: Deactivated users cannot log in; only unaccepted invitees can be permanently deleted from user list. Space removal keeps prior contributions; full leaver private data/agent ownership effects unspecified. - seat_assignment: Active and invited users count as seats; adding prorates cost, removal credits next invoice. Deactivated-seat billing treatment not fully specified. - scim — Is SCIM provisioning supported? [supported]: Dedicated sso-sync creates, updates anddeactivates users automatically; manual creation/profile/role/CSV changes are locked under SCIM. Sources: omnifact:omnifact:users. - group_sync — Are identity-provider groups synced? [supported]: Entra, Okta or Google Workspace groups mirror into immutable-membership Synced Groups with Omnifact-managed permissions. Sources: omnifact:omnifact:groups. - jit_provisioning — Are users created at first login? [partial]: Provisioned status includes SSO/SCIM-created accounts before first login; invitations are skipped for SSO. Exact just-in-time account trigger not specified. Sources: omnifact:omnifact:users. - deprovisioning — What happens to a removed user's data and shared assets? [partial]: Deactivated users cannot log in; only unaccepted invitees can be permanently deleted from user list. Space removal keeps prior contributions; full leaver private data/agent ownership effects unspecified. Sources: omnifact:omnifact:users, omnifact:omnifact:share. - seat_assignment — Can admins assign and reclaim seats? [partial]: Active and invited users count as seats; adding prorates cost, removal credits next invoice. Deactivated-seat billing treatment not fully specified. Sources: omnifact:omnifact:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:users, omnifact:omnifact:groups, omnifact:omnifact:share, omnifact:omnifact:billing ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Standard Docker multi-user governance uses Admin, Manager and Default roles plus workspace membership. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - groups: Can permissions be set per group? An independently configurable local/IdP group object and two-group permission fixture were not established. - feature_toggles: Operators configure available Agent skills, providers and workspaces. A fine-grained per-group feature matrix was not established for standard roles. - multi_entity: Workspaces separate access within one installation; legal-entity tenancy, separate operator boundaries and a multi-entity contract were not verified. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Admins control the whole system; Managers manage workspaces but cannot change the system LLM/embedder/vector settings; Default users chat in assigned workspaces. Sources: anythingllm:anythingllm:security. - groups — Can permissions be set per group? [unknown]: groups: Can permissions be set per group? An independently configurable local/IdP group object and two-group permission fixture were not established. - feature_toggles — Which features can be switched on or off per group? [partial]: Operators configure available Agent skills, providers and workspaces. A fine-grained per-group feature matrix was not established for standard roles. Sources: anythingllm:anythingllm:agent-setup, anythingllm:anythingllm:security. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Workspaces separate access within one installation; legal-entity tenancy, separate operator boundaries and a multi-entity contract were not verified. Sources: anythingllm:anythingllm:security. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:agent-setup #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Owner/Admin/Member and Space roles combine with additive groups. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - multi_entity: Organization tenant separation and department Space/group boundaries are described; terms prohibit multiple accounts for one company and usage beyond own personnel without agreement. Multi-subsidiary contract rights were not established. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Owner includes Admin/Member, Admin includes Member; Admin manages team users/settings except Owner. Space Admin/Editor is separate, with optional Knowledge Base Manager in DPA. Sources: omnifact:omnifact:users, omnifact:omnifact:share, omnifact:omnifact:dpa. - groups — Can permissions be set per group? [supported]: Everyone, SCIM-synced andmanual groups; permissions union rather than deny. Sources: omnifact:omnifact:groups. - feature_toggles — Which features can be switched on or off per group? [supported]: Group grants file/image uploads, audio, web, imagegeneration, code, dictation, modeltiers, USmodels, filterexemption; organization models/features must also be enabled. Sources: omnifact:omnifact:groups. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Organization tenant separation and department Space/group boundaries are described; terms prohibit multiple accounts for one company and usage beyond own personnel without agreement. Multi-subsidiary contract rights were not established. Sources: omnifact:omnifact:dpa, omnifact:omnifact:terms, omnifact:omnifact:share. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:users, omnifact:omnifact:share, omnifact:omnifact:dpa, omnifact:omnifact:groups, omnifact:omnifact:terms ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Authorized accounts can inspect chat/event activity and export chat logs; a full adoption/cost dashboard was not verified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - adoption_dashboard: Is there an adoption dashboard? A dedicated adoption dashboard and pseudonymized/aggregated per-person reporting controls were not established; optional anonymous product telemetry is a separate data flow. - breakdowns: Chat logs are available per workspace/user to authorized accounts; complete model/feature/assistant/group adoption breakdowns were not established. - privacy_modes: Can per-person reporting be limited or pseudonymised? A dedicated adoption dashboard and pseudonymized/aggregated per-person reporting controls were not established; optional anonymous product telemetry is a separate data flow. - adoption_dashboard — Is there an adoption dashboard? [unknown]: adoption_dashboard: Is there an adoption dashboard? A dedicated adoption dashboard and pseudonymized/aggregated per-person reporting controls were not established; optional anonymous product telemetry is a separate data flow. - breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Chat logs are available per workspace/user to authorized accounts; complete model/feature/assistant/group adoption breakdowns were not established. Sources: anythingllm:anythingllm:logs, anythingllm:anythingllm:event. - export — Can usage data be exported? [supported]: Chat logs export as CSV, JSON, Alpaca JSON or OpenAI-style JSONL once at least ten logs exist. Sources: anythingllm:anythingllm:logs. - privacy_modes — Can per-person reporting be limited or pseudonymised? [unknown]: privacy_modes: Can per-person reporting be limited or pseudonymised? A dedicated adoption dashboard and pseudonymized/aggregated per-person reporting controls were not established; optional anonymous product telemetry is a separate data flow. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:logs, anythingllm:anythingllm:event #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise adoption analytics show active users and message counts; deeper breakdown/export controls are unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise Usage Analytics & Insights; Pro excluded; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Dashboard scope is organization/day level; additional model/group/assistant breakdowns and export remain unverified. - adoption_dashboard — Is there an adoption dashboard? [supported]: Analytics provides date-range totals and daily active-user/message charts with interactive metric toggles; Enterprise-only in pricing. Sources: omnifact:omnifact:analytics-rev2, omnifact:omnifact:pricing-rev2. - breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Documented dashboard is organization/day level. Model, group, feature andassistant breakdown matrix was not established. Sources: omnifact:omnifact:analytics-rev2. - export — Can usage data be exported? [unknown]: Can usage data be exported? Unknown. No documented analytics export/API or configurable individual-reporting controls were established. Direct HTML retrieval returned403; public cached official page was retrieved through the web tool. - privacy_modes — Can per-person reporting be limited or pseudonymised? [partial]: DPA describes anonymized PostHog feature-use analytics without individual attribution; separate customer-visible reporting privacy toggles were not established. Sources: omnifact:omnifact:dpa-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:analytics-rev2, omnifact:omnifact:pricing-rev2, omnifact:omnifact:dpa-rev2 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Per-user message quotas control consumption; monetary budgets and cost-centre allocation were not established. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - cost_visibility: Authorized users see chat activity by workspace/user. The reviewed sources do not establish actual billed currency cost by group. - budgets: Admins can set per-user daily message quotas. This is a count limit, not a documented CHF/EUR budget or pooled cost-centre allowance. - chargeback: Can costs be exported per cost centre? Monetary spend caps, model downgrades and cost-centre chargeback export were not verified. - cost_visibility — Can admins see cost or consumption per user and group? [partial]: Authorized users see chat activity by workspace/user. The reviewed sources do not establish actual billed currency cost by group. Sources: anythingllm:anythingllm:logs. - budgets — Can budgets be set per user or group? [partial]: Admins can set per-user daily message quotas. This is a count limit, not a documented CHF/EUR budget or pooled cost-centre allowance. Sources: anythingllm:anythingllm:user-pin. - budget_enforcement — Does reaching a budget alert, block or downgrade? [supported]: The inspected non-admin multi-user chat route aborts before generation when the trailing-24-hour message quota is reached. Sources: anythingllm:anythingllm:chat-pin, anythingllm:anythingllm:user-pin. - chargeback — Can costs be exported per cost centre? [unknown]: chargeback: Can costs be exported per cost centre? Monetary spend caps, model downgrades and cost-centre chargeback export were not verified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:logs, anythingllm:anythingllm:user-pin, anythingllm:anythingllm:chat-pin #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared pooled credits and model permissions constrain spend; individual financial allocation is unspecified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - cost_visibility: Billing shows pooled real-time consumption andforecast; Enterprise detailed real-time dashboard is described as forthcoming, while total used is available. - budgets: Organization pooled allowance and manual additional-credit recharge. Model-tier and USroute access can be group-controlled, but per-user/group monetary hard caps were not established. - Unverified chargeback: No cost-centre chargeback export or complete cost-per-user/group allocation interface was established. - cost_visibility — Can admins see cost or consumption per user and group? [partial]: Billing shows pooled real-time consumption andforecast; Enterprise detailed real-time dashboard is described as forthcoming, while total used is available. Sources: omnifact:omnifact:billing. - budgets — Can budgets be set per user or group? [partial]: Organization pooled allowance and manual additional-credit recharge. Model-tier and USroute access can be group-controlled, but per-user/group monetary hard caps were not established. Sources: omnifact:omnifact:billing, omnifact:omnifact:groups. - budget_enforcement — Does reaching a budget alert, block or downgrade? [supported]: Monthly budget: chat downgrades to enabled fallbacks; Gateway hard-blocks all calls on exhausted credits. Daily message quota disables send until reset. Sources: omnifact:omnifact:limits, omnifact:omnifact:gateway, omnifact:omnifact:chat. - chargeback — Can costs be exported per cost centre? [unknown]: Can costs be exported per cost centre? Unknown. No cost-centre chargeback export or complete cost-per-user/group allocation interface was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:billing, omnifact:omnifact:groups, omnifact:omnifact:limits, omnifact:omnifact:gateway, omnifact:omnifact:chat ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Event logs record named administrative/security activity and chats are exportable. Immutable audit retention and legal hold remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - siem_export: Can logs stream to a SIEM or be exported? No complete log retention period, tamper-evident integrity model, SIEM streaming contract or eDiscovery/legal-hold workflow was verified. These are event/chat logs, not a certified audit archive. - ediscovery: Are eDiscovery and legal hold supported? No complete log retention period, tamper-evident integrity model, SIEM streaming contract or eDiscovery/legal-hold workflow was verified. These are event/chat logs, not a certified audit archive. - log_retention: How long are logs kept? No complete log retention period, tamper-evident integrity model, SIEM streaming contract or eDiscovery/legal-hold workflow was verified. These are event/chat logs, not a certified audit archive. - admin_events — Are admin and security events logged? [supported]: Pinned admin routes log user creation/deletion, invitation and API-key events; docs also name logins, setting changes and uploads. Sources: anythingllm:anythingllm:admin-pin, anythingllm:anythingllm:event. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [supported]: Workspace chat history/logs retain prompts/responses and expose permissioned exports. Retention and external copies depend on the deployment. Sources: anythingllm:anythingllm:logs. - siem_export — Can logs stream to a SIEM or be exported? [unknown]: siem_export: Can logs stream to a SIEM or be exported? No complete log retention period, tamper-evident integrity model, SIEM streaming contract or eDiscovery/legal-hold workflow was verified. These are event/chat logs, not a certified audit archive. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: ediscovery: Are eDiscovery and legal hold supported? No complete log retention period, tamper-evident integrity model, SIEM streaming contract or eDiscovery/legal-hold workflow was verified. These are event/chat logs, not a certified audit archive. - log_retention — How long are logs kept? [unknown]: log_retention: How long are logs kept? No complete log retention period, tamper-evident integrity model, SIEM streaming contract or eDiscovery/legal-hold workflow was verified. These are event/chat logs, not a certified audit archive. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:admin-pin, anythingllm:anythingllm:event, anythingllm:anythingllm:logs #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA documents append-only admin logs for at least 90 days; content compliance export is unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - log_retention: Administrative logs retained at least 90 days; content retention is customer-configured but not a published compliance archive. - Unverified content_logging, siem_export, ediscovery: No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports. - admin_events — Are admin and security events logged? [supported]: TOM2.5 records user-status changes/resource deletions with user attribution, UTC timestamps, encrypted transport/storage and append-only protection; event coverage can expand. Sources: omnifact:omnifact:dpa. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [unknown]: Can prompts and answers be retained for compliance, and is it configurable? Unknown. No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports. - siem_export — Can logs stream to a SIEM or be exported? [unknown]: Can logs stream to a SIEM or be exported? Unknown. No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are e Discovery and legal hold supported? Unknown. No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports. - log_retention — How long are logs kept? [partial]: Administrative logs retained at least 90 days; content retention is customer-configured but not a published compliance archive. Sources: omnifact:omnifact:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa ### 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. #### AnythingLLM Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Default Privacy Filter combines local NER/regex masking with several explicit bypass paths. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise, filter defaults enabled; user exemptions/advanced feature flags qualified; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - pii_detection: Names, addresses, email, phone, IPv4, US/German IDs/passports, tax/pensionnumbers, IBAN/BIC/card/routing/account numbers, companies anddocument filenames. Media bytes are not scanned; AHV recognition untested. - pii_action: Detected strings replaced with placeholders then restored in output; web queries containing masked values are blocked. Click-to-Reveal confirms sending individual terms; optional%%exemption defaults off andrequires Support. Group exemptions may disable filtering per agent/Space. - custom_patterns: Vendor detector uses custom-trained SLMNER andregex, but customer-defined pattern/dictionary UI/API was not established. Optional%%syntax bypasses rather than adds detection. - filter_location: DPA places filter within Azure Germany West Central, Frankfurt before external model. MCP arguments/results, code, sandbox, images/audio bytes, personalization and Published Space API bypass filtering by design. - Unverified dlp_integration: No existing third-party DLP/Purview integration or synthetic AHV/IBAN accuracy fixture was established. - pii_detection — Is personal data detected in prompts and files? [partial]: Names, addresses, email, phone, IPv4, US/German IDs/passports, tax/pensionnumbers, IBAN/BIC/card/routing/account numbers, companies anddocument filenames. Media bytes are not scanned; AHV recognition untested. Sources: omnifact:omnifact:dpa, omnifact:omnifact:files, omnifact:omnifact:privacy. - pii_action — Is it redacted, masked, blocked or only warned? [partial]: Detected strings replaced with placeholders then restored in output; web queries containing masked values are blocked. Click-to-Reveal confirms sending individual terms; optional%%exemption defaults off andrequires Support. Group exemptions may disable filtering per agent/Space. Sources: omnifact:omnifact:privacy, omnifact:omnifact:web, omnifact:omnifact:groups, omnifact:omnifact:dpa. - custom_patterns — Can admins add custom patterns or terms? [partial]: Vendor detector uses custom-trained SLMNER andregex, but customer-defined pattern/dictionary UI/API was not established. Optional%%syntax bypasses rather than adds detection. Sources: omnifact:omnifact:dpa. - dlp_integration — Does it integrate with an existing DLP product? [unknown]: Does it integrate with an existing DLP product? Unknown. No existing third-party DLP/Purview integration or synthetic AHV/IBAN accuracy fixture was established. - filter_location — Where does filtering run? [partial]: DPA places filter within Azure Germany West Central, Frankfurt before external model. MCP arguments/results, code, sandbox, images/audio bytes, personalization and Published Space API bypass filtering by design. Sources: omnifact:omnifact:dpa, omnifact:omnifact:privacy, omnifact:omnifact:published, omnifact:omnifact:account. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa, omnifact:omnifact:files, omnifact:omnifact:privacy, omnifact:omnifact:web, omnifact:omnifact:groups, omnifact:omnifact:published, omnifact:omnifact:account ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workspace instructions can guide models; a mandatory organization-wide policy and violation system remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - org_instructions: Admins/Managers configure workspace/system prompt context and model defaults. A single unavoidable organization policy and its enforcement were not established. - usage_notice: Can users be required to accept a usage policy? Required policy acknowledgement, semantic content filters and administrator policy-violation reporting were not established by the configuration/security sources. Model instructions are not a demonstrated content-control guarantee. - content_filters: Are content filters configurable? Required policy acknowledgement, semantic content filters and administrator policy-violation reporting were not established by the configuration/security sources. Model instructions are not a demonstrated content-control guarantee. - violation_reporting: Are policy hits visible to admins? Required policy acknowledgement, semantic content filters and administrator policy-violation reporting were not established by the configuration/security sources. Model instructions are not a demonstrated content-control guarantee. - org_instructions — Can admins set organisation-wide instructions? [partial]: Admins/Managers configure workspace/system prompt context and model defaults. A single unavoidable organization policy and its enforcement were not established. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:systemprompt, anythingllm:anythingllm:llmconfig. - usage_notice — Can users be required to accept a usage policy? [unknown]: usage_notice: Can users be required to accept a usage policy? Required policy acknowledgement, semantic content filters and administrator policy-violation reporting were not established by the configuration/security sources. Model instructions are not a demonstrated content-control guarantee. - content_filters — Are content filters configurable? [unknown]: content_filters: Are content filters configurable? Required policy acknowledgement, semantic content filters and administrator policy-violation reporting were not established by the configuration/security sources. Model instructions are not a demonstrated content-control guarantee. - violation_reporting — Are policy hits visible to admins? [unknown]: violation_reporting: Are policy hits visible to admins? Required policy acknowledgement, semantic content filters and administrator policy-violation reporting were not established by the configuration/security sources. Model instructions are not a demonstrated content-control guarantee. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:systemprompt, anythingllm:anythingllm:llmconfig #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Company/Space instructions and privacy/tool governance exist; mandatory policy workflows are unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - org_instructions: Teamdescription supplies businesscontext; Spaceinstructions set response behavior and strict grounding. No guaranteed immutable organization safety instruction hierarchy was established. - content_filters: Organization PIImasking, group capabilities/modelroutes andper-tool approval/block settings are documented. General topic/abusefilter customization was not established. - Unverified usage_notice, violation_reporting: No mandatory AI-use-policy acknowledgement, admin policy-hit dashboard or configurable general content-filter taxonomy was established. - org_instructions — Can admins set organisation-wide instructions? [partial]: Teamdescription supplies businesscontext; Spaceinstructions set response behavior and strict grounding. No guaranteed immutable organization safety instruction hierarchy was established. Sources: omnifact:omnifact:company, omnifact:omnifact:create, omnifact:omnifact:retrieval. - usage_notice — Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? Unknown. No mandatory AI-use-policy acknowledgement, admin policy-hit dashboard or configurable general content-filter taxonomy was established. - content_filters — Are content filters configurable? [partial]: Organization PIImasking, group capabilities/modelroutes andper-tool approval/block settings are documented. General topic/abusefilter customization was not established. Sources: omnifact:omnifact:privacy, omnifact:omnifact:groups, omnifact:omnifact:mcp. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. No mandatory AI-use-policy acknowledgement, admin policy-hit dashboard or configurable general content-filter taxonomy was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:company, omnifact:omnifact:create, omnifact:omnifact:retrieval, omnifact:omnifact:privacy, omnifact:omnifact:groups, omnifact:omnifact:mcp ## 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Self-hosted locations are customer-selected. Managed Cloud uses AWS, but a guaranteed country for all storage/inference/support was not established. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - backups_logs_region: Self-hosted logs/storage follow deployment choices; telemetry is optional. Cloud backup/log geography and actual egress were not audited. - support_access_region: Cloud privacy explicitly allows necessary Mintplex team access for debugging/maintenance; support-access country restrictions were not established. - swiss_hosting: Customers can self-host on Swiss infrastructure. A vendor-managed Swiss Cloud region and Swiss inference/support commitment were not established. - residency_plan: Customer-operated placement is available with self-hosting. Public Basic/Pro/Enterprise offers do not establish a complete Swiss/EU data-boundary package. - storage_region — Where are chats, files and indexes stored? [supported]: Docker data/embedding storage is customer configured; Desktop uses its local OS data directory. Managed Cloud documentation identifies AWS but does not establish a country. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:storage, anythingllm:anythingllm:cloud-overview. - inference_region — Where do model calls run, per provider? [supported]: Local endpoints run where the operator deploys them; Azure/AWS/Vertex routes and cloud APIs use the selected provider. Self-hosting the UI does not fix inference geography. Sources: anythingllm:anythingllm:built-in, anythingllm:anythingllm:azure, anythingllm:anythingllm:bedrock, anythingllm:anythingllm:vertex. - backups_logs_region — Where are backups, logs and telemetry? [partial]: Self-hosted logs/storage follow deployment choices; telemetry is optional. Cloud backup/log geography and actual egress were not audited. Sources: anythingllm:anythingllm:privacy, anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:localdocker. - support_access_region — From where can vendor staff access data? [partial]: Cloud privacy explicitly allows necessary Mintplex team access for debugging/maintenance; support-access country restrictions were not established. Sources: anythingllm:anythingllm:privacy-cloud. - swiss_hosting — Is Swiss hosting available? [partial]: Customers can self-host on Swiss infrastructure. A vendor-managed Swiss Cloud region and Swiss inference/support commitment were not established. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:cloud-overview. - residency_plan — Which plan or option provides residency? [partial]: Customer-operated placement is available with self-hosting. Public Basic/Pro/Enterprise offers do not establish a complete Swiss/EU data-boundary package. Sources: anythingllm:anythingllm:docker, anythingllm:anythingllm:cloud. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:storage, anythingllm:anythingllm:cloud-overview, anythingllm:anythingllm:built-in, anythingllm:anythingllm:azure, anythingllm:anythingllm:bedrock, anythingllm:anythingllm:vertex, anythingllm:anythingllm:privacy, anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:docker, anythingllm:anythingllm:cloud #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Hosted primary workspace storage is in Azure EU. Germany-only processing and complete backup/log/support residency are not established; model and metadata routes differ. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise hosted Azure platform storage; model and edge-metadata routes separately scoped; add_ons=Enterprise AI Gateway where named; provider/model route and eu/ prefix selected explicitly; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - The storage finding covers primary workspace content, not every model/edge/support processing path. No Germany-only or whole-service EU-only guarantee is made. - storage_region — Where are chats, files and indexes stored? [partial]: Hosted raw chats/files/indexed workspace content uses Azure infrastructure in the EU. DPA identifies GermanyWestCentral/Frankfurt; the live infrastructure register also names NL/SE/IE. Only EU primary-platform storage is claimed here; a Germany-only deployment footprint is not established. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:trust-rev2. - inference_region — Where do model calls run, per provider? [supported]: EU routes include Azure OpenAI, Google Cloud EU for Gemini/Anthropic, and Mistral EU. Direct OpenAI/Anthropic US and Google API global routes also exist. Gateway needs eu/ prefix; unprefixed IDs never use EU backends. Sources: omnifact:omnifact:models, omnifact:omnifact:vertex, omnifact:omnifact:gateway, omnifact:omnifact:trust-rev2. - backups_logs_region — Where are backups, logs and telemetry? [unknown]: Unknown per-service backup/log geography for a particular contract. DPA Frankfurt/EU wording and the broader Azure DE/NL/SE/IE register do not map each backup stream. Cloudflare EU/US edge metadata/security logs are separate from platform document storage. - support_access_region — From where can vendor staff access data? [partial]: Pricing names German and US service teams; DPA permits justified, time-limited production access. Staff physical access locations by task are not specified. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:dpa-rev2. - swiss_hosting — Is Swiss hosting available? [unknown]: Is Swiss hosting available? Unknown. No full Swiss platform/backup/support hosting option was established. - residency_plan — Which plan or option provides residency? [partial]: Pro/Enterprise pricing offers EU cloud storage and EU model routes. This does not establish all-service EU residency. Enterprise Gateway requests require eu/ model IDs for EU backends; direct/global model routes and edge metadata have different geography. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:gateway, omnifact:omnifact:providers-rev2, omnifact:omnifact:trust-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:models, omnifact:omnifact:vertex, omnifact:omnifact:gateway, omnifact:omnifact:trust-rev2, omnifact:omnifact:pricing-rev2, omnifact:omnifact:groups-rev2, omnifact:omnifact:providers-rev2 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Docker supports customer-cloud/on-premise operation; Cloud sells isolated managed instances and Desktop is a separate local client. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - multi_tenant_saas: Is a shared SaaS offered? A shared multi-tenant SaaS was not established: the public managed offer describes private isolated instances. - air_gapped: Local models/embeddings can run after assets are downloaded. A full disconnected fixture was not run; online tools and optional periodically validated Desktop Pro need separate treatment. - multi_tenant_saas — Is a shared SaaS offered? [unknown]: multi_tenant_saas: Is a shared SaaS offered? A shared multi-tenant SaaS was not established: the public managed offer describes private isolated instances. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [supported]: The managed Cloud overview describes one isolated AWS instance per customer. Current pricing lists Basic and Pro, with Enterprise custom services; no numeric seat minimum is published in the reviewed offer. Sources: anythingllm:anythingllm:cloud-overview, anythingllm:anythingllm:cloud. - customer_cloud — Can it run in the customer's own cloud account, from what size? [supported]: Docker can run on customer-selected servers/cloud accounts without an MIT software seat minimum. Sources: anythingllm:anythingllm:docker, anythingllm:anythingllm:localdocker, anythingllm:anythingllm:license. - on_premise — Can the whole platform run on customer infrastructure, from what size? [supported]: Customers can operate the Docker stack with local providers; commercial Enterprise also advertises on-premise support. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:models, anythingllm:anythingllm:cloud. - air_gapped — Can it run without internet access? [partial]: Local models/embeddings can run after assets are downloaded. A full disconnected fixture was not run; online tools and optional periodically validated Desktop Pro need separate treatment. Sources: anythingllm:anythingllm:built-in, anythingllm:anythingllm:local-embed, anythingllm:anythingllm:pro-key. - mode_feature_gaps — Which features are missing outside SaaS? [supported]: Desktop is single-user; Docker provides multi-user administration; Cloud explicitly excludes built-in inference, custom coded Agents and MCP. Scheduled Jobs and mail skills are single-user only. Sources: anythingllm:anythingllm:desktop, anythingllm:anythingllm:cloud-limits, anythingllm:anythingllm:job, anythingllm:anythingllm:outlook. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:cloud-overview, anythingllm:anythingllm:cloud, anythingllm:anythingllm:docker, anythingllm:anythingllm:localdocker, anythingllm:anythingllm:license, anythingllm:anythingllm:models, anythingllm:anythingllm:built-in, anythingllm:anythingllm:local-embed, anythingllm:anythingllm:pro-key, anythingllm:anythingllm:desktop, anythingllm:anythingllm:cloud-limits, anythingllm:anythingllm:job, anythingllm:anythingllm:outlook #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Saa S, customer-cloud and on-premise are offered without published private-deployment minimums. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Enterprise customer-cloud/on-premise; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise Saa S; Enterprise quoted private deployment; add_ons=Deployment/infrastructure/operator costs quoted; deployment_mode=not specified; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - dedicated_instance: Managed, own-cloud and on-premise are advertised; a distinct dedicated Saa S specification and seat threshold were not established. - customer_cloud: Own/private cloud is available on request; minimum seats/spend, operating roles and supported infrastructure are not public. - on_premise: Enterprise on-premise option includes municipal datacenters; numeric minimum and architecture requirements are unpublished. - Unverified air_gapped, mode_feature_gaps: Air-gapped operation and per-mode feature/egress parity were not established; a general self-hosting article is not a deployment specification. - multi_tenant_saas — Is a shared SaaS offered? [supported]: Cloud Saa S uses logical organization/client separation. Sources: omnifact:omnifact:terms, omnifact:omnifact:dpa. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [partial]: Managed, own-cloud and on-premise are advertised; a distinct dedicated Saa S specification and seat threshold were not established. Sources: omnifact:omnifact:home. - customer_cloud — Can it run in the customer's own cloud account, from what size? [partial]: Own/private cloud is available on request; minimum seats/spend, operating roles and supported infrastructure are not public. Sources: omnifact:omnifact:home, omnifact:omnifact:public-sector. - on_premise — Can the whole platform run on customer infrastructure, from what size? [partial]: Enterprise on-premise option includes municipal datacenters; numeric minimum and architecture requirements are unpublished. Sources: omnifact:omnifact:pricing, omnifact:omnifact:public-sector. - air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? Unknown. Air-gapped operation and per-mode feature/egress parity were not established; a general self-hosting article is not a deployment specification. - mode_feature_gaps — Which features are missing outside SaaS? [unknown]: Which features are missing outside Saa S? Unknown. Air-gapped operation and per-mode feature/egress parity were not established; a general self-hosting article is not a deployment specification. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:terms, omnifact:omnifact:dpa, omnifact:omnifact:home, omnifact:omnifact:public-sector, omnifact:omnifact:pricing ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Application locality and provider retention are separate; no universal no-training or zero-retention contract was verified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - vendor_training: The Desktop policy describes local chat/document storage and optional anonymous telemetry. Cloud terms grant platform-improvement usage rights without a specific reviewed model-training exclusion. This is not a blanket no-training assurance. - provider_training: Do model providers train on it under this product's contracts? No configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. - provider_retention: How long do model providers keep prompts, including for abuse monitoring? No configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. - zero_retention: Is zero data retention available, and on which plan? No configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. - human_review: Can provider staff review content? No configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. - vendor_training — Does the vendor train on customer content? [partial]: The Desktop policy describes local chat/document storage and optional anonymous telemetry. Cloud terms grant platform-improvement usage rights without a specific reviewed model-training exclusion. This is not a blanket no-training assurance. Sources: anythingllm:anythingllm:privacy-desktop, anythingllm:anythingllm:terms-cloud. - 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 configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. - 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 configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. - zero_retention — Is zero data retention available, and on which plan? [unknown]: zero_retention: Is zero data retention available, and on which plan? No configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. - human_review — Can provider staff review content? [unknown]: human_review: Can provider staff review content? No configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:privacy-desktop, anythingllm:anythingllm:terms-cloud #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Managed-route documentation promises no model training. Applicable upstream retention, ZDR eligibility and human-review exceptions remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise managed chat routes; AI Gateway statements apply only to the Enterprise API module; actual upstream retention unverified; add_ons=Enterprise AI Gateway enablement where explicitly named; BYOK under customer-provider agreement; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - No universal provider ZDR finding is made. The advertised ZDR option is not treated as unsupported; its applicable terms remain a gap. - vendor_training — Does the vendor train on customer content? [supported]: Vendor says it never uses customer data to train its own models. Sources: omnifact:omnifact:privacy-intro. - provider_training — Do model providers train on it under this product's contracts? [partial]: The vendor promises no underlying-provider training for the Enterprise AI Gateway. BYOK processing is under the customer-provider agreement; no managed-route promise is extended to arbitrary customer keys. Sources: omnifact:omnifact:gateway-web, omnifact:omnifact:dpa-rev2. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [unknown]: Unknown applicable duration per enabled model/provider/project. The Trust register describes typical directOpenAI30-day retention and configuration-dependent Google logging, while EU-route pages advertise ZDR. These are not mapped to an actual customer route/contract, so no model-specific retention guarantee is asserted. - zero_retention — Is zero data retention available, and on which plan? [unknown]: Unknown verified ZDR eligibility and scope per Pro/Enterprise model route. Gateway payload handling and EU-route marketing do not establish the upstream provider agreement or every safety/logging exception. Workspace database storage is separate. - human_review — Can provider staff review content? [partial]: Provider processing summaries are request-only in Trust Center; human abuse-review exceptions by provider/model were not established. Sources: omnifact:omnifact:trust-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:privacy-intro, omnifact:omnifact:gateway-web, omnifact:omnifact:dpa-rev2, omnifact:omnifact:trust-rev2, omnifact:omnifact:vertex ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Removing workspace access differs from full document erasure; managed Cloud states immediate unrecoverable deletion on cancellation. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - default_retention: Self-hosted documents/history remain in local storage until removed; a universal duration covering chats, indexes, logs, backups and memory was not established. - admin_retention: Can admins set retention periods? A general time-based admin retention scheduler and verified deletion of backups/external-provider copies were not established. - default_retention — What is retained and for how long by default? [partial]: Self-hosted documents/history remain in local storage until removed; a universal duration covering chats, indexes, logs, backups and memory was not established. Sources: anythingllm:anythingllm:privacy, anythingllm:anythingllm:storage. - admin_retention — Can admins set retention periods? [unknown]: admin_retention: Can admins set retention periods? A general time-based admin retention scheduler and verified deletion of backups/external-provider copies were not established. - user_deletion — Can users delete their chats and files permanently? [supported]: Workspace removal deletes that workspace’s vectors but retains the reusable document. My Documents deletion removes the parsed source/cache and all workspace copies according to the privacy guide. Sources: anythingllm:anythingllm:privacy. - contract_end_deletion — What is deleted at contract end, and when? [supported]: For managed Cloud only, the current policy and generic terms state permanent non-recoverable instance/data deletion at cancellation, nonpayment or manual termination. No grace period is promised. Sources: anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:terms-cloud. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:privacy, anythingllm:anythingllm:storage, anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:terms-cloud #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA contract-end return/approved-destruction duties are separate from support-request deletion and backup retention. A guaranteed runtime exit window remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise published DPA return/deletion obligations; actual runtime exit and account-deletion timing unverified; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - The finding states separate contractual and documented operational procedures. It does not turn a support-request clock into an exit grace period. - default_retention — What is retained and for how long by default? [partial]: DPA: database PITR30 days with daily snapshots/continuous WAL; weekly pg_dump fallback; blob soft-delete14 days. Universal default chat/file retention is unspecified. Sources: omnifact:omnifact:dpa-rev2. - admin_retention — Can admins set retention periods? [partial]: DPA permits organization administrators to set customer-data retention; UI range and per-object options are not published. Sources: omnifact:omnifact:dpa-rev2. - user_deletion — Can users delete their chats and files permanently? [partial]: The Space uploaded-file guide describes permanent deletion of a selected file. Registered-user/profile and whole-organization runtime deletion semantics are not established here; the user-list Delete operation applies to unaccepted invitations. Sources: omnifact:omnifact:uploads, omnifact:omnifact:users. - contract_end_deletion — What is deleted at contract end, and when? [partial]: DPA9.2 requires return or controller-approved destruction no later than contract end, except legal retention;9.3 permits proof-of-processing documentation retention. The TOM separately describes support-request organization deletion within30days and backups aging out. No guaranteed post-termination self-service access window or tested runtime completion time is inferred. Sources: omnifact:omnifact:dpa-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:users, omnifact:omnifact:uploads ### 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. #### AnythingLLM Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA defines processor-change notice and transfer safeguards; a complete current contract-specific supplier/entity/country register remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise standard hosted DPA; optional model-provider routes only under the applicable contract/instruction; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Neither public list is silently treated as complete. Ordinary notification/transfer contract terms remain distinct from a verified current processing inventory. - subprocessor_list — Is a dated sub-processor list published? [unknown]: Unknown complete current plan-specific processor inventory. DPAAnnex4 and the live Trust register publish different sets; no source establishes a consolidated applicable list or the role of every listed provider for a given contract. - subprocessor_countries — Which countries do sub-processors operate in? [unknown]: Unknown complete country/legal-entity matrix for the scoped contract. Azure infrastructure and Cloudflare metadata have different roles, and optional model-provider routes depend on selection. The differing DPA/Trust entries are not combined into one asserted authoritative list. - change_notification — Are customers notified of sub-processor changes? [supported]: DPA6.3 requires written/text notice at least 30 days before new/replaced subprocessor and objection opportunity before start. Sources: omnifact:omnifact:dpa-rev2. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: Omnifact Gmb H, Frankfurt, Germany, HRB131357. Ultimate parent/shareholding was not established. Sources: omnifact:omnifact:imprint. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [partial]: DPA1.4 permits nonEEA processing after prior information and safeguards under Articles44-49. Optional BYOK/provider routes depend on their applicable agreements. A specific current SCC/DPF basis for every Trust entry was not verified. Sources: omnifact:omnifact:dpa-rev2. - government_access_policy — Is there a published government-access or transparency policy? [partial]: DPA11.2 requires seizure/confiscation notice unless prohibited by court/authority; Terms15.3 require advance compelled-disclosure notice where legal. Separate request statistics were not verified. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:trust-rev2, omnifact:omnifact:imprint, omnifact:omnifact:terms ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Generic Cloud terms specify California law; a negotiated DPA and regulatory or sector package were not verified. Availability: generally-available Delivery: native Scope: surfaces=AnythingLLM Cloud managed instance, Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - dpa: Is a DPA available, and is it negotiable? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. - revdsg_gdpr: Does the DPA cover revDSG and GDPR? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. - governing_law: Managed Cloud terms specify California, United States law and explicitly exclude self-hosted deployments. A specific court and enterprise override were not established. - ai_act_materials: Is EU AI Act documentation provided? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. - sector_materials: Are FINMA or other sector materials provided? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. - dpa — Is a DPA available, and is it negotiable? [unknown]: dpa: Is a DPA available, and is it negotiable? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [unknown]: revdsg_gdpr: Does the DPA cover revDSG and GDPR? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. - governing_law — Which law and court govern the contract? [partial]: Managed Cloud terms specify California, United States law and explicitly exclude self-hosted deployments. A specific court and enterprise override were not established. Sources: anythingllm:anythingllm:terms-cloud. - ai_act_materials — Is EU AI Act documentation provided? [unknown]: ai_act_materials: Is EU AI Act documentation provided? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. - sector_materials — Are FINMA or other sector materials provided? [unknown]: sector_materials: Are FINMA or other sector materials provided? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:terms-cloud #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public GDPR DPA is binding in German; Swiss and sector-specific contract coverage remains incomplete. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - dpa: Article28 DPA accepted at registration. German text prevails; English is a translation. Written amendments are possible but negotiability is not promised. - revdsg_gdpr: GDPR is explicit; revised Swiss DSG coverage/addendum and Swiss SCC modifications were not established. - ai_act_materials: Public AI Act whitepaper and Academy literacy/certification training are advertised; these are not product conformity attestations. - sector_materials: Public-administration, banking and healthcare positioning/private hosting are advertised; actual FINMA/DORA/§203 contract pack was not verified. - dpa — Is a DPA available, and is it negotiable? [partial]: Article28 DPA accepted at registration. German text prevails; English is a translation. Written amendments are possible but negotiability is not promised. Sources: omnifact:omnifact:dpa, omnifact:omnifact:dpa-de. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: GDPR is explicit; revised Swiss DSG coverage/addendum and Swiss SCC modifications were not established. Sources: omnifact:omnifact:dpa. - governing_law — Which law and court govern the contract? [supported]: German law and Frankfurt exclusive jurisdiction under Terms18; German legal version prevails. Sources: omnifact:omnifact:terms. - ai_act_materials — Is EU AI Act documentation provided? [partial]: Public AI Act whitepaper and Academy literacy/certification training are advertised; these are not product conformity attestations. Sources: omnifact:omnifact:whitepapers, omnifact:omnifact:pricing. - sector_materials — Are FINMA or other sector materials provided? [partial]: Public-administration, banking and healthcare positioning/private hosting are advertised; actual FINMA/DORA/§203 contract pack was not verified. Sources: omnifact:omnifact:home, omnifact:omnifact:public-sector. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa, omnifact:omnifact:dpa-de, omnifact:omnifact:terms, omnifact:omnifact:whitepapers, omnifact:omnifact:pricing, omnifact:omnifact:home, omnifact:omnifact:public-sector ### 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. #### AnythingLLM Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public ISO27001 certificate verifies platform/Spaces ISMS through 2029-04-06. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - pentest: DPA states annual external pentests with remediation; actual report/period/summary was not verified. - Unverified soc2, c5, other_certifications: No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified. - iso_27001 — ISO 27001 with scope and validity? [supported]: Prescient Security LLC certificate123228 issue1, ISO/IEC27001:2022, issued/certified 2026-04-07, valid until 2029-04-06 subject to surveillance. Covers ISMS supporting Platform/Spaces, data, Azure infrastructure, software, people and procedures; So A1.4 dated 2026-03-30. All in-scope activities conducted remotely. Sources: omnifact:omnifact:iso. - soc2 — SOC 2 type, period and covered service? [unknown]: SOC 2 type, period and covered service? Unknown. No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified. - c5 — BSI C5 attestation? [unknown]: BSI C5 attestation? Unknown. No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified. - other_certifications — Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Unknown. No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified. - report_access — How can customers obtain reports? [supported]: ISO PDF is public and downloadable through Trust Center. Eight AI-provider processing summaries are request-only and were not requested. Sources: omnifact:omnifact:trust. - pentest — Are independent penetration test summaries available? [partial]: DPA states annual external pentests with remediation; actual report/period/summary was not verified. Sources: omnifact:omnifact:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:iso, omnifact:omnifact:trust, omnifact:omnifact:dpa ### 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). #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Private deployment and managed-instance isolation are documented; default encryption of all content and a product key-custody service were not verified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - encryption_at_rest: Is data encrypted at rest? Default encryption-at-rest/transit settings for every database, file, backup and provider route were not verified. - customer_managed_keys: Self-hosted operators control infrastructure/secrets. A product-level BYOK/HYOK content-encryption contract was not established. - tenant_isolation: Managed Cloud describes private isolated AWS instances and resources per customer. This was not independently tested and is separate from source/workspace access control. - encryption_at_rest — Is data encrypted at rest? [unknown]: encryption_at_rest: Is data encrypted at rest? Default encryption-at-rest/transit settings for every database, file, backup and provider route were not verified. - customer_managed_keys — Can the customer manage or hold the keys? [partial]: Self-hosted operators control infrastructure/secrets. A product-level BYOK/HYOK content-encryption contract was not established. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:config. - private_networking — Is private connectivity or IP restriction available? [supported]: Docker can be placed on customer infrastructure; Desktop API listens on loopback unless optional network discovery is enabled. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:desktop. - tenant_isolation — How are customers separated in shared SaaS? [partial]: Managed Cloud describes private isolated AWS instances and resources per customer. This was not independently tested and is separate from source/workspace access control. Sources: anythingllm:anythingllm:cloud-overview. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:config, anythingllm:anythingllm:desktop, anythingllm:anythingllm:cloud-overview #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial AES256/TLS and logical tenant separation are documented; customer-held keys remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - private_networking: Vendor internal services use NSGs/Private Endpoints and NetBird JIT VPN for privileged production access; public app is Cloudflare-fronted. A customer private-link/IP-allowlist option was not established. - Unverified customer_managed_keys: No customer-managed/held encryption-key configuration was established; sovereignty discussion does not establish key-management functionality. - encryption_at_rest — Is data encrypted at rest? [supported]: DPA requires AES256 at rest for Postgre SQL, Blob Storage and other persistent Azure services; HTTPS/TLS in transit. Sources: omnifact:omnifact:dpa. - customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Unknown. No customer-managed/held encryption-key configuration was established; sovereignty discussion does not establish key-management functionality. - private_networking — Is private connectivity or IP restriction available? [partial]: Vendor internal services use NSGs/Private Endpoints and NetBird JIT VPN for privileged production access; public app is Cloudflare-fronted. A customer private-link/IP-allowlist option was not established. Sources: omnifact:omnifact:dpa. - tenant_isolation — How are customers separated in shared SaaS? [supported]: Organization-scoped data/roles, separate production/development/test Azure environments, no customer data in tests. This is logical tenant separation. Sources: omnifact:omnifact:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Local/self-hosted and managed Cloud content-access paths differ. Cloud permits necessary operational team access; a Mintplex staff/sub-processor professional-secrecy undertaking and its plan/add-on terms remain unverified. Availability: unknown Delivery: unknown Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation and managed-service terms retrieved 2026-10-21; this row does not infer contract terms from the source-code licence; plan=Mixed modes identified per answer: Docker/Desktop on customer infrastructure; Basic/Pro managed Cloud dedicated AWS instance; Enterprise custom services checked separately; add_ons=none stated; deployment_mode=not specified; region=Customer-selected Docker/Desktop location; managed Cloud AWS country and provider/support staff locations unverified; no DE/CH secrecy-contract variant established; os=not specified. Limitations: - The secrecy undertaking, sub-processor coverage, offering and professional-secrecy-specific documentation remain unknown. - content_access: Exact Cloud staff/sub-processor plain-text access, provider human access and deployment-specific operator grants remain unverified. - 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]: No § 203 StGB / Art. 321 StGB or equivalent professional-secrecy undertaking binding Mintplex staff was obtained from the reviewed Cloud terms/privacy, Desktop privacy, pricing and product documentation. Generic privacy commitments are not recorded as that undertaking. Sources: anythingllm:anythingllm:terms-cloud, anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:privacy-desktop. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The Cloud policy names AWS, Stripe and PostHog, but no professional-secrecy undertaking extending to covered sub-processors and their personnel was obtained. Customer-selected model/tool services require separate terms; coverage of their staff remains unknown. Sources: anythingllm:anythingllm:privacy-cloud. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: The public Basic, Pro and quote-only Enterprise descriptions did not establish a professional-secrecy package, paid add-on, plan entitlement or price. Availability under a separately negotiated Enterprise agreement remains unknown; no sales contact was made. Sources: anythingllm:anythingllm:cloud. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: Docker data is held on customer-mounted storage; Desktop documents local chat/file storage. Local or external models can be selected. For the separate managed Cloud service, the policy permits necessary Mintplex team instance access for debugging and maintenance and names AWS infrastructure; configured remote models process inference requests. The documents do not establish exactly which plain-text fields operational staff/sub-processors can see or each provider’s human-access permissions. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:privacy-desktop, anythingllm:anythingllm:secrecy-cloud-access, anythingllm:anythingllm:secrecy-model-routing. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Public Cloud terms/privacy, Desktop privacy and setup guides provide general data-handling information. No product-scoped DE/CH secrecy contract template, staff/sub-processor annex or professional-body guidance was located in the reviewed public sources and targeted searches. Sources: anythingllm:anythingllm:terms-cloud, anythingllm:anythingllm:privacy-desktop, anythingllm:anythingllm:secrecy-cloud-access. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:terms-cloud, anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:privacy-desktop, anythingllm:anythingllm:cloud, anythingllm:anythingllm:localdocker, anythingllm:anythingllm:secrecy-cloud-access, anythingllm:anythingllm:secrecy-model-routing #### Omnifact Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ## 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The current public offer page advertises Cloud Basic at $50/month and Pro at $99/month. These are advertised card prices; legacy tier identities, capacities and checkout entitlements are not mapped here. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public offer cards and Desktop Pro documentation retrieved 2026-10-21; no inference of renamed checkout/legacy tier equivalence; plan=MIT self-hosted/core Desktop; advertised Cloud Basic/Pro cards and quote-only Enterprise; optional Desktop Pro is a separate offer; add_ons=none stated; deployment_mode=not specified; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - This claim quotes advertised offer-card prices only; it does not assert that Basic/Pro and Starter/Professional are equivalent SKUs. - Legacy-tier capacity limits are excluded. Current-card capacity, model-credit allowances, ISO currency and Desktop Pro numeric pricing remain unverified. - pricing_unit — What is the pricing unit? [supported]: Self-hosted software has no per-seat MIT licence fee. The current Cloud cards quote a private instance per month; optional Desktop Pro is a separate licence. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cloud-cards-r2, anythingllm:anythingllm:pro. - list_prices — What are list prices per plan, with date and currency? [partial]: As retrieved 2026-10-21, the public Cloud cards advertise Basic $50/month and Pro $99/month; Enterprise requires a quote. The page does not give an ISO currency code. These prices are not mapped to Starter/Professional checkout identifiers; Desktop Pro pricing remains unverified. Sources: anythingllm:anythingllm:cloud-cards-r2, anythingllm:anythingllm:pro-key. - included_usage — What usage is included? [partial]: The Basic card explicitly requires a customer LLM API key. Included model credits, overage tariffs and quantified capacity/entitlements for the current Basic/Pro cards were not established. Legacy limitations-page tier names are not used to infer them. Sources: anythingllm:anythingllm:cloud-cards-r2. - add_ons — Which features cost extra? [partial]: Optional Desktop Pro removes Magic-feature daily limits and document watermarks. Its price and custom Enterprise integration/support prices remain unverified; Cloud Pro is a separate product offer. Sources: anythingllm:anythingllm:pro, anythingllm:anythingllm:cloud-cards-r2. - overage — What do usage beyond limits and premium models cost? [partial]: Customer-selected model/tool accounts incur their own provider charges. No current-card included allowance or AnythingLLM token-overage tariff was verified. Sources: anythingllm:anythingllm:models, anythingllm:anythingllm:cloud-cards-r2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cloud-cards-r2, anythingllm:anythingllm:pro, anythingllm:anythingllm:pro-key, anythingllm:anythingllm:models #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pro costs EUR25/user/month annually up to50users. Its binding credit currency/value and recharge tariff remain unknown; Enterprise Gateway costs are outside this offer. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro hosted workspace up to50users; Enterprise/API Gateway quote and markup excluded; add_ons=Optional Academy separately quoted; Enterprise terms require separate offer; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Pro Chat/Spaces pricing is not mixed with Enterprise Gateway billing. The conflicting credit examples remain a named allowance gap. - pricing_unit — What is the pricing unit? [supported]: Pro uses named seats with monthly or annual billing and pooled premium-model credit; this finding covers the hosted Chat/Spaces subscription. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing. - list_prices — What are list prices per plan, with date and currency? [partial]: Checked2026-10-21: Pro EUR25/user/month billed annually, advertised16% discount versus monthly. Exact monthly rate was not verified. Pro up to50 users; Enterprise custom with unlimited team size. VAT excluded under terms. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms. - included_usage — What usage is included? [partial]: Unknown applicable monetary allowance currency/value for the contract: pricing statesEUR5/user/month while Billing usesUSD5 examples. Pooling, monthly expiry and continued base-tier access subject to fair-use limits are documented, but no definitive currency-denominated allowance is asserted. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing. - add_ons — Which features cost extra? [partial]: Academy training is separately quoted. Enterprise is a separate custom offer adding SSO/SCIM, BYOK/self-hosted models, analytics and custom deployment/SLA. No Enterprise Gateway markup is applied to Pro Chat/Spaces pricing. Sources: omnifact:omnifact:pricing-rev2. - overage — What do usage beyond limits and premium models cost? [partial]: The Pro billing guide directs admins to discuss additional credits; a public recharge tariff was not established. Base-tier chat remains available after included premium credit is used subject to usage limits. Enterprise Gateway billing/markup is outside this Pro finding. Sources: omnifact:omnifact:billing, omnifact:omnifact:pricing-rev2, omnifact:omnifact:limits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing, omnifact:omnifact:terms, omnifact:omnifact:limits, omnifact:omnifact:users, omnifact:omnifact:gateway, omnifact:omnifact:developer ### 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. #### AnythingLLM Verification status: Agent cross-checked (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 source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=Analyst-selected direct OpenAI API proxy, not a bundled model, Assumed operations staffing; optional commercial services excluded; deployment_mode=customer-cloud; region=Azure Switzerland North for the reference application infrastructure; standard OpenAI API inference has no Swiss/EU residency assumption; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21 are analyst inputs, not vendor sizing or an uptime promise. - The budget is a floor because named infrastructure and service costs are unpriced. - cost_200 — Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 200 users, 12 months excluding VAT: from CHF 34778.28 / EUR 37651.06 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 4749.26, operations CHF 30000.00, and BYO model usage USD 475.20. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cost-vm, anythingllm:anythingllm:cost-pg, anythingllm:anythingllm:cost-fx, anythingllm:anythingllm:cost-model, anythingllm:anythingllm:cost-effort. - cost_1000 — Year-one cost at 1,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 1,000 users, 12 months excluding VAT: from CHF 88600.40 / EUR 95919.02 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 12605.23, operations CHF 75000.00, and BYO model usage USD 2376.00. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cost-vm, anythingllm:anythingllm:cost-pg, anythingllm:anythingllm:cost-fx, anythingllm:anythingllm:cost-model, anythingllm:anythingllm:cost-effort. - cost_5000 — Year-one cost at 5,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 5,000 users, 12 months excluding VAT: from CHF 189541.24 / EUR 205197.83 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 32214.49, operations CHF 150000.00, and BYO model usage USD 11880.00. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cost-vm, anythingllm:anythingllm:cost-pg, anythingllm:anythingllm:cost-fx, anythingllm:anythingllm:cost-model, anythingllm:anythingllm:cost-effort. - variable_share — Which part depends on usage? [partial]: Shared mix is 60% light at 100, 30% regular at 400 and 10% power at 1,500 messages/user/month, or 330 weighted messages. Each message is 3,000 input and 600 output tokens. Direct BYO proxy is gpt-6-luna, reasoning effort none, Standard short-context uncached rates USD 0.10/0.50 per million input/output tokens. It costs USD 2.376/user/year before optional tools, embedding, caching or regional processing. This proxy is an analyst assumption, not the product default. Sources: anythingllm:anythingllm:cost-model, anythingllm:anythingllm:cost-effort. - unknown_parts — Which costs could not be priced? [partial]: Unpriced additions are file/object storage beyond the assumed 500 GB PostgreSQL storage, VM OS/data disks, backup excess, egress/load balancers, Redis or additional database services, high availability, embeddings, OCR, search, audio/images, integration work and optional commercial services. The shared PostgreSQL reference budget is not AnythingLLM’s default storage architecture; application/vector storage, extra services and capacity validation remain unpriced. Paid Desktop Pro, managed Cloud and Enterprise are excluded from this self-hosted scenario. The shared VM/PG sizes have not been load-tested and do not replace each product’s documented runtime dependencies. Sources: anythingllm:anythingllm:cost-vm, anythingllm:anythingllm:cost-pg, anythingllm:anythingllm:license. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cost-vm, anythingllm:anythingllm:cost-pg, anythingllm:anythingllm:cost-fx, anythingllm:anythingllm:cost-model, anythingllm:anythingllm:cost-effort #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared v1.4 costs remain unknown for200/1000/5000 users because all exceed the50-seat Pro cap. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. - ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. - cost_200 — Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown for 200 users:Pro caps50 users,so Enterprise licence,allowance and deployment/support quote are required. No quote requested; do not extrapolate EUR25 Pro rate. ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx. - cost_1000 — Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown for 1000 users:Pro caps50 users,so Enterprise licence,allowance and deployment/support quote are required. No quote requested; do not extrapolate EUR25 Pro rate. ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx. - cost_5000 — Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown for 5000 users:Pro caps50 users,so Enterprise licence,allowance and deployment/support quote are required. No quote requested; do not extrapolate EUR25 Pro rate. ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx. - variable_share — Which part depends on usage? [partial]: Enterprise base,pooled credit allowance,model/route rates,additional credits and Gateway markup are unknown. Quote base plus usage beyond included credit plus deployment/services; convert known EUR components at0.9237 CHF/EUR. No substitute vendor tariff/model assumed. Sources: omnifact:omnifact:pricing, omnifact:omnifact:gateway, omnifact:omnifact:billing, omnifact:omnifact:ecb-fx. - unknown_parts — Which costs could not be priced? [supported]: Enterprise seat/volume rate,minimum spend,credit allowance,recharge tariff,model/route rates,Gateway markup percentage,private hosting and Academy service fees are unknown. Sources: omnifact:omnifact:pricing, omnifact:omnifact:gateway, omnifact:omnifact:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx, omnifact:omnifact:gateway, omnifact:omnifact:billing ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Self-installation and free Desktop permit evaluation without sales; managed Cloud offers paid self-serve instance checkout. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - self_serve_trial: Free self-install has no software trial clock/card requirement. Cloud has paid self-serve signup links, but a free business Cloud trial and its card/duration terms were not established. - trial_scope: Docker self-install includes standard multi-user administration and workspace knowledge; Enterprise SSO/custom service scope is quote-only and Cloud excludes MCP/custom Agents. - sales_gate: Standard self-install and paid public Cloud tiers have self-serve paths. Custom Enterprise services require a quote; no vendor was contacted. - free_tier — Is there a free tier for business use? [supported]: MIT self-hosting and the core Desktop download are free; Magic features have a free allowance with optional Desktop Pro. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:desktop, anythingllm:anythingllm:pro. - self_serve_trial — Is a self-serve business trial available? [partial]: Free self-install has no software trial clock/card requirement. Cloud has paid self-serve signup links, but a free business Cloud trial and its card/duration terms were not established. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:cloud. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Docker self-install includes standard multi-user administration and workspace knowledge; Enterprise SSO/custom service scope is quote-only and Cloud excludes MCP/custom Agents. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:cloud, anythingllm:anythingllm:cloud-limits. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Standard self-install and paid public Cloud tiers have self-serve paths. Custom Enterprise services require a quote; no vendor was contacted. Sources: anythingllm:anythingllm:cloud, anythingllm:anythingllm:localdocker. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:desktop, anythingllm:anythingllm:pro, anythingllm:anythingllm:localdocker, anythingllm:anythingllm:cloud, anythingllm:anythingllm:security, anythingllm:anythingllm:cloud-limits #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Ten-day no-card Pro trial is self-serve; enterprise setup is gated. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - free_tier: Time-limited free trial; billing requires a paid subscription afterward. No permanent business free tier established. - trial_scope: Pro chat, Spaces, Privacy Filter and platform access advertised; terms call trial scope limited. Enterprise SSO/SCIM/BYOK/private deployment and support-enabled APIs are not established trial entitlements. - sales_gate: Base Pro trial is self-serve; Enterprise quotes, SSO and advanced API activation require vendor interaction. No vendor contact was made. - free_tier — Is there a free tier for business use? [partial]: Time-limited free trial; billing requires a paid subscription afterward. No permanent business free tier established. Sources: omnifact:omnifact:pricing, omnifact:omnifact:billing. - self_serve_trial — Is a self-serve business trial available? [supported]: Ten-day trial, no credit card, teams up to50 users via account signup. Sources: omnifact:omnifact:pricing. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Pro chat, Spaces, Privacy Filter and platform access advertised; terms call trial scope limited. Enterprise SSO/SCIM/BYOK/private deployment and support-enabled APIs are not established trial entitlements. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms, omnifact:omnifact:developer. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Base Pro trial is self-serve; Enterprise quotes, SSO and advanced API activation require vendor interaction. No vendor contact was made. Sources: omnifact:omnifact:pricing, omnifact:omnifact:users, omnifact:omnifact:developer. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:billing, omnifact:omnifact:terms, omnifact:omnifact:developer, omnifact:omnifact:users ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The self-hosted MIT grant has no seat commitment; Cloud publishes monthly prices and cancellation terms, with immediate deletion. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - minimum_commitment: The MIT grant has no user-count minimum; Cloud per-instance pricing lists no numeric seat floor. Enterprise minima were not established. - local_invoicing: Can it be invoiced in CHF or EUR from a European entity? CHF/EUR billing from a European contracting entity and Enterprise-specific renewal/price-change terms were not established. - transparency_class: Self-host licensing and Cloud Basic/Pro headlines are disclosed. Enterprise service scope, Desktop Pro tariff and full all-in provider spend are only partially specified or unknown. - minimum_commitment — What seat or spend minimum applies? [partial]: The MIT grant has no user-count minimum; Cloud per-instance pricing lists no numeric seat floor. Enterprise minima were not established. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cloud. - contract_length — What contract lengths are offered? [supported]: Cloud Basic/Pro are listed monthly; MIT software use has no subscription term. Sources: anythingllm:anythingllm:cloud, anythingllm:anythingllm:license. - cancellation — How can the contract be cancelled or reduced? [supported]: Cloud can be cancelled via the dashboard or email under the generic terms, with immediate non-recoverable deletion and a stated prorated-current-cycle refund provision. Self-hosted service contracts are separate. Sources: anythingllm:anythingllm:terms-cloud, anythingllm:anythingllm:privacy-cloud. - 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? CHF/EUR billing from a European contracting entity and Enterprise-specific renewal/price-change terms were not established. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: Self-host licensing and Cloud Basic/Pro headlines are disclosed. Enterprise service scope, Desktop Pro tariff and full all-in provider spend are only partially specified or unknown. Sources: anythingllm:anythingllm:cloud, anythingllm:anythingllm:pro-key, anythingllm:anythingllm:license. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cloud, anythingllm:anythingllm:terms-cloud, anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:pro-key #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pro monthly/annual terms are public; Enterprise minimum and CHF invoicing are unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - minimum_commitment: Pro maximum 50 users, Enterprise no team-size cap; public Enterprise minimum seat/spend and private-deployment minimum not established. - local_invoicing: Omnifact Gmb H Frankfurt invoices EUR public prices, supports invoice/SEPA and payment within 14 days. CHF billing not established. - transparency_class: Partial: public Pro price/credits/team cap but Enterprise, deployment, additional credits and services quote-only; Gateway markup not quantified. - minimum_commitment — What seat or spend minimum applies? [partial]: Pro maximum 50 users, Enterprise no team-size cap; public Enterprise minimum seat/spend and private-deployment minimum not established. Sources: omnifact:omnifact:pricing. - contract_length — What contract lengths are offered? [supported]: Monthly/annual terms; Enterprise flexible agreement. Annual renews yearly, monthly renews monthly. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms. - cancellation — How can the contract be cancelled or reduced? [supported]: Annual notice three months before term end; monthly cancel for following month; text/email accepted. Seat removal gives prorated credit on next invoice per billing doc. Sources: omnifact:omnifact:terms, omnifact:omnifact:billing. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: Omnifact Gmb H Frankfurt invoices EUR public prices, supports invoice/SEPA and payment within 14 days. CHF billing not established. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms, omnifact:omnifact:imprint. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: Partial: public Pro price/credits/team cap but Enterprise, deployment, additional credits and services quote-only; Gateway markup not quantified. Sources: omnifact:omnifact:pricing, omnifact:omnifact:gateway. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms, omnifact:omnifact:billing, omnifact:omnifact:imprint, omnifact:omnifact:gateway ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The pinned main repository is MIT. Paid hosted/Desktop entitlements must be distinguished from that source licence. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - enterprise_features_closed: Cloud Enterprise and Desktop Pro add commercial services/entitlements. Whether particular enterprise-only implementations are closed or separately licensed was not established from the main MIT file. - licence_type — Which licence applies to each component? [supported]: The pinned main client/server repository at v1.18.0 uses MIT. Mobile, browser extension and optional paid-service components require their own component licence review. Sources: anythingllm:anythingllm:license. - branding_restrictions — Do licence terms restrict branding or user counts? [supported]: MIT requires notice preservation but has no UI-branding or user-count clause. Optional Desktop Pro removes watermarks from generated documents; that is a paid feature entitlement, not a restriction in the main MIT source licence. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:pro. - enterprise_features_closed — Are enterprise features in a separate closed edition? [partial]: Cloud Enterprise and Desktop Pro add commercial services/entitlements. Whether particular enterprise-only implementations are closed or separately licensed was not established from the main MIT file. Sources: anythingllm:anythingllm:cloud, anythingllm:anythingllm:pro, anythingllm:anythingllm:license. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:pro, anythingllm:anythingllm:cloud #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Platform is proprietary; four inspected public integration/client components have MIT licences. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync, Omnifact example embeddable widget; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise hosted licence; separately MIT-licensed client/integration tools at pinned revisions; API enablement required; add_ons=Customer-run CLI/widget tools; Published Spaces/API access and resource permissions as needed; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Client/integration capabilities are documented in pinned README/licence files, not implementation-inspected or tested; they do not license the hosted platform. - licence_type — Which licence applies to each component? [supported]: Terms grant contract-term nontransferable/non-sublicensable software use; platform source excluded unless expressly agreed. CLI, widget, n8n nodes and XWiki sync carry MIT licences at pinned commits; these do not license the hosted platform. Sources: omnifact:omnifact:terms, omnifact:omnifact:cli-licence-rev2, omnifact:omnifact:widget-licence-rev2, omnifact:omnifact:n8n-nodes-omnifact-licence-rev2, omnifact:omnifact:xwiki-sync-licence-rev2. - branding_restrictions — Do licence terms restrict branding or user counts? [partial]: Platform use limited to agreed user count/own business personnel. Widget can theme colors/title under MIT notice obligations; MIT integrations do not impose seat limits. Platform branding-removal rules were not fully established. Sources: omnifact:omnifact:terms, omnifact:omnifact:widget-rev2, omnifact:omnifact:widget-licence-rev2. - enterprise_features_closed — Are enterprise features in a separate closed edition? [partial]: Enterprise is a commercial feature/deployment tier; no open-core platform edition was established. Source may be included by separate agreement under terms3.3. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:terms, omnifact:omnifact:cli-licence-rev2, omnifact:omnifact:widget-licence-rev2, omnifact:omnifact:n8n-nodes-omnifact-licence-rev2, omnifact:omnifact:xwiki-sync-licence-rev2, omnifact:omnifact:widget-rev2, omnifact:omnifact:pricing-rev2 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Authorized accounts can export chat logs; a complete assistant/knowledge exit fixture was not run. Cloud cancellation leaves no recovery window. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - assistant_export: Can assistants and prompts be exported in a reusable format? No reusable complete assistant/prompt export, knowledge/source fidelity export or admin leaver/exit fixture was verified. Export Cloud data before cancellation under its current terms. - knowledge_export: Can knowledge bases and their sources be exported? No reusable complete assistant/prompt export, knowledge/source fidelity export or admin leaver/exit fixture was verified. Export Cloud data before cancellation under its current terms. - chat_export — Can admins export all chats? [supported]: Permissioned exports cover workspace/user chat logs in CSV, JSON, Alpaca JSON or OpenAI-style JSONL once at least ten logs exist. No all-organization export fixture was run. Sources: anythingllm:anythingllm:logs. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: assistant_export: Can assistants and prompts be exported in a reusable format? No reusable complete assistant/prompt export, knowledge/source fidelity export or admin leaver/exit fixture was verified. Export Cloud data before cancellation under its current terms. - knowledge_export — Can knowledge bases and their sources be exported? [unknown]: knowledge_export: Can knowledge bases and their sources be exported? No reusable complete assistant/prompt export, knowledge/source fidelity export or admin leaver/exit fixture was verified. Export Cloud data before cancellation under its current terms. - export_format — Are formats documented and machine-readable? [supported]: Documented chat-log formats are machine-readable. This does not establish complete source-file, assistant or index portability. Sources: anythingllm:anythingllm:logs. - post_termination_window — How long can data be retrieved after termination? [supported]: Managed Cloud policy states permanent unrecoverable data deletion at cancellation/nonpayment/termination, so no post-termination retrieval window is promised. Self-hosted data remains under operator control. Sources: anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:terms-cloud. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:logs, anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:terms-cloud #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA promises data handover; documented APIs do not establish a complete workspace export. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync, Omnifact example embeddable widget; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise hosted licence; separately MIT-licensed client/integration tools at pinned revisions; API enablement required; add_ons=Customer-run CLI/widget tools; Published Spaces/API access and resource permissions as needed; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Client/integration capabilities are documented in pinned README/licence files, not implementation-inspected or tested; they do not license the hosted platform. - chat_export — Can admins export all chats? [unknown]: Can admins export all chats? Unknown. No admin export-all-chats or reusable complete Space/agent/prompt export was established. No exit fixture was run. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unknown. No admin export-all-chats or reusable complete Space/agent/prompt export was established. No exit fixture was run. - knowledge_export — Can knowledge bases and their sources be exported? [partial]: Documents API/CLI list metadata and manage Space files, while native generated files download. Full original-source, index and ACL export bundle was not established. Sources: omnifact:omnifact:api-docs, omnifact:omnifact:cli-rev2, omnifact:omnifact:documents. - export_format — Are formats documented and machine-readable? [partial]: Document metadata via JSON; native outputs DOCX/XLSX/PPTX and chart images. Widget stores only its own conversation in browser local Storage; this is not an admin export of platform chats. Sources: omnifact:omnifact:api-docs, omnifact:omnifact:documents, omnifact:omnifact:widget-rev2. - post_termination_window — How long can data be retrieved after termination? [partial]: DPA9.2 requires handover or approved destruction at completion/end; no guaranteed post-termination self-service download window specified. TOM gives30-day support organization deletion. Sources: omnifact:omnifact:dpa-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:api-docs, omnifact:omnifact:cli-rev2, omnifact:omnifact:documents, omnifact:omnifact:widget-rev2, omnifact:omnifact:dpa-rev2 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public community/team support routes and the generic managed Cloud no-offline-credit terms are documented. No bespoke Enterprise SLA or Pro response-time entitlement is established by this claim. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Cloud managed instance; version=Public support guide and generic Cloud terms (last updated 2024-07-01) retrieved 2026-10-21; plan=Self-hosted community/team support and managed Cloud under the published generic terms only; separately negotiated Enterprise SLAs and advertised Pro response terms are outside verified contractual scope; add_ons=none stated; deployment_mode=not specified; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - Generic Cloud contract facts are not extended to a bespoke Enterprise agreement. - Advertised support timing is excluded from contractual uptime/compensation findings. - Support languages, hours, regional staffing and a status history remain unverified. - support_channels — Which support channels are available on each plan? [supported]: The public guide lists GitHub issues, team email and community Discord, recommending GitHub/email for direct team assistance. These channels do not establish contracted response hours. Sources: anythingllm:anythingllm:support-r2. - support_languages — Is support available in German, French or Italian? [unknown]: Contracted German, French or Italian support coverage, service hours and time zones were not established in the scoped guide and generic terms. - regional_presence — Is there a DACH or Swiss entity, team or partner? [unknown]: A CH/DACH support entity, staffed local presence or named support partner was not verified from these sources. - uptime_sla — Is there an uptime SLA with credits? [partial]: The generic managed Cloud terms deny refunds/credits for an offline instance and do not establish an uptime percentage/credit schedule. This is a finding about those generic terms only; no executed Enterprise override or contractual definition of advertised Pro support timing was reviewed. Sources: anythingllm:anythingllm:cloud-terms-r2. - status_page — Is there a public status page with history? [unknown]: A first-party public service-status page with incident history was not verified in the support/contract sources. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:support-r2, anythingllm:anythingllm:cloud-terms-r2 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pro email support and Enterprise custom support are documented; a single applicable platform uptime SLA remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro published support terms; Enterprise support and negotiated SLA only under its contract; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Network and system availability percentages are not interchangeable. Enterprise SLA terms require the actual contract. - support_channels — Which support channels are available on each plan? [partial]: Pro pricing promises email within 24 hours; terms process M–F usually09–17 and answer within one working day. Enterprise dedicated support/account manager/custom SLA; timezone not specified in terms. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. No verified public incident-history status page or contracted DE/FR/IT support-language matrix was located; status.omnifact.ai did not resolve. - regional_presence — Is there a DACH or Swiss entity, team or partner? [partial]: Omnifact Gmb H Frankfurt, Germany; pricing also mentions German and US service teams. No Swiss entity established. Sources: omnifact:omnifact:imprint, omnifact:omnifact:pricing-rev2. - uptime_sla — Is there an uptime SLA with credits? [unknown]: Unknown applicable end-to-end service guarantee. Terms7.3 specify99.5% annual pure-network availability while DPA TOM states99.9% system availability, and Enterprise offers a custom SLA. No order-form/service mapping or fixed credit schedule was retrieved, so no single platform SLA is asserted. - status_page — Is there a public status page with history? [unknown]: Is there a public status page with history? Unknown. No verified public incident-history status page or contracted DE/FR/IT support-language matrix was located; status.omnifact.ai did not resolve. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms, omnifact:omnifact:imprint, omnifact:omnifact:dpa-rev2 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public setup/skill tutorials are available and Enterprise advertises custom services; a priced workforce adoption package was not verified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - onboarding_service: Is guided onboarding included? No included guided rollout, DE/FR/IT end-user training, champion programme or change-management package was verified. - user_training: Is end-user training offered, in which languages? No included guided rollout, DE/FR/IT end-user training, champion programme or change-management package was verified. - use_case_library: Public Agent Flow, SQL, mail, document-generation and meeting guides provide use-case examples. A formal role-based workforce curriculum was not established. - adoption_programme: Is there a champion or adoption programme? No included guided rollout, DE/FR/IT end-user training, champion programme or change-management package was verified. - service_cost: Enterprise premium service/custom integrations/on-premise support are quote-only. Included rollout/training deliverables and prices were not established. - onboarding_service — Is guided onboarding included? [unknown]: onboarding_service: Is guided onboarding included? No included guided rollout, DE/FR/IT end-user training, champion programme or change-management package was verified. - user_training — Is end-user training offered, in which languages? [unknown]: user_training: Is end-user training offered, in which languages? No included guided rollout, DE/FR/IT end-user training, champion programme or change-management package was verified. - use_case_library — Are role-based use cases and templates provided? [partial]: Public Agent Flow, SQL, mail, document-generation and meeting guides provide use-case examples. A formal role-based workforce curriculum was not established. Sources: anythingllm:anythingllm:flow, anythingllm:anythingllm:docgen, anythingllm:anythingllm:meeting, anythingllm:anythingllm:sql. - adoption_programme — Is there a champion or adoption programme? [unknown]: adoption_programme: Is there a champion or adoption programme? No included guided rollout, DE/FR/IT end-user training, champion programme or change-management package was verified. - service_cost — Which services cost extra? [partial]: Enterprise premium service/custom integrations/on-premise support are quote-only. Included rollout/training deliverables and prices were not established. Sources: anythingllm:anythingllm:cloud. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:flow, anythingllm:anythingllm:docgen, anythingllm:anythingllm:meeting, anythingllm:anythingllm:sql, anythingllm:anythingllm:cloud #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pro has learning material/webinar; Enterprise workshops and Academy are tailored. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - user_training: Academy offers foundational/advanced courses, individual training and certificate options supporting AI literacy; complete delivery-language/volume entitlement not published. - adoption_programme: Enterprise rollout/admin enablement/use-case workshops and Academy strategy/governance workshops advertised; a formal champion programme was not established. - service_cost: Academy/additional training separately quoted; terms3.6 generally make installations, instruction/training chargeable under separate agreement. - onboarding_service — Is guided onboarding included? [supported]: Pro onboarding documentation/e-learning and webinar; Enterprise custom onboarding/use-case workshops and account manager. Sources: omnifact:omnifact:pricing. - user_training — Is end-user training offered, in which languages? [partial]: Academy offers foundational/advanced courses, individual training and certificate options supporting AI literacy; complete delivery-language/volume entitlement not published. Sources: omnifact:omnifact:pricing. - use_case_library — Are role-based use cases and templates provided? [supported]: Space Starter templates include content creation, knowledge queries, professional development; release notes add meeting-minutes/mail-triage/helpdesk template previews. Sources: omnifact:omnifact:create, omnifact:omnifact:changes. - adoption_programme — Is there a champion or adoption programme? [partial]: Enterprise rollout/admin enablement/use-case workshops and Academy strategy/governance workshops advertised; a formal champion programme was not established. Sources: omnifact:omnifact:home, omnifact:omnifact:pricing. - service_cost — Which services cost extra? [partial]: Academy/additional training separately quoted; terms3.6 generally make installations, instruction/training chargeable under separate agreement. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:create, omnifact:omnifact:changes, omnifact:omnifact:home, omnifact:omnifact:terms ## Sources ### anythingllm:anythingllm:models Language models. The product documents multiple cloud and local provider integrations, with selected models supplied by the connected account/server. - URL: https://docs.anythingllm.com/features/language-models - Locator: Supported local/cloud providers - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:llmconfig LLM configuration. System defaults can be overridden per workspace and separately for agent use. - URL: https://docs.anythingllm.com/setup/llm-configuration/overview - Locator: System, Workspace and Agent LLMs - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:built-in Built-in local model engine. Desktop is moving its built-in engine from Ollama to Lemonade/llama.cpp; current Docker documentation describes opt-in local inference on images after v1.18.0. - URL: https://docs.anythingllm.com/setup/llm-configuration/local/built-in - Locator: Lemonade/llama.cpp; Desktop migration; Docker opt-in - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:router Model Router. Self-hosted and Desktop installations can route messages by ordered calculated or model-classified rules, with a fallback provider/model. - URL: https://docs.anythingllm.com/model-router/overview - Locator: Availability; rule types; fallback - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:constants-pin AnythingLLM file converter registration. The pinned collector registers PDF, DOCX, PPTX, XLSX, EPUB, text, image and audio converters; legacy DOC is commented out. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/collector/utils/constants.js - Locator: collector/utils/constants.js, accepted MIME and converter maps - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: collector/utils/constants.js ### omnifact:omnifact:models Models: All Leading AI Models on One Platform – Omnifact. Current catalogue lists model families, tiers and EU/global region flags. - URL: https://omnifact.ai/models - Locator: OpenAI, Anthropic, Google and Mistral tables - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:select Selecting an AI Model - Omnifact. Manual model picker shows provider/model/region and reasoning effort; browser stores per-model effort. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/model-selection - Locator: Model selector, effort and reasoning trace - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:files Attaching Documents & Images - Omnifact. Attachments have type-specific limits and media bypasses text filtering. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/attaching-documents - Locator: Formats, input limits and privacy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:pricing-rev2 Pricing Plans – Omnifact. Pro is EUR25/user/month annually up to50users. Enterprise adds BYOK/self-hosted models, analytics, SSO and custom SLA. The page is not used to establish an eligible Gateway markup or reconcile conflicting credit examples. - URL: https://omnifact.ai/pricing - Locator: Pro/Enterprise tier table, annual price and credit footnote - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:providers-rev2 Providers - Omnifact. Customer keys, custom OpenAI-compatible endpoints and self-hosted model connections require Enterprise BYOK; managed model access is separate. - URL: https://docs.omnifact.ai/en/platform/team-administration/providers - Locator: Supported Providers and Enterprise-only Bring Your Own Key - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:groups-rev2 Group Management - Omnifact. The Python/code execution tool is explicitly Experimental, has internet access and bypasses the Privacy Filter for sandbox inputs. - URL: https://docs.omnifact.ai/en/platform/team-administration/groups - Locator: Execute code (Experimental), tool controls and security note - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:dpa-rev2 Data Processing Agreement – Omnifact. DPA states return/approved destruction at contract end, distinct support-request deletion within30days, backup schedules and30-day subprocessor-change notice. This does not resolve runtime/plan-specific implementation or a complete current supplier mapping. - URL: https://omnifact.ai/dpa - Locator: Sections6.3,9.2/9.3; Annex3 deletion and backups; Annex4 subprocessor terms - Evidence kind: documented - Source date: 2026-04-21 - Retrieved: 2026-10-21 ### anythingllm:anythingllm:generic Generic OpenAI configuration. Operators can configure an OpenAI-compatible provider, with endpoint-specific behavior and configuration caveats. - URL: https://docs.anythingllm.com/setup/llm-configuration/cloud/openai-generic - Locator: Compatible API route - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:changelog Desktop v1.18.0 changelog. Desktop v1.18.0 changes the built-in engine from Ollama to Lemonade/llama.cpp and records format/sync fixes. - URL: https://docs.anythingllm.com/changelog/v1.18.0 - Locator: Lemond/Lemonade migration; reasoning controls; fixes - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:releases AnythingLLM v1.18.0 release. The latest retrieved stable GitHub release is v1.18.0, published 2026-10-13. - URL: https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.18.0 - Locator: Release date and change list - Evidence kind: documented - Source date: 2026-10-13 - Retrieved: 2026-10-21 ### omnifact:omnifact:changes Release Notes – Omnifact. Dated release notes through October 20 add models, agents, code, MCP, groups and 2FA. - URL: https://omnifact.ai/release-notes - Locator: October–May2026 and earlier entries - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### omnifact:omnifact:blog Blog – Omnifact. Feature announcements include Gemini4Argon October 13 and integrations October 6. - URL: https://omnifact.ai/blog - Locator: Current dated feature drops - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:azure Azure OpenAI configuration. The Azure route uses the customer Azure subscription and its model access. - URL: https://docs.anythingllm.com/setup/llm-configuration/cloud/azure-openai - Locator: Customer Azure subscription - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:bedrock AWS Bedrock configuration. Bedrock is a separately configured customer cloud-account route. - URL: https://docs.anythingllm.com/setup/llm-configuration/cloud/aws-bedrock - Locator: Credentials and provider settings - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:vertex Google Vertex AI configuration. Vertex uses customer Google Cloud credentials and deployment configuration. - URL: https://docs.anythingllm.com/setup/llm-configuration/cloud/google-vertex - Locator: Service account, project and region - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cloud AnythingLLM Cloud pricing. Current public pricing lists private Cloud Basic at $50/month, Pro at $99/month and quote-only Enterprise with SSO/custom services. - URL: https://anythingllm.com/cloud - Locator: Basic, Pro and Enterprise offer table - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cloud-limits Cloud limitations. Managed Cloud explicitly excludes built-in inference, custom coded Agents and MCP; local/self-hosted capabilities cannot be assumed there. - URL: https://docs.anythingllm.com/cloud/limitations - Locator: No built-in LLM; no custom Agents; no MCP - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:license AnythingLLM v1.18.0 licence. The pinned main repository is MIT licensed with copyright/permission notice preservation and an as-is disclaimer. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/LICENSE - Locator: LICENSE, MIT grant and notice - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:terms Terms of Service – Omnifact. Terms define proprietary rights,99.5% annual network availability, support and cancellation. - URL: https://omnifact.ai/terms - Locator: Sections3/6–8/10–11/14–18 - Evidence kind: documented - Source date: 2024-08-01 - Retrieved: 2026-10-21 ### omnifact:omnifact:providers Providers - Omnifact. Enterprise BYOK supports direct providers, Azure/Vertex and custom OpenAI-compatible endpoints. - URL: https://docs.omnifact.ai/en/platform/team-administration/providers - Locator: Supported Providers, BYOK and connection management - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:model-settings Model Management - Omnifact. Model enablement applies to chat, Published Spaces and Gateway; image defaults and tiers are configurable. - URL: https://docs.omnifact.ai/en/platform/team-administration/models - Locator: Availability, Image Models and Model Providers - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:ollama Ollama configuration. A separately installed Ollama endpoint can provide customer-operated chat inference. - URL: https://docs.anythingllm.com/setup/llm-configuration/local/ollama - Locator: Local provider setup - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:local-embed Built-in embedding provider. The built-in all-MiniLM-L6-v2 embedder runs on CPU and is primarily trained on English; it must first be downloaded. - URL: https://docs.anythingllm.com/setup/embedder-configuration/local/built-in - Locator: CPU model and download - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:embed Embedding models. Retrieval embedding providers are configured separately from chat inference. - URL: https://docs.anythingllm.com/features/embedding-models - Locator: Local and cloud embedding options - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:pricing Pricing Plans – Omnifact. Pro annual EUR25 includes pooled EUR5 monthly AI credits per seat up to50 users; Enterprise and Academy are quoted. - URL: https://omnifact.ai/pricing - Locator: Pro, Enterprise, comparison and footnote1 - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:user-pin AnythingLLM user quota implementation. The pinned user quota counts chats over the preceding 24 hours for non-admin multi-user accounts; null limits and admins are exempt. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/server/models/user.js - Locator: server/models/user.js, canSendChat and dailyMessageLimit validation - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: server/models/user.js ### anythingllm:anythingllm:chat-pin AnythingLLM chat quota enforcement. The pinned chat endpoints abort before generation when a multi-user account reaches its configured 24-hour quota. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/server/endpoints/chat.js - Locator: server/endpoints/chat.js, multiUserMode and canSendChat checks - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: server/endpoints/chat.js ### omnifact:omnifact:dpa Data Processing Agreement – Omnifact. DPA includes Frankfurt infrastructure/TOMs, retention, audit requirements and approved subprocessors. - URL: https://omnifact.ai/dpa - Locator: Sections1/6/9/11, Annex1, TOMs2.1–2.10 and Annex4 - Evidence kind: documented - Source date: 2026-04-21 - Retrieved: 2026-10-21 ### omnifact:omnifact:groups Group Management - Omnifact. Additive groups govern capabilities, model tiers, US routes and filter exemptions; Enterprise SCIM mirrors groups. - URL: https://docs.omnifact.ai/en/platform/team-administration/groups - Locator: Group types, SCIM, permissions and sharing - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:gateway AI Gateway - Omnifact. Enterprise opt-in OpenAI-compatible gateway uses eu/ routing and hard credit enforcement; V1 lacks tools/structured output. - URL: https://docs.omnifact.ai/en/platform/team-administration/ai-gateway - Locator: Prerequisites, EU routes, constraints, billing and errors - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:published Published Spaces - Omnifact. Support-enabled Published Space APIs disable the Privacy Filter and use secret endpoint URLs. - URL: https://docs.omnifact.ai/en/platform/team-administration/published-spaces - Locator: Activation, model management and security - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:chat Introduction to Chats - Omnifact. Chat retains conversations and supports document output, sources and daily message quotas. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/introduction - Locator: Features, quotas and message limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:limits AI Credits and Usage Limits - Omnifact. Exhausted monthly credits fall back in chat; Gateway blocks all calls without base fallback. - URL: https://docs.omnifact.ai/en/guides/troubleshooting/usage-and-credits - Locator: Credit exhaustion and fallback models - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:docchat Documents in chat, current interface. Attachments inject full text while embedded documents are retrieved as chunks and become available to every authorized workspace user. - URL: https://docs.anythingllm.com/chatting-with-documents/introduction - Locator: v1.8.5+; attachment vs embedding; context; workspace scope - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:pdf-pin AnythingLLM PDF extraction implementation. The pinned PDF handler attempts OCR when its initial text loader returns no pages, without establishing scan accuracy. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/collector/processSingleFile/convert/asPDF/index.js - Locator: collector/processSingleFile/convert/asPDF/index.js, no-text fallback - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: collector/processSingleFile/convert/asPDF/index.js ### omnifact:omnifact:documents Document Creation - Omnifact. Isolated Python code creates XLSX/DOCX/PPTX/charts with internet egress and group controls. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/document-creation - Locator: Document types, editing, formulas and sandbox - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:uploads Managing Uploaded Files - Omnifact. Space file pipeline uses Tika OCR, chunking, embeddings and summaries; documents can be deleted permanently. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/managing-uploaded-files - Locator: Processing, deletion and FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:retrieval Uploaded Files Retrieval - Omnifact. Agents retrieve source passages under Space membership and show citations/progress; strict no-answer grounding is instructed. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/uploaded-files-retrieval - Locator: Retrieval and source behavior - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:security Security and access. Docker multi-user roles are Admin, Manager and Default; Default users only chat in explicitly assigned workspaces. - URL: https://docs.anythingllm.com/features/security-and-access - Locator: Docker only; single-user vs multi-user; roles - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:billing Billing & Usage - Omnifact. Billing describes proration, pooled credit and plan changes but uses USD5 examples and5000-page Pro quota. - URL: https://docs.omnifact.ai/en/platform/team-administration/billing - Locator: Seat Management, Monthly Usage Credit and Plan Management - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:spaces What are Spaces? - Omnifact. Spaces persist instructions/knowledge and conversations with shared member access. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/introduction - Locator: Concepts, benefits and examples - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:share Sharing Spaces with Colleagues - Omnifact. Organization users/groups share Spaces; group access is view-only and removal is immediate. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/sharing-spaces - Locator: Roles, group sharing and removal - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:sync Connected Sources - Omnifact. Connected sources index selected Drive/OneDrive/SharePoint folders every five minutes and remove deleted content next cycle. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/connected-sources - Locator: Setup, privacy and FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:sync Automatic document sync preview. Preview sync refreshes watched sources; removing a watched Desktop original leaves existing parsed content and embeddings in place. - URL: https://docs.anythingllm.com/beta-preview/active-features/live-document-sync - Locator: Docker vs Desktop scope; intervals; missing local file - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:mcp MCP compatibility. Self-hosted/desktop MCP supports local stdio and remote SSE/Streamable transports with configured credentials/headers. - URL: https://docs.anythingllm.com/mcp-compatibility/overview - Locator: Configuration file; management UI; transport types - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:outlook Outlook Agent. The single-user Outlook skill uses a customer Entra application and requests approval for mailbox-modifying operations. - URL: https://docs.anythingllm.com/agent/usage/outlook-agent - Locator: Single-user only; delegated scopes; approvals - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:gmail Gmail Agent. The Gmail skill is single-user only and distinguishes read actions from modifying actions requiring approval. - URL: https://docs.anythingllm.com/agent/usage/gmail-agent - Locator: Single-user only; setup; action approvals - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:sql SQL Agent. A configurable SQL Agent can query a separately connected database. - URL: https://docs.anythingllm.com/agent/usage/sql-agent - Locator: Database connection and tool use - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:localdocker Local Docker installation. Self-hosting runs the application in customer-controlled infrastructure and mounted storage. - URL: https://docs.anythingllm.com/installation-docker/local-docker - Locator: Volumes; local network; configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:connectors-pin AnythingLLM connector registration. The pinned UI registers Confluence, repository, website, YouTube, Obsidian and other import connectors; no source ACL test was performed. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/frontend/src/components/Modals/ManageWorkspace/DataConnectors/index.jsx - Locator: frontend/src/components/Modals/ManageWorkspace/DataConnectors/index.jsx - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: frontend/src/components/Modals/ManageWorkspace/DataConnectors/index.jsx ### omnifact:omnifact:integrations Integrations - Omnifact. Curated first-party MCP and document connectors use separate live-versus-indexed access patterns. - URL: https://docs.omnifact.ai/en/platform/team-administration/integrations - Locator: Catalog, integration types and privacy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:directory Integrations: Connect the Tools Your Team Uses – Omnifact. Current catalogue names cloud storage, Google, Atlassian, CRM, design, communications and developer systems. - URL: https://omnifact.ai/integrations/catalog - Locator: Integration cards and custom MCP - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:xwiki-sync-rev2 omnifact-xwiki-sync pinned README. omnifact-xwiki-sync documents incremental XWiki page/attachment ingestion with delete propagation. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-xwiki-sync/blob/599db2ec0c7f28ddb2a22c4a09a9242e5781316b/README.md - Locator: Pinned README.md documentation at commit 599db2ec0c7f28ddb2a22c4a09a9242e5781316b; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-08-25 - Retrieved: 2026-10-21 ### omnifact:omnifact:mcp-rev2 MCP Servers - Omnifact. Tools have Always/Approval/Disable policies; Approval shows the request payload. Documentation conflicts on initial discovery defaults, which remain unknown. - URL: https://docs.omnifact.ai/en/platform/team-administration/mcp-servers - Locator: Per-tool policies, authentication and later tool refresh; initial discovery defaults excluded - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:mcp MCP Servers - Omnifact. Remote MCP has personal OAuth/shared static credentials, per-tool Always/Approval/Disable policies and private-network restrictions. - URL: https://docs.omnifact.ai/en/platform/team-administration/mcp-servers - Locator: Setup, policies, OAuth, approvals and privacy boundaries - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:vector Vector databases. The application supports configurable local and external vector databases rather than a single fixed vendor region. - URL: https://docs.anythingllm.com/features/vector-databases - Locator: Local and cloud storage choices - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:privacy Privacy and data handling. Telemetry is optional; deleting a document from a workspace differs from deleting it from My Documents and all workspaces. - URL: https://docs.anythingllm.com/features/privacy-and-data-handling - Locator: Telemetry; document removal vs full erasure - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:chatmodes Chat modes. Agent mode uses configured tools; Query mode is documented to report when it finds no relevant document information. - URL: https://docs.anythingllm.com/features/chat-modes - Locator: Agent, Chat and Query modes - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:citation-pin AnythingLLM source citation rendering. The pinned client renders citation sources with file/link/provider metadata and source-detail controls. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/frontend/src/components/WorkspaceChat/ChatContainer/ChatHistory/Citation/index.jsx - Locator: frontend/src/components/WorkspaceChat/ChatContainer/ChatHistory/Citation/index.jsx - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: frontend/src/components/WorkspaceChat/ChatContainer/ChatHistory/Citation/index.jsx ### anythingllm:anythingllm:memory Memories and personalization. Admins enable user-scoped workspace/global memory, and users can edit/delete it; selected memories go to the configured model. - URL: https://docs.anythingllm.com/features/memories - Locator: Off by default; user scope; limits; extraction - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:systemprompt System prompt variables. Workspace system prompts can include dynamic user/time context; this does not establish a mandatory organization policy. - URL: https://docs.anythingllm.com/features/system-prompt-variables - Locator: Workspace prompt variables and context - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:account Account Settings - Omnifact. English/German UI and persistent personal context/instructions are documented; personalization is unfiltered. - URL: https://docs.omnifact.ai/en/platform/core-features/account-settings/user-profile-and-personalization - Locator: Language Preferences and Personalization - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:agent-setup Agent setup. Operators configure Agent models and skills per workspace; the setup guide still names DuckDuckGo as the default search engine. - URL: https://docs.anythingllm.com/agent/setup - Locator: Workspace model; enabled skills; search configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:flow Agent Flows. A visual no-code flow editor creates reusable Agent skills; code skills remain a separate developer route. - URL: https://docs.anythingllm.com/agent-flows/overview - Locator: No-code builder; Desktop vs Docker - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:desktop Desktop installation overview. Desktop supports Windows/macOS/Linux, is single-user and exposes only its API when optional LAN discovery is enabled. - URL: https://docs.anythingllm.com/installation-desktop/overview - Locator: OS support; single-player; network discovery - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:users User Management - Omnifact. User roles and Enterprise SSO/SCIM automate lifecycle while locking manual changes. - URL: https://docs.omnifact.ai/en/platform/team-administration/users - Locator: Roles, statuses, lifecycle and SSO/SCIM - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:create Creating New Spaces - Omnifact. Users create custom Space agents with instructions and starter examples. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/creating-spaces - Locator: Space Starters and configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:flow-api Agent Flow API-call block. A flow block calls a configured API and passes its result into later flow steps. - URL: https://docs.anythingllm.com/agent-flows/blocks/api-call - Locator: HTTP action configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:docgen Document generation skill. The enabled built-in skill generates text, PDF, Excel, DOCX and PowerPoint files, with model-dependent results. - URL: https://docs.anythingllm.com/agent/usage/document-generation-agent - Locator: Availability; document types - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:chart Chart generation skill. An Agent chart skill generates charts from prompts and workspace data. - URL: https://docs.anythingllm.com/agent/usage/chart-generation - Locator: Examples and workspace data - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:images Image Generation - Omnifact. Images are generated/edited from references and retained in an Assets gallery. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/image-generation - Locator: Generation, reference images and gallery - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:web Web Search and Browsing - Omnifact. Web search displays citations and blocks queries with masked sensitive values. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/web-search-browsing - Locator: Search, privacy and limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:agent-usage Using agents. Agent sessions use configured skills and tool-capable models. - URL: https://docs.anythingllm.com/agent/usage/overview - Locator: Skills and tool use - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:browsing Agent web browsing. The web-browsing skill searches the internet from an Agent request. - URL: https://docs.anythingllm.com/agent/usage/web-browsing - Locator: Built-in search skill - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:search-configured-r2 AnythingLLM v1.18.0 explicitly configured DuckDuckGo route. At the pinned revision, explicit agent_search_provider=duckduckgo-engine routes queries to the DuckDuckGo HTML search endpoint; this finding makes no default-provider claim. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/server/utils/agents/aibitat/plugins/web-browsing.js - Locator: agent_search_provider lookup; duckduckgo-engine switch case at lines 96-98; _duckDuckGoEngine at lines 1117-1210 - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: server/utils/agents/aibitat/plugins/web-browsing.js ### anythingllm:anythingllm:agent-skills-r2 AnythingLLM Agent skill controls. The setup guide documents skill selection in Settings > Agent Skills and tool toggles from the chat prompt menu. - URL: https://docs.anythingllm.com/agent/setup - Locator: Configure your available skills, excluding the unversioned default-search example - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:job Scheduled Jobs. Recurring Agent jobs are available only in single-user mode, with allowed tools, execution history and generated-file downloads. - URL: https://docs.anythingllm.com/scheduled-jobs/overview - Locator: Single-user restriction; schedules; run traces - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:n8n-nodes-omnifact-rev2 n8n-nodes-omnifact pinned README. n8n-nodes-omnifact documents n8n community nodes for Gateway/chat/documents. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/n8n-nodes-omnifact/blob/7a3947c620206d4e195064421db525aaa4dfb50a/README.md - Locator: Pinned README.md documentation at commit 7a3947c620206d4e195064421db525aaa4dfb50a; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-09-10 - Retrieved: 2026-10-21 ### omnifact:omnifact:api-chat Published Spaces Chat API - Omnifact. Published chat provides JSON/SSE and optional inline sources/agentic workflow headers. - URL: https://docs.omnifact.ai/en/api-reference/published-space-chat - Locator: Headers, responses and SSE events - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:stop Stopping and Regenerating Responses - Omnifact. Send changes to a Stop button during response generation. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/stopping-regenerating-responses - Locator: How to Stop - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:api Developer API. Instance APIs manage workspaces, document embedding and chat; API keys confer access and must be protected. - URL: https://docs.anythingllm.com/features/api - Locator: Instance /api/docs; key management; workspace APIs - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:config Configuration. Simple SSO issues short-lived one-use login links for already-provisioned users through a privileged API key; it is not a native SAML/OIDC protocol implementation. - URL: https://docs.anythingllm.com/configuration - Locator: Simple SSO passthrough; multi-user prerequisites - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:developer Developer Tools - Omnifact. API enablement is gated and organization key regeneration/revocation is centralized. - URL: https://docs.omnifact.ai/en/platform/team-administration/developer-tools - Locator: Activation and API key management - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:api-docs Documents API - Omnifact. Document APIs upload/list/inspect/update/delete Space files asynchronously. - URL: https://docs.omnifact.ai/en/api-reference/documents - Locator: Endpoints and schema examples - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:docker Docker installation overview. Docker provides the shared browser/server deployment with multi-user administration; Desktop is a separate single-user application. - URL: https://docs.anythingllm.com/installation-docker/overview - Locator: Desktop/Docker comparison; server deployment - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:windows Windows installation. Silent installation can support MDM packaging, but all-users installation is explicitly unsupported and Enterprise/Server OS use has caveats. - URL: https://docs.anythingllm.com/installation-desktop/windows - Locator: Current User only; silent install and uninstall - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:ext Browser extension installation. The extension sends pages/selected text into workspaces using an API connection; it does not by itself enforce original web content ACLs. - URL: https://docs.anythingllm.com/browser-extension/install - Locator: Supported browsers; API connection; collected content - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:mobile Mobile overview. A separate Android app runs local models and can pair with Desktop or server instances; iOS is not currently available. - URL: https://docs.anythingllm.com/mobile/overview - Locator: Android only; local models; pairing; feature set - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:meeting-intro Meeting Assistant introduction. Free Desktop meeting recording/transcription is local on Windows/macOS; a selected cloud summary model receives the transcript. - URL: https://docs.anythingllm.com/meeting-assistant/introduction - Locator: Desktop exclusivity; supported OS; privacy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:home AI for the Public Sector & Regulated Industries – Omnifact. Platform offers governed multi-model chat, Spaces, Privacy Filter and private deployment. - URL: https://omnifact.ai/ - Locator: Product, governance and deployment overview - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:pro AnythingLLM Pro overview. Optional Desktop Pro removes daily Magic-feature limits and generated-document watermarks; it is separate from Cloud Pro. - URL: https://docs.anythingllm.com/pro/overview - Locator: Desktop v1.15+; Magic features; document watermarks - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:images Image generation. Configured OpenAI/OpenRouter/Lemonade tools can edit reference images, while the documented Ollama route generates without using references. - URL: https://docs.anythingllm.com/features/image-generation - Locator: Provider table; reference-image editing; /img - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:privacy Data Privacy - Omnifact. Filter defaults on but MCP, code, image/audio paths bypass it; code sandbox has internet egress. - URL: https://docs.omnifact.ai/en/platform/team-administration/data-privacy - Locator: Privacy Filter Control and boundaries - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:tts Text to speech. Read-aloud uses configured local/browser or external TTS engines, depending on the selected provider. - URL: https://docs.anythingllm.com/features/text-to-speech - Locator: Provider engines and configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:stt Transcription models. Audio transcription is a separately configurable provider route. - URL: https://docs.anythingllm.com/features/transcription-models - Locator: Transcription provider overview - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:meeting Meeting Assistant features. The Desktop meeting workflow records/imports audio, identifies speakers, allows transcript corrections and summarizes meetings. - URL: https://docs.anythingllm.com/meeting-assistant/features - Locator: Transcription; speakers; editable text; summaries - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:i18n-pin AnythingLLM locale registration. The pinned frontend registers English, German, French and Italian resources; completeness and naturalness are not established. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/frontend/src/locales/resources.js - Locator: frontend/src/locales/resources.js, English/German/French/Italian imports - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: frontend/src/locales/resources.js ### anythingllm:anythingllm:r4-german-admin AnythingLLM German administrator locale. German locale resources include user/invite/event-log and administrator settings labels. This establishes partial admin localization, not completeness or naturalness. - URL: https://github.com/Mintplex-Labs/anything-llm/blob/9b1fcab141000eaba9f78ed131151de04904454b/frontend/src/locales/de/common.js - Locator: settings users, invites, event-logs and role/admin labels - Evidence kind: source-inspected - Source date: 2026-10-25 - Retrieved: 2026-10-26 - Commit: 9b1fcab141000eaba9f78ed131151de04904454b - Path: frontend/src/locales/de/common.js ### omnifact:omnifact:sso-blog Single Sign-On (SSO) for Enterprise Authentication – Omnifact. Enterprise SAML2.0 supports optional SCIM, Id P policies and disabled email sign-in. - URL: https://omnifact.ai/blog/feature-drop-introducing-sso - Locator: Setup, benefits and changes - Evidence kind: documented - Source date: 2024-11-25 - Retrieved: 2026-10-21 ### omnifact:omnifact:public-sector GDPR-Compliant AI for Public Administration – Omnifact. Public-sector page names Entra/Okta/Keycloak and Germany/municipal on-premise options. - URL: https://omnifact.ai/solutions/public-administration - Locator: SSO, deployment and onboarding - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:auth Authentication - Omnifact. TOTP, recovery codes and account/IP-specific throttling are described. - URL: https://docs.omnifact.ai/en/platform/core-features/account-settings/authentication - Locator: 2FA setup and failure handling - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:security-rev2 Security and Access - Omnifact. SSO/SAML users rely on identity-provider authentication and MFA and do not see native2FA setup. This does not establish nativeTOTP inclusion in a plan. - URL: https://docs.omnifact.ai/en/platform/team-administration/security-and-access - Locator: SSO/SAML identity-provider authentication; native2FA tier not established - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:admin-pin AnythingLLM administrative events. The pinned admin routes record user creation/deletion, invitation and API-key lifecycle events. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/server/endpoints/admin.js - Locator: server/endpoints/admin.js, user, invite and API-key routes - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: server/endpoints/admin.js ### anythingllm:anythingllm:logs Workspace chat logs. Authorized users export workspace/user chat logs in CSV, JSON, Alpaca JSON or JSONL once at least ten logs are available. - URL: https://docs.anythingllm.com/features/chat-logs - Locator: Permissions; export formats; minimum log count - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:event Event logs. The UI records login attempts, messages, setting changes and uploads with user/time details, without a stated immutable retention model. - URL: https://docs.anythingllm.com/features/event-logs - Locator: Events and fields - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:analytics-rev2 Analytics - Omnifact. Enterprise dashboard presents daily active users and messages with date ranges and toggles; export and additional breakdowns are not established. - URL: https://docs.omnifact.ai/en/platform/team-administration/team-analytics - Locator: Analytics heading, date-range selector, summary cards, activity chart; HTTP200 re-read2026-10-21 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:company Company Profile - Omnifact. Company description and business context shape AI responses. - URL: https://docs.omnifact.ai/en/platform/team-administration/company-profile - Locator: Team Description and company identity - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cloud-overview Cloud overview. Mintplex describes each managed customer instance as isolated AWS infrastructure operated and updated by its team. - URL: https://docs.anythingllm.com/cloud/overview - Locator: Private managed instance - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:privacy-cloud Cloud privacy policy. The managed-service policy excludes self-hosting, names AWS/Stripe/PostHog, permits necessary team access and states deletion at cancellation. - URL: https://docs.anythingllm.com/cloud/privacy-policy - Locator: Service scope; AWS; operational access; deletion - Evidence kind: documented - Source date: 2024-07-01 - Retrieved: 2026-10-21 ### anythingllm:anythingllm:storage Desktop storage. Desktop data is stored in an OS-specific local data directory controlled by its user. - URL: https://docs.anythingllm.com/installation-desktop/storage - Locator: Data location and backup - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:vertex EU Data Residency for Claude and Gemini via Google Cloud – Omnifact. Google/Anthropic EU via Google Cloud are advertised with zero retention and EU-only configuration. - URL: https://omnifact.ai/blog/feature-drop-eu-data-residency-vertex-ai - Locator: What is new, compliance and EU model configuration - Evidence kind: vendor-claimed - Source date: 2026-04-01 - Retrieved: 2026-10-21 ### omnifact:omnifact:trust-rev2 https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust. Public register lists Azure DE/NL/SE/IE infrastructure and Cloudflare EU/US edge metadata, plus model-provider routes; it is not a plan-specific processor/data-flow inventory. - URL: https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust - Locator: Public JSON subprocessors, lastUpdatedAt; infrastructure/metadata roles distinguished - Evidence kind: documented - Source date: 2026-10-21 - Retrieved: 2026-10-21 ### anythingllm:anythingllm:pro-key Desktop Pro activation. A purchased Desktop Pro key is periodically validated; free feature allowances remain without a subscription. - URL: https://docs.anythingllm.com/pro/getting-started - Locator: Periodic licence validation; free allowances - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:terms-cloud Cloud terms. Managed-service terms name Mintplex Labs Inc in California, California law, cancellation deletion and no credits for offline service under the generic terms. - URL: https://docs.anythingllm.com/cloud/terms-and-conditions - Locator: Scope; entity; payment; cancellation; offline credits; law - Evidence kind: documented - Source date: 2024-07-01 - Retrieved: 2026-10-21 ### anythingllm:anythingllm:privacy-desktop Desktop privacy policy. The policy describes local Desktop data and optional telemetry; connected external models still need separately scoped data processing. - URL: https://docs.anythingllm.com/installation-desktop/privacy - Locator: Desktop-only scope; telemetry - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:gateway-web AI Gateway: One API for Every Model – Omnifact. Gateway consumes organization budget, does not store payloads and requires ZDR-capable models for strict retention. - URL: https://omnifact.ai/ai-gateway - Locator: Regional routing, budget and governance - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:privacy-intro Why Data Privacy Matters - Omnifact. Vendor explicitly excludes training its own models on customer data and distinguishes EU/self-hosted routes. - URL: https://docs.omnifact.ai/en/platform/core-features/privacy-security/introduction - Locator: Privacy Commitment and FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:imprint Legal Notice – Omnifact. Omnifact Gmb H is registered in Frankfurt, Germany, HRB131357. - URL: https://omnifact.ai/legal-notice - Locator: Company address and register - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:dpa-de Auftragsverarbeitungsvertrag – Omnifact. Binding German DPA confirms region, transfer, retention and processor terms. - URL: https://omnifact.ai/de/dpa - Locator: Anlagen and main agreement - Evidence kind: documented - Source date: 2026-04-21 - Retrieved: 2026-10-21 ### omnifact:omnifact:whitepapers Get Instant Access to our Full Enterprise Whitepaper – Omnifact. Public library includes AI Act, workplace enablement, self-hosting and RAG guides. - URL: https://omnifact.ai/whitepapers - Locator: Whitepaper catalogue - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:trust https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust. Public Trust Center JSON exposes certificate access and named processor locations, including US direct model routes and Cloudflare telemetry. - URL: https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust - Locator: documents, subprocessors and lastUpdatedAt - Evidence kind: documented - Source date: 2026-10-21 - Retrieved: 2026-10-21 ### omnifact:omnifact:iso Omnifact GmbH ISO/IEC27001:2022 official certificate. Certificate123228 issue1 from Prescient Security LLC covers Omnifact Platform/Spaces and Azure ISMS; valid2026-04-07 through 2029-04-06 subject to surveillance. - URL: https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust/documents/bb9dd08f-c61a-48f3-be41-9fbcdf24e9c3/download-url - Locator: Public Trust Center certificate PDF, one page: scope, issuer, issue date and validity - Evidence kind: certificate-verified - Source date: 2026-04-07 - Retrieved: 2026-10-21 - Issuer: Prescient Security LLC - Certificate scope: ISMS supporting Omnifact GmbH, Omnifact Platform and Spaces, associated data, infrastructure, software, personnel and procedures, including Microsoft Azure; SoA1.4 dated2026-03-30. - Valid: 2026-04-07 to 2029-04-06 - Registry: https://trust.omnifact.ai/ ### anythingllm:anythingllm:secrecy-cloud-access AnythingLLM Cloud operational access policy. The managed-only policy permits operational team instance access, names AWS infrastructure and excludes self-hosted deployments; it does not enumerate plain-text field permissions. - URL: https://docs.anythingllm.com/cloud/privacy-policy - Locator: Instance Access and Management; Third-Party Services; Data Storage and Security; policy scope - Evidence kind: documented - Source date: 2024-07-01 - Retrieved: 2026-10-21 ### anythingllm:anythingllm:secrecy-model-routing AnythingLLM local and cloud model routing. System, workspace and agent models can use local or cloud providers; the selected inference path is separate from where the application is hosted. - URL: https://docs.anythingllm.com/setup/llm-configuration/overview - Locator: System LLM; Workspace LLM; Agent LLM; Supported LLM Providers - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cloud-cards-r2 AnythingLLM advertised Cloud plan cards. The current offer page advertises Basic at $50/month and Pro at $99/month, with Enterprise by quote; Basic explicitly asks for an LLM API key. - URL: https://anythingllm.com/cloud - Locator: Basic $50/month, Pro $99/month and quote-only Enterprise cards; Basic BYO LLM key - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cost-vm Azure Retail Prices, Switzerland North Linux VMs. EUR hourly PAYG rates retrieved 2026-10-21 are 0.2226, 0.4453 and 0.8905 for D4s, D8s and D16s v5 respectively. - URL: https://prices.azure.com/api/retail/prices?currencyCode=EUR&%24filter=armRegionName+eq+%27switzerlandnorth%27+and+serviceName+eq+%27Virtual+Machines%27+and+%28armSkuName+eq+%27Standard_D4s_v5%27+or+armSkuName+eq+%27Standard_D8s_v5%27+or+armSkuName+eq+%27Standard_D16s_v5%27%29+and+priceType+eq+%27Consumption%27 - Locator: Consumption; Virtual Machines Dsv5 Series; Standard_D4s_v5/D8s_v5/D16s_v5 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cost-pg Azure Retail Prices, PostgreSQL Flexible Server. 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. - URL: https://prices.azure.com/api/retail/prices?currencyCode=EUR&%24filter=armRegionName+eq+%27switzerlandnorth%27+and+serviceName+eq+%27Azure+Database+for+PostgreSQL%27+and+priceType+eq+%27Consumption%27 - Locator: General Purpose Ddsv5 Series Compute, 2/4/8 vCore; Flex Server Storage - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cost-fx ECB euro reference rate history. The 2026-10-20 reference rates are EUR 1 = USD 1.1215 and CHF 0.9237. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time=2026-10-20; USD and CHF - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cost-model OpenAI API pricing. 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. - URL: https://developers.openai.com/api/docs/pricing - Locator: Standard, short-context gpt-6-luna row - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cost-effort GPT-6 Luna model documentation. The model accepts reasoning effort none, the lowest documented effort, and lists the same standard text-token rates. - URL: https://developers.openai.com/api/docs/models/gpt-6-luna - Locator: Reasoning effort and text-token pricing - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:ecb-fx ECB historical euro reference rates, 20 October 2026. ECB2026-10-20 reference rates:EUR1=USD1.1215=CHF0.9237, implying USD1=EUR0.89166206. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time=2026-10-20, USD and CHF currency entries - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### omnifact:omnifact:widget-rev2 omnifact-widget pinned README. omnifact-widget documents an unsupported demonstration web component with local Storage conversations. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-widget/blob/9d53cadfbfe1bd9a0e31b7da49b74a1dfc2626f2/README.md - Locator: Pinned README.md documentation at commit 9d53cadfbfe1bd9a0e31b7da49b74a1dfc2626f2; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-02-06 - Retrieved: 2026-10-21 ### omnifact:omnifact:cli-licence-rev2 omnifact-cli MIT licence. MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-cli/blob/576aea6a6c0ce195de08a1d2b9b385d18efe3d06/LICENSE - Locator: Pinned LICENSE documentation at commit 576aea6a6c0ce195de08a1d2b9b385d18efe3d06; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-05-12 - Retrieved: 2026-10-21 ### omnifact:omnifact:widget-licence-rev2 omnifact-widget MIT licence. MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-widget/blob/9d53cadfbfe1bd9a0e31b7da49b74a1dfc2626f2/LICENSE - Locator: Pinned LICENSE documentation at commit 9d53cadfbfe1bd9a0e31b7da49b74a1dfc2626f2; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-02-06 - Retrieved: 2026-10-21 ### omnifact:omnifact:n8n-nodes-omnifact-licence-rev2 n8n-nodes-omnifact MIT licence. MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/n8n-nodes-omnifact/blob/7a3947c620206d4e195064421db525aaa4dfb50a/LICENSE - Locator: Pinned LICENSE documentation at commit 7a3947c620206d4e195064421db525aaa4dfb50a; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-09-10 - Retrieved: 2026-10-21 ### omnifact:omnifact:xwiki-sync-licence-rev2 omnifact-xwiki-sync MIT licence. MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-xwiki-sync/blob/599db2ec0c7f28ddb2a22c4a09a9242e5781316b/LICENSE - Locator: Pinned LICENSE documentation at commit 599db2ec0c7f28ddb2a22c4a09a9242e5781316b; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-08-25 - Retrieved: 2026-10-21 ### omnifact:omnifact:cli-rev2 omnifact-cli pinned README. omnifact-cli documents document management and conversational CLI commands. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-cli/blob/576aea6a6c0ce195de08a1d2b9b385d18efe3d06/README.md - Locator: Pinned README.md documentation at commit 576aea6a6c0ce195de08a1d2b9b385d18efe3d06; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-05-12 - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cloud-terms-r2 AnythingLLM generic managed Cloud contract scope. The published generic terms cover managed Cloud, exclude self-hosting and deny offline-service credits; no bespoke Enterprise override was reviewed. - URL: https://docs.anythingllm.com/cloud/terms-and-conditions - Locator: Scope of Agreement; Instance Offline Recovery; last-updated date - Evidence kind: documented - Source date: 2024-07-01 - Retrieved: 2026-10-21 ### anythingllm:anythingllm:support-r2 AnythingLLM public support channels. Public support routes are GitHub, team email and community Discord; the guide recommends GitHub/email for direct team assistance. - URL: https://docs.anythingllm.com/support - Locator: GitHub Issues; team email; Discord Community; direct-assistance note - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21