Skip to content

Agent-readable comparison

Cohere North vs Dust

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

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

Dust

Agent cross-checked Support: partial

Dust offers per-message model choice and ordered auto-model lists, with access-tier and region controls.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit plan (Free/Pro/Max); Enterprise model access inherits the published catalogue; model-tier and EU eligibility separately constrained; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • The catalogue finding is restricted to named documentation entries; conflicting Gemini4 Argon EU eligibility is an explicit gap.
  • providers Which model providers are available? [supported]: Docs list OpenAI, Anthropic, Google, Mistral and Fireworks-served models; exact enabled models depend on workspace and tier. Sources: dust:dust:models, dust:dust:eu-models.
  • current_models Which current models are selectable on this plan? [partial]: The model-selection document lists GPT6.1 Sol, Claude Opus5.5/Sonnet5.5, Gemini3.8 Flash and Mistral models. Gemini4 Argon is excluded from this current-EU availability finding: its release note conflicts with the EU table, and the documented authoritative picker flag was not observed. No complete current tenant catalogue is claimed. Sources: dust:dust:models, dust:dust:changelog, dust:dust:eu-models, dust:dust:pricing.
  • user_choice Can users pick the model per chat? [supported]: The composer chooses a model for the next message; Agent Builder sets a persistent agent default. Sources: dust:dust:models.
  • auto_routing Does the product route between models automatically, and is the chosen model shown? [supported]: Basic/Standard/Premium use ordered candidate lists and availability fallback, not prompt-dependent task routing. A replacement indicator names the fallback during a detected outage. Sources: dust:dust:models.
  • multimodal_input Which models accept images, audio or files? [partial]: Conversation files support images, documents and audio transcripts; the exact input capability for every current model is not fully tabulated. Sources: dust:dust:files.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:models, dust:dust:eu-models, dust:dust:changelog, dust:dust:pricing, dust:dust:files.

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.

Dust

Agent cross-checked Support: partial

The public changelog and exact agent model selection are documented; release-lag and removal notice remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • 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? The dated changelog and model-selection docs were checked; last-three-release/provider lag measurements and a fixed advance deprecation-notice period were not established.
  • changelog Is there a dated public model changelog? [supported]: The public changelog contains dated model releases including Gemini 4 Argon on October 14, 2026. Sources: dust:dust:changelog.
  • deprecation_notice How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? The dated changelog and model-selection docs were checked; last-three-release/provider lag measurements and a fixed advance deprecation-notice period were not established.
  • version_pinning Can an admin keep an older model version? [partial]: An agent can select a specific model and keeps it until changed, subject to continued provider/workspace availability. No indefinite old-version entitlement is established. Sources: dust:dust:models.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:changelog, dust:dust:models.

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.

Dust

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.

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.

Dust

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.

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.

Dust

Agent cross-checked Support: partial

Admins cap models by workspace, group and member, with explicit published-agent exceptions and credit limits.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • No two-user enforcement test. Published agents can run above member tiers if the separate admin setting permits it.
  • model_allowlist_by_group Can admins limit models per group? [supported]: Model access ceilings apply to the workspace, groups or individuals and cover reasoning efforts as well as auto selections. Sources: dust:dust:tiers.
  • data_bound_models Can admins restrict which models receive connector or knowledge content? [partial]: EU-only mode restricts all active agents and pickers to EU-hosted models. Spaces bound knowledge and agent access; arbitrary per-data-class model rules were not established. Sources: dust:dust:eu-models, dust:dust:spaces.
  • default_model Can admins set the default model? [supported]: Builders configure an agent default, which may be exact or Basic/Standard/Premium. Composer changes do not edit it for others. Sources: dust:dust:models.
  • user_limits What per-user message or token limits apply, and are they published? [supported]: Free seats have 500 lifetime credits, Pro 8,000/month and Max 40,000/month, plus applicable shared-pool rules and member spend limits. Sources: dust:dust:credits, dust:dust:credit-management.
  • limit_behaviour What happens when a limit is reached? [supported]: Members block when applicable sources/caps are exhausted. A message begun under a cap can finish above it; new messages then block. A separate root-task checkpoint can pause at 600 AWU. Sources: dust:dust:credit-management, dust:dust:credits.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:tiers, dust:dust:eu-models, dust:dust:spaces, dust:dust:models, dust:dust:credits, dust:dust:credit-management.

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.

Dust

Agent cross-checked Support: partial

Conversation files and code/OCR handling are documented; conflicting effective upload caps are explicitly unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • No common PDF/scan/Excel/PowerPoint fixture run.
  • Do not use either disputed cap set as the effective Business upload limit.
  • formats Which formats are accepted? [supported]: Conversation uploads accept documents/PDF, text/code, Excel/CSV/TSV, images and supported audio. Direct video uploads are explicitly excluded by the limits FAQ. Sources: dust:dust:files, dust:dust:file-limits.
  • limits What size and count limits apply per file and chat? [unknown]: Effective image/audio/tabular maximums and file counts are unknown: Conversation Files lists5/25/50MB while File size limits lists20/100/350MB. Both mention50MB general data files, but neither resolves the actual current per-plan upload route. No logged-in upload test was performed.
  • ocr Are scanned PDFs read? [partial]: Computer documents OCR for English, French and mixed scans with page-level caveats. Drive connector itself ignores image-only files; upload to a conversation is the documented route. Sources: dust:dust:computer, dust:dust:drive.
  • spreadsheets Are Excel tables read with structure intact? [partial]: Computer can read, calculate and edit uploaded Excel with code. Formula/style preservation must be checked; no fixture fidelity result is available. Sources: dust:dust:computer.
  • full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [partial]: Conversation uploads are not indexed in workspace sources. Computer can inspect full files, while knowledge search retrieves relevant context; complete chunk visibility was not verified. Sources: dust:dust:files, dust:dust:computer, dust:dust:search.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:files, dust:dust:file-limits, dust:dust:computer, dust:dust:drive, dust:dust:search.

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.

Dust

Agent cross-checked Support: partial

Spaces persist shared knowledge and bind it to agent tools.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • persistent_collections Can users keep document collections across chats? [supported]: Open and restricted Spaces retain connected sources, folders and other data across conversations. Sources: dust:dust:spaces.
  • sharing_scope Can collections be shared with users, groups or the whole organisation? [supported]: Open Spaces are workspace-wide; restricted Spaces have explicit members or provisioned groups. Sources: dust:dust:spaces.
  • size_limits What are the collection limits? [partial]: Business supports five Spaces and Enterprise 100. Complete per-Space storage/document quotas were not established. Sources: dust:dust:spaces.
  • assistant_binding Can collections be bound to an assistant? [supported]: An agent tool can use selected Space data; Space membership governs agent visibility and use. Sources: dust:dust:spaces.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:spaces.

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.

Dust

Agent cross-checked Support: partial

Managed content connectors coexist with MCP tools and beta imports; Microsoft content indexing is account-scoped.

Availability: generally-available · Delivery: official-integration
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business: up to3 connections and5 remote MCP servers; Enterprise: unlimited connection/MCP packaging; beta imports identified separately; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • Managed sources, metadata/table-query connections, MCP tools and beta imports are separate routes; no all-systems managed-index promise.
  • microsoft_365 Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: The Microsoft connection syncs selected SharePoint drives/documents within the connecting account permissions. Teams-associated SharePoint content is described; this does not establish Outlook mail or all Teams messages as indexed sources. Sources: dust:dust:microsoft.
  • google_workspace Which Google sources are connected? [partial]: Drive documents, Sheets, Slides and text PDFs can sync. Gmail is separately available as an MCP tool in the credits/tool catalog, not established as the same managed content index. Sources: dust:dust:drive, dust:dust:credits.
  • atlassian Confluence and Jira? [partial]: Confluence indexes selected global spaces, excluding restricted pages. Jira has a beta custom import and MCP tool route; do not count the beta import as a general managed connector. Sources: dust:dust:confluence, dust:dust:jira, dust:dust:credits.
  • other_systems Which other business systems? [partial]: Documented routes include managed Slack/Notion/GitHub and Salesforce/Zendesk/Snowflake sources/tools. BigQuery specifically uses a dedicated-service-account table-query connection: Dust keeps metadata, not a synchronized table-content index; queries stay within the chosen BigQuery dataset location and Space admins select tables. General Business/Enterprise connection limits apply; a BigQuery-specific commercial add-on is not separately specified. Sources: dust:dust:sources, dust:dust:credits, dust:dust:r2-bigquery, dust:dust:pricing.
  • on_prem_sources Can on-prem file shares or databases be connected? [partial]: Admins can connect a customer-hosted MCP server at a reachable secured URL. This is tool access, not evidence of a native SMB/file-share connector or on-premises Dust deployment. Sources: dust:dust:tools.
  • connector_provider Who builds and maintains each connector? [supported]: Dust manages built-in connections; external MCP servers can be vendor/community/customer hosted and authenticated separately. Sources: dust:dust:permissions, dust:dust:tools.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:microsoft, dust:dust:drive, dust:dust:credits, dust:dust:confluence, dust:dust:jira, dust:dust:sources, dust:dust:r2-bigquery, dust:dust:pricing, dust:dust:tools, dust:dust:permissions.

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.

Dust

Agent cross-checked Support: partial

Knowledge access is documented through connection-account scope and Dust Spaces; per-user source-ACL mirroring is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Connector access through one account is not counted as demonstrated per-user source permission preservation.
  • source_permissions_respected Are source permissions enforced per user? [partial]: Drive and Microsoft content available to Dust follows the connecting account and admin-selected data. Users then access agent knowledge through Space membership. Individual source ACL inheritance for each querying user was not established. Sources: dust:dust:drive, dust:dust:microsoft, dust:dust:permissions.
  • enforcement_point Does the source system, a mirrored index or nothing enforce them? [supported]: Managed content is synchronized under the connection identity and gated through open/restricted Spaces; personal tool credentials are a separate per-user route. Sources: dust:dust:permissions, dust:dust:credentials.
  • revocation_delay How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? No two-user restricted-document or revocation fixture was run. Checked connector/Space docs did not establish per-query source ACL mirrors, a source-permission revocation SLA, or Microsoft Purview-label enforcement.
  • admin_scope_controls Can admins exclude sites, folders or labels? [supported]: Admins choose connector folders/documents/sites and control restricted Space membership. Sources: dust:dust:spaces, dust:dust:microsoft.
  • sensitivity_labels Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? No two-user restricted-document or revocation fixture was run. Checked connector/Space docs did not establish per-query source ACL mirrors, a source-permission revocation SLA, or Microsoft Purview-label enforcement.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:drive, dust:dust:microsoft, dust:dust:permissions, dust:dust:credentials, dust:dust:spaces.

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.

Dust

Agent cross-checked Support: partial

Managed connectors copy and synchronize content, with source-specific refresh and deletion timing.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • live_or_indexed Is content searched live or copied into an index? [supported]: Connections synchronize content into Dust; conversation uploads remain scoped to the chat. MCP tools can access live services separately. Sources: dust:dust:permissions, dust:dust:files, dust:dust:tools.
  • sync_interval How often does an index refresh? [supported]: Microsoft describes five-minute sync cycles; Drive says a few minutes; Confluence describes event updates plus an approximate hourly check. Sources: dust:dust:microsoft, dust:dust:drive, dust:dust:confluence.
  • deletion_propagation How quickly does a deleted document disappear? [partial]: Microsoft changes/deletions appear on a subsequent sync and large batches can take longer. Drive deletions occur during its sync. No measured end-to-end bound was tested. Sources: dust:dust:microsoft, dust:dust:drive.
  • index_location Where is indexed content stored? [partial]: Dust markets EU or US hosting; exact per-index country, cloud provider and backup location were not established. Sources: dust:dust:security.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:permissions, dust:dust:files, dust:dust:tools, dust:dust:microsoft, dust:dust:drive, dust:dust:confluence, dust:dust:security.

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.

Dust

Agent cross-checked Support: partial

Knowledge and research tools cite sources; observed retrieval quality remains unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • citations Are answers linked to specific sources? [supported]: Deep-dive documents citations to documents, web pages and data queries. Sources: dust:dust:deep.
  • citation_accuracy Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test.
  • cross_language Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test.
  • no_answer_behaviour Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test.
  • observed_accuracy How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep.

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.

Dust

Agent cross-checked Support: partial

Agent-specific private memory persists across chats and can be viewed or deleted.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • custom_instructions Can users set persistent instructions? [partial]: Agent instructions persist in the agent configuration and saved memory can contain user preferences; a separate personal global-instructions setting was not established. Sources: dust:dust:builder, dust:dust:memory.
  • cross_chat_memory Does the product remember facts across chats? [supported]: The Memory tool retains user-specific information across conversations per agent. Sources: dust:dust:memory.
  • user_memory_controls Can users view, edit and delete memories? [partial]: Users can view and delete agent memories, which persist until deletion. Direct editing or a global personal off switch was not established. Sources: dust:dust:memory.
  • admin_memory_controls Can admins turn memory off? [unknown]: Can admins turn memory off? The Agent Memory and governance guides were checked; an admin-wide switch to disable all memory was not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:memory.

Assistants and agents

AGT-01 Custom assistants

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

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.

Dust

Agent cross-checked Support: partial

Custom agents have instructions, models, knowledge and tools with group-governed creation and sharing.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • create_assistants Can users create assistants with instructions, knowledge and tools? [supported]: Agent Builder configures instructions, models, knowledge and tools. Sources: dust:dust:builder.
  • creator_permissions Can admins limit who creates them? [supported]: Create/publish agent and skill permissions can be Everyone, Groups or Admin only. Sources: dust:dust:governance.
  • sharing_scope Can assistants be shared with users, groups or everyone? [supported]: Agents and their knowledge access are controlled by sharing and Space memberships; group governance regulates publishing. Sources: dust:dust:builder, dust:dust:spaces, dust:dust:governance.
  • catalogue Is there an internal assistant directory? [partial]: Published/shared agents and default agents are discoverable in the workspace; exact catalog configuration was not observed. Sources: dust:dust:builder, dust:dust:models.
  • prompt_library Are shared prompt templates available? [partial]: Reusable agents and skills package instructions, knowledge and tools. A separate legacy prompt-library feature is not assumed. Sources: dust:dust:governance, dust:dust:builder.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:governance, dust:dust:spaces, dust:dust:models.

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.

Dust

Agent cross-checked Support: partial

Dust supports built-in tools, customer MCP servers and personal or shared credentials.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • No external-tool call or access-boundary fixture was run.
  • builtin_tools Which tools are built in? [supported]: Documented tools include knowledge search, table queries, web search, Computer, images, speech and agent orchestration. Sources: dust:dust:credits, dust:dust:computer.
  • custom_actions Can admins add API actions? [supported]: Admins can connect customer-written MCP tools over secured publicly reachable URLs. Sources: dust:dust:tools.
  • mcp_client Can it use remote MCP servers, and with what admin control? [supported]: Admins add remote MCP servers with automatic/static OAuth or bearer-token authentication and can restrict tools to skills. Sources: dust:dust:tools.
  • tool_auth Do tools act as the user or as a shared account? [supported]: Shared credentials act as one service account; personal credentials use each user OAuth after initial admin setup. Sources: dust:dust:credentials.
  • tool_approval Can admins approve or block tools, and can users confirm actions before they run? [partial]: Computer network domains can require user approval; dated connector releases describe approval for writes. A universal confirmation rule for every tool and unattended trigger was not established. Sources: dust:dust:computer, dust:dust:changelog.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:credits, dust:dust:computer, dust:dust:tools, dust:dust:credentials, dust:dust:changelog.

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.

Dust

Agent cross-checked Support: partial

Agents can search the web and run multi-step Deep-dive research.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • web_search Is web search available? [supported]: Web Search & Browse runs Google queries and reads result pages. Sources: dust:dust:web.
  • admin_toggle Can admins disable it per organisation or group? [partial]: Web tools are selected in agent configuration; default Deep-dive can be disabled by admins. A universal per-group web-off rule was not established. Sources: dust:dust:web, dust:dust:deep.
  • search_provider Which search provider handles queries, and where? [partial]: The guide calls the search a Google query. The intermediary provider and countries handling queries/crawling were not established. Sources: dust:dust:web.
  • deep_research Is multi-step research with a report available? [supported]: Deep-dive plans, spawns parallel specialists and produces a research report. It searches Company Data and cannot use Table Query. Sources: dust:dust:deep.
  • web_citations Are web sources cited? [supported]: Deep-dive promises citations to web and company sources. Sources: dust:dust:deep.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:web, dust:dust:deep.

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.

Dust

Agent cross-checked Support: partial

Agents support schedules and webhook automation with admin-created event sources.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • workflow_builder Is there a workflow or chain builder? [partial]: Agents orchestrate tools and sub-agents; external n8n and trigger workflows are documented. A separate visual multi-step chain canvas was not established. Sources: dust:dust:deep, dust:dust:triggers, dust:dust:changelog.
  • scheduled_tasks Can prompts or assistants run on a schedule? [supported]: Agents can run on recurring schedules. Sources: dust:dust:schedules.
  • event_triggers Can external events start a workflow? [supported]: Built-in webhook sources include GitHub, Jira, Linear, Zendesk and Fathom; signed custom webhooks are supported. Sources: dust:dust:webhooks.
  • builder_audience Is building aimed at business users, IT or developers? [supported]: Admins connect event sources; builders/members attach filtered triggers in Agent Builder and can use natural-language trigger creation through Dust Default. Sources: dust:dust:webhooks, dust:dust:changelog.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep, dust:dust:triggers, dust:dust:changelog, dust:dust:schedules, dust:dust:webhooks.

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.

Dust

Agent cross-checked Support: partial

Multi-step agent work and visible Deep-dive progress are documented; safety controls depend on tool and trigger.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • No shared gather/documents/email fixture or side-effect audit was run.
  • agent_mode Is there an agent mode for multi-step tasks? [supported]: Deep-dive plans, delegates and synthesizes, and Computer can execute deterministic file/code work. Sources: dust:dust:deep, dust:dust:computer.
  • visible_steps Are steps and tool calls shown? [supported]: Deep-dive documentation shows reasoning and sub-agent progress in real time. Sources: dust:dust:deep.
  • side_effect_confirmation Must the user confirm actions with side effects? [partial]: Computer domains may require user approval and selected connector write actions ask for approval. Pods agents can also act without a human, so universal write confirmation is not claimed. Sources: dust:dust:computer, dust:dust:changelog, dust:dust:pods.
  • stop_control Can the user stop a running task? [partial]: The 600-AWU root-task checkpoint offers Stop or Continue. A complete general stop/rollback behavior was not tested. Sources: dust:dust:credits.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep, dust:dust:computer, dust:dust:changelog, dust:dust:pods, dust:dust:credits.

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.

Dust

Agent cross-checked Support: supported

Dust offers conversation/knowledge APIs, enforceable API-key caps and OAuth MCP access.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust APIs and MCP server; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business conversation API; Enterprise adds Data Source API per pricing; MCP subject to workspace enablement; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

  • chat_api Is there an API for chat and assistants? [supported]: Documented APIs retrieve/create conversations and messages with scoped API keys. Sources: dust:dust:get-conversation, dust:dust:api-keys.
  • knowledge_api Can documents be loaded through an API? [supported]: The data-source API upserts documents into scoped data sources. Sources: dust:dust:upsert.
  • api_governance Do audit, budgets and model rules apply to API use? [supported]: Per-key caps reject further API usage at the limit. Model overrides obey workspace/tier rules; programmatic usage uses the workspace pool and does not count toward beta pooled group budgets. Sources: dust:dust:api-keys, dust:dust:models, dust:dust:credit-management.
  • mcp_server Does the product expose itself to other agents over MCP? [supported]: Global and EU MCP URLs expose authorized Dust knowledge, conversations, agents, files and Pods via OAuth; admins can disable access and control redirects. Sources: dust:dust:mcp-server.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:get-conversation, dust:dust:api-keys, dust:dust:upsert, dust:dust:models, dust:dust:credit-management, dust:dust: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.

Dust

Agent cross-checked Support: partial

Web, browser extension and Teams access are documented; native desktop/mobile availability remains unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust browser extension; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • web Is a full web client available? [supported]: Dust provides the hosted web workspace, including the EU region. Sources: dust:dust:pricing, dust:dust:models.
  • desktop_apps Windows and macOS apps? [unknown]: Windows and macOS apps? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established.
  • mobile_apps iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established.
  • browser_extension Is there a browser extension or sidebar? [supported]: The extension guide covers Chrome, Firefox and Chromium browsers. Sources: dust:dust:browser.
  • managed_deployment Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established.
  • client_feature_gaps Which features are missing on mobile? [unknown]: Which features are missing on mobile? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:models, dust:dust:browser.

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.

Dust

Agent cross-checked Support: partial

An official Teams integration runs agents in Teams; document connectors do not imply Office add-ins.

Availability: generally-available · Delivery: official-integration
Scope: surfaces=Dust in Microsoft Teams; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • word_excel_powerpoint Does it work inside Word, Excel and PowerPoint? [unknown]: Does it work inside Word, Excel and PowerPoint? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately.
  • outlook Does it work inside Outlook? [unknown]: Does it work inside Outlook? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately.
  • teams Is there a Teams app or bot? [supported]: Dust in Teams has an official integration guide and admin setup. Sources: dust:dust:teams.
  • google_workspace_apps Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately.
  • licence_prerequisites Which licences or consents are needed? [partial]: The Teams guide requires integration/admin authorization in a Dust workspace. Extra Microsoft/Dust licence charges were not established. Sources: dust:dust:teams.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:teams.

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.

Dust

Agent cross-checked Support: partial

Agents can perform language work, but document-translation fidelity and controlled terminology are untested.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • document_translation Can whole documents be translated with formatting kept? [unknown]: Can whole documents be translated with formatting kept? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established.
  • translation_engine Which engine translates? [unknown]: Which engine translates? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established.
  • glossaries Are company glossaries supported? [unknown]: Are company glossaries supported? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established.
  • formality_and_variants Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established.
  • writing_tools Are dedicated rewrite and proofreading tools available? [partial]: Configurable agent instructions and Computer document editing support writing workflows; a separate dedicated proofreading product was not established. Sources: dust:dust:builder, dust:dust:computer.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:computer.

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.

Dust

Agent cross-checked Support: partial

Image tools use reference images and parallel generation; exact model and output-right terms need further evidence.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • image_generation Can users generate images, with which models? [partial]: Image Generation is a configurable agent capability with SynthID-marked output. The exact current model identifier is not named in the checked guide. Sources: dust:dust:images.
  • image_editing Can users edit uploaded images? [partial]: Uploaded and prior generated images can be used as references, with up to 14 references. Precise inpainting/masking controls were not established. Sources: dust:dust:images.
  • admin_control Can admins restrict image generation? [partial]: Builders enable image tools in an agent, while group governance controls who creates/publishes agents. A separate organization/group image-off switch was not established. Sources: dust:dust:images, dust:dust:governance.
  • usage_terms What usage rights apply to output? [unknown]: What usage rights apply to output? The image guide and legal entry points were checked. Current model identifier, per-image tariff and contractual output usage rights were not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:images, dust:dust:governance.

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.

Dust

Agent cross-checked Support: partial

Speech generation and meeting-transcript integrations are documented; live voice and Swiss German recognition remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • dictation Can users dictate prompts? [unknown]: Can users dictate prompts? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established.
  • read_aloud Can answers be read aloud? [partial]: Speech Generator converts written text to MP3 audio with selectable voices/languages; a one-click read-aloud mode for all responses was not established. Sources: dust:dust:speech.
  • voice_conversation Is a live voice mode available? [unknown]: Is a live voice mode available? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established.
  • meeting_summaries Are meetings transcribed and summarised? [supported]: Connected Granola/Fathom/Gong/Praiz transcripts can feed summaries; private Gong transcripts are excluded. This is not a native meeting recorder claim. Sources: dust:dust:meetings.
  • swiss_german_speech Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:speech, dust:dust:meetings.

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.

Dust

Agent cross-checked Support: supported

Computer executes analysis and creates real Office files; Frames provide editable interactive output.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • No Excel/PowerPoint fixture or artifact fidelity test. File Generation is deprecated in favor of Computer as of October 14, 2026.
  • data_analysis Can it analyse spreadsheets with executed code? [supported]: Computer executes code to inspect and transform Excel/CSV, compute every-row results and return edited workbooks. Sources: dust:dust:computer.
  • charts Can it produce charts? [supported]: Computer documents chart generation from spreadsheet data and inclusion in reports/decks. Sources: dust:dust:computer.
  • office_file_output Can it create Word, Excel or PowerPoint files? [supported]: Computer creates/edits Word, Excel and PowerPoint files and returns downloadable artifacts, with fidelity caveats. Sources: dust:dust:computer.
  • canvas_editing Is there a document or canvas editor for iterating on output? [supported]: Frames are persistent interactive content that can be revised through agents and shared. Sources: dust:dust:frames.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:computer, dust:dust:frames.

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.

Dust

Agent cross-checked Support: partial

Pods provide shared team conversations, files and tasks; source-sharing effects still need testing.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • No cross-group sharing fixture. Do not infer source-ACL propagation from Pod membership.
  • share_chats Can chats be shared inside the organisation? [supported]: Pod conversations are visible to all members, who can contribute. Sources: dust:dust:pod-chats.
  • team_spaces Are shared projects or workspaces available? [supported]: Open/Restricted Pods group conversations, files and tasks; restricted access is invite-only. Sources: dust:dust:pods.
  • group_chat Can several people chat together with the AI? [supported]: Teammates and agents participate in the same Pod thread and can be mentioned. Sources: dust:dust:pod-chats.
  • share_permission_boundary Does sharing respect the recipient's access to sources? [partial]: All Pod members read conversation contents. Spaces restrict source/agent use and personal tools act under their user; recipient-safe redaction of previously generated text was not established. Sources: dust:dust:pod-chats, dust:dust:permissions, dust:dust:credentials.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pod-chats, dust:dust:pods, dust:dust:permissions, dust:dust:credentials.

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.

Dust

Agent cross-checked Support: partial

German and French UI releases are documented alongside English, with remaining English areas.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • ui_languages Which UI languages are offered? [supported]: October 21, 2026 release adds German; October 16 adds French alongside English US/UK, across product, Frames, extension, Sidekick and Slack/Teams. Sources: dust:dust:changelog.
  • dach_language_quality Are German, French and Italian UIs complete and natural? [partial]: Release notes explicitly leave agent/skill names and instructions in English. German/French naturalness and completeness were not observed; Italian UI was not established. Sources: dust:dust:changelog.
  • accessibility_statement Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? The dated locale announcements were checked; Italian UI and a WCAG conformance statement/report were not established.
  • admin_ui_languages Is the admin interface available in German? [partial]: Admins can set a workspace default language. A complete German admin-screen walkthrough was not observed. Sources: dust:dust:changelog.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:changelog.

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.

Dust

Agent cross-checked Support: partial

SAML SSO can be enforced; Business offers it from five seats on demand.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • No self-serve SSO login test.
  • sso_protocols Which SSO protocols and identity providers work? [supported]: SAML SSO is documented, with Okta, Entra ID and JumpCloud named on pricing. Enterprise marketing also names OIDC; a full provider/protocol matrix was not verified. Sources: dust:dust:sso, dust:dust:pricing, dust:dust:enterprise.
  • sso_plan Which plan includes SSO? [supported]: Business pricing lists SSO for 5+ seats on demand; Enterprise includes it. Sources: dust:dust:pricing.
  • mfa Can MFA be enforced? [partial]: Enforced SAML routes sign-in through the IdP. Specific MFA enforcement behavior was not tested or established in the checked setup guide. Sources: dust:dust:sso.
  • conditional_access Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? SSO and plan guides were checked; conditional-access compatibility and verified-domain capture/migration semantics were not established.
  • domain_capture Can the company claim its email domain? [unknown]: Can the company claim its email domain? SSO and plan guides were checked; conditional-access compatibility and verified-domain capture/migration semantics were not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:sso, dust:dust:pricing, dust:dust:enterprise.

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.

Dust

Agent cross-checked Support: partial

Enterprise SCIM and group roles are documented, with specific annual-seat reclaim behavior.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Enterprise for SCIM; seat-management differences stated; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • scim Is SCIM provisioning supported? [supported]: SCIM 2.0 creates, updates and deactivates users from an IdP as an Enterprise feature. Sources: dust:dust:provision.
  • group_sync Are identity-provider groups synced? [supported]: Provisioned IdP groups govern Space access and can map to Admin/Manager roles. Sources: dust:dust:provision, dust:dust:spaces.
  • jit_provisioning Are users created at first login? [unknown]: Are users created at first login? Provisioning and seat docs were checked. First-login JIT creation and complete leaver-data transfer were not established.
  • deprovisioning What happens to a removed user's data and shared assets? [partial]: SCIM deactivates users; removal/reassignment affects seats but exact chat/agent/knowledge ownership transfer was not tested. Sources: dust:dust:provision, dust:dust:seats.
  • seat_assignment Can admins assign and reclaim seats? [supported]: Admins assign seat types independent of roles. Unassigned members cannot interact with agents; annual seats return to stock, and already-granted credits can persist to period end. Sources: dust:dust:seats.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:provision, dust:dust:spaces, dust:dust:seats.

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.

Dust

Agent cross-checked Support: partial

Dust separates Admin, Manager, Member and group-manager permissions and supports restricted knowledge spaces.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • admin_roles Which admin roles exist, and can admin rights be delegated? [supported]: Admins control all governance; Managers delegate member/group/usage administration; group managers administer selected groups. Sources: dust:dust:governance.
  • groups Can permissions be set per group? [supported]: Permissions go to manual or provisioned groups using Everyone, Groups or Admin-only modes. Multiple grants combine additively. Sources: dust:dust:governance.
  • feature_toggles Which features can be switched on or off per group? [partial]: Group controls cover agent/skill creation and publishing, automation charging, billing/security and model ceilings. An exhaustive per-feature toggle matrix for uploads/web/images was not established. Sources: dust:dust:governance, dust:dust:tiers.
  • multi_entity Can subsidiaries or departments be separated within one contract? [partial]: Restricted Spaces and Pods separate audiences inside a workspace; separate legal/subsidiary tenant boundaries within one contract were not established. Sources: dust:dust:spaces, dust:dust:pods.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:governance, dust:dust:tiers, dust:dust:spaces, dust:dust:pods.

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.

Dust

Agent cross-checked Support: partial

Consumption analytics has detailed attribution and exports without message content.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • adoption_dashboard Is there an adoption dashboard? [partial]: Pricing lists usage/adoption reporting; the Analytics guide focuses on credit consumption and attribution rather than a complete active-user adoption scorecard. Sources: dust:dust:pricing, dust:dust:analytics.
  • breakdowns Can usage be broken down by group, model, feature and assistant? [supported]: Analytics filters/ranks agents, members, groups, models, tools, sources, API keys, skills and Pods. Group attribution may count a member in several groups. Sources: dust:dust:analytics.
  • export Can usage data be exported? [supported]: Raw CSV consumption export and API analytics export are documented, with workspace enablement and key-scope restrictions. Sources: dust:dust:analytics.
  • privacy_modes Can per-person reporting be limited or pseudonymised? [partial]: Analytics exports omit message content, but contain member/message/conversation identifiers. Pseudonymous or works-council privacy modes were not established. Sources: dust:dust:analytics.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:analytics.

ADM-05 Spend controls and cost allocation

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

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.

Dust

Agent cross-checked Support: partial

Credit plans offer consumption visibility, member limits and plan-specific pooled budgets, with programmatic exceptions.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Group budgets are beta and exclude programmatic usage. No budget fixture test.
  • cost_visibility Can admins see cost or consumption per user and group? [supported]: Analytics and Credits show consumed credits by member, group, model, tool and agent. Credits are not assumed to be invoice currency. Sources: dust:dust:analytics, dust:dust:credit-management.
  • budgets Can budgets be set per user or group? [supported]: Members have shared-pool spend limits; beta group budgets require Enterprise Pooled. Programmatic monthly and API-key caps are separate. Sources: dust:dust:credit-management, dust:dust:api-keys.
  • budget_enforcement Does reaching a budget alert, block or downgrade? [supported]: Pool limits/group budgets block further requests; an in-progress message can finish above its starting cap. API calls reject at per-key caps. Optional automatic seat upgrades may increase billed subscriptions. Sources: dust:dust:credit-management, dust:dust:api-keys.
  • chargeback Can costs be exported per cost centre? [partial]: Consumption CSV includes groups and identifiers, but group attribution can duplicate usage and is not a guaranteed invoice-ready cost-center chargeback. Sources: dust:dust:analytics.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:analytics, dust:dust:credit-management, dust:dust:api-keys.

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.

Dust

Agent cross-checked Support: partial

Enterprise has documented event logs and SIEM delivery; content logging and legal hold remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust APIs and MCP server; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Enterprise; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • admin_events Are admin and security events logged? [supported]: Enterprise Audit Logs record significant admin/security, user, API-key, system and tool events with timestamps, targets and actor metadata. Sources: dust:dust:audit.
  • content_logging Can prompts and answers be retained for compliance, and is it configurable? [unknown]: Can prompts and answers be retained for compliance, and is it configurable? Audit, analytics and public legal entry points were checked. Prompt/response compliance capture, eDiscovery/legal hold and detailed log-integrity implementation/retention contract were not established.
  • siem_export Can logs stream to a SIEM or be exported? [supported]: CSV export and continuous destinations include Datadog, Splunk, S3, GCS and custom HTTPS. Sources: dust:dust:audit.
  • ediscovery Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Audit, analytics and public legal entry points were checked. Prompt/response compliance capture, eDiscovery/legal hold and detailed log-integrity implementation/retention contract were not established.
  • log_retention How long are logs kept? [partial]: Enterprise marketing states 365-day audit retention; no underlying report/contract or configurable retention details were retrieved. Sources: dust:dust:enterprise.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:audit, dust:dust:enterprise.

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.

Dust

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.

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.

Dust

Agent cross-checked Support: partial

Agents have persistent instructions and workspace governance; broad enforced content-policy administration is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • org_instructions Can admins set organisation-wide instructions? [partial]: Admins/builders configure agent instructions; an enforced single organization-wide instruction applied to every agent/message was not established. Sources: dust:dust:builder, dust:dust:governance.
  • usage_notice Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? Agent, governance and security pages were checked. Mandatory usage-policy acknowledgement and administrator policy-violation reporting were not established.
  • content_filters Are content filters configurable? [partial]: Image Generation documents NSFW/celebrity safety filtering. Custom organization-wide topic/content rules were not established. Sources: dust:dust:images.
  • violation_reporting Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Agent, governance and security pages were checked. Mandatory usage-policy acknowledgement and administrator policy-violation reporting were not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:governance, dust:dust:images.

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.

Dust

Agent cross-checked Support: partial

EU workspace and EU model controls are distinct from general hosting and global subprocessing.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • storage_region Where are chats, files and indexes stored? [partial]: Pricing/security advertise EU or US workspace hosting. Exact cloud provider, storage country and index location were not established. Sources: dust:dust:pricing, dust:dust:security.
  • inference_region Where do model calls run, per provider? [supported]: EU credit-priced workspaces using Dust-hosted models can enable EU-hosted models only after all active agents comply. BYOK is outside this setting; not every model is eligible. Sources: dust:dust:eu-models.
  • backups_logs_region Where are backups, logs and telemetry? [unknown]: Where are backups, logs and telemetry? Hosting, EU-model and privacy pages were checked. Backup/log/telemetry countries, customer-content support-access geography and Swiss hosting were not established.
  • support_access_region From where can vendor staff access data? [partial]: The controller privacy policy permits non-EEA access/processing including the US; it does not establish customer-content support access by staff country. Sources: dust:dust:privacy.
  • swiss_hosting Is Swiss hosting available? [unknown]: Is Swiss hosting available? Hosting, EU-model and privacy pages were checked. Backup/log/telemetry countries, customer-content support-access geography and Swiss hosting were not established.
  • residency_plan Which plan or option provides residency? [supported]: Business and Enterprise list EU/US residency; EU-only model restrictions additionally require EU region and credit pricing with Dust model hosting. Sources: dust:dust:pricing, dust:dust:eu-models.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:security, dust:dust:eu-models, dust:dust:privacy.

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.

Dust

Agent cross-checked Support: partial

Hosted Business and Enterprise single-tenant offers are public; supported customer-operated whole-platform modes are unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust Enterprise single-tenant deployment; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=not specified; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • multi_tenant_saas Is a shared SaaS offered? [partial]: Business is a self-serve hosted workspace; exact shared-infrastructure isolation architecture is not documented in the checked pages. Sources: dust:dust:pricing, dust:dust:privacy.
  • dedicated_instance Is a dedicated single-tenant instance offered, from what size? [supported]: Enterprise pricing advertises single-tenant deployment. Numerical seat/spend minimum, supported countries and operating terms were not established. Sources: dust:dust:pricing.
  • customer_cloud Can it run in the customer's own cloud account, from what size? [unknown]: Can it run in the customer's own cloud account, from what size? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment.
  • on_premise Can the whole platform run on customer infrastructure, from what size? [unknown]: Can the whole platform run on customer infrastructure, from what size? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment.
  • air_gapped Can it run without internet access? [unknown]: Can it run without internet access? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment.
  • mode_feature_gaps Which features are missing outside SaaS? [partial]: Business/Enterprise packaging differs in connectors, MCP, Spaces, APIs and governance. No customer-operated hosting feature-parity contract was established. Sources: dust:dust:pricing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:privacy.

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.

Dust

Agent cross-checked Support: partial

Dust publishes no-training and provider-retention claims; the customer DPA was not retrieved.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Controller privacy-policy scope is distinct from processor DPA coverage.
  • vendor_training Does the vendor train on customer content? [partial]: The security page claims customer data is never used for model training. This remains vendor-claimed because no customer DPA/contract clause was retrieved. Sources: dust:dust:security.
  • provider_training Do model providers train on it under this product's contracts? [partial]: The privacy policy names OpenAI, Anthropic, Mistral, Google and Fireworks as prohibited from training on customer/personal content; BYOK arrangements need separate confirmation. Sources: dust:dust:training-policy.
  • provider_retention How long do model providers keep prompts, including for abuse monitoring? [partial]: The policy states providers do not log Customer Content for human review or save it to disk. Exception/abuse-retention periods were not established from customer contracts. Sources: dust:dust:training-policy.
  • zero_retention Is zero data retention available, and on which plan? [partial]: Security and privacy pages assert provider zero retention, but applicable plan/model exceptions were not contract-verified. Sources: dust:dust:security, dust:dust:training-policy.
  • human_review Can provider staff review content? [partial]: The published policy says listed providers do not log Customer Content for human review. This is a vendor assertion, not an independently reviewed model-provider contract. Sources: dust:dust:training-policy.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:training-policy.

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.

Dust

Agent cross-checked Support: partial

Some user deletion and memory retention behavior is documented; tenant-wide retention schedules remain open.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • default_retention What is retained and for how long by default? [partial]: Agent memories persist until manually deleted. This does not define default retention for all conversations, files, indexes or logs. Sources: dust:dust:memory.
  • admin_retention Can admins set retention periods? [partial]: Enterprise pricing offers custom data retention; periods, deletion mechanics and exceptions were not retrieved. Sources: dust:dust:pricing.
  • user_deletion Can users delete their chats and files permanently? [partial]: Users can delete conversations and agent memories. Backup erasure timing and all attached-file deletion behavior were not established. Sources: dust:dust:delete-chat, dust:dust:memory.
  • contract_end_deletion What is deleted at contract end, and when? [unknown]: What is deleted at contract end, and when? Conversation/memory docs, Enterprise pricing and unreadable legal entry points were checked. Contract-end erasure timing and complete storage/index/log retention defaults remain unknown.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:memory, dust:dust:pricing, dust:dust:delete-chat.

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.

Dust

Agent cross-checked Support: partial

Dust identifies a French operating entity; customer subprocessor inventory and notice rules remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • subprocessor_list Is a dated sub-processor list published? [unknown]: Is a dated sub-processor list published? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established.
  • subprocessor_countries Which countries do sub-processors operate in? [unknown]: Which countries do sub-processors operate in? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established.
  • change_notification Are customers notified of sub-processor changes? [unknown]: Are customers notified of sub-processor changes? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established.
  • parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: The public policy identifies Permutation Labs at a Paris, France address. A separate parent company or controlling entity was not established. Sources: dust:dust:privacy.
  • transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [partial]: For its controller processing, the privacy policy describes adequacy or EU SCC safeguards for non-EU transfers, including the US. Customer processor transfer terms were not retrieved. Sources: dust:dust:privacy.
  • government_access_policy Is there a published government-access or transparency policy? [partial]: The controller policy allows legally required disclosure to authorities; a dedicated government-request transparency policy for customer content was not established. Sources: dust:dust:privacy.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:privacy.

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.

Dust

Agent cross-checked Support: partial

Enterprise offers custom MSA/DPA terms, while the underlying legal materials were inaccessible.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • dpa Is a DPA available, and is it negotiable? [partial]: Enterprise pricing explicitly offers custom MSA/DPA terms. The form, sign-up incorporation and negotiability boundaries were not inspected. Sources: dust:dust:pricing.
  • revdsg_gdpr Does the DPA cover revDSG and GDPR? [partial]: Marketing and privacy materials reference GDPR; explicit Swiss revDSG coverage in the customer DPA was not established. Sources: dust:dust:security, dust:dust:privacy.
  • governing_law Which law and court govern the contract? [unknown]: Which law and court govern the contract? Official Terms & Policies redirects to a Notion page that returned no readable terms; trust.dust.com also exposed no report text. Governing law/court and EU AI Act technical/role materials were not established.
  • ai_act_materials Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? Official Terms & Policies redirects to a Notion page that returned no readable terms; trust.dust.com also exposed no report text. Governing law/court and EU AI Act technical/role materials were not established.
  • sector_materials Are FINMA or other sector materials provided? [partial]: Security marketing says the service enables HIPAA compliance. A BAA, FINMA or banking-secrecy outsourcing pack was not retrieved. Sources: dust:dust:security.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:security, dust:dust:privacy.

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.

Dust

Agent cross-checked Support: partial

SOC 2 Type II is claimed publicly, without a verified report or certificate.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • iso_27001 ISO 27001 with scope and validity? [unknown]: ISO 27001 with scope and validity? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified.
  • soc2 SOC 2 type, period and covered service? [partial]: Dust security/pricing claim SOC 2 Type II. Auditor, reporting period and exact service scope were not verified. Sources: dust:dust:security, dust:dust:pricing.
  • c5 BSI C5 attestation? [unknown]: BSI C5 attestation? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified.
  • other_certifications Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified.
  • report_access How can customers obtain reports? [partial]: The security page directs customers to trust.dust.com; underlying reports were not accessible in this public source pass. Sources: dust:dust:security.
  • pentest Are independent penetration test summaries available? [unknown]: Are independent penetration test summaries available? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:pricing.

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.

Dust

Agent cross-checked Support: partial

Dust claims AES-256/TLS and advertises Enterprise single tenancy; customer key custody is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • encryption_at_rest Is data encrypted at rest? [supported]: The security page states AES-256 at rest and TLS in transit; this is a vendor claim. Sources: dust:dust:security.
  • customer_managed_keys Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Security, pricing and network/MCP docs were checked. Customer-managed/held data-encryption keys and key-location guarantees were not established. Provider API BYOK is not encryption-key custody.
  • private_networking Is private connectivity or IP restriction available? [partial]: Custom MCP servers can restrict access and use documented static egress on verified domains. This is tool connectivity, not proof of private connectivity to the whole service. Sources: dust:dust:tools.
  • tenant_isolation How are customers separated in shared SaaS? [partial]: Enterprise offers single tenancy; shared Business tenancy and lower-level isolation mechanics were not established. Sources: dust:dust:pricing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:tools, dust:dust:pricing.

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.

Dust

Agent cross-checked Support: partial

Public personnel/model handling statements exist; an explicit professional-secrecy contract and subprocessor flow-down remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Dust Business/Enterprise public policy; Enterprise and BYOK routes differ; add_ons=none stated; deployment_mode=multi-tenant-saas; region=EU/US storage and provider routes; no DE/CH-specific secrecy contract verified; os=not specified.

Limitations

  • No-training, ZDR marketing/policy assertions, EU hosting and a general privacy policy do not establish a professional-secrecy undertaking.
  • No legal suitability or compliance conclusion.
  • secrecy_undertaking Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: The public security and platform privacy pages do not establish a signed §203 StGB/Art321 StGB professional-secrecy undertaking covering Dust staff. The Terms/Policies link did not expose readable contractual text in this pass.
  • subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The privacy policy describes service-provider data-protection agreements and model no-training/retention conditions, but no dedicated professional-secrecy undertaking or its binding subprocessor flow-down was retrieved.
  • secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: No publicly documented German/Swiss professional-secrecy-specific plan or paid add-on was established. Enterprise single-tenancy/EU model options are not treated as such a contractual undertaking.
  • content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: The platform privacy policy limits personnel access to authorized staff and says customer context is processed by selected foundation-model providers; it asserts no provider disk retention/human-review logging. This vendor statement does not establish the complete customer-content plaintext access matrix, support countries, private contracts or every BYOK/MCP/tool route. Sources: dust:dust:privacy, dust:dust:training-policy, dust:dust:eu-models.
  • secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Reviewed public security, privacy, EU-hosted model documentation and Enterprise plan scope plus targeted first-party secrecy search. Trust Center content was not available and Terms/Policies routed to unreadable external content. No public §203/Art321 template or professional-body guidance was retrieved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:privacy, dust:dust:training-policy, dust:dust:eu-models.

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.

Dust

Agent cross-checked Support: partial

Business seat prices are public; only the documented prepaid route is described here, while conflicting Business overage eligibility remains unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business Free/Pro/Max seat list pricing; Enterprise quoted pool and programmatic contracts are separate; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • Do not present Business PAYG as established; retain list seat prices separately from the unresolved overage route.
  • pricing_unit What is the pricing unit? [partial]: Business publishes per-seat subscriptions and included credits. Detailed Credit management describes prepaid Business top-ups and Enterprise PAYG; pricing FAQ separately describes enabled Business workspace overage, so Business post-allocation billing eligibility is unverified. Sources: dust:dust:pricing, dust:dust:credit-management.
  • list_prices What are list prices per plan, with date and currency? [supported]: As retrieved 2026-10-21, ex-VAT Business Free is EUR 0; Pro EUR 30/month or EUR 24/month annually; Max EUR 150/month or EUR 120/month annually. Enterprise is quote-only. Sources: dust:dust:pricing.
  • included_usage What usage is included? [supported]: Free has 500 lifetime credits, Pro 8,000/month and Max 40,000/month. Monthly credits do not roll over; Workspace seats draw from a contracted pool. Sources: dust:dust:credits, dust:dust:seats.
  • add_ons Which features cost extra? [partial]: Business limits include three connectors, five remote MCP servers and five Spaces. Enterprise adds unlimited connector/MCP packaging, SCIM, audit, retention and support. Individual add-on tariffs are not published. Sources: dust:dust:pricing.
  • overage What do usage beyond limits and premium models cost? [unknown]: Effective Business post-allocation billing is unknown: current pricing FAQ allows Pro/Max workspace overage, while Credit management reserves PAYG for Enterprise and describes prepaid Business top-ups. The USD0.01/credit Business programmatic rate does not resolve whether interactive overage is PAYG or prepaid. No account/contract test resolved this.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:credit-management, dust:dust:credits, dust:dust:seats.

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.

Dust

Agent cross-checked Support: partial

ALM-14 shared cost assumptions v1.4, 2026-10-21 apply; all three target seat counts require unpriced Enterprise terms.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • cost_200 Year-one cost at 200 users? [unknown]: Year-one cost at 200 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope.
  • cost_1000 Year-one cost at 1,000 users? [unknown]: Year-one cost at 1,000 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope.
  • cost_5000 Year-one cost at 5,000 users? [unknown]: Year-one cost at 5,000 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope.
  • variable_share Which part depends on usage? [supported]: Consumption adds token and action credits, including sub-agent work. Programmatic use and Enterprise PAYG draw from workspace pools separately from personal seat allocations. Sources: dust:dust:credits, dust:dust:credit-management.
  • unknown_parts Which costs could not be priced? [supported]: Business is scoped to 100 people, so 200/1,000/5,000 seat Enterprise fees, committed pool and PAYG tariffs are unknown. The default Standard auto list is published, but a complete token-to-credit tariff is not, so no proxy replaces vendor-billed usage. Sources: dust:dust:pricing, dust:dust:models, dust:dust:credits.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:credits, dust:dust:credit-management, dust:dust:pricing, dust:dust:models, dust:dust:fx-ecb.

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.

Dust

Agent cross-checked Support: partial

A limited Business free option enables self-serve evaluation; Enterprise features remain contract-scoped.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • free_tier Is there a free tier for business use? [supported]: Business free supports up to five members with 500 lifetime credits per Free seat. Credits do not reset and a user cannot return to Free after upgrading. Sources: dust:dust:seats.
  • self_serve_trial Is a self-serve business trial available? [partial]: The public site offers self-serve free workspace access, not a documented time-limited fully featured Enterprise trial. No card requirement was established. Sources: dust:dust:pricing, dust:dust:seats.
  • trial_scope Do trials include SSO, connectors and admin features? [partial]: Business lists up to three connectors/five Spaces/five remote MCP servers and SSO at 5+ seats on demand. SCIM, audit and custom retention are Enterprise. Sources: dust:dust:pricing.
  • sales_gate Does meaningful evaluation require sales contact? [supported]: Enterprise terms, pooled credits, advanced governance and support are sales-led; a small-team free evaluation is self-serve. Sources: dust:dust:pricing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:seats, dust:dust:pricing.

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.

Dust

Agent cross-checked Support: partial

Business monthly and annual subscriptions are public; Enterprise seats are annual and prices contractual.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • minimum_commitment What seat or spend minimum applies? [partial]: The free option has up to five members and Business targets up to 100 people; Enterprise numerical seat/spend minimum was not established. Sources: dust:dust:pricing, dust:dust:seats.
  • contract_length What contract lengths are offered? [supported]: Business offers monthly and annual seats together; Enterprise seats are annual only. Sources: dust:dust:seats.
  • cancellation How can the contract be cancelled or reduced? [supported]: Monthly seats unassign immediately with a prorated credit; annual seats return to stock for reassignment and are not refunded when someone leaves. Sources: dust:dust:seats.
  • local_invoicing Can it be invoiced in CHF or EUR from a European entity? [partial]: Prices are displayed in EUR and the privacy policy identifies a French entity; CHF invoicing and the actual invoicing entity/currency were not contract-verified. Sources: dust:dust:pricing, dust:dust:privacy.
  • transparency_class Is pricing transparent, partial, quote-only or unknown? [supported]: Partially specified: Business seat prices/credit allowances are public, while Enterprise pricing, complete usage conversion and negotiated terms require a quote. Sources: dust:dust:pricing, dust:dust:credits.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:seats, dust:dust:privacy, dust:dust:credits.

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.

Dust

Agent cross-checked Support: partial

The pinned public repository has an MIT root licence; hosted licensing and complete component coverage are separate.

Availability: generally-available · Delivery: native
Scope: surfaces=Public dust-tt/dust repository root licence; version=dust-tt/dust commit2b1a4973af824f8ff970d585c5eb1f40ae76186c; root LICENSE only; plan=Public source component, not Business/Enterprise hosted-service rights; add_ons=none stated; deployment_mode=not specified; region=Repository licence has no deployment-region entitlement; os=not specified.

Limitations

  • MIT applies to the pinned repository root grant only; dependencies, supported self-host deployment, hosted terms and any closed Enterprise boundary remain unverified.
  • licence_type Which licence applies to each component? [partial]: dust-tt/dust root LICENSE is MIT at commit 2b1a4973af824f8ff970d585c5eb1f40ae76186c. This does not classify every dependency or the contracted hosted service. Sources: dust:dust:licence.
  • branding_restrictions Do licence terms restrict branding or user counts? [supported]: The MIT root grant requires preserving copyright and permission notices and does not itself impose branding or user-count caps. Sources: dust:dust:licence.
  • enterprise_features_closed Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? The pinned root LICENSE and README were retrieved; a complete nested-component licence inventory and separate closed Enterprise edition boundary were not established. Hosted terms were inaccessible.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:licence.

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.

Dust

Agent cross-checked Support: partial

Business Conversation API and Enterprise Data Source API provide scoped data retrieval; agent export entitlement and complete tenant exit remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust APIs and MCP server, Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business Conversation API and web analytics; Enterprise adds Data Source API. Agent-YAML endpoint entitlement is unverified.; add_ons=API keys with appropriate workspace/resource permissions; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Conversation and document retrieval require the corresponding plan and resource permissions. Complete organization coverage, agent-export entitlement and the post-termination retrieval window remain unknown.
  • chat_export Can admins export all chats? [partial]: Business pricing includes Conversation API; authorized API users retrieve accessible conversation messages with pagination. This does not establish one-click all-tenant admin export. Sources: dust:dust:get-conversation, dust:dust:pricing.
  • assistant_export Can assistants and prompts be exported in a reusable format? [unknown]: The agent-YAML endpoint and public pricing were checked on 2026-10-21. Neither establishes its Business or Enterprise entitlement. Reusable assistant/prompt export for a named plan remains unknown.
  • knowledge_export Can knowledge bases and their sources be exported? [partial]: Enterprise pricing adds Data Source API; the documented endpoint retrieves accessible data-source documents as JSON. Complete source/credential/permission portability and an all-tenant export are unverified. Sources: dust:dust:get-document, dust:dust:pricing.
  • export_format Are formats documented and machine-readable? [partial]: Business Conversation API and Enterprise Data Source API return JSON for accessible resources. Web analytics separately exports CSV. These formats do not establish complete tenant export; no plan-scoped agent-YAML export is claimed. Sources: dust:dust:get-conversation, dust:dust:get-document, dust:dust:analytics, dust:dust:pricing.
  • post_termination_window How long can data be retrieved after termination? [unknown]: How long can data be retrieved after termination? No trial admin exit/export was run; complete tenant coverage and the post-termination retrieval window were not established from the accessible API docs or unreadable contract route.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:get-conversation, dust:dust:pricing, dust:dust:get-document, dust:dust:analytics.

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.

Dust

Agent cross-checked Support: partial

Business email support and Enterprise priority/SLA service are advertised; credit terms and local-language support remain open.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • support_channels Which support channels are available on each plan? [supported]: Pricing lists Business email and Enterprise priority support with dedicated CSM; public support/community resources are available. Sources: dust:dust:pricing, dust:dust:support.
  • support_languages Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Support/pricing/Enterprise pages and the official status URL were checked. German/French/Italian staffed support and detailed credited SLA terms were not established.
  • regional_presence Is there a DACH or Swiss entity, team or partner? [partial]: The public policy identifies a Paris, France entity. A DACH/Swiss support team or named regional partner was not established. Sources: dust:dust:privacy.
  • uptime_sla Is there an uptime SLA with credits? [partial]: Enterprise marketing claims 99.9% uptime and pricing includes an SLA; service-credit amounts, exclusions and claim rules were not retrieved. Sources: dust:dust:enterprise, dust:dust:pricing.
  • status_page Is there a public status page with history? [partial]: Model-selection docs link https://dust.statuspage.io for incidents. Direct retrieval timed out, so incident history was not verified. Sources: dust:dust:models.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:support, dust:dust:privacy, dust:dust:enterprise, dust:dust:models.

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.

Dust

Agent cross-checked Support: partial

Dust has rollout and training material, with hands-on support packaged for Enterprise.

Availability: generally-available · Delivery: native
Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Public learning material (no paid entitlement required to read); contracted CSM/onboarding is Enterprise; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • onboarding_service Is guided onboarding included? [supported]: Enterprise pricing includes dedicated CSM and onboarding; exact hours and scope are contractual. Sources: dust:dust:pricing.
  • user_training Is end-user training offered, in which languages? [partial]: Public team onboarding and education resources are available. Course/live-session language coverage was not established. Sources: dust:dust:training, dust:dust:rollout.
  • use_case_library Are role-based use cases and templates provided? [supported]: The public Use Cases and Guides index lists departmental guides for Sales, Support, Marketing, Engineering, Data Analytics, Knowledge, People, Product and Collaboration; the Sales guide supplies concrete agent examples and build links. This establishes public role-based guidance, not a separately verified in-product template entitlement. Sources: dust:dust:r2-department-guides, dust:dust:r2-sales-guide.
  • adoption_programme Is there a champion or adoption programme? [partial]: The rollout guide covers launch, builder community, education and expansion; a contracted champion programme entitlement was not established. Sources: dust:dust:rollout.
  • service_cost Which services cost extra? [partial]: Hands-on CSM/onboarding is Enterprise packaging; a numerical professional-services tariff was not established. Sources: dust:dust:pricing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:training, dust:dust:rollout, dust:dust:r2-department-guides, dust:dust:r2-sales-guide.

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. Auto models and the model picker dust:dust:models

    Users select a model per message or agent; auto choices use maintained ordered lists rather than task-based routing.

    Auto model lists; availability; API overrides · documented · Source date not stated · Retrieved 2026-10-21

  10. EU-hosted models dust:dust:eu-models

    EU credit-plan workspaces using Dust model hosting can restrict agents and auto choices to EU-hosted models; BYOK is excluded from this setting.

    Availability; supported/excluded model table · documented · Source date not stated · Retrieved 2026-10-21

  11. Dust changelog dust:dust:changelog

    Recent dated changes include German/French UI, Gemini 4 Argon and migration from File Generation to Computer.

    October 21, 16 and 14, 2026 entries · documented · Source date 2026-10-21 · Retrieved 2026-10-21

  12. Conversation Files dust:dust:files

    Conversation uploads are scoped to one conversation and support documents, tabular data, images and audio.

    Formats; size table; generating files · documented · Source date not stated · Retrieved 2026-10-21

  13. Dust Pricing dust:dust:pricing

    Business supports up to 100 people with Free/Pro/Max seats; Enterprise pricing is sales-led and adds pooled credits, SCIM, audit, single tenancy and support.

    Business/Enterprise table and FAQ · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

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

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

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

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

  24. Model access tiers dust:dust:tiers

    Admins restrict models and reasoning efforts at workspace, group or member level, with a separate published-agent bypass setting.

    Workspace, group and individual ceilings · documented · Source date not stated · Retrieved 2026-10-21

  25. Spaces management dust:dust:spaces

    Spaces control knowledge and agent access; Business allows five and Enterprise 100 spaces.

    Open/restricted spaces; limits; visibility · documented · Source date not stated · Retrieved 2026-10-21

  26. Credits dust:dust:credits

    Consumption adds token and tool credits; a 600-AWU checkpoint can pause user-started root tasks, with exceptions.

    Token/action credits; checkpoints · documented · Source date not stated · Retrieved 2026-10-21

  27. Credit management dust:dust:credit-management

    Credit sources and block behavior vary by plan; beta Enterprise Pooled group budgets exclude programmatic consumption.

    Personal caps; group budgets; programmatic use · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  31. File size limits dust:dust:file-limits

    The dedicated limits FAQ gives different image, audio and tabular caps than Conversation Files and excludes direct video uploads.

    Upload caps; audio-only restriction · documented · Source date not stated · Retrieved 2026-10-21

  32. Computer dust:dust:computer

    Computer executes code in temporary workspaces, handles Office/PDF files, performs documented OCR and restricts network access by allowlist.

    File work; OCR; network control; secrets · documented · Source date not stated · Retrieved 2026-10-21

  33. Google Drive dust:dust:drive

    Drive sync follows a dedicated connection account and selected content; scanned documents need conversation upload for OCR and Excel table queries need conversion to Sheets.

    Connection identity; refresh; OCR; spreadsheet limitations · documented · Source date not stated · Retrieved 2026-10-21

  34. Search data sources dust:dust:search

    Agents search selected knowledge sources and retrieve relevant document context.

    Document selection; retrieval · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

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

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

  43. Access Controls and Permissions dust:dust:permissions

    Knowledge access is organized through admin-selected connection content and membership of open/restricted Spaces.

    Access policy; connection account; Spaces · documented · Source date not stated · Retrieved 2026-10-21

  44. Microsoft dust:dust:microsoft

    Microsoft data is scoped to the connecting account and selected SharePoint sources; changes synchronize on a five-minute cycle.

    Connection account; delegated and service-principal setup; sync · documented · Source date not stated · Retrieved 2026-10-21

  45. Confluence dust:dust:confluence

    Confluence sync covers selected global spaces, excluding private spaces and pages with view restrictions.

    Scope; restricted pages; refresh · documented · Source date not stated · Retrieved 2026-10-21

  46. Beta: Import Jira issues dust:dust:jira

    A separately documented beta route imports Jira issues as a custom connection.

    Import path · documented · Source date not stated · Retrieved 2026-10-21

  47. What data sources can be connected to Dust? dust:dust:sources

    Official guides identify managed connections and custom API/import routes.

    Named sources · documented · Source date not stated · Retrieved 2026-10-21

  48. Adding an MCP Server dust:dust:tools

    Admins add remote MCP servers with OAuth or bearer credentials and can restrict tools to skills.

    Remote/custom servers; auth; tool restriction · documented · Source date not stated · Retrieved 2026-10-21

  49. Dust BigQuery connection dust:dust:r2-bigquery

    Dust stores BigQuery metadata and runs table queries through a dedicated service account; dataset content is not synchronized into the index.

    No content sync; service-account setup, one location and Space table selection · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

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

  57. Personal vs Shared Credentials for Tools & MCP Servers dust:dust:credentials

    Tools can use a shared account or each user OAuth identity; even personal auth needs initial admin setup.

    Shared versus personal authentication · documented · Source date not stated · Retrieved 2026-10-21

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

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

  60. Dust Security dust:dust:security

    Dust claims EU/US hosting, AES-256/TLS, no model training, provider zero retention and SOC 2 Type II.

    Hosting, training, encryption and certification statements · vendor-claimed · Source date not stated · Retrieved 2026-10-21

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

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

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

  64. Deep-dive Agent dust:dust:deep

    Deep-dive plans, delegates and writes cited reports, using Company Data knowledge and selected tools; Table Query is excluded.

    Research flow; citations; limitations · 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. Agent Memory dust:dust:memory

    Enabled agents retain user-private memory across conversations; users can view and delete it and it persists until deletion.

    Adding the tool; viewing/deleting; privacy · documented · Source date not stated · Retrieved 2026-10-21

  70. Create your first agent dust:dust:builder

    Agents combine instructions, models, knowledge and tools with controlled sharing.

    Instructions; tools; sharing · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  74. Workspace Governance: Roles, Groups & Permissions dust:dust:governance

    Admins delegate manager/group permissions for agents, skills, models, billing and security; grants are additive.

    Roles; permission matrix; additive access · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

  80. Web Search & Browse dust:dust:web

    The tool runs Google queries and browses results, with agent-level configuration and format options.

    Search and browsing flow · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

  85. Triggers dust:dust:triggers

    Agents can run automatically from schedule or event triggers.

    Schedules and events · documented · Source date not stated · Retrieved 2026-10-21

  86. Schedules dust:dust:schedules

    Agents can run on recurring schedules.

    Schedule setup · documented · Source date not stated · Retrieved 2026-10-21

  87. Webhooks dust:dust:webhooks

    Admins configure webhook sources; members attach filtered triggers to agents, with optional signature verification for custom sources.

    Built-in and custom event sources · documented · Source date not stated · Retrieved 2026-10-21

  88. Pods overview dust:dust:pods

    Pods combine shared conversations, tasks and files; open Pods are workspace-browsable and restricted Pods require invitation.

    Shared workspace and visibility · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

  95. API keys dust:dust:api-keys

    Dust API keys have read/admin scopes, data access and enforceable per-key monthly caps.

    Scopes; Space access; caps · documented · Source date not stated · Retrieved 2026-10-21

  96. Dust MCP Server dust:dust:mcp-server

    Dust exposes workspace knowledge, agents, conversations, files and Pods to OAuth MCP clients under the authenticated user permissions.

    Region URLs; OAuth; user permissions · documented · Source date not stated · Retrieved 2026-10-21

  97. Upsert a document in a data source dust:dust:upsert

    The API loads or updates documents in a scoped data source.

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

  98. Get a conversation dust:dust:get-conversation

    The API retrieves accessible conversation messages with pagination.

    Response schema · documented · Source date not stated · Retrieved 2026-10-21

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

  100. Browser Extension dust:dust:browser

    An official extension supports Chrome, Firefox and Chromium-based browsers.

    Browsers and capabilities · documented · Source date not stated · Retrieved 2026-10-21

  101. Dust in Teams dust:dust:teams

    An official Teams integration runs Dust agents within Microsoft Teams after admin setup.

    Setup and usage · documented · Source date not stated · Retrieved 2026-10-21

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

  103. Image Generation dust:dust:images

    Agents generate images from text or references, up to 14 reference images, with SynthID and content restrictions.

    Reference images; parallel generation; safety · documented · Source date not stated · Retrieved 2026-10-21

  104. Voice and sound generation dust:dust:speech

    The speech tool generates MP3 narration or multi-speaker dialogue with selectable languages and styles.

    Speech Generator · documented · Source date not stated · Retrieved 2026-10-21

  105. Meeting transcripts dust:dust:meetings

    Dust consumes transcripts from connected notetaker and sales tools; Gong private transcripts are excluded.

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

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

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

  108. Frames overview dust:dust:frames

    Frames provide persistent interactive agent output that can be refined and shared.

    Creating and editing interactive content · documented · Source date not stated · Retrieved 2026-10-21

  109. Pod conversations dust:dust:pod-chats

    All Pod members can read and contribute to Pod conversations, which are automatically indexed.

    Visibility; indexing; participation · documented · Source date not stated · Retrieved 2026-10-21

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

  111. Single Sign-On dust:dust:sso

    Admins configure and enforce SAML SSO, which disables other social sign-in paths for the workspace.

    Setup; enforcement · documented · Source date not stated · Retrieved 2026-10-21

  112. Dust for Enterprise dust:dust:enterprise

    The Enterprise marketing page claims 365-day audit retention, 99.9% uptime and support for 10,000+ users.

    Security and scale · vendor-claimed · Source date not stated · Retrieved 2026-10-21

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

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

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

  116. Users and groups provisioning dust:dust:provision

    Enterprise SCIM creates, updates and deactivates users and syncs groups; groups can grant Admin/Manager roles.

    SCIM 2.0; group role mapping · documented · Source date not stated · Retrieved 2026-10-21

  117. Seat management dust:dust:seats

    Admins assign independent roles and Free/Pro/Max seats; annual stock and already-allocated credits have specific reclaim rules.

    Seat assignments; billing cycles; leaving · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

  122. Analytics dust:dust:analytics

    Consumption reports break down users, groups, models, tools, agents and Pods; exports omit message content and can double-attribute group usage.

    Attribution; CSV; content exclusion · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

  127. Audit Logs dust:dust:audit

    Enterprise logs distinguish users, API keys and system actors with CSV and continuous SIEM delivery.

    Enterprise scope; actor types; SIEM · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

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

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

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

  137. Dust Platform Privacy Policy dust:dust:privacy

    The policy identifies Permutation Labs in Paris and distinguishes its controller processing from customer processor processing, with non-EEA transfer safeguards.

    About Us; sections 2, 6 and 7 · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

  142. Dust Platform Privacy Policy dust:dust:training-policy

    The policy asserts listed providers do not train, retain or log Customer Content for human review; this source pass did not retrieve the customer DPA.

    Section 6, Foundational Model Providers · vendor-claimed · Source date not stated · Retrieved 2026-10-21

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

  144. Can I delete or rename a conversation? dust:dust:delete-chat

    Users can delete or rename their conversations.

    Conversation actions · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

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

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

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

  154. ECB historical euro reference rates dust:dust:fx-ecb

    EUR 1 = USD 1.1215 = CHF 0.9237 on October 20, 2026.

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

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

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

  157. Dust repository LICENSE at pinned commit dust:dust:licence

    The pinned public repository root licence is MIT; hosted service terms and third-party components are separate.

    Root LICENSE, MIT permission grant · documented · Source date not stated · Retrieved 2026-10-21

  158. Retrieve a document from a data source dust:dust:get-document

    The API retrieves a source document; this does not establish a complete one-click tenant export.

    Endpoint and response · documented · Source date not stated · Retrieved 2026-10-21

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

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

  161. Dust Support dust:dust:support

    The vendor provides public support entry points and community/documentation resources.

    Support channels · documented · Source date not stated · Retrieved 2026-10-21

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

  163. Dust Rollout Guide dust:dust:rollout

    Public rollout guidance covers setup, launch, team education and measurement.

    Rollout phases · documented · Source date not stated · Retrieved 2026-10-21

  164. Team onboarding material dust:dust:training

    Dust provides reusable team-onboarding material.

    Training resources · documented · Source date not stated · Retrieved 2026-10-21

  165. Dust Use Cases and Guides dust:dust:r2-department-guides

    Public guides are organized by Sales, Support, Marketing, Engineering, Data, Knowledge, People, Product and Collaboration.

    Use Cases by Department · documented · Source date not stated · Retrieved 2026-10-21

  166. Dust Sales use-case guide dust:dust:r2-sales-guide

    The Sales guide provides concrete role-based agent examples; this is public learning material, not a contracted training entitlement.

    Sales agent examples and build links · documented · Source date not stated · Retrieved 2026-10-21

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