--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/anythingllm-vs-langdock/" data_url: "https://onaihq.com/compare/agents/anythingllm-vs-langdock/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 Langdock > 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 45 criteria with sourced findings for both products, including 45 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. - Langdock source checks: 2026-10-21 to 2026-10-26. - Canonical HTML: https://onaihq.com/compare/agents/anythingllm-vs-langdock/ - Machine-readable JSON: https://onaihq.com/compare/agents/anythingllm-vs-langdock/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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Curated multi-provider models and a task-complexity Auto mode are documented; catalogue publication is not a tested picker. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - current_models: Published text catalogue: Gemini 3.1 Pro Preview, 3 Flash Preview, 3.5/3.6/3.7/3.8 Flash, 4 Argon; GPT-5/5.1/5.1 Thinking Fast/5.2/5.2 Pro/5.4/5.4 Mini/5.5/5.6 Luna/Sol/Terra/5 Mini/5 Pro, GPT-6 Luna/Sol/Astra, GPT-6.1 Sol, GPT oss 120b; Fable 5/5.1, Haiku 4.5/5.5, Opus 4.5/4.6/4.7/4.8/5/5.5, Sonnet 4.5/4.6/5/5.5; Llama 3.3 70B/4 Maverick; Mistral Large 3/4; DeepSeek v3.1. Plan/admin/region settings can narrow this list; API availability is listed alongside chat, not independently observed. - auto_routing: Auto analyzes the first message and estimates complexity to select a conversation model; exact final model disclosure was not verified. - Unverified multimodal_input: A model-by-model image/audio input matrix and authenticated model picker were not inspected. - providers — Which model providers are available? [supported]: OpenAI, Anthropic, Google, Meta, Mistral and DeepSeek have named current catalogue entries. Sources: langdock:langdock:models. - current_models — Which current models are selectable on this plan? [partial]: Published text catalogue: Gemini 3.1 Pro Preview, 3 Flash Preview, 3.5/3.6/3.7/3.8 Flash, 4 Argon; GPT-5/5.1/5.1 Thinking Fast/5.2/5.2 Pro/5.4/5.4 Mini/5.5/5.6 Luna/Sol/Terra/5 Mini/5 Pro, GPT-6 Luna/Sol/Astra, GPT-6.1 Sol, GPT oss 120b; Fable 5/5.1, Haiku 4.5/5.5, Opus 4.5/4.6/4.7/4.8/5/5.5, Sonnet 4.5/4.6/5/5.5; Llama 3.3 70B/4 Maverick; Mistral Large 3/4; DeepSeek v3.1. Plan/admin/region settings can narrow this list; API availability is listed alongside chat, not independently observed. Sources: langdock:langdock:models. - user_choice — Can users pick the model per chat? [supported]: Per-chat selection and mid-chat switching are documented. Sources: langdock:langdock:model-guide. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [partial]: Auto analyzes the first message and estimates complexity to select a conversation model; exact final model disclosure was not verified. Sources: langdock:langdock:model-guide. - multimodal_input — Which models accept images, audio or files? [unknown]: Which models accept images, audio or files? Unknown. A model-by-model image/audio input matrix and authenticated model picker were not inspected. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:models, langdock:langdock:model-guide ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public dated model additions exist, but release-lag medians and guaranteed retirement notice remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - Unverified release_lag_days, deprecation_notice, version_pinning: No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise 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. No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established. - changelog — Is there a dated public model changelog? [supported]: Changelog includes Gemini 4 Argon on 13 October, Haiku 5.5 on 8 October and GPT-6.1 Sol on 30 September 2026. Sources: langdock:langdock:changes. - deprecation_notice — How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? Unknown. No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established. - version_pinning — Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unknown. No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:changes ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial BYOK supports customer credentials, named cloud providers and custom compatible HTTPS endpoints. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business BYOK and individually contracted Enterprise BYOK; customer provider charges separate; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - Cloud BYOK requires separately configured completion, embedding and image routes; local/private endpoints are not implied by a cloud key. - own_api_keys — Can the customer use its own provider API keys? [supported]: Customer keys can replace managed completion, embedding and image keys; BYOK can be selected at upgrade or enabled later by support. Sources: langdock:langdock:byok. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [supported]: Guides cover customer Azure deployment settings, Google cloud and AWS Bedrock, separately from simple direct provider keys. Sources: langdock:langdock:byok-routes. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [supported]: Manual OpenAI-compatible endpoints include vLLM, LiteLLM, Ollama, TGI and LocalAI. Cloud requires public HTTPS; private/local hostnames are blocked by default. Sources: langdock:langdock:byok-routes. - byo_pricing — Does BYO change the licence price? [partial]: Customer model usage is billed by the customer provider under BYOK. The applicable Business/Enterprise BYOK licence rate is unknown: the public Standard headline and calculator do not reconcile, and the prior hashed asset is not a stable tariff source. No BYOK seat-rate arithmetic is retained. Sources: langdock:langdock:byok, langdock:langdock:billing. - byo_restrictions — Which features stop working with BYO? [supported]: Completion, embeddings and image models must all be configured. Deep Research needs reasoning/fast-reasoning/backbone routes; absent categories leave features non-functional. Sources: langdock:langdock:byok, langdock:langdock:research. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:byok, langdock:langdock:byok-routes, langdock:langdock:billing, langdock:langdock:research ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Self-hosted compatible inference is a documented BYOK route with network and capability requirements. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - self_hosted_embeddings: BYOK requires a configured embedding model for search; custom model setup includes embeddings. A private customer-hosted embedding network path was not independently verified. - feature_parity: Manual setup needs correct image, tool and editor capability flags. Missing embeddings/images or research routes disables their corresponding features; there is no universal parity guarantee. - vendor_hosted_open_models: Catalogue includes Llama, GPT oss, Mistral and DeepSeek; terms identify Azure/Mistral EU routes, with global opt-ins separately described. - self_hosted_chat — Can chat use a customer-hosted model? [supported]: vLLM/Ollama/TGI/LocalAI routes work through OpenAI-compatible HTTPS endpoints, not localhost/private addresses on default SaaS. Sources: langdock:langdock:byok-routes. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [partial]: BYOK requires a configured embedding model for search; custom model setup includes embeddings. A private customer-hosted embedding network path was not independently verified. Sources: langdock:langdock:byok, langdock:langdock:byok-models. - feature_parity — Which features fail with self-hosted models? [partial]: Manual setup needs correct image, tool and editor capability flags. Missing embeddings/images or research routes disables their corresponding features; there is no universal parity guarantee. Sources: langdock:langdock:byok-models, langdock:langdock:research. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [partial]: Catalogue includes Llama, GPT oss, Mistral and DeepSeek; terms identify Azure/Mistral EU routes, with global opt-ins separately described. Sources: langdock:langdock:models, langdock:langdock:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:byok-routes, langdock:langdock:byok, langdock:langdock:byok-models, langdock:langdock:research, langdock:langdock:models, langdock:langdock:terms ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workspace model defaults and usage/fallback behavior are documented; per-group model/data boundaries remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - user_limits: Five-hour session and Monday-reset weekly limits depend on model-priced token consumption; numeric included budget is shown per account, not fully published. Spam protection is 250 messages/3h. Max is five times Standard. - Unverified model_allowlist_by_group, data_bound_models: Group-specific model allowlists and rules binding connectors/knowledge to certain models were not established in model and role documentation; no two-user test was run. - model_allowlist_by_group — Can admins limit models per group? [unknown]: Can admins limit models per group? Unknown. Group-specific model allowlists and rules binding connectors/knowledge to certain models were not established in model and role documentation; no two-user test was run. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [unknown]: Can admins restrict which models receive connector or knowledge content? Unknown. Group-specific model allowlists and rules binding connectors/knowledge to certain models were not established in model and role documentation; no two-user test was run. - default_model — Can admins set the default model? [supported]: Admins set a default across new chats and agents; users can have their own default. Sources: langdock:langdock:workspace. - user_limits — What per-user message or token limits apply, and are they published? [partial]: Five-hour session and Monday-reset weekly limits depend on model-priced token consumption; numeric included budget is shown per account, not fully published. Spam protection is 250 messages/3h. Max is five times Standard. Sources: langdock:langdock:limits, langdock:langdock:pricing. - limit_behaviour — What happens when a limit is reached? [supported]: With no usable extra usage, Cloud falls back to GPT-6 Luna; BYOK/dedicated use configured fallback. Current responses finish, so spend can slightly overshoot. Personal API calls error rather than fall back. Sources: langdock:langdock:extra. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:limits, langdock:langdock:pricing, langdock:langdock:extra ## 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Format/count limits and direct previews differ from semantic search paths. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - spreadsheets: Spreadsheets use direct reading and file tools, not chunk embeddings; source formula/structure accuracy was not fixture-tested. - Unverified ocr: No shared scanned-PDF OCR or multilingual file fixture was uploaded. - formats — Which formats are accepted? [supported]: PDF/Word/PowerPoint and text, Excel/CSV/TSV/Parquet, listed image, audio and video types are documented; Knowledge bases exclude tabular/media. Sources: langdock:langdock:files. - limits — What size and count limits apply per file and chat? [supported]: Web 50 files/message, mobile five; agent 50 files. PDF/Office 256 MB, text 10 MB, tabular 100 MB, images 20 MB; text 8M characters and PDF 5000 pages. Sources: langdock:langdock:files, langdock:langdock:file-count. - ocr — Are scanned PDFs read? [unknown]: Are scanned PDFs read? Unknown. No shared scanned-PDF OCR or multilingual file fixture was uploaded. - spreadsheets — Are Excel tables read with structure intact? [partial]: Spreadsheets use direct reading and file tools, not chunk embeddings; source formula/structure accuracy was not fixture-tested. Sources: langdock:langdock:files, langdock:langdock:retrieval. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [supported]: Small direct files are previewed in full where possible; agent knowledge above 20 documents uses lists/tools. Knowledge-base/synced text uses up to 50 chunks of up to 2000 characters. Sources: langdock:langdock:retrieval. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:files, langdock:langdock:file-count, langdock:langdock: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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: supported Persistent knowledge bases and library folders have separate limits and access roles. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. - persistent_collections — Can users keep document collections across chats? [supported]: Knowledge bases persist for chat, agents, workflows and API use. Sources: langdock:langdock:knowledge. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: Owner/Editor/Viewer roles; share with persons, groups or workspace, subject to workspace-sharing permission. Sources: langdock:langdock:knowledge. - size_limits — What are the collection limits? [supported]: Cloud Knowledge bases support 1000 files, 8M characters/file. Normal folders have 100 files and 250 MB total; dedicated limits are configurable. Sources: langdock:langdock:knowledge, langdock:langdock:file-count. - assistant_binding — Can collections be bound to an assistant? [supported]: Agent Folders attach knowledge bases/library folders/synced folders. Sources: langdock:langdock:agents. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:knowledge, langdock:langdock:file-count, langdock:langdock:agents ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Native tools, daily folder sync and customer MCP/API integrations are distinct routes. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - on_prem_sources: Confluence Data Center and customer API/MCP endpoints can connect; private network access is restricted by default in Cloud, so generic local shares are not established. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [supported]: Directory includes SharePoint, OneDrive, Outlook Email/Calendar and Teams. SharePoint/OneDrive also support indexed folder sync. Sources: langdock:langdock:integrations, langdock:langdock:sync. - google_workspace — Which Google sources are connected? [supported]: Drive, Gmail, Calendar, Docs, Sheets, Slides and Meet are listed; Drive supports folder sync. Sources: langdock:langdock:integrations. - atlassian — Confluence and Jira? [supported]: Confluence Cloud, self-hosted Confluence Data Center and Jira are in the native directory. Sources: langdock:langdock:integrations. - other_systems — Which other business systems? [supported]: Named routes include Salesforce, ServiceNow, HubSpot, Slack, Notion, Airtable, Asana, GitHub, Azure AI Search, Kendra and Databricks; see directory for authentication and actions. Sources: langdock:langdock:integrations. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Confluence Data Center and customer API/MCP endpoints can connect; private network access is restricted by default in Cloud, so generic local shares are not established. Sources: langdock:langdock:integrations, langdock:langdock:mcp. - connector_provider — Who builds and maintains each connector? [supported]: Langdock provides native integrations; customers build custom actions or connect official third-party MCP servers. Sources: langdock:langdock:integrations, langdock:langdock:mcp. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:integrations, langdock:langdock:sync, langdock:langdock:mcp ### KNOW-04: Permission-aware retrieval Judgment rule: Using two test users, verify that a restricted document in the fixture tenant is never cited or summarised for the user without access, including after a permission change. Record whether permissions are enforced at query time by the source system, mirrored into an index, or not enforced. Record the propagation delay of a revocation. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Folder Sync checks each user source access; Purview labels add a separate, qualified control. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - source_permissions_respected: Synced folder retrieval checks the user source rights in real time and requires the user connection. Static shared knowledge follows Langdock sharing instead. No fixture test was run. - sensitivity_labels: Request-enabled policy covers five Microsoft integrations, with exceptions for certain Outlook actions/copy attachments, unlabeled/new labels, custom MCP and uploaded files; saved-policy enforcement is conditional on integration rollout. - Unverified revocation_delay: A two-user restricted-file/revocation test was not run; no measured source-permission revocation latency is asserted. - source_permissions_respected — Are source permissions enforced per user? [partial]: Synced folder retrieval checks the user source rights in real time and requires the user connection. Static shared knowledge follows Langdock sharing instead. No fixture test was run. Sources: langdock:langdock:sync, langdock:langdock:knowledge. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: A copied content index is searched while access is checked live against the source system for synced files. Sources: langdock:langdock:sync. - revocation_delay — How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? Unknown. A two-user restricted-file/revocation test was not run; no measured source-permission revocation latency is asserted. - admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins choose integrations/actions; synced folders scope imported content and labels can exclude documents. Sources: langdock:langdock:actions, langdock:langdock:labels, langdock:langdock:sync. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [partial]: Request-enabled policy covers five Microsoft integrations, with exceptions for certain Outlook actions/copy attachments, unlabeled/new labels, custom MCP and uploaded files; saved-policy enforcement is conditional on integration rollout. Sources: langdock:langdock:labels. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:sync, langdock:langdock:knowledge, langdock:langdock:labels, langdock:langdock:actions ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Folder Sync copies indexed text and refreshes daily, with live access checks and manual refresh. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - deletion_propagation: Daily sync removes source-deleted files; no measured end-to-end deletion delay is available. - index_location: Terms place customer files/embeddings in EU Azure storage, with default Frankfurt hosting. Per-index backup copies are not separately mapped. - live_or_indexed — Is content searched live or copied into an index? [supported]: Folder Sync downloads supported text into an index; spreadsheets remain direct-read files. Other integration actions query source APIs. Sources: langdock:langdock:sync, langdock:langdock:integrations. - sync_interval — How often does an index refresh? [supported]: Daily updates, manual refresh and up to one hour initial sync. Sources: langdock:langdock:sync. - deletion_propagation — How quickly does a deleted document disappear? [partial]: Daily sync removes source-deleted files; no measured end-to-end deletion delay is available. Sources: langdock:langdock:sync. - index_location — Where is indexed content stored? [partial]: Terms place customer files/embeddings in EU Azure storage, with default Frankfurt hosting. Per-index backup copies are not separately mapped. Sources: langdock:langdock:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:sync, langdock:langdock:integrations, langdock:langdock:terms ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Citations are documented; retrieval outcomes remain untested. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - citations: Agent responses cite sources by default; source-access restriction can hide click-through while still using content. - Unverified citation_accuracy, cross_language, no_answer_behaviour, observed_accuracy: No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown. - citations — Are answers linked to specific sources? [partial]: Agent responses cite sources by default; source-access restriction can hide click-through while still using content. Sources: langdock:langdock:agents. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown. - cross_language — Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown. - no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:agents ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: supported Regular-chat instructions and memory have user and workspace controls. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. - custom_instructions — Can users set persistent instructions? [supported]: Personal instructions apply in regular chat; agent/project instructions replace them. Sources: langdock:langdock:account. - cross_chat_memory — Does the product remember facts across chats? [supported]: Regular chats use a personal store of up to 50 memories; projects/agents do not use this memory. Sources: langdock:langdock:memory. - user_memory_controls — Can users view, edit and delete memories? [supported]: Users inspect, edit, delete or disable memories in account settings and can update/forget through chat. Sources: langdock:langdock:memory, langdock:langdock:account. - admin_memory_controls — Can admins turn memory off? [supported]: Memory availability requires workspace and personal enablement. Sources: langdock:langdock:chat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:account, langdock:langdock:memory, langdock:langdock:chat ## 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents combine reusable knowledge and tools with creation/sharing controls. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - sharing_scope: Workspace/group resources and permissioned agent configuration are documented; no fixture was shared. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Agents configure model, instructions, files, folders, integrations, subagents, skills and workflows. Sources: langdock:langdock:agents. - creator_permissions — Can admins limit who creates them? [supported]: System/custom roles and extra permissions control agent creation/sharing. Sources: langdock:langdock:roles. - sharing_scope — Can assistants be shared with users, groups or everyone? [partial]: Workspace/group resources and permissioned agent configuration are documented; no fixture was shared. Sources: langdock:langdock:workspace, langdock:langdock:agents. - catalogue — Is there an internal assistant directory? [supported]: Workspace agent management has All/Unassigned/Verified views. Sources: langdock:langdock:workspace. - prompt_library — Are shared prompt templates available? [supported]: The workspace guide documents group/workspace prompt-library sharing. Sources: langdock:langdock:workspace. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:agents, langdock:langdock:roles, langdock:langdock:workspace ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Remote MCP and custom actions have admin access controls and optional confirmations. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - tool_approval: Admins share integrations/actions by user/group/key, but native core actions cannot be disabled. New MCP tools default to no confirmation; per-tool/agent confirmations can be configured. - builtin_tools — Which tools are built in? [supported]: Search, images, file work, document editor, memory, research and company knowledge are governed tools. Sources: langdock:langdock:chat. - custom_actions — Can admins add API actions? [supported]: Custom API integrations and shareable individual actions are documented. Sources: langdock:langdock:actions. - mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: Streamable HTTP/SSE with OAuth CIMD/DCR/manual PKCE, API key or none; private network URLs blocked by default. Sources: langdock:langdock:mcp. - tool_auth — Do tools act as the user or as a shared account? [supported]: Native integrations use personal OAuth or service credentials per provider; MCP supports user OAuth or API headers. Sources: langdock:langdock:integrations, langdock:langdock:mcp. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins share integrations/actions by user/group/key, but native core actions cannot be disabled. New MCP tools default to no confirmation; per-tool/agent confirmations can be configured. Sources: langdock:langdock:actions, langdock:langdock:mcp, langdock:langdock:changes. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:chat, langdock:langdock:actions, langdock:langdock:mcp, langdock:langdock:integrations, langdock:langdock:changes ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Cited search and public-web Deep Research are available; provider/region details remain incomplete. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - admin_toggle: Workspace admins disable web search and separate agent capabilities. Per-group search-toggle coverage was not established. - Unverified search_provider: Search/crawl provider contracts and query-processing region were not established in the public tool documentation. - web_search — Is web search available? [supported]: Chat tool generates a query and can open URLs; sources are inspectable. Sources: langdock:langdock:web. - admin_toggle — Can admins disable it per organisation or group? [partial]: Workspace admins disable web search and separate agent capabilities. Per-group search-toggle coverage was not established. Sources: langdock:langdock:workspace. - search_provider — Which search provider handles queries, and where? [unknown]: Which search provider handles queries, and where? Unknown. Search/crawl provider contracts and query-processing region were not established in the public tool documentation. - deep_research — Is multi-step research with a report available? [supported]: Regular chat only, public web only, cited PDF reports; standard keys allow 15 researches per rolling 30 days. BYOK needs research models. Sources: langdock:langdock:research. - web_citations — Are web sources cited? [supported]: Search sources link to corresponding paragraphs and Deep Research has activity/source lists. Sources: langdock:langdock:web, langdock:langdock:research. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:web, langdock:langdock:workspace, langdock:langdock:research ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Multi-step workflows support automatic triggers and human review. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=Workflow run package; model usage separately metered; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - builder_audience: Quickstart and conversational Workflow Builder guide non-developers, with code/HTTP nodes for technical users. - workflow_builder — Is there a workflow or chain builder? [supported]: Workflows chain agents, integrations, logic, loops and custom code after workspace activation. Sources: langdock:langdock:workflows. - scheduled_tasks — Can prompts or assistants run on a schedule? [supported]: Schedule triggers are documented for workflows; the public API index also exposes recurring saved tasks. Sources: langdock:langdock:workflows. - event_triggers — Can external events start a workflow? [supported]: Connected-app events, forms and webhooks start runs; dated composable-workflow release supports multiple triggers. Sources: langdock:langdock:workflows, langdock:langdock:changes. - builder_audience — Is building aimed at business users, IT or developers? [partial]: Quickstart and conversational Workflow Builder guide non-developers, with code/HTTP nodes for technical users. Sources: langdock:langdock:workflows. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workflows, langdock:langdock:changes ### 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. #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents execute actions/subagents; workflow and add-in confirmation behavior is explicit. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace, Langdock Excel and Outlook add-ins; version=Public documentation checked 2026-10-26; plan=Business Chat & Agents/Workflows; Outlook add-in for paid plans and trials, enabled by workspace admin; add_ons=Workflow package as needed; compatible Microsoft Outlook/Exchange Online subscription; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - visible_steps: Deep Research shows search/page-read activity; workflows expose run history and nested run links. General agent step-display completeness was not independently observed. - side_effect_confirmation: Configurable per-agent confirmations and workflow action review exist. Newly saved MCP actions default to no confirmation; Office add-ins ask before edits by default. - stop_control: Deep Research has a stop button; general external side effects already committed cannot be inferred reversible. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: Agents can call integrations, subagents and workflows to carry out multiple steps. Sources: langdock:langdock:agents. - visible_steps — Are steps and tool calls shown? [partial]: Deep Research shows search/page-read activity; workflows expose run history and nested run links. General agent step-display completeness was not independently observed. Sources: langdock:langdock:research, langdock:langdock:changes. - side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Web agents can require configured action confirmation; workflow action review is separate. Newly saved MCP actions default to no confirmation. In the Outlook add-in, edits ask by default, users can allow subsequent edits for the chat, and sending requires a requested action plus confirmation. Sources: langdock:langdock:changes, langdock:langdock:hitl, langdock:langdock:mcp, langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace. - stop_control — Can the user stop a running task? [partial]: Deep Research has a stop button; general external side effects already committed cannot be inferred reversible. Sources: langdock:langdock:research. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:agents, langdock:langdock:research, langdock:langdock:changes, langdock:langdock:hitl, langdock:langdock:mcp, langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace, langdock:langdock:outlook-rev2-20261026, langdock:langdock:outlook-admin-20261026, langdock:langdock:pricing-20261026, langdock:langdock:agents-20261026, langdock:langdock:research-20261026, langdock:langdock:changes-20261026, langdock:langdock:hitl-20261026, langdock:langdock:mcp-20261026, langdock:langdock:excel-20261026 ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public APIs include knowledge and agent MCP, with distinct personal/workspace governance boundaries. Availability: generally-available Delivery: native Scope: surfaces=Langdock public APIs and agent MCP server; version=Public documentation checked 2026-10-21; plan=API/Agent/Knowledge scopes; workspace activation may apply; add_ons=Metered API usage; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - api_governance: Personal API keys share member/workspace spend limits and error on exhaustion; workspace API keys and workflow costs use separate limits. - chat_api — Is there an API for chat and assistants? [supported]: Public Completion and Agent APIs use scoped bearer keys. Workspace/personal key access is controlled by admins. Sources: langdock:langdock:workspace. - knowledge_api — Can documents be loaded through an API? [supported]: Knowledge Folder API supports upload/update/delete/retrieve/search with API-key sharing roles. Sources: langdock:langdock:knowledge. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: Personal API keys share member/workspace spend limits and error on exhaustion; workspace API keys and workflow costs use separate limits. Sources: langdock:langdock:billing, langdock:langdock:extra. - mcp_server — Does the product expose itself to other agents over MCP? [supported]: https://api.langdock.com/mcp exposes find_agent/ask_agent/ask_custom_agent under Agent API key scope; dedicated URL differs. Sources: langdock:langdock:mcp-server. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:knowledge, langdock:langdock:billing, langdock:langdock:extra, langdock:langdock:mcp-server ## 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web, desktop and mobile clients are documented, with IT deployment guidance. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace, Langdock Windows/macOS desktop, Langdock iOS/Android; version=Public documentation checked 2026-10-21; plan=Business or contracted Enterprise workspace clients; the same subscription/approved models apply; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=Windows, macOS, iOS, Android. Limitations: - Native-client and SSO parity beyond the documented file limit was not tested. The source is installation guidance, not proof of a paid Enterprise-only client entitlement. - web — Is a full web client available? [supported]: The core platform is a browser workspace. Sources: langdock:langdock:terms. - desktop_apps — Windows and macOS apps? [supported]: Official Windows/macOS downloads use the same workspace and approved models as web. This is documented availability, not a hands-on parity test. Sources: langdock:langdock:desktop-product. - mobile_apps — iOS and Android apps with SSO? [partial]: The vendor publishes iOS/Android clients and official store links. Mobile-specific SSO and managed-access compatibility were not independently tested. Sources: langdock:langdock:mobile-rev2, langdock:langdock:mobile-product. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. A general browser extension and exhaustive mobile/SSO/Intune parity matrix were not established. - managed_deployment — Can IT deploy and configure clients through MDM? [partial]: Windows machine-wide MSIX/Intune and deployment kits are documented. macOS PKG/DMG works with Jamf, Kandji and Intune. These are client installation methods; separate mobile MAM/dedicated entitlements are not established by this finding. Sources: langdock:langdock:desktop-rev2. - client_feature_gaps — Which features are missing on mobile? [partial]: Mobile permits five files per message versus 50 on web; other parity gaps were not tested. Sources: langdock:langdock:file-count. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:desktop-product, langdock:langdock:mobile-rev2, langdock:langdock:mobile-product, langdock:langdock:desktop-rev2, langdock:langdock:file-count ### 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. #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Excel and Outlook add-ins and a Teams bot are documented; broad Office-suite coverage is not inferred. Availability: generally-available Delivery: native Scope: surfaces=Langdock Excel and Outlook add-ins, Langdock Teams bot; version=Public documentation checked 2026-10-26; plan=Business or Enterprise workspace; Outlook available on paid plans/trials, Excel/Teams require workspace-admin enablement; add_ons=Compatible Microsoft licences not priced; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - word_excel_powerpoint: Excel add-in reads/writes workbooks with formulas/charts; no Word or PowerPoint add-in was established. - licence_prerequisites: Excel web/Windows/Mac version matrix and Outlook Exchange Online requirement are explicit; workspace admin access controls apply and extra M365 seat costs were not priced. - Unverified google_workspace_apps: Google in-editor apps were not established; Google content integrations are recorded separately. - word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [partial]: Excel add-in reads/writes workbooks with formulas/charts; no Word or PowerPoint add-in was established. Sources: langdock:langdock:excel. - outlook — Does it work inside Outlook? [supported]: Outlook reads connected mailbox/calendar and edits drafts; sending requires a requested action and confirmation. Exchange Online is required. Sources: langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace. - teams — Is there a Teams app or bot? [supported]: Admin-installed Teams bot supports private chat and collaborative channel mentions. Sources: langdock:langdock:teams, langdock:langdock:teams-20261026. - google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Unknown. Google in-editor apps were not established; Google content integrations are recorded separately. Rechecked 2026-10-26 in Outlook Add-in, Excel Add-in, How to use the Teams Bot. The Teams Markdown guide was retrieved with HTTP 200; Google in-editor app coverage remains undocumented in these sources. - licence_prerequisites — Which licences or consents are needed? [partial]: Excel web/Windows/Mac version matrix and Outlook Exchange Online requirement are explicit; workspace admin access controls apply and extra M365 seat costs were not priced. Sources: langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:teams, langdock:langdock:outlook-marketplace, langdock:langdock:teams-20261026. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace, langdock:langdock:teams, langdock:langdock:outlook-rev2-20261026, langdock:langdock:outlook-admin-20261026, langdock:langdock:pricing-20261026, langdock:langdock:excel-20261026, langdock:langdock:teams-20261026 ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial DeepL integration offers document translation and glossaries; end-to-end layout quality is untested. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - document_translation: Native DeepL integration lists document translation; its supported layout guarantees were not verified in a trial. - glossaries: DeepL integration lists glossary management; full enterprise glossary rollout was not tested. - Unverified formality_and_variants: Formality/de-CH configuration and DE-to-FR/IT layout-preservation fixtures remain unverified. - document_translation — Can whole documents be translated with formatting kept? [partial]: Native DeepL integration lists document translation; its supported layout guarantees were not verified in a trial. Sources: langdock:langdock:integrations. - translation_engine — Which engine translates? [supported]: The dedicated DeepL integration uses the customer DeepL API key; ordinary chat rewriting uses the chosen model. Sources: langdock:langdock:integrations. - glossaries — Are company glossaries supported? [partial]: DeepL integration lists glossary management; full enterprise glossary rollout was not tested. Sources: langdock:langdock:integrations. - formality_and_variants — Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Unknown. Formality/de-CH configuration and DE-to-FR/IT layout-preservation fixtures remain unverified. - writing_tools — Are dedicated rewrite and proofreading tools available? [supported]: DeepL integration includes writing polish; Document Editor supports selected-text and whole-document AI edits. Sources: langdock:langdock:integrations, langdock:langdock:editor. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:integrations, langdock:langdock:editor ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Image generation and model-specific editing are documented with workspace controls. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - image_generation: Image-generation tool invokes a chosen available image model; dated September release names EU GPT-Image 2.5 Flare and Sunburst. - image_editing: The release describes image editing and BYOK model setup has an image-editing capability flag; exhaustive per-model editing limits were not verified. - usage_terms: As between customer/vendor, customer content rights belong to the customer; third-party model terms and rights restrictions remain applicable. - image_generation — Can users generate images, with which models? [partial]: Image-generation tool invokes a chosen available image model; dated September release names EU GPT-Image 2.5 Flare and Sunburst. Sources: langdock:langdock:images, langdock:langdock:changes. - image_editing — Can users edit uploaded images? [partial]: The release describes image editing and BYOK model setup has an image-editing capability flag; exhaustive per-model editing limits were not verified. Sources: langdock:langdock:changes, langdock:langdock:byok-models. - admin_control — Can admins restrict image generation? [supported]: Workspace admins can disable image generation and manage available models. Sources: langdock:langdock:workspace. - usage_terms — What usage rights apply to output? [partial]: As between customer/vendor, customer content rights belong to the customer; third-party model terms and rights restrictions remain applicable. Sources: langdock:langdock:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:images, langdock:langdock:changes, langdock:langdock:byok-models, langdock:langdock:workspace, langdock:langdock:terms ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Audio/meeting-source integrations are documented; live voice and Swiss German remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - read_aloud: ElevenLabs integration offers text-to-speech using a customer API key; this is not a guaranteed native read-aloud control. - meeting_summaries: Google Meet/Zoom and ElevenLabs integrations can retrieve transcripts; source recordings and processing depend on the connected service. No native meeting-bot transcription fixture was run. - Unverified dictation, voice_conversation, swiss_german_speech: Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages. - dictation — Can users dictate prompts? [unknown]: Can users dictate prompts? Unknown. Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages. - read_aloud — Can answers be read aloud? [partial]: ElevenLabs integration offers text-to-speech using a customer API key; this is not a guaranteed native read-aloud control. Sources: langdock:langdock:integrations. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages. - meeting_summaries — Are meetings transcribed and summarised? [partial]: Google Meet/Zoom and ElevenLabs integrations can retrieve transcripts; source recordings and processing depend on the connected service. No native meeting-bot transcription fixture was run. Sources: langdock:langdock:integrations. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:integrations ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial File analysis, charts and editable document generation are documented; execution-location detail is incomplete. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - data_analysis: The data-analysis guide documents spreadsheet metrics/calculations; exact executed-code sandbox/model configuration was not verified. - canvas_editing: Document Editor replaces Canvas; it exports Markdown/Word/PDF but cannot directly edit imported Word/PDF files. - data_analysis — Can it analyse spreadsheets with executed code? [partial]: The data-analysis guide documents spreadsheet metrics/calculations; exact executed-code sandbox/model configuration was not verified. Sources: langdock:langdock:analysis. - charts — Can it produce charts? [supported]: Charts and downloadable chart images are supported in the guide. Sources: langdock:langdock:analysis. - office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: Analysis lists Excel/CSV/Word/PDF/JSON; changelog and agent file templates also describe PowerPoint. Sources: langdock:langdock:analysis, langdock:langdock:changes. - canvas_editing — Is there a document or canvas editor for iterating on output? [partial]: Document Editor replaces Canvas; it exports Markdown/Word/PDF but cannot directly edit imported Word/PDF files. Sources: langdock:langdock:editor. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:analysis, langdock:langdock:changes, langdock:langdock:editor ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared projects expose chats/files, and Teams channels support group interaction. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace, Langdock Teams bot; version=Public documentation checked 2026-10-21; plan=Business/Enterprise workspace sharing; Teams bot requires workspace-admin setup and Microsoft tenant installation; add_ons=Microsoft Teams access; bot installed and permitted by tenant admin; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - Unverified share_permission_boundary: No cross-group source-boundary sharing fixture was run; project sharing does not by itself prove permission-safe redistribution of generated answers. - share_chats — Can chats be shared inside the organisation? [supported]: Workspace chat-link sharing is managed under account shared chats. Sources: langdock:langdock:account. - team_spaces — Are shared projects or workspaces available? [supported]: Projects shared with users/groups include all current and future project chats, files and instructions; cannot share a project to the whole workspace. Sources: langdock:langdock:projects. - group_chat — Can several people chat together with the AI? [supported]: Teams channel threads allow several people to participate with @Langdock. Sources: langdock:langdock:teams. - share_permission_boundary — Does sharing respect the recipient's access to sources? [unknown]: Does sharing respect the recipient's access to sources? Unknown. No cross-group source-boundary sharing fixture was run; project sharing does not by itself prove permission-safe redistribution of generated answers. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:account, langdock:langdock:projects, langdock:langdock:teams ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Five interface languages are documented; quality and accessibility have not been audited. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - Unverified dach_language_quality, accessibility_statement, admin_ui_languages: No authenticated language-quality/admin-translation inspection or WCAG conformance report was established. - ui_languages — Which UI languages are offered? [supported]: English, German, Spanish, French and Italian are listed in Account Preferences. Sources: langdock:langdock: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 authenticated language-quality/admin-translation inspection or WCAG conformance report was established. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No authenticated language-quality/admin-translation inspection or WCAG conformance report was established. - admin_ui_languages — Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. No authenticated language-quality/admin-translation inspection or WCAG conformance report was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock: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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business includes SAML SSO and verified domains; MFA relies on the identity provider. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - mfa: No standalone Langdock MFA; SAML identity provider enforces MFA. - Unverified conditional_access: OIDC/LDAP enterprise options and a tested Entra Conditional Access compatibility matrix were not established. - sso_protocols — Which SSO protocols and identity providers work? [supported]: SAML 2.0 with Entra ID, Google Workspace and Okta; account docs also name Google/Microsoft SSO. Sources: langdock:langdock:saml, langdock:langdock:account. - sso_plan — Which plan includes SSO? [supported]: Business up to 1000 users includes SSO, SCIM and SAML. Sources: langdock:langdock:billing. - mfa — Can MFA be enforced? [partial]: No standalone Langdock MFA; SAML identity provider enforces MFA. Sources: langdock:langdock:saml. - conditional_access — Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? Unknown. OIDC/LDAP enterprise options and a tested Entra Conditional Access compatibility matrix were not established. - domain_capture — Can the company claim its email domain? [supported]: Join by domain and verified email domains are prerequisites for SAML; SAML remains required on those verified domains. Sources: langdock:langdock:saml. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:saml, langdock:langdock:account, langdock:langdock:billing ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial SCIM synchronizes users/groups and preserves functioning ownerless agents. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - deprovisioning: Entra Update removes unassigned/blocked/soft-deleted memberships when enabled. Agents become unassigned, continue to work and need a new owner before editing; sync-folder owner removal can interrupt refresh. - seat_assignment: Admins assign roles/plans in member management; exact reclaimed-seat billing rules depend on subscription. - Unverified jit_provisioning: Just-in-time first-login provisioning and complete user-chat/knowledge ownership effects were not tested or fully specified. - scim — Is SCIM provisioning supported? [supported]: SCIM 2.0 via Entra, with prior SAML and verified domains. Sources: langdock:langdock:scim. - group_sync — Are identity-provider groups synced? [supported]: Entra SCIM group sync is documented and can be disabled; default group roles are separately configurable. Sources: langdock:langdock:scim-entra, langdock:langdock:workspace. - jit_provisioning — Are users created at first login? [unknown]: Are users created at first login? Unknown. Just-in-time first-login provisioning and complete user-chat/knowledge ownership effects were not tested or fully specified. - deprovisioning — What happens to a removed user's data and shared assets? [partial]: Entra Update removes unassigned/blocked/soft-deleted memberships when enabled. Agents become unassigned, continue to work and need a new owner before editing; sync-folder owner removal can interrupt refresh. Sources: langdock:langdock:scim-entra, langdock:langdock:leaver, langdock:langdock:sync. - seat_assignment — Can admins assign and reclaim seats? [partial]: Admins assign roles/plans in member management; exact reclaimed-seat billing rules depend on subscription. Sources: langdock:langdock:workspace. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:scim, langdock:langdock:scim-entra, langdock:langdock:workspace, langdock:langdock:leaver, langdock:langdock:sync ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial System/custom roles and delegated groups govern product and action permissions. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - feature_toggles: Role permissions plus integration/action sharing can target people/groups. Global chat/agent capabilities include search, images and file work; universal per-group toggle parity was not established. - Unverified multi_entity: Subsidiary/contract-level isolation beyond group and workspace boundaries was not established. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Member, Editor, Admin, up to five custom roles and extra permissions; group admins are separate from workspace admins. Sources: langdock:langdock:roles. - groups — Can permissions be set per group? [supported]: Groups can be SCIM-synced, admin-created or user-created if allowed; group rights and resources are distinct from system roles. Sources: langdock:langdock:workspace. - feature_toggles — Which features can be switched on or off per group? [partial]: Role permissions plus integration/action sharing can target people/groups. Global chat/agent capabilities include search, images and file work; universal per-group toggle parity was not established. Sources: langdock:langdock:roles, langdock:langdock:actions, langdock:langdock:workspace. - multi_entity — Can subsidiaries or departments be separated within one contract? [unknown]: Can subsidiaries or departments be separated within one contract? Unknown. Subsidiary/contract-level isolation beyond group and workspace boundaries was not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:roles, langdock:langdock:workspace, langdock:langdock:actions ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: supported Analytics and exports cover adoption and consumption with user-detail controls. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. - adoption_dashboard — Is there an adoption dashboard? [supported]: Active users, message trends, agent/group counts and leaderboards are documented. Sources: langdock:langdock:workspace. - breakdowns — Can usage be broken down by group, model, feature and assistant? [supported]: Products, models, users, groups, API keys, agents, workflows, projects and add-ins have dashboard/export breakdowns. Sources: langdock:langdock:workspace, langdock:langdock:exports. - export — Can usage data be exported? [supported]: CSV and Usage Export API, up to 12 months, one million rows per export and 15-minute generation limit. Sources: langdock:langdock:exports. - privacy_modes — Can per-person reporting be limited or pseudonymised? [supported]: User-level data toggle omits listed identifying fields from CSV; whole analytics can be disabled via support. Sources: langdock:langdock:exports, langdock:langdock:workspace. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:exports ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Chat/BYOK, workspace API and workflows have separate spend controls. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - budget_enforcement: Chat/agents fall back; personal API errors; workflow AI runs stop. Current response overshoot, unpriced models and excluded backbone/workspace API/workflow costs limit a single-budget interpretation. - chargeback: Usage CSV/API include cost and department/company grouping fields; a full accounting chargeback integration was not established. - cost_visibility — Can admins see cost or consumption per user and group? [supported]: BYOK analytics show estimated USD from configured custom-model rates; API/extra usage has billed costs. These can differ from provider invoices. Sources: langdock:langdock:workspace, langdock:langdock:byok. - budgets — Can budgets be set per user or group? [supported]: Workspace, plan, group, user and agent BYOK limits; personal extra limits; workflow workspace and individual limits. Sources: langdock:langdock:byok-limits, langdock:langdock:extra, langdock:langdock:workflow-limits. - budget_enforcement — Does reaching a budget alert, block or downgrade? [partial]: Chat/agents fall back; personal API errors; workflow AI runs stop. Current response overshoot, unpriced models and excluded backbone/workspace API/workflow costs limit a single-budget interpretation. Sources: langdock:langdock:extra, langdock:langdock:byok-limits, langdock:langdock:workflow-limits. - chargeback — Can costs be exported per cost centre? [partial]: Usage CSV/API include cost and department/company grouping fields; a full accounting chargeback integration was not established. Sources: langdock:langdock:exports. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:byok, langdock:langdock:byok-limits, langdock:langdock:extra, langdock:langdock:workflow-limits, langdock:langdock:exports ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise dedicated deployment documents separate administrative-event and conversation-content export APIs. Cloud content export requires workspace enablement and is outside this dedicated finding. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace, Langdock public APIs and agent MCP server; version=Public documentation checked 2026-10-26; plan=Enterprise dedicated deployment: administrative and resource APIs plus separately enabled Compliance API; Business Cloud outside this finding; add_ons=Dedicated Enterprise deployment and relevant API scopes; Compliance API deployment enablement; deployment_mode=dedicated-instance; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - Audit events, usage rows and conversation-content exports are distinct API functions. The dedicated-deployment behavior is not universal Business Cloud availability. - admin_events — Are admin and security events logged? [partial]: API logs workspace/model/role/skill/action/workflow changes and failed logins with actor/IP/diff; immutable storage guarantees were not verified. Sources: langdock:langdock:audit. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [partial]: Dedicated deployments serve the Compliance API unless disabled for that deployment. A key with the Compliance API scope is required. Conversation message content and tool inputs/outputs are included only when include_message_content=true and include_action_results=true are both set. On Cloud the scope is hidden and requests return 404 until workspace enablement; Business Cloud entitlement is not inferred. Sources: langdock:langdock:compliance-rev2-20261026. - siem_export — Can logs stream to a SIEM or be exported? [supported]: Cursor-paginated event API is documented for SIEM ingestion, under AUDIT_LOG_API scope. Sources: langdock:langdock:audit. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Unknown. Native legal hold/eDiscovery and audit integrity guarantees were not established. Rechecked 2026-10-26 in Audit Logs API Overview, Export tool parameters and outputs. - log_retention — How long are logs kept? [supported]: Administrative audit events have documented90-day retention. Conversation data follows the deployment workspace retention settings. A separate SaaS workflow pricing retention period is not asserted for this dedicated deployment. Sources: langdock:langdock:audit, langdock:langdock:workspace, langdock:langdock:pricing. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:audit, langdock:langdock:compliance-rev2, langdock:langdock:workspace, langdock:langdock:pricing, langdock:langdock:compliance-rev2-20261026, langdock:langdock:audit-20261026, langdock:langdock:workspace-20261026, langdock:langdock:pricing-20261026 ### 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. #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Purview source filtering is documented; generic prompt/file PII redaction remains unverified. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - dlp_integration: Request-enabled Purview label policy can withhold content before AI access for supported Microsoft integrations, with substantial documented exclusions. - filter_location: The label check runs in Langdock integration code before permitted content reaches the AI; it is not a generic AHV/IBAN detector. - Unverified pii_detection, pii_action, custom_patterns: The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run. - pii_detection — Is personal data detected in prompts and files? [unknown]: Is personal data detected in prompts and files? Unknown. The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run. - pii_action — Is it redacted, masked, blocked or only warned? [unknown]: Is it redacted, masked, blocked or only warned? Unknown. The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run. - custom_patterns — Can admins add custom patterns or terms? [unknown]: Can admins add custom patterns or terms? Unknown. The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run. - dlp_integration — Does it integrate with an existing DLP product? [partial]: Request-enabled Purview label policy can withhold content before AI access for supported Microsoft integrations, with substantial documented exclusions. Sources: langdock:langdock:labels. - filter_location — Where does filtering run? [partial]: The label check runs in Langdock integration code before permitted content reaches the AI; it is not a generic AHV/IBAN detector. Sources: langdock:langdock:labels. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:labels ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Instructions, disclaimers and agent compliance checks exist; prompt-level topic enforcement remains incomplete. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - org_instructions: Company description supplies up to 10000 characters in regular chats; agent/project instructions replace that field. - usage_notice: Admins can set chat/folder disclaimers and custom guidance links; required acceptance is not established. - content_filters: Governance rules evaluate agent configurations when created/published, not every prompt; failure can lead to manual flag/disable. - violation_reporting: Rule severity/results and per-rule failure analytics are visible in Governance; runtime prompt-policy reporting was not established. - org_instructions — Can admins set organisation-wide instructions? [partial]: Company description supplies up to 10000 characters in regular chats; agent/project instructions replace that field. Sources: langdock:langdock:workspace. - usage_notice — Can users be required to accept a usage policy? [partial]: Admins can set chat/folder disclaimers and custom guidance links; required acceptance is not established. Sources: langdock:langdock:workspace. - content_filters — Are content filters configurable? [partial]: Governance rules evaluate agent configurations when created/published, not every prompt; failure can lead to manual flag/disable. Sources: langdock:langdock:gov. - violation_reporting — Are policy hits visible to admins? [partial]: Rule severity/results and per-rule failure analytics are visible in Governance; runtime prompt-policy reporting was not established. Sources: langdock:langdock:gov. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:gov ## 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Default Azure Frankfurt/EU storage and provider-specific inference are contractually distinguished. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - backups_logs_region: DPA Appendix 2 places Sentry diagnostic data in EU; full backup/telemetry physical region matrix was not disclosed. - swiss_hosting: Custom model setup allows CH region on some dedicated deployments, which does not prove end-to-end Swiss platform/support residency. - support_access_region: User-granted Support sharing expires after 72 hours and is unavailable on dedicated deployments; staff access geography is not specified. - storage_region — Where are chats, files and indexes stored? [supported]: Terms Appendix 1 places files, prompts, outputs and embeddings in selected EU Azure data centres; Frankfurt named. Sources: langdock:langdock:terms. - inference_region — Where do model calls run, per provider? [supported]: Azure, OpenAI, Google, AWS Bedrock and Mistral have described EU routes. Opt-in Global Azure/Google/AWS/OpenAI routes can infer worldwide, including US; default model enablement is EU only. Sources: langdock:langdock:terms, langdock:langdock:dpa, langdock:langdock:workspace. - backups_logs_region — Where are backups, logs and telemetry? [partial]: DPA Appendix 2 places Sentry diagnostic data in EU; full backup/telemetry physical region matrix was not disclosed. Sources: langdock:langdock:dpa. - support_access_region — From where can vendor staff access data? [partial]: User-granted Support sharing expires after 72 hours and is unavailable on dedicated deployments; staff access geography is not specified. Sources: langdock:langdock:account. - swiss_hosting — Is Swiss hosting available? [partial]: Custom model setup allows CH region on some dedicated deployments, which does not prove end-to-end Swiss platform/support residency. Sources: langdock:langdock:byok-models. - residency_plan — Which plan or option provides residency? [supported]: Standard multi-tenant uses EU Azure; global model activation is a controller instruction under DPA section 8. Sources: langdock:langdock:security, langdock:langdock:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:dpa, langdock:langdock:workspace, langdock:langdock:byok-models, langdock:langdock:account, langdock:langdock:security ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Deployment minimums differ from Enterprise subscription entry. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Standard SaaS; Enterprise 1000+; managed dedicated 2000+; own cloud/on-premise 5000+; add_ons=Deployment and operations quoted; deployment_mode=not specified; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - customer_cloud: Customer-cloud dedicated deployment from 5000+ seats; detailed operator and feature allocation are contract-specific. - on_premise: Custom Kubernetes via Helm from 5000+ seats; operator split and infrastructure requirements are not public here. - mode_feature_gaps: Dedicated lacks Support chat-sharing and password/profile editing in Langdock; other feature controls depend on deployment configuration. No exhaustive parity list was found. - Unverified air_gapped: Air-gapped operation was not established. Thresholds are not universal feature or pricing entitlements. - multi_tenant_saas — Is a shared SaaS offered? [supported]: Standard multi-tenant SaaS is hosted on Microsoft Azure within EU. Sources: langdock:langdock:security. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [supported]: Langdock-managed single-tenant SaaS from 2000+ seats. Sources: langdock:langdock:security. - customer_cloud — Can it run in the customer's own cloud account, from what size? [partial]: Customer-cloud dedicated deployment from 5000+ seats; detailed operator and feature allocation are contract-specific. Sources: langdock:langdock:security. - on_premise — Can the whole platform run on customer infrastructure, from what size? [partial]: Custom Kubernetes via Helm from 5000+ seats; operator split and infrastructure requirements are not public here. Sources: langdock:langdock:security. - air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? Unknown. Air-gapped operation was not established. Thresholds are not universal feature or pricing entitlements. - mode_feature_gaps — Which features are missing outside SaaS? [partial]: Dedicated lacks Support chat-sharing and password/profile editing in Langdock; other feature controls depend on deployment configuration. No exhaustive parity list was found. Sources: langdock:langdock:account, langdock:langdock:chat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:security, langdock:langdock:account, langdock:langdock:chat ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: supported Microsoft Azure model routes use the contract-described no-training and Modified Abuse Monitoring configuration. Other providers are outside this finding. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business/Enterprise managed Microsoft Azure model routes only; BYOK and Fable/other-provider routes excluded; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default; explicitly selected global Azure models may infer outside EU; os=not specified. Limitations: - Fable5/5.1 and direct/OpenAI image/file exceptions are outside this Azure-only scope; no platform-wide ZDR claim is made. - vendor_training — Does the vendor train on customer content? [supported]: Terms section9 prohibits Langdock use of customer data for model development, training or improvement. Sources: langdock:langdock:terms-rev2. - provider_training — Do model providers train on it under this product's contracts? [supported]: Appendix1 Microsoft Azure obligations exclude sharing customer prompts/files/embeddings with model developers and using them to train or improve models. Sources: langdock:langdock:terms-rev2. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [supported]: For the scoped Microsoft Azure model route, Langdock states Modified Abuse Monitoring disables provider storage of prompts/outputs for abuse monitoring. Platform conversation storage is separate. Sources: langdock:langdock:terms-rev2. - zero_retention — Is zero data retention available, and on which plan? [supported]: The Azure route has the Modified Abuse Monitoring zero-retention configuration described in Appendix1. This does not establish ZDR for arbitrary customer keys or other providers. Sources: langdock:langdock:terms-rev2. - human_review — Can provider staff review content? [supported]: Appendix1 states Azure human abuse review of the scoped prompts/outputs is disabled by Modified Abuse Monitoring. Sources: langdock:langdock:terms-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms-rev2 ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Admins control chat retention; file cleanup depends on all remaining references. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - default_retention: No universal default duration is specified. File retention depends on recent files, chats, agents, folders or knowledge links; workflow pricing lists 30-day run retention. - user_deletion: Deleted chats become unavailable immediately; files belonging only to them are deleted at overnight cleanup. Files linked elsewhere remain; deleting a folder alone retains its files. - default_retention — What is retained and for how long by default? [partial]: No universal default duration is specified. File retention depends on recent files, chats, agents, folders or knowledge links; workflow pricing lists 30-day run retention. Sources: langdock:langdock:retention, langdock:langdock:pricing. - admin_retention — Can admins set retention periods? [supported]: Chat inactivity retention options are seven days, one/three/twelve months or forever, with daily irreversible deletion. Sources: langdock:langdock:workspace. - user_deletion — Can users delete their chats and files permanently? [partial]: Deleted chats become unavailable immediately; files belonging only to them are deleted at overnight cleanup. Files linked elsewhere remain; deleting a folder alone retains its files. Sources: langdock:langdock:retention. - contract_end_deletion — What is deleted at contract end, and when? [supported]: DPA section 11 requires deletion within 30 days of termination subject to legal retention, confirmation on request and export access until deletion. Sources: langdock:langdock:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:retention, langdock:langdock:pricing, langdock:langdock:workspace, langdock:langdock:dpa ### DATA-05: Sub-processors and foreign-law exposure Judgment rule: Record the published sub-processor list with countries, change-notification rules, the vendor's and parent company's jurisdiction, transfer mechanisms (EU-US Data Privacy Framework, Swiss-US DPF, SCCs) and the vendor's documented position on foreign government access requests (e.g. US CLOUD Act). Record facts, not a legal assessment. #### 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. #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA publishes seven default subprocessors and conditional Global routes with transfer mechanisms. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - parent_jurisdiction: Langdock GmbH, Berlin, Germany is contracting entity. Parent-company ownership was not fully established. - government_access_policy: Confidentiality clause requires minimizing legally compelled disclosure and notifying where legally permitted; no separate request statistics/transparency report was found. - subprocessor_list — Is a dated sub-processor list published? [supported]: DPA 2.1 Appendix 2 embeds the current named list; trust-centre subprocessor page needs client rendering and did not return text. Sources: langdock:langdock:dpa. - subprocessor_countries — Which countries do sub-processors operate in? [supported]: Default entities: Microsoft Ireland, AWS EMEA Luxembourg, Google Cloud EMEA Ireland, OpenAI Ireland, Mistral France, Sentry US and Cloudflare US; default processing column is EU. Global opt-ins include worldwide/US inference and Azure EU storage. Sources: langdock:langdock:dpa. - change_notification — Are customers notified of sub-processor changes? [supported]: At least 14 days before new/replaced subprocessor via public register and email only if subscribed; objection within 14 days of publication. Sources: langdock:langdock:dpa. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: Langdock GmbH, Berlin, Germany is contracting entity. Parent-company ownership was not fully established. Sources: langdock:langdock:terms. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [supported]: DPA lists EU-US/Swiss-US DPF, UK extension and EU/UK SCCs with Swiss addenda per provider; Global OpenAI lists EU/UK SCCs. Sources: langdock:langdock:dpa. - government_access_policy — Is there a published government-access or transparency policy? [partial]: Confidentiality clause requires minimizing legally compelled disclosure and notifying where legally permitted; no separate request statistics/transparency report was found. Sources: langdock:langdock:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:dpa, langdock:langdock: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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA automatically forms part of German-law terms; Swiss and sector materials need qualification. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - dpa: Terms section 16 automatically incorporates public DPA 2.1; nonstandard instructions require written amendment, and negotiability is not promised. - revdsg_gdpr: GDPR Article 28 governs; provider transfer table includes Swiss safeguards but a complete revDSG scope/addendum was not established. - ai_act_materials: Governance templates include EU AI Act/GDPR/security checks of agent definitions; these do not establish a complete product provider/deployer dossier. - sector_materials: Legal-links page advertises a Professional Secrecy Addendum in Trust Center; no FINMA package was obtained. - dpa — Is a DPA available, and is it negotiable? [partial]: Terms section 16 automatically incorporates public DPA 2.1; nonstandard instructions require written amendment, and negotiability is not promised. Sources: langdock:langdock:terms, langdock:langdock:dpa. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: GDPR Article 28 governs; provider transfer table includes Swiss safeguards but a complete revDSG scope/addendum was not established. Sources: langdock:langdock:dpa. - governing_law — Which law and court govern the contract? [supported]: German law, Berlin exclusive jurisdiction; German language version binds over English translation. Sources: langdock:langdock:terms. - ai_act_materials — Is EU AI Act documentation provided? [partial]: Governance templates include EU AI Act/GDPR/security checks of agent definitions; these do not establish a complete product provider/deployer dossier. Sources: langdock:langdock:pricing, langdock:langdock:gov. - sector_materials — Are FINMA or other sector materials provided? [partial]: Legal-links page advertises a Professional Secrecy Addendum in Trust Center; no FINMA package was obtained. Sources: langdock:langdock:legal. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:dpa, langdock:langdock:pricing, langdock:langdock:gov, langdock:langdock:legal ### 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. #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial ISO 27001 and SOC 2 Type II are vendor claims pending certificate/report verification. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - iso_27001: Security page claims Langdock ISO 27001; issuer, exact scope and validity were not retrieved. - soc2: Security page claims SOC 2 Type II; report period/auditor/service scope was not retrieved. - report_access: Public legal-links page sends certificate/report requests to the Trust Center, which rendered no text in this access method. - pentest: Vendor describes frequent independent penetration testing; no test report or bounded result was retrieved. - Unverified c5, other_certifications: No C5, other product certificate, issuer-register verification or gated report was established. - iso_27001 — ISO 27001 with scope and validity? [partial]: Security page claims Langdock ISO 27001; issuer, exact scope and validity were not retrieved. Sources: langdock:langdock:security. - soc2 — SOC 2 type, period and covered service? [partial]: Security page claims SOC 2 Type II; report period/auditor/service scope was not retrieved. Sources: langdock:langdock:security. - c5 — BSI C5 attestation? [unknown]: BSI C5 attestation? Unknown. No C5, other product certificate, issuer-register verification or gated report was established. - other_certifications — Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Unknown. No C5, other product certificate, issuer-register verification or gated report was established. - report_access — How can customers obtain reports? [partial]: Public legal-links page sends certificate/report requests to the Trust Center, which rendered no text in this access method. Sources: langdock:langdock:legal. - pentest — Are independent penetration test summaries available? [partial]: Vendor describes frequent independent penetration testing; no test report or bounded result was retrieved. Sources: langdock:langdock:security. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:security, langdock:langdock:legal ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Encryption and network restrictions are documented; customer key custody is not established. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - private_networking: CIDR IP allowlists block workspace login/use from unapproved networks; private-link endpoint availability was not established. - Unverified customer_managed_keys, tenant_isolation: Customer-managed encryption keys and exact shared-SaaS tenant isolation implementation were not established; LLM BYOK is a separate concept. - encryption_at_rest — Is data encrypted at rest? [supported]: Vendor states AES-256 storage and TLS 1.2+ transport. Sources: langdock:langdock:security. - customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Unknown. Customer-managed encryption keys and exact shared-SaaS tenant isolation implementation were not established; LLM BYOK is a separate concept. - private_networking — Is private connectivity or IP restriction available? [partial]: CIDR IP allowlists block workspace login/use from unapproved networks; private-link endpoint availability was not established. Sources: langdock:langdock:ip. - tenant_isolation — How are customers separated in shared SaaS? [unknown]: How are customers separated in shared SaaS? Unknown. Customer-managed encryption keys and exact shared-SaaS tenant isolation implementation were not established; LLM BYOK is a separate concept. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:security, langdock:langdock:ip ### 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 #### Langdock 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business uses seats with included managed-chat usage; workflow/API and other add-ons are separate. An applicable Standard/BYOK licence tariff is not established. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents and optional modules; Enterprise quoted at1000+; applicable Standard/BYOK tariff unknown; add_ons=Workflows, Governance, API/Extra Usage; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - Inconsistent price representations are retained as a named price gap, not combined into a synthetic tariff. - pricing_unit — What is the pricing unit? [supported]: Seat/month platform, per-workspace workflow packages, metered API/workflow AI/extra usage, optional per-seat Governance. Sources: langdock:langdock:pricing-rev2. - list_prices — What are list prices per plan, with date and currency? [unknown]: Unknown applicable Standard/BYOK seat tariff. The public Business headline is EUR25 while the annual price breakdown starts at EUR23.20; billing docs refer to the same pricing page without reconciling them. Enterprise1000+ is quote-only. Prior hashed-calculator rates are excluded. - included_usage — What usage is included? [partial]: Standard includes managed chat/agent usage under five-hour and weekly windows; Max has 5x. Precise numerical included cost budgets are not public. Starter includes 2500 workflow runs/month but no workflow model tokens. Sources: langdock:langdock:pricing-rev2, langdock:langdock:limits. - add_ons — Which features cost extra? [partial]: Workflow Starter includes2500runs/month with AI tokens billed separately. The public add-on page lists40k/100k packages and Governance free until2027-01-01, then separately priced per base-plan seat. The applicable binding package/billing-period amounts are not established here. Sources: langdock:langdock:pricing-rev2. - overage — What do usage beyond limits and premium models cost? [supported]: Extra usage is charged at API rates. Model page lists GPT-5 Mini EUR 0.22 input/1.78 output per million; workflow and API spend use separate caps. Sources: langdock:langdock:extra, langdock:langdock:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:pricing-rev2, langdock:langdock:limits, langdock:langdock:extra, langdock:langdock:models ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial All requested200/1000/5000-user totals are unknown because an applicable Business Standard tariff or Enterprise quote is not verified. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Standard up to1000 users; Enterprise1000+; all applicable scenario licence totals unknown; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21:12months, list prices, excluding VAT;60/30/10 users at100/400/1500messages monthly,3000input+600output tokens/message. Only separately billed usage uses this token mix. - ECB2026-10-20 EUR1=USD1.1215=CHF0.9237. Unknown base/variable components prevent totals; no silent conversion. - cost_200 — Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown total for200users over12months excluding VAT. No applicable Business Standard tariff is established from the conflicting headline/breakdown; Enterprise at1000+ is quote-only. No calculator-derived base floor or inferred discount is retained. Included managed-chat use is not separately billed by the token mix. - cost_1000 — Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown total for1000users over12months excluding VAT. No applicable Business Standard tariff is established from the conflicting headline/breakdown; Enterprise at1000+ is quote-only. No calculator-derived base floor or inferred discount is retained. Included managed-chat use is not separately billed by the token mix. - cost_5000 — Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown total for5000users over12months excluding VAT. No applicable Business Standard tariff is established from the conflicting headline/breakdown; Enterprise at1000+ is quote-only. No calculator-derived base floor or inferred discount is retained. Included managed-chat use is not separately billed by the token mix. - variable_share — Which part depends on usage? [partial]: Managed Business chat includes model usage subject to usage limits. ExtraUsage,workflow/API,Governance and customer-provider BYOK bills are separate. Missing applicable tariff/allowance components remain unknown; no proxy substitutes for vendor-billed usage. Sources: langdock:langdock:billing, langdock:langdock:extra. - unknown_parts — Which costs could not be priced? [partial]: Business Standard/BYOK applicable seat rate, Enterprise licence/deployment quote, workload-preserving overage and required modules/services are unknown. This prevents a verifiable EUR/CHF total. Sources: langdock:langdock:pricing-rev2, langdock:langdock:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:pricing-rev2, langdock:langdock:billing, langdock:langdock:extra, langdock:langdock:ecb-fx ### VEN-03: Evaluation access Judgment rule: Distinguish free tier, self-serve trial, sales-led pilot, paid proof of concept and open-source self-install. Record card requirement, duration, seat limit, and which features (SSO, connectors, admin) the trial includes. Map which shared scenarios can be run without sales approval. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial A seven-day self-serve business trial is advertised without a card. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - free_tier: Terms describe a time-limited trial that ends automatically; permanent business free access is not established. - trial_scope: Pricing says test all platform features, but enterprise deployments and optional enablement cannot be inferred; SAML/SCIM trial configuration was not run. - sales_gate: Base trial is self-serve; enterprise deployment and custom terms require an offer. - free_tier — Is there a free tier for business use? [partial]: Terms describe a time-limited trial that ends automatically; permanent business free access is not established. Sources: langdock:langdock:terms. - self_serve_trial — Is a self-serve business trial available? [supported]: Seven days, no card, EUR 5 model credit and team invitations. Sources: langdock:langdock:pricing. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Pricing says test all platform features, but enterprise deployments and optional enablement cannot be inferred; SAML/SCIM trial configuration was not run. Sources: langdock:langdock:pricing. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Base trial is self-serve; enterprise deployment and custom terms require an offer. Sources: langdock:langdock:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:pricing, langdock:langdock:billing ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Monthly/annual contract defaults and EUR invoices are public; some pricing representations conflict. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - minimum_commitment: Calculator starts at one user and Business supports up to1000; Enterprise/deployment minimums differ. - local_invoicing: Langdock GmbH invoices EUR excl tax; contract specifies market-rate conversion of provider foreign-currency charges. CHF invoices were not established. - transparency_class: Partially specified public rates and usage rules; Enterprise quote-only and headline/calculator rates differ. - minimum_commitment — What seat or spend minimum applies? [partial]: Calculator starts at one user and Business supports up to1000; Enterprise/deployment minimums differ. Sources: langdock:langdock:pricing, langdock:langdock:security. - contract_length — What contract lengths are offered? [supported]: Monthly or annual; annual offers 20% reduction on Standard tiers. Sources: langdock:langdock:billing. - cancellation — How can the contract be cancelled or reduced? [supported]: Terms specify seven-day notice before monthly end, fourteen days before annual/multiyear end; automatic monthly/12-month renewals; notices by text/email or platform. Sources: langdock:langdock:terms. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: Langdock GmbH invoices EUR excl tax; contract specifies market-rate conversion of provider foreign-currency charges. CHF invoices were not established. Sources: langdock:langdock:terms. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: Partially specified public rates and usage rules; Enterprise quote-only and headline/calculator rates differ. Sources: langdock:langdock:pricing, langdock:langdock:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:pricing, langdock:langdock:security, langdock:langdock:billing, langdock:langdock:terms ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Commercial platform rights are proprietary and time-limited. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - licence_type: Terms grant a nonexclusive/nontransferable contract-term right, not an OSI source licence. Component-level connector/client licences are not enumerated. - branding_restrictions: Terms prohibit removing proprietary notices and reselling platform access; admin branding options do not transfer platform IP. - Unverified enterprise_features_closed: A public component-by-component source licence/current revision and distinct open/closed enterprise edition mapping were not established. - licence_type — Which licence applies to each component? [partial]: Terms grant a nonexclusive/nontransferable contract-term right, not an OSI source licence. Component-level connector/client licences are not enumerated. Sources: langdock:langdock:terms. - branding_restrictions — Do licence terms restrict branding or user counts? [partial]: Terms prohibit removing proprietary notices and reselling platform access; admin branding options do not transfer platform IP. Sources: langdock:langdock:terms. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Unknown. A public component-by-component source licence/current revision and distinct open/closed enterprise edition mapping were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise dedicated resource/configuration and conversation-content APIs document exports. A complete source/index/ACL workspace exit bundle has not been established. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace, Langdock public APIs and agent MCP server; version=Public documentation checked 2026-10-26; plan=Enterprise dedicated deployment: administrative and resource APIs plus separately enabled Compliance API; Business Cloud outside this finding; add_ons=Dedicated Enterprise deployment and relevant API scopes; Compliance API deployment enablement; deployment_mode=dedicated-instance; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - Configuration/file APIs are separate from conversation export. Dedicated Compliance API availability does not establish a Business Cloud entitlement. - chat_export — Can admins export all chats? [partial]: The dedicated-deployment Compliance API documents paginated conversation/message exports. include_message_content=true adds messages; both it and include_action_results=true add tool arguments and outputs. A scoped key is required. Cloud workspaces need separate enablement and no Business Cloud entitlement is inferred. Sources: langdock:langdock:compliance-rev2-20261026. - assistant_export — Can assistants and prompts be exported in a reusable format? [partial]: Agent API Get/Create migration exports configuration; attachments/skills must be handled separately and some fields/ownership do not transfer. Sources: langdock:langdock:migration. - knowledge_export — Can knowledge bases and their sources be exported? [partial]: Knowledge Folder API can retrieve/list files; a complete original-source/index/ACL export bundle was not demonstrated. Sources: langdock:langdock:knowledge, langdock:langdock:knowledge-20261026. - export_format — Are formats documented and machine-readable? [partial]: Agent and Compliance API JSON plus usage CSV/JSON are documented; this is not a one-click complete workspace export. Sources: langdock:langdock:compliance-rev2, langdock:langdock:migration, langdock:langdock:exports, langdock:langdock:exports-20261026. - post_termination_window — How long can data be retrieved after termination? [supported]: DPA permits exports during contract and until deletion, which occurs no later than30 days after termination subject to legal retention. Sources: langdock:langdock:dpa. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:compliance-rev2, langdock:langdock:migration, langdock:langdock:knowledge, langdock:langdock:exports, langdock:langdock:dpa, langdock:langdock:compliance-rev2-20261026, langdock:langdock:migration-20261026, langdock:langdock:knowledge-20261026, langdock:langdock:exports-20261026, langdock:langdock:dpa-20261026 ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Berlin vendor support, public status history and a 99% monthly availability term are documented. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - support_channels: Support email is documented; Enterprise has custom account management/support, and rollout programmes have shared Teams/Slack channels. - uptime_sla: Terms promise at least99% monthly availability with defined exclusions and up to5h scheduled maintenance/month. Statutory remedy/credit procedure exists, but no fixed percentage-credit schedule is published. - Unverified support_languages: Contractual DE/FR/IT support languages, full hours/timezone and dedicated response/credit schedules were not established. - support_channels — Which support channels are available on each plan? [partial]: Support email is documented; Enterprise has custom account management/support, and rollout programmes have shared Teams/Slack channels. Sources: langdock:langdock:billing, langdock:langdock:playbook. - support_languages — Is support available in German, French or Italian? [partial]: The imprint says users and authorities can contact support@langdock.com in German and English. It does not specify contractual French or Italian support, hours or response times. Sources: langdock:langdock:imprint-20261026. - regional_presence — Is there a DACH or Swiss entity, team or partner? [supported]: Langdock GmbH contracts from Berlin, Germany. Sources: langdock:langdock:terms. - uptime_sla — Is there an uptime SLA with credits? [partial]: Terms promise at least99% monthly availability with defined exclusions and up to5h scheduled maintenance/month. Statutory remedy/credit procedure exists, but no fixed percentage-credit schedule is published. Sources: langdock:langdock:terms. - status_page — Is there a public status page with history? [supported]: Public status separates app/API/Workflow/Integration history. Sources: langdock:langdock:status. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:billing, langdock:langdock:playbook, langdock:langdock:terms, langdock:langdock:status, langdock:langdock:imprint-20261026, langdock:langdock:terms-20261026, langdock:langdock:status-20261026 ### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Rollout support starts at 250 licences; public learning material and champion guidance are available. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - onboarding_service: Dedicated rollout/workshops/shared channels are available from250 seats; exact included versus chargeable services depends on contract. - user_training: Public workshops have recordings/slides; the complete delivery-language and included-live-training matrix is not specified. - service_cost: Enterprise custom onboarding/support is quote-based; public per-workshop fees were not found. - onboarding_service — Is guided onboarding included? [partial]: Dedicated rollout/workshops/shared channels are available from250 seats; exact included versus chargeable services depends on contract. Sources: langdock:langdock:playbook. - user_training — Is end-user training offered, in which languages? [partial]: Public workshops have recordings/slides; the complete delivery-language and included-live-training matrix is not specified. Sources: langdock:langdock:training. - use_case_library — Are role-based use cases and templates provided? [supported]: Playbook recommends role-specific prompts/agents and gives structured use-case discovery material. Sources: langdock:langdock:playbook. - adoption_programme — Is there a champion or adoption programme? [supported]: Playbook includes department champions, follow-ups, hackathons and AI challenges. Sources: langdock:langdock:playbook. - service_cost — Which services cost extra? [partial]: Enterprise custom onboarding/support is quote-based; public per-workshop fees were not found. Sources: langdock:langdock:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:playbook, langdock:langdock:training, langdock:langdock:billing ## 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 ### langdock:langdock:models AI Models | Langdock. Public model table lists current text models and EUR metered prices. - URL: https://langdock.com/models - Locator: Provider tables - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:model-guide Model Guide. Users select models or Auto routing; reasoning levels vary by model. - URL: https://docs.langdock.com/en/using-langdock/models-and-limits/models.md - Locator: Selecting a Model, Auto and Thinking - Evidence kind: documented - Source date: Not stated - 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 ### langdock:langdock:changes Product Changelog | Langdock. Dated releases document model additions, desktop apps and per-agent confirmations. - URL: https://langdock.com/changelog - Locator: 13 October 2026 model release; 15/10 September feature releases - 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 ### langdock:langdock:billing https://docs.langdock.com/en/admin/billing/pricing.md. Business covers up to 1000 users, BYOK separates model costs, workflows/API are metered and Enterprise is quoted. - URL: https://docs.langdock.com/en/admin/billing/pricing.md - Locator: Products, volume tiers, Enterprise and API - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:byok https://docs.langdock.com/en/admin/byok/byok.md. BYOK replaces completion, embedding and image routes; missing model categories break relevant features. - URL: https://docs.langdock.com/en/admin/byok/byok.md - Locator: Options, requirements, setup and usage export - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:byok-routes Setup Guides. Named BYOK routes include cloud providers, Vercel Gateway and self-hosted OpenAI-compatible HTTPS endpoints. - URL: https://docs.langdock.com/en/admin/byok/setup-guides.md - Locator: Provider setup tabs and OpenAI-compatible endpoints - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:research Deep Research. Deep Research creates cited public-web reports and has a 15-per-30-days cap for standard keys. - URL: https://docs.langdock.com/en/using-langdock/chat/tools/deep-research.md - Locator: Model configuration, limitations and usage - 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 ### langdock:langdock:terms Terms of Use | Langdock. Terms 2.1 prohibit training and describe provider-specific residency and retention agreements, proprietary use rights and contract defaults. - URL: https://langdock.com/terms - Locator: Sections 6/7/9/12/15/16/19 and Appendix 1 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:byok-models How to add your own models. Admins configure completion, image and embedding models, deployments, capability flags and USD accounting rates. - URL: https://docs.langdock.com/en/admin/byok/adding-models.md - Locator: Custom model setup and deployment configuration - Evidence kind: documented - 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 ### langdock:langdock:pricing Pricing Plans | Langdock. Business headline prices, annual discounts, workflow packages and Governance promotion are public. - URL: https://langdock.com/pricing - Locator: Chat & Agents, price breakdown, add-ons and API - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:workspace Workspace Settings. Workspace settings define retention, model defaults, EU-only default enablement, analytics and product controls. - URL: https://docs.langdock.com/en/admin/workspace/workspace.md - Locator: Product Settings, Models, Analytics and Customizations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:limits Usage Limits. Five-hour and weekly usage windows trigger extra usage or a fallback; spam protection caps 250 messages per three hours. - URL: https://docs.langdock.com/en/using-langdock/models-and-limits/fair-usage-policy.md - Locator: Usage windows and exhaustion - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:extra Extra Usage. Extra usage has workspace/plan/user caps and fallback behavior with possible final-response overshoot. - URL: https://docs.langdock.com/en/admin/manage-usage/extra-usage.md - Locator: Enabling extra usage, spend limits and API exceptions - 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 ### langdock:langdock:files Which file types does Langdock support?. Supported files have different type-specific size limits and processing restrictions. - URL: https://docs.langdock.com/en/using-langdock/troubleshooting/faq/supported-file-types.md - Locator: Format/size tables and processing limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:file-count What are the file limits in the chat and in agents?. Web message uploads allow 50 files, mobile five; agent knowledge and knowledge bases have separate limits. - URL: https://docs.langdock.com/en/using-langdock/troubleshooting/faq/file-limit.md - Locator: Chat and agent attachment limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:retrieval Knowledge Basics. Direct file previews differ from semantic search over 2000-character chunks, returning up to 50 passages. - URL: https://docs.langdock.com/en/using-langdock/guides/knowledge/knowledge-basics.md - Locator: Direct context and embedding search - 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 ### langdock:langdock:knowledge Knowledge bases. Persistent shareable knowledge bases accept up to 1000 text documents, search chunks and attach to agents. - URL: https://docs.langdock.com/en/using-langdock/library/knowledge-bases.md - Locator: Creation, sharing, limits and agent use - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:agents Agent Configuration. Agents combine instructions, files, folders, models, actions, skills and subagents, with optional source-access restrictions. - URL: https://docs.langdock.com/en/using-langdock/agents/configuration.md - Locator: Agent configuration, knowledge and source restriction - 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 ### langdock:langdock:sync Folder Sync. Daily folder sync supports SharePoint, OneDrive, Drive and Confluence, with real-time user access checks. - URL: https://docs.langdock.com/en/using-langdock/guides/integrations/folder-sync.md - Locator: Setup, permission checks, sync behavior and owner removal - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:integrations Integration Directory. The native directory lists Microsoft, Google, Atlassian, CRM, BI, vector search, DeepL and audio integrations. - URL: https://docs.langdock.com/en/using-langdock/integrations/integration-directory.md - Locator: Native integration directory - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:mcp Model Context Protocol (MCP). MCP clients support Streamable HTTP/SSE and several authentication types; new tools do not require confirmation by default. - URL: https://docs.langdock.com/en/using-langdock/guides/integrations/mcp/mcp.md - Locator: Transports, authentication and tool confirmation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:labels Sensitivity Label Policy. A request-enabled Purview label policy filters supported integrations, with documented actions and upload exceptions. - URL: https://docs.langdock.com/en/admin/manage-integrations/sensitivity-label-policy.md - Locator: Availability, enforcement, exceptions and unsupported areas - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:actions Manage Action Access. Admins share integrations and actions with users/groups/API keys; native core actions cannot be disabled. - URL: https://docs.langdock.com/en/admin/manage-integrations/manage-action-access.md - Locator: Access settings and native-action exception - 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 ### langdock:langdock:chat Basic Chat functionalities. Chat supports model selection and governed tools; memory, deep research and agent tool conditions differ. - URL: https://docs.langdock.com/en/using-langdock/chat/functionalities.md - Locator: Model selector and tool availability - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:account Account Settings. Account settings include five UI languages, personal controls and temporary 72-hour Support sharing. - URL: https://docs.langdock.com/en/using-langdock/account/account.md - Locator: Preferences, shared chats, custom instructions and memory - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:memory Memory. Memory works in regular chats only, with a 50-memory cap and view/edit/delete controls. - URL: https://docs.langdock.com/en/using-langdock/chat/tools/memory.md - Locator: Availability, management and limits - 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 ### langdock:langdock:roles Roles and extra permissions. System roles, up to five custom roles and delegated group permissions are configurable. - URL: https://docs.langdock.com/en/admin/workspace/roles.md - Locator: System roles, custom roles and group permissions - 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 ### 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 ### langdock:langdock:web Web Search. Web search returns inspectable citations and has a separate open-URL tool. - URL: https://docs.langdock.com/en/using-langdock/chat/tools/web-search.md - Locator: Search behavior and source inspection - 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 ### langdock:langdock:workflows Introduction to Workflows. Workflows chain agents, integrations and logic with form, schedule and event triggers after admin activation. - URL: https://docs.langdock.com/en/using-langdock/workflows/introduction.md - Locator: Introduction and activation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:hitl Human in the Loop. Workflow runs can pause for editor approval or per-action confirmation. - URL: https://docs.langdock.com/en/using-langdock/workflows/fundamentals/human-in-the-loop.md - Locator: Approval and action confirmation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:excel Excel Add-in. The Excel add-in reads and writes workbooks with default edit confirmation and named version prerequisites. - URL: https://docs.langdock.com/en/using-langdock/microsoft-add-ins/excel.md - Locator: Install, workbook operations and edit permissions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:outlook-rev2 Outlook Add-in. The Outlook add-in requires workspace-admin access and Exchange Online; edits ask by default and sending requires an explicit requested and confirmed action. - URL: https://docs.langdock.com/en/using-langdock/microsoft-add-ins/outlook.md - Locator: Installation and Exchange Online prerequisites; edit permissions; HTTP200 Markdown re-read2026-10-21 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:outlook-marketplace Langdock for Outlook, by Langdock GmbH. Vendor listing offers the add-in to every paid Langdock plan and trials, with draft review before sending. - URL: https://marketplace.microsoft.com/en-us/product/WA200011534?tab=Overview - Locator: Overview and eligibility sentence - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:outlook-rev2-20261026 Outlook Add-in. The Outlook add-in requires workspace-admin access and Exchange Online; edits ask by default and sending requires an explicit requested and confirmed action. - URL: https://docs.langdock.com/en/using-langdock/microsoft-add-ins/outlook.md - Locator: Installation and Exchange Online prerequisites; edit permissions; HTTP200 Markdown re-read2026-10-21 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:pricing-20261026 Pricing Plans | Langdock. Business headline prices, annual discounts, workflow packages and Governance promotion are public. - URL: https://langdock.com/pricing - Locator: Chat & Agents, price breakdown, add-ons and API - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:changes-20261026 Product Changelog | Langdock. Dated releases document model additions, desktop apps and per-agent confirmations. - URL: https://langdock.com/changelog - Locator: 13 October 2026 model release; 15/10 September feature releases - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:outlook-admin-20261026 Outlook Add-in setup. Admins set Outlook add-in access to Nobody, Everyone or Specific members and groups; Outlook Email and Calendar integrations have separate access/scopes. - URL: https://docs.langdock.com/en/admin/manage-integrations/add-in-setup-guides/outlook.md - Locator: Availability and access settings - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:agents-20261026 Agent Configuration. Agents combine instructions, files, folders, models, actions, skills and subagents, with optional source-access restrictions. - URL: https://docs.langdock.com/en/using-langdock/agents/configuration.md - Locator: Agent configuration, knowledge and source restriction - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:research-20261026 Deep Research. Deep Research creates cited public-web reports and has a 15-per-30-days cap for standard keys. - URL: https://docs.langdock.com/en/using-langdock/chat/tools/deep-research.md - Locator: Model configuration, limitations and usage - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:hitl-20261026 Human in the Loop. Workflow runs can pause for editor approval or per-action confirmation. - URL: https://docs.langdock.com/en/using-langdock/workflows/fundamentals/human-in-the-loop.md - Locator: Approval and action confirmation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:mcp-20261026 Model Context Protocol (MCP). MCP clients support Streamable HTTP/SSE and several authentication types; new tools do not require confirmation by default. - URL: https://docs.langdock.com/en/using-langdock/guides/integrations/mcp/mcp.md - Locator: Transports, authentication and tool confirmation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:excel-20261026 Excel Add-in. The Excel add-in reads and writes workbooks with default edit confirmation and named version prerequisites. - URL: https://docs.langdock.com/en/using-langdock/microsoft-add-ins/excel.md - Locator: Install, workbook operations and edit permissions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### 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 ### langdock:langdock:mcp-server Langdock Agent MCP Server. A public MCP endpoint exposes workspace agents under Agent API scope. - URL: https://docs.langdock.com/en/using-langdock/guides/integrations/mcp/langdock-agent-mcp-server.md - Locator: Endpoint, authentication and tools - 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 ### langdock:langdock:desktop-rev2 Enterprise Guide for Langdock Desktop. Managed desktop rollout supports machine-wide Windows packages and signed/notarized macOS installers; these installation instructions do not change subscription entitlements. - URL: https://docs.langdock.com/en/admin/desktop-app/deploy.md - Locator: Windows machine-wide MSIX/Intune; macOS PKG/DMG/Jamf/Kandji; HTTP200 Markdown re-read2026-10-21 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:mobile-rev2 Mobile App. HTTP200 Markdown introduction links official Apple App Store and Google Play mobile clients. - URL: https://docs.langdock.com/en/using-langdock/mobile-app/introduction.md - Locator: Download routes - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:desktop-product Langdock Desktop. Windows/macOS desktop clients use the same workspace and approved models as web. - URL: https://langdock.com/products/desktop - Locator: Downloads and Q&A - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:mobile-product Langdock Mobile. Vendor mobile page offers iOS/Android clients using the workspace-approved models. - URL: https://langdock.com/mobile - Locator: App Store/Google Play links and Q&A - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:teams How to use the Teams Bot. Teams has personal bot chats and channel threads with team participation. - URL: https://docs.langdock.com/en/using-langdock/guides/chatbots/teams-bot.md - Locator: Private chats, channels and admin install - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:teams-20261026 How to use the Teams Bot. The public Markdown guide was retrieved with HTTP 200. A workspace admin installs the Teams app, which supports private bot chat and channel threads using @Langdock; it is separate from the web chat history. - URL: https://docs.langdock.com/en/using-langdock/guides/chatbots/teams-bot.md - Locator: Installation note; Two Ways to Use the Teams Bot; Private Chat; Using Langdock in Channels; Limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### 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 ### langdock:langdock:editor Document Editor. Document Editor replaces Canvas and exports Markdown, Word and PDF; imported Word/PDF cannot be edited directly there. - URL: https://docs.langdock.com/en/using-langdock/chat/document-editor.md - Locator: Editor, AI edits, export and limitations - 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 ### langdock:langdock:images Image Generation. Chat invokes configured image-generation models with a user model selector. - URL: https://docs.langdock.com/en/using-langdock/chat/tools/image-generation.md - Locator: Generating images and model choice - 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 ### langdock:langdock:analysis Using Langdock for Data Analysis. Tabular analysis produces charts and downloadable spreadsheet and document formats. - URL: https://docs.langdock.com/en/using-langdock/guides/data-analysis.md - Locator: Analysis procedure and outputs - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:projects Projects. Shared projects expose all project chats/files to members and can be shared with users/groups, not the whole workspace. - URL: https://docs.langdock.com/en/using-langdock/chat/projects.md - Locator: Project sharing and permissions - 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 ### langdock:langdock:saml https://docs.langdock.com/en/admin/security/saml/saml.md. SAML 2.0 requires a verified domain; MFA comes from the IdP rather than standalone Langdock MFA. - URL: https://docs.langdock.com/en/admin/security/saml/saml.md - Locator: Checklist, supported IdPs, external authentication and MFA - 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 ### langdock:langdock:scim https://docs.langdock.com/en/admin/security/scim/scim.md. SCIM 2.0 supports Entra provisioning after SAML setup and domain verification. - URL: https://docs.langdock.com/en/admin/security/scim/scim.md - Locator: Overview and prerequisites - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:scim-entra https://docs.langdock.com/en/admin/security/scim/entra.md. Entra target actions control provisioning/deactivation and group synchronization. - URL: https://docs.langdock.com/en/admin/security/scim/entra.md - Locator: Target Object Actions and optional group synchronization - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:leaver Unassign Agents. Agents whose owner is deactivated keep functioning but cannot be edited until reassigned. - URL: https://docs.langdock.com/en/admin/manage-agents/unassign-agents.md - Locator: Unassigned agents and reassignment - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:exports Usage Exports. Usage CSV exports span users, agents, keys, projects, models and workflows, with user-detail privacy controls. - URL: https://docs.langdock.com/en/admin/compliance-and-governance/usage-exports.md - Locator: Export data types, limits and user-level data - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:byok-limits Usage and spend limits. BYOK cost limits depend on configured prices and exclude backbone, workflows and workspace API usage. - URL: https://docs.langdock.com/en/admin/manage-usage/byok/usage-limits.md - Locator: Scope, unpriced models and spend limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:workflow-limits Workflow limits. Workflow AI use has a separate workspace EUR limit and per-workflow USD limits that block new runs. - URL: https://docs.langdock.com/en/admin/manage-workflows/spend-limits.md - Locator: Spend limits and execution step cap - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:audit Audit Logs API Overview. Audit events retain 90 days and are retrievable by a dedicated-scope admin API for SIEM ingestion. - URL: https://docs.langdock.com/en/developer/audit-logs-api/intro-to-audit-logs-api.md - Locator: Event schema, retention and prerequisites - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:compliance-rev2 Export tool parameters and outputs. Cloud Compliance API is workspace-enable­ment gated; dedicated deployments serve it unless disabled. Conversation exports include messages and tool inputs/outputs only with both explicit flags. - URL: https://docs.langdock.com/en/developer/compliance-api/export-tool-results.md - Locator: Before You Start, parameters and conversation endpoints; HTTP200 Markdown re-read2026-10-21 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:compliance-rev2-20261026 Export tool parameters and outputs. Cloud Compliance API is workspace-enable­ment gated; dedicated deployments serve it unless disabled. Conversation exports include messages and tool inputs/outputs only with both explicit flags. - URL: https://docs.langdock.com/en/developer/compliance-api/export-tool-results.md - Locator: Before You Start, parameters and conversation endpoints; HTTP200 Markdown re-read2026-10-21 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:audit-20261026 Audit Logs API Overview. Audit events retain 90 days and are retrievable by a dedicated-scope admin API for SIEM ingestion. - URL: https://docs.langdock.com/en/developer/audit-logs-api/intro-to-audit-logs-api.md - Locator: Event schema, retention and prerequisites - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:workspace-20261026 Workspace Settings. Workspace settings define retention, model defaults, EU-only default enablement, analytics and product controls. - URL: https://docs.langdock.com/en/admin/workspace/workspace.md - Locator: Product Settings, Models, Analytics and Customizations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:gov Compliance Rules. Custom agent compliance checks produce pass/fail and severity results with per-rule analytics. - URL: https://docs.langdock.com/en/admin/governance/compliance-rules.md - Locator: Rule operation, failures and analytics - 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 ### langdock:langdock:security security. Default Azure EU SaaS, managed dedicated from 2000 and customer-cloud/on-premise from 5000 seats are advertised. - URL: https://langdock.com/security - Locator: Deployment, security, BYOK and certifications - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:dpa Data Processing Agreement | Langdock. DPA 2.1 defines third-country instructions, subprocessor notice and deletion/export rules, with an embedded provider table. - URL: https://langdock.com/dpa - Locator: Sections 7-12 and Appendices 1/2 - Evidence kind: documented - Source date: Not stated - 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 ### langdock:langdock:terms-rev2 Terms of Use | Langdock. Microsoft Azure routes use Modified Abuse Monitoring, disabling provider prompt/output retention and human abuse review. Other provider/model routes require separate assessment. - URL: https://langdock.com/terms - Locator: Section9 and Appendix1 Microsoft Azure service terms - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:retention How long are files saved in Langdock?. Deleted chats are immediately unavailable and unreferenced files are cleaned overnight; shared file references survive. - URL: https://docs.langdock.com/en/using-langdock/troubleshooting/faq/data-retention-for-files.md - Locator: Retention by object type - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:legal https://docs.langdock.com/en/admin/compliance-and-governance/legal-compliance.md. DPA applies automatically and a Professional Secrecy Addendum and certificates are linked from the Trust Center. - URL: https://docs.langdock.com/en/admin/compliance-and-governance/legal-compliance.md - Locator: Legal and compliance links - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:ip IP Restrictions. CIDR allowlists immediately block unauthorized network access when enabled. - URL: https://docs.langdock.com/en/admin/security/ip-restrictions.md - Locator: Prerequisites and enforcement - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:pricing-rev2 Pricing Plans | Langdock. The page maps Business to up to1000 users and Enterprise to1000+; the Standard headline and breakdown disagree, so no applicable Standard/BYOK tariff is established here. - URL: https://langdock.com/pricing - Locator: Business/Enterprise cards; price breakdown; product add-ons - 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 ### langdock:langdock: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 ### langdock:langdock:migration Agent Migration Guide. Agent API export/import preserves selected configuration; files/skills and some fields require separate migration. - URL: https://docs.langdock.com/en/developer/agents-api/agent-migration.md - Locator: Prerequisites, exported settings and field mapping - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:dpa-20261026 Data Processing Agreement | Langdock. DPA 2.1 defines third-country instructions, subprocessor notice and deletion/export rules, with an embedded provider table. - URL: https://langdock.com/dpa - Locator: Sections 7-12 and Appendices 1/2 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:migration-20261026 Agent Migration Guide. Agent API export/import preserves selected configuration; files/skills and some fields require separate migration. - URL: https://docs.langdock.com/en/developer/agents-api/agent-migration.md - Locator: Prerequisites, exported settings and field mapping - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:knowledge-20261026 Knowledge bases. The public Markdown guide was retrieved with HTTP 200. The Knowledge Folder API can upload, update, delete, retrieve and search files; Viewer supports retrieval, while writes need Editor. This does not establish a complete index/ACL workspace export bundle. - URL: https://docs.langdock.com/en/using-langdock/library/knowledge-bases.md - Locator: Create a Knowledge base and add documents, API upload; Share search access; Convert a Knowledge base to a folder - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:exports-20261026 Usage Exports. The public Markdown guide was retrieved with HTTP 200. Workspace administrators can export usage analytics as CSV or through the Usage Export API, with up to 12 months of history and JSON-valued mapping fields. Usage analytics are distinct from a complete chat/knowledge export. - URL: https://docs.langdock.com/en/admin/compliance-and-governance/usage-exports.md - Locator: Accessing Usage Exports; Export Limits; Export Data Structure; Usage Exports; Data Retention - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### 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 ### langdock:langdock:playbook Rollout Playbook. Dedicated rollout support/workshops start at 250 licences and include a champion approach. - URL: https://docs.langdock.com/en/admin/ai-adoption-and-rollout/getting-started/rollout-playbook.md - Locator: Programme qualification and rollout phases - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:status status. The public status page covers the app, APIs, Workflows and Integrations with history. - URL: https://status.langdock.com/ - Locator: Components and history - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:terms-20261026 Terms of Use | Langdock. Terms 2.1 prohibit training and describe provider-specific residency and retention agreements, proprietary use rights and contract defaults. - URL: https://langdock.com/terms - Locator: Sections 6/7/9/12/15/16/19 and Appendix 1 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:imprint-20261026 Langdock imprint and contact point. Users and authorities can contact support@langdock.com in German and English; the imprint identifies Langdock GmbH in Berlin. - URL: https://langdock.com/imprint - Locator: Contact Point for Users and Authorities - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:status-20261026 status. The public status page covers the app, APIs, Workflows and Integrations with history. - URL: https://status.langdock.com/ - Locator: Components and history - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:training Langdock Workshops. Official workshop recordings/slides cover chat, skills, integrations, agents and workflows. - URL: https://docs.langdock.com/en/using-langdock/resources/langdock-workshops.md - Locator: Workshop catalogue - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21