Agent-readable comparison

Cohere North vs Unique AI

Name: Cohere North vs Unique AI: agent-readable comparison
Creator: onAI

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

Cohere North source checks: 2026-10-21 to 2026-10-26. Website: https://cohere.com/north
Unique AI source checks: 2026-10-21 to 2026-10-26. Website: https://www.unique.ai
Generated 2026-10-27; next source check due 2026-12-20.

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.

providers Which model providers are available? [supported]: Provider types include customer Cohere containers, Cohere Platform/compatibility, vLLM, Azure Cohere, Bedrock, SageMaker, Azure OpenAI, OpenAI and Anthropic. Sources: cohere-north:cohere-north:n-doc-177-20261026.
current_models Which current models are selectable on this plan? [partial]: 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. Sources: 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.
user_choice Can users pick the model per chat? [supported]: Default-agent chat has a model picker; custom agents choose models in settings. Alpha tier picker aliases Default/Alternate/Legacy and can expose additional permitted models. Sources: cohere-north:cohere-north:n-doc-1-20261026, cohere-north:cohere-north:n-doc-134-20261026.
auto_routing Does the product route between models automatically, and is the chosen model shown? [partial]: 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. Sources: cohere-north:cohere-north:n-doc-134-20261026.
multimodal_input Which models accept images, audio or files? [partial]: 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. Sources: cohere-north:cohere-north:n-doc-32-20261026, cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-97-20261026.

Checked 2026-10-26; 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.

Unique AI

Agent cross-checked Support: partial

The platform catalogue supports several providers, subject to tenant credentials, contracts and validation status.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number.

providers Which model providers are available? [partial]: Catalogue includes Azure OpenAI/OpenAI, Anthropic, Google Gemini/Vertex, Together AI and xAI. Provider use must be agreed with each client; a catalogue row is not proof every tenant has it. Sources: unique-ai:unique-ai:models.
current_models Which current models are selectable on this plan? [partial]: Release 2026.42, hosted 14 October, explicitly adds Azure GPT-6.1 Sol and Claude Opus/Sonnet 5.5 through Anthropic/Vertex. Availability overview also lists Gemini3.8 Flash; provider/tenant credentials and validation differ. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:models.
user_choice Can users pick the model per chat? [partial]: Space admins set enabled models; release notes describe chat model switching and API per-message model selection under the same rules. Conduct choices depend on administrator configuration. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct.
auto_routing Does the product route between models automatically, and is the chosen model shown? [unknown]: Does the product route between models automatically, and is the chosen model shown? Unknown. Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number.
multimodal_input Which models accept images, audio or files? [unknown]: Which models accept images, audio or files? Unknown. Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:models, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct, unique-ai:unique-ai:release42.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Unique publishes dated model additions and retirement/migration notes; a complete provider-release lag series remains unknown.

Limitations

A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented.

release_lag_days What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? Unknown. A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented.
changelog Is there a dated public model changelog? [supported]: Availability overview has a dated Recent changes table through 13 October 2026, with provider retirement sources. Sources: unique-ai:unique-ai:models.
deprecation_notice How much notice is given before a model is removed? [partial]: Dated 14 October release announces migrations ahead of o-series provider retirement on 19 November 2026. No guaranteed Unique contractual notice period is established. Sources: unique-ai:unique-ai:release42.
version_pinning Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unknown. A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:models, unique-ai:unique-ai:release42.

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 2026-10-26; 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.

Unique AI

Agent cross-checked Support: partial

Operators can configure customer model endpoints and credentials through GraphQL.

Limitations

BYO licence discounts, provider-by-provider contract onboarding and a full tool/RAG/embedding parity matrix are not public.

own_api_keys Can the customer use its own provider API keys? [supported]: ExternalLanguageModel accepts provider API credentials stored encrypted as immutable write-only values; OAuth2 is also documented. Sources: unique-ai:unique-ai:customllm.
own_cloud_contract Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Custom Azure OpenAI deployment examples specify customer endpoint, deployment, API version and token. Compliance docs mention Bedrock; exact supported Bedrock/Vertex contract routes need deployment scoping. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:compliance.
custom_endpoint Can an admin add any OpenAI-compatible endpoint? [partial]: Documents self/cloud-hosted LXM endpoints and an Azure-compatible connection object. Universal support for any OpenAI-compatible endpoint is not guaranteed. Sources: unique-ai:unique-ai:customllm.
byo_pricing Does BYO change the licence price? [unknown]: Does BYO change the licence price? Unknown. BYO licence discounts, provider-by-provider contract onboarding and a full tool/RAG/embedding parity matrix are not public.
byo_restrictions Which features stop working with BYO? [partial]: Azure Chat Code Execution requires compatible Azure Responses models; switching a custom model group name/deleting an in-use group can break configured assistants. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:code.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:compliance, unique-ai:unique-ai:code.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

The platform documents custom model and embedding connections. Tool parity depends on the selected route: Code Execution lists Azure and LiteLLM OpenAI compatibility, while arbitrary self-hosted model parity is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform; custom-model/embedding connectors and optional Code Execution availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

Code Execution has a listed Responses-capability/model matrix, not universal support for every custom-hosted model. Azure sandbox controls are not extended to every LiteLLM route.
No customer runtime or feature-parity fixture was used; QA-only Phoeniqs is not presented as GA.

self_hosted_chat Can chat use a customer-hosted model? [supported]: Custom LXM and on-premises architecture allow customer-hosted model connections. Models, endpoint compatibility and enabled modules are selected for the contracted deployment. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:onpremsecurity.
self_hosted_embeddings Can retrieval use customer-hosted embeddings? [partial]: An instance maintainer can configure embedding endpoint, key and deployment; the operator overview allows self-hosted embeddings. Supported non-Azure runtimes and a particular customer configuration were not verified. Sources: unique-ai:unique-ai:embeddings, unique-ai:unique-ai:operators.
feature_parity Which features fail with self-hosted models? [partial]: Changing embeddings requires re-embedding existing files. The Code Execution compatibility section explicitly lists Azure Responses-capable IDs and LiteLLM OpenAI IDs, so no blanket Azure-only restriction is asserted. Its introduction/security section describes an Azure sandbox; the actual LiteLLM execution route and parity for arbitrary self-hosted models remain unverified. Sources: unique-ai:unique-ai:embeddings, unique-ai:unique-ai:review2-code.
vendor_hosted_open_models Does the vendor host open-weight models in EU/CH? [partial]: The model catalogue describes Swiss Phoeniqs open models in QA only, not the UAT01/Prod offer. Production entitlement to a vendor-hosted Swiss open model was not established. Sources: unique-ai:unique-ai:review2-models.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:embeddings, unique-ai:unique-ai:operators, unique-ai:unique-ai:review2-code, unique-ai:unique-ai:review2-models.

MOD-05 Model control and usage limits

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

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 2026-10-26; 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.

Unique AI

Agent cross-checked Support: partial

Models and knowledge/tools are configured per access-controlled Space; optional beta daily spending caps block calls.

Availability: beta · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

No two-group restriction fixture was run. Exact contract token/message limits, platform-wide model allow-lists and provider data-routing policy remain unverified.

model_allowlist_by_group Can admins limit models per group? [partial]: Admins bind deployed/approved models to Spaces and grant people/groups space access. Direct per-group model lists across all chats are not documented. Sources: unique-ai:unique-ai:agent.
data_bound_models Can admins restrict which models receive connector or knowledge content? [partial]: A Space binds one model, selected KB sources and tools, and people/group access. A global connector-content model policy is not established. Sources: unique-ai:unique-ai:agent.
default_model Can admins set the default model? [supported]: Administrators select the model for each Space. Sources: unique-ai:unique-ai:agent.
user_limits What per-user message or token limits apply, and are they published? [partial]: Off-by-default beta cost management supports daily USD limits at company/group/user levels, reset at user-local midnight. Public fixed token/message quotas are not established. Sources: unique-ai:unique-ai:cost.
limit_behaviour What happens when a limit is reached? [supported]: With limits enabled, the next model call is blocked when daily spend reaches the cap. Most permissive group limit wins unless a user override exists. Sources: unique-ai:unique-ai:cost.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:cost.

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 2026-10-26; 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.

Unique AI

Agent cross-checked Support: partial

Chat upload defaults are 512 MB/file and 30 files/batch, with source retrieval for large documents.

Limitations

Configured scanned-PDF OCR is documented: MDI supports image-based PDFs, Docling has partial support, and Base Unique Ingestion does not support them. MDI must be provisioned and enabled for the folder or chat Space.
Scanned-PDF accuracy, formula preservation, embedded-figure extraction and shared fixture outcomes were not measured. Older general ingestion limits differ from current production chat defaults.

formats Which formats are accepted? [supported]: Chat supports PDF, DOCX, XLSX, PPTX, CSV, HTML, MD and TXT; PNG/JPEG when enabled per Space. Sources: unique-ai:unique-ai:files.
limits What size and count limits apply per file and chat? [partial]: Production Chat defaults 512 MB/file, 30 files/upload. Code Execution has separate 100 MB and 10-file limits. Environment overrides and aggregate chat caps need tenant confirmation. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:code.
ocr Are scanned PDFs read? [partial]: The file-ingestion guide explicitly distinguishes methods: Base Unique Ingestion does not support image-based scanned PDFs, MDI supports them, and Docling has partial support. MDI must be provisioned and enabled for the folder or in the chat Space ingestion settings. Experimental image-content extraction and deprecated agentic ingestion are separate. No scanned-document fixture or accuracy measurement was run. Sources: unique-ai:unique-ai:file-ingestion-20261026.
spreadsheets Are Excel tables read with structure intact? [partial]: Chat guide says default extraction can fail beyond 5,000 rows x 100 columns. General format guide lists 1,000 x 40; formulas and structure retention were not tested. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:filetypes.
full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [supported]: Checked uploads force retrieval each turn. Large files contribute selected chunks, not necessarily the full file, and users do not see full coverage. Experimental full-PDF mode is separate. Sources: unique-ai:unique-ai:files.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:code, unique-ai:unique-ai:filetypes, unique-ai:unique-ai:file-ingestion-20261026.

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.

persistent_collections Can users keep document collections across chats? [supported]: Libraries reuse uploaded/My files/Google/Microsoft collections across agents/chats/nodes. Alpha Projects index separate private project files. Sources: cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-11-20261026.
sharing_scope Can collections be shared with users, groups or the whole organisation? [supported]: Libraries support user/group/company access with source-dependent roles; Outlook/Exchange remain private. Attaching library to shared agent does not grant library access. Sources: cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-133-20261026.
size_limits What are the collection limits? [partial]: 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. Sources: cohere-north:cohere-north:n-doc-11-20261026, cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-66-20261026.
assistant_binding Can collections be bound to an assistant? [supported]: Agent Resources bind persistent libraries; composer attachment applies to one chat only. Shared recipients must already have library Viewer access. Sources: cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-18-20261026.

Checked 2026-10-26; 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.

Unique AI

Agent cross-checked Support: partial

Knowledge folders persist and can be scoped to users/groups and bound to Spaces.

Limitations

Public total collection/document/token caps and organisation-wide sharing defaults are not specified; chat-only uploads are separately private and expiring.

persistent_collections Can users keep document collections across chats? [supported]: Ingested content lives in knowledge-base folders/scopes beyond a chat. Sources: unique-ai:unique-ai:kbpermissions.
sharing_scope Can collections be shared with users, groups or the whole organisation? [supported]: ScopeAccess grants users or groups read/write access. A flat folder permission does not automatically grant subfolder access. Sources: unique-ai:unique-ai:kbpermissions.
size_limits What are the collection limits? [unknown]: What are the collection limits? Unknown. Public total collection/document/token caps and organisation-wide sharing defaults are not specified; chat-only uploads are separately private and expiring.
assistant_binding Can collections be bound to an assistant? [supported]: Space Internal Search binds selected folders/files and further narrows user permissions. Sources: unique-ai:unique-ai:agent.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:agent.

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.

microsoft_365 Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: 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. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:north-release-html-20261026.
google_workspace Which Google sources are connected? [partial]: 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. Sources: cohere-north:cohere-north:n-doc-151-20261026, cohere-north:cohere-north:n-doc-152-20261026, cohere-north:cohere-north:north-release-html-20261026.
atlassian Confluence and Jira? [partial]: North 2 names Jira among its connectors. Versioned release notes remove the legacy Jira path in 2.0; no Confluence connector entitlement was established. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:north-release-html-20261026.
other_systems Which other business systems? [partial]: 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. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:north-release-html-20261026, cohere-north:cohere-north:n-doc-126-20261026.
on_prem_sources Can on-prem file shares or databases be connected? [partial]: 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. Sources: cohere-north:cohere-north:n-doc-53-20261026, cohere-north:cohere-north:n-doc-126-20261026.
connector_provider Who builds and maintains each connector? [partial]: 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. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:n-doc-126-20261026.

Checked 2026-10-26; 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.

Unique AI

Agent cross-checked Support: partial

Indexed SharePoint and Confluence are documented. Current architecture also names Google Drive/Salesforce, and release notes describe Salesforce/Yahoo Finance MCP connector dashboards; detailed entitlements and source permissions remain connector-specific.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

Architecture labels and release examples do not prove that every source is enabled or included in every contract.
Future items on the roadmap are not promoted to current connector support.
No source-connection or two-user permission fixture was run.

microsoft_365 Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: SharePoint Online connector copies selected content with application consent and optional permission sync. Platform documentation also exposes Teams and Outlook MCP operator guides, but their exact contracted scope and OneDrive coverage were not verified. Sources: unique-ai:unique-ai:sharepoint.
google_workspace Which Google sources are connected? [partial]: The current Platform Overview names Google Drive as a Knowledge Source feeding the Knowledge Base. It does not establish Gmail/Calendar coverage, a deployment guide, source consent scopes or inclusion in a particular customer contract. This is a documented architecture listing, not an observed enabled connector. Sources: unique-ai:unique-ai:platform-overview-20261026.
atlassian Confluence and Jira? [partial]: Official Confluence connector supports Cloud and Data Center; Jira connector coverage was not established. Sources: unique-ai:unique-ai:confluence.
other_systems Which other business systems? [partial]: Release 2026.40 names Salesforce and Yahoo Finance as examples in GA MCP connector dashboards that admins can list, enable and sign in to. Platform Overview also names Salesforce as a Knowledge Source. Exact origin implementation, connector rights, credentials and commercial inclusion vary by configured connector and contract. Sources: unique-ai:unique-ai:release40-20261026, unique-ai:unique-ai:platform-overview-20261026.
on_prem_sources Can on-prem file shares or databases be connected? [partial]: Confluence Data Center sources are supported via REST. Generic file-share/database connector scope was not established. Sources: unique-ai:unique-ai:confluence.
connector_provider Who builds and maintains each connector? [supported]: Unique publishes Kubernetes operator guides for SharePoint and Confluence; client IT supplies source credentials, consent, scope and deployment configuration. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:platform-overview-20261026, unique-ai:unique-ai:release40-20261026.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

SharePoint permission mirroring is optional; Confluence does not synchronise source permissions.

Limitations

No two-user restricted-document/revocation fixture was run. End-to-end revocation SLA and label enforcement are not established. Older folder-permissions documentation says SharePoint never mirrors permissions, conflicting with the newer optional-sync guide.

source_permissions_respected Are source permissions enforced per user? [partial]: SharePoint content_and_permissions mirrors source rights, while content_only uses Unique scope rules. Confluence explicitly has no source-permission sync, so Unique folder access needs configuration. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence.
enforcement_point Does the source system, a mirrored index or nothing enforce them? [supported]: Indexed content is filtered through Unique user/group ScopeAccess. This is not source-system live query-time enforcement. Sources: unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:sharepoint.
revocation_delay How quickly does a removed permission take effect? [partial]: SharePoint source rights refresh periodically, default scans 15 minutes. Internal gatekeeper changes usually propagate under one second but have no hard upper bound; degraded/missed broadcasts can leave old rules active. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:permissioncache.
admin_scope_controls Can admins exclude sites, folders or labels? [supported]: Admins allow SharePoint sites/libraries and require a sync flag, Confluence labels, and Space KB restrictions. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:agent.
sensitivity_labels Are Microsoft Purview or similar labels respected? [partial]: July SharePoint connector explicitly excludes sensitivity/classification-level detection. Separately, release2026.42 documents experimental Purview-protected-file decryption using uploader rights, gated by MIP_DECRYPTION_ENABLED and Entra/operator changes. This is not proof of general label-policy enforcement. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:sharepoint.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:permissioncache, unique-ai:unique-ai:agent, unique-ai:unique-ai:release42.

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 2026-10-26; 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.

Unique AI

Agent cross-checked Support: partial

SharePoint and Confluence copy content to Unique indexes on configurable scans, default every 15 minutes.

Limitations

No source-edit/delete fixture was run. Actual sync duration, strict deletion SLA and index/backup region per contract remain unverified.

live_or_indexed Is content searched live or copied into an index? [supported]: Connectors ingest documents/page attachments into the Unique knowledge base for RAG. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence.
sync_interval How often does an index refresh? [supported]: Default 15-minute scan for both connectors; schedules are configurable. Real-time sync is explicitly not supported. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence.
deletion_propagation How quickly does a deleted document disappear? [partial]: Diff processing detects deleted source files/pages and removes them on a sync run. A strict completion bound is not provided. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence.
index_location Where is indexed content stored? [partial]: Hosted documents use Azure storage; embeddings Qdrant and search vectors on managed disks in the selected deployment. Exact per-client index region needs the MSA/architecture. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:keys.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Unique documents source-linked answers and reference limits, without a shared-corpus accuracy result.

Limitations

No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results.

citations Are answers linked to specific sources? [supported]: Chat retrieval cites sources; Conduct links source facts, with PDF/Word page-level references and other formats at document level. Generated files are not citation-linked or hallucination-checked. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:conduct.
citation_accuracy Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results.
cross_language Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results.
no_answer_behaviour Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results.
observed_accuracy How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:conduct.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Context Memory provides a private cross-chat user profile with edit and opt-out controls.

Limitations

No authenticated memory fixture or permanent deletion test was run. The guide explicitly contradicts the settings deletion promise.

custom_instructions Can users set persistent instructions? [partial]: Admins configure Space instructions; memory learns preferences. A separate persistent user-authored global instruction field was not established. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:memory.
cross_chat_memory Does the product remember facts across chats? [supported]: One per-user profile is loaded across enabled spaces/chats and updated after answers; stored in a private unindexed KB folder. Sources: unique-ai:unique-ai:memory.
user_memory_controls Can users view, edit and delete memories? [partial]: Users view/edit the profile and disable updates/loading. Docs explicitly say disabling does not delete the profile despite contrary settings text; a delete control is not established. Sources: unique-ai:unique-ai:memory.
admin_memory_controls Can admins turn memory off? [supported]: Release2026.42 makes Context Memory GA, with per-company enable/disable feature flag and per-Space activation. Users can opt out; Web Search combinations remain restricted by default. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:memory.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:memory, unique-ai:unique-ai:release42.

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.

create_assistants Can users create assistants with instructions, knowledge and tools? [supported]: Users create agents with instructions, model, tools, libraries and output modes; drafts publish as versioned releases with restore/evaluations. Sources: cohere-north:cohere-north:n-doc-18.
creator_permissions Can admins limit who creates them? [supported]: Can create agents and separate sharing grants control creation/publication audiences. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-114.
sharing_scope Can assistants be shared with users, groups or everyone? [supported]: Published agents share to users/groups/company subject to grants; libraries need separate recipient access and email libraries remain private. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-42.
catalogue Is there an internal assistant directory? [supported]: Agent directory has Starred/My/Shared with me/Company tabs, search and duplication. Sources: cohere-north:cohere-north:n-doc-21.
prompt_library Are shared prompt templates available? [partial]: Agents expose up to four starter prompts and reusable Skills; a separate central prompt-template catalogue not established. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-12.

Checked 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Admins configure Spaces with instructions, models, knowledge, tools, prompts and group access.

Limitations

Assistant versioning, organisation-wide directory discovery and unrestricted end-user creation were not established.

create_assistants Can users create assistants with instructions, knowledge and tools? [supported]: Space setup includes model, instructions, knowledge sources and tools. Sources: unique-ai:unique-ai:agent.
creator_permissions Can admins limit who creates them? [supported]: Space creation/management requires delegated role permissions; Can manage grants space configuration access. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent.
sharing_scope Can assistants be shared with users, groups or everyone? [supported]: Share through Access with people/groups as Can chat or Can manage. Sources: unique-ai:unique-ai:agent.
catalogue Is there an internal assistant directory? [partial]: Space Management lists configured workspaces; a dedicated employee assistant-discovery directory is not described. Sources: unique-ai:unique-ai:agent.
prompt_library Are shared prompt templates available? [supported]: Admins publish Suggested Prompts with a Space; users also have personal saved prompts. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:chat.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:roles, unique-ai:unique-ai:chat.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Built-in tools and beta MCP connectors are governed at organisation and Space levels.

Availability: beta · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique AI Conduct, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted platform with MCP beta feature flag and configured connectors; add_ons=MCP entitlement and enablement per contract; deployment_mode=not specified; region=Tenant plus downstream connector/provider regions; os=not specified.

Limitations

Arbitrary OpenAPI action import, local stdio MCP support, each connector auth mode and universal side-effect approval are not established. Hub planned DLP/elicitation pipeline is not treated as released.

builtin_tools Which tools are built in? [supported]: Internal search, web search, Deep Research and Code Execution are documented; Deep Research is experimental and code has model restrictions. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:code, unique-ai:unique-ai:deepresearch.
custom_actions Can admins add API actions? [unknown]: Can admins add API actions? Unknown. Arbitrary OpenAPI action import, local stdio MCP support, each connector auth mode and universal side-effect approval are not established. Hub planned DLP/elicitation pipeline is not treated as released.
mcp_client Can it use remote MCP servers, and with what admin control? [supported]: MCP Tools for Spaces is beta, off until enabled for the organisation; connector admins and space managers can selectively expose connectors/tools. Sources: unique-ai:unique-ai:mcp.
tool_auth Do tools act as the user or as a shared account? [supported]: MCP Hub maps user hub tokens to downstream per-user OAuth tokens; secrets are injected server-side. Sources: unique-ai:unique-ai:hub.
tool_approval Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins restrict origin/connector/tool exposure. Conduct can pause for approve/deny of configured sensitive actions; it is not a universal confirmation guarantee. Sources: unique-ai:unique-ai:hub, unique-ai:unique-ai:conduct.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:code, unique-ai:unique-ai:deepresearch, unique-ai:unique-ai:mcp, unique-ai:unique-ai:hub, unique-ai:unique-ai:conduct.

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.

web_search Is web search available? [supported]: GA web search supports live URL/search retrieval; text-only and no authenticated websites. Sources: cohere-north:cohere-north:n-doc-74.
admin_toggle Can admins disable it per organisation or group? [partial]: Admins enable provider/tool; Deep Research additionally needs user/group grants. Complete group-specific web-search matrix unverified. Sources: cohere-north:cohere-north:n-doc-74, cohere-north:cohere-north:n-doc-15.
search_provider Which search provider handles queries, and where? [partial]: Tavily defaultGA; Brave/LinkUp alpha, own API keys and one active provider. Provider processing countries not retrieved. Sources: cohere-north:cohere-north:n-doc-74.
deep_research Is multi-step research with a report available? [supported]: Alpha Deep Research delegates multi-step subqueries and creates reports; requires enabled sources, admin/user grants and may queue. Sources: cohere-north:cohere-north:n-doc-15.
web_citations Are web sources cited? [supported]: Live web and Deep Research include source citations; quality untested. Sources: cohere-north:cohere-north:n-doc-74, cohere-north:cohere-north:n-doc-15.

Checked 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Web search has provider/strategy controls; separate Deep Research is experimental.

Limitations

No search/report fixture was run. Exact query/provider regions, contract enablement and current Deep Research production readiness remain unverified.

web_search Is web search available? [supported]: Real-time web search/read is a Space tool, with stable V1/V2 modes and experimental V3. Sources: unique-ai:unique-ai:websearch.
admin_toggle Can admins disable it per organisation or group? [supported]: Admins enable/disable tools per Space shared with groups. Deep Research tools are configured separately; disabling ordinary Web Search is not a universal external-search block. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:deepresearch.
search_provider Which search provider handles queries, and where? [partial]: Configured engines can include Google, Bing, Brave, Jina, Tavily, Firecrawl, Vertex or custom API; query context can leave the tenant. Exact provider region must be set per contract. Sources: unique-ai:unique-ai:websearch.
deep_research Is multi-step research with a report available? [supported]: Experimental tool creates multi-source research and reports. Unique engine can use internal/web sources; OpenAI-native engine requires direct OpenAI-hosted models and lacks internal sources/hosting-location control. Sources: unique-ai:unique-ai:deepresearch.
web_citations Are web sources cited? [supported]: Web answers include source references; Deep Research documents citation-linked reports. Sources: unique-ai:unique-ai:websearch, unique-ai:unique-ai:deepresearch.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:websearch, unique-ai:unique-ai:agent, unique-ai:unique-ai:deepresearch.

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.

workflow_builder Is there a workflow or chain builder? [supported]: Visual node builder combines LLM/agent/tool/conditional/loop steps, versioning and JSON import/export. Sources: cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-29.
scheduled_tasks Can prompts or assistants run on a schedule? [supported]: Users schedule hourly/daily/weekly or cron; optional natural-language suggestions require confirmation. Repeated failure can disable schedules. Sources: cohere-north:cohere-north:n-doc-30.
event_triggers Can external events start a workflow? [partial]: Authenticated execute API enables custom external event integrations. A native inbox/file-change webhook listener was not established. Sources: cohere-north:cohere-north:n-api-run.
builder_audience Is building aimed at business users, IT or developers? [supported]: Business builders use visual/natural-language tools and Human Review; IT provisions connectors/models and developers call APIs. Sources: cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-26, cohere-north:cohere-north:n-api-run.

Checked 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Recurring Scheduled Tasks run with user permissions; current release notes label the feature experimental.

Limitations

No general no-code workflow/chain builder or complete event-source trigger catalogue was established. Automated runs may stop for manual approval/questions and are subject to normal usage limits.

workflow_builder Is there a workflow or chain builder? [unknown]: Is there a workflow or chain builder? Unknown. No general no-code workflow/chain builder or complete event-source trigger catalogue was established. Automated runs may stop for manual approval/questions and are subject to normal usage limits.
scheduled_tasks Can prompts or assistants run on a schedule? [partial]: User guide labels recurring Chat/Conduct tasks beta and off by default; release2026.42 instead labels Scheduled Tasks experimental, off by default, enabled on request, and describes scheduling/eligibility fixes. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:scheduled.
event_triggers Can external events start a workflow? [partial]: SDK documents webhook-driven applications, which require developer-hosted modules; a packaged no-code external-event builder was not established. Sources: unique-ai:unique-ai:sdk.
builder_audience Is building aimed at business users, IT or developers? [partial]: Business users author recurring tasks in the UI or Conduct; developers host webhook-driven SDK modules. Availability and scheduling behaviour depend on deployed release. Sources: unique-ai:unique-ai:scheduled, unique-ai:unique-ai:sdk.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:scheduled, unique-ai:unique-ai:sdk, unique-ai:unique-ai:conduct, unique-ai:unique-ai:release42.

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.

agent_mode Is there an agent mode for multi-step tasks? [supported]: Agents use tools/code; Deep Research decomposes tasks and delegates subagents; automations execute multiple nodes. Sources: cohere-north:cohere-north:n-doc-15, cohere-north:cohere-north:n-doc-34, cohere-north:cohere-north:n-doc-16.
visible_steps Are steps and tool calls shown? [supported]: Sandbox activity expands executed code; automation run viewer shows node inputs/outputs; shared chat includes thinking trace. Sources: cohere-north:cohere-north:n-doc-34, cohere-north:cohere-north:n-doc-30, cohere-north:cohere-north:n-doc-4.
side_effect_confirmation Must the user confirm actions with side effects? [partial]: Tool hints trigger approval; global Allow Always bypasses it and workflows accept action permissions at launch. Human Review nodes can add deliberate checkpoints. Sources: cohere-north:cohere-north:n-doc-150, cohere-north:cohere-north:n-doc-30, cohere-north:cohere-north:n-doc-26.
stop_control Can the user stop a running task? [partial]: Running automations have Cancel. General chat stop behavior and rollback of already executed external actions were not tested. Sources: cohere-north:cohere-north:n-doc-30.

Checked 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Contract-enabled Conduct plans and executes multi-step tasks with visible tools and stop controls. Sensitive actions can ask for approval; separately enabled Experimental Scheduled Tasks offer automatic approval.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Conduct; version=Conduct 2026.40+; scheduling status/flags per 2026.42; plan=Contracted Unique AI platform; Conduct; Scheduled Tasks separately enabled per contract and feature flag availability and deployment/provider configuration depend on the customer agreement; add_ons=Conduct; optional Scheduled Tasks feature flag; deployment_mode=not specified; region=Configured tenant/models/tools; scheduled actions run with the owner permissions and configured approval policy; os=not specified.

Limitations

No agent fixture was run. Interactive sensitive-action approval and separately enabled unattended automatic approval are different execution modes.
Actual tools, entitlement, approval policy and deployed release depend on the customer contract/configuration.

agent_mode Is there an agent mode for multi-step tasks? [supported]: Plans and executes Python/Bash, files, internal search and configured MCP tools in an autonomous workspace. Sources: unique-ai:unique-ai:conduct.
visible_steps Are steps and tool calls shown? [supported]: Shows checklist, progress, code/tool inputs and outputs, and waiting/working indicators. Sources: unique-ai:unique-ai:conduct.
side_effect_confirmation Must the user confirm actions with side effects? [partial]: Conduct shows approve/deny for actions configured as sensitive. The separate Scheduled Tasks guide offers Automatic or Manual approval for Chat/Conduct unattended runs. Release 2026.42 labels scheduling Experimental and feature-flagged. Mandatory human approval of every side effect is therefore not established for all configured runs. Sources: unique-ai:unique-ai:conduct, unique-ai:unique-ai:review2-scheduled, unique-ai:unique-ai:review2-release42.
stop_control Can the user stop a running task? [supported]: Stop ends the turn within seconds; completed steps/files remain and interrupted work can be resumed. Sources: unique-ai:unique-ai:conduct.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:conduct, unique-ai:unique-ai:review2-scheduled, unique-ai:unique-ai:review2-release42.

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.

chat_api Is there an API for chat and assistants? [supported]: Instance REST API supports chat/agents/automations; response endpoint exposes models/tools and SDK access. Separate from Cohere model Platform API. Sources: cohere-north:cohere-north:n-north-api, cohere-north:cohere-north:n-api-response.
knowledge_api Can documents be loaded through an API? [supported]: Authenticated file upload stores content with IDs; library APIs create collections under library permissions. Sources: cohere-north:cohere-north:n-api-upload, cohere-north:cohere-north:n-api-libraries, cohere-north:cohere-north:n-doc-114.
api_governance Do audit, budgets and model rules apply to API use? [partial]: APIs return permission/rate-limit errors and use North identities; sharing restrictions cover API, audit GET exists. Full guardrail/budget/content logging parity not tested. Sources: cohere-north:cohere-north:n-api-response, cohere-north:cohere-north:n-doc-89, cohere-north:cohere-north:n-doc-140.
mcp_server Does the product expose itself to other agents over MCP? [unknown]: Unknown for mcp_server. North REST APIs are public. Full API guardrail/audit/rate-limit parity and a turnkey North-as-MCP server were not established.

Checked 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Public API/Python SDK and Knowledge Base MCP are documented.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique API and Python SDK, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted APIs and KB MCP deployment; model tracking requires enablement; add_ons=KB MCP and usage-tracking enablement per contract; deployment_mode=not specified; region=Configured deployment and external client region; os=not specified.

Limitations

No API/SDK fixture was run; complete endpoint catalogue, rate limits, budget enforcement and all-services audit parity remain unverified.

chat_api Is there an API for chat and assistants? [partial]: SDK exposes the Unique public API, personal/app keys and webhook signatures. Exact endpoint entitlements/rate limits require the contracted deployment. Sources: unique-ai:unique-ai:sdk.
knowledge_api Can documents be loaded through an API? [partial]: Connector/operator docs describe ingestion and knowledge APIs; public SDK supports platform integrations. Sources: unique-ai:unique-ai:sdk, unique-ai:unique-ai:sharepoint.
api_governance Do audit, budgets and model rules apply to API use? [partial]: Feature-flagged model-use tracking covers public API/SDK/agentic and Azure SDK calls with company/user/app metadata. Complete budget/model-rule enforcement across all internal services is not established. Sources: unique-ai:unique-ai:api-usage.
mcp_server Does the product expose itself to other agents over MCP? [supported]: Knowledge Base MCP lets external assistants search/read the Unique KB with the user permissions and admin scope restrictions. The documentation-only MCP endpoint is distinct. Sources: unique-ai:unique-ai:mcpkb.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sdk, unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:api-usage, unique-ai:unique-ai:mcpkb.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

A web workspace is documented; native-client and managed-deployment coverage is unverified.

Limitations

The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown.

web Is a full web client available? [supported]: Public documentation describes browser chat, Space Management and administration. Sources: unique-ai:unique-ai:chat, unique-ai:unique-ai:agent.
desktop_apps Windows and macOS apps? [unknown]: Windows and macOS apps? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown.
mobile_apps iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown.
browser_extension Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown.
managed_deployment Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown.
client_feature_gaps Which features are missing on mobile? [unknown]: Which features are missing on mobile? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:chat, unique-ai:unique-ai:agent.

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.

Unique AI

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-9.

Unique AI

Agent cross-checked Support: partial

A beta Translator Space translates Office files and text with configurable glossaries.

Limitations

No translated-contract fixture was run. Exact engine/model, formality/de-CH controls, supported glossary language pairs and layout fidelity need verification.

document_translation Can whole documents be translated with formatting kept? [partial]: DOCX, XLSX and PPTX document translation is documented, with possible layout disruption. PDF input is explicitly excluded in this Translator mode. Sources: unique-ai:unique-ai:translation.
translation_engine Which engine translates? [partial]: Translator V2 is a standalone AI module configured with a model; no dedicated DeepL engine was established. Sources: unique-ai:unique-ai:translation.
glossaries Are company glossaries supported? [supported]: Admins can configure glossary pre/postprocessing. Sources: unique-ai:unique-ai:translation.
formality_and_variants Can formality and regional variants (de-CH) be set? [partial]: Postprocessing can change regional spelling, exemplified by US-to-UK English. Formality or de-CH-specific support was not verified. Sources: unique-ai:unique-ai:translation.
writing_tools Are dedicated rewrite and proofreading tools available? [partial]: Chat generates and iterates on text; no distinct proofreading/rewriting tool scope was established. Sources: unique-ai:unique-ai:chat.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:translation, unique-ai:unique-ai:chat.

WORK-04 Image generation and editing

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

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.

Unique AI

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.

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.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Voice dictation is documented with Azure Speech prerequisites; recording use is separately described in the DPA.

Limitations

Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone.

dictation Can users dictate prompts? [supported]: Microphone transcribes into the prompt field, with audio discarded after live transcription. Requires configured Azure AI Speech Services; EN/DE/FR/IT are listed. Sources: unique-ai:unique-ai:voice, unique-ai:unique-ai:voice-user.
read_aloud Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone.
voice_conversation Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone.
meeting_summaries Are meetings transcribed and summarised? [partial]: DPA recording use case covers audio/transcripts, optional video and GPT summaries/follow-up emails. This is a contracted recording use case, not proof every Chat plan includes meeting capture. Sources: unique-ai:unique-ai:dpa.
swiss_german_speech Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:voice, unique-ai:unique-ai:voice-user, unique-ai:unique-ai:dpa.

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 2026-10-26; 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.

Unique AI

Agent cross-checked Support: partial

Enabled Chat Code Execution and Conduct can analyse data and produce downloadable files. Selected KB documents can be preloaded into the code container; ordinary unrestricted KB retrieval is separate.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique AI Conduct; version=not specified; plan=Contracted Unique AI platform; Chat Code Execution or Conduct; model compatibility and flags configured separately availability and deployment/provider configuration depend on the customer agreement; add_ons=Code Execution / Conduct enablement per contract; deployment_mode=not specified; region=Documented Azure code container for the Azure route; LiteLLM execution region unverified; Conduct sandbox per contracted deployment; os=not specified.

Limitations

Selected admin-preloaded KB files are supported; this is not arbitrary sandbox retrieval of the whole Knowledge Base.
The page lists Azure and LiteLLM-compatible model IDs but describes Azure-specific container controls. Actual provider execution routing and entitlement require deployment configuration.
No generated-file quality/editability fixture was run.

data_analysis Can it analyse spreadsheets with executed code? [partial]: Chat Code Execution runs Python for CSV/XLSX analysis. The general limitation says KB files are not directly accessible, but admin configuration additionalUploadedDocuments preloads selected KB content_ids, for example templates, into the container. The documented Azure route has no outbound internet/runtime installs and a ten-file/100 MB per-file limit. The compatibility table also lists LiteLLM OpenAI models; that does not establish the same execution-region controls for every route. Conduct separately runs Python/Bash. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct.
charts Can it produce charts? [supported]: The Code Execution guide documents matplotlib PNG/SVG and inline charts. Its described Azure container lacks kaleido, limiting Plotly static exports; no statement about every alternative runtime is inferred. Sources: unique-ai:unique-ai:review2-code.
office_file_output Can it create Word, Excel or PowerPoint files? [partial]: The guide documents DOCX/XLSX generation and PPTX from supplied templates, with variable presentation quality. KB templates can be supplied by the admin preload setting. Generated files remain outside Conduct source-citation/hallucination checks. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct.
canvas_editing Is there a document or canvas editor for iterating on output? [unknown]: No dedicated canvas editor or editable spreadsheet-to-PowerPoint fixture result was established. Downloadable file generation does not establish in-product canvas editing.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Shared Chats is GA in release 2026.42, with company settings and a per-Space toggle. Simultaneous group conversation and recipient source-permission handling remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration; version=2026.42 or later; plan=Contracted Unique AI platform; Shared Chats and Spaces; sharing settings and deployed release availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

A shared conversation is not evidence of simultaneous group participation or recipient access to every source.
No cross-group shared-chat permission fixture was run.

share_chats Can chats be shared inside the organisation? [supported]: Release 2026.42 makes whole-chat sharing GA and on by default for companies, while each Space still needs its Shared chat toggle. Explicit existing company preferences are preserved. Owners can search recipients and copy share links. Sources: unique-ai:unique-ai:review2-release42.
team_spaces Are shared projects or workspaces available? [partial]: Admins publish shared Spaces with people/group Can chat and Can manage roles. These share agent configuration/knowledge, not necessarily a conversation. Sources: unique-ai:unique-ai:agent.
group_chat Can several people chat together with the AI? [unknown]: Whole-chat sharing is documented. A simultaneous multi-person AI conversation, collaborative commenting or live co-editing mode was not established or tested.
share_permission_boundary Does sharing respect the recipient's access to sources? [unknown]: Whole-chat sharing is documented, but whether a recipient can open every cited source or inherits source permissions was not established in the retrieved release/Space documentation. No cross-group fixture was run.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:review2-release42.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-1.

Unique AI

Agent cross-checked Support: partial

Current release notes document German, French and Swiss German UI language behaviour; completeness and accessibility remain unverified.

Limitations

Release notes describe locale fixes, not a full UI audit or conformance statement. No authenticated UI was reviewed.

ui_languages Which UI languages are offered? [partial]: Release2026.42 describes German/French label translations and selected-language login/notices/errors/side-panels, including Swiss German spellings. A complete language matrix was not provided. Sources: unique-ai:unique-ai:release42.
dach_language_quality Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained.
accessibility_statement Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained.
admin_ui_languages Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:release42.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-105.

Unique AI

Agent cross-checked Support: partial

Zitadel supports Entra OIDC, generic OIDC and SAML across documented deployment types.

Limitations

Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented.

sso_protocols Which SSO protocols and identity providers work? [supported]: Setup guides explicitly cover Entra ID OIDC, generic OIDC and SAML, including IdP metadata for closed networks. Sources: unique-ai:unique-ai:sso.
sso_plan Which plan includes SSO? [partial]: Compliance matrix lists SSO for multi-tenant, single-tenant, client-hosted and on-premise modes. Numeric tariff prerequisites are not public. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance.
mfa Can MFA be enforced? [partial]: Hosted compliance matrix lists enforced 2FA; SSO setup delegates authentication to the external IdP. Exact customer MFA policy controls need verification. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance.
conditional_access Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? Unknown. Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented.
domain_capture Can the company claim its email domain? [unknown]: Can the company claim its email domain? Unknown. Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

SCIM, group sync and SAML automatic user creation are documented.

Limitations

Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run.

scim Is SCIM provisioning supported? [supported]: Unique supplies SCIM URL/key for IdP synchronisation, with an Entra guide. Sources: unique-ai:unique-ai:scim.
group_sync Are identity-provider groups synced? [supported]: SCIM syncs users/groups; SSO group claims can also sync on login, requiring optional Graph group permission/admin consent. Sources: unique-ai:unique-ai:scim, unique-ai:unique-ai:sso.
jit_provisioning Are users created at first login? [supported]: SAML setup explicitly enables automatic creation/update and account creation. Sources: unique-ai:unique-ai:sso.
deprovisioning What happens to a removed user's data and shared assets? [unknown]: What happens to a removed user's data and shared assets? Unknown. Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run.
seat_assignment Can admins assign and reclaim seats? [unknown]: Can admins assign and reclaim seats? Unknown. Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:scim, unique-ai:unique-ai:sso.

ADM-03 Roles, groups and feature permissions

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

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Four role/access layers separate identity, feature, Space and knowledge controls.

Limitations

No two-user disabled-feature test was run. Full cross-Space per-group controls and legal-entity separation require contracted setup.

admin_roles Which admin roles exist, and can admin rights be delegated? [supported]: IAM owner/viewer/org-manager plus Unique application roles delegate administration; Space Can manage grants local configuration. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent.
groups Can permissions be set per group? [supported]: Users/groups receive Space and ScopeAccess permissions. Sources: unique-ai:unique-ai:roles.
feature_toggles Which features can be switched on or off per group? [partial]: Tools and upload settings are configured per Space, then Spaces shared to groups. A global group-feature matrix is not established. Sources: unique-ai:unique-ai:agent.
multi_entity Can subsidiaries or departments be separated within one contract? [partial]: Compliance docs describe workspace isolation for departments/client engagements. Multi-subsidiary contractual/billing boundaries are not specified. Sources: unique-ai:unique-ai:compliance.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent, unique-ai:unique-ai:compliance.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Analytics exports cover adoption, assistants, models and tools with privacy controls.

Limitations

Exact group breakdowns, every dashboard entitlement and suppression beyond exported identifiers need verification.

adoption_dashboard Is there an adoption dashboard? [supported]: Reports cover daily/weekly/monthly active users, assistant interactions and document reference statistics. Sources: unique-ai:unique-ai:analytics.
breakdowns Can usage be broken down by group, model, feature and assistant? [partial]: Detailed exports include assistant/model, tool calls, skills, cost and tokens. Group and cost-centre breakdowns were not established. Sources: unique-ai:unique-ai:analytics.
export Can usage data be exported? [supported]: Admins request and download reports with date/assistant filtering; model usage supports CSV. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost.
privacy_modes Can per-person reporting be limited or pseudonymised? [supported]: Environment flags anonymise export emails, optionally with stable pseudonyms; detailed exports respect organisation settings. Sources: unique-ai:unique-ai:analytics.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Off-by-default beta cost management offers estimated spend and enforced daily caps.

Limitations

No small-budget fixture was run. Estimates are configurable cost-sheet values, not a public billing tariff; cost-centre and full invoice reconciliation remain gaps.

cost_visibility Can admins see cost or consumption per user and group? [partial]: Tracks estimated USD/input/output tokens by user, model, assistant/app; a billed invoice reconciliation or group cost view is not established. Sources: unique-ai:unique-ai:cost.
budgets Can budgets be set per user or group? [supported]: Company fallback, group and user daily USD caps; user override first, highest applicable group limit next. Sources: unique-ai:unique-ai:cost.
budget_enforcement Does reaching a budget alert, block or downgrade? [supported]: Before the next call, accumulated daily spend at cap blocks the model call; resets at local midnight. Docs warn caps may break background-job SLAs. Sources: unique-ai:unique-ai:cost.
chargeback Can costs be exported per cost centre? [partial]: CSV exports contain user/app/assistant/model/token/cost metadata, with privacy controls. Cost-centre attribution is not documented. Sources: unique-ai:unique-ai:cost.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:cost.

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 2026-10-26; 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.

Unique AI

Agent cross-checked Support: partial

API audit events, detailed interaction exports and Single-Tenant security-event streaming are documented. A single authoritative retention period for the customer's audit records is not established.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; Audit Logs, Analytics and Single-Tenant Security Events Export availability and deployment/provider configuration depend on the customer agreement; add_ons=SEE for the contracted Single-Tenant deployment; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified.

Limitations

API security-event records, detailed prompt/answer interaction exports, SEE replay and generic operational logging are separate sources/data flows. Their public retention figures are not substituted for each other.
No executed customer retention override or legal-hold/eDiscovery fixture was inspected.

admin_events Are admin and security events logged? [supported]: Event logging covers privileged public/internal API interactions; many self-identity/chat operations are excluded. Basic mode is default; verbose content mode is opt-in. Sources: unique-ai:unique-ai:audit.
content_logging Can prompts and answers be retained for compliance, and is it configurable? [supported]: Detailed chat interaction exports contain prompts/answers for authorised admins and respect configured privacy. Verbose event logging can include CID but is discouraged. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:audit.
siem_export Can logs stream to a SIEM or be exported? [supported]: SEE offers Single-Tenant Azure Defender and Activity events via Event Hub to Sentinel/Splunk, seven-day replay. It excludes tenant-level Entra events and is not a prompt-content audit stream. Sources: unique-ai:unique-ai:security-export.
ediscovery Are eDiscovery and legal hold supported? [unknown]: No public legal-hold/eDiscovery workflow or complete event-log immutability design was established.
log_retention How long are logs kept? [unknown]: Different sources describe different record scopes. The API event guide gives basic-mode MT events 90 days and ST events five years, including post-termination ST retention. DPA 3.15 says audit logs ten years without mapping its audit-log category to those API events. The generic hosted policy says logging up to one year after termination or longer if legally required. SEE has a separate seven-day Event Hub replay window, not the lifetime of all audit records. No customer agreement or authoritative record-class/precedence mapping was retrieved; the applicable audit retention period is unknown.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-audit, unique-ai:unique-ai:analytics, unique-ai:unique-ai:security-export, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:review2-retention.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

DLP is primarily customer infrastructure and integration; it is not a verified default native redaction feature.

Limitations

Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking.

pii_detection Is personal data detected in prompts and files? [unknown]: Is personal data detected in prompts and files? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking.
pii_action Is it redacted, masked, blocked or only warned? [unknown]: Is it redacted, masked, blocked or only warned? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking.
custom_patterns Can admins add custom patterns or terms? [unknown]: Can admins add custom patterns or terms? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking.
dlp_integration Does it integrate with an existing DLP product? [partial]: Documents customer HTTPS proxy/interceptor DLP and post-chat Analytics API scanning; Compliance Layer says pre-LLM calls can be implemented. Multi-Tenant matrix explicitly excludes DLP integration. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance.
filter_location Where does filtering run? [partial]: Proxy inspection runs in customer egress infrastructure; Analytics API supports customer post-chat inspection. A deployment-specific pre-LLM service may be implemented. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Space instructions/banners and customer-specific login terms are documented.

Limitations

Org-wide instruction enforcement, customer content-filter policy controls and administrator violation reports are not established. Prompt guidance is not guaranteed enforcement.

org_instructions Can admins set organisation-wide instructions? [partial]: Admins set Space-level system instructions and persistent banners. A mandatory organisation-wide instruction hierarchy is not specified. Sources: unique-ai:unique-ai:agent.
usage_notice Can users be required to accept a usage policy? [supported]: First login requires terms acceptance; custom terms/editing/deactivation depend on MSA eligibility and admin GraphQL role. Acceptance/version data can be exported. Sources: unique-ai:unique-ai:policy.
content_filters Are content filters configurable? [partial]: Single-tenant Azure prompts pass through Azure content filters; Compliance matrix marks hosted modes with content filtering. Customer filter configuration and scope remain unspecified. Sources: unique-ai:unique-ai:single, unique-ai:unique-ai:compliance.
violation_reporting Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. Org-wide instruction enforcement, customer content-filter policy controls and administrator violation reports are not established. Prompt guidance is not guaranteed enforcement.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:policy, unique-ai:unique-ai:single, unique-ai:unique-ai:compliance.

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.

storage_region Where are chats, files and indexes stored? [partial]: North/Compass data resides in customer VPC/on-prem storage. Customer chooses country; no fixed vendor-hosted North region matrix retrieved. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-168.
inference_region Where do model calls run, per provider? [partial]: Local model chart stays in customer environment; optional Vault/Foundry/other APIs route inference to separately configured regions. Actual contracted provider region unverified. Sources: cohere-north:cohere-north:n-doc-168, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-doc-218.
backups_logs_region Where are backups, logs and telemetry? [partial]: Operators configure backups, logs and telemetry collectors in their environment. Docs do not fix country or require all exports remain local. Sources: cohere-north:cohere-north:n-doc-214, cohere-north:cohere-north:n-doc-208, cohere-north:cohere-north:n-doc-146.
support_access_region From where can vendor staff access data? [partial]: Private-deployment commitment says Cohere does not receive customer prompts; optional Vault processes inference and support bundles may be shared. Support-staff countries/contract access rules unknown. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-217.
swiss_hosting Is Swiss hosting available? [partial]: Customer can place private infrastructure in its chosen country, but a Cohere-operated Swiss North hosting SKU/residency promise was not established. Sources: cohere-north:cohere-north:n-private.
residency_plan Which plan or option provides residency? [partial]: Customer-managed private deployment controls location; optional external inference/telemetry/connector routes require separate governance. No named residency add-on price retrieved. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-217.

Checked 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Documentation offers CH North multitenant hosting and selectable single/customer-hosted regions, with model processing configured separately. The customer's binding residency schedule and full backup/log/support map remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; hosted or customer-hosted platform; separately selected model/tool routes availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Documented options: CH North hosted MT; selected ST/customer region; provider/SKU/tool inference region separately configured; actual contracted boundaries unverified; os=not specified.

Limitations

Available architecture/region options are not a signed residency schedule. Storage, model inference, backups/logs, support access and external tools must be scoped separately.
DPA CH-storage and chosen-location statements are not reconciled by silently treating one as the current customer contract.

storage_region Where are chats, files and indexes stored? [partial]: The deployment matrix documents Azure Switzerland North for hosted multitenant and chosen supported regions for Single Tenant. Tenant storage includes PostgreSQL, documents and vector data. These are configuration options; no customer-specific storage schedule was inspected. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-keys.
inference_region Where do model calls run, per provider? [partial]: The model catalogue separates Azure regional/Data Zone/Global SKUs and external provider routes, with some Swiss deployments and some global-only services. Actual selected provider/SKU/tool routing must be configured for the contracted deployment. CH storage is not a verified CH inference guarantee. Sources: unique-ai:unique-ai:review2-models, unique-ai:unique-ai:deepresearch.
backups_logs_region Where are backups, logs and telemetry? [partial]: Single-tenant backup resources follow the configured landing-zone design and SEE sends events to a separately selected consumer region. An exhaustive physical replica/backup/log/telemetry country matrix was not retrieved. Sources: unique-ai:unique-ai:review2-single, unique-ai:unique-ai:security-export.
support_access_region From where can vendor staff access data? [unknown]: The public DPA gives need-to-know access controls and customer-controlled on-premises support, but not an exhaustive physical country list for vendor/subprocessor support access. Office addresses are not used as support-access locations.
swiss_hosting Is Swiss hosting available? [partial]: CH North is a documented hosted-MT option, and selected-region ST can be Swiss. This records available deployment options, not the customer's end-to-end storage/inference/support contract. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-models.
residency_plan Which plan or option provides residency? [unknown]: DPA 6.1 says storage stays in Switzerland, while its Appendix A allows a client-chosen Microsoft location and current platform docs offer selected jurisdictions. No current customer MSA, precedence clause or deployment schedule was inspected to resolve the binding scope. A contractual CH-wide residency commitment is not asserted.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-models, unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:security-export, unique-ai:unique-ai:deepresearch.

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.

multi_tenant_saas Is a shared SaaS offered? [unknown]: Unknown for multi_tenant_saas. Private VPC/on-prem/air-gapped deployment is documented. Seat floors, full SaaS offers and every disconnected-mode feature exception were not established.
dedicated_instance Is a dedicated single-tenant instance offered, from what size? [partial]: Customer-managed North instance supported; Model Vault inference is dedicated Cohere-managed. Minimum seat/capacity size unpriced. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-vault.
customer_cloud Can it run in the customer's own cloud account, from what size? [partial]: North Helm installs on customer Kubernetes/VPC; infrastructure/network/security operated by customer. No minimum seats retrieved. Sources: cohere-north:cohere-north:n-doc-165, cohere-north:cohere-north:n-private.
on_premise Can the whole platform run on customer infrastructure, from what size? [partial]: Whole North app plus Compass/models documented for customer on-prem Kubernetes; component/GPU dependencies apply. No seat floor retrieved. Sources: cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-doc-168.
air_gapped Can it run without internet access? [partial]: Vendor explicitly offers air-gapped on-prem deployment. External API/search/remote MCP unavailable without egress; registry/image supply needs mirroring. Contracted disconnected feature matrix not retrieved. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-159.
mode_feature_gaps Which features are missing outside SaaS? [partial]: Remote MCP needs internet; external search/inference also need provider access. Local visual parsing/guardrails require extra models/GPU services. Full parity unknown. Sources: cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-14, cohere-north:cohere-north:n-doc-193.

Checked 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Current docs offer shared SaaS, dedicated instances, customer cloud and customer-operated on-premise/air-gapped modes.

Limitations

No deployed tenant was inspected. Seat/contract thresholds and an exhaustive offline feature-parity matrix remain unknown; docs establish an option, not universal entitlement.

multi_tenant_saas Is a shared SaaS offered? [supported]: Installation overview lists Multi Tenant on Unique cloud. Sources: unique-ai:unique-ai:install.
dedicated_instance Is a dedicated single-tenant instance offered, from what size? [partial]: Unique-managed Single Tenant has its own Azure landing zone separated from other customers. Minimum seats/contract value are unpublished. Sources: unique-ai:unique-ai:single.
customer_cloud Can it run in the customer's own cloud account, from what size? [partial]: Operator guide documents deployment in customer cloud account with Unique software/support; cloud-specific rollout is contracted. Sources: unique-ai:unique-ai:operators.
on_premise Can the whole platform run on customer infrastructure, from what size? [partial]: Customer provisions/manages infrastructure on own premises, may run own models and can exclude Unique access. Minimum commitment not published. Sources: unique-ai:unique-ai:onpremsecurity.
air_gapped Can it run without internet access? [partial]: IT-operator overview explicitly offers a full air-gapped on-premise deployment. Compatibility and feature limitations depend on customer setup. Sources: unique-ai:unique-ai:operators, unique-ai:unique-ai:onpremsecurity.
mode_feature_gaps Which features are missing outside SaaS? [partial]: Compliance matrix separates SSO/content filter/DLP/PAM/key capabilities by mode. Azure Chat Code Execution/voice and external web/providers require those services and cannot be assumed in an isolated environment. Sources: unique-ai:unique-ai:compliance, unique-ai:unique-ai:code, unique-ai:unique-ai:voice.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:install, unique-ai:unique-ai:single, unique-ai:unique-ai:operators, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:compliance, unique-ai:unique-ai:code, unique-ai:unique-ai:voice.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Hosted Azure documentation says no model training and disabled Microsoft prompt storage/human review; other provider routes require separate terms.

Limitations

No signed Azure amendment was inspected. Retention and review conditions for Anthropic, Gemini, Together, xAI and direct OpenAI research remain unverified; do not generalise the Azure-only policy.

vendor_training Does the vendor train on customer content? [supported]: Hosted retention policy says no customer data is used for AI/neural-network training. Public terms allow service development and anonymised metadata use; that is not a blanket prohibition of all secondary processing. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:terms.
provider_training Do model providers train on it under this product's contracts? [partial]: Hosted Azure deployment is separate from public OpenAI and training is excluded. Other catalogue providers/direct OpenAI research need their applicable customer terms. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:models, unique-ai:unique-ai:deepresearch.
provider_retention How long do model providers keep prompts, including for abuse monitoring? [supported]: For hosted Azure OpenAI, documents/prompts/answers process in memory only, with logging/human-review opt-out. Ordinary application chats persist in Unique databases. Sources: unique-ai:unique-ai:retention.
zero_retention Is zero data retention available, and on which plan? [partial]: Hosted Azure model calls use no provider content storage per opt-out; this is not zero retention of Unique application history, logs or other provider routes. Sources: unique-ai:unique-ai:retention.
human_review Can provider staff review content? [partial]: Hosted Azure guide says Microsoft prompt/response human review is disabled. Vendor staff need-to-know access and alternate model-provider review conditions are separate. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:dpa.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:terms, unique-ai:unique-ai:models, unique-ai:unique-ai:deepresearch, unique-ai:unique-ai:dpa.

DATA-04 Retention and deletion

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

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Chat content clearing, chat uploads, KB documents, contract-end content deletion, recoverable files, backups and audit records have separate policies. No common purge deadline is established for all copies.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; Chat, Knowledge Base and hosted retention configuration; customer-hosted policy separately controlled availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Contracted storage/provider region; hosted-policy timings not extended to every customer-hosted system; os=not specified.

Limitations

Hosted content policy expressly permits contract-specific variation. Its timings do not define API/DPA audit-record retention.
No tenant configuration, customer MSA, final backup purge or external-provider deletion fixture was inspected.

default_retention What is retained and for how long by default? [partial]: The chat-upload guide describes an admin-configured expiry, typically two weeks, for chat uploads. Hosted policy lists no minimum for KB/blob/vector/database content. Neither figure defines audit-event retention or proves a tenant's configured default. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:review2-retention.
admin_retention Can admins set retention periods? [supported]: DATA_RETENTION_IN_DAYS drives the daily midnight chat-content clearing job; unset/zero disables it. This clears the content categories named by the redaction guide, not all uploads, KB, external tool records or audit events. Sources: unique-ai:unique-ai:redaction.
user_deletion Can users delete their chats and files permanently? [partial]: The redaction guide says deleting a chat removes its Unique chat-content copy and marks the chat record deleted. Separate upload, KB, external-tool, soft-delete, backup and audit policies are not collapsed into that action. Sources: unique-ai:unique-ai:redaction.
contract_end_deletion What is deleted at contract end, and when? [partial]: For Unique-hosted ordinary content, the published policy states a standard 30-day post-termination period unless the customer contract differs. It separately describes recoverable files for 30 days after deletion and database backups for two further weeks. DPA 6.1 requires return/deletion subject to legal record-keeping. Audit-log classes and their contractual lifetime remain unknown under ADM-06; this is not a deadline for deletion of every copy. Sources: unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-dpa.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:redaction, unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-dpa.

DATA-05 Sub-processors and foreign-law exposure

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Checked 2026-10-26; 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.

Unique AI

Agent cross-checked Support: partial

The dated public DPA lists Microsoft, but a complete applicable current subprocessor/country schedule for all contracted model/tool routes was not retrieved. A technical provider catalogue is not substituted for that legal schedule.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; current platform infrastructure and enabled model/tool integrations availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Actual customer provider/country/transfer schedule unverified; os=not specified.

Limitations

The provider catalogue establishes technical choices, not each party's processor role or the legal schedule for a customer contract.
No sales contact, executed current MSA or nonpublic schedule was obtained.

subprocessor_list Is a dated sub-processor list published? [unknown]: The July 2025 public DPA Appendix A lists Microsoft for infrastructure, Cognitive/Azure OpenAI and email. The current technical catalogue offers other provider/tool routes, which may have different contractual roles. No applicable complete current legal schedule or executed customer supplement was retrieved; the Microsoft-only list is not presented as complete.
subprocessor_countries Which countries do sub-processors operate in? [unknown]: DPA Appendix A names CH or a client-chosen Microsoft location; technical model routes separately include regional and global processing. A complete current legal provider/country and support-access schedule for the chosen deployment was not retrieved.
change_notification Are customers notified of sub-processor changes? [unknown]: No applicable current processor-change notification/objection clause for the customer's full provider schedule was retrieved from the DPA or current contract-access documentation.
parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: The current contact page identifies Unique AI AG in Switzerland and regional entities. The public DPA uses Unique AG. Ultimate parent/beneficial-owner jurisdiction and a customer-specific contracting entity were not independently established. Sources: unique-ai:unique-ai:contact, unique-ai:unique-ai:review2-dpa.
transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [unknown]: No complete customer-content transfer-instrument mapping per non-CH/EU provider was retrieved. The website visitor privacy policy is not substituted for customer-content terms.
government_access_policy Is there a published government-access or transparency policy? [unknown]: No current customer-content government-request/transparency policy was retrieved for the complete contracted provider chain. General banking/DPA assurances do not establish such a policy.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:review2-models, unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:contact.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

A public DPA and finance-specific compliance material are available; actual contractual amendments were not inspected.

Limitations

DPA negotiability and signed sector amendments, product-specific EU AI Act roles and exact sector assurance scope remain unverified. This records materials, not a compliance verdict.

dpa Is a DPA available, and is it negotiable? [partial]: DPA accepts click-through/use or signature and defines Unique as processor for hosted MT/ST. Negotiability is not specified. Sources: unique-ai:unique-ai:dpa.
revdsg_gdpr Does the DPA cover revDSG and GDPR? [partial]: DPA addresses GDPR, Swiss FDPIC oversight and MSA-defined laws; Compliance Layer identifies nFDAP/Swiss M329 amendment. Exact signed revDSG/GDPR scope requires MSA. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:compliance.
governing_law Which law and court govern the contract? [supported]: DPA 7 specifies Swiss substantive law and Zürich 1 courts unless mandatory GDPR/MSA otherwise. Public ToS similarly names Swiss law. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:terms.
ai_act_materials Is EU AI Act documentation provided? [partial]: Trust centre describes per-use-case conformity assessments; ISO42001 and AI governance material are public. A complete provider/deployer AI Act technical file is not established. Sources: unique-ai:unique-ai:trust, unique-ai:unique-ai:compliance.
sector_materials Are FINMA or other sector materials provided? [partial]: Compliance Layer names Microsoft M453 FINMA audit-rights amendment, M744 professional/banking secrecy and M329 CH-DPA for Unique-hosted deployments. Actual annexes and current signed scope are not public. Sources: unique-ai:unique-ai:compliance.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:compliance, unique-ai:unique-ai:terms, unique-ai:unique-ai:trust.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-trust.

Unique AI

Agent cross-checked Support: partial

New public 2026 ATTESTA renewals establish ISO27001 and ISO9001 validity to 31 May 2029; the public TÜV SÜD ISO42001 certificate runs to 6 March 2028. SOC2 Type2 is vendor-documented, with full report evidence NDA-gated.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=ATTESTA 10 June 2026 renewals; TÜV SÜD 7 March 2025 certificate; plan=Contracted Unique AI platform; platform assurance; certificates cover the named legal entity and stated scopes, not every module/provider availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Certificates name Unique AG, Zurich, Switzerland; module/provider coverage depends on the stated audit scope; os=not specified.

Limitations

Current ISO27001/9001 evidence is the 2026 renewal plus matching register entries; the stale website-linked PDF is not used to deny current certification.
SOC chronology and access process are vendor-documented, not a reviewed independent SOC report. Certificate scopes are entity-specific and not a universal module/provider assurance.

iso_27001 ISO 27001 with scope and validity? [supported]: Inspected the 2026 ATTESTA Schweizer Zertifizierungsgesellschaft AG ISO27001:2022 certificate for Unique AG, registration 223-06-018.I. It covers software development/operation/trading/distribution and IT services, is issued 10 June 2026 after 4 June surveillance and expires 31 May 2029. The certificate-linked public register matches the number and expiry. The marketing-linked 2025 PDF is an older artifact, not the current renewal. Sources: unique-ai:unique-ai:review2-iso27001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:review2-iso-docs.
soc2 SOC 2 type, period and covered service? [partial]: The dedicated SOC page documents Type1 in December 2023 followed by Type2 in January 2025. This explains the historical Type1 references rather than proving an ongoing Type1-only state. Current Type2 status is a vendor claim; the auditor, actual report period and service/control scope were not inspected because the full report is NDA-gated. Sources: unique-ai:unique-ai:review2-soc.
c5 BSI C5 attestation? [unknown]: No public BSI C5 attestation was retrieved from the certification pages/trust centre or targeted first-party search.
other_certifications Which other certificates (27701, 42001, TISAX)? [partial]: Inspected ATTESTA ISO9001:2015 renewal 223-06-017.Q for the same Unique AG software/IT scope, expiring 31 May 2029, matched in the public register. Separately inspected TÜV SÜD South Asia ISO42001:2023 certificate 99 420 00001, valid 7 March 2025 to 6 March 2028, for development/deployment of financial-services SaaS using foundation or client models. Current full ISAE/FINMA report scope was not inspected. Sources: unique-ai:unique-ai:review2-iso9001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:iso42001.
report_access How can customers obtain reports? [supported]: The ISO documentation provides public certificate downloads. It says the ISO27001 Statement of Applicability requires a valid NDA. The dedicated SOC page likewise makes the audit report/certificate available on request after NDA. No NDA or sales request was made. Sources: unique-ai:unique-ai:review2-iso-docs, unique-ai:unique-ai:review2-soc.
pentest Are independent penetration test summaries available? [partial]: The public DPA describes internal/external security testing and the trust page describes tests/bug bounty. An independent penetration-test report, current scope or summary was not inspected. Sources: unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:trust.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-iso27001, unique-ai:unique-ai:review2-iso9001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:review2-iso-docs, unique-ai:unique-ai:iso42001, unique-ai:unique-ai:review2-soc, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:trust.

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.

encryption_at_rest Is data encrypted at rest? [partial]: Optional deployment-level AES256GCM envelope encryption covers sensitive PostgreSQL chat columns, excluding automations/workflows. Operator must secure object/index/backups and database volumes separately. Sources: cohere-north:cohere-north:n-doc-154, cohere-north:cohere-north:n-doc-146.
customer_managed_keys Can the customer manage or hold the keys? [partial]: Operator supplies32-byte master key in Kubernetes Secret or chart generates it; wrapped DEKs stay in database, key rotation supported. Hardware-held external-KMS entitlement not established. Sources: cohere-north:cohere-north:n-doc-154.
private_networking Is private connectivity or IP restriction available? [partial]: Customer manages VPC, ingress/egress, TLS and Kubernetes network policies; private/on-prem operation documented. These are deployment tasks, not proof every installation enforces them. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-doc-159.
tenant_isolation How are customers separated in shared SaaS? [partial]: Each separately administered installation has own users/config/data; customer operates cluster/network isolation. Multi-tenant hosted North architecture not established. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-doc-146.

Checked 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Deployment guides document encryption, isolated Single Tenant resources and optional IP filtering. Exact current MT PMK/CMK/HSM configuration and key sizes are not established across the conflicting pages.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; hosted MT/ST encryption and optional customer-controlled self-hosting availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Contracted Azure tenant/storage/backup region; actual key-vault/HSM location unverified; os=not specified.

Limitations

No exact RSA/HSM key size or actual MT PMK/CMK design is asserted. A customer-specific deployment/key diagram and key-vault region were not inspected.
Customer-generated imported keys held by Unique do not establish customer-exclusive key custody; full control is a separate self-hosting option.

encryption_at_rest Is data encrypted at rest? [partial]: The compliance matrix documents encryption at rest and in transit across deployment options, with AES256/TLS1.2+ in its controls text. No exact current RSA key size is asserted: the ST architecture says 2048-bit RSA-HSM while the hosted retention page says 4096-bit. An implementation-specific key design was not retrieved. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-retention.
customer_managed_keys Can the customer manage or hold the keys? [partial]: The infrastructure key guide allows a customer-generated key to be imported for a Unique-hosted Single Tenant, with Unique holding/managing it. It directs clients needing exclusive control of all storage keys to customer self-hosting. This is not HYOK or exclusive customer custody in Unique hosting. Actual MT PMK/CMK/HSM configuration is unknown because the key guide and hosted retention matrix disagree. Sources: unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:review2-retention.
private_networking Is private connectivity or IP restriction available? [partial]: The Single-Tenant WAF supports optional IP blocking. The separate SEE consumer endpoint is public TLS with optional allow-list and no standard private endpoint/peering. These are distinct scopes; other private-link options for the customer deployment were not verified. Sources: unique-ai:unique-ai:review2-single, unique-ai:unique-ai:security-export.
tenant_isolation How are customers separated in shared SaaS? [supported]: The Single-Tenant architecture describes a separate customer landing zone under Unique's subscription, isolating its storage/processing from other customers. This documents that ST architecture, not the isolation configuration of every hosted or customer-managed instance. Sources: unique-ai:unique-ai:review2-single.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:security-export.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Unique documents general staff/external-party access controls and customer-controlled on-premises access. A professional-secrecy undertaking under § 203 StGB or Art. 321 StGB, its subprocessor flow-down and qualifying plan/add-on remain unverified. Financial-sector banking-secrecy amendments are recorded separately under DATA-06.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI; profession-specific eligibility and fees unpublished; add_ons=none stated; deployment_mode=not specified; region=Contracted hosting jurisdiction; customer-controlled on-premises access described separately from Unique-hosted access; os=not specified.

Limitations

No executed professional-secrecy undertaking or § 203 / Art. 321 contract was inspected. General DPA confidentiality is not treated as such an undertaking.
The M744 professional-secrecy wording appears in a banking-secrecy/financial-services framework; no inference is made to lawyers, doctors, auditors or tax advisers.
Customer-controlled on-premises access does not establish the same access conditions for Unique-hosted deployments or all model-provider routes. Full plaintext-access mapping remains unknown.

secrecy_undertaking Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: No public Unique AI-specific § 203 StGB or Art. 321 StGB secrecy undertaking covering staff was located in the DPA, compliance documentation or targeted first-party search on 21 October 2026. The DPA confidentiality commitment alone does not establish a professional-secrecy undertaking. No executed or negotiated customer agreement was inspected.
subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The DPA says employees, contractual subprocessors and other service providers are bound to confidentiality of sensitive information. A professional-secrecy-specific obligation extending through the subprocessor/model-provider chain was not verified. The Microsoft M744 banking-secrecy amendment mentioned in the financial-services framework is not counted as evidence of § 203 / Art. 321 coverage for professional secrecy holders.
secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: No qualifying professional-secrecy plan, dedicated offering, add-on tariff or named eligibility rule was located. The documented financial-services amendments and general deployment choices do not establish a separate § 203 / Art. 321 offering. Contract-specific terms and fees remain unknown.
content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: DPA Appendix B permits employees or external parties access to personal/confidential information on a need-to-know basis. For on-premises support, customers control remote connections and Unique staff cannot access a customer system without customer knowledge or full active participation. The on-premises architecture also allows operation without any Unique access under customer control. These sources do not exhaustively identify plaintext access at each hosted subprocessor/model provider or profession-specific access conditions. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:onpremsecurity.
secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: A public DPA and on-premises architecture describe confidentiality and access controls, but no profession-specific secrecy template or professional-body guidance was located. The compliance page describes Microsoft M453/M744/M329 in a financial-services context; those banking/FINMA disclosures belong to DATA-06 and do not establish the missing professional-secrecy contract.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:compliance.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Applicable current platform pricing unit, list tariff, included usage and overages remain unknown. A separately documented Single-Tenant SEE consumption/engineering charge is retained; legacy sales-conversation terms are excluded.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; platform subscription and separately enabled Single-Tenant SEE availability and deployment/provider configuration depend on the customer agreement; add_ons=SEE scope only where contracted; deployment_mode=not specified; region=Vendor currency and applicable invoicing terms not established for the platform; SEE guide separately quotes indicative CHF consumption; os=not specified.

Limitations

The SEE cost finding is scoped only to that Single-Tenant integration. It does not price the platform subscription or all modules.
The 2023 sales-conversation ToS is excluded as evidence of current Unique AI commercial terms; no sales quote or private contract was requested.

pricing_unit What is the pricing unit? [unknown]: No applicable current platform MSA/order form or tariff establishing seat, active-user, platform or usage pricing units was retrieved. The public 18 October 2023 ToS defines a sales-conversation intelligence service, so its subscription/Order Form clauses are not applied to current Unique AI.
list_prices What are list prices per plan, with date and currency? [unknown]: No applicable current platform list tariff, tier names or primary invoicing currency was retrieved from platform/contract documentation or targeted first-party search.
included_usage What usage is included? [unknown]: No applicable current platform agreement specifying included model tokens, storage or module allowances was publicly retrieved.
add_ons Which features cost extra? [partial]: Single-Tenant SEE passes through Azure consumption without markup; guide observes CHF20-50/month/environment, not a fixed quote, with initial engineering at agreed rates. Other module charges are unpublished. Sources: unique-ai:unique-ai:security-export.
overage What do usage beyond limits and premium models cost? [unknown]: No applicable current platform overage or premium-model sales tariff was retrieved. Cost-management model estimates are not substituted for a customer sales tariff.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:security-export, unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

ALM-14 shared cost assumptions v1.4, 2026-10-21. Public enterprise pricing is insufficient for the required 200/1,000/5,000-user annual totals.

Limitations

ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate.

cost_200 Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate.
cost_1000 Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate.
cost_5000 Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate.
variable_share Which part depends on usage? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate.
unknown_parts Which costs could not be priced? [supported]: Subscription/order pricing, usage billing, provider contracts, deployment operation, connectors, execution, training and support charges are not publicly priced. SEE consumption example alone cannot price the platform. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:platform, unique-ai:unique-ai:security-export.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:platform, unique-ai:unique-ai:security-export, unique-ai:unique-ai:ecb-fx.

VEN-03 Evaluation access

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

The partial atomic answers state their documentation or verification limits.

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

Checked 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

The public route is demo/evaluation by arrangement; self-service trial conditions were not established.

Limitations

No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used.

free_tier Is there a free tier for business use? [unknown]: Is there a free tier for business use? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used.
self_serve_trial Is a self-serve business trial available? [unknown]: Is a self-serve business trial available? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used.
trial_scope Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used.
sales_gate Does meaningful evaluation require sales contact? [partial]: Current platform CTA requests a demo; public baseline ToS says Unique may offer evaluation at its discretion. This does not prove every meaningful evaluation is sales-gated. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:terms.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:terms.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Current platform minimums, term, cancellation and local invoicing remain unknown because the applicable agreement was not publicly retrieved. Current documentation makes legal contracts available on request; legacy sales-conversation renewal clauses are excluded.

Availability: generally-available · Delivery: native
Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; platform commercial agreement; actual agreement not inspected availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CHF/EUR invoicing and legal entity for a specific platform contract unverified; os=not specified.

Limitations

No current customer agreement or sales quote was requested. Contract availability on request does not establish price, term or cancellation conditions.

minimum_commitment What seat or spend minimum applies? [unknown]: No current platform seat/spend minimum was established from the public contract-access and platform pages.
contract_length What contract lengths are offered? [unknown]: No applicable current Unique AI agreement establishing subscription duration, renewal term or notice period was retrieved. The 2023 sales-conversation service term is not applied.
cancellation How can the contract be cancelled or reduced? [unknown]: Current Unique AI cancellation, refund, seat-reduction and nonrenewal rules were not retrieved. The 30-day renewal notice and quantity restrictions from the sales-conversation ToS are excluded.
local_invoicing Can it be invoiced in CHF or EUR from a European entity? [unknown]: CHF/EUR invoice currency, billing entity and local invoicing eligibility for a current platform contract were not established.
transparency_class Is pricing transparent, partial, quote-only or unknown? [partial]: The current governance framework says legal contracts and end-user T&Cs are available on request. No applicable public platform list tariff or complete commercial agreement was retrieved. This records an access/transparency gap, not a price or a customer-specific commitment. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

The public reference repository uses restricted Unique License v1, while the Python SDK has an explicit MIT exception. Hosted platform component terms and enterprise-edition boundaries remain unverified.

Availability: source-only · Delivery: native
Scope: surfaces=Unique API and Python SDK, Unique AI Chat and administration; version=Unique-AG/ai commit afa596c9b4b0231895ff70f44029a9a525f746e9; plan=Public reference-code and Python SDK licences; current contracted Unique AI client/server/connector agreement remains unavailable; add_ons=none stated; deployment_mode=not specified; region=Public Unique License v1 specifies Swiss law and Zurich venue; this is not a hosted-service residency claim; os=not specified.

Limitations

The MIT exception applies to unique_sdk, not every directory or the hosted platform.
Root reference-code terms are not substituted for customer platform branding, seat or enterprise-edition conditions.
The 2023 sales-conversation service ToS remains excluded.

licence_type Which licence applies to each component? [partial]: The public Unique-AG/ai repository at afa596c9b4b0231895ff70f44029a9a525f746e9 defaults to Unique License v1, which restricts commercial use, distribution and modification without written approval. The unique_sdk directory is an explicit MIT exception, confirmed by LICENSE and package metadata. This is a component-level source-available/MIT distinction; current hosted client/server/connector customer terms and a full dependency inventory remain unknown. Sources: unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026, unique-ai:unique-ai:sdk-package-20261026.
branding_restrictions Do licence terms restrict branding or user counts? [partial]: Unique License v1 requires written approval to modify or redistribute covered reference code; the MIT SDK exception requires retention of copyright/licence notices. A current hosted-platform white-label/logo-removal obligation or a numerical user cap is not established by these public component licences. Sources: unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026.
enterprise_features_closed Are enterprise features in a separate closed edition? [unknown]: Current closed/open enterprise-edition boundaries were not established from an applicable component licence inventory. Public SDK/repository availability is not proof of the whole platform licence. Rechecked 2026-10-26 in Unique AI governance framework: contract access, Terms and Conditions Administration. No current customer MSA, quote, private schedule or gated contract was requested. The differently scoped 2023 sales-conversation ToS remains excluded.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin, unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026, unique-ai:unique-ai:sdk-package-20261026, unique-ai:unique-ai:review2-governance-20261026, unique-ai:unique-ai:review2-terms-admin-20261026.

VEN-06 Data export and exit

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

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Authorised content/report export exists, but full assistant/knowledge portability is unverified.

Limitations

Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run.

chat_export Can admins export all chats? [partial]: Detailed interaction export includes user prompts/answers over a chosen period with privacy settings. Completeness across files, agent state and all historical chats was not tested. Sources: unique-ai:unique-ai:analytics.
assistant_export Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unknown. Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run.
knowledge_export Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? Unknown. Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run.
export_format Are formats documented and machine-readable? [partial]: Model usage CSV and detailed analytics exports are documented. DPA promises return in existing format, not a universal reusable assistant/knowledge format. Sources: unique-ai:unique-ai:cost, unique-ai:unique-ai:analytics, unique-ai:unique-ai:dpa.
post_termination_window How long can data be retrieved after termination? [partial]: Baseline ToS 11.4 offers recorded-call download/export on written request within 30 days; that does not establish a chat/assistant/KB exit window. DPA return is within reasonable time. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:dpa.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost, unique-ai:unique-ai:dpa, unique-ai:unique-ai:terms.

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

Enterprise support and a public multitenant status page are available; response times are contracted.

Limitations

Guaranteed DE/FR/IT support, numeric hours/response times, dedicated uptime/credits and complete incident-history export were not established.

support_channels Which support channels are available on each plan? [supported]: Enterprise email and three-layer dedicated support escalation through customer team, CS and engineering. Hours/responses depend on SLA; extended-hours contract is extra. Sources: unique-ai:unique-ai:support.
support_languages Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. Guaranteed DE/FR/IT support, numeric hours/response times, dedicated uptime/credits and complete incident-history export were not established.
regional_presence Is there a DACH or Swiss entity, team or partner? [supported]: Unique AI AG lists Zürich, Unique Germany GmbH Berlin, plus UK/US/Singapore entities. Sources: unique-ai:unique-ai:contact.
uptime_sla Is there an uptime SLA with credits? [partial]: Support docs defer hours and response times to SLA contract; no public uptime/credit schedule was obtained. Baseline terms only promise commercially reasonable availability efforts. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:terms.
status_page Is there a public status page with history? [supported]: status.prod.unique.app publicly shows component/uptime history. Support docs scope it to multitenant accounts, not every dedicated environment. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:status.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:contact, unique-ai:unique-ai:terms, unique-ai:unique-ai:status.

VEN-08 Onboarding, training and adoption

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

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 2026-10-21; 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.

Unique AI

Agent cross-checked Support: partial

The vendor markets forward-deployed delivery and structured training; inclusion and cost remain unpriced.

Limitations

Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published.

onboarding_service Is guided onboarding included? [partial]: Homepage markets embedded forward-deployed experts helping business/IT ship use cases; exact licence-included rollout scope is contracted. Sources: unique-ai:unique-ai:homepage.
user_training Is end-user training offered, in which languages? [partial]: Vendor homepage describes structured programmes teaching users to use/build/scale; current languages and course entitlement are not specified. Sources: unique-ai:unique-ai:homepage.
use_case_library Are role-based use cases and templates provided? [supported]: Public documentation has finance-role workflows, Chat/Conduct guidance, configurable Suggested Prompts and agent examples. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct.
adoption_programme Is there a champion or adoption programme? [unknown]: Is there a champion or adoption programme? Unknown. Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published.
service_cost Which services cost extra? [unknown]: Which services cost extra? Unknown. Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:homepage, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct.

Sources

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
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
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
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
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
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
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
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
Unique LLM availability overview unique-ai:unique-ai:models
Lists contract-dependent provider/model availability, region SKUs, dated additions and retirements; CH Phoeniqs remains QA-only.
Per-client availability; Azure/LiteLLM/Phoeniqs matrices; Recent changes · documented · Source date 2026-10-12 · Retrieved 2026-10-21
Unique AI space configuration unique-ai:unique-ai:agent
Documents admin instructions, configured model/tools, knowledge binding, prompts and people/group Can chat/Can manage access.
Models; sources/tools; sharing; publishing · documented · Source date 2026-06-18 · Retrieved 2026-10-21
Unique AI Conduct unique-ai:unique-ai:conduct
Documents autonomous Python/Bash work, visible steps, approvals and stop, with per-chat files and restricted egress.
GA release 2026.40; execution UI; limitations · documented · Source date 2026-09-30 · Retrieved 2026-10-21
Unique release 2026.42 unique-ai:unique-ai:release42
Hosted release 14 October 2026 makes chat sharing and Context Memory GA, labels Scheduled Tasks experimental, changes protected-file ingestion and documents current model additions/migrations.
Release Overview; Chat Platform; RAG; Unique AI; Language Model · documented · Source date 2026-10-14 · Retrieved 2026-10-21
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
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
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
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
Custom LXM connection unique-ai:unique-ai:customllm
Documents operator-created external model endpoints, API/OAuth credentials and model groups.
Technical insight; Create and Connect; Security · documented · Source date 2026-05-07 · Retrieved 2026-10-21
Code Execution unique-ai:unique-ai:code
Documents Azure Responses API Python execution, downloadable outputs, no outbound internet and model/file restrictions.
Compatibility; output; limitations; governance · documented · Source date 2026-07-30 · Retrieved 2026-10-21
Compliance Layer 3.0 unique-ai:unique-ai:compliance
Describes FINMA/bank-secrecy/CH-DPA Microsoft amendments and deployment-specific assurance limitations.
Legal framework; FSI amendments; deployment feature matrix · documented · Source date 2026-05-27 · Retrieved 2026-10-21
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
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
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
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
Custom embedding models unique-ai:unique-ai:embeddings
Documents custom embedding endpoints, one model per organisation and mandatory re-embedding after model/dimension changes.
Setup; configuration; re-embedding · documented · Source date 2026-05-07 · Retrieved 2026-10-21
On-premises security architecture unique-ai:unique-ai:onpremsecurity
Documents full customer control and possible operation without Unique access, with customer models/infrastructure.
Overview; custom setup · documented · Source date 2026-05-08 · Retrieved 2026-10-21
IT operator documentation overview unique-ai:unique-ai:operators
Describes dedicated Unique-managed, customer-cloud and full air-gapped on-premise modes.
Supported deployment models · documented · Source date not stated · Retrieved 2026-10-21
Code Execution unique-ai:unique-ai:review2-code
The page allows selected Knowledge Base files to be preloaded with additionalUploadedDocuments. Its compatibility list includes Azure and LiteLLM OpenAI Responses-capable IDs despite Azure-only introduction/limitations. Azure sandbox controls are not proof of the LiteLLM execution region.
Functionality; Limitations; All available models; Security & Governance; additionalUploadedDocuments · documented · Source date 2026-07-30 · Retrieved 2026-10-21
Unique LLM availability overview unique-ai:unique-ai:review2-models
The model catalogue separates provider routes, region/SKU choices and QA-only Swiss Phoeniqs. It is a technical availability inventory, not a complete legal subprocessor schedule.
Provider and region matrices; Phoeniqs Model Service; recent changes · documented · Source date 2026-10-12 · Retrieved 2026-10-21
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
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
Model usage and cost management unique-ai:unique-ai:cost
Documents off-by-default estimated usage dashboards and enforced daily company/group/user model-call limits.
Beta flags; daily limits; cost calculation; CSV · documented · Source date 2026-07-21 · Retrieved 2026-10-21
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
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
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
Upload and Chat limits unique-ai:unique-ai:files
Specifies 512 MB/file, 30 files/batch, default forced retrieval for selected uploads and configurable expiry.
Production limits; retrieval; expiry · documented · Source date 2026-06-28 · Retrieved 2026-10-21
Supported file types unique-ai:unique-ai:filetypes
Lists common Office/PDF/text formats and general ingestion limitations that differ from the newer chat-specific limits.
Types; exceptions; ingestion quality · documented · Source date 2026-05-09 · Retrieved 2026-10-21
Unique file ingestion administration unique-ai:unique-ai:file-ingestion-20261026
Base ingestion lacks scanned-PDF OCR. MDI supports image-based PDFs; Docling has partial support. MDI must be provisioned and enabled per folder or chat Space, and the guide distinguishes experimental image-content extraction and deprecated agentic ingestion.
Ingestion overview capability table; Enable MDI; Enable MDI for Upload in Chat · documented · Source date not stated · Retrieved 2026-10-26
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
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
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
Knowledge scope permissions unique-ai:unique-ai:kbpermissions
Describes query filtering by user/group scopes, but older SharePoint permission statements differ from the newer connector guide.
Scopes; source integration limits · documented · Source date 2026-05-07 · Retrieved 2026-10-21
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
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
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
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
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
SharePoint connector unique-ai:unique-ai:sharepoint
Documents periodic indexed sync, optional content-and-permissions mode, site selection and absent label-level detection.
Modes; permission sync; limitations · documented · Source date 2026-07-06 · Retrieved 2026-10-21
Confluence connector unique-ai:unique-ai:confluence
Documents Cloud/Data Center content sync without source-permission synchronisation.
Requirements; sync; limitations · documented · Source date 2026-06-28 · Retrieved 2026-10-21
Unique platform overview unique-ai:unique-ai:platform-overview-20261026
The platform architecture names Google Drive and Salesforce among knowledge sources, alongside SharePoint/OneDrive, Confluence and Teams/Outlook. It does not provide per-connector consent, rollout or price entitlements.
Connectors and Knowledge Sources diagram · documented · Source date not stated · Retrieved 2026-10-26
Unique release 2026.40 unique-ai:unique-ai:release40-20261026
GA HTML dashboards can list, enable and sign in to MCP connectors, with Salesforce and Yahoo Finance named examples. Contract/module enablement and personal connection state still apply.
Hosted September 30 2026; Chat Experience, GA HTML connector dashboards · documented · Source date 2026-09-30 · Retrieved 2026-10-26
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
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
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
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
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
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
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
Permission cache timing unique-ai:unique-ai:permissioncache
Describes usual subsecond internal permission propagation without a hard upper bound, and stale rules after a missed broadcast.
Expected timing; degraded scenarios · documented · Source date 2026-09-22 · Retrieved 2026-10-21
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
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
Single-tenant key management unique-ai:unique-ai:keys
Explains why client-held keys are unavailable across all Single Tenant data stores and directs full key control to self-hosting.
Big picture; BYOK/CYOK/HYOK; storage locations · documented · Source date 2026-05-27 · Retrieved 2026-10-21
Retention and deletion at Unique unique-ai:unique-ai:retention
Documents no training, Azure abuse-monitoring opt-out, post-termination retention and backup exceptions.
Hosted-only scope; Azure provider retention; deletion; encryption · documented · Source date 2026-05-04 · Retrieved 2026-10-21
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
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
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
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
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
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
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
Context Memory in Unique AI Chat unique-ai:unique-ai:memory
Documents private per-user cross-chat memory, edit/disable controls and an explicit warning that disabling does not delete the stored profile.
Private profile; edit and disable; web-search restriction · documented · Source date 2026-09-15 · Retrieved 2026-10-21
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
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
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
Unique AI Chat unique-ai:unique-ai:chat
Describes the user chat workspace and configurable tools.
Features and access · documented · Source date 2026-09-03 · Retrieved 2026-10-21
Access role concept unique-ai:unique-ai:roles
Defines identity, application, space and knowledge-scope permissions, including delegated management roles.
Four access layers · documented · Source date 2026-05-07 · Retrieved 2026-10-21
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
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
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
MCP tools for spaces unique-ai:unique-ai:mcp
Describes feature-flagged beta MCP clients with organisation and per-space connector/tool controls.
Beta warning; flags; selective tool enablement · documented · Source date 2026-05-21 · Retrieved 2026-10-21
MCP Hub security governance unique-ai:unique-ai:hub
Documents per-user token routing, approved origin restrictions and tool-call correlation; some DLP/elicitation pipeline measures are planned.
Authentication; governance; planned request pipeline · documented · Source date 2026-08-26 · Retrieved 2026-10-21
Deep Research tool unique-ai:unique-ai:deepresearch
Documents experimental research/report engine, with separate external OpenAI-engine data flows and limited current tools.
Experimental warning; engines; user flow · documented · Source date 2026-05-09 · Retrieved 2026-10-21
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
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
Web Search tool unique-ai:unique-ai:websearch
Documents multiple search engines, source citations and experimental query review/screening; conversation context may leave through queries.
Modes; engines; external-query warning · documented · Source date 2026-05-20 · Retrieved 2026-10-21
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
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
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
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
Python SDK documentation unique-ai:unique-ai:sdk
Documents SDK/public API access and customer-operated modules with event-driven webhook integration.
Public API; webhook verification; personal/app keys · documented · Source date 2026-05-08 · Retrieved 2026-10-21
Scheduled Tasks unique-ai:unique-ai:scheduled
Documents off-by-default recurring tasks running with user permissions; unattended approvals/questions can stop a run.
Beta warning; task settings; runs and limits · documented · Source date 2026-10-12 · Retrieved 2026-10-21
Scheduled Tasks unique-ai:unique-ai:review2-scheduled
Scheduled Chat/Conduct tasks offer Automatic or Manual approval. The newer release labels scheduling Experimental and feature-flagged; unattended automatic approval is not mandatory human confirmation.
At a glance; task Approval setting; unattended runs · documented · Source date 2026-10-12 · Retrieved 2026-10-21
Unique release 2026.42 unique-ai:unique-ai:review2-release42
Release 2026.42 makes Shared Chats GA, on by default per company with a per-Space toggle and preservation of explicit settings. Scheduled Tasks remain Experimental and feature-flagged.
Highlights; Chat Platform; Conduct scheduling flag · documented · Source date 2026-10-14 · Retrieved 2026-10-21
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
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
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
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
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
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
Knowledge Base MCP user guide unique-ai:unique-ai:mcpkb
Documents external-assistant search/read with user permissions, citations and optional KB scope restrictions.
Connecting; access; limitations · documented · Source date 2026-10-05 · Retrieved 2026-10-21
API model usage tracking unique-ai:unique-ai:api-usage
Documents public API/SDK model-call usage tracking; some other internal-service calls are outside scope and REST usage retrieval is planned.
Coverage; flags; limitations · documented · Source date not stated · Retrieved 2026-10-21
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
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
Translator space unique-ai:unique-ai:translation
Documents beta Office-file/text translation with glossary pre/postprocessing and potential layout disruption.
Beta; glossary; document types; limitations · documented · Source date 2026-05-06 · Retrieved 2026-10-21
Voice administration unique-ai:unique-ai:voice
Requires Azure AI Speech Services and describes potential public/backbone audio routing.
Dependencies; networking; limitations · documented · Source date 2026-05-07 · Retrieved 2026-10-21
Unique data processing addendum unique-ai:unique-ai:dpa
Public DPA covers hosted chat/recordings, lists Microsoft, Swiss storage, return/deletion, confidentiality and ten-year audit-log retention.
Sections 2-3, 6-7; Appendices A-B; July 2025 footer · documented · Source date not stated · Retrieved 2026-10-21
Using Voice unique-ai:unique-ai:voice-user
Documents prompt dictation with EN/DE/FR/IT, immediate audio discard and dialect/recognition limitations.
Prompt dictation; privacy note; supported languages · documented · Source date not stated · Retrieved 2026-10-21
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
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
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
Single sign-on setup unique-ai:unique-ai:sso
Documents Zitadel SSO across deployment types, group claims and automatic SAML account creation/update.
Entra ID OIDC; SAML; managed-tenant setup · documented · Source date 2026-05-07 · Retrieved 2026-10-21
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
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
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
SCIM provisioning unique-ai:unique-ai:scim
Documents Unique SCIM endpoint/key for IdP user/group synchronisation.
Prerequisites and Entra setup · documented · Source date 2026-05-07 · Retrieved 2026-10-21
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
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
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
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
Analytics interface unique-ai:unique-ai:analytics
Documents adoption reports, detailed chat/model/tool exports and randomised or stable pseudonymous identifiers.
Reports; anonymisation; detailed interactions · documented · Source date 2026-09-03 · Retrieved 2026-10-21
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
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
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
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
Audit logs unique-ai:unique-ai:audit
Defines privileged API event logging with self-service exclusions, deployment-specific retention and request-based export.
Scope; exclusions; default basic mode; retention and export · documented · Source date 2026-05-07 · Retrieved 2026-10-21
Security Events Export unique-ai:unique-ai:security-export
Documents Single-Tenant-only Azure Activity/Defender Event Hub export with seven-day replay, client-region selection and consumption cost.
Availability; delivered events; retention; cost · documented · Source date not stated · Retrieved 2026-10-21
Audit logs unique-ai:unique-ai:review2-audit
API audit-event guide specifies basic/verbose modes and MT 90-day/ST five-year operational retention. It does not reconcile those event classes to DPA audit logs or a customer-specific contractual override.
About audit logs; modes; Single and Multi Tenant Clients · documented · Source date 2026-05-07 · Retrieved 2026-10-21
Unique data processing addendum unique-ai:unique-ai:review2-dpa
The public July 2025 DPA specifies ten-year audit logs and CH storage, while Appendix A lists Microsoft and a client-chosen location. No signed current provider schedule, retention override or contract-precedence mapping was inspected.
Sections 3.15 and 6.1; Appendix A; July 2025 footer · documented · Source date not stated · Retrieved 2026-10-21
Retention and deletion at Unique unique-ai:unique-ai:review2-retention
Hosted-only policy separates ordinary post-termination content retention, recoverable files and backups and permits contract customisation. Its log/key statements are not reconciled to audit-event/DPA/key-management scopes.
Purpose; Data retention; Deletion after termination; Backups; Encryption in Place · documented · Source date 2026-05-04 · Retrieved 2026-10-21
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
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
Data leakage prevention integration unique-ai:unique-ai:dlp
Describes customer-operated HTTPS/DLP proxy and post-chat analytics scanning rather than a default native PII-redaction feature.
Proxy; analytics API; compatibility · documented · Source date 2026-05-07 · Retrieved 2026-10-21
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
Single-tenant security architecture unique-ai:unique-ai:single
Documents separate Azure landing zone, network restrictions, retention and Unique-managed infrastructure keys.
Azure resources; SSO; encryption; monitoring · documented · Source date 2026-05-28 · Retrieved 2026-10-21
Terms and conditions administration unique-ai:unique-ai:policy
Documents first-login acceptance, custom terms under an MSA and version/agreement export through GraphQL.
First-login acceptance; MSA condition; API export · documented · Source date 2026-05-07 · Retrieved 2026-10-21
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
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
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
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
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
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
Single-tenant key management unique-ai:unique-ai:review2-keys
May 2026 key guide distinguishes imported customer-generated keys held by Unique from customer-exclusive key control via self-hosting. Its MT/ST CMK statement differs from the hosted retention page; actual MT configuration is unverified.
Infrastructure-only scope; PMK; BYOK/CYOK/HYOK; Summary · documented · Source date 2026-05-27 · Retrieved 2026-10-21
Single-tenant security architecture unique-ai:unique-ai:review2-single
Single-tenant guide documents separate landing zone, WAF/IP controls and Unique-managed encryption. Its 2048-bit RSA-HSM description differs from the hosted retention page; this does not establish an exact current key design.
Overview; Encryption; Data classification · documented · Source date 2026-05-28 · Retrieved 2026-10-21
Compliance Layer 3.0 unique-ai:unique-ai:review2-compliance
The deployment matrix documents CH North multitenant hosting and selectable single/client-hosted regions, with deployment-specific controls. These are options, not proof of a particular customer contract or current key configuration.
Digital Sovereignty; Feature overview matrix · documented · Source date 2026-05-27 · Retrieved 2026-10-21
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
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
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
Unique installation models unique-ai:unique-ai:install
Enumerates multi-tenant, single-tenant, customer-managed and on-premise deployments.
Overview · documented · Source date 2025-08-06 · Retrieved 2026-10-21
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
Unique terms of service unique-ai:unique-ai:terms
Describes a sales-conversation service with Order Form subscription fees, nonrenewal notice, recording export and proprietary rights; applicability to the current AI MSA needs confirmation.
Sections 1-2, 4-6, 11, 17-18 · documented · Source date not stated · Retrieved 2026-10-21
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
Chat data redaction and retention unique-ai:unique-ai:redaction
Documents scheduled clearing of chat content and workspace records, with separate upload/KB retention rules.
What is cleared; exclusions; administrator settings · documented · Source date 2026-10-18 · Retrieved 2026-10-21
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
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
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
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
Unique AI contact unique-ai:unique-ai:contact
Lists Unique AI AG in Zürich, Unique Germany GmbH in Berlin and other regional entities.
Office addresses · documented · Source date not stated · Retrieved 2026-10-21
Unique AI governance framework: contract access unique-ai:unique-ai:review2-governance
The current governance framework says legal contracts and end-user T&Cs are available on request; the public page does not expose platform subscription or component licence clauses.
Individual standards; Legal contracts; End-User Terms and Conditions · documented · Source date 2026-04-12 · Retrieved 2026-10-21
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
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
Unique AI trust centre unique-ai:unique-ai:trust
Describes CH Azure storage separately from globally routed inference and claims ISO/SOC assurances, with differing SOC types in the FAQ.
Enterprise security; compliance standards; FAQ · vendor-claimed · Source date not stated · Retrieved 2026-10-21
Unique ISO/IEC 42001 certificate unique-ai:unique-ai:iso42001
TÜV SÜD certificate covers development/deployment SaaS for financial services using pretrained foundation models or client-provided models, valid to 6 March 2028.
One page; registration 99 420 00001; scope and dates · certificate-verified · Source date 2025-03-07 · Retrieved 2026-10-21
Issuer: TÜV SÜD South Asia Private Limited. Scope: Unique AG, Stockerstr.34, Zurich. Development and deployment of SaaS for financial-services clients based on pretrained AI foundation models using Azure OpenAI or client-provided models, including client on-premise models.. Valid 2025-03-07 to 2028-03-06
ISO Certifications and current downloads unique-ai:unique-ai:review2-iso-docs
The ISO documentation links 2026 English/German ATTESTA ISO27001 and ISO9001 renewals, plus the 2025 ISO42001 certificate; ISO27001 SoA requires an NDA.
Certificate ISO27001; ISO9001; ISO42001; Statement of Applicability · documented · Source date 2026-08-05 · Retrieved 2026-10-21
Unique AG ISO27001 ATTESTA 2026 renewal unique-ai:unique-ai:review2-iso27001
Inspected ATTESTA ISO27001:2022 renewal for Unique AG, registration 223-06-018.I, issued 10 June 2026 after 4 June surveillance, valid until 31 May 2029. The certificate-linked public register lists the same number and expiry.
One-page 2026 English certificate; scope, registration, surveillance, printed expiry · certificate-verified · Source date 2026-06-10 · Retrieved 2026-10-21
Issuer: ATTESTA Schweizer Zertifizierungsgesellschaft AG. Scope: Unique AG, Stockerstrasse 34, 8002 Zürich: development, operation, trading and distribution of software and provision of IT/information-technology services; ISO27001:2022 information security management. Valid from an unstated date to 2029-05-31
Unique AG ISO9001 ATTESTA 2026 renewal unique-ai:unique-ai:review2-iso9001
Inspected ATTESTA ISO9001:2015 renewal for Unique AG, registration 223-06-017.Q, issued 10 June 2026 after 4 June surveillance, valid until 31 May 2029. The certificate-linked public register lists the same number and expiry.
One-page 2026 English certificate; scope, registration, surveillance, printed expiry · certificate-verified · Source date 2026-06-10 · Retrieved 2026-10-21
Issuer: ATTESTA Schweizer Zertifizierungsgesellschaft AG. Scope: Unique AG, Stockerstrasse 34, 8002 Zürich: development, operation, trading and distribution of software and provision of IT/information-technology services; ISO9001:2015 quality management. Valid from an unstated date to 2029-05-31
Certificate-linked public register: Unique AG unique-ai:unique-ai:review2-iso-register
Public certificate-linked register lookup for Unique AG lists registrations 223-06-018.I and 223-06-017.Q, Zurich, software/IT scope and expiry 31 May 2029. Standard/status text fields are blank; certificate PDFs supply the standards.
Unique AG result rows; registration, scope, expiry · documented · Source date not stated · Retrieved 2026-10-21
SOC2 Type2: chronology and report access unique-ai:unique-ai:review2-soc
The dedicated SOC page explains Type1 in December 2023 followed by Type2 in January 2025; audit report and certificate are available only on request after NDA. Auditor, service scope and actual reporting period were not publicly inspected.
SOC2 Type2 timeline; Certificates/report access · vendor-claimed · Source date 2026-04-12 · Retrieved 2026-10-21
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
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
Terms and Conditions Administration unique-ai:unique-ai:review2-terms-admin
Current platform T&C administration refers to a customer MSA and gated admin export; it does not publish the vendor platform agreement or determine subscription/IP/branding clauses.
Overview; MSA exceptions; Modifying/Exporting Terms and Conditions · documented · Source date 2026-05-08 · Retrieved 2026-10-21
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
Unique AI platform unique-ai:unique-ai:platform
Markets a modular finance platform with governed connectors, frontend, financial agents and APIs.
Frontend, financial agents, MCP Hub; deployment section · vendor-claimed · Source date not stated · Retrieved 2026-10-21
ECB euro foreign exchange reference rates, 20 October 2026 unique-ai:unique-ai:ecb-fx
ECB records EUR 1 = USD 1.1215 and CHF 0.9237 on 20 October 2026; derived USD to EUR is 1/1.1215 and CHF to EUR is 1/0.9237.
Cube time="2026-10-20": USD and CHF · documented · Source date 2026-10-20 · Retrieved 2026-10-21
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
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
Unique AI governance framework: contract access unique-ai:unique-ai:review2-governance-20261026
The current governance framework says legal contracts and end-user T&Cs are available on request; the public page does not expose platform subscription or component licence clauses.
Individual standards; Legal contracts; End-User Terms and Conditions · documented · Source date 2026-04-12 · Retrieved 2026-10-26
Unique public reference repository licence unique-ai:unique-ai:reference-licence-20261026
The public repository defaults to Unique License v1 unless an explicit licence says otherwise; commercial use, distribution and modifications require prior approval. The default is restricted source-available, not an OSI open-source licence.
LICENSE, repository-wide disclaimer and exceptions · documented · Source date not stated · Retrieved 2026-10-26
Unique License v1 unique-ai:unique-ai:unique-licence-v1-20261026
The published full licence permits personal noncommercial use and requires prior written approval for commercial use, distribution and modification, with separate component-licence exceptions. Swiss law and Zurich venue are specified.
Grant, Restrictions, Open Source Components, Governing Law · documented · Source date 2024-09-24 · Retrieved 2026-10-26
Unique Python SDK MIT licence unique-ai:unique-ai:sdk-licence-20261026
The Python SDK directory has an explicit MIT licence permitting commercial use and modification subject to notice requirements; this exception does not license the hosted platform.
unique_sdk/LICENSE, explicit component exception · documented · Source date not stated · Retrieved 2026-10-26
Unique SDK package metadata unique-ai:unique-ai:sdk-package-20261026
At the pinned October 23 repository commit, unique_sdk package metadata declares MIT, consistent with its component licence. Repository/package version is not treated as the hosted release date.
project name/version and licence · documented · Source date not stated · Retrieved 2026-10-26
Terms and Conditions Administration unique-ai:unique-ai:review2-terms-admin-20261026
Current platform T&C administration refers to a customer MSA and gated admin export; it does not publish the vendor platform agreement or determine subscription/IP/branding clauses.
Overview; MSA exceptions; Modifying/Exporting Terms and Conditions · documented · Source date 2026-05-08 · Retrieved 2026-10-26
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
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
Enterprise support unique-ai:unique-ai:support
Provides public multitenant status link, enterprise email and a contract-specific dedicated support model.
Contact; dedicated support model; hours · documented · Source date not stated · Retrieved 2026-10-21
Unique public system status unique-ai:unique-ai:status
Public status page displays service/API/collector components and historical uptime panels; dedicated environments are outside the documented status scope.
Component and 90-day uptime panels · documented · Source date not stated · Retrieved 2026-10-21
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
Unique AI finance platform unique-ai:unique-ai:homepage
Markets embedded experts and structured training programmes for finance users and IT.
Forward-Deployed Engineers and training section · vendor-claimed · Source date not stated · Retrieved 2026-10-21
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