Skip to content

Agent-readable comparison

Cohere North vs Langdock

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

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

Same facts as Markdown and JSON. Methodology.

Models

MOD-01 Model catalogue and providers

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

Cohere North

Agent cross-checked Support: partial

North supports customer-configured Cohere and external providers; deployed models determine availability.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha model-tier aliases and direct image input; North Mini separately Beta; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • current_models: The model card documents North Large 01-2026, and the October 16 release adds North Mini Beta. The Skills guide recommends additional external model identifiers, but those do not establish what any customer deployment has installed or licensed.
  • auto_routing: Documented resolution is group default, Default alias, then deployment default; inaccessible aliases silently fall back to provider default with a log warning. Automatic task-based routing across providers and UI disclosure of that fallback remain unknown.
  • multimodal_input: North Large 01-2026 accepts text/images,256K input and32K text output. Alpha image input is Cohere-only; visual parser handles PDF/DOCX/PPTX, including OCR. Dictation uses configured ASR; complete per-model matrix unknown.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-177-20261026, cohere-north:cohere-north:n-doc-32-20261026, cohere-north:cohere-north:north-release-html-20261026, cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-1-20261026, cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-97-20261026.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:models, langdock:langdock:model-guide.

MOD-02 Model freshness

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

Cohere North

Agent cross-checked Support: partial

Dated platform notes and operator-pinned model artifacts exist; provider release lag is unknown.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: release_lag_days, deprecation_notice.
  • release_lag_days What was the lag for each of the last three major releases, per provider? [unknown]: Unknown for release_lag_days. No matched provider/product dates for the last three releases or contractual model-removal notice period was retrieved.
  • changelog Is there a dated public model changelog? [supported]: Public North release notes through October 20 v2.0.1 include model and feature changes. Sources: cohere-north:cohere-north:n-north-changelog.
  • deprecation_notice How much notice is given before a model is removed? [unknown]: Unknown for deprecation_notice. No matched provider/product dates for the last three releases or contractual model-removal notice period was retrieved.
  • version_pinning Can an admin keep an older model version? [partial]: Self-hosted serving images/model artifacts are versioned independently; operators select image tags/digests. This does not guarantee retention of external API model versions. Sources: cohere-north:cohere-north:n-doc-168.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-north-changelog, cohere-north:cohere-north:n-doc-168.

Langdock

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

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

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

Cohere North

Agent cross-checked Support: partial

North documents own keys, cloud deployments and OpenAI-compatible endpoints.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha direct image input restriction; provider registration is separately scoped; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • own_cloud_contract: Own Azure OpenAI, Bedrock Cohere/Anthropic and SageMaker endpoints documented. Foundry can bill supported inference to customer Azure subscription; Vertex integration not established.
  • byo_pricing: Unknown for byo_pricing. Provider configuration is documented; commercial BYO discounts and complete feature parity across every provider remain unknown. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/models?format=html, https://private.docs.cohere.com/north/docs/advanced/headless-configuration/model-providers?format=html, https://private.docs.cohere.com/north/docs/admin/bedrock-anthropic?format=html. No additional scoped evidence established this answer.
  • byo_restrictions: Alpha direct image input currently requires Cohere models. Foundry lacks North Large/sparse and Compass keyless model authentication; complete per-provider feature parity remains unknown.
  • own_api_keys Can the customer use its own provider API keys? [supported]: Provider registration accepts customer API keys or identity tokens; declarative providers reference Kubernetes Secrets. Sources: cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-177-20261026.
  • own_cloud_contract Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Own Azure OpenAI, Bedrock Cohere/Anthropic and SageMaker endpoints documented. Foundry can bill supported inference to customer Azure subscription; Vertex integration not established. Sources: cohere-north:cohere-north:n-doc-177-20261026, cohere-north:cohere-north:n-doc-135-20261026, cohere-north:cohere-north:n-doc-218-20261026.
  • custom_endpoint Can an admin add any OpenAI-compatible endpoint? [supported]: OpenAI provider base_url can point at compatible endpoints; vLLM and Cohere compatibility provider types also supported. Actual compatibility still depends on model/tool schema. Sources: cohere-north:cohere-north:n-doc-177-20261026.
  • byo_pricing Does BYO change the licence price? [unknown]: Unknown for byo_pricing. Provider configuration is documented; commercial BYO discounts and complete feature parity across every provider remain unknown. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/models?format=html, https://private.docs.cohere.com/north/docs/advanced/headless-configuration/model-providers?format=html, https://private.docs.cohere.com/north/docs/admin/bedrock-anthropic?format=html. No additional scoped evidence established this answer.
  • byo_restrictions Which features stop working with BYO? [partial]: Alpha direct image input currently requires Cohere models. Foundry lacks North Large/sparse and Compass keyless model authentication; complete per-provider feature parity remains unknown. Sources: cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-218-20261026.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-177-20261026, cohere-north:cohere-north:n-doc-135-20261026, cohere-north:cohere-north:n-doc-218-20261026, cohere-north:cohere-north:n-doc-14-20261026.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:byok, langdock:langdock:byok-routes, langdock:langdock:billing, langdock:langdock:research.

MOD-04 Local and self-hosted models

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

Cohere North

Agent cross-checked Support: partial

North chat and retrieval models can run in customer infrastructure.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: vendor_hosted_open_models.
  • self_hosted_chat Can chat use a customer-hosted model? [supported]: Customer Cohere serving containers and vLLM endpoints are supported; independent model chart deploys generative services in customer GPU clusters. Sources: cohere-north:cohere-north:n-doc-177, cohere-north:cohere-north:n-doc-168.
  • self_hosted_embeddings Can retrieval use customer-hosted embeddings? [partial]: Packed Compass provides local dense embeddings, sparse and rerank. Operator connects North/Compass to these services; arbitrary embedding model compatibility was not established. Sources: cohere-north:cohere-north:n-doc-168.
  • feature_parity Which features fail with self-hosted models? [partial]: Local visual processing needs parser/GPU deployment; hosted search/MCP needs egress. Foundry lacks sparse/North Large, so mixed inference required there. No full disconnected parity matrix retrieved. Sources: cohere-north:cohere-north:n-doc-14, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-218.
  • vendor_hosted_open_models Does the vendor host open-weight models in EU/CH? [unknown]: Unknown for vendor_hosted_open_models. Self-hosted Cohere models and Compass are documented; arbitrary embedding-model compatibility and a Cohere-operated EU/CH open-model hosting SKU were not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-177, cohere-north:cohere-north:n-doc-168, cohere-north:cohere-north:n-doc-14, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-218.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:byok-routes, langdock:langdock:byok, langdock:langdock:byok-models, langdock:langdock:research, langdock:langdock:models, langdock:langdock:terms.

MOD-05 Model control and usage limits

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

Cohere North

Agent cross-checked Support: partial

Group model controls have additive and shared-agent exceptions; alpha limits require deployment.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha model RBAC and Flow control; Models UI separately Beta; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • data_bound_models: Unknown for data_bound_models. Model RBAC and alpha rate limits are documented; content-bound model exclusion and measured enforcement were not tested. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/models?format=html, https://private.docs.cohere.com/north/docs/get-started/agents/creating-custom-agents?format=html, https://private.docs.cohere.com/north/docs/admin/flow-control?format=html. No additional scoped evidence established this answer.
  • user_limits: Alpha Flow control supports requests/input/output tokens by user/group/model/source/provider and time window. Limits default unlimited; no fixed commercial message allowance was retrieved.
  • limit_behaviour: Configured limits block until window resets. Enforcement requires Helm proxy services; UI alone does nothing. Failure policy may allow or deny requests and token estimation is optional; actual overshoot untested.
  • model_allowlist_by_group Can admins limit models per group? [supported]: Beta Models UI configures provider/model user/group access; alpha model RBAC must be enabled. Provider OR model grants access, admins bypass; shared agents use owner permissions, not each recipient. Sources: cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-18-20261026.
  • data_bound_models Can admins restrict which models receive connector or knowledge content? [unknown]: Unknown for data_bound_models. Model RBAC and alpha rate limits are documented; content-bound model exclusion and measured enforcement were not tested. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/models?format=html, https://private.docs.cohere.com/north/docs/get-started/agents/creating-custom-agents?format=html, https://private.docs.cohere.com/north/docs/admin/flow-control?format=html. No additional scoped evidence established this answer.
  • default_model Can admins set the default model? [supported]: Group defaults precede Default tier and deployment default. Aliases are per deployment and initially empty. Sources: cohere-north:cohere-north:n-doc-134-20261026.
  • user_limits What per-user message or token limits apply, and are they published? [partial]: Alpha Flow control supports requests/input/output tokens by user/group/model/source/provider and time window. Limits default unlimited; no fixed commercial message allowance was retrieved. Sources: cohere-north:cohere-north:n-doc-137-20261026.
  • limit_behaviour What happens when a limit is reached? [partial]: Configured limits block until window resets. Enforcement requires Helm proxy services; UI alone does nothing. Failure policy may allow or deny requests and token estimation is optional; actual overshoot untested. Sources: cohere-north:cohere-north:n-doc-137-20261026.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-18-20261026, cohere-north:cohere-north:n-doc-137-20261026.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:limits, langdock:langdock:pricing, langdock:langdock:extra.

Company knowledge

KNOW-01 Files in chat

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

Cohere North

Agent cross-checked Support: partial

Broad file formats and optional OCR are documented; the effective My files size limit for a deployment remains unknown.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • limits: The effective My files default is unknown: its dedicated guide states 50 MB/file subject to configuration, while Supported files describes a 100 MB limit across all files. Neither is asserted as the verified deployment limit. Separately, chat images are limited to 20/message, 5 MB/image and 20 MB total; the supported-files guide lists 500 MB for SharePoint/OneDrive.
  • ocr: Vision parser can OCR scanned PDFs and extract visual tables; alpha setup requires smart parser and hosted vision parser. More than500 visual pages fall back to pure text processing. No scan test run.
  • spreadsheets: The supported-files guide says spreadsheet rows are not indexed for ordinary search and requires Data Interpreter for tabular prompts. Beta Skills also provide spreadsheet/CSV file operations through the code sandbox. Workbook formula/structure fidelity has not been tested.
  • full_vs_chunked: The SharePoint and OneDrive implementation guides remain inaccessible in Markdown, HTML and page-level index forms on 2026-10-26. Retrieved My files and multimodality guides do not establish universal full-file/chunk thresholds or prompt-context disclosure. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/get-started/supported-files?format=html, https://private.docs.cohere.com/north/docs/get-started/north-automations/building-automations/north-multimodality?format=html, https://private.docs.cohere.com/north/docs/get-started/tools/my-files/home?format=html. No additional scoped evidence established this answer.
  • formats Which formats are accepted? [supported]: Office/PDF/text/HTML/email/JSON/XML/EPUB and tabular formats; common images, audio/video with parser enabled. Upload/index support differs from preview and individual vision model support. Sources: cohere-north:cohere-north:n-doc-73-20261026, cohere-north:cohere-north:n-doc-14-20261026.
  • limits What size and count limits apply per file and chat? [partial]: The effective My files default is unknown: its dedicated guide states 50 MB/file subject to configuration, while Supported files describes a 100 MB limit across all files. Neither is asserted as the verified deployment limit. Separately, chat images are limited to 20/message, 5 MB/image and 20 MB total; the supported-files guide lists 500 MB for SharePoint/OneDrive. Sources: cohere-north:cohere-north:n-doc-66-20261026, cohere-north:cohere-north:n-doc-73-20261026, cohere-north:cohere-north:n-doc-1-20261026.
  • ocr Are scanned PDFs read? [partial]: Vision parser can OCR scanned PDFs and extract visual tables; alpha setup requires smart parser and hosted vision parser. More than500 visual pages fall back to pure text processing. No scan test run. Sources: cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-100-20261026.
  • spreadsheets Are Excel tables read with structure intact? [partial]: The supported-files guide says spreadsheet rows are not indexed for ordinary search and requires Data Interpreter for tabular prompts. Beta Skills also provide spreadsheet/CSV file operations through the code sandbox. Workbook formula/structure fidelity has not been tested. Sources: cohere-north:cohere-north:n-doc-73-20261026, cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:north-release-html-20261026.
  • full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [unknown]: The SharePoint and OneDrive implementation guides remain inaccessible in Markdown, HTML and page-level index forms on 2026-10-26. Retrieved My files and multimodality guides do not establish universal full-file/chunk thresholds or prompt-context disclosure. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/get-started/supported-files?format=html, https://private.docs.cohere.com/north/docs/get-started/north-automations/building-automations/north-multimodality?format=html, https://private.docs.cohere.com/north/docs/get-started/tools/my-files/home?format=html. No additional scoped evidence established this answer.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-73-20261026, cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-66-20261026, cohere-north:cohere-north:n-doc-1-20261026, cohere-north:cohere-north:n-doc-100-20261026, cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:north-release-html-20261026.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:files, langdock:langdock:file-count, langdock:langdock:retrieval.

KNOW-02 Knowledge bases and shared collections

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

Cohere North

Agent cross-checked Support: partial

Beta Libraries persist shared source collections; alpha Projects are separate private workspaces.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha Projects; Libraries separately Beta; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • size_limits: Alpha Projects default to a 2 GiB aggregate allowance per user across projects. Beta Libraries/uploads use administrator-configured file-size/count settings; complete effective deployment limits were not retrieved.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-11-20261026, cohere-north:cohere-north:n-doc-133-20261026, cohere-north:cohere-north:n-doc-66-20261026, cohere-north:cohere-north:n-doc-18-20261026.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:knowledge, langdock:langdock:file-count, langdock:langdock:agents.

KNOW-03 Enterprise connectors

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

Cohere North

Agent cross-checked Support: partial

North has first-party connectors, custom MCP and an on-prem SharePoint Server path.

Availability: unknown · Delivery: official-integration
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North 2.0.1; Notion/Linear first-party MCP Beta; SharePoint Server Alpha; other connector states per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • microsoft_365: The North 2 announcement names SharePoint, OneDrive, Outlook and Exchange. The October 16 release separately documents read-only Outlook Calendar as alpha. Teams connector entitlement was not established.
  • google_workspace: The retrieved sync guide distinguishes indexed Google Drive Libraries from live Full Access Drive queries. Gmail is documented, but its storage/sync behavior remains unknown because the Syncing and Sharing guides disagree. Google Calendar was not established.
  • atlassian: North 2 names Jira among its connectors. Versioned release notes remove the legacy Jira path in 2.0; no Confluence connector entitlement was established.
  • other_systems: The current North 2 announcement names Slack, Linear, Notion and GitHub. The October 16 release describes Salesforce and PitchBook as alpha features. Customer/third-party MCP connections remain separately configured and licensed.
  • on_prem_sources: The SharePoint Server connector setup is explicitly Alpha. Customer in-network MCP may expose other systems; a native SMB/database inventory and its source-permission guarantees remain unverified.
  • connector_provider: Cohere documents its North connector families and a distinct customer/third-party remote MCP setup. Exact connector-specific maintenance and service commitments require the applicable contract.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:north-release-html-20261026, cohere-north:cohere-north:n-doc-151-20261026, cohere-north:cohere-north:n-doc-152-20261026, cohere-north:cohere-north:n-doc-126-20261026, cohere-north:cohere-north:n-doc-53-20261026.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:integrations, langdock:langdock:sync, langdock:langdock:mcp.

KNOW-04 Permission-aware retrieval

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

Cohere North

Agent cross-checked Support: partial

Indexed retrieval adds runtime source checks; shared snapshots have a separate visibility boundary.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: sensitivity_labels.
  • source_permissions_respected Are source permissions enforced per user? [partial]: Atlas retrieval checks agent scope and user source access; permission-check errors exclude files. This does not re-protect already generated shared chat snapshots; no ACL fixture run. Sources: cohere-north:cohere-north:n-doc-152, cohere-north:cohere-north:n-doc-4.
  • enforcement_point Does the source system, a mirrored index or nothing enforce them? [supported]: Compass retrieves indexed candidates, then Atlas/source API checks filter permissioned documents. Google Drive Full Access queries source directly; local uploads use North sharing rules. Sources: cohere-north:cohere-north:n-doc-152, cohere-north:cohere-north:n-doc-151.
  • revocation_delay How quickly does a removed permission take effect? [partial]: Authorization guide claims external permission changes apply immediately; token/group membership refresh and caches are separate. No measured revocation SLA or fixture. Sources: cohere-north:cohere-north:n-doc-149, cohere-north:cohere-north:n-doc-111.
  • admin_scope_controls Can admins exclude sites, folders or labels? [partial]: Selected sites/folders/files scope Atlas ingestion; library and tool grants scope users/groups. Label-based exclusions not established. Sources: cohere-north:cohere-north:n-doc-64, cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-126.
  • sensitivity_labels Are Microsoft Purview or similar labels respected? [unknown]: Unknown for sensitivity_labels. No two-user ACL revocation or sensitivity-label fixture was run; source API permission claims remain documented, not observed.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-152, cohere-north:cohere-north:n-doc-4, cohere-north:cohere-north:n-doc-151, cohere-north:cohere-north:n-doc-149, cohere-north:cohere-north:n-doc-111, cohere-north:cohere-north:n-doc-64, cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-126.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:sync, langdock:langdock:knowledge, langdock:langdock:labels, langdock:langdock:actions.

KNOW-05 Freshness and sync model

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

Cohere North

Agent cross-checked Support: partial

Atlas file connectors copy selected content to Compass; Drive Full Access uses live API calls. Effective Gmail storage/sync behavior remains unknown.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • live_or_indexed: Atlas file connectors copy selected files to Compass. Google Drive Full Access calls the live API instead. Gmail storage is unknown: the Data Syncing guide says no Compass copy by default, while Data Sharing and the tools overview describe stored/synced email. No live-only Gmail guarantee is asserted.
  • sync_interval: The accessible Data Syncing guide describes periodic Atlas updates and source changes appearing within minutes to hours depending on volume. Drive Full Access is request-time. The previously cited SharePoint/OneDrive 10-minute implementation detail could not be re-retrieved and is not asserted.
  • deletion_propagation: The source-specific SharePoint/OneDrive implementation and Data Deletion pages remain inaccessible in public Markdown/HTML/index forms. General sync documentation does not establish a bounded delete-to-answer or purge interval. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/security/data-syncing?format=html, https://private.docs.cohere.com/north/docs/security/data-sharing?format=html, https://private.docs.cohere.com/north/docs/get-started/tools-overview.md. No additional scoped evidence established this answer.
  • index_location: Compass runs with the customer-controlled North deployment, whose cloud/on-premise placement is selected by the operator. Foundry inference is separately routed to the customer Azure subscription. A universal vendor-hosted index country is not established.
  • live_or_indexed Is content searched live or copied into an index? [partial]: Atlas file connectors copy selected files to Compass. Google Drive Full Access calls the live API instead. Gmail storage is unknown: the Data Syncing guide says no Compass copy by default, while Data Sharing and the tools overview describe stored/synced email. No live-only Gmail guarantee is asserted. Sources: cohere-north:cohere-north:n-doc-151-20261026, cohere-north:cohere-north:n-doc-152-20261026, cohere-north:cohere-north:n-doc-33.
  • sync_interval How often does an index refresh? [partial]: The accessible Data Syncing guide describes periodic Atlas updates and source changes appearing within minutes to hours depending on volume. Drive Full Access is request-time. The previously cited SharePoint/OneDrive 10-minute implementation detail could not be re-retrieved and is not asserted. Sources: cohere-north:cohere-north:n-doc-151-20261026.
  • deletion_propagation How quickly does a deleted document disappear? [unknown]: The source-specific SharePoint/OneDrive implementation and Data Deletion pages remain inaccessible in public Markdown/HTML/index forms. General sync documentation does not establish a bounded delete-to-answer or purge interval. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/security/data-syncing?format=html, https://private.docs.cohere.com/north/docs/security/data-sharing?format=html, https://private.docs.cohere.com/north/docs/get-started/tools-overview.md. No additional scoped evidence established this answer.
  • index_location Where is indexed content stored? [partial]: Compass runs with the customer-controlled North deployment, whose cloud/on-premise placement is selected by the operator. Foundry inference is separately routed to the customer Azure subscription. A universal vendor-hosted index country is not established. Sources: cohere-north:cohere-north:n-doc-165-20261026, cohere-north:cohere-north:n-doc-218-20261026.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-151-20261026, cohere-north:cohere-north:n-doc-152-20261026, cohere-north:cohere-north:n-doc-33, cohere-north:cohere-north:n-doc-165-20261026, cohere-north:cohere-north:n-doc-218-20261026.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:sync, langdock:langdock:integrations, langdock:langdock:terms.

KNOW-06 Grounding and retrieval quality

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

Cohere North

Agent cross-checked Support: partial

Citations are documented but have model-specific limitations; quality remains unmeasured.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: citation_accuracy, cross_language, no_answer_behaviour, observed_accuracy.
  • citations Are answers linked to specific sources? [partial]: Chat highlights open source previews and Project citations exact passages. North Large card acknowledges missing citations in long multi-turn chats and Document Mode. Correctness not tested. Sources: cohere-north:cohere-north:n-doc-1, cohere-north:cohere-north:n-doc-11, cohere-north:cohere-north:n-doc-32.
  • citation_accuracy Do the cited passages support the answer? [unknown]: Unknown for citation_accuracy. Shared DE/FR/EN fixture was not run; citation accuracy, cross-language retrieval, abstention and measured accuracy remain unobserved.
  • cross_language Does a question in one language find documents in another? [unknown]: Unknown for cross_language. Shared DE/FR/EN fixture was not run; citation accuracy, cross-language retrieval, abstention and measured accuracy remain unobserved.
  • no_answer_behaviour Does it say when the corpus has no answer? [unknown]: Unknown for no_answer_behaviour. Shared DE/FR/EN fixture was not run; citation accuracy, cross-language retrieval, abstention and measured accuracy remain unobserved.
  • observed_accuracy How many of the question set were answered correctly? [unknown]: Unknown for observed_accuracy. Shared DE/FR/EN fixture was not run; citation accuracy, cross-language retrieval, abstention and measured accuracy remain unobserved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-1, cohere-north:cohere-north:n-doc-11, cohere-north:cohere-north:n-doc-32.

Langdock

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

KNOW-07 Memory and personal context

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

Cohere North

Agent cross-checked Support: partial

Alpha memory separates editable personal memories from inaccessible agent archival memory.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The vendor marks this control alpha. The catalogue availability field stays unknown because its enum has no alpha value; this does not mean unsupported.
  • custom_instructions Can users set persistent instructions? [supported]: Agents persist instructions; optional company preamble applies across models. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-86.
  • cross_chat_memory Does the product remember facts across chats? [supported]: Alpha personal memory learns across chats; archival memory per agent is generated in background, typically daily. Sources: cohere-north:cohere-north:n-doc-8, cohere-north:cohere-north:n-doc-96.
  • user_memory_controls Can users view, edit and delete memories? [partial]: Personal categories can be viewed/edited; pause retains or Delete removes memory. Archival memories cannot be viewed/edited; manual personal edits can be overwritten by later extraction. Sources: cohere-north:cohere-north:n-doc-8.
  • admin_memory_controls Can admins turn memory off? [supported]: Instance admin can jointly toggle core/archival/conversation memory and configure extraction frequency. Sources: cohere-north:cohere-north:n-doc-96.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-86, cohere-north:cohere-north:n-doc-8, cohere-north:cohere-north:n-doc-96.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:account, langdock:langdock:memory, langdock:langdock:chat.

Assistants and agents

AGT-01 Custom assistants

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

Cohere North

Agent cross-checked Support: partial

North offers versioned custom agents, scoped sharing and an internal catalogue.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The partial atomic answers state their documentation or verification limits.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-21, cohere-north:cohere-north:n-doc-12.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:agents, langdock:langdock:roles, langdock:langdock:workspace.

AGT-02 Tools, actions and MCP

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

Cohere North

Agent cross-checked Support: partial

MCP, code and enterprise tools have scoped authentication and configurable approvals.

Availability: unknown · Delivery: official-integration
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; always-on MCP policies are Alpha; guide recommends testing/staging initially; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The partial atomic answers state their documentation or verification limits.
  • Approval-parameter editing is an interface affordance only in this finding. No execution guarantee is credited without a corrected guide or a bounded tool-call fixture.
  • Always-on MCP configuration is Alpha with a testing/staging recommendation until the organization is ready for broader adoption. Criterion availability remains unknown; this subfact does not establish production readiness.
  • builtin_tools Which tools are built in? [supported]: Built-in search, source connectors, code sandbox, Skills and output capabilities documented with individual states. Sources: cohere-north:cohere-north:n-doc-33, cohere-north:cohere-north:n-doc-34.
  • custom_actions Can admins add API actions? [supported]: Custom MCP servers expose APIs/actions; admin configures tools and auth, with action hints for approval. Sources: cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-150.
  • mcp_client Can it use remote MCP servers, and with what admin control? [supported]: North registers custom/remote MCP; remote OAuth dynamic registration needs outbound access and is unavailable fully air-gapped. Tool access policies can target groups. Always-on MCP policies are Alpha; the guide recommends enabling them only in testing/staging until the organization is ready for broader adoption. Sources: cohere-north:cohere-north:n-doc-126.
  • tool_auth Do tools act as the user or as a shared account? [supported]: Static headers, per-user ID/connector tokens, OAuth client credentials or remote OAuth supported. Shared/static credentials require separate source-policy assessment. Sources: cohere-north:cohere-north:n-doc-126.
  • tool_approval Can admins approve or block tools, and can users confirm actions before they run? [partial]: Destructive-hint tools can pause for approval or denial, and the modal offers parameter editing. Whether edited values execute is unknown: the guide says both that modifications replace the original request and that original keys/values are submitted. Allow Always and advance automation action permissions can bypass later prompts; universal per-action confirmation is not guaranteed. Sources: cohere-north:cohere-north:n-doc-150, cohere-north:cohere-north:n-doc-30.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-33, cohere-north:cohere-north:n-doc-34, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-150, cohere-north:cohere-north:n-doc-30.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:chat, langdock:langdock:actions, langdock:langdock:mcp, langdock:langdock:integrations, langdock:langdock:changes.

AGT-03 Web search and deep research

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

Cohere North

Agent cross-checked Support: partial

GA web search and alpha Deep Research are distinct capabilities.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Web search GA; Deep Research alpha.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-74, cohere-north:cohere-north:n-doc-15.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:web, langdock:langdock:workspace, langdock:langdock:research.

AGT-04 Workflows and automation

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

Cohere North

Agent cross-checked Support: partial

Node workflows support schedules, API invocation and human review.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The partial atomic answers state their documentation or verification limits.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-29, cohere-north:cohere-north:n-doc-30, cohere-north:cohere-north:n-api-run, cohere-north:cohere-north:n-doc-26.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workflows, langdock:langdock:changes.

AGT-05 Agentic task execution

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

Cohere North

Agent cross-checked Support: partial

North executes multi-step work with visible tasks, approval options and workflow cancellation.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The partial atomic answers state their documentation or verification limits.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-15, cohere-north:cohere-north:n-doc-34, cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-30, cohere-north:cohere-north:n-doc-4, cohere-north:cohere-north:n-doc-150, cohere-north:cohere-north:n-doc-26.

Langdock

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.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:agents, langdock:langdock:research, langdock:langdock:changes, langdock:langdock:hitl, langdock:langdock:mcp, langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace, langdock:langdock:outlook-rev2-20261026, langdock:langdock:outlook-admin-20261026, langdock:langdock:pricing-20261026, langdock:langdock:agents-20261026, langdock:langdock:research-20261026, langdock:langdock:changes-20261026, langdock:langdock:hitl-20261026, langdock:langdock:mcp-20261026, langdock:langdock:excel-20261026.

AGT-06 Programmable access

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

Cohere North

Agent cross-checked Support: partial

North has its own authenticated REST APIs for responses, agents, files, libraries and workflows.

Availability: unknown · Delivery: native
Scope: surfaces=North instance REST API and SDK access; version=North 2.0.1 docs; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: mcp_server.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-north-api, cohere-north:cohere-north:n-api-response, cohere-north:cohere-north:n-api-upload, cohere-north:cohere-north:n-api-libraries, cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-89, cohere-north:cohere-north:n-doc-140.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:knowledge, langdock:langdock:billing, langdock:langdock:extra, langdock:langdock:mcp-server.

Daily work

WORK-01 Clients and access points

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

Cohere North

Agent cross-checked Support: partial

North has web and mobile access; desktop/MDM coverage is unknown.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, North iOS and alpha Android app; version=not specified; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: desktop_apps, browser_extension, managed_deployment.
  • web Is a full web client available? [supported]: Full browser chat, Admin and builders documented. Sources: cohere-north:cohere-north:n-doc-1, cohere-north:cohere-north:n-doc-18.
  • desktop_apps Windows and macOS apps? [unknown]: Unknown for desktop_apps. Web and alpha mobile are documented; no desktop package, browser extension, MDM deployment matrix or mobile SSO test was retrieved.
  • mobile_apps iOS and Android apps with SSO? [partial]: October 16 release documents Android alpha with iOS feature parity for agents/automations/record/translate. Mobile SSO/installation workflow not tested. Sources: cohere-north:cohere-north:n-north-changelog.
  • browser_extension Is there a browser extension or sidebar? [unknown]: Unknown for browser_extension. Web and alpha mobile are documented; no desktop package, browser extension, MDM deployment matrix or mobile SSO test was retrieved.
  • managed_deployment Can IT deploy and configure clients through MDM? [unknown]: Unknown for managed_deployment. Web and alpha mobile are documented; no desktop package, browser extension, MDM deployment matrix or mobile SSO test was retrieved.
  • client_feature_gaps Which features are missing on mobile? [partial]: Mobile record/translate and document review are documented; complete web/admin/builders parity and managed-client matrix not retrieved. Sources: cohere-north:cohere-north:n-north-changelog, cohere-north:cohere-north:n-doc-97.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-1, cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-north-changelog, cohere-north:cohere-north:n-doc-97.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:desktop-product, langdock:langdock:mobile-rev2, langdock:langdock:mobile-product, langdock:langdock:desktop-rev2, langdock:langdock:file-count.

WORK-02 Office suite and Teams integration

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

Cohere North

No public information found Support: not-published

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

Langdock

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 ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace, langdock:langdock:teams, langdock:langdock:outlook-rev2-20261026, langdock:langdock:outlook-admin-20261026, langdock:langdock:pricing-20261026, langdock:langdock:excel-20261026, langdock:langdock:teams-20261026.

WORK-03 Translation and writing

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

Cohere North

Agent cross-checked Support: partial

Document mode supports translation and writing; controlled layout-preserving translation is unverified.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: translation_engine, glossaries.
  • document_translation Can whole documents be translated with formatting kept? [partial]: Document mode can translate whole generated documents or selections; shortcut is alpha. Preservation of uploaded document layout, tables and glossary terms untested. Sources: cohere-north:cohere-north:n-doc-9.
  • translation_engine Which engine translates? [unknown]: Unknown for translation_engine. Document mode supports translation/rewriting. Layout-preserving file translation, managed glossary, dedicated engine and de-CH controls were not established.
  • glossaries Are company glossaries supported? [unknown]: Unknown for glossaries. Document mode supports translation/rewriting. Layout-preserving file translation, managed glossary, dedicated engine and de-CH controls were not established.
  • formality_and_variants Can formality and regional variants (de-CH) be set? [partial]: Tone actions include professional/friendly/concise/persuasive and prompts can request formal rewrites. Dedicated de-CH/regional controls not established. Sources: cohere-north:cohere-north:n-doc-9.
  • writing_tools Are dedicated rewrite and proofreading tools available? [supported]: Document editor supports rewriting, tone/length actions, manual edits and prompt-guided revision with history. Sources: cohere-north:cohere-north:n-doc-9.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-9.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:integrations, langdock:langdock:editor.

WORK-04 Image generation and editing

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

Cohere North

No public information found Support: not-published

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

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:images, langdock:langdock:changes, langdock:langdock:byok-models, langdock:langdock:workspace, langdock:langdock:terms.

WORK-05 Voice and meetings

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

Cohere North

Agent cross-checked Support: partial

Alpha dictation and beta long-form mobile recording are documented.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, North iOS and alpha Android app; version=not specified; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Dictation alpha; long-form mobile recording beta.
  • Remaining atomic gaps: read_aloud, voice_conversation, swiss_german_speech.
  • dictation Can users dictate prompts? [supported]: Off-by-default alpha dictation supports web/mobile prompts and some instruction/automation fields; configured ASR and microphone permission required. Sources: cohere-north:cohere-north:n-doc-97, cohere-north:cohere-north:n-doc-1.
  • read_aloud Can answers be read aloud? [unknown]: Unknown for read_aloud. Dictation and long-form mobile recording have alpha/beta states. Read-aloud, conversational speech, automatic meeting capture and Swiss German quality were not established.
  • voice_conversation Is a live voice mode available? [unknown]: Unknown for voice_conversation. Dictation and long-form mobile recording have alpha/beta states. Read-aloud, conversational speech, automatic meeting capture and Swiss German quality were not established.
  • meeting_summaries Are meetings transcribed and summarised? [partial]: North can summarise supplied meeting transcripts; beta mobile long recording exists. Automatic meeting participation/transcription and accuracy unverified. Sources: cohere-north:cohere-north:n-doc-1, cohere-north:cohere-north:n-doc-97.
  • swiss_german_speech Is Swiss German speech recognised? [unknown]: Unknown for swiss_german_speech. Dictation and long-form mobile recording have alpha/beta states. Read-aloud, conversational speech, automatic meeting capture and Swiss German quality were not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-97, cohere-north:cohere-north:n-doc-1.

Langdock

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

WORK-06 Data analysis and document output

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

Cohere North

Agent cross-checked Support: partial

Beta sandbox/Skills create Office files. Document mode supports iteration, with alpha incremental editing distinguished from the broader document workflow.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha incremental document editing; sandbox/Skills separately Beta; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • data_analysis: Beta Skills run file-producing work through sandbox_run_python or sandbox_run_command and provide spreadsheet/CSV operations. The sandbox service and skills permission must be enabled. Analysis correctness and formula preservation were not benchmarked.
  • charts: The document-mode guide describes Data Interpreter creating a chart and embedding it in the editor. The inaccessible sandbox/interpreter guides do not establish a complete plotting-library inventory; chart correctness was not tested.
  • data_analysis Can it analyse spreadsheets with executed code? [partial]: Beta Skills run file-producing work through sandbox_run_python or sandbox_run_command and provide spreadsheet/CSV operations. The sandbox service and skills permission must be enabled. Analysis correctness and formula preservation were not benchmarked. Sources: cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:north-release-html-20261026.
  • charts Can it produce charts? [partial]: The document-mode guide describes Data Interpreter creating a chart and embedding it in the editor. The inaccessible sandbox/interpreter guides do not establish a complete plotting-library inventory; chart correctness was not tested. Sources: cohere-north:cohere-north:n-doc-9-20261026.
  • office_file_output Can it create Word, Excel or PowerPoint files? [supported]: Beta Skills include DOCX/PPTX/XLSX/CSV creation/editing; model and sandbox prerequisites apply. Sources: cohere-north:cohere-north:n-doc-12-20261026.
  • canvas_editing Is there a document or canvas editor for iterating on output? [supported]: Document mode combines direct editing, prompted edits, version history and PDF/DOCX/MD/HTML export. Incremental document-editing controls are alpha; this does not make the whole criterion beta or generally available. Sources: cohere-north:cohere-north:n-doc-9-20261026, cohere-north:cohere-north:n-north-changelog-20261026.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:north-release-html-20261026, cohere-north:cohere-north:n-doc-9-20261026, cohere-north:cohere-north:n-north-changelog-20261026.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:analysis, langdock:langdock:changes, langdock:langdock:editor.

WORK-07 Sharing and team spaces

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

Cohere North

Agent cross-checked Support: partial

Shared snapshots and source collections have different access boundaries.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: group_chat.
  • share_chats Can chats be shared inside the organisation? [supported]: Signed-in colleagues open read-only snapshot links with messages, citations, thinking and presented sandbox files; subsequent changes need a new link. Sources: cohere-north:cohere-north:n-doc-4.
  • team_spaces Are shared projects or workspaces available? [partial]: Beta Libraries share collections via user/group/company roles. Alpha Projects are private per-user workspaces; not shared team Projects. Sources: cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-11.
  • group_chat Can several people chat together with the AI? [unknown]: Unknown for group_chat. Chat links are static read-only snapshots. Concurrent human group chat and rechecking original-source ACLs on all shared-answer content were not established.
  • share_permission_boundary Does sharing respect the recipient's access to sources? [partial]: Shared chat exposes existing answer text/files to signed-in recipients; no original-source ACL recheck established. Library/agent retrieval separately checks source and library access. Sources: cohere-north:cohere-north:n-doc-4, cohere-north:cohere-north:n-doc-152.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-4, cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-11, cohere-north:cohere-north:n-doc-152.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:account, langdock:langdock:projects, langdock:langdock:teams.

WORK-08 Interface languages and accessibility

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

Cohere North

Agent cross-checked Support: partial

User UI offers German and French among eight languages; accessibility and admin translation remain gaps.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: accessibility_statement, admin_ui_languages.
  • ui_languages Which UI languages are offered? [supported]: Guide lists English default, Spanish, French, Portuguese, Arabic, Japanese, Korean and German. Italian is not in this documented selector list. Sources: cohere-north:cohere-north:n-doc-1.
  • dach_language_quality Are German, French and Italian UIs complete and natural? [partial]: German/French available; Italian not listed. Completeness/naturalness was not tested and model language support does not prove UI quality. Sources: cohere-north:cohere-north:n-doc-1.
  • accessibility_statement Is there a WCAG conformance statement? [unknown]: Unknown for accessibility_statement. Eight user UI languages are listed. No WCAG conformance statement, complete German admin UI inventory or DE/FR/IT usability assessment was retrieved.
  • admin_ui_languages Is the admin interface available in German? [unknown]: Unknown for admin_ui_languages. Eight user UI languages are listed. No WCAG conformance statement, complete German admin UI inventory or DE/FR/IT usability assessment was retrieved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-1.

Langdock

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

Administration and governance

ADM-01 Single sign-on and authentication

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

Cohere North

Agent cross-checked Support: partial

North supports OIDC, SAML and hybrid identity patterns in customer deployments.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: conditional_access, domain_capture.
  • sso_protocols Which SSO protocols and identity providers work? [supported]: Dex-based broker supports OIDC preferred/SAML legacy, LDAP shim, Entra-LDAP hybrid and authentication proxy; interactive SSO uses authorization-code PKCE. Sources: cohere-north:cohere-north:n-doc-105.
  • sso_plan Which plan includes SSO? [partial]: SSO is documented for deployed North; no public commercial tier restriction or included-price matrix retrieved. Sources: cohere-north:cohere-north:n-doc-105.
  • mfa Can MFA be enforced? [partial]: Authentication proxy supports external MFA chains; no standalone North-enforced MFA policy was retrieved. Sources: cohere-north:cohere-north:n-doc-105.
  • conditional_access Do Entra conditional-access policies apply? [unknown]: Unknown for conditional_access. SSO protocols and IdP integration are documented. Tenant MFA/conditional-access enforcement and domain capture were not exercised.
  • domain_capture Can the company claim its email domain? [unknown]: Unknown for domain_capture. SSO protocols and IdP integration are documented. Tenant MFA/conditional-access enforcement and domain capture were not exercised.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-105.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:saml, langdock:langdock:account, langdock:langdock:billing.

ADM-02 User provisioning and lifecycle

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

Cohere North

Agent cross-checked Support: partial

JIT and alpha SCIM provision users/groups; deletion preserves selected shared assets.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • SCIM alpha; graceful deletion settings beta. Commercial seat assignment unverified.
  • Remaining atomic gaps: seat_assignment.
  • scim Is SCIM provisioning supported? [supported]: SCIM2 alpha provides user/group lifecycle and is bidirectional; incompatible with some connector group-filter settings. Sources: cohere-north:cohere-north:n-doc-112.
  • group_sync Are identity-provider groups synced? [partial]: JIT groups hydrate at login/session refresh; SCIM can sync groups including matching preregistered names. No propagation measurement. Sources: cohere-north:cohere-north:n-doc-111, cohere-north:cohere-north:n-doc-112.
  • jit_provisioning Are users created at first login? [supported]: First successful login automatically creates user linked to external ID; no pre-invite required in this documented mode. Sources: cohere-north:cohere-north:n-doc-111.
  • deprovisioning What happens to a removed user's data and shared assets? [supported]: Disable removes access reversibly; delete uses grace policy, keeps shared agents/workflows/files but removes Microsoft libraries even if shared. Admin can transfer preserved assets; cleanup asynchronous. Sources: cohere-north:cohere-north:n-doc-112, cohere-north:cohere-north:n-doc-90, cohere-north:cohere-north:n-doc-153.
  • seat_assignment Can admins assign and reclaim seats? [unknown]: Unknown for seat_assignment. JIT and alpha bidirectional SCIM are documented. Commercial seat assignment and measured identity-propagation timing were not retrieved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-112, cohere-north:cohere-north:n-doc-111, cohere-north:cohere-north:n-doc-90, cohere-north:cohere-north:n-doc-153.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:scim, langdock:langdock:scim-entra, langdock:langdock:workspace, langdock:langdock:leaver, langdock:langdock:sync.

ADM-03 Roles, groups and feature permissions

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

Cohere North

Agent cross-checked Support: partial

North delegates fine-grained roles/groups; separately administered subsidiaries count as application instances.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The partial atomic answers state their documentation or verification limits.
  • admin_roles Which admin roles exist, and can admin rights be delegated? [supported]: System roles include Agent/Automation/Tools managers, Compliance Requester/Approver and Library Access Manager; custom roles and individual temporary assignments. Some grants, including model configuration, must be assigned directly. Sources: cohere-north:cohere-north:n-doc-114.
  • groups Can permissions be set per group? [supported]: Permissions/roles/resources assign users, IdP groups or company. JIT group membership updates with token/session refresh; rename/delete needs configuration review. Sources: cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-111.
  • feature_toggles Which features can be switched on or off per group? [supported]: Group grants control agents, tools, libraries, automation and some admin capabilities; models additionally have alpha RBAC and inherited-owner exceptions. Sources: cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-134, cohere-north:cohere-north:n-doc-18.
  • multi_entity Can subsidiaries or departments be separated within one contract? [partial]: Separate administered installation with its own users/config/data is a separate licensed Application Instance, including business units/subsidiaries. Single-contract multi-instance price unknown. Sources: cohere-north:cohere-north:n-doc-158.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-111, cohere-north:cohere-north:n-doc-134, cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-158.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:roles, langdock:langdock:workspace, langdock:langdock:actions.

ADM-04 Usage and adoption analytics

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

Cohere North

Agent cross-checked Support: partial

Alpha analytics offers detailed adoption/usage exports with named-user visibility.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The vendor marks this control alpha. The catalogue availability field stays unknown because its enum has no alpha value; this does not mean unsupported.
  • adoption_dashboard Is there an adoption dashboard? [supported]: Separate Helm/ClickHouse analytics stack reports adoption, agents, automations, tools and libraries with date/group filters. Sources: cohere-north:cohere-north:n-doc-78.
  • breakdowns Can usage be broken down by group, model, feature and assistant? [supported]: Groups/models/sources/agents/workflows/tools and user leaderboards documented; sampled/capped cards have explicit limitations. Sources: cohere-north:cohere-north:n-doc-78.
  • export Can usage data be exported? [supported]: Cards export CSV data or PNG; CSV includes user names and capped tables export only loaded scope. Sources: cohere-north:cohere-north:n-doc-78.
  • privacy_modes Can per-person reporting be limited or pseudonymised? [partial]: Raw analytics event collection can be disabled and retention configured. This does not establish pseudonymisation or removal of named-user reporting in the dashboard. Sources: cohere-north:cohere-north:n-doc-95, cohere-north:cohere-north:n-doc-78.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-78, cohere-north:cohere-north:n-doc-95.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:exports.

ADM-05 Spend controls and cost allocation

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

Cohere North

Agent cross-checked Support: partial

North reports token use and can limit capacity; a currency budget ledger is unverified.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The vendor marks this control alpha. The catalogue availability field stays unknown because its enum has no alpha value; this does not mean unsupported.
  • Remaining atomic gaps: chargeback.
  • cost_visibility Can admins see cost or consumption per user and group? [partial]: Analytics shows user/group/agent/model token activity; Prometheus/Grafana has provider/model billed/raw counters without per-user labels and can undercount. Currency cost reconciliation unknown. Sources: cohere-north:cohere-north:n-doc-78, cohere-north:cohere-north:n-doc-207.
  • budgets Can budgets be set per user or group? [partial]: Alpha Flow control caps requests/input/output tokens by user/group/rules, not a verified CHF/EUR spend budget. Sources: cohere-north:cohere-north:n-doc-137.
  • budget_enforcement Does reaching a budget alert, block or downgrade? [partial]: Limits block for the window only when Helm proxy deployed; unlimited default/failure allow option can admit use. Currency overshoot bounds and chargeback not tested. Sources: cohere-north:cohere-north:n-doc-137.
  • chargeback Can costs be exported per cost centre? [unknown]: Unknown for chargeback. Token metrics and alpha capacity limits are documented. Currency budgets, billing reconciliation and cost-centre allocation were not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-78, cohere-north:cohere-north:n-doc-207, cohere-north:cohere-north:n-doc-137.

Langdock

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.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:byok, langdock:langdock:byok-limits, langdock:langdock:extra, langdock:langdock:workflow-limits, langdock:langdock:exports.

ADM-06 Audit logs and compliance export

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

Cohere North

Agent cross-checked Support: partial

Alpha audits and approval-controlled compliance export coexist with operator log forwarding.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • content_logging: Alpha Compliance uses a request/approval workflow for 24-hour conversation review and CSV export, including guardrail-blocked/redacted messages. Self-approval is forbidden; view access and self-grants are restricted. Exact Organization admin approval rights remain unknown because the permission table and Reviewing requests prerequisite disagree.
  • siem_export: Audit records can be queried through GET /v1/admin/audits, with an actions endpoint and date/action filters. A complete supported SIEM integration, delivery/retry guarantee or content-stream schema was not established.
  • ediscovery: Compliance supports investigation/preservation downloads; specific eDiscovery/legal hold preventing deletion was not established.
  • log_retention: Retrieved Audits and Compliance pages do not state numeric audit-log retention or immutability. Analytics-event retention is a different dataset, and the general Security page could not be retrieved in public representations. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/audits?format=html, https://private.docs.cohere.com/north/docs/admin/compliance?format=html, https://private.docs.cohere.com/north/docs/admin/permissions?format=html. No additional scoped evidence established this answer.
  • admin_events Are admin and security events logged? [supported]: Audits records identity, permission, configuration, model/tool, sharing and compliance events; filters and GET audit API exist. Sources: cohere-north:cohere-north:n-doc-140-20261026.
  • content_logging Can prompts and answers be retained for compliance, and is it configurable? [partial]: Alpha Compliance uses a request/approval workflow for 24-hour conversation review and CSV export, including guardrail-blocked/redacted messages. Self-approval is forbidden; view access and self-grants are restricted. Exact Organization admin approval rights remain unknown because the permission table and Reviewing requests prerequisite disagree. Sources: cohere-north:cohere-north:n-doc-139-20261026.
  • siem_export Can logs stream to a SIEM or be exported? [partial]: Audit records can be queried through GET /v1/admin/audits, with an actions endpoint and date/action filters. A complete supported SIEM integration, delivery/retry guarantee or content-stream schema was not established. Sources: cohere-north:cohere-north:n-doc-140-20261026.
  • ediscovery Are eDiscovery and legal hold supported? [partial]: Compliance supports investigation/preservation downloads; specific eDiscovery/legal hold preventing deletion was not established. Sources: cohere-north:cohere-north:n-doc-139-20261026.
  • log_retention How long are logs kept? [unknown]: Retrieved Audits and Compliance pages do not state numeric audit-log retention or immutability. Analytics-event retention is a different dataset, and the general Security page could not be retrieved in public representations. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/audits?format=html, https://private.docs.cohere.com/north/docs/admin/compliance?format=html, https://private.docs.cohere.com/north/docs/admin/permissions?format=html. No additional scoped evidence established this answer.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-140-20261026, cohere-north:cohere-north:n-doc-139-20261026.

Langdock

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 ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:audit, langdock:langdock:compliance-rev2, langdock:langdock:workspace, langdock:langdock:pricing, langdock:langdock:compliance-rev2-20261026, langdock:langdock:audit-20261026, langdock:langdock:workspace-20261026, langdock:langdock:pricing-20261026.

ADM-07 Data loss prevention and personal data

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

Cohere North

Agent cross-checked Support: partial

Selected-customer beta HiddenLayer can detect/block/redact PII, with permissive defaults and failure paths.

Availability: beta · Delivery: native
Scope: surfaces=Customer-hosted North and Compass Kubernetes deployment, North 2 web application and Admin console; version=not specified; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=Selected-customer HiddenLayer beta deployment; commercial cost unverified; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: custom_patterns.
  • pii_detection Is personal data detected in prompts and files? [partial]: HiddenLayer scans configured prompt/response/tool content and PII entity types; beta available to selected customers after deployment. File coverage depends on what reaches scanned requests, not a verified whole-file DLP pipeline. Sources: cohere-north:cohere-north:n-doc-138.
  • pii_action Is it redacted, masked, blocked or only warned? [partial]: ALLOW/BLOCK/REDACT supported. Default monitor_only does not enforce; background scans and timeouts can occur after delivery, unsupported entities fail open. Effectiveness not tested. Sources: cohere-north:cohere-north:n-doc-138.
  • custom_patterns Can admins add custom patterns or terms? [unknown]: Unknown for custom_patterns. Selected-customer beta HiddenLayer scanning is documented. Custom regex/customer dictionaries and an external enterprise DLP integration matrix were not retrieved.
  • dlp_integration Does it integrate with an existing DLP product? [partial]: HiddenLayer AIDR integration documented; generic existing-DLP/Purview connector not established. Sources: cohere-north:cohere-north:n-doc-138, cohere-north:cohere-north:n-doc-193.
  • filter_location Where does filtering run? [supported]: Documented self-contained GPU engine runs inside customer cluster with external HiddenLayer cloud disabled; requires both HiddenLayer and cohere-guardrails releases. Sources: cohere-north:cohere-north:n-doc-193.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-138, cohere-north:cohere-north:n-doc-193.

Langdock

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

ADM-08 AI policy and guardrails

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

Cohere North

Agent cross-checked Support: partial

Organisation instructions/policy acceptance exist; content safety checks are advisory.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The vendor marks this control alpha. The catalogue availability field stays unknown because its enum has no alpha value; this does not mean unsupported.
  • org_instructions Can admins set organisation-wide instructions? [supported]: Optional company instructions append to preamble across all models; agent instructions also apply. Sources: cohere-north:cohere-north:n-doc-86.
  • usage_notice Can users be required to accept a usage policy? [supported]: Alpha hosted terms can require acceptance at sign-up/tool use and re-acceptance after versions. External terms URL overrides hosted terms. Sources: cohere-north:cohere-north:n-doc-145.
  • content_filters Are content filters configurable? [partial]: Alpha Content Compliance Auditor offers Contextual/Strict, targeted user/group rules and qualified models. Model chooses whether to check/refuse; unavailable/error verdict can be safe, so not mandatory enforcement. Sources: cohere-north:cohere-north:n-doc-138.
  • violation_reporting Are policy hits visible to admins? [supported]: Guardrail Events list conversation decisions/categories/actions. Safety Block means unsafe verdict to model, not proof response was prevented. Sources: cohere-north:cohere-north:n-doc-138.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-86, cohere-north:cohere-north:n-doc-145, cohere-north:cohere-north:n-doc-138.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:gov.

Data protection and sovereignty

DATA-01 Hosting location and data residency

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

Cohere North

Agent cross-checked Support: partial

Private North follows customer infrastructure placement; external inference and support need separate scope.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The partial atomic answers state their documentation or verification limits.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-168, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-doc-218, cohere-north:cohere-north:n-doc-214, cohere-north:cohere-north:n-doc-208, cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-commitments.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:dpa, langdock:langdock:workspace, langdock:langdock:byok-models, langdock:langdock:account, langdock:langdock:security.

DATA-02 Deployment options

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

Cohere North

Agent cross-checked Support: partial

North can run in customer cloud, on-prem or air-gapped; optional managed inference changes that boundary.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: multi_tenant_saas.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-vault, cohere-north:cohere-north:n-doc-165, cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-doc-168, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-159, cohere-north:cohere-north:n-doc-14, cohere-north:cohere-north:n-doc-193.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:security, langdock:langdock:account, langdock:langdock:chat.

DATA-03 Training use and provider retention

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

Cohere North

Agent cross-checked Support: partial

Private North and hosted model APIs have different data-use policies.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The partial atomic answers state their documentation or verification limits.
  • vendor_training Does the vendor train on customer content? [partial]: Private deployment commitments say Cohere receives no prompts/outputs. Cohere Platform API separately permits opt-out training; do not apply that SaaS default to private North. Optional Vault processes inference. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-217.
  • provider_training Do model providers train on it under this product's contracts? [partial]: Self-hosted inference does not call external provider. If operator configures third-party APIs, their customer contracts govern; no blanket no-training assurance retrieved. Sources: cohere-north:cohere-north:n-doc-177, cohere-north:cohere-north:n-commitments.
  • provider_retention How long do model providers keep prompts, including for abuse monitoring? [partial]: Separate Cohere SaaS model Platform logs default30 days with legal/contract/abuse exceptions; private North retention configured locally. Other configured provider retention unverified. Sources: cohere-north:cohere-north:n-commitments.
  • zero_retention Is zero data retention available, and on which plan? [partial]: North↔Model Vault guide documents optional ZDR for inference; North app data remains stored locally. Platform ZDR approval applies separately; not zero chat persistence. Sources: cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-commitments.
  • human_review Can provider staff review content? [partial]: Private prompts do not reach Cohere by default. Platform security teams may review flagged logs; local admins/investigators can review under North compliance process. Third-party staff rules unknown. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-139.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-doc-177, cohere-north:cohere-north:n-doc-139.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms-rev2.

DATA-04 Retention and deletion

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

Cohere North

Agent cross-checked Support: partial

Retention and deletion are operator-configured with separate conversation and user policies.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Conversation retention alpha; graceful account deletion beta. Commercial exit deadline unknown.
  • Remaining atomic gaps: contract_end_deletion.
  • default_retention What is retained and for how long by default? [partial]: Automatic conversation age retention off by default; manually deleted conversations still hard-delete on hourly job with zero effective timeout. Backup/shared-resource retention differs. Sources: cohere-north:cohere-north:n-doc-88, cohere-north:cohere-north:n-doc-153.
  • admin_retention Can admins set retention periods? [supported]: Alpha enabled defaults90 days from creation plus30-day soft-delete timeout; configurable1+days and0–365days. Retroactive changes and batch queues can affect timing. Sources: cohere-north:cohere-north:n-doc-88.
  • user_deletion Can users delete their chats and files permanently? [partial]: Users delete conversations; hourly hard cleanup removes messages/metadata with best-effort external resources. Account private-data cleanup follows beta grace policy; shared assets can persist. Sources: cohere-north:cohere-north:n-doc-153, cohere-north:cohere-north:n-doc-90.
  • contract_end_deletion What is deleted at contract end, and when? [unknown]: Unknown for contract_end_deletion. Conversation/user deletion policies are documented. Commercial contract-end deletion and guaranteed backup purge deadlines were not retrieved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-88, cohere-north:cohere-north:n-doc-153, cohere-north:cohere-north:n-doc-90.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:retention, langdock:langdock:pricing, langdock:langdock:workspace, langdock:langdock:dpa.

DATA-05 Sub-processors and foreign-law exposure

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

Cohere North

Agent cross-checked Support: partial

Published terms name Cohere Inc. and the Trust Center lists subprocessors; ultimate post-combination ownership and the complete contracted North inventory remain unknown.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=Published Cohere terms and Trust Center as retrieved 2026-10-21; post-combination ownership excluded as unverified; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • subprocessor_list: Trust Center exposes subprocessors but no visible revision date; complete North-specific contracted inventory not verified.
  • subprocessor_countries: Visible rows list Google Cloud, Fullstory, LaunchDarkly, New Relic, Retool, Sentry, Segment, Sendgrid and Vercel in USA. Scope mainly hosted services, not automatic private North content recipients.
  • change_notification: Unknown for change_notification. Public Trust Center lists subprocessors without a visible revision date. Full contracted North scope, change notices and post-combination legal structure remain unverified. Search on 2026-10-26: https://trustcenter.cohere.com/?format=html, https://cohere.com/terms-of-use, https://cohere.com/blog/cohere-and-aleph-alpha-sign-agreement. No additional scoped evidence established this answer.
  • parent_jurisdiction: The public terms name Cohere Inc. and Ontario/Toronto law. The September 16 Aleph Alpha business-combination agreement remains described as subject to final regulatory approvals in that announcement. Current October 15 AISLE copy calls Aleph Alpha a partnership, not a completed acquisition; no subsequent first-party closing notice was located. A post-combination parent/jurisdiction is not asserted.
  • transfer_mechanism: Trust Center says its multi-jurisdictional DPA incorporates2021 EU SCCs and describes a TIA. NDA-gated DPA and exact Swiss adaptations not inspected.
  • government_access_policy: Trust FAQ describes prompt customer notice of government requests unless prohibited, within DPA commitments. Actual North contract/transparency statistics unverified.
  • subprocessor_list Is a dated sub-processor list published? [partial]: Trust Center exposes subprocessors but no visible revision date; complete North-specific contracted inventory not verified. Sources: cohere-north:cohere-north:n-trust-20261026.
  • subprocessor_countries Which countries do sub-processors operate in? [partial]: Visible rows list Google Cloud, Fullstory, LaunchDarkly, New Relic, Retool, Sentry, Segment, Sendgrid and Vercel in USA. Scope mainly hosted services, not automatic private North content recipients. Sources: cohere-north:cohere-north:n-trust-20261026.
  • change_notification Are customers notified of sub-processor changes? [unknown]: Unknown for change_notification. Public Trust Center lists subprocessors without a visible revision date. Full contracted North scope, change notices and post-combination legal structure remain unverified. Search on 2026-10-26: https://trustcenter.cohere.com/?format=html, https://cohere.com/terms-of-use, https://cohere.com/blog/cohere-and-aleph-alpha-sign-agreement. No additional scoped evidence established this answer.
  • parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: The public terms name Cohere Inc. and Ontario/Toronto law. The September 16 Aleph Alpha business-combination agreement remains described as subject to final regulatory approvals in that announcement. Current October 15 AISLE copy calls Aleph Alpha a partnership, not a completed acquisition; no subsequent first-party closing notice was located. A post-combination parent/jurisdiction is not asserted. Sources: cohere-north:cohere-north:n-terms-20261026, cohere-north:cohere-north:n-combination-20261026, cohere-north:cohere-north:corporate-aisle-20261026.
  • transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [partial]: Trust Center says its multi-jurisdictional DPA incorporates2021 EU SCCs and describes a TIA. NDA-gated DPA and exact Swiss adaptations not inspected. Sources: cohere-north:cohere-north:n-trust-20261026.
  • government_access_policy Is there a published government-access or transparency policy? [partial]: Trust FAQ describes prompt customer notice of government requests unless prohibited, within DPA commitments. Actual North contract/transparency statistics unverified. Sources: cohere-north:cohere-north:n-trust-20261026.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-trust-20261026, cohere-north:cohere-north:n-terms-20261026, cohere-north:cohere-north:n-combination-20261026, cohere-north:cohere-north:corporate-aisle-20261026.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:dpa, langdock:langdock:terms.

DATA-06 Contracts and regulatory coverage

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

Cohere North

Agent cross-checked Support: partial

DPA and regulatory resources are listed, but North-specific contract terms remain unverified.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The partial atomic answers state their documentation or verification limits.
  • dpa Is a DPA available, and is it negotiable? [partial]: Trust Center says DPA available on request with NDA; Enterprise Data Commitments offers SaaS DPA but says private deployment receives no input processing. No contact/request made; North negotiated terms unknown. Sources: cohere-north:cohere-north:n-trust, cohere-north:cohere-north:n-commitments.
  • revdsg_gdpr Does the DPA cover revDSG and GDPR? [partial]: Vendor says multi-jurisdictional DPA/GDPR compliance. Explicit revised Swiss DSG terms not retrieved from gated DPA. Sources: cohere-north:cohere-north:n-trust.
  • governing_law Which law and court govern the contract? [partial]: General 2022website/service terms choose Ontario/Canadian law and Toronto courts, subject to subscription agreement. Binding North commercial agreement not retrieved. Sources: cohere-north:cohere-north:n-terms.
  • ai_act_materials Is EU AI Act documentation provided? [partial]: Trust Center lists EU AI Act/GPAI Code of Practice FAQs. Contents and North deployment obligations not inspected. Sources: cohere-north:cohere-north:n-trust.
  • sector_materials Are FINMA or other sector materials provided? [partial]: Trust FAQ says BAA only for approved custom model development and excludes Cohere-hosted SaaS/PHI. North-specific health/FINMA contract not retrieved. Sources: cohere-north:cohere-north:n-trust.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-trust, cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-terms.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:dpa, langdock:langdock:pricing, langdock:langdock:gov, langdock:langdock:legal.

DATA-07 Certifications and attestations

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

Cohere North

Agent cross-checked Support: partial

Trust Center lists attestations; certificates and reports were not verified.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: c5.
  • iso_27001 ISO 27001 with scope and validity? [partial]: ISO 27001 certificate listed behind request; issuer, scope and validity unknown. Sources: cohere-north:cohere-north:n-trust.
  • soc2 SOC 2 type, period and covered service? [partial]: SOC 2 Type II annual audit/report listed, request and signed mutual NDA needed; report period/scope not inspected. Sources: cohere-north:cohere-north:n-trust.
  • c5 BSI C5 attestation? [unknown]: Unknown for c5. Trust Center lists certificates and reports behind requests. Issuer, scope, validity and independent report contents were not inspected.
  • other_certifications Which other certificates (27701, 42001, TISAX)? [partial]: ISO 42001 and UK Cyber Essentials for Cohere Inc./Cohere UK listed. Certificate validity/scope not inspected. Sources: cohere-north:cohere-north:n-trust.
  • report_access How can customers obtain reports? [supported]: Trust Center requests gate reports; SOC 2 requires signed mutual NDA, DPA also NDA-gated. No request made. Sources: cohere-north:cohere-north:n-trust.
  • pentest Are independent penetration test summaries available? [partial]: Latest API and web penetration test reports listed behind request; findings/scope/date not inspected. Sources: cohere-north:cohere-north:n-trust.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-trust.

Langdock

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

DATA-08 Encryption and key control

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

Cohere North

Agent cross-checked Support: partial

Customer keys can encrypt chat columns; workflows and other stores need separate controls.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The partial atomic answers state their documentation or verification limits.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-154, cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-159, cohere-north:cohere-north:n-doc-158.

Langdock

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

DATA-09 Professional secrecy

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

Cohere North

Agent cross-checked Support: partial

Profession-specific secrecy undertaking and add-on remain unknown; general confidentiality and scoped content-access controls do not establish §203 StGB or Art.321 StGB coverage.

Availability: unknown · Delivery: unknown
Scope: surfaces=Customer-hosted North and Compass Kubernetes deployment, North 2 web application and Admin console, Optional Cohere-managed Model Vault inference with customer-hosted North; version=North 2.0.1; plan=Customer-hosted North 2.0.1 under custom commercial contract; optional Model Vault/external models separately scoped; add_ons=none stated; deployment_mode=not specified; region=No profession-specific DE/CH contractual scope verified; deployment/provider regions follow the other scoped claims.; os=not specified.

Limitations

  • Contract facts only; no legal suitability assessment. No profession-specific commitment or paid option inferred from generic confidentiality, hosting, encryption or no-training terms.
  • Public, unauthenticated source pass only; no sales contact, NDA request or authenticated access-control test.
  • secrecy_undertaking Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: Unknown. Reviewed North security/encryption/compliance and private-deployment data flows, Trust Center and Enterprise Data Commitments, plus targeted first-party professional-secrecy searches. DPA is request/NDA-gated. No public North §203 StGB or Art.321 StGB undertaking or profession-specific add-on was retrieved; none requested. A DPA or no-training clause alone does not answer whether a profession-specific undertaking is signed.
  • subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [unknown]: Unknown. No retrieved §203/Art.321 undertaking establishes flow-down to all relevant subcontractors/model providers. General DPA confidentiality is not equivalent.
  • secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: Unknown. No documented profession-specific plan, dedicated instance option or paid secrecy add-on and its entitlements/pricing were established.
  • content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: Private-deployment commitments say Cohere does not receive customer prompts/outputs; the local North app decrypts configured chat columns for use and authorised investigators can export conversations. Optional Model Vault processes inference despite ZDR, and external model endpoints follow their contracts. No complete staff/subprocessor plaintext matrix or secrecy undertaking was inspected. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-154, cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-trust.
  • secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Unknown. Reviewed North security/encryption/compliance and private-deployment data flows, Trust Center and Enterprise Data Commitments, plus targeted first-party professional-secrecy searches. DPA is request/NDA-gated. No public North §203 StGB or Art.321 StGB undertaking or profession-specific add-on was retrieved; none requested. General data-flow/security pages are available but do not document such a secrecy offering.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-154, cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-trust.

Langdock

No public information found Support: not-published

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

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.

Cohere North

Agent cross-checked Support: partial

North uses capacity and installation licensing with custom prices.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: overage.
  • pricing_unit What is the pricing unit? [supported]: Compute Units cover model GPU capacity via hardware/model factors; Application Instances count separate administered North installations. Not documented as a universal per-seat tariff. Sources: cohere-north:cohere-north:n-doc-158.
  • list_prices What are list prices per plan, with date and currency? [partial]: North pricing page says custom enterprise pricing; numeric North licence rates not published in retrieved sources. Separate Model Vault/API rates are not North total. Sources: cohere-north:cohere-north:n-pricing.
  • included_usage What usage is included? [partial]: Licensed capacity depends on GPUs/model factors, application instances and contract; no public included-message allowance retrieved. Sources: cohere-north:cohere-north:n-doc-158.
  • add_ons Which features cost extra? [partial]: Model Vault inference, external provider/search API contracts, extra parser/guardrail GPUs and deployment services may add cost; exact included entitlements/rates unknown. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-193, cohere-north:cohere-north:n-doc-14.
  • overage What do usage beyond limits and premium models cost? [unknown]: Unknown for overage. Compute units/application instances and custom pricing are documented. North rates, included usage, minimums and extras were not quoted or invented.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-193, cohere-north:cohere-north:n-doc-14.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:pricing-rev2, langdock:langdock:limits, langdock:langdock:extra, langdock:langdock:models.

VEN-02 Scenario cost

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

Cohere North

Agent cross-checked Support: partial

Shared-scenario North totals remain unknown because the commercial rates and capacity sizing are not public.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The partial atomic answers state their documentation or verification limits.
  • cost_200 Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21: twelve months, excl VAT, no discounts, 330 messages/user/month. At 200 users, North licence/capacity, infrastructure, implementation and support are unknown in EUR/CHF. No total or nonzero floor can be calculated without North tariff and sizing. Separate Model Vault/API prices are not substitutes. FX basis: ECB 2026-10-20 EUR1=USD1.1215=CHF0.9237. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:fx-ecb.
  • cost_1000 Year-one cost at 1,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21: twelve months, excl VAT, no discounts, 330 messages/user/month. At 1,000 users, North licence/capacity, infrastructure, implementation and support are unknown in EUR/CHF. No total or nonzero floor can be calculated without North tariff and sizing. Separate Model Vault/API prices are not substitutes. FX basis: ECB 2026-10-20 EUR1=USD1.1215=CHF0.9237. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:fx-ecb.
  • cost_5000 Year-one cost at 5,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21: twelve months, excl VAT, no discounts, 330 messages/user/month. At 5,000 users, North licence/capacity, infrastructure, implementation and support are unknown in EUR/CHF. No total or nonzero floor can be calculated without North tariff and sizing. Separate Model Vault/API prices are not substitutes. FX basis: ECB 2026-10-20 EUR1=USD1.1215=CHF0.9237. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:fx-ecb.
  • variable_share Which part depends on usage? [partial]: Capacity, replicas and external model/search usage vary;330 messages/user does not determine GPUs, parallelism or tool calls. Vendor-recommended model cannot price unknown North commercial terms; variable currency share remains unknown. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-pricing.
  • unknown_parts Which costs could not be priced? [partial]: North licence per CU/instance, minimum capacity, model translation factors for chosen current models, HA/GPU sizing, external usage, storage/network, support, rollout and taxes outside excl VAT basis. No quote/contact requested. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:fx-ecb.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:pricing-rev2, langdock:langdock:billing, langdock:langdock:extra, langdock:langdock:ecb-fx.

VEN-03 Evaluation access

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

Cohere North

Agent cross-checked Support: partial

Public demo and model API trial do not verify a full North tenant trial.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • The partial atomic answers state their documentation or verification limits.
  • free_tier Is there a free tier for business use? [partial]: Pricing page distinguishes free rate-limited model API trial from paid production; trial key prohibited for commercial/production use. A free North business tier not established. Sources: cohere-north:cohere-north:n-pricing.
  • self_serve_trial Is a self-serve business trial available? [partial]: North links instant demo/custom pricing; no self-serve North tenant with SSO/admin/connectors was provisioned or established. Sources: cohere-north:cohere-north:n-home, cohere-north:cohere-north:n-pricing.
  • trial_scope Do trials include SSO, connectors and admin features? [partial]: Free model API trial does not establish North SSO, connectors or administration. Full North evaluation scope unknown. Sources: cohere-north:cohere-north:n-pricing.
  • sales_gate Does meaningful evaluation require sales contact? [partial]: North custom pricing and private rollout route through sales; whether an independent full tenant evaluation can start without contact remains unknown. No contact made. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-private.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-home, cohere-north:cohere-north:n-private.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:pricing, langdock:langdock:billing.

VEN-04 Contract terms and pricing transparency

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

Cohere North

Agent cross-checked Support: partial

North contract minimums, term and local billing are unverified; pricing is quote-only.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: contract_length, cancellation, local_invoicing.
  • minimum_commitment What seat or spend minimum applies? [partial]: Each separately administered installation counts as an Application Instance; compute-unit licence metric exists, but numeric minimum/spend not retrieved. Sources: cohere-north:cohere-north:n-doc-158.
  • contract_length What contract lengths are offered? [unknown]: Unknown for contract_length. North custom enterprise contract was not public in retrieved sources; minimums, term, reduction and invoice currencies remain unknown.
  • cancellation How can the contract be cancelled or reduced? [unknown]: Unknown for cancellation. North custom enterprise contract was not public in retrieved sources; minimums, term, reduction and invoice currencies remain unknown.
  • local_invoicing Can it be invoiced in CHF or EUR from a European entity? [unknown]: Unknown for local_invoicing. North custom enterprise contract was not public in retrieved sources; minimums, term, reduction and invoice currencies remain unknown.
  • transparency_class Is pricing transparent, partial, quote-only or unknown? [supported]: Quote-only for North licence/deployment. Separate Model Vault instance rates and model API tariffs do not make North pricing transparent. Sources: cohere-north:cohere-north:n-pricing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-pricing.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:pricing, langdock:langdock:security, langdock:langdock:billing, langdock:langdock:terms.

VEN-05 Source licence

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

Cohere North

Agent cross-checked Support: partial

North is commercially licensed; component source rights and branding terms need contract review.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: enterprise_features_closed.
  • licence_type Which licence applies to each component? [partial]: Commercial CU/Application Instance licence documented; full North application/model/component licence texts not retrieved. Sources: cohere-north:cohere-north:n-doc-158.
  • branding_restrictions Do licence terms restrict branding or user counts? [partial]: White-label settings configure product branding; entitlement, use restrictions and licence fee terms unverified. Separate installations count for licensing, with no public per-user cap retrieved. Sources: cohere-north:cohere-north:n-doc-142, cohere-north:cohere-north:n-doc-158.
  • enterprise_features_closed Are enterprise features in a separate closed edition? [unknown]: Unknown for enterprise_features_closed. North is commercially licensed by capacity/installations. Full application/model component licences and branding rights were not publicly retrieved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-doc-142.

Langdock

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

VEN-06 Data export and exit

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

Cohere North

Agent cross-checked Support: partial

APIs and approved exports provide some portability; full tenant exit is unverified.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: post_termination_window.
  • chat_export Can admins export all chats? [partial]: Alpha compliance approves targeted user/agent conversations for24 hours and downloadsCSV. API lists/retrieves conversations; a single complete admin export and preservation hold not established. Sources: cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-north-api.
  • assistant_export Can assistants and prompts be exported in a reusable format? [partial]: Automation definitions export reusableJSON graph/dependencies but omit credentials and schedules. Agent configurations have API access/version history; full portable agent export not established. Sources: cohere-north:cohere-north:n-doc-29, cohere-north:cohere-north:n-north-api.
  • knowledge_export Can knowledge bases and their sources be exported? [partial]: File API retrieves content and library metadata APIs exist; complete all-index/source bulk export and permission preservation not established. Sources: cohere-north:cohere-north:n-api-upload, cohere-north:cohere-north:n-api-libraries.
  • export_format Are formats documented and machine-readable? [partial]: AutomationJSON, complianceCSV, original file API content and documentPDF/DOCX/HTML/TXT/MD are documented. These do not constitute complete tenant-state export. Sources: cohere-north:cohere-north:n-doc-29, cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-doc-9.
  • post_termination_window How long can data be retrieved after termination? [unknown]: Unknown for post_termination_window. Automation JSON, API files and approved compliance CSV are documented. Complete bulk tenant export, agent portability and post-exit recovery window remain unverified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-north-api, cohere-north:cohere-north:n-doc-29, cohere-north:cohere-north:n-api-upload, cohere-north:cohere-north:n-api-libraries, cohere-north:cohere-north:n-doc-9.

Langdock

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 ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:compliance-rev2, langdock:langdock:migration, langdock:langdock:knowledge, langdock:langdock:exports, langdock:langdock:dpa, langdock:langdock:compliance-rev2-20261026, langdock:langdock:migration-20261026, langdock:langdock:knowledge-20261026, langdock:langdock:exports-20261026, langdock:langdock:dpa-20261026.

VEN-07 Support and service levels

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

Cohere North

Agent cross-checked Support: partial

Support resources exist; North SLA, regional entity and support languages remain unknown.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: support_languages, uptime_sla.
  • support_channels Which support channels are available on each plan? [partial]: Private deployments include access to solution architects, applied ML and customer success; public security/support resources exist. Contracted response times unknown. Sources: cohere-north:cohere-north:n-private.
  • support_languages Is support available in German, French or Italian? [unknown]: Unknown for support_languages. Public support/status resources and deployment assistance exist; response languages, North SLA credits and contracted DACH entity were not established.
  • regional_presence Is there a DACH or Swiss entity, team or partner? [partial]: September 16 agreement plans Berlin/Toronto headquarters and Heidelberg research subject to close. A North-contract Swiss/DACH delivery entity or completed combination was not verified. Sources: cohere-north:cohere-north:n-combination.
  • uptime_sla Is there an uptime SLA with credits? [unknown]: Unknown for uptime_sla. Public support/status resources and deployment assistance exist; response languages, North SLA credits and contracted DACH entity were not established.
  • status_page Is there a public status page with history? [partial]: Cohere has a public hosted API status page. Customer-hosted North availability is operator-managed; a North-wide hosted status/SLA not established. Sources: cohere-north:cohere-north:n-status, cohere-north:cohere-north:n-doc-165.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-combination, cohere-north:cohere-north:n-status, cohere-north:cohere-north:n-doc-165.

Langdock

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 ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:billing, langdock:langdock:playbook, langdock:langdock:terms, langdock:langdock:status, langdock:langdock:imprint-20261026, langdock:langdock:terms-20261026, langdock:langdock:status-20261026.

VEN-08 Onboarding, training and adoption

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

Cohere North

Agent cross-checked Support: partial

Deployment assistance and public user/builder guides are offered; included service scope is unknown.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

  • Remaining atomic gaps: adoption_programme, service_cost.
  • onboarding_service Is guided onboarding included? [partial]: Vendor describes rollout support from architects, applied ML and customer success. Included hours/fees are not published. Sources: cohere-north:cohere-north:n-private.
  • user_training Is end-user training offered, in which languages? [partial]: Public user/agent/workflow guides support self-learning. Live end-user training and language entitlement not established. Sources: cohere-north:cohere-north:n-guide, cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-16.
  • use_case_library Are role-based use cases and templates provided? [supported]: Agent guide gives ticket deflection/sales/legal examples and internal agent catalogue permits sharing; document/Skills guides include task examples. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-21, cohere-north:cohere-north:n-doc-12.
  • adoption_programme Is there a champion or adoption programme? [unknown]: Unknown for adoption_programme. Vendor offers rollout assistance and guides; service language, included hours, adoption programme and costs were not retrieved.
  • service_cost Which services cost extra? [unknown]: Unknown for service_cost. Vendor offers rollout assistance and guides; service language, included hours, adoption programme and costs were not retrieved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-guide, cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-21, cohere-north:cohere-north:n-doc-12.

Langdock

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:playbook, langdock:langdock:training, langdock:langdock:billing.

Sources

  1. Headless model providers cohere-north:cohere-north:n-doc-177-20261026

    Operators register Cohere, vLLM, Azure, Bedrock, SageMaker, OpenAI and Anthropic endpoints with customer secrets.

    Provider types, endpoint and credentials; public representation of https://private.docs.cohere.com/north/docs/advanced/headless-configuration/model-providers.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 813d19abcb01a5b84e23e8615ef38b9e94cd57097f91ae7e44a139e6b62c4cbb on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  2. North Large 01-2026 cohere-north:cohere-north:n-doc-32-20261026

    North partnership model accepts text/images with256K input/32K output and48 languages; citation gaps acknowledged.

    Model card and limitations; public representation of https://private.docs.cohere.com/north/docs/north-large-01-2026.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 46ad467b680bd511cfc5f0d3168f40dd32b61be945b039d7cf029b3527b5ece7 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  3. Models and providers cohere-north:cohere-north:n-doc-134-20261026

    Custom endpoints/providers, group access and defaults; grants additive and alias may silently fall back to provider default.

    Beta UI, alpha RBAC, aliases and fallback; public representation of https://private.docs.cohere.com/north/docs/admin/models.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 3ddb8818e63c7322d79680498f711ab0dd1a15dd87f1315c3065bed5171538dd on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  4. Chat cohere-north:cohere-north:n-doc-1-20261026

    Chat model choice, source-linked responses, eight UI languages and configurable voice/image input are documented.

    Model picker, UI languages, image input and dictation; public representation of https://private.docs.cohere.com/north/docs/get-started/north-chat.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 2a609c8b8dc88bce89ad912f7d8c43ee63449c23a0bac0e5fcb5954bf55e0964 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  5. North multimodal features cohere-north:cohere-north:n-doc-14-20261026

    Vision/OCR requires configured models/parser; third-party image input planned, document visual pages limited500.

    Cohere-only image input and visual parser; public representation of https://private.docs.cohere.com/north/docs/get-started/north-automations/building-automations/north-multimodality.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 c4763a8ec53fc0d63b4393939e71c9df423160564cdbc748004dcd7af256faba on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  6. Voice settings cohere-north:cohere-north:n-doc-97-20261026

    Dictation and long-form mobile recording are separately off by default and require configured transcription service.

    Alpha dictation and beta mobile recording; public representation of https://private.docs.cohere.com/north/docs/admin/configuring_voice_settings.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 26565385151f6fa21890665138a7d900c61ea1cbff3bb96f46e67955e5ac54a1 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  7. Skills cohere-north:cohere-north:n-doc-12-20261026

    Built-in/custom skills create/edit DOCX/PPTX/XLSX/CSV using code sandbox and supported models.

    Beta skills and Office file packages; public representation of https://private.docs.cohere.com/north/docs/get-started/skills.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 9167ea7e86e91dabe44c8cbcc8e0f3b3baa5b44badaf1d393bb4ae67e41fdb0d on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  8. North release notes, public HTML cohere-north:cohere-north:north-release-html-20261026

    North 2 documents model aliases, beta Library sharing/Skills and sandbox, alpha controls, version-scoped legacy removals and the October 20 storage patch. Release labels are feature-specific, not a guarantee of private-deployment parity.

    October 16 North 2.0.0 and October 20 2.0.1; Models, Libraries, Google Drive, Skills, Sandbox and Admin; HTTP 200, body SHA256 be38218043c7eb99d836db5d02f86ce71b5af7c2c267327410f58f81936ed720 · documented · Source date 2026-10-20 · Retrieved 2026-10-26

  9. AI Models | Langdock langdock:langdock:models

    Public model table lists current text models and EUR metered prices.

    Provider tables · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  10. Model Guide langdock:langdock:model-guide

    Users select models or Auto routing; reasoning levels vary by model.

    Selecting a Model, Auto and Thinking · documented · Source date not stated · Retrieved 2026-10-21

  11. North release notes cohere-north:cohere-north:n-north-changelog

    Dated releases document new models, beta/alpha capabilities and removal/deprecation of legacy connectors and APIs.

    October 20 v2.0.1 andOctober 16 v2.0.0; migrations · documented · Source date 2026-10-20 · Retrieved 2026-10-21

  12. Deploy models chart cohere-north:cohere-north:n-doc-168

    Customer GPU model chart supports local chat/embed/rerank; serving containers version independently.

    In-cluster generative/Compass components and pinned artifacts · documented · Source date not stated · Retrieved 2026-10-21

  13. Product Changelog | Langdock langdock:langdock:changes

    Dated releases document model additions, desktop apps and per-agent confirmations.

    13 October 2026 model release; 15/10 September feature releases · documented · Source date not stated · Retrieved 2026-10-21

  14. Bedrock Anthropic setup cohere-north:cohere-north:n-doc-135-20261026

    Own AWS account/region and authorized Claude models support chat, agents and automations.

    Customer AWS prerequisites and roles; public representation of https://private.docs.cohere.com/north/docs/admin/bedrock-anthropic.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 185176cbe038586b463babfc0584a55cd212cf96f554cf6eadaf1238e4105617 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  15. Microsoft Foundry with North cohere-north:cohere-north:n-doc-218-20261026

    Customer Azure billing supports chat/embed/rerank/Parse5; sparse and North Large unavailable there, mixed hosting required.

    Customer Azure inference and feature gaps; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 e717dddf6149bafdb68a613b1268d366565e212be0e292d989d1c2a8d960f35e on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  16. https://docs.langdock.com/en/admin/billing/pricing.md langdock:langdock:billing

    Business covers up to 1000 users, BYOK separates model costs, workflows/API are metered and Enterprise is quoted.

    Products, volume tiers, Enterprise and API · documented · Source date not stated · Retrieved 2026-10-21

  17. https://docs.langdock.com/en/admin/byok/byok.md langdock:langdock:byok

    BYOK replaces completion, embedding and image routes; missing model categories break relevant features.

    Options, requirements, setup and usage export · documented · Source date not stated · Retrieved 2026-10-21

  18. Setup Guides langdock:langdock:byok-routes

    Named BYOK routes include cloud providers, Vercel Gateway and self-hosted OpenAI-compatible HTTPS endpoints.

    Provider setup tabs and OpenAI-compatible endpoints · documented · Source date not stated · Retrieved 2026-10-21

  19. Deep Research langdock:langdock:research

    Deep Research creates cited public-web reports and has a 15-per-30-days cap for standard keys.

    Model configuration, limitations and usage · documented · Source date not stated · Retrieved 2026-10-21

  20. Headless model providers cohere-north:cohere-north:n-doc-177

    Operators register Cohere, vLLM, Azure, Bedrock, SageMaker, OpenAI and Anthropic endpoints with customer secrets.

    Provider types, endpoint and credentials · documented · Source date not stated · Retrieved 2026-10-21

  21. North multimodal features cohere-north:cohere-north:n-doc-14

    Vision/OCR requires configured models/parser; third-party image input planned, document visual pages limited500.

    Cohere-only image input and visual parser · documented · Source date not stated · Retrieved 2026-10-21

  22. Microsoft Foundry with North cohere-north:cohere-north:n-doc-218

    Customer Azure billing supports chat/embed/rerank/Parse5; sparse and North Large unavailable there, mixed hosting required.

    Customer Azure inference and feature gaps · documented · Source date not stated · Retrieved 2026-10-21

  23. MCP server administration cohere-north:cohere-north:n-doc-126

    Customer/remote MCP support scoped OAuth/tokens/static headers; remote registration needs internet and dynamic registration.

    Registration, custom headers, permissions and remote limits · documented · Source date not stated · Retrieved 2026-10-21

  24. Terms of Use | Langdock langdock:langdock:terms

    Terms 2.1 prohibit training and describe provider-specific residency and retention agreements, proprietary use rights and contract defaults.

    Sections 6/7/9/12/15/16/19 and Appendix 1 · documented · Source date not stated · Retrieved 2026-10-21

  25. How to add your own models langdock:langdock:byok-models

    Admins configure completion, image and embedding models, deployments, capability flags and USD accounting rates.

    Custom model setup and deployment configuration · documented · Source date not stated · Retrieved 2026-10-21

  26. Creating custom agents cohere-north:cohere-north:n-doc-18-20261026

    Agents combine instructions/models/tools/libraries; shared agents inherit owner model access.

    Instructions, versioning, sharing and model permission model; public representation of https://private.docs.cohere.com/north/docs/get-started/agents/creating-custom-agents.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 6ae6b9abfe4e5de1679146a003d858f773f48d669e0c579e530654feba66aba9 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  27. Flow control cohere-north:cohere-north:n-doc-137-20261026

    User/group/model/source/provider rules enforce request/input/output token limits only after Helm services deployed; fail-open option and unlimited default.

    Alpha model rate-limit proxy; public representation of https://private.docs.cohere.com/north/docs/admin/flow-control.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 b0aabd0e2334636f4ff1d4bea234db5f41b155a385923fbce27a1face1df2312 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  28. Pricing Plans | Langdock langdock:langdock:pricing

    Business headline prices, annual discounts, workflow packages and Governance promotion are public.

    Chat & Agents, price breakdown, add-ons and API · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  29. Workspace Settings langdock:langdock:workspace

    Workspace settings define retention, model defaults, EU-only default enablement, analytics and product controls.

    Product Settings, Models, Analytics and Customizations · documented · Source date not stated · Retrieved 2026-10-21

  30. Usage Limits langdock:langdock:limits

    Five-hour and weekly usage windows trigger extra usage or a fallback; spam protection caps 250 messages per three hours.

    Usage windows and exhaustion · documented · Source date not stated · Retrieved 2026-10-21

  31. Extra Usage langdock:langdock:extra

    Extra usage has workspace/plan/user caps and fallback behavior with possible final-response overshoot.

    Enabling extra usage, spend limits and API exceptions · documented · Source date not stated · Retrieved 2026-10-21

  32. Supported files cohere-north:cohere-north:n-doc-73-20261026

    Documents text/Office/tabular/image/audio formats and configurable processing; My files limit differs from its dedicated guide.

    Formats and100 MB/500 MB limit wording; public representation of https://private.docs.cohere.com/north/docs/get-started/supported-files.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 9bc5a3f6698e34d553cd9b9efd32964736dbe6989a31fc138e6eaec28fe9e680 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  33. My files cohere-north:cohere-north:n-doc-66-20261026

    Guide states50 MB/file and configured totals; image-only PDFs require parser setup and images are not indexed for general Smart Search.

    Upload limit, OCR and Smart Search; public representation of https://private.docs.cohere.com/north/docs/get-started/tools/my-files/home.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 d6f571cfecc507841ce963c91571a3822f44b24d28d0192f21498d4abdcc1c30 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  34. Multimodality configuration cohere-north:cohere-north:n-doc-100-20261026

    Image input currently limited to Cohere vision models; smart parser and infrastructure are separately required.

    Alpha parser/model/feature prerequisites; public representation of https://private.docs.cohere.com/north/docs/admin/multimodality.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 2e036dc55b465b41bcff9b28bb0fc83bb5ff07d7750137f983ef0461fc1ef593 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  35. Which file types does Langdock support? langdock:langdock:files

    Supported files have different type-specific size limits and processing restrictions.

    Format/size tables and processing limits · documented · Source date not stated · Retrieved 2026-10-21

  36. What are the file limits in the chat and in agents? langdock:langdock:file-count

    Web message uploads allow 50 files, mobile five; agent knowledge and knowledge bases have separate limits.

    Chat and agent attachment limits · documented · Source date not stated · Retrieved 2026-10-21

  37. Knowledge Basics langdock:langdock:retrieval

    Direct file previews differ from semantic search over 2000-character chunks, returning up to 50 passages.

    Direct context and embedding search · documented · Source date not stated · Retrieved 2026-10-21

  38. Libraries cohere-north:cohere-north:n-doc-42-20261026

    Libraries bind to agents/chats/nodes; source libraries and uploads have different sharing/access rules.

    Beta persistence, source/sharing and binding; public representation of https://private.docs.cohere.com/north/docs/get-started/tools/libraries.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 dbe8dc45b308026365048a6e52ee685ac8fedfe257517c688f624e9e2ebf4374 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  39. Projects cohere-north:cohere-north:n-doc-11-20261026

    Private indexed project files are isolated to the project; default per-user aggregate storage2 GiB.

    Alpha workspace and storage; public representation of https://private.docs.cohere.com/north/docs/get-started/projects.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 f7d3bab16beb3744f5def211a909d7acebcb6a00cd68b747a826b2d608fd0a0e on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  40. Admin library directory cohere-north:cohere-north:n-doc-133-20261026

    Admins manage library access without seeing contents; groups and company access supported, email libraries private.

    Beta user/group access; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 f4248f5cd4bf98f610b6f39c57494e2834de07e117db292498eca4707a592b8f on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  41. Knowledge bases langdock:langdock:knowledge

    Persistent shareable knowledge bases accept up to 1000 text documents, search chunks and attach to agents.

    Creation, sharing, limits and agent use · documented · Source date not stated · Retrieved 2026-10-21

  42. Agent Configuration langdock:langdock:agents

    Agents combine instructions, files, folders, models, actions, skills and subagents, with optional source-access restrictions.

    Agent configuration, knowledge and source restriction · documented · Source date not stated · Retrieved 2026-10-21

  43. Data syncing cohere-north:cohere-north:n-doc-151-20261026

    Atlas periodic indexing differs from live APIs; generic freshness minutes to hours.

    Atlas copies versus live Gmail/Google Drive Full Access; public representation of https://private.docs.cohere.com/north/docs/security/data-syncing.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 9098552e0be35967acf545ee4d3c6487281481833795c49d487dfe417382184e on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  44. MCP server administration cohere-north:cohere-north:n-doc-126-20261026

    Customer/remote MCP support scoped OAuth/tokens/static headers; remote registration needs internet and dynamic registration.

    Registration, custom headers, permissions and remote limits; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 8b401a0257b45f4b284dd89368b795118eb74b1a2b0d193d56a9b1687e804ea9 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  45. SharePoint Server connector setup cohere-north:cohere-north:n-doc-53-20261026

    Documents customer-network SharePoint Server integration with deployment/auth prerequisites.

    On-prem SharePoint Server prerequisites; public representation of https://private.docs.cohere.com/north/docs/get-started/tools/microsoft-connectors/sharepoint-server-connector-setup.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 10f8e3e90ba4fcf31095515a6fe687de0e080d90e1d72e9d0257a555486a2475 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  46. Data sharing cohere-north:cohere-north:n-doc-152-20261026

    Atlas/source permission checks fail closed for retrieval; old email storage descriptions conflict with live Gmail guide.

    Agent/library scope, runtime checks and private email; public representation of https://private.docs.cohere.com/north/docs/security/data-sharing.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 b001f4de791c2eadc7d050e3863bbd26d4476540f6516d632b1b420bf025ccbd on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  47. North 2 product launch cohere-north:cohere-north:north2-launch-20261026

    The first-party announcement names shared Libraries, Skills, applications, third-party models, user/group governance and built-in enterprise connector families; planned financial connectors are distinguished from current release-specific alpha documentation.

    Core feature and connector lists; model and governance sections · vendor-claimed · Source date 2026-10-05 · Retrieved 2026-10-26

  48. Folder Sync langdock:langdock:sync

    Daily folder sync supports SharePoint, OneDrive, Drive and Confluence, with real-time user access checks.

    Setup, permission checks, sync behavior and owner removal · documented · Source date not stated · Retrieved 2026-10-21

  49. Integration Directory langdock:langdock:integrations

    The native directory lists Microsoft, Google, Atlassian, CRM, BI, vector search, DeepL and audio integrations.

    Native integration directory · documented · Source date not stated · Retrieved 2026-10-21

  50. Model Context Protocol (MCP) langdock:langdock:mcp

    MCP clients support Streamable HTTP/SSE and several authentication types; new tools do not require confirmation by default.

    Transports, authentication and tool confirmation · documented · Source date not stated · Retrieved 2026-10-21

  51. SharePoint implementation cohere-north:cohere-north:n-doc-64

    Selected content is indexed;10-minute sync detects updates/deletes, after source-side indexing permits discovery.

    Compass indexing,10-minute sync and source search dependency · documented · Source date not stated · Retrieved 2026-10-21

  52. Libraries cohere-north:cohere-north:n-doc-42

    Libraries bind to agents/chats/nodes; source libraries and uploads have different sharing/access rules.

    Beta persistence, source/sharing and binding · documented · Source date not stated · Retrieved 2026-10-21

  53. Data syncing cohere-north:cohere-north:n-doc-151

    Atlas periodic indexing differs from live APIs; generic freshness minutes to hours.

    Atlas copies versus live Gmail/Google Drive Full Access · documented · Source date not stated · Retrieved 2026-10-21

  54. Data sharing cohere-north:cohere-north:n-doc-152

    Atlas/source permission checks fail closed for retrieval; old email storage descriptions conflict with live Gmail guide.

    Agent/library scope, runtime checks and private email · documented · Source date not stated · Retrieved 2026-10-21

  55. Sharing and collaborating with chat cohere-north:cohere-north:n-doc-4

    Shared snapshots expose full messages, citations, thinking trace and sandbox files to signed-in recipients.

    Snapshot contents and debug visibility · documented · Source date not stated · Retrieved 2026-10-21

  56. Tool authorization cohere-north:cohere-north:n-doc-149

    Per-user access and runtime source checks documented; revocation immediacy not independently measured.

    OAuth/source permission checks · documented · Source date not stated · Retrieved 2026-10-21

  57. JIT provisioning cohere-north:cohere-north:n-doc-111

    First successful login creates users; groups refresh at authentication/session renewal; admin deprovisioning APIs documented.

    First login and refreshed groups · documented · Source date not stated · Retrieved 2026-10-21

  58. Sensitivity Label Policy langdock:langdock:labels

    A request-enabled Purview label policy filters supported integrations, with documented actions and upload exceptions.

    Availability, enforcement, exceptions and unsupported areas · documented · Source date not stated · Retrieved 2026-10-21

  59. Manage Action Access langdock:langdock:actions

    Admins share integrations and actions with users/groups/API keys; native core actions cannot be disabled.

    Access settings and native-action exception · documented · Source date not stated · Retrieved 2026-10-21

  60. North tools overview cohere-north:cohere-north:n-doc-33

    Names first-party sources and states, including Jira/Slack MCP beta, Atlas SharePointGA and Gmail alpha.

    Per-tool state and categories · documented · Source date not stated · Retrieved 2026-10-21

  61. Deployment model cohere-north:cohere-north:n-doc-165-20261026

    North application Helm chart deployed on customer Kubernetes; GitOps/ArgoCD recommended for production.

    Helm and production GitOps; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 39b2586fa7cca8f9c540e2c02dc9471ed0b3c89484c9f776421e78e477711721 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  62. North Large 01-2026 cohere-north:cohere-north:n-doc-32

    North partnership model accepts text/images with256K input/32K output and48 languages; citation gaps acknowledged.

    Model card and limitations · documented · Source date not stated · Retrieved 2026-10-21

  63. Chat cohere-north:cohere-north:n-doc-1

    Chat model choice, source-linked responses, eight UI languages and configurable voice/image input are documented.

    Model picker, UI languages, image input and dictation · documented · Source date not stated · Retrieved 2026-10-21

  64. Projects cohere-north:cohere-north:n-doc-11

    Private indexed project files are isolated to the project; default per-user aggregate storage2 GiB.

    Alpha workspace and storage · documented · Source date not stated · Retrieved 2026-10-21

  65. Creating custom agents cohere-north:cohere-north:n-doc-18

    Agents combine instructions/models/tools/libraries; shared agents inherit owner model access.

    Instructions, versioning, sharing and model permission model · documented · Source date not stated · Retrieved 2026-10-21

  66. Preamble and prompt settings cohere-north:cohere-north:n-doc-86

    Optional organisation instructions apply across models alongside platform/agent preambles.

    Company instructions · documented · Source date not stated · Retrieved 2026-10-21

  67. Memory cohere-north:cohere-north:n-doc-8

    Personal memories can be edited or deleted; agent archival memory cannot be viewed or edited.

    Alpha personal/archival memory · documented · Source date not stated · Retrieved 2026-10-21

  68. Memory settings cohere-north:cohere-north:n-doc-96

    Instance toggles jointly control core/archival/conversation memory and extraction timing.

    Alpha admin controls · documented · Source date not stated · Retrieved 2026-10-21

  69. Basic Chat functionalities langdock:langdock:chat

    Chat supports model selection and governed tools; memory, deep research and agent tool conditions differ.

    Model selector and tool availability · documented · Source date not stated · Retrieved 2026-10-21

  70. Account Settings langdock:langdock:account

    Account settings include five UI languages, personal controls and temporary 72-hour Support sharing.

    Preferences, shared chats, custom instructions and memory · documented · Source date not stated · Retrieved 2026-10-21

  71. Memory langdock:langdock:memory

    Memory works in regular chats only, with a 50-memory cap and view/edit/delete controls.

    Availability, management and limits · documented · Source date not stated · Retrieved 2026-10-21

  72. Skills cohere-north:cohere-north:n-doc-12

    Built-in/custom skills create/edit DOCX/PPTX/XLSX/CSV using code sandbox and supported models.

    Beta skills and Office file packages · documented · Source date not stated · Retrieved 2026-10-21

  73. Roles and permissions cohere-north:cohere-north:n-doc-114

    Roles/groups delegate permissions; some direct grants cannot be packaged into roles; individual role assignment can expire.

    System/custom roles and grants · documented · Source date not stated · Retrieved 2026-10-21

  74. Browsing agents cohere-north:cohere-north:n-doc-21

    Internal starred/personal/shared/company agent directory supports search and duplication.

    Agent catalogue and duplication · documented · Source date not stated · Retrieved 2026-10-21

  75. Roles and extra permissions langdock:langdock:roles

    System roles, up to five custom roles and delegated group permissions are configurable.

    System roles, custom roles and group permissions · documented · Source date not stated · Retrieved 2026-10-21

  76. Code sandbox cohere-north:cohere-north:n-doc-34

    Persistent per-chat Python/bash runtime creates files/charts and shows executed code; admin deployment/access required.

    Beta execution, files and activity visibility · documented · Source date not stated · Retrieved 2026-10-21

  77. Tool action approvals cohere-north:cohere-north:n-doc-150

    Approval modal can edit/deny action parameters, but tool hints and persistent global bypass limit per-action assurance.

    Destructive actions and global Allow Always · documented · Source date not stated · Retrieved 2026-10-21

  78. Consuming automations cohere-north:cohere-north:n-doc-30

    Schedules support cron/natural language; run viewer shows inputs/outputs and cancellation; action permission accepted at launch.

    Run, cron schedule, approval and cancel · documented · Source date not stated · Retrieved 2026-10-21

  79. Web search cohere-north:cohere-north:n-doc-74

    Tavily defaultGA; Brave/LinkUp alpha; API keys needed; live web page content is not ingested.

    GA provider choices and handling · documented · Source date not stated · Retrieved 2026-10-21

  80. Deep research cohere-north:cohere-north:n-doc-15

    Multi-step cited research requires enabled sources and user/group access, with downloadable reports.

    Alpha feature and administrator grants · documented · Source date not stated · Retrieved 2026-10-21

  81. Web Search langdock:langdock:web

    Web search returns inspectable citations and has a separate open-URL tool.

    Search behavior and source inspection · documented · Source date not stated · Retrieved 2026-10-21

  82. Automations cohere-north:cohere-north:n-doc-16

    Node-based workflows combine models, tools and reusable versioned definitions.

    Visual builder, roles and workflow lifecycle · documented · Source date not stated · Retrieved 2026-10-21

  83. Saving and publishing automations cohere-north:cohere-north:n-doc-29

    Automation definitions export JSON with graph/dependencies; credentials and schedules excluded.

    Versioning and JSON import/export · documented · Source date not stated · Retrieved 2026-10-21

  84. North execute automation API cohere-north:cohere-north:n-api-run

    External authenticated clients can start workflows with typed inputs; this is not a native source-event watcher.

    POST /v1/automations/{id}/execute · documented · Source date not stated · Retrieved 2026-10-21

  85. Human-in-the-loop automations cohere-north:cohere-north:n-doc-26

    Workflows can pause for review and route by human decisions; review timeouts apply.

    Human Review node · documented · Source date not stated · Retrieved 2026-10-21

  86. Introduction to Workflows langdock:langdock:workflows

    Workflows chain agents, integrations and logic with form, schedule and event triggers after admin activation.

    Introduction and activation · documented · Source date not stated · Retrieved 2026-10-21

  87. Human in the Loop langdock:langdock:hitl

    Workflow runs can pause for editor approval or per-action confirmation.

    Approval and action confirmation · documented · Source date not stated · Retrieved 2026-10-21

  88. Excel Add-in langdock:langdock:excel

    The Excel add-in reads and writes workbooks with default edit confirmation and named version prerequisites.

    Install, workbook operations and edit permissions · documented · Source date not stated · Retrieved 2026-10-21

  89. Outlook Add-in langdock:langdock:outlook-rev2

    The Outlook add-in requires workspace-admin access and Exchange Online; edits ask by default and sending requires an explicit requested and confirmed action.

    Installation and Exchange Online prerequisites; edit permissions; HTTP200 Markdown re-read2026-10-21 · documented · Source date not stated · Retrieved 2026-10-21

  90. Langdock for Outlook, by Langdock GmbH langdock:langdock:outlook-marketplace

    Vendor listing offers the add-in to every paid Langdock plan and trials, with draft review before sending.

    Overview and eligibility sentence · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  91. Outlook Add-in langdock:langdock:outlook-rev2-20261026

    The Outlook add-in requires workspace-admin access and Exchange Online; edits ask by default and sending requires an explicit requested and confirmed action.

    Installation and Exchange Online prerequisites; edit permissions; HTTP200 Markdown re-read2026-10-21 · documented · Source date not stated · Retrieved 2026-10-26

  92. Pricing Plans | Langdock langdock:langdock:pricing-20261026

    Business headline prices, annual discounts, workflow packages and Governance promotion are public.

    Chat & Agents, price breakdown, add-ons and API · vendor-claimed · Source date not stated · Retrieved 2026-10-26

  93. Product Changelog | Langdock langdock:langdock:changes-20261026

    Dated releases document model additions, desktop apps and per-agent confirmations.

    13 October 2026 model release; 15/10 September feature releases · documented · Source date not stated · Retrieved 2026-10-26

  94. Outlook Add-in setup langdock:langdock:outlook-admin-20261026

    Admins set Outlook add-in access to Nobody, Everyone or Specific members and groups; Outlook Email and Calendar integrations have separate access/scopes.

    Availability and access settings · documented · Source date not stated · Retrieved 2026-10-26

  95. Agent Configuration langdock:langdock:agents-20261026

    Agents combine instructions, files, folders, models, actions, skills and subagents, with optional source-access restrictions.

    Agent configuration, knowledge and source restriction · documented · Source date not stated · Retrieved 2026-10-26

  96. Deep Research langdock:langdock:research-20261026

    Deep Research creates cited public-web reports and has a 15-per-30-days cap for standard keys.

    Model configuration, limitations and usage · documented · Source date not stated · Retrieved 2026-10-26

  97. Human in the Loop langdock:langdock:hitl-20261026

    Workflow runs can pause for editor approval or per-action confirmation.

    Approval and action confirmation · documented · Source date not stated · Retrieved 2026-10-26

  98. Model Context Protocol (MCP) langdock:langdock:mcp-20261026

    MCP clients support Streamable HTTP/SSE and several authentication types; new tools do not require confirmation by default.

    Transports, authentication and tool confirmation · documented · Source date not stated · Retrieved 2026-10-26

  99. Excel Add-in langdock:langdock:excel-20261026

    The Excel add-in reads and writes workbooks with default edit confirmation and named version prerequisites.

    Install, workbook operations and edit permissions · documented · Source date not stated · Retrieved 2026-10-26

  100. About the North API cohere-north:cohere-north:n-north-api

    Instance REST API covers chat, agents, automations and files with bearer/OAuth/workload identity.

    Authentication and API scope · documented · Source date not stated · Retrieved 2026-10-21

  101. North create response API cohere-north:cohere-north:n-api-response

    North exposes model response API with tool and reasoning parameters and permission/rate-limit errors.

    Request/response and authentication · documented · Source date not stated · Retrieved 2026-10-21

  102. North file upload API cohere-north:cohere-north:n-api-upload

    Authenticated multipart upload stores a file with ID and downloadable content endpoints.

    POST /v1/files · documented · Source date not stated · Retrieved 2026-10-21

  103. North library API cohere-north:cohere-north:n-api-libraries

    Authenticated library creation complements file APIs and library permissions.

    Create library endpoint · documented · Source date not stated · Retrieved 2026-10-21

  104. Data controls cohere-north:cohere-north:n-doc-89

    Blocks new API/web share links; existing conversation links stop, existing automation/table links remain.

    Alpha sharing restrictions · documented · Source date not stated · Retrieved 2026-10-21

  105. Audits cohere-north:cohere-north:n-doc-140

    Admin changes/compliance decisions have searchable event rows and programmatic audit endpoints.

    Alpha admin events and GET API · documented · Source date not stated · Retrieved 2026-10-21

  106. Langdock Agent MCP Server langdock:langdock:mcp-server

    A public MCP endpoint exposes workspace agents under Agent API scope.

    Endpoint, authentication and tools · documented · Source date not stated · Retrieved 2026-10-21

  107. Voice settings cohere-north:cohere-north:n-doc-97

    Dictation and long-form mobile recording are separately off by default and require configured transcription service.

    Alpha dictation and beta mobile recording · documented · Source date not stated · Retrieved 2026-10-21

  108. Enterprise Guide for Langdock Desktop langdock:langdock:desktop-rev2

    Managed desktop rollout supports machine-wide Windows packages and signed/notarized macOS installers; these installation instructions do not change subscription entitlements.

    Windows machine-wide MSIX/Intune; macOS PKG/DMG/Jamf/Kandji; HTTP200 Markdown re-read2026-10-21 · documented · Source date not stated · Retrieved 2026-10-21

  109. Mobile App langdock:langdock:mobile-rev2

    HTTP200 Markdown introduction links official Apple App Store and Google Play mobile clients.

    Download routes · documented · Source date not stated · Retrieved 2026-10-21

  110. Langdock Desktop langdock:langdock:desktop-product

    Windows/macOS desktop clients use the same workspace and approved models as web.

    Downloads and Q&A · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  111. Langdock Mobile langdock:langdock:mobile-product

    Vendor mobile page offers iOS/Android clients using the workspace-approved models.

    App Store/Google Play links and Q&A · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  112. How to use the Teams Bot langdock:langdock:teams

    Teams has personal bot chats and channel threads with team participation.

    Private chats, channels and admin install · documented · Source date not stated · Retrieved 2026-10-21

  113. How to use the Teams Bot langdock:langdock:teams-20261026

    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.

    Installation note; Two Ways to Use the Teams Bot; Private Chat; Using Langdock in Channels; Limitations · documented · Source date not stated · Retrieved 2026-10-26

  114. Document mode cohere-north:cohere-north:n-doc-9

    Canvas supports manual/prompt edits, tone/translation actions, versions and DOCX/PDF/MD/HTML exports.

    Editing, quick actions and exports · documented · Source date not stated · Retrieved 2026-10-21

  115. Document Editor langdock:langdock:editor

    Document Editor replaces Canvas and exports Markdown, Word and PDF; imported Word/PDF cannot be edited directly there.

    Editor, AI edits, export and limitations · documented · Source date not stated · Retrieved 2026-10-21

  116. Image Generation langdock:langdock:images

    Chat invokes configured image-generation models with a user model selector.

    Generating images and model choice · documented · Source date not stated · Retrieved 2026-10-21

  117. North release notes cohere-north:cohere-north:n-north-changelog-20261026

    Dated releases document new models, beta/alpha capabilities and removal/deprecation of legacy connectors and APIs.

    October 20 v2.0.1 andOctober 16 v2.0.0; migrations; public representation of https://private.docs.cohere.com/north/changelog.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 be38218043c7eb99d836db5d02f86ce71b5af7c2c267327410f58f81936ed720 on 2026-10-26 · documented · Source date 2026-10-20 · Retrieved 2026-10-26

  118. Document mode cohere-north:cohere-north:n-doc-9-20261026

    Canvas supports manual/prompt edits, tone/translation actions, versions and DOCX/PDF/MD/HTML exports.

    Editing, quick actions and exports; public representation of https://private.docs.cohere.com/north/docs/get-started/north-document-mode.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 19535713d7c2ccff7e98fa4e94dde5dcdb6aae67809de5a1e27cb22d286812a1 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  119. Using Langdock for Data Analysis langdock:langdock:analysis

    Tabular analysis produces charts and downloadable spreadsheet and document formats.

    Analysis procedure and outputs · documented · Source date not stated · Retrieved 2026-10-21

  120. Projects langdock:langdock:projects

    Shared projects expose all project chats/files to members and can be shared with users/groups, not the whole workspace.

    Project sharing and permissions · documented · Source date not stated · Retrieved 2026-10-21

  121. About SSO cohere-north:cohere-north:n-doc-105

    OIDC preferred; SAML, LDAP shim/hybrid and authentication proxy documented; group claims required for group access.

    Protocols and Dex identity broker · documented · Source date not stated · Retrieved 2026-10-21

  122. https://docs.langdock.com/en/admin/security/saml/saml.md langdock:langdock:saml

    SAML 2.0 requires a verified domain; MFA comes from the IdP rather than standalone Langdock MFA.

    Checklist, supported IdPs, external authentication and MFA · documented · Source date not stated · Retrieved 2026-10-21

  123. Data deletion cohere-north:cohere-north:n-doc-153

    Deletion has asynchronous external cleanup and explicit preserved shared-resource exceptions.

    Conversation, user and connector cleanup · documented · Source date not stated · Retrieved 2026-10-21

  124. SCIM provisioning cohere-north:cohere-north:n-doc-112

    Bidirectional user/group sync; disable is reversible, delete re-creates a new identity if later added.

    Alpha SCIM2 and deactivation/deletion · documented · Source date not stated · Retrieved 2026-10-21

  125. Graceful delete settings cohere-north:cohere-north:n-doc-90

    Access ends immediately; configurable private cleanup grace period, shared resources preserved except nontransferable Microsoft libraries.

    Beta account removal and shared-resource exceptions · documented · Source date not stated · Retrieved 2026-10-21

  126. https://docs.langdock.com/en/admin/security/scim/scim.md langdock:langdock:scim

    SCIM 2.0 supports Entra provisioning after SAML setup and domain verification.

    Overview and prerequisites · documented · Source date not stated · Retrieved 2026-10-21

  127. https://docs.langdock.com/en/admin/security/scim/entra.md langdock:langdock:scim-entra

    Entra target actions control provisioning/deactivation and group synchronization.

    Target Object Actions and optional group synchronization · documented · Source date not stated · Retrieved 2026-10-21

  128. Unassign Agents langdock:langdock:leaver

    Agents whose owner is deactivated keep functioning but cannot be edited until reassigned.

    Unassigned agents and reassignment · documented · Source date not stated · Retrieved 2026-10-21

  129. Models and providers cohere-north:cohere-north:n-doc-134

    Custom endpoints/providers, group access and defaults; grants additive and alias may silently fall back to provider default.

    Beta UI, alpha RBAC, aliases and fallback · documented · Source date not stated · Retrieved 2026-10-21

  130. Compute requirements cohere-north:cohere-north:n-doc-158

    North licensed by compute units and separately administered application instances; licence rates absent.

    Sizing and licensing metrics · documented · Source date not stated · Retrieved 2026-10-21

  131. Analytics v2 cohere-north:cohere-north:n-doc-78

    Self-hosted analytics reports users/groups/models/agents/tools; named-user CSV and sampled metrics have limits.

    Alpha metrics and CSV/PNG exports · documented · Source date not stated · Retrieved 2026-10-21

  132. Analytics settings cohere-north:cohere-north:n-doc-95

    Operators can turn event collection off and configure retention for database analytics events.

    Alpha event collection and retention · documented · Source date not stated · Retrieved 2026-10-21

  133. Usage Exports langdock:langdock:exports

    Usage CSV exports span users, agents, keys, projects, models and workflows, with user-detail privacy controls.

    Export data types, limits and user-level data · documented · Source date not stated · Retrieved 2026-10-21

  134. Flow control cohere-north:cohere-north:n-doc-137

    User/group/model/source/provider rules enforce request/input/output token limits only after Helm services deployed; fail-open option and unlimited default.

    Alpha model rate-limit proxy · documented · Source date not stated · Retrieved 2026-10-21

  135. Token usage monitoring cohere-north:cohere-north:n-doc-207

    Operators collect billed/raw tokens by model/provider/operation; no per-user labels, scrape gaps and incomplete paths prevent billing-ledger equivalence.

    Prometheus/Grafana collection and limits · documented · Source date not stated · Retrieved 2026-10-21

  136. Usage and spend limits langdock:langdock:byok-limits

    BYOK cost limits depend on configured prices and exclude backbone, workflows and workspace API usage.

    Scope, unpriced models and spend limits · documented · Source date not stated · Retrieved 2026-10-21

  137. Workflow limits langdock:langdock:workflow-limits

    Workflow AI use has a separate workspace EUR limit and per-workflow USD limits that block new runs.

    Spend limits and execution step cap · documented · Source date not stated · Retrieved 2026-10-21

  138. Audits cohere-north:cohere-north:n-doc-140-20261026

    Admin changes/compliance decisions have searchable event rows and programmatic audit endpoints.

    Alpha admin events and GET API; public representation of https://private.docs.cohere.com/north/docs/admin/audits.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 4694734d3c4deaa7540b7df9604377266d387b5b92dea6b958aebbfdd74d20fc on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  139. Compliance cohere-north:cohere-north:n-doc-139-20261026

    Approved investigators get24-hour conversation access/CSV including blocked/redacted content; self-approval forbidden.

    Alpha dual-control investigation and CSV; public representation of https://private.docs.cohere.com/north/docs/admin/compliance.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 8d8d2439993a46e02f92eaf3dc040bacc2a9b59f3ad61352c04278648157c37c on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  140. Audit Logs API Overview langdock:langdock:audit

    Audit events retain 90 days and are retrievable by a dedicated-scope admin API for SIEM ingestion.

    Event schema, retention and prerequisites · documented · Source date not stated · Retrieved 2026-10-21

  141. Export tool parameters and outputs langdock:langdock:compliance-rev2

    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.

    Before You Start, parameters and conversation endpoints; HTTP200 Markdown re-read2026-10-21 · documented · Source date not stated · Retrieved 2026-10-21

  142. Export tool parameters and outputs langdock:langdock:compliance-rev2-20261026

    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.

    Before You Start, parameters and conversation endpoints; HTTP200 Markdown re-read2026-10-21 · documented · Source date not stated · Retrieved 2026-10-26

  143. Audit Logs API Overview langdock:langdock:audit-20261026

    Audit events retain 90 days and are retrievable by a dedicated-scope admin API for SIEM ingestion.

    Event schema, retention and prerequisites · documented · Source date not stated · Retrieved 2026-10-26

  144. Workspace Settings langdock:langdock:workspace-20261026

    Workspace settings define retention, model defaults, EU-only default enablement, analytics and product controls.

    Product Settings, Models, Analytics and Customizations · documented · Source date not stated · Retrieved 2026-10-26

  145. Guardrails admin cohere-north:cohere-north:n-doc-138

    HiddenLayer supports allow/block/redact with monitor-only default; timeouts/unsupported entities and advisory content safety can fail open.

    Selected-customer beta PII and alpha content safety · documented · Source date not stated · Retrieved 2026-10-21

  146. Guardrails deployment cohere-north:cohere-north:n-doc-193

    GPU scanning engine runs inside customer cluster without external HiddenLayer cloud traffic in documented configuration.

    Selected-customer beta in-cluster HiddenLayer · documented · Source date not stated · Retrieved 2026-10-21

  147. Terms and conditions cohere-north:cohere-north:n-doc-145

    Sign-up/tool-specific multilingual terms require acceptance again after new versions; external URL overrides hosted terms.

    Alpha required policy acceptance · documented · Source date not stated · Retrieved 2026-10-21

  148. Compliance Rules langdock:langdock:gov

    Custom agent compliance checks produce pass/fail and severity results with per-rule analytics.

    Rule operation, failures and analytics · documented · Source date not stated · Retrieved 2026-10-21

  149. North security cohere-north:cohere-north:n-doc-146

    Recommends operator encryption/network/SSO controls and stdout-to-SIEM forwarding; no observed hardened configuration implied.

    Customer deployment hardening and log forwarding · documented · Source date not stated · Retrieved 2026-10-21

  150. Cohere private deployments cohere-north:cohere-north:n-private

    Vendor offers customer-managed VPC and air-gapped on-prem delivery with deployment assistance.

    VPC/on-prem/air-gap and rollout support · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  151. Model Vault with North cohere-north:cohere-north:n-doc-217

    North stays customer-hosted; Cohere processes model inputs in dedicated Vault; ZDR option removes prompt retention.

    Customer app plus Cohere inference · documented · Source date not stated · Retrieved 2026-10-21

  152. Backup and restore cohere-north:cohere-north:n-doc-214

    Operator controls backup placement and retention; encryption master key needed for restore.

    Database, secrets and object storage · documented · Source date not stated · Retrieved 2026-10-21

  153. Distributed tracing cohere-north:cohere-north:n-doc-208

    Optional tracing sends deployment telemetry to operator-selected collectors; geographic placement is not fixed.

    Operator OpenTelemetry export · documented · Source date not stated · Retrieved 2026-10-21

  154. Enterprise data commitments cohere-north:cohere-north:n-commitments

    Private deployments do not send prompts to Cohere; SaaS Platform has opt-out training and30-day logs with exceptions; Model Vault integration has its own inference scope.

    Private/third-party versus SaaS Platform; retention and ZDR FAQ · documented · Source date 2025-12-05 · Retrieved 2026-10-21

  155. security langdock:langdock:security

    Default Azure EU SaaS, managed dedicated from 2000 and customer-cloud/on-premise from 5000 seats are advertised.

    Deployment, security, BYOK and certifications · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  156. Data Processing Agreement | Langdock langdock:langdock:dpa

    DPA 2.1 defines third-country instructions, subprocessor notice and deletion/export rules, with an embedded provider table.

    Sections 7-12 and Appendices 1/2 · documented · Source date not stated · Retrieved 2026-10-21

  157. Model Vault overview cohere-north:cohere-north:n-vault

    Cohere-managed dedicated inference is separate from the North control plane.

    Dedicated inference deployment and choices · documented · Source date not stated · Retrieved 2026-10-21

  158. Deployment model cohere-north:cohere-north:n-doc-165

    North application Helm chart deployed on customer Kubernetes; GitOps/ArgoCD recommended for production.

    Helm and production GitOps · documented · Source date not stated · Retrieved 2026-10-21

  159. Networking requirements cohere-north:cohere-north:n-doc-159

    Operator network/DNS/TLS controls; hosted model API optional, image supply needs mirroring for disconnected installations.

    Optional external model API and registry access · documented · Source date not stated · Retrieved 2026-10-21

  160. Compliance cohere-north:cohere-north:n-doc-139

    Approved investigators get24-hour conversation access/CSV including blocked/redacted content; self-approval forbidden.

    Alpha dual-control investigation and CSV · documented · Source date not stated · Retrieved 2026-10-21

  161. Terms of Use | Langdock langdock:langdock:terms-rev2

    Microsoft Azure routes use Modified Abuse Monitoring, disabling provider prompt/output retention and human abuse review. Other provider/model routes require separate assessment.

    Section9 and Appendix1 Microsoft Azure service terms · documented · Source date not stated · Retrieved 2026-10-21

  162. Data retention settings cohere-north:cohere-north:n-doc-88

    Age-based retention off by default; enabled defaults90day soft-delete plus30-day timeout; hourly hard-delete still runs for manually deleted conversations.

    Alpha conversation retention and jobs · documented · Source date not stated · Retrieved 2026-10-21

  163. How long are files saved in Langdock? langdock:langdock:retention

    Deleted chats are immediately unavailable and unreferenced files are cleaned overnight; shared file references survive.

    Retention by object type · documented · Source date not stated · Retrieved 2026-10-21

  164. Cohere and Aleph Alpha combination agreement cohere-north:cohere-north:n-combination-20261026

    Combination remains subject to regulatory approvals; future dual headquarters and leadership depend on closing.

    September 16 definitive agreement and closing conditions; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 972ee8d4e3dd868bf9d5986f00e66c0543ffd55cf519b78909aa7ec0cad9c399 on 2026-10-26 · documented · Source date 2026-09-16 · Retrieved 2026-10-26

  165. Cohere AISLE proposed acquisition announcement cohere-north:cohere-north:corporate-aisle-20261026

    The current text calls AISLE a proposed acquisition and calls Aleph Alpha a partnership. It does not provide closing/approval evidence for the September business-combination agreement.

    October 15 announcement, opening paragraphs and closing transaction conditions; HTTP 200, body SHA256 e17b07229ecb36abb9f98b4d36e6541d3c74db64f0758fa93b8b48df3c7ccf58 · vendor-claimed · Source date 2026-10-15 · Retrieved 2026-10-26

  166. Cohere public terms of use cohere-north:cohere-north:n-terms-20261026

    Public general terms identify Cohere Inc and Ontario/Toronto law; North commercial subscription terms were not retrieved.

    2022 terms; scope and choice of law; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 09c6e9b556c82d0e47438f044477298abb536b98fb30622371806a82ea1f3cbd on 2026-10-26 · documented · Source date 2022-09-07 · Retrieved 2026-10-26

  167. Cohere Trust Center cohere-north:cohere-north:n-trust-20261026

    Lists request-gated SOC 2/ISO 27001/42001 reports, USA subprocessors, NDA-gated DPA and SaaS US-Central hosting; not a whole-North private deployment policy.

    Reports, subprocessors and regulatory FAQs; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 be106d8cf80369b1d1adf72c7912bf7c8af1221b76a8a381c6a95455d2666401 on 2026-10-26 · vendor-claimed · Source date not stated · Retrieved 2026-10-26

  168. Cohere Trust Center cohere-north:cohere-north:n-trust

    Lists request-gated SOC 2/ISO 27001/42001 reports, USA subprocessors, NDA-gated DPA and SaaS US-Central hosting; not a whole-North private deployment policy.

    Reports, subprocessors and regulatory FAQs · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  169. Cohere public terms of use cohere-north:cohere-north:n-terms

    Public general terms identify Cohere Inc and Ontario/Toronto law; North commercial subscription terms were not retrieved.

    2022 terms; scope and choice of law · documented · Source date 2022-09-07 · Retrieved 2026-10-21

  170. https://docs.langdock.com/en/admin/compliance-and-governance/legal-compliance.md langdock:langdock:legal

    DPA applies automatically and a Professional Secrecy Addendum and certificates are linked from the Trust Center.

    Legal and compliance links · documented · Source date not stated · Retrieved 2026-10-21

  171. Data encryption at rest cohere-north:cohere-north:n-doc-154

    Customer-held Kubernetes master key encrypts chat columns; automation/workflow data excluded.

    Optional AES256GCM chat-column envelope encryption · documented · Source date not stated · Retrieved 2026-10-21

  172. IP Restrictions langdock:langdock:ip

    CIDR allowlists immediately block unauthorized network access when enabled.

    Prerequisites and enforcement · documented · Source date not stated · Retrieved 2026-10-21

  173. Cohere pricing cohere-north:cohere-north:n-pricing

    North pricing is custom; model API trials and Model Vault instance rates are separate products.

    North custom pricing; separate Model Vault/API tables · documented · Source date not stated · Retrieved 2026-10-21

  174. Pricing Plans | Langdock langdock:langdock:pricing-rev2

    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.

    Business/Enterprise cards; price breakdown; product add-ons · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  175. ECB historical FX cohere-north:cohere-north:fx-ecb

    EUR1=USD1.1215=CHF0.9237; rates recorded without inventing an unpriced North total.

    2026-10-20 USD/CHF rates · documented · Source date 2026-10-20 · Retrieved 2026-10-21

  176. ECB historical euro reference rates, 20 October 2026 langdock:langdock:ecb-fx

    ECB2026-10-20 reference rates:EUR1=USD1.1215=CHF0.9237, implying USD1=EUR0.89166206.

    Cube time=2026-10-20, USD and CHF currency entries · documented · Source date 2026-10-20 · Retrieved 2026-10-21

  177. North 2 product page cohere-north:cohere-north:n-home

    North offers agents, automations, libraries, applications and private deployment.

    Platform and private deployment overview · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  178. White labeling cohere-north:cohere-north:n-doc-142

    Operators configure branding; commercial branding licence terms not established.

    Branding configuration · documented · Source date not stated · Retrieved 2026-10-21

  179. Agent Migration Guide langdock:langdock:migration

    Agent API export/import preserves selected configuration; files/skills and some fields require separate migration.

    Prerequisites, exported settings and field mapping · documented · Source date not stated · Retrieved 2026-10-21

  180. Data Processing Agreement | Langdock langdock:langdock:dpa-20261026

    DPA 2.1 defines third-country instructions, subprocessor notice and deletion/export rules, with an embedded provider table.

    Sections 7-12 and Appendices 1/2 · documented · Source date not stated · Retrieved 2026-10-26

  181. Agent Migration Guide langdock:langdock:migration-20261026

    Agent API export/import preserves selected configuration; files/skills and some fields require separate migration.

    Prerequisites, exported settings and field mapping · documented · Source date not stated · Retrieved 2026-10-26

  182. Knowledge bases langdock:langdock:knowledge-20261026

    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.

    Create a Knowledge base and add documents, API upload; Share search access; Convert a Knowledge base to a folder · documented · Source date not stated · Retrieved 2026-10-26

  183. Usage Exports langdock:langdock:exports-20261026

    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.

    Accessing Usage Exports; Export Limits; Export Data Structure; Usage Exports; Data Retention · documented · Source date not stated · Retrieved 2026-10-26

  184. Cohere and Aleph Alpha combination agreement cohere-north:cohere-north:n-combination

    Combination remains subject to regulatory approvals; future dual headquarters and leadership depend on closing.

    September 16 definitive agreement and closing conditions · documented · Source date 2026-09-16 · Retrieved 2026-10-21

  185. Cohere status cohere-north:cohere-north:n-status

    Public hosted service status is available; it does not establish customer-hosted North SLA.

    Hosted API service status · documented · Source date not stated · Retrieved 2026-10-21

  186. Rollout Playbook langdock:langdock:playbook

    Dedicated rollout support/workshops start at 250 licences and include a champion approach.

    Programme qualification and rollout phases · documented · Source date not stated · Retrieved 2026-10-21

  187. status langdock:langdock:status

    The public status page covers the app, APIs, Workflows and Integrations with history.

    Components and history · documented · Source date not stated · Retrieved 2026-10-21

  188. Terms of Use | Langdock langdock:langdock:terms-20261026

    Terms 2.1 prohibit training and describe provider-specific residency and retention agreements, proprietary use rights and contract defaults.

    Sections 6/7/9/12/15/16/19 and Appendix 1 · documented · Source date not stated · Retrieved 2026-10-26

  189. Langdock imprint and contact point langdock:langdock:imprint-20261026

    Users and authorities can contact support@langdock.com in German and English; the imprint identifies Langdock GmbH in Berlin.

    Contact Point for Users and Authorities · documented · Source date not stated · Retrieved 2026-10-26

  190. status langdock:langdock:status-20261026

    The public status page covers the app, APIs, Workflows and Integrations with history.

    Components and history · documented · Source date not stated · Retrieved 2026-10-26

  191. North user guide cohere-north:cohere-north:n-guide

    Lists planned November 13 v2.1 andDecember 11 v2.2 releases, subject to change; not individual feature delivery promises.

    Release calendar and feature-state definitions · documented · Source date not stated · Retrieved 2026-10-21

  192. Langdock Workshops langdock:langdock:training

    Official workshop recordings/slides cover chat, skills, integrations, agents and workflows.

    Workshop catalogue · documented · Source date not stated · Retrieved 2026-10-21

  193. Data Interpreter cohere-north:cohere-north:n-doc-36

    Legacy spreadsheet Python tool is deprecated in favor of code sandbox; whole-sheet analysis differs from indexed metadata search.

    Deprecated tool and successor · documented · Source date not stated · Retrieved 2026-10-21