--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/langdock-vs-meingpt/" data_url: "https://onaihq.com/compare/agents/langdock-vs-meingpt/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" --- # Langdock vs meinGPT > 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 47 criteria with sourced findings for both products, including 47 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. - Langdock source checks: 2026-10-21 to 2026-10-26. - meinGPT source checks: 2026-10-21 to 2026-10-26. - Canonical HTML: https://onaihq.com/compare/agents/langdock-vs-meingpt/ - Machine-readable JSON: https://onaihq.com/compare/agents/langdock-vs-meingpt/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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Curated multi-provider models are selected per chat or by context-length routing; the signed DPA and admin approvals affect availability. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Business and individually contracted Enterprise web workspace; permitted models depend on workspace approval and DPA; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - auto_routing: Bestes Modell starts with GPT-5 and changes to Gemini 3.5 Flash-Lite only when context is too long. This is length routing, not task routing; visibility of the final routed identity is not established. - providers — Which model providers are available? [supported]: Model authors include OpenAI, Anthropic, Google, Mistral, DeepSeek, Moonshot, Qwen, GLM and MiniMax. Hosts are separate from authors. Sources: meingpt:meingpt:models-rev2, meingpt:meingpt:lifecycle-rev2. - current_models — Which current models are selectable on this plan? [supported]: Active table lists GPT-4.1, GPT-4o/Mini, GPT-5/mini/Nano/Thinking/5.2/5.4/5.5/5.6 Luna/Sol/Terra, GPT-6 Luna/Sol/Astra, GPT-6.1 Sol; o3; Claude Haiku 5.5, Opus 4.5/4.6/4.7/4.8/5/5.5, Sonnet 4.6/5/5.5; Gemini 3.5 Flash/Flash-Lite, 3.6/3.7/3.8 Flash and 4 Argon; MeinGPT Web; Mistral Medium 3.5/CodeStral; GPT-OSS 120B; Kimi K2.6/K3; DeepSeek V3.2/V4 Flash/V4 Pro/V4.1 Flash; GLM-5.3/Flash, MiniMax-M3 and Qwen3.8 Max. Duplicate EU/provider routes exist. GPT-6 Astra requires accepted AVV 2.0. Model labels do not guarantee one-to-one public provider variant names. Sources: meingpt:meingpt:lifecycle-rev2, meingpt:meingpt:models-rev2, meingpt:meingpt:rates. - user_choice — Can users pick the model per chat? [supported]: Users select and switch a permitted model per chat. Sources: meingpt:meingpt:models-rev2. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [partial]: Bestes Modell starts with GPT-5 and changes to Gemini 3.5 Flash-Lite only when context is too long. This is length routing, not task routing; visibility of the final routed identity is not established. Sources: meingpt:meingpt:models-rev2. - multimodal_input — Which models accept images, audio or files? [supported]: GPT-4o/5, Claude, Gemini and Mistral Medium/Magistral accept JPEG/PNG/GIF/WEBP; DeepSeek, GPT-OSS, CodeStral and older Kimi K2 do not. Audio uses separate transcription. Sources: meingpt:meingpt:models-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:models-rev2, meingpt:meingpt:lifecycle-rev2, meingpt:meingpt:rates ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial A dated changelog and explicit retirement rules exist; comparative release-lag medians were not established. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - version_pinning: An available model can be selected, but retirement automatically substitutes a successor in assistants, workflows and chats; indefinite retention of a retired model is excluded. - Unverified release_lag_days: Provider release dates for the last three major releases per provider were not reconciled against product release dates, so no lag or median is asserted. - 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. Provider release dates for the last three major releases per provider were not reconciled against product release dates, so no lag or median is asserted. - changelog — Is there a dated public model changelog? [supported]: Public releases include v2.67.0 dated 2026-10-18. Sources: meingpt:meingpt:changes. - deprecation_notice — How much notice is given before a model is removed? [supported]: Normally four weeks, then reminders at two and one week; provider short notice can shorten this. Opus 4.5 is listed for 23 November retirement; other future dates are in the table. Sources: meingpt:meingpt:lifecycle. - version_pinning — Can an admin keep an older model version? [partial]: An available model can be selected, but retirement automatically substitutes a successor in assistants, workflows and chats; indefinite retention of a retired model is excluded. Sources: meingpt:meingpt:lifecycle. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:changes, meingpt:meingpt:lifecycle ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Customer LLM API keys, cloud contracts and arbitrary model endpoints are explicitly excluded from the hosted catalogue. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - own_api_keys: The hosted workspace does not accept customer OpenAI, Azure OpenAI or Anthropic keys. DeepL translation BYOK is separate. - own_cloud_contract: LLM requests use meinGPT-managed provider accounts, not customer Azure/OpenAI contracts. - custom_endpoint: Admins cannot add a model or provider key to the catalogue. Custom MCP adds tools, not LLM endpoints. - byo_pricing: There is no hosted LLM BYOK licence schedule because LLM BYOK is excluded. DeepL BYOK bills translation directly through DeepL. - byo_restrictions: Only DeepL has a documented BYOK exception; it does not replace the workspace model route. - own_api_keys — Can the customer use its own provider API keys? [unsupported]: The hosted workspace does not accept customer OpenAI, Azure OpenAI or Anthropic keys. DeepL translation BYOK is separate. Sources: meingpt:meingpt:models. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [unsupported]: LLM requests use meinGPT-managed provider accounts, not customer Azure/OpenAI contracts. Sources: meingpt:meingpt:models. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [unsupported]: Admins cannot add a model or provider key to the catalogue. Custom MCP adds tools, not LLM endpoints. Sources: meingpt:meingpt:models. - byo_pricing — Does BYO change the licence price? [partial]: There is no hosted LLM BYOK licence schedule because LLM BYOK is excluded. DeepL BYOK bills translation directly through DeepL. Sources: meingpt:meingpt:models, meingpt:meingpt:translation. - byo_restrictions — Which features stop working with BYO? [partial]: Only DeepL has a documented BYOK exception; it does not replace the workspace model route. Sources: meingpt:meingpt:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:models, meingpt:meingpt:translation ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Vendor-operated open-model routes exist; customer-hosted LLM and embedding routes were not verified. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - vendor_hosted_open_models: Open-weight routes include GPT-OSS via Nebius in Finland, DeepSeek/Kimi via TensorX in Ireland and custom models via Verda in Finland; the active table also lists Melious routes. These are vendor-selected routes, with exact region absent for Melious. - Unverified self_hosted_chat, self_hosted_embeddings, feature_parity: Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference. - self_hosted_chat — Can chat use a customer-hosted model? [unknown]: Can chat use a customer-hosted model? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [unknown]: Can retrieval use customer-hosted embeddings? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference. - feature_parity — Which features fail with self-hosted models? [unknown]: Which features fail with self-hosted models? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [partial]: Open-weight routes include GPT-OSS via Nebius in Finland, DeepSeek/Kimi via TensorX in Ireland and custom models via Verda in Finland; the active table also lists Melious routes. These are vendor-selected routes, with exact region absent for Melious. Sources: meingpt:meingpt:lifecycle, meingpt:meingpt:subprocessors. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:lifecycle, meingpt:meingpt:subprocessors ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Admins set model access and defaults; personal category limits have documented exceptions. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - limit_behaviour: Zero blocks the category; API budget exhaustion returns 403. Running/concurrent meeting recordings can exceed personal limits; scheduled tasks consume workspace credit outside personal categories. - Unverified data_bound_models: A separate rule binding particular knowledge sources to approved models was not documented; no two-user restriction test was run. - model_allowlist_by_group — Can admins limit models per group? [supported]: Per-team/person allow and deny rules are documented. Workspace admins and free models are exempt; denied chat models fall back, denied API models fail. Sources: meingpt:meingpt:config. - 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. A separate rule binding particular knowledge sources to approved models was not documented; no two-user restriction test was run. - default_model — Can admins set the default model? [supported]: Workspace admins set the default model and chat standards. Sources: meingpt:meingpt:config. - user_limits — What per-user message or token limits apply, and are they published? [supported]: Six usage levels set monthly EUR limits for text, images, API, other services and meeting bots; no single universal message cap. Sources: meingpt:meingpt:limits. - limit_behaviour — What happens when a limit is reached? [partial]: Zero blocks the category; API budget exhaustion returns 403. Running/concurrent meeting recordings can exceed personal limits; scheduled tasks consume workspace credit outside personal categories. Sources: meingpt:meingpt:limits, meingpt:meingpt:api. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:config, meingpt:meingpt:limits, meingpt:meingpt:api ## 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Chat uploads and direct sandbox processing have different document behavior. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - spreadsheets: Text extraction loses layout; the sandbox reads original Excel files using code and can preserve formulas. No fixture result is claimed. - full_vs_chunked: Direct attachments enter model context after extraction and are constrained by the context window; pools retrieve passages instead. Long-chat compression can drop earlier attachment context. - Unverified ocr: No scanned contract or structured spreadsheet fixture was uploaded; OCR behavior for direct scanned attachments was not bounded by a test. - formats — Which formats are accepted? [supported]: Text/PDF, images, Word, PowerPoint, Excel, CSV, TXT and URLs are listed; sandbox is needed to read archives and raw mail formats. Sources: meingpt:meingpt:flow. - limits — What size and count limits apply per file and chat? [supported]: 50 files per chat, 50 MB per non-image file; JPEG/PNG/WEBP/GIF are model-readable images. Provider PDF/page/image limits still apply. Sources: meingpt:meingpt:chat, meingpt:meingpt:models. - ocr — Are scanned PDFs read? [unknown]: Are scanned PDFs read? Unknown. No scanned contract or structured spreadsheet fixture was uploaded; OCR behavior for direct scanned attachments was not bounded by a test. - spreadsheets — Are Excel tables read with structure intact? [partial]: Text extraction loses layout; the sandbox reads original Excel files using code and can preserve formulas. No fixture result is claimed. Sources: meingpt:meingpt:chat, meingpt:meingpt:sandbox. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [partial]: Direct attachments enter model context after extraction and are constrained by the context window; pools retrieve passages instead. Long-chat compression can drop earlier attachment context. Sources: meingpt:meingpt:chat, meingpt:meingpt:models, meingpt:meingpt:pools. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:flow, meingpt:meingpt:chat, meingpt:meingpt:models, meingpt:meingpt:sandbox, meingpt:meingpt:pools ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: supported Cloud pools persist across chats and attach to assistants; Outpost is a separate local index. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. - persistent_collections — Can users keep document collections across chats? [supported]: Persistent cloud data sources index SharePoint/OneDrive, Drive, Confluence, S3, WebDAV and web content. Sources: meingpt:meingpt:pools. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: Admins share data sources with teams; workspace admins have broad visibility. Sources: meingpt:meingpt:pools. - size_limits — What are the collection limits? [supported]: Standard cloud raw-data budget is 300 GB across the workspace; indexing new content stops when full. Sources: meingpt:meingpt:pools. - assistant_binding — Can collections be bound to an assistant? [supported]: Pools bind to assistants or can be selected in a chat; projects themselves cannot bind pools. Sources: meingpt:meingpt:assistants, meingpt:meingpt:projects. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pools, meingpt:meingpt:assistants, meingpt:meingpt:projects ### 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). #### 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 #### meinGPT 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. ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Live OAuth preserves source access; indexed permissions require a separate, default-off setting. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - source_permissions_respected: Live M365 tools use each user account. Cloud SharePoint/Drive pools enforce imported source permissions only when request-enabled and switched on; other source types do not inherit them. No two-user test was run. - Unverified revocation_delay, sensitivity_labels: No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown. - source_permissions_respected — Are source permissions enforced per user? [partial]: Live M365 tools use each user account. Cloud SharePoint/Drive pools enforce imported source permissions only when request-enabled and switched on; other source types do not inherit them. No two-user test was run. Sources: meingpt:meingpt:m365, meingpt:meingpt:pool-controls. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: Live tools execute under user OAuth. Indexed SharePoint/Drive permissions are mirrored and fail closed when stale; source-permission mode is off by default. Sources: meingpt:meingpt:pool-controls. - revocation_delay — How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? Unknown. No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown. - admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins select imported sources/folders and control team sharing. Sources: meingpt:meingpt:pools. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? Unknown. No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:m365, meingpt:meingpt:pool-controls, meingpt:meingpt:pools ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Live connectors query the source; cloud pools copy an index to Germany. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - Unverified deletion_propagation: No edit/delete fixture was run and an end-to-end deletion-propagation bound was not verified. - live_or_indexed — Is content searched live or copied into an index? [supported]: Native connectors fetch live; cloud data pools index imported documents. Sources: meingpt:meingpt:pools. - sync_interval — How often does an index refresh? [supported]: Cloud import runs every 15 minutes. Sources: meingpt:meingpt:pools. - deletion_propagation — How quickly does a deleted document disappear? [unknown]: How quickly does a deleted document disappear? Unknown. No edit/delete fixture was run and an end-to-end deletion-propagation bound was not verified. - index_location — Where is indexed content stored? [supported]: Cloud pools run at Hetzner in Germany; local Outpost pools stay in the customer network. Sources: meingpt:meingpt:pools. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pools ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Source display is documented; grounding quality remains untested. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - no_answer_behaviour: The guide says source search reports no matching result; actual refusals were not tested. - Unverified citation_accuracy, cross_language, observed_accuracy: The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown. - citations — Are answers linked to specific sources? [supported]: Cloud source answers always display sources and this cannot be disabled. Sources: meingpt:meingpt:pool-controls. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are 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. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown. - no_answer_behaviour — Does it say when the corpus has no answer? [partial]: The guide says source search reports no matching result; actual refusals were not tested. Sources: meingpt:meingpt:pools. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pool-controls, meingpt:meingpt:pools ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Personal instructions and user-specific assistant memory are documented. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - user_memory_controls: Users view and delete one/all memories; direct editing is unavailable in settings, but an assistant can update entries. - custom_instructions — Can users set persistent instructions? [supported]: Preferences store a persistent system instruction applied with workspace and assistant context. Sources: meingpt:meingpt:preferences. - cross_chat_memory — Does the product remember facts across chats? [supported]: Enabled assistants share a personal user memory store across chats, not a team store. Sources: meingpt:meingpt:memory. - user_memory_controls — Can users view, edit and delete memories? [partial]: Users view and delete one/all memories; direct editing is unavailable in settings, but an assistant can update entries. Sources: meingpt:meingpt:memory. - admin_memory_controls — Can admins turn memory off? [supported]: Admins can disable or remove Memory from the permitted tools. Sources: meingpt:meingpt:memory. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:preferences, meingpt:meingpt:memory ## Assistants and agents ### AGT-01: Custom assistants Judgment rule: Record creation of assistants with instructions, model, knowledge and tools; who can create; sharing scope; versioning; and an internal catalogue or directory. Build one HR policy assistant on the fixture and share it with one group. Prompt templates and a prompt library are recorded here. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: supported Assistants combine model, instructions, tools and knowledge, with governed creation and sharing. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: The editor supports instructions, model, files, pools, connectors and built-in tools. Sources: meingpt:meingpt:assistants. - creator_permissions — Can admins limit who creates them? [supported]: Request-enabled permissions restrict assistant creation/sharing/publication by team or person; admins are exempt. Sources: meingpt:meingpt:permissions. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Team and direct-person assistant sharing are documented; workspace-wide publication is admin-only by default. Sources: meingpt:meingpt:permissions, meingpt:meingpt:roles. - catalogue — Is there an internal assistant directory? [supported]: The navigation lists personal assistants and shared resources. Sources: meingpt:meingpt:assistants. - prompt_library — Are shared prompt templates available? [supported]: Prompt folders can be personal, workspace or department scoped. Sources: meingpt:meingpt:prompts. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:assistants, meingpt:meingpt:permissions, meingpt:meingpt:roles, meingpt:meingpt:prompts ### 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. #### 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 #### meinGPT 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. ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: supported Linkup powers cited web search and Deep Research; admins can restrict app access. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. - web_search — Is web search available? [supported]: Search can be switched on in chat, is always on in MeinGPT Web and runs in the Recherche app. Sources: meingpt:meingpt:web. - admin_toggle — Can admins disable it per organisation or group? [supported]: Request-enabled per-team/person app controls include Web search. Sources: meingpt:meingpt:permissions. - search_provider — Which search provider handles queries, and where? [supported]: Linkup processes search; the register lists Azure France. Prompt terms can enter generated search queries. Sources: meingpt:meingpt:web, meingpt:meingpt:subprocessors. - deep_research — Is multi-step research with a report available? [supported]: The research app has a user-controlled multi-step Deep Research mode. Sources: meingpt:meingpt:web. - web_citations — Are web sources cited? [supported]: Results include source previews and page references. Sources: meingpt:meingpt:web. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:web, meingpt:meingpt:permissions, meingpt:meingpt:subprocessors ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: supported Multi-step workflows are documented; scheduled/event automations are request-enabled beta. Availability: beta Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - Workflow editor is documented separately from request-enabled beta scheduled tasks; beta is not universal plan availability. - workflow_builder — Is there a workflow or chain builder? [supported]: A project editor chains prompts with variables and per-step models, or Buddy drafts the workflow. Sources: meingpt:meingpt:workflows. - scheduled_tasks — Can prompts or assistants run on a schedule? [supported]: Support enables beta tasks with daily, weekly, monthly or selected calendar schedules. Sources: meingpt:meingpt:scheduled. - event_triggers — Can external events start a workflow? [supported]: Beta tasks accept tokenized webhooks and task-specific email addresses. Sources: meingpt:meingpt:scheduled. - builder_audience — Is building aimed at business users, IT or developers? [supported]: Members can build with natural-language Buddy help or manual steps, subject to admin rights. Sources: meingpt:meingpt:workflows. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:workflows, meingpt:meingpt:scheduled ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Assistants can execute successive tool calls, show progress and stop; per-action confirmation is absent. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - side_effect_confirmation: No built-in method-specific permission popup exists at runtime; admin-approved write/dangerous methods can run without an additional dialog. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: Assistant tools run multiple sequential steps within a response and stop at a bounded tool-call budget. Sources: meingpt:meingpt:assistants. - visible_steps — Are steps and tool calls shown? [supported]: Tool/reasoning steps and progress are shown in chat. Sources: meingpt:meingpt:assistants, meingpt:meingpt:chat. - side_effect_confirmation — Must the user confirm actions with side effects? [unsupported]: No built-in method-specific permission popup exists at runtime; admin-approved write/dangerous methods can run without an additional dialog. Sources: meingpt:meingpt:tools. - stop_control — Can the user stop a running task? [supported]: The input button changes to Abbrechen and stops response generation while preserving text. Sources: meingpt:meingpt:chat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:assistants, meingpt:meingpt:chat, meingpt:meingpt:tools ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise-enabled APIs cover chat, assistants and workflows with model and budget enforcement. Availability: generally-available Delivery: native Scope: surfaces=meinGPT Enterprise API; version=Public documentation checked 2026-10-21; plan=Enterprise API, explicitly enabled; no public add-on price; add_ons=Enterprise API; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - api_governance: Model permission failures return 403; API has a separate personal budget and shared token-rate ceilings; compliance-content logging coverage was not fully established. - Unverified knowledge_api, mcp_server: A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide. - chat_api — Is there an API for chat and assistants? [supported]: Bearer-key chat completions, assistants, workflow runs, embeddings and transcription are documented; personal keys require Enterprise enablement. Sources: meingpt:meingpt:api, meingpt:meingpt:outlook. - knowledge_api — Can documents be loaded through an API? [unknown]: Can documents be loaded through an API? Unknown. A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: Model permission failures return 403; API has a separate personal budget and shared token-rate ceilings; compliance-content logging coverage was not fully established. Sources: meingpt:meingpt:api, meingpt:meingpt:config, meingpt:meingpt:audit. - mcp_server — Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? Unknown. A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:api, meingpt:meingpt:outlook, meingpt:meingpt:config, meingpt:meingpt:audit ## 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The platform is browser-based; Outlook has a separate centrally deployed add-in. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace, meinGPT Outlook add-in, meinGPT Enterprise API; version=Public documentation checked 2026-10-21; plan=Business/Enterprise web workspace; Outlook add-in requires Enterprise API enablement and personal API key; add_ons=Enterprise API enabled for Outlook add-in; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - managed_deployment: The Outlook add-in can be assigned to users or groups in Microsoft 365 integrated apps; general desktop/mobile MDM configuration was not found. - Unverified desktop_apps, mobile_apps, browser_extension, client_feature_gaps: No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested. - web — Is a full web client available? [supported]: The terms define a browser-accessible workspace. Sources: meingpt:meingpt:terms. - desktop_apps — Windows and macOS apps? [unknown]: Windows and macOS apps? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested. - mobile_apps — iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested. - managed_deployment — Can IT deploy and configure clients through MDM? [partial]: The Enterprise API-enabled Outlook add-in can be assigned to users/groups through Microsoft365 integrated apps. It supports Outlook web, Windows classic/new and Mac; each user needs a personal meinGPT API key. General desktop/mobile MDM configuration was not established. Sources: meingpt:meingpt:outlook. - client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:terms, meingpt:meingpt:outlook ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial A documented Outlook add-in operates in the received-message view and needs Enterprise API access. Availability: generally-available Delivery: native Scope: surfaces=meinGPT Outlook add-in; version=Public documentation checked 2026-10-21; plan=Enterprise API enabled workspace; add_ons=Enterprise API; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - licence_prerequisites: Personal meinGPT API key and Enterprise API enablement are required; tenant admins can centrally deploy the add-in. A separate Microsoft licence price is not stated. - Unverified word_excel_powerpoint, teams, google_workspace_apps: Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03. - word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [unknown]: Does it work inside Word, Excel and PowerPoint? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03. - outlook — Does it work inside Outlook? [supported]: Outlook Web, Windows classic/new and Mac support summarizing the selected received email and drafting replies; compose view is excluded. Sources: meingpt:meingpt:outlook. - teams — Is there a Teams app or bot? [unknown]: Is there a Teams app or bot? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03. - google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03. - licence_prerequisites — Which licences or consents are needed? [partial]: Personal meinGPT API key and Enterprise API enablement are required; tenant admins can centrally deploy the add-in. A separate Microsoft licence price is not stated. Sources: meingpt:meingpt:outlook. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:outlook ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dedicated text/document translation uses EU Google/DeepL routes and managed glossaries. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - document_translation: DeepL document translation preserves layout for DOC/DOCX, PPT/PPTX, XLS/XLSX, PDF, HTML, TXT, SRT and XLIFF. Layout quality was not fixture-tested. - writing_tools: Quick Actions rewrite answers, including more formal and improve options. - Unverified formality_and_variants: Formality settings within the translator and guaranteed de-CH spelling were not established; no DE-to-FR/IT contract fixture was translated. - document_translation — Can whole documents be translated with formatting kept? [partial]: DeepL document translation preserves layout for DOC/DOCX, PPT/PPTX, XLS/XLSX, PDF, HTML, TXT, SRT and XLIFF. Layout quality was not fixture-tested. Sources: meingpt:meingpt:translation. - translation_engine — Which engine translates? [supported]: Default Google Cloud Translate for text and DeepL for documents; own DeepL key switches both to DeepL. Sources: meingpt:meingpt:translation. - glossaries — Are company glossaries supported? [supported]: Workspace admins create per-language-pair glossaries and import CSV; exact word forms must match. Sources: meingpt:meingpt:translation. - formality_and_variants — Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Unknown. Formality settings within the translator and guaranteed de-CH spelling were not established; no DE-to-FR/IT contract fixture was translated. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Quick Actions rewrite answers, including more formal and improve options. Sources: meingpt:meingpt:chat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:translation, meingpt:meingpt:chat ### WORK-04: Image generation and editing Judgment rule: Record available image models, editing (inpainting, reference images), admin control and per-image cost visibility, and licence or usage terms for generated images. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Twelve named image variants include reference editing with administrator model controls. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - image_editing: Reference image generation supports model-dependent uploads; app lacks post-generation crop/color editing. - usage_terms: Terms warn third-party output may carry rights; no blanket unrestricted-use warranty is made. C2PA metadata labels generated output. - image_generation — Can users generate images, with which models? [supported]: FLUX.2 Klein/Pro/Flex/Max, FLUX 1.1 Pro, FLUX.1 Kontext Max; GPT Image 1/Mini/1.5/2; Gemini 2.5 Flash Image and 3 Pro Image. Sources: meingpt:meingpt:images. - image_editing — Can users edit uploaded images? [partial]: Reference image generation supports model-dependent uploads; app lacks post-generation crop/color editing. Sources: meingpt:meingpt:images. - admin_control — Can admins restrict image generation? [supported]: Admins enable models and default; request-enabled permissions can restrict Image app use by teams or persons. Sources: meingpt:meingpt:image-admin, meingpt:meingpt:permissions. - usage_terms — What usage rights apply to output? [partial]: Terms warn third-party output may carry rights; no blanket unrestricted-use warranty is made. C2PA metadata labels generated output. Sources: meingpt:meingpt:terms, meingpt:meingpt:images. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:images, meingpt:meingpt:image-admin, meingpt:meingpt:permissions, meingpt:meingpt: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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dictation and meeting transcription are documented; speech quality was not tested. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - Unverified read_aloud, voice_conversation, swiss_german_speech: No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established. - dictation — Can users dictate prompts? [supported]: A microphone transcribes prompts into the input field. Sources: meingpt:meingpt:chat. - read_aloud — Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established. - meeting_summaries — Are meetings transcribed and summarised? [supported]: Audio/video/transcript uploads and meeting-bot notes are documented; storage Hetzner Germany, Gladia transcription France, Vertex EU summaries. Sources: meingpt:meingpt:meeting. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:chat, meingpt:meingpt:meeting ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial An isolated EU sandbox executes analysis code and generates downloadable Office files. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - canvas_editing: Downloaded artifacts and an Excel editor exist; editor changes stay local until downloaded and the chat card keeps the original. - data_analysis — Can it analyse spreadsheets with executed code? [supported]: Python/JavaScript sandbox reads original spreadsheets with pandas/openpyxl and executes code. Sources: meingpt:meingpt:sandbox. - charts — Can it produce charts? [supported]: Executed matplotlib charts can be returned as PNG. Sources: meingpt:meingpt:sandbox. - office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: Sandbox libraries support DOCX/XLSX/PPTX; workflows also generate Word/PDF/Excel/CSV/PowerPoint/JSON. Sources: meingpt:meingpt:sandbox, meingpt:meingpt:workflows. - canvas_editing — Is there a document or canvas editor for iterating on output? [partial]: Downloaded artifacts and an Excel editor exist; editor changes stay local until downloaded and the chat card keeps the original. Sources: meingpt:meingpt:sandbox. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:sandbox, meingpt:meingpt:workflows ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Chat links and shared projects exist; projects preserve private member chat histories. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - group_chat: Each project member has a separate private chat list; shared project chats are not a simultaneous group conversation. - Unverified share_permission_boundary: No cross-group chat-sharing test was run; recipient access to source attachments and restricted knowledge was not verified. - Project chat privacy does not prove absence of every group-chat surface. - share_chats — Can chats be shared inside the organisation? [supported]: A share toggle creates a link displaying the shared conversation. Sources: meingpt:meingpt:chat. - team_spaces — Are shared projects or workspaces available? [supported]: Projects share instructions and workflows with Owner/Editor/Member roles. Sources: meingpt:meingpt:projects. - group_chat — Can several people chat together with the AI? [partial]: Within Projects,each member has a separate private chat list. Simultaneous multi-user group conversation elsewhere was not established. Sources: meingpt:meingpt:projects. - 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 chat-sharing test was run; recipient access to source attachments and restricted knowledge was not verified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:chat, meingpt:meingpt:projects ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Platform-language choice exists, but the full UI and accessibility matrix remains unverified. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - ui_languages: Preferences provide a platform-language selector distinct from response language; a complete named language list is not published on this page. - Unverified dach_language_quality, accessibility_statement, admin_ui_languages: No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested. - ui_languages — Which UI languages are offered? [partial]: Preferences provide a platform-language selector distinct from response language; a complete named language list is not published on this page. Sources: meingpt:meingpt:preferences. - 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 DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested. - admin_ui_languages — Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:preferences ## 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Microsoft/Google login is included; custom OIDC is enabled on request and SAML is excluded. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - sso_plan: Platform pricing includes Microsoft/Google/Magic Link; own OIDC needs workspace enablement, while Governance prices Entra group sync and provisioning. Exact custom-OIDC fee is not stated. - sso_protocols — Which SSO protocols and identity providers work? [supported]: Google and Microsoft sign-in plus custom OpenID Connect for Entra, Keycloak, Okta, PingFederate and Authentik. SAML is not supported. Sources: meingpt:meingpt:sso. - sso_plan — Which plan includes SSO? [partial]: Platform pricing includes Microsoft/Google/Magic Link; own OIDC needs workspace enablement, while Governance prices Entra group sync and provisioning. Exact custom-OIDC fee is not stated. Sources: meingpt:meingpt:sso, meingpt:meingpt:prices. - mfa — Can MFA be enforced? [supported]: MFA is enforced at the customer IdP; disabling a user prevents new sign-ins but does not immediately invalidate an existing session. Sources: meingpt:meingpt:sso. - conditional_access — Do Entra conditional-access policies apply? [supported]: Customer IdP controls Conditional Access. Existing sessions expire normally unless separately removing the membership. Sources: meingpt:meingpt:sso. - domain_capture — Can the company claim its email domain? [supported]: DNS TXT verification enables domain auto-join and optional rejection of invitations into other workspaces; existing external memberships remain. Sources: meingpt:meingpt:sso. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:sso, meingpt:meingpt:prices ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Governance includes SCIM; user provisioning and login-time group sync have separate effects. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform plus Governance provisioning add-on; add_ons=Governance; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - group_sync: Entra group-to-team synchronization is separate from user-only SCIM and adds memberships on login. It is not a general bidirectional SCIM-group sync. - deprovisioning: SCIM deactivates membership, preserves data and releases the seat. Shared-asset transfer behavior was not trial-tested. - scim — Is SCIM provisioning supported? [supported]: Entra SCIM v1 creates/updates/deactivates users, requires a verified domain and workspace enablement, and replaces manual invitations. Sources: meingpt:meingpt:scim, meingpt:meingpt:prices. - group_sync — Are identity-provider groups synced? [partial]: Entra group-to-team synchronization is separate from user-only SCIM and adds memberships on login. It is not a general bidirectional SCIM-group sync. Sources: meingpt:meingpt:scim, meingpt:meingpt:sso. - jit_provisioning — Are users created at first login? [supported]: Custom OIDC can join a verified-domain workspace on first authenticated login; plain Microsoft sign-in alone does not grant workspace membership. Sources: meingpt:meingpt:sso, meingpt:meingpt:scim. - deprovisioning — What happens to a removed user's data and shared assets? [partial]: SCIM deactivates membership, preserves data and releases the seat. Shared-asset transfer behavior was not trial-tested. Sources: meingpt:meingpt:scim. - seat_assignment — Can admins assign and reclaim seats? [supported]: New SCIM users start as unlicensed viewers unless automatic seat assignment is on; admins can assign seats. Sources: meingpt:meingpt:scim. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:scim, meingpt:meingpt:prices, meingpt:meingpt:sso ### ADM-03: Roles, groups and feature permissions Judgment rule: Record admin roles, delegated admins, groups, per-feature permissions (web search, image generation, connectors, file upload, agents), separation of subsidiaries or departments, and enforcement. Test one disabled feature for one group. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Role and group controls include request-enabled app permissions and model restrictions. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - multi_entity: Multiple workspaces can represent separate companies, but each has separate credit and billing; a unified multi-entity contract was not established. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Admin, Member and Viewer; unlimited workspace admins and separate team administrators are documented. Workspace admins consume a seat and bypass restrictions. Sources: meingpt:meingpt:roles, meingpt:meingpt:permissions. - groups — Can permissions be set per group? [supported]: Teams control shared resources and models; admins see all team-shared assets. Sources: meingpt:meingpt:roles, meingpt:meingpt:config. - feature_toggles — Which features can be switched on or off per group? [supported]: Request-enabled controls restrict image, meeting notes/bot, translation, web, Voice Agent, Buddy and automation use by teams or persons. Sources: meingpt:meingpt:permissions. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Multiple workspaces can represent separate companies, but each has separate credit and billing; a unified multi-entity contract was not established. Sources: meingpt:meingpt:sso. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:roles, meingpt:meingpt:permissions, meingpt:meingpt:config, meingpt:meingpt:sso ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Adoption metrics and cost CSVs have team and anonymization options. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - breakdowns: Usage-based plans report costs by user, team, model and platform/API; complete assistant/feature breakdown is not demonstrated. - adoption_dashboard — Is there an adoption dashboard? [supported]: Cockpit lists prompts, active users, daily prompts/workflow runs and popular workflows. Sources: meingpt:meingpt:analytics. - breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Usage-based plans report costs by user, team, model and platform/API; complete assistant/feature breakdown is not demonstrated. Sources: meingpt:meingpt:analytics. - export — Can usage data be exported? [supported]: User/team cost statistics export to CSV. Sources: meingpt:meingpt:analytics. - privacy_modes — Can per-person reporting be limited or pseudonymised? [supported]: Metric anonymization replaces names with IDs; top-user metrics depend on that setting. Sources: meingpt:meingpt:analytics. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:analytics ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Personal category budgets and pooled credit provide controls with documented exceptions. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - budget_enforcement: Zero blocks new category use and API exhaustion returns 403; running meeting bots can overshoot and automated runs are outside personal categories. - chargeback: CSV cost exports exist by user/team; formal cost-centre coding is not established. - cost_visibility — Can admins see cost or consumption per user and group? [supported]: Usage-based plans show EUR costs per user/model and team, separately for platform and API. Sources: meingpt:meingpt:analytics. - budgets — Can budgets be set per user or group? [supported]: Six personal usage levels configure monthly budgets across five categories and are assigned singly or in bulk. Sources: meingpt:meingpt:limits. - budget_enforcement — Does reaching a budget alert, block or downgrade? [partial]: Zero blocks new category use and API exhaustion returns 403; running meeting bots can overshoot and automated runs are outside personal categories. Sources: meingpt:meingpt:limits, meingpt:meingpt:api. - chargeback — Can costs be exported per cost centre? [partial]: CSV cost exports exist by user/team; formal cost-centre coding is not established. Sources: meingpt:meingpt:analytics. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:analytics, meingpt:meingpt:limits, meingpt:meingpt:api ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Administrative change exports and a separate Outpost search log have distinct retention. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - admin_events: Administrative settings and SCIM changes are logged with actor and changes; a login/security-event coverage inventory and tamper-evidence model were not found. - content_logging: The settings-change log explicitly excludes conversation contents; a separate API-logging setting exists but prompt/response compliance-retention coverage is unclear. - siem_export: CSV/JSON filtered audit export, 10000 entries/20 MiB/two minutes per export; SIEM streaming is not established. - Unverified ediscovery: No legal-hold or eDiscovery documentation was located; immutable audit storage and full content-logging configuration were not established. - admin_events — Are admin and security events logged? [partial]: Administrative settings and SCIM changes are logged with actor and changes; a login/security-event coverage inventory and tamper-evidence model were not found. Sources: meingpt:meingpt:audit, meingpt:meingpt:scim. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [partial]: The settings-change log explicitly excludes conversation contents; a separate API-logging setting exists but prompt/response compliance-retention coverage is unclear. Sources: meingpt:meingpt:audit. - siem_export — Can logs stream to a SIEM or be exported? [partial]: CSV/JSON filtered audit export, 10000 entries/20 MiB/two minutes per export; SIEM streaming is not established. Sources: meingpt:meingpt:audit-export. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Unknown. No legal-hold or eDiscovery documentation was located; immutable audit storage and full content-logging configuration were not established. - log_retention — How long are logs kept? [supported]: Administrative settings changes are retained indefinitely; Governance Outpost query records are retained 90 days from enablement. Sources: meingpt:meingpt:audit. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:audit, meingpt:meingpt:scim, meingpt:meingpt:audit-export ### 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. #### 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 #### meinGPT 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. ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workspace instructions and Governance acknowledgements are documented; policy enforcement breadth is limited. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - org_instructions: Additional Chat Context is a workspace-wide system instruction, not a guaranteed enforcement layer. - content_filters: Provider content filtering can stop output; configurable organization-wide topic filters were not established. - Unverified violation_reporting: Admin policy-violation reporting was not established in Compliance Controls; no guardrail fixture was run. - org_instructions — Can admins set organisation-wide instructions? [partial]: Additional Chat Context is a workspace-wide system instruction, not a guaranteed enforcement layer. Sources: meingpt:meingpt:config. - usage_notice — Can users be required to accept a usage policy? [supported]: Governance includes multilingual acceptable-use policies for acknowledgement and mandatory courses that block other pages until complete. Sources: meingpt:meingpt:prices, meingpt:meingpt:audit. - content_filters — Are content filters configurable? [partial]: Provider content filtering can stop output; configurable organization-wide topic filters were not established. Sources: meingpt:meingpt:api. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. Admin policy-violation reporting was not established in Compliance Controls; no guardrail fixture was run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:config, meingpt:meingpt:prices, meingpt:meingpt:audit, meingpt:meingpt:api ## 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Germany platform storage and model-specific EU/global routes must be scoped separately. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - inference_region: Azure Sweden/France, Vertex Frankfurt, Mistral France/Sweden, OpenAI EU endpoint, Nebius Finland, TensorX Ireland and other conditional routes. Some image variants remain Global; the accepted DPA governs authorized exceptions. - backups_logs_region: Scaleway France is conditional backup infrastructure; log/telemetry locations are not separately specified. - residency_plan: DPA 2.0.1 governs new acceptance since 24 September; existing customers retain agreed versions. EU inference depends on selected/approved routes; section 4(3) permits listed/instructed third-country transfers. - Unverified support_access_region, swiss_hosting: No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found. - storage_region — Where are chats, files and indexes stored? [supported]: Hetzner Germany hosts chats, accounts, documents and cloud indexes; register identifies Nürnberg/Falkenstein. Sources: meingpt:meingpt:pools, meingpt:meingpt:subprocessors. - inference_region — Where do model calls run, per provider? [partial]: Azure Sweden/France, Vertex Frankfurt, Mistral France/Sweden, OpenAI EU endpoint, Nebius Finland, TensorX Ireland and other conditional routes. Some image variants remain Global; the accepted DPA governs authorized exceptions. Sources: meingpt:meingpt:subprocessors, meingpt:meingpt:image-admin, meingpt:meingpt:dpa. - backups_logs_region — Where are backups, logs and telemetry? [partial]: Scaleway France is conditional backup infrastructure; log/telemetry locations are not separately specified. Sources: meingpt:meingpt:subprocessors, meingpt:meingpt:dpa. - support_access_region — From where can vendor staff access data? [unknown]: From where can vendor staff access data? Unknown. No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found. - swiss_hosting — Is Swiss hosting available? [unknown]: Is Swiss hosting available? Unknown. No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found. - residency_plan — Which plan or option provides residency? [partial]: DPA 2.0.1 governs new acceptance since 24 September; existing customers retain agreed versions. EU inference depends on selected/approved routes; section 4(3) permits listed/instructed third-country transfers. Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pools, meingpt:meingpt:subprocessors, meingpt:meingpt:image-admin, meingpt:meingpt:dpa, meingpt:meingpt:dpa-page ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial SaaS is offered; terms permit individually agreed on-premise use, while Outpost is a connector. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace, meinGPT Outpost local connector; version=Public documentation checked 2026-10-21; plan=Public SaaS; on-premise only if specifically contracted; add_ons=none stated; deployment_mode=not specified; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - on_premise: Terms section 1a permits the whole software in customer data centres when agreed in the licence contract. The linked on-premise-requirements URL redirects to the generic security page; minimum seats and setup/operator terms are not public. - mode_feature_gaps: The code sandbox remains in Frankfurt cloud even for on-premise customers; there is no complete mode parity list. - Unverified dedicated_instance, customer_cloud, air_gapped: Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes. - multi_tenant_saas — Is a shared SaaS offered? [supported]: The public web workspace and shared organization API limits establish the managed SaaS offer. Sources: meingpt:meingpt:terms, meingpt:meingpt:api. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [unknown]: Is a dedicated single-tenant instance offered, from what size? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes. - customer_cloud — Can it run in the customer's own cloud account, from what size? [unknown]: Can it run in the customer's own cloud account, from what size? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes. - on_premise — Can the whole platform run on customer infrastructure, from what size? [partial]: Terms section 1a permits the whole software in customer data centres when agreed in the licence contract. The linked on-premise-requirements URL redirects to the generic security page; minimum seats and setup/operator terms are not public. Sources: meingpt:meingpt:terms. - air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes. - mode_feature_gaps — Which features are missing outside SaaS? [partial]: The code sandbox remains in Frankfurt cloud even for on-premise customers; there is no complete mode parity list. Sources: meingpt:meingpt:sandbox. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:terms, meingpt:meingpt:api, meingpt:meingpt:sandbox ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA 2.0.1 prohibits training and marks conditional AI services for no permanent provider content copy. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - provider_retention: Annex 4 defines ZDR as no permanent copy on the provider infrastructure; exact abuse-monitoring time and exceptions are not specified. - zero_retention: Conditional AI/function services in Annex 4 carry ZDR, while SelectCode-controlled storage remains separate; applies to the accepted DPA version. - Unverified human_review: Human provider-review rights and per-model transient/abuse-retention durations are not disclosed in the accepted-form DPA or data-flow guide. - vendor_training — Does the vendor train on customer content? [supported]: Section 5(5) restricts processing to service delivery and excludes other purposes. Sources: meingpt:meingpt:dpa. - provider_training — Do model providers train on it under this product's contracts? [supported]: Section 5(5) states no subprocessor uses customer data to train its own AI model. Sources: meingpt:meingpt:dpa. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [partial]: Annex 4 defines ZDR as no permanent copy on the provider infrastructure; exact abuse-monitoring time and exceptions are not specified. Sources: meingpt:meingpt:dpa. - zero_retention — Is zero data retention available, and on which plan? [partial]: Conditional AI/function services in Annex 4 carry ZDR, while SelectCode-controlled storage remains separate; applies to the accepted DPA version. Sources: meingpt:meingpt:dpa. - human_review — Can provider staff review content? [unknown]: Can provider staff review content? Unknown. Human provider-review rights and per-model transient/abuse-retention durations are not disclosed in the accepted-form DPA or data-flow guide. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:dpa ### DATA-04: Retention and deletion Judgment rule: Record default retention for chats, files, indexes and logs; admin-configured retention; user deletion; deletion after contract end; and deletion confirmation. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Ordinary chat removal archives; admin retention and contractual deletion use different mechanisms. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - user_deletion: Chat removal does not permanently delete messages or attachments; final account deletion is requested by the administrator via support. Generated images/text translations have their own deletion controls. - default_retention — What is retained and for how long by default? [supported]: Chat/file data stays until instructed deletion; UI Chat löschen archives. Text translations remain until user deletion; document translations persist until account/workspace deletion. Sources: meingpt:meingpt:flow, meingpt:meingpt:translation. - admin_retention — Can admins set retention periods? [supported]: Release 2.67.0 adds disabled-by-default deletion periods for chats, meetings and automation runs, with a 24-hour wait before a new/shorter period applies. Sources: meingpt:meingpt:changes. - user_deletion — Can users delete their chats and files permanently? [partial]: Chat removal does not permanently delete messages or attachments; final account deletion is requested by the administrator via support. Generated images/text translations have their own deletion controls. Sources: meingpt:meingpt:flow, meingpt:meingpt:security, meingpt:meingpt:images, meingpt:meingpt:translation. - contract_end_deletion — What is deleted at contract end, and when? [supported]: DPA section 12 requires return or requested deletion, including backups, within 30 days after termination or an agreed export window; statutory retention exceptions apply and proof is available on request. Sources: meingpt:meingpt:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:flow, meingpt:meingpt:translation, meingpt:meingpt:changes, meingpt:meingpt:security, meingpt:meingpt:images, meingpt:meingpt: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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA and processing register name providers, conditional use and advance change notices. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - parent_jurisdiction: SelectCode GmbH is a German entity; the security site describes it as independent. A separately owned parent was not identified. - subprocessor_list — Is a dated sub-processor list published? [supported]: DPA Annex 4 is dated 24 September 2026; live function/region register is also public. Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors. - subprocessor_countries — Which countries do sub-processors operate in? [supported]: Contract entities include Germany, Netherlands, Slovenia, Luxembourg, France, Ireland and Finland. Processing register names Germany platform, France backups, Finland, Ireland, Sweden/France and Frankfurt inference routes; EU symbol is processing, not ownership. Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors. - change_notification — Are customers notified of sub-processor changes? [supported]: Section 9 requires notice before additions/replacements and gives two weeks to object on important data-protection grounds, with specified termination rights. Sources: meingpt:meingpt:dpa. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: SelectCode GmbH is a German entity; the security site describes it as independent. A separately owned parent was not identified. Sources: meingpt:meingpt:terms, meingpt:meingpt:subprocessors. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [supported]: DPA section 4(3) uses GDPR Article 45 adequacy or Article 46 safeguards for disclosed/instructed transfers; it does not promise a blanket absence of third-country processing. Sources: meingpt:meingpt:dpa. - government_access_policy — Is there a published government-access or transparency policy? [supported]: Section 7 requires notification where lawful, review/challenge of disproportionate requests, minimization and no compliance with unrecognized third-country requests. Sources: meingpt:meingpt:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors, meingpt:meingpt: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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial A public GDPR DPA and German-law terms are available; sector coverage needs qualification. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - dpa: Version 2.0.1 is a public signed-form or electronic-acceptance DPA; negotiability is not promised. - revdsg_gdpr: GDPR Article 28 governs the DPA; an explicit Swiss revDSG annex was not found. - ai_act_materials: Governance includes usage policies and mandatory training; automated EU AI Act use-case checks are labelled Coming soon, so a complete current provider/deployer dossier was not established. - sector_materials: Governance offers a separate section 203 German professional-secrecy agreement; FINMA-specific materials were not found. - dpa — Is a DPA available, and is it negotiable? [partial]: Version 2.0.1 is a public signed-form or electronic-acceptance DPA; negotiability is not promised. Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: GDPR Article 28 governs the DPA; an explicit Swiss revDSG annex was not found. Sources: meingpt:meingpt:dpa. - governing_law — Which law and court govern the contract? [supported]: DPA section 13 uses German law; terms choose the competent court at the vendor seat. Sources: meingpt:meingpt:dpa, meingpt:meingpt:terms. - ai_act_materials — Is EU AI Act documentation provided? [partial]: Governance includes usage policies and mandatory training; automated EU AI Act use-case checks are labelled Coming soon, so a complete current provider/deployer dossier was not established. Sources: meingpt:meingpt:prices. - sector_materials — Are FINMA or other sector materials provided? [partial]: Governance offers a separate section 203 German professional-secrecy agreement; FINMA-specific materials were not found. Sources: meingpt:meingpt:prices. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa, meingpt:meingpt:terms, meingpt:meingpt:prices ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial ISO and penetration-test documents are advertised behind email access; certificates were not independently verified. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - iso_27001: DPA Annex 3 states ISO/IEC 27001:2022 certificate DE-IS-20250256, Proks Certification GmbH, development/operation of MeinGPT SaaS and custom services, valid to 2028-12-16. The certificate/issuer record was not obtained, so this remains a vendor claim. - c5: The register attributes BSI C5 to Hetzner infrastructure, not to the MeinGPT service. - pentest: A SySS 2025 penetration-test certificate is listed but its result/scope and validity were not retrieved. - Unverified soc2, other_certifications: SOC 2 and other product attestations were not established. No email-gated report was requested. - iso_27001 — ISO 27001 with scope and validity? [partial]: DPA Annex 3 states ISO/IEC 27001:2022 certificate DE-IS-20250256, Proks Certification GmbH, development/operation of MeinGPT SaaS and custom services, valid to 2028-12-16. The certificate/issuer record was not obtained, so this remains a vendor claim. Sources: meingpt:meingpt:dpa, meingpt:meingpt:trust. - soc2 — SOC 2 type, period and covered service? [unknown]: SOC 2 type, period and covered service? Unknown. SOC 2 and other product attestations were not established. No email-gated report was requested. - c5 — BSI C5 attestation? [partial]: The register attributes BSI C5 to Hetzner infrastructure, not to the MeinGPT service. Sources: meingpt:meingpt:subprocessors. - other_certifications — Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Unknown. SOC 2 and other product attestations were not established. No email-gated report was requested. - report_access — How can customers obtain reports? [supported]: The trust centre asks for email-based access for ISO and SySS 2025 penetration-test documents. Sources: meingpt:meingpt:trust. - pentest — Are independent penetration test summaries available? [partial]: A SySS 2025 penetration-test certificate is listed but its result/scope and validity were not retrieved. Sources: meingpt:meingpt:trust. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:dpa, meingpt:meingpt:trust, meingpt:meingpt:subprocessors ### 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). #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Encryption and logical tenancy are documented; key and private-networking details remain incomplete. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Business/Enterprise hosted workspace; CMK entitlement excluded from verified findings; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - CMK is an access/entitlement gap, not an absent capability. - encryption_at_rest — Is data encrypted at rest? [supported]: Security guide states AES-256 at rest and TLS 1.3; DPA Annex 3 includes encryption at rest/transit. Sources: meingpt:meingpt:security, meingpt:meingpt:dpa. - customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Unknown for Business or Enterprise. The security FAQ says Customer Managed Keys are on request but does not identify an eligible tier, price, key custody or location. No plan-scoped CMK commitment was verified. - private_networking — Is private connectivity or IP restriction available? [unknown]: Is private connectivity or IP restriction available? Unknown. A private-link/IP allowlist/VPN product entitlement was not established; Outpost outbound TLS is a source connector rather than a private SaaS endpoint. - tenant_isolation — How are customers separated in shared SaaS? [partial]: DPA Annex 3 specifies logical tenant separation and network segmentation; no independent isolation test was run. Sources: meingpt:meingpt:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:security, meingpt:meingpt:dpa ### DATA-09: Professional secrecy Judgment rule: For professional secrecy holders (Berufsgeheimnisträger: lawyers, doctors, auditors, tax advisers) under § 203 StGB (DE) and Art. 321 StGB (CH), record whether the vendor signs a contractual secrecy undertaking or a § 203 agreement that binds its staff and its sub-processors; whether this comes as a dedicated offering or a paid add-on, and on which plan; who can access content in plain text (vendor staff, sub-processors, model providers); and the documentation provided. A DPA or a no-training clause alone is not a secrecy undertaking. Banking secrecy and FINMA outsourcing belong to DATA-06, not here. Record contract facts, not a legal assessment. #### 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. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The base AGB contains conditional professional-secrecy duties. Eligibility and executed terms of the separately marketed Governance addendum remain unknown. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked2026-10-21; plan=Business/Enterprise customer contracts incorporating AGB section12(4); only the base-terms obligation is assessed; add_ons=Separate Governance addendum excluded from verified entitlement; contract required; deployment_mode=multi-tenant-saas; region=Germany/EU platform; model route and deployment exceptions apply; os=not specified. Limitations: - The base-terms duties and a separately executed Governance addendum are separate legal documents. No claim that one depends on purchase of the other is made. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [partial]: For contracts incorporating the published AGB, section12(4) applies when processed data fall under professional secrecy, including §203. It imposes indefinite confidentiality, access only as necessary to perform services and acknowledgement of criminal duties. The clause states no Governance prerequisite. It does not establish a separately executed addendum or Swiss Art321 coverage. Sources: meingpt:meingpt:secrecy-contract-rev2. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [partial]: Section12(4) requires staff/subcontractors who can access covered data to be bound in at least text form. Subcontracting and services outside the EU require text consent, deemed granted for known providers at contract start. Provider-specific executed undertakings were not retrieved. Sources: meingpt:meingpt:secrecy-contract-rev2. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: Unknown whether the separate Governance §203 addendum is available with self-service Business or only a contracted platform offer. The calculator lists it under Governance at EUR1.35/user/month annually, but this is not proof of eligibility or a fee for the base AGB duties. Sources: meingpt:meingpt:prices-rev2. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: The base AGB restrict knowledge of covered data to what is necessary for the contracted service. The clause does not promise that staff or model providers can never see plaintext. Agreement-specific access restrictions beyond section12(4) were not verified. Sources: meingpt:meingpt:secrecy-contract-rev2. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [partial]: The public AGB section12(4) is the verified contract text. A separately executed/template Governance addendum and provider-by-provider undertakings were not obtained. Sources: meingpt:meingpt:secrecy-contract-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:secrecy-contract-rev2, meingpt:meingpt:prices-rev2 ## 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Self-service Business costs EUR29/user/month excluding VAT and includes standard-model use. Enterprise and platform-module pricing are outside this scoped offer. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Self-service Business, monthly billing only; contracted Enterprise/platform calculator excluded; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - The progressive platform calculator is not used as a Business tariff. Its contract eligibility remains outside this finding. - pricing_unit — What is the pricing unit? [supported]: Business is sold per user per month through self-service Stripe checkout. Premium/reasoning models, API use and meeting-bot recordings are separately metered. Sources: meingpt:meingpt:billing-rev2. - list_prices — What are list prices per plan, with date and currency? [supported]: Self-service Business is EUR29/user/month, excluding VAT, on monthly billing. No annual discount or progressive marginal tiers are applied to this offer. Sources: meingpt:meingpt:billing-rev2. - included_usage — What usage is included? [partial]: Standard-model use in Business is unlimited according to the billing guide. Premium/reasoning models, API and meeting bots remain additional; the exact standard-model catalog and any applicable workload restrictions are not fixed by this page. Sources: meingpt:meingpt:billing-rev2. - add_ons — Which features cost extra? [unknown]: Unknown for self-service Business. The separate platform calculator has Governance/Outpost modules, but their Business eligibility and package prices were not established. - overage — What do usage beyond limits and premium models cost? [partial]: Business standard models do not consume additional billed usage under the billing guide. Premium/reasoning, API and meeting-bot use draw on workspace credit; meeting bots cost EUR0.80/audio hour. Other route-specific charges depend on the selected service. Sources: meingpt:meingpt:billing-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:billing-rev2 ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business-only seat floors are EUR69600 / EUR348000 / EUR1740000 for200/1000/5000 users over12months, each plus unknown workload and contract components. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Self-service Business at EUR29/user/month, paid monthly for12months; Business standard-chat floor only; add_ons=No paid add-ons included; required extras unknown; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21:12months, list prices, excluding VAT;60% light100,30% regular400,10% power1500 messages/user/month;3000 input and600 output tokens/message. Weighted330messages,0.99M input/0.198M output per user/month. Token mix is used only on separately billed routes; this Business standard-chat floor has included usage. - ECB2026-10-20 EUR1=USD1.1215=CHF0.9237. Vendor currency EUR is primary. Contract-specific extras remain unknown. - cost_200 — Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 200 users over12months: from EUR69600.00 / CHF64289.52 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx. - cost_1000 — Year-one cost at 1,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 1000 users over12months: from EUR348000.00 / CHF321447.60 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx. - cost_5000 — Year-one cost at 5,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 5000 users over12months: from EUR1740000.00 / CHF1607238.00 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx. - variable_share — Which part depends on usage? [partial]: Business standard-model chat is included. A model-preserving workload outside that standard catalog, premium/reasoning models, API and meeting-bot charges cannot be quantified without the actual route and contract; the variable remainder stays unknown. No provider proxy or progressive-platform tariff is substituted. Sources: meingpt:meingpt:billing-rev2. - unknown_parts — Which costs could not be priced? [partial]: Business eligibility for200/1000/5000 users, standard-model mapping, premium/tool use, required Governance/Outpost, rollout and Enterprise services remain unknown. No progressive-platform amount is mixed into the Business floor. Sources: meingpt:meingpt:billing-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt: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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial A self-serve 10-day trial exists, while several enterprise features still need enablement. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - free_tier: Trial expiry locks the workspace even for free models; the guide does not describe a permanent free business workspace. - trial_scope: Most base functions are included; personal API keys are off, and request-only meeting/live recording and automations are initially off as in paid plans. SCIM/SSO enterprise enablement is not guaranteed. - sales_gate: Base trial is self-serve; request-enabled features and Enterprise terms are not self-service. No sales contact was made. - free_tier — Is there a free tier for business use? [partial]: Trial expiry locks the workspace even for free models; the guide does not describe a permanent free business workspace. Sources: meingpt:meingpt:billing. - self_serve_trial — Is a self-serve business trial available? [supported]: 10 days, EUR 5 after phone verification, no payment details or automatic paid conversion, up to ten emailed invitees. Sources: meingpt:meingpt:billing. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Most base functions are included; personal API keys are off, and request-only meeting/live recording and automations are initially off as in paid plans. SCIM/SSO enterprise enablement is not guaranteed. Sources: meingpt:meingpt:billing. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Base trial is self-serve; request-enabled features and Enterprise terms are not self-service. No sales contact was made. Sources: meingpt:meingpt:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt: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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public price fields and German contract defaults exist; customer-specific terms and CHF invoicing remain open. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - minimum_commitment: Public calculator starts at one user; individually negotiated Enterprise or on-prem minimums are not stated. - local_invoicing: SelectCode GmbH is the German contracting entity and prices are EUR; CHF invoices were not confirmed. - transparency_class: Partially specified: public marginal seat/model/add-on rates, but PII base, services and deployments are quote-only and Business packaging differs. - minimum_commitment — What seat or spend minimum applies? [partial]: Public calculator starts at one user; individually negotiated Enterprise or on-prem minimums are not stated. Sources: meingpt:meingpt:prices. - contract_length — What contract lengths are offered? [supported]: Public calculator has annual/monthly options; terms default to one year absent another agreement. Sources: meingpt:meingpt:prices, meingpt:meingpt:terms. - cancellation — How can the contract be cancelled or reduced? [supported]: Absent other terms, three months before term-end, text/email or admin cancellation; downgrades/user reductions effective following month, no current-month refund. Price changes require the stated notice/consent procedure. Sources: meingpt:meingpt:terms. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: SelectCode GmbH is the German contracting entity and prices are EUR; CHF invoices were not confirmed. Sources: meingpt:meingpt:terms. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: Partially specified: public marginal seat/model/add-on rates, but PII base, services and deployments are quote-only and Business packaging differs. Sources: meingpt:meingpt:prices, meingpt:meingpt:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:prices, meingpt:meingpt:terms, meingpt:meingpt:billing ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The public AGB establish a commercial subscription/rental use licence with contract-limited rights. Public component source licences and a distinct enterprise source-edition mapping remain unverified. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - Contractual service-use rights do not establish the licence of every server/client/connector dependency. - No public implementation repository or enterprise source-edition map was identified. - licence_type — Which licence applies to each component? [partial]: SelectCode AGB describe the software as a subscription/rental and grant a non-exclusive use right limited to the contract term. Public display, adaptation, translation and decompilation of the software are restricted subject to statutory rights. This establishes the commercial service-use licence; a client/server/connector source-licence inventory and current implementation revision remain unpublished. Sources: meingpt:meingpt:terms-20261026. - branding_restrictions — Do licence terms restrict branding or user counts? [partial]: AGB require purchased licences for majority-owned affiliates and give no independent right to sublicense or transfer usage rights. They restrict adapting the software. A numerical user cap or a component-specific branding licence is not established by these clauses. Sources: meingpt:meingpt:terms-20261026. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Unknown. The public commercial terms describe rented software, but no public client/server/connector source licence or current repository revision was located. Repository visibility was not treated as a licence. Rechecked 2026-10-26 in Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. Official links and targeted first-party searches yielded no further plan-scoped specification for the remaining atom. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: meingpt:meingpt:terms-20261026 ### VEN-06: Data export and exit Judgment rule: Record admin export of chats, assistants, knowledge bases, prompts and audit logs, formats, export completeness, user self-export, and what survives contract end. Run an admin export on a trial. Exported chats alone do not make assistants and knowledge portable. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Individual downloads exist but a bulk chat export is explicitly unavailable. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - chat_export: Security FAQ explicitly says there is currently no function to export all chats at once. - export_format: Individual artifacts/slides/files/images can be downloaded; administrative logs have CSV/JSON exports. This does not establish portable assistants or a complete knowledge export. - post_termination_window: Terms permit export until termination takes effect; later access is blocked. DPA allows an individually agreed export window and return/deletion within 30 days after it. - Unverified assistant_export, knowledge_export: No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run. - chat_export — Can admins export all chats? [unsupported]: Security FAQ explicitly says there is currently no function to export all chats at once. Sources: meingpt:meingpt:security. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unknown. No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run. - knowledge_export — Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? Unknown. No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run. - export_format — Are formats documented and machine-readable? [partial]: Individual artifacts/slides/files/images can be downloaded; administrative logs have CSV/JSON exports. This does not establish portable assistants or a complete knowledge export. Sources: meingpt:meingpt:security, meingpt:meingpt:audit-export. - post_termination_window — How long can data be retrieved after termination? [partial]: Terms permit export until termination takes effect; later access is blocked. DPA allows an individually agreed export window and return/deletion within 30 days after it. Sources: meingpt:meingpt:terms, meingpt:meingpt:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:security, meingpt:meingpt:audit-export, meingpt:meingpt:terms, meingpt:meingpt:dpa ### 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. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial German vendor support and a public incident history are documented; an uptime credit schedule was not found. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - support_channels: Terms provide email support Monday-Friday 09:00-17:00; timezone and plan-specific guaranteed response times are not stated. - Unverified support_languages, uptime_sla: Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage. - support_channels — Which support channels are available on each plan? [partial]: Terms provide email support Monday-Friday 09:00-17:00; timezone and plan-specific guaranteed response times are not stated. Sources: meingpt:meingpt:terms. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage. - regional_presence — Is there a DACH or Swiss entity, team or partner? [supported]: SelectCode GmbH contracts from Unterhaching, Germany. Sources: meingpt:meingpt:terms. - uptime_sla — Is there an uptime SLA with credits? [unknown]: Is there an uptime SLA with credits? Unknown. Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage. - status_page — Is there a public status page with history? [supported]: Public status.meingpt.com lists the platform and historical incidents; uptime is not an SLA. Sources: meingpt:meingpt:status. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:terms, meingpt:meingpt:status ### VEN-08: Onboarding, training and adoption Judgment rule: Record vendor-led onboarding, admin training, end-user training (live, e-learning, languages), use-case libraries, champion programmes, change-management materials and their cost. Distinguish included services from paid professional services and partner offerings. #### 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 #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Learning paths and business examples are built in; personal rollout services are quote-based. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - onboarding_service: Personal guidance covers selection, pilot and rollout on an individual offer; universal included consulting is not promised. - user_training: The learning area has guided practical courses; Governance enables mandatory assignments. Complete course language coverage was not stated. - adoption_programme: Pilot/adoption workspaces typically run a three-month fixed-price pilot with workshops; a defined champion programme was not found. - onboarding_service — Is guided onboarding included? [partial]: Personal guidance covers selection, pilot and rollout on an individual offer; universal included consulting is not promised. Sources: meingpt:meingpt:prices. - user_training — Is end-user training offered, in which languages? [partial]: The learning area has guided practical courses; Governance enables mandatory assignments. Complete course language coverage was not stated. Sources: meingpt:meingpt:academy, meingpt:meingpt:audit. - use_case_library — Are role-based use cases and templates provided? [supported]: Role/department personalization and business-use-case material are documented. Sources: meingpt:meingpt:academy. - adoption_programme — Is there a champion or adoption programme? [partial]: Pilot/adoption workspaces typically run a three-month fixed-price pilot with workshops; a defined champion programme was not found. Sources: meingpt:meingpt:billing. - service_cost — Which services cost extra? [supported]: Personal guidance is quote-only; terms bill services by time/person-days or individually agreed fixed price. Sources: meingpt:meingpt:prices, meingpt:meingpt:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:prices, meingpt:meingpt:academy, meingpt:meingpt:audit, meingpt:meingpt:billing, meingpt:meingpt:terms ## Sources ### 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 ### meingpt:meingpt:rates Alle Modelle | MeinGPT Docs. Public EUR token and service rates include GPT-5 mini at EUR 0.30 input and EUR 2.40 output per million tokens. - URL: https://meingpt.com/docs/admin-guide/pricing - Locator: Text-generation, translation, images and other-functions tables - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:models-rev2 Modelle | MeinGPT Docs. Current documentation lists selectable non-Meta model families, per-chat selection and context-length routing; the lifecycle table contains no current selectable Meta model. - URL: https://meingpt.com/docs/platform/models - Locator: Model picker, model tables and own-LLM-key FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:lifecycle-rev2 Modell-Lifecycle | MeinGPT Docs. Active models, future retirement dates and automatic replacement rules are published. - URL: https://meingpt.com/docs/admin-guide/model-lifecycle - Locator: Phases, notice period and current-model table - Evidence kind: documented - Source date: Not stated - 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 ### meingpt:meingpt:lifecycle Modell-Lifecycle | MeinGPT Docs. Active models, future retirement dates and automatic replacement rules are published. - URL: https://meingpt.com/docs/admin-guide/model-lifecycle - Locator: Phases, notice period and current-model table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:changes Was wir zuletzt released haben | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. Release 2.67.0 on 18 October adds Gemini 4 Argon, retires named models and adds configurable deletion periods. - URL: https://meingpt.com/changelog - Locator: v2.67.0, model retirement and deletion periods - Evidence kind: documented - Source date: 2026-10-18 - 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 ### meingpt:meingpt:models Modelle | MeinGPT Docs. Users choose models per chat; automatic selection is based on context length; customer LLM keys and endpoints cannot be added. - URL: https://meingpt.com/docs/platform/models - Locator: Model picker, model tables and own-LLM-key FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:translation Übersetzer | MeinGPT Docs. Default text translation uses Google Cloud Translate and document translation uses DeepL through EU endpoints; glossaries and layout preservation are documented. - URL: https://meingpt.com/docs/platform/translation - Locator: Engine/hosting, formats and glossary management - 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 ### meingpt:meingpt:subprocessors Subdienstleister & Verarbeitungsregionen | MeinGPT. The register separates Germany platform storage, France backups and provider-specific EU inference regions. - URL: https://meingpt.com/sicherheit/subdienstleister - Locator: Register by function and processing region - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### meingpt:meingpt:config Workspace-Konfiguration | MeinGPT Docs. Admins can restrict models by teams or people and supply workspace-wide instructions; denied API models return an error. - URL: https://meingpt.com/docs/admin-guide/workspace-configuration - Locator: Model access, default settings and additional chat context - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:limits Nutzungslimits | MeinGPT Docs. Personal category budgets block new use at zero; running meeting bots can overrun limits and scheduled runs are outside personal categories. - URL: https://meingpt.com/docs/admin-guide/usage-limits - Locator: Usage levels, meeting limits and user consumption table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:api Einführung | MeinGPT Docs. Chat, embeddings, assistants, workflows and transcription APIs use bearer keys and published token rate limits; translation is UI-only. - URL: https://meingpt.com/docs/api - Locator: API overview, rate limits and errors - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### meingpt:meingpt:pools Datenquellen & RAG | MeinGPT Docs. Cloud pools index six source types in Germany, refresh every 15 minutes and share a 300 GB raw-data budget. - URL: https://meingpt.com/docs/integrations/data-pools-rag - Locator: Cloud-source table, connector comparison and normal-chat search - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:chat Eingabefeld | MeinGPT Docs. Chat has stop, model choice, file upload, dictation and sharing links, with 50 files and 50 MB per non-image file. - URL: https://meingpt.com/docs/platform/chats/eingabefeld - Locator: Input controls, file limits, dictation and sharing - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:flow Datenfluss bei MeinGPT Chats | MeinGPT Docs. Chat deletion archives content; prompts have provider-dependent processing, and platform data stays until instructed deletion. - URL: https://meingpt.com/docs/privacy-security/faq-chats-datenfluss - Locator: Processing steps, providers and deletion rights - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:sandbox Code-Sandbox | MeinGPT Docs. Python/JavaScript analysis and Office generation run in an isolated Unikraft Cloud VM in Frankfurt, including for on-premise customers. - URL: https://meingpt.com/docs/platform/code-sandbox - Locator: Execution flow, hosting, lifetime and limitations - 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 ### meingpt:meingpt:assistants Assistenten | MeinGPT Docs. Assistants combine model, instructions, files, pools, connectors, tools and memory. - URL: https://meingpt.com/docs/platform/assistants - Locator: Creation guide and editor sections - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:projects Projekte | MeinGPT Docs. Projects share instructions and workflows while each member keeps a private chat history. - URL: https://meingpt.com/docs/platform/projects - Locator: Collaboration, roles and deletion - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### meingpt:meingpt:m365 Microsoft 365 | MeinGPT Docs. Separate Outlook, Teams, SharePoint and OneDrive connectors run under user OAuth; Outlook can write, the other three read. - URL: https://meingpt.com/docs/integrations/connectors/microsoft365 - Locator: Overview, setup, tenant consent and permission model - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:pool-controls Sucheinstellungen am Datenpool | MeinGPT Docs. Source-permission import is off by default and request-enabled for SharePoint and Drive only; answers always show sources. - URL: https://meingpt.com/docs/integrations/data-pool-search-settings - Locator: Settings table and source-permission section - 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 ### meingpt:meingpt:memory Memory | MeinGPT Docs. Memory persists per user across enabled assistants; users can inspect/delete it and admins can disable the tool. - URL: https://meingpt.com/docs/platform/memory - Locator: How memory works, management and admin controls - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:preferences Präferenzen | MeinGPT Docs. Users can set persistent system instructions and a platform-language preference. - URL: https://meingpt.com/docs/platform/preferences - Locator: Chat settings and appearance - 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 ### meingpt:meingpt:roles Rollen & Zugriffsmodell | MeinGPT Docs. Admin, Member and Viewer roles differ in settings access and seat use; admins see all team-shared assets. - URL: https://meingpt.com/docs/admin-guide/roles-and-access-model - Locator: Role table, admin exception and support visibility - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:permissions Berechtigungen | MeinGPT Docs. Support-enabled permissions control creation, sharing and app use per person or team. - URL: https://meingpt.com/docs/admin-guide/permissions - Locator: Availability, permissions table and app restrictions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:prompts Prompt-Bibliothek | MeinGPT Docs. Saved prompt folders have private, workspace or department visibility. - URL: https://meingpt.com/docs/platform/prompt-library - Locator: Core functions, visibility and sharing - 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 ### meingpt:meingpt:web Websuche | MeinGPT Docs. Linkup powers chat search and a multi-step Deep Research app with cited sources. - URL: https://meingpt.com/docs/platform/web-search - Locator: Three routes, query creation, Linkup and research app - 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 ### meingpt:meingpt:workflows Workflows erstellen und ausführen | MeinGPT Docs. Project workflows support multiple models, variables, documents and downloadable Office, PDF or JSON output. - URL: https://meingpt.com/docs/platform/workflows-create - Locator: Workflow editor and output format - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:scheduled Geplante Aufgaben | MeinGPT Docs. Scheduled tasks are support-enabled beta with schedule, webhook and email triggers under the creator account. - URL: https://meingpt.com/docs/platform/scheduled-tasks - Locator: Beta availability, triggers and execution account - 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 ### meingpt:meingpt:tools Tool-Zugriffsrichtlinien | MeinGPT Docs. Tool methods are intersected across admin and assistant policies; there is no interactive per-action permission dialog. - URL: https://meingpt.com/docs/admin-guide/tool-access-policy - Locator: Security warning and four enforcement layers - 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 ### meingpt:meingpt:audit Compliance Controls | MeinGPT Docs. Administrative settings logs exclude chat contents and are retained indefinitely; Governance Outpost search records are retained 90 days. - URL: https://meingpt.com/docs/admin-guide/compliance-controls - Locator: Core controls and Outpost search log - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:outlook Outlook Add-in | MeinGPT Docs. The Outlook add-in requires Enterprise API enablement and a personal API key and works in the received-mail reading view. - URL: https://meingpt.com/docs/integrations/connectors/outlook-addin - Locator: Prerequisites, supported clients and central deployment - 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 ### meingpt:meingpt:terms Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. German commercial terms distinguish SaaS from contract-agreed on-premise deployment and describe subscriptions, export and termination. - URL: https://meingpt.com/agb - Locator: Sections 1a, 2, 3, 5 and final provisions - Evidence kind: documented - 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 ### 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 ### 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 ### meingpt:meingpt:images Bilder Generieren | MeinGPT Docs. The image app supports FLUX, GPT Image and Gemini image models with reference images and downloadable files. - URL: https://meingpt.com/docs/platform/image-generator - Locator: Model list, references and output management - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:image-admin Bildmodelle verwalten | MeinGPT Docs. Admins enable image models and set a default; the table distinguishes manufacturer, host and EU/global processing. - URL: https://meingpt.com/docs/admin-guide/image-models - Locator: Image-model controls and complete table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:meeting Meetings | MeinGPT Docs. Recordings and transcripts become searchable meeting notes; Hetzner, Gladia and Vertex EU form the processing path. - URL: https://meingpt.com/docs/platform/meetings - Locator: Formats/limits, data flow and prices - 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 ### 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 ### meingpt:meingpt:prices prices. The public calculator uses marginal seat tiers plus model consumption and optional Governance and Outpost fees. - URL: https://meingpt.com/preise - Locator: Annual price tiers, included functions, add-ons and model-cost sections - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:sso Access & Login Security | MeinGPT Docs. OIDC, Google and Microsoft login, verified domains and additive Entra group synchronization are documented; SAML is explicitly excluded. - URL: https://meingpt.com/docs/admin-guide/access-and-login-security - Locator: Own identity provider, authentication methods and Entra synchronization - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### meingpt:meingpt:scim Entra ID SCIM-Provisionierung | MeinGPT Docs. SCIM v1 provisions users only; deactivated accounts retain data and release their seat. - URL: https://meingpt.com/docs/admin-guide/entra-scim-provisioning - Locator: SCIM versus SSO, prerequisites, effects and seat assignment - 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 ### meingpt:meingpt:analytics KI-Cockpit | MeinGPT Docs. Adoption and cost reports include user, model, API/platform and team breakdowns with CSV and ID-based anonymization. - URL: https://meingpt.com/docs/admin-guide/ai-cockpit - Locator: Typical metrics, user/team costs and knowledge search - 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 ### meingpt:meingpt:audit-export Änderungsprotokoll exportieren | MeinGPT Docs. Admins export filtered administrative changes as CSV or JSON, capped at 10000 entries, 20 MiB and two minutes. - URL: https://meingpt.com/docs/admin-guide/admin-settings-map - Locator: Export procedure, fields and limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### 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 ### meingpt:meingpt:dpa-page Auftragsverarbeitungsvertrag | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. DPA 2.0.1 dated 24 September 2026 needs signature or recorded electronic acceptance; existing customers retain their agreed version. - URL: https://meingpt.com/avv - Locator: Version and effectiveness - Evidence kind: documented - Source date: 2026-09-24 - Retrieved: 2026-10-21 ### meingpt:meingpt:dpa MeinGPT DPA 2.0.1. The signed-form DPA prohibits training, lists conditional subprocessors, defines authority-request handling and requires return or deletion within 30 days. - URL: https://meingpt.com/legal/avv/v2.0.1.pdf - Locator: Version 2.0.1; sections 4, 5(5), 7, 9, 12, 13 and Annexes 3/4, pages 3-12 - Evidence kind: documented - Source date: 2026-09-24 - 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 ### meingpt:meingpt:security Sind meine Daten sicher? | MeinGPT Docs. Security documentation states TLS 1.3, AES-256, customer-managed keys on request, and no bulk chat/file export. - URL: https://meingpt.com/docs/privacy-security/faq-data-security - Locator: Technical security, deletion and data portability - 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 ### meingpt:meingpt:trust Sicherheitsnachweise & Trust Center | MeinGPT. ISO 27001 and a 2025 SySS penetration-test certificate are listed behind email-gated access. - URL: https://meingpt.com/sicherheit/nachweise - Locator: Certificates, assessments and document access - Evidence kind: vendor-claimed - 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 ### meingpt:meingpt:prices-rev2 Preise für Plattform, Add-ons und KI-Nutzung | MeinGPT. The contracted platform is offered with optional Governance and Outpost modules; local files are Early Access and local MCP/PostgreSQL Private Beta. The price calculator requires a binding individual offer. - URL: https://meingpt.com/preise - Locator: Feature table: Outpost release states; Governance separate agreement; calculator explicitly nonbinding - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:secrecy-contract-rev2 meinGPT terms: professional secrecy. Section12(4) itself imposes indefinite professional secrecy and text-form staff/subcontractor obligations when covered data are processed; it does not state a Governance prerequisite. A separate addendum is outside the verified base-terms finding. - URL: https://meingpt.com/agb - Locator: Section12(4), conditional duties for professional-secret data; no Governance prerequisite stated - Evidence kind: documented - 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 ### meingpt:meingpt:billing-rev2 Abrechnung verwalten | MeinGPT Docs. Self-service Business is EUR29 per user/month excluding VAT, billed monthly, with unlimited standard-model use; premium/reasoning, API and meeting-bot use are separately metered. - URL: https://meingpt.com/docs/admin-guide/billing - Locator: Workspace types; Business upgrade card; standard-model inclusion - 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 ### meingpt:meingpt: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 ### meingpt:meingpt:billing Abrechnung verwalten | MeinGPT Docs. A separate Business offer includes standard models; the trial lasts 10 days with EUR 5 credit and no payment details. - URL: https://meingpt.com/docs/admin-guide/billing - Locator: Workspace types, trial differences and Business upgrade - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:terms-20261026 Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. German commercial terms distinguish SaaS from contract-agreed on-premise deployment and describe subscriptions, export and termination. - URL: https://meingpt.com/agb - Locator: Sections 1a, 2, 3, 5 and final provisions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### 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 ### 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 ### meingpt:meingpt:status status. A public service-status page exposes incident history. - URL: https://status.meingpt.com/ - Locator: Platform component and incidents - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### meingpt:meingpt:academy Lernen & Entdecken | MeinGPT Docs. The learning area includes guided learning paths and business use cases. - URL: https://meingpt.com/docs/platform/academy - Locator: Learning area content and personalization - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21