Skip to content

Agent-readable comparison

Cohere North vs Omnifact

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

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

Same facts as Markdown and JSON. Methodology.

Models

MOD-01 Model catalogue and providers

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Manual selection spans OpenAI, Anthropic, Google and Mistral with EU/direct routes and tier controls.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise managed model catalogue; customer API keys and custom/self-hosted endpoints require Enterprise BYOK; add_ons=Enterprise BYOK for custom provider endpoints; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • current_models: Public text catalogue: GPT6Sol/Luna,5.6Sol/Terra/Luna,5.5,5.4/mini,5.2,5.1,5/mini/nano,4.1/mini/nano,4o/mini,4,3.5; Claude Opus5.5/5/4.8/4.7/4.6/4.5/4.1/4, Sonnet5.5/5/4.6/4.5/4, Haiku5.5/4.5; Gemini4Argon,3.8/3.7/3.6/3.5Flash,3.5Flash Lite,3.1Pro/Flash Lite,3Pro,2.5Pro/Flash,2.0Flash/Flash Lite; Mistral Medium3.5/3, Large3, Small4, Nemo, Ministral8B, Pixtral Large, Codestral, Devstral Small. Each is subject to admin enablement, tier, route and provider availability; not independently tested in picker.
  • multimodal_input: Image input only for capable selected models; experimental audio uploads need audio-capable models. Extracted document text and code tools are separate paths; no complete model-by-model native audio matrix was established.
  • Unverified auto_routing: No documented automatic cross-model routing strategy or chosen-model display after automatic routing was established; autonomous tool selection is separate from model routing.
  • providers Which model providers are available? [partial]: Pro/Enterprise managed provider options include OpenAI/AzureOpenAI, Anthropic, Google/Vertex and Mistral subject to workspace configuration. Customer API keys, custom OpenAI-compatible endpoints and self-hosted model connections require Enterprise BYOK. Optional DPA-listed Groq is not treated as a currently selectable managed model. Sources: omnifact:omnifact:providers-rev2, omnifact:omnifact:pricing-rev2, omnifact:omnifact:models.
  • current_models Which current models are selectable on this plan? [partial]: Public text catalogue: GPT6Sol/Luna,5.6Sol/Terra/Luna,5.5,5.4/mini,5.2,5.1,5/mini/nano,4.1/mini/nano,4o/mini,4,3.5; Claude Opus5.5/5/4.8/4.7/4.6/4.5/4.1/4, Sonnet5.5/5/4.6/4.5/4, Haiku5.5/4.5; Gemini4Argon,3.8/3.7/3.6/3.5Flash,3.5Flash Lite,3.1Pro/Flash Lite,3Pro,2.5Pro/Flash,2.0Flash/Flash Lite; Mistral Medium3.5/3, Large3, Small4, Nemo, Ministral8B, Pixtral Large, Codestral, Devstral Small. Each is subject to admin enablement, tier, route and provider availability; not independently tested in picker. Sources: omnifact:omnifact:models.
  • user_choice Can users pick the model per chat? [supported]: Picker changes before/within a conversation and shows provider logo, model name and region flag. Reasoning effort has Low/Medium/High/Extra High depending on model. Sources: omnifact:omnifact:select.
  • 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. No documented automatic cross-model routing strategy or chosen-model display after automatic routing was established; autonomous tool selection is separate from model routing.
  • multimodal_input Which models accept images, audio or files? [partial]: Image input only for capable selected models; experimental audio uploads need audio-capable models. Extracted document text and code tools are separate paths; no complete model-by-model native audio matrix was established. Sources: omnifact:omnifact:files, omnifact:omnifact:groups-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:providers-rev2, omnifact:omnifact:dpa-rev2, omnifact:omnifact:models, omnifact:omnifact:select, omnifact:omnifact:files, omnifact:omnifact:groups-rev2, omnifact:omnifact:pricing-rev2.

MOD-02 Model freshness

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Dated model/feature changelog exists; exact release lag and fixed deprecation policy are unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • Unverified release_lag_days, deprecation_notice, version_pinning: Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established.
  • release_lag_days What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? Unknown. Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established.
  • changelog Is there a dated public model changelog? [supported]: Monthly release notes updated2026-10-20; individual feature posts date Gemini4Argon October 13, Haiku5.5 October 8, Sonnet5.5 September 28 and GPT6/Opus5.5 September 22. Sources: omnifact:omnifact:changes, omnifact:omnifact:blog.
  • deprecation_notice How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? Unknown. Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established.
  • version_pinning Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unknown. Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:changes, omnifact:omnifact:blog.

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

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Enterprise BYOK supports own provider accounts and custom OpenAI-compatible connections.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise BYOK, customer provider contracts; add_ons=Customer provider charges separate; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • own_cloud_contract: Supported environments include Azure OpenAI, Vertex Anthropic/Vertex Google; model settings mention AWSBedrock via custom endpoints. Customer deployment/contract setup details not fully specified.
  • byo_pricing: BYOK moves model costs to customer account/negotiated rates; Enterprise licence adjustment is quote-only.
  • Unverified byo_restrictions: No complete BYOK-specific feature failure/parity matrix or public licence discount was established.
  • own_api_keys Can the customer use its own provider API keys? [supported]: Enterprise only; connects own provider API keys, charges provider account and bypasses standard Omnifact rate limits. Sources: omnifact:omnifact:providers.
  • own_cloud_contract Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Supported environments include Azure OpenAI, Vertex Anthropic/Vertex Google; model settings mention AWSBedrock via custom endpoints. Customer deployment/contract setup details not fully specified. Sources: omnifact:omnifact:providers, omnifact:omnifact:model-settings.
  • custom_endpoint Can an admin add any OpenAI-compatible endpoint? [supported]: Custom provider supports OpenAI-compatible endpoints; self-hosted connection enabled with support. Sources: omnifact:omnifact:providers, omnifact:omnifact:terms.
  • byo_pricing Does BYO change the licence price? [partial]: BYOK moves model costs to customer account/negotiated rates; Enterprise licence adjustment is quote-only. Sources: omnifact:omnifact:providers.
  • byo_restrictions Which features stop working with BYO? [unknown]: Which features stop working with BYO? Unknown. No complete BYOK-specific feature failure/parity matrix or public licence discount was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:providers, omnifact:omnifact:model-settings, omnifact:omnifact:terms.

MOD-04 Local and self-hosted models

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

Cohere North

Agent cross-checked Support: partial

North chat and retrieval models can run in customer infrastructure.

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Enterprise can integrate customer-hosted models; embedding and tool parity remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise self-hosted model connection; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • vendor_hosted_open_models: Mistral family appears with EU flags; the operating party and infrastructure for every open-weight route are not fully mapped. It is not proof of Swiss hosting.
  • Unverified self_hosted_embeddings, feature_parity: No documented customer-hosted embedding route or exhaustive feature-parity matrix was established; on-premise platform availability alone does not prove either.
  • self_hosted_chat Can chat use a customer-hosted model? [supported]: Enterprise lists self-hosted LLMs; terms6.4 requires coordination with support and custom provider endpoints are documented. Sources: omnifact:omnifact:pricing, omnifact:omnifact:providers, omnifact:omnifact:terms.
  • self_hosted_embeddings Can retrieval use customer-hosted embeddings? [unknown]: Can retrieval use customer-hosted embeddings? Unknown. No documented customer-hosted embedding route or exhaustive feature-parity matrix was established; on-premise platform availability alone does not prove either.
  • feature_parity Which features fail with self-hosted models? [unknown]: Which features fail with self-hosted models? Unknown. No documented customer-hosted embedding route or exhaustive feature-parity matrix was established; on-premise platform availability alone does not prove either.
  • vendor_hosted_open_models Does the vendor host open-weight models in EU/CH? [partial]: Mistral family appears with EU flags; the operating party and infrastructure for every open-weight route are not fully mapped. It is not proof of Swiss hosting. Sources: omnifact:omnifact:models.

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

Omnifact

Agent cross-checked Support: partial

Groups add model-tier/capability permissions while organization settings control concrete models/routes.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • model_allowlist_by_group: Groups add Base/Standard/Premium-tier and US-hosted-model access. Everyone and overlapping groups union grants; no deny overrides. Concrete model enablement is organization-wide, not an arbitrary per-group model list.
  • data_bound_models: Admins disable providers/models globally; DPA annexes also describe per-Space provider approval. No tested classifier routes knowledge content to distinct allowed models automatically.
  • default_model: October notes set Haiku5.5 as fast default for new organizations. Image default and Published Space model are configurable; universal organization text-default setting not established.
  • user_limits: Plan-determined per-user24-hour rolling message quotas show remaining count/reset. Numeric plan quotas are not public; pooled credit and page limits are separate.
  • model_allowlist_by_group Can admins limit models per group? [partial]: Groups add Base/Standard/Premium-tier and US-hosted-model access. Everyone and overlapping groups union grants; no deny overrides. Concrete model enablement is organization-wide, not an arbitrary per-group model list. Sources: omnifact:omnifact:groups, omnifact:omnifact:model-settings.
  • data_bound_models Can admins restrict which models receive connector or knowledge content? [partial]: Admins disable providers/models globally; DPA annexes also describe per-Space provider approval. No tested classifier routes knowledge content to distinct allowed models automatically. Sources: omnifact:omnifact:model-settings, omnifact:omnifact:dpa.
  • default_model Can admins set the default model? [partial]: October notes set Haiku5.5 as fast default for new organizations. Image default and Published Space model are configurable; universal organization text-default setting not established. Sources: omnifact:omnifact:changes, omnifact:omnifact:model-settings, omnifact:omnifact:published.
  • user_limits What per-user message or token limits apply, and are they published? [partial]: Plan-determined per-user24-hour rolling message quotas show remaining count/reset. Numeric plan quotas are not public; pooled credit and page limits are separate. Sources: omnifact:omnifact:chat.
  • limit_behaviour What happens when a limit is reached? [supported]: Daily message exhaustion disables new sends until reset. Monthly credit exhaustion greys premium models and chat falls back; Gateway returns credit error for all models without fallback. Sources: omnifact:omnifact:chat, omnifact:omnifact:limits, omnifact:omnifact:gateway.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:groups, omnifact:omnifact:model-settings, omnifact:omnifact:dpa, omnifact:omnifact:changes, omnifact:omnifact:published, omnifact:omnifact:chat, omnifact:omnifact:limits, omnifact:omnifact:gateway.

Company knowledge

KNOW-01 Files in chat

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Broad attachment formats and published limits exist; indexing uses OCR/chunks while workbook fidelity is untested.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • limits: 10 attachments/message;8000 text characters/message;20MB/image;25MB/audio. Space Uploaded Files FAQ says no individual/aggregate file-size limit; ordinary document/chat count ceilings not fully specified.
  • ocr: Space upload pipeline documents Apache Tika OCR for scanned PDFs/images; no accuracy fixture.
  • spreadsheets: Spreadsheet inputs can be processed with executed Python and native XLSX formulas; structure/merged cells/formula preservation not tested.
  • full_vs_chunked: Space documents are extracted/chunked/embedded and relevant sections retrieved with progress/citation displays. Exact direct-attachment full-text thresholds were not established.
  • formats Which formats are accepted? [supported]: PDF, Word, Excel, Power Point, Open Document text/presentation, TXT, JSON, Markdown, CSV, SVG; images PNG/JPEG/Web P/HEIC/HEIF/AVIF/BMP/GIF/ICO/TIFF/SVG; audio examples MP3/WAV/AAC/FLAC with group/model restriction. Sources: omnifact:omnifact:files.
  • limits What size and count limits apply per file and chat? [partial]: 10 attachments/message;8000 text characters/message;20MB/image;25MB/audio. Space Uploaded Files FAQ says no individual/aggregate file-size limit; ordinary document/chat count ceilings not fully specified. Sources: omnifact:omnifact:files, omnifact:omnifact:uploads.
  • ocr Are scanned PDFs read? [partial]: Space upload pipeline documents Apache Tika OCR for scanned PDFs/images; no accuracy fixture. Sources: omnifact:omnifact:uploads.
  • spreadsheets Are Excel tables read with structure intact? [partial]: Spreadsheet inputs can be processed with executed Python and native XLSX formulas; structure/merged cells/formula preservation not tested. Sources: omnifact:omnifact:documents.
  • full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [partial]: Space documents are extracted/chunked/embedded and relevant sections retrieved with progress/citation displays. Exact direct-attachment full-text thresholds were not established. Sources: omnifact:omnifact:uploads, omnifact:omnifact:retrieval.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:files, omnifact:omnifact:uploads, omnifact:omnifact:documents, omnifact:omnifact:retrieval.

KNOW-02 Knowledge bases and shared collections

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Spaces persist and share uploaded/connected knowledge. The applicable Pro page quota remains unknown; Enterprise advertises unlimited pages.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro up to50users and Enterprise Spaces; actual Pro page quota unverified; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • Pro page quota is excluded from verified limits until the applicable offer is identified. Connected-source and manual-upload accounting are separate.
  • persistent_collections Can users keep document collections across chats? [supported]: Uploaded Files and connected folders persist in a Space for multiple conversations; message attachments remain specific to their conversation. Sources: omnifact:omnifact:spaces.
  • sharing_scope Can collections be shared with users, groups or the whole organisation? [supported]: Organization users/groups including Everyone; Admin/Editor manage, Member queries. Groups receive view-only membership; edit grants are individual. Sources: omnifact:omnifact:share.
  • size_limits What are the collection limits? [partial]: Enterprise pricing advertises unlimited knowledge pages. Actual Pro page quota is unknown because pricing says25000 while Billing says5000; neither is asserted as an independently applicable limit. The Connected Sources documentation says synced files currently do not count against the manual-upload page quota. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing, omnifact:omnifact:sync.
  • assistant_binding Can collections be bound to an assistant? [supported]: Space agent uses its own instructions and isolated Uploaded Files/Connected Sources knowledge. Sources: omnifact:omnifact:spaces.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:spaces, omnifact:omnifact:share, omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing, omnifact:omnifact:sync.

KNOW-03 Enterprise connectors

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Cloud document sync and live first-party MCP integrations cover different system/action scopes.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise cloud document connectors; separately run API-enabled XWiki importer documented at pinned revision; add_ons=Customer-run XWiki sync tool; API access and source credentials required; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • XWiki behavior is documented in a pinned README, with no support/guarantee. It was not implementation-inspected or executed in this pass.
  • microsoft_365 Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: SharePoint, OneDrive Business and personal OneDrive document access/sync. No verified native Outlook/Teams connector in current catalogue. Sources: omnifact:omnifact:integrations.
  • google_workspace Which Google sources are connected? [supported]: Drive document sync plus MCP Drive, Docs, Sheets, Slides, Gmail, Calendar, Chat tools. Sources: omnifact:omnifact:integrations.
  • atlassian Confluence and Jira? [supported]: Atlassian official MCP for Jira/Confluence search and updates. Sources: omnifact:omnifact:directory.
  • other_systems Which other business systems? [partial]: Slack, Zoom, Notion, Hub Spot, Zendesk, Box, Egnyte, Asana, Click Up, Linear, Airtable, Canva, Miro, Lucid, Stripe, Pay Pal, Git Hub/Git Lab, Sentry, PostHog, Supabase, Neon, Webflow, Todoist; official XWiki importer is separate unsupported CLI. Sources: omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2.
  • on_prem_sources Can on-prem file shares or databases be connected? [partial]: Custom MCP can expose internal systems but cloud deployment blocks private IP/loopback/subnets by default. XWiki REST importer runs where customer executes it; native file-share/database network support is not established. Sources: omnifact:omnifact:mcp-rev2, omnifact:omnifact:xwiki-sync-rev2.
  • connector_provider Who builds and maintains each connector? [partial]: Catalogue MCP servers are supplied by listed software vendors; Omnifact manages installation/governance. Document connectors and XWiki tool are Omnifact; support scope varies. Sources: omnifact:omnifact:directory, omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:integrations, omnifact:omnifact:directory, omnifact:omnifact:xwiki-sync-rev2, omnifact:omnifact:mcp-rev2.

KNOW-04 Permission-aware retrieval

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Personal OAuth tools honor source-account rights; synced content is scoped to Space membership, without a verified per-user ACL mirror.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • source_permissions_respected: OAuth MCP executes only within each user account rights. Space indexed knowledge is available under shared Space membership; per-recipient source ACL enforcement was not established.
  • enforcement_point: Live OAuth uses source account access. Space retrieval is indexed and checks Space membership; this is not documented as a source-ACL recheck on every query.
  • revocation_delay: Removing Space/group membership immediately revokes those grants; source document/ACL revocation timing beyond deletion sync was not tested.
  • admin_scope_controls: Space admins select connected folders; organization enables/removes connectors and tools. No sensitivity-label classifier was established.
  • Unverified sensitivity_labels: No cross-group source-ACL/revocation fixture or Microsoft Purview sensitivity-label implementation was established.
  • source_permissions_respected Are source permissions enforced per user? [partial]: OAuth MCP executes only within each user account rights. Space indexed knowledge is available under shared Space membership; per-recipient source ACL enforcement was not established. Sources: omnifact:omnifact:mcp, omnifact:omnifact:retrieval, omnifact:omnifact:sync.
  • enforcement_point Does the source system, a mirrored index or nothing enforce them? [partial]: Live OAuth uses source account access. Space retrieval is indexed and checks Space membership; this is not documented as a source-ACL recheck on every query. Sources: omnifact:omnifact:mcp, omnifact:omnifact:retrieval, omnifact:omnifact:sync.
  • revocation_delay How quickly does a removed permission take effect? [partial]: Removing Space/group membership immediately revokes those grants; source document/ACL revocation timing beyond deletion sync was not tested. Sources: omnifact:omnifact:share, omnifact:omnifact:groups.
  • admin_scope_controls Can admins exclude sites, folders or labels? [partial]: Space admins select connected folders; organization enables/removes connectors and tools. No sensitivity-label classifier was established. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations.
  • sensitivity_labels Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? Unknown. No cross-group source-ACL/revocation fixture or Microsoft Purview sensitivity-label implementation was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:mcp, omnifact:omnifact:retrieval, omnifact:omnifact:sync, omnifact:omnifact:share, omnifact:omnifact:groups, omnifact:omnifact:integrations.

KNOW-05 Freshness and sync model

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Connected documents are indexed on a five-minute cycle; live MCP queries remain separate.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise cloud document connectors; separately run API-enabled XWiki importer documented at pinned revision; add_ons=Customer-run XWiki sync tool; API access and source credentials required; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • XWiki behavior is documented in a pinned README, with no support/guarantee. It was not implementation-inspected or executed in this pass.
  • live_or_indexed Is content searched live or copied into an index? [supported]: Connected Sources index selected cloud files; MCP tools query source systems live. XWiki CLI uploads converted Markdown on customer-run sync. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2.
  • sync_interval How often does an index refresh? [supported]: Connected Sources checks every five minutes; initial indexing may take minutes. XWiki tool is one-shot and requires external cron/systemd/Kubernetes scheduling. Sources: omnifact:omnifact:sync, omnifact:omnifact:xwiki-sync-rev2.
  • deletion_propagation How quickly does a deleted document disappear? [supported]: Cloud deletions removed on next five-minute cycle; disconnect permanently removes that source index from Space. XWiki importer tracks deleted/excluded pages on next run. Sources: omnifact:omnifact:sync, omnifact:omnifact:xwiki-sync-rev2.
  • index_location Where is indexed content stored? [partial]: DPA maps prefilter files/indexing to Azure Saa S Germany/Frankfurt storage; model embeddings/summaries have provider-dependent paths not fully mapped. Sources: omnifact:omnifact:dpa-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2, omnifact:omnifact:dpa-rev2.

KNOW-06 Grounding and retrieval quality

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Passage citations and controllable strict grounding are documented; retrieval quality remains unmeasured.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • no_answer_behaviour: Space instructions can require answers only from uploaded documents and explicit missing-information statements; default guaranteed abstention is not established.
  • Unverified citation_accuracy, cross_language, observed_accuracy: No DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run.
  • citations Are answers linked to specific sources? [supported]: Source references identify uploaded document or cloud filename/provider and direct original link; progress shows retrieved document count. Sources: omnifact:omnifact:retrieval, omnifact:omnifact:sync.
  • citation_accuracy Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run.
  • 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 DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run.
  • no_answer_behaviour Does it say when the corpus has no answer? [partial]: Space instructions can require answers only from uploaded documents and explicit missing-information statements; default guaranteed abstention is not established. Sources: omnifact:omnifact:retrieval.
  • observed_accuracy How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:retrieval, omnifact:omnifact:sync.

KNOW-07 Memory and personal context

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Persistent personal instructions exist; automatic cross-chat memory was not established.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • user_memory_controls: Users edit/remove their supplied personalization fields. This is not documentation of viewing/deleting automatically learned memories.
  • Unverified cross_chat_memory, admin_memory_controls: No automatic fact-memory feature or administrator memory-disable setting was established in account, Space and release documentation. Conversation history is not itself cross-chat memory.
  • custom_instructions Can users set persistent instructions? [supported]: Personalization stores role/context and response tone/style/format and sends them in every conversation. These fields bypass the Privacy Filter. Sources: omnifact:omnifact:account.
  • cross_chat_memory Does the product remember facts across chats? [unknown]: Does the product remember facts across chats? Unknown. No automatic fact-memory feature or administrator memory-disable setting was established in account, Space and release documentation. Conversation history is not itself cross-chat memory.
  • user_memory_controls Can users view, edit and delete memories? [partial]: Users edit/remove their supplied personalization fields. This is not documentation of viewing/deleting automatically learned memories. Sources: omnifact:omnifact:account.
  • admin_memory_controls Can admins turn memory off? [unknown]: Can admins turn memory off? Unknown. No automatic fact-memory feature or administrator memory-disable setting was established in account, Space and release documentation. Conversation history is not itself cross-chat memory.

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

Assistants and agents

AGT-01 Custom assistants

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Space agents combine custom instructions, knowledge and shared access with starter prompts.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • creator_permissions: Member role includes Space creation; group permissions control file/code/features. An explicit deny-Space-creation privilege was not established.
  • prompt_library: Space Starters/template previews and example prompts provide shared starting points; a separate centrally managed standalone prompt-library product was not established.
  • create_assistants Can users create assistants with instructions, knowledge and tools? [supported]: Members create Spaces, become Space Admin and set instructions/examples/knowledge. Workspace-level tool availability is governed separately. Sources: omnifact:omnifact:create, omnifact:omnifact:users.
  • creator_permissions Can admins limit who creates them? [partial]: Member role includes Space creation; group permissions control file/code/features. An explicit deny-Space-creation privilege was not established. Sources: omnifact:omnifact:users, omnifact:omnifact:groups.
  • sharing_scope Can assistants be shared with users, groups or everyone? [supported]: Users or organization groups including Everyone; group membership grants Member only. Sources: omnifact:omnifact:share.
  • catalogue Is there an internal assistant directory? [supported]: All/Favorite Spaces directory shows accessible agents with pin/favorite navigation. Sources: omnifact:omnifact:spaces.
  • prompt_library Are shared prompt templates available? [partial]: Space Starters/template previews and example prompts provide shared starting points; a separate centrally managed standalone prompt-library product was not established. Sources: omnifact:omnifact:create, omnifact:omnifact:changes.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:create, omnifact:omnifact:users, omnifact:omnifact:groups, omnifact:omnifact:share, omnifact:omnifact:spaces, omnifact:omnifact:changes.

AGT-02 Tools, actions and MCP

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Remote MCP has explicit tool policies, personal OAuth and teamwide static-credential access.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise managed remote MCP; workspace-admin setup and chosen tool policy required; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • Configured policies are documented; initial-discovery defaults remain unknown. Static credentials are shared teamwide as documented and do not provide personal source authorization.
  • Experimental code/output entitlement is unknown; generic Enterprise early-access wording does not identify an eligible Execute code tier.
  • builtin_tools Which tools are built in? [partial]: Web search/browse, Space retrieval, image tools and curated MCP business actions are documented for the scoped workspace. Eligibility for the separate Experimental Execute code and its Python/Office outputs is unknown because the documentation does not map it to Pro or Enterprise. Sources: omnifact:omnifact:web, omnifact:omnifact:retrieval, omnifact:omnifact:images, omnifact:omnifact:documents, omnifact:omnifact:integrations, omnifact:omnifact:groups-rev2.
  • custom_actions Can admins add API actions? [partial]: Admins add custom remote MCP URL and discovered tools. Arbitrary non-MCP REST wrappers require an external server. Sources: omnifact:omnifact:mcp-rev2.
  • mcp_client Can it use remote MCP servers, and with what admin control? [supported]: Remote HTTP MCP supports OAuth, APIkey, Bearer, customheader ornone. Destination validation blocks private/subnet/metadata endpoints by default. Sources: omnifact:omnifact:mcp-rev2.
  • tool_auth Do tools act as the user or as a shared account? [partial]: OAuth requires personal sign-in; static APIkey/Bearer/header/none is central and immediately available teamwide, with no current per-user/group permission for those types. Sources: omnifact:omnifact:mcp-rev2.
  • tool_approval Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins explicitly configure each tool as Always, Approval or Disable. Approval displays the exact request payload with Allow/Deny; later refresh adds new tools disabled. Initial-discovery default is unknown because setup and security sections disagree, so no safe or permissive initial default is asserted. Sources: omnifact:omnifact:mcp-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:web, omnifact:omnifact:retrieval, omnifact:omnifact:images, omnifact:omnifact:documents, omnifact:omnifact:integrations, omnifact:omnifact:mcp-rev2, omnifact:omnifact:groups-rev2.

AGT-03 Web search and deep research

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

Cohere North

Agent cross-checked Support: partial

GA web search and alpha Deep Research are distinct capabilities.

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

Limitations

  • Web search GA; Deep Research alpha.

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

Omnifact

Agent cross-checked Support: partial

Web research is cited and group-controlled; Brave handles public search.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • search_provider: DPA names Brave Software US as web-search processor; exact request-processing datacentre is not specified. Masked-sensitive queries are blocked before search.
  • deep_research: Agents can perform multi-step browsing/research; no separately bounded Deep Research report product or benchmark was established.
  • web_search Is web search available? [supported]: Automatically triggered when needed or explicitly requested; URL reader caps2MB and excludes login/paywall/captcha pages. Sources: omnifact:omnifact:web.
  • admin_toggle Can admins disable it per organisation or group? [supported]: Groups grant web search/browsing additively; remove grant from Everyone/allgroups to disable for targeted users. Sources: omnifact:omnifact:groups.
  • search_provider Which search provider handles queries, and where? [partial]: DPA names Brave Software US as web-search processor; exact request-processing datacentre is not specified. Masked-sensitive queries are blocked before search. Sources: omnifact:omnifact:dpa, omnifact:omnifact:web.
  • deep_research Is multi-step research with a report available? [partial]: Agents can perform multi-step browsing/research; no separately bounded Deep Research report product or benchmark was established. Sources: omnifact:omnifact:changes, omnifact:omnifact:web.
  • web_citations Are web sources cited? [supported]: Numbered citations and original source links accompany search/browse results. Sources: omnifact:omnifact:web.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:web, omnifact:omnifact:groups, omnifact:omnifact:dpa, omnifact:omnifact:changes.

AGT-04 Workflows and automation

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

Cohere North

Agent cross-checked Support: partial

Node workflows support schedules, API invocation and human review.

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

External n8n nodes support automation; a native scheduled workflow builder is not established.

Availability: generally-available · Delivery: official-integration
Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise Published Spaces/Documents API when enabled; AI Gateway nodes require Enterprise; external n8n runs separately; add_ons=External n8n community-node installation; customer-run scheduler/XWiki importer; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • These integrations are pinned README documentation, not executed or source-inspected implementation. A native Omnifact workflow builder/scheduler is not established.
  • workflow_builder Is there a workflow or chain builder? [partial]: Vendor-owned repository publishes n8n community nodes for Gateway completions/model list, Published Space chat and document CRUD. The visual builder is external n8n, not an established native Omnifact builder. Sources: omnifact:omnifact:n8n-nodes-omnifact-rev2.
  • scheduled_tasks Can prompts or assistants run on a schedule? [partial]: XWiki importer explicitly uses external cron/systemd/Kubernetes Cron Job. Native scheduled prompts/agents were not established. Sources: omnifact:omnifact:xwiki-sync-rev2.
  • event_triggers Can external events start a workflow? [unknown]: Can external events start a workflow? Unknown. Native schedule/webhook/event-trigger support was not established from docs, index, changelog and automation integrations.
  • builder_audience Is building aimed at business users, IT or developers? [partial]: n8n community-node/API integrations and CLI sync target technical integrators; Space instructions target business users. Sources: omnifact:omnifact:n8n-nodes-omnifact-rev2, omnifact:omnifact:create.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:n8n-nodes-omnifact-rev2, omnifact:omnifact:xwiki-sync-rev2, omnifact:omnifact:create.

AGT-05 Agentic task execution

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Agentic chat plans tools and streams progress with configurable approvals and Stop.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • visible_steps: Tool/search/retrieval progress and expandable reasoning show activity; exact full execution trace was not independently inspected.
  • side_effect_confirmation: Curated actions wait for confirmation by default; admins choose Always/Approval/Disable. It is not unconditional confirmation for every write under all configurations.
  • stop_control: Send becomes Stop while response generates; clicking halts generation. Cancellation of already committed external side effects is not established.
  • agent_mode Is there an agent mode for multi-step tasks? [supported]: August release rebuilt chat around multi-step agents with automatic tool selection; API optionally enables agentic workflow. Sources: omnifact:omnifact:changes, omnifact:omnifact:api-chat.
  • visible_steps Are steps and tool calls shown? [partial]: Tool/search/retrieval progress and expandable reasoning show activity; exact full execution trace was not independently inspected. Sources: omnifact:omnifact:select, omnifact:omnifact:retrieval, omnifact:omnifact:web.
  • side_effect_confirmation Must the user confirm actions with side effects? [partial]: Curated actions wait for confirmation by default; admins choose Always/Approval/Disable. It is not unconditional confirmation for every write under all configurations. Sources: omnifact:omnifact:directory, omnifact:omnifact:mcp.
  • stop_control Can the user stop a running task? [partial]: Send becomes Stop while response generates; clicking halts generation. Cancellation of already committed external side effects is not established. Sources: omnifact:omnifact:stop.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:changes, omnifact:omnifact:api-chat, omnifact:omnifact:select, omnifact:omnifact:retrieval, omnifact:omnifact:web, omnifact:omnifact:directory, omnifact:omnifact:mcp, omnifact:omnifact:stop.

AGT-06 Programmable access

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

  • Remaining atomic gaps: mcp_server.

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

Omnifact

Agent cross-checked Support: partial

Spaces/document API and Enterprise Gateway use organization keys with different filtering/credit behavior.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact Published Spaces, Public API and Enterprise AI Gateway; version=Public documentation checked 2026-10-21; plan=Pro published Spaces advertised but support enablement needed; Gateway Enterprise opt-in; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • chat_api: Published Spaces chat JSON/SSE with source/agentic headers; Enterprise Gateway OpenAI-compatible completions. Gateway V1 explicitly lacks tool calls and structured outputs.
  • knowledge_api: Document upload, list, inspect, rename/delete with Space scope and async ingestion; no agent-configuration CRUD endpoint established.
  • api_governance: Org-level revocable key, enabled-modelcontrols and shared credit budget apply. Gateway hard-stops on exhaustion; Published Space API disables Privacy Filter. Fine-grained API-key scopes/end-user identities/audit parity were not established.
  • Unverified mcp_server: No first-party Omnifact MCP server exposing platform agents was established; inbound MCP client integrations are distinct.
  • chat_api Is there an API for chat and assistants? [partial]: Published Spaces chat JSON/SSE with source/agentic headers; Enterprise Gateway OpenAI-compatible completions. Gateway V1 explicitly lacks tool calls and structured outputs. Sources: omnifact:omnifact:api-chat, omnifact:omnifact:gateway.
  • knowledge_api Can documents be loaded through an API? [partial]: Document upload, list, inspect, rename/delete with Space scope and async ingestion; no agent-configuration CRUD endpoint established. Sources: omnifact:omnifact:api-docs.
  • api_governance Do audit, budgets and model rules apply to API use? [partial]: Org-level revocable key, enabled-modelcontrols and shared credit budget apply. Gateway hard-stops on exhaustion; Published Space API disables Privacy Filter. Fine-grained API-key scopes/end-user identities/audit parity were not established. Sources: omnifact:omnifact:developer, omnifact:omnifact:gateway, omnifact:omnifact:published, omnifact:omnifact:model-settings.
  • mcp_server Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? Unknown. No first-party Omnifact MCP server exposing platform agents was established; inbound MCP client integrations are distinct.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:api-chat, omnifact:omnifact:gateway, omnifact:omnifact:api-docs, omnifact:omnifact:developer, omnifact:omnifact:published, omnifact:omnifact:model-settings.

Daily work

WORK-01 Clients and access points

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Browser and mobile web access are advertised; native and managed clients remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • mobile_apps: Pricing lists Mobile Web App and model picker adapts to small screens; no native i OS/Android app with SSO was established.
  • client_feature_gaps: Mobile effort picker is inline rather than flyout; broader mobile feature parity is not specified.
  • Unverified desktop_apps, browser_extension, managed_deployment: No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment.
  • web Is a full web client available? [supported]: Full Saa S browser client provides chat and Spaces. Sources: omnifact:omnifact:home.
  • desktop_apps Windows and macOS apps? [unknown]: Windows and mac OS apps? Unknown. No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment.
  • mobile_apps iOS and Android apps with SSO? [partial]: Pricing lists Mobile Web App and model picker adapts to small screens; no native i OS/Android app with SSO was established. Sources: omnifact:omnifact:pricing, omnifact:omnifact:select.
  • browser_extension Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment.
  • managed_deployment Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? Unknown. No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment.
  • client_feature_gaps Which features are missing on mobile? [partial]: Mobile effort picker is inline rather than flyout; broader mobile feature parity is not specified. Sources: omnifact:omnifact:select.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:home, omnifact:omnifact:pricing, omnifact:omnifact:select.

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.

Omnifact

Agent cross-checked Support: partial

Office files and live Google connectors exist; embedded office/Teams apps are unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • word_excel_powerpoint: Generates DOCX/XLSX/PPTX and modifies uploaded files, but this does not establish in-Word/Excel/Power Point add-ins.
  • google_workspace_apps: Google Docs/Sheets/Slides/Gmail/Calendar/Chat MCP actions run from Omnifact after personal OAuth; embedded add-ons were not established.
  • licence_prerequisites: Microsoft document access may require tenantwide admin consent; all OAuth integrations need individual authorized source accounts and third-party entitlements. Exact office-suite licence matrix not established.
  • Unverified outlook, teams: No current native Outlook add-in or Teams chat app/bot was established in documentation/catalogue.
  • word_excel_powerpoint Does it work inside Word, Excel and PowerPoint? [partial]: Generates DOCX/XLSX/PPTX and modifies uploaded files, but this does not establish in-Word/Excel/Power Point add-ins. Sources: omnifact:omnifact:documents.
  • outlook Does it work inside Outlook? [unknown]: Does it work inside Outlook? Unknown. No current native Outlook add-in or Teams chat app/bot was established in documentation/catalogue.
  • teams Is there a Teams app or bot? [unknown]: Is there a Teams app or bot? Unknown. No current native Outlook add-in or Teams chat app/bot was established in documentation/catalogue.
  • google_workspace_apps Does it work inside Docs, Sheets or Gmail? [partial]: Google Docs/Sheets/Slides/Gmail/Calendar/Chat MCP actions run from Omnifact after personal OAuth; embedded add-ons were not established. Sources: omnifact:omnifact:integrations.
  • licence_prerequisites Which licences or consents are needed? [partial]: Microsoft document access may require tenantwide admin consent; all OAuth integrations need individual authorized source accounts and third-party entitlements. Exact office-suite licence matrix not established. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:documents, omnifact:omnifact:integrations, omnifact:omnifact:sync.

WORK-03 Translation and writing

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Persistent style instructions support writing; specialized document translation is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • formality_and_variants: Personal response instructions can request formal/casual tone and style. Specific de-CH controls or terminology enforcement were not documented.
  • writing_tools: Chat supports drafting and rewriting via instructions and document generation; a dedicated proofreading/translation toolbar was not established.
  • Unverified document_translation, translation_engine, glossaries: Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations.
  • document_translation Can whole documents be translated with formatting kept? [unknown]: Can whole documents be translated with formatting kept? Unknown. Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations.
  • translation_engine Which engine translates? [unknown]: Which engine translates? Unknown. Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations.
  • glossaries Are company glossaries supported? [unknown]: Are company glossaries supported? Unknown. Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations.
  • formality_and_variants Can formality and regional variants (de-CH) be set? [partial]: Personal response instructions can request formal/casual tone and style. Specific de-CH controls or terminology enforcement were not documented. Sources: omnifact:omnifact:account.
  • writing_tools Are dedicated rewrite and proofreading tools available? [partial]: Chat supports drafting and rewriting via instructions and document generation; a dedicated proofreading/translation toolbar was not established. Sources: omnifact:omnifact:account, omnifact:omnifact:documents.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:account, omnifact:omnifact:documents.

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.

Omnifact

Agent cross-checked Support: partial

Image generation and edits use configured OpenAI/Google models under group permission.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • image_generation: Model Settings lists GPTImage2/1.5/1/1Mini, Nano Banana/Pro/2; September notes add GPTImage2.5Flare/Sunburst and October Nano Banana2.1 direct Google. EU generation remains Nano Banana2 because2.1 is not on Google Cloud EU.
  • admin_control: Generate Images is group-granted; model enablement/default is organization-wide. Image/audio contents bypass PII masking and retain route constraints.
  • Unverified usage_terms: Model-specific output licence/commercial rights were not established; general software rights do not define image-output ownership.
  • image_generation Can users generate images, with which models? [partial]: Model Settings lists GPTImage2/1.5/1/1Mini, Nano Banana/Pro/2; September notes add GPTImage2.5Flare/Sunburst and October Nano Banana2.1 direct Google. EU generation remains Nano Banana2 because2.1 is not on Google Cloud EU. Sources: omnifact:omnifact:model-settings, omnifact:omnifact:changes.
  • image_editing Can users edit uploaded images? [supported]: Uploaded reference images can be transformed with text instructions; results appear in gallery and download. Sources: omnifact:omnifact:images.
  • admin_control Can admins restrict image generation? [partial]: Generate Images is group-granted; model enablement/default is organization-wide. Image/audio contents bypass PII masking and retain route constraints. Sources: omnifact:omnifact:groups, omnifact:omnifact:model-settings, omnifact:omnifact:privacy.
  • usage_terms What usage rights apply to output? [unknown]: What usage rights apply to output? Unknown. Model-specific output licence/commercial rights were not established; general software rights do not define image-output ownership.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:model-settings, omnifact:omnifact:changes, omnifact:omnifact:images, omnifact:omnifact:groups, omnifact:omnifact:privacy.

WORK-05 Voice and meetings

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Experimental dictation/audio input exists; meeting bot/live voice coverage is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • dictation: Experimental Dictate Messages requires enabled Azure OpenAI; audio bypasses filtering and speech is converted to text.
  • meeting_summaries: Uploaded meeting transcripts can be summarized and Zoom integration searches/recaps recordings; no native automatic meeting-joining/transcription bot was established.
  • Unverified read_aloud, voice_conversation, swiss_german_speech: No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established.
  • dictation Can users dictate prompts? [partial]: Experimental Dictate Messages requires enabled Azure OpenAI; audio bypasses filtering and speech is converted to text. Sources: omnifact:omnifact:groups.
  • read_aloud Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established.
  • voice_conversation Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established.
  • meeting_summaries Are meetings transcribed and summarised? [partial]: Uploaded meeting transcripts can be summarized and Zoom integration searches/recaps recordings; no native automatic meeting-joining/transcription bot was established. Sources: omnifact:omnifact:directory, omnifact:omnifact:documents.
  • swiss_german_speech Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:groups, omnifact:omnifact:directory, omnifact:omnifact:documents.

WORK-06 Data analysis and document output

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

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-07 Sharing and team spaces

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

Cohere North

Agent cross-checked Support: partial

Shared snapshots and source collections have different access boundaries.

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Shared Spaces organize agents/knowledge; multi-user conversations and complete source-safe redistribution are unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • share_permission_boundary: Space members can see referenced uploaded knowledge. Personal OAuth MCP follows each source account, but Space source-ACL rechecking and generated-answer resharing boundaries were not tested.
  • Unverified share_chats, group_chat: Sharing individual chat links and simultaneous group conversation were not explicitly established; shared Space access alone is insufficient evidence.
  • share_chats Can chats be shared inside the organisation? [unknown]: Can chats be shared inside the organisation? Unknown. Sharing individual chat links and simultaneous group conversation were not explicitly established; shared Space access alone is insufficient evidence.
  • team_spaces Are shared projects or workspaces available? [supported]: Space instructions, knowledge and membership are shared with users/groups; conversations remain organized under the Space. Sources: omnifact:omnifact:spaces, omnifact:omnifact:share.
  • group_chat Can several people chat together with the AI? [unknown]: Can several people chat together with the AI? Unknown. Sharing individual chat links and simultaneous group conversation were not explicitly established; shared Space access alone is insufficient evidence.
  • share_permission_boundary Does sharing respect the recipient's access to sources? [partial]: Space members can see referenced uploaded knowledge. Personal OAuth MCP follows each source account, but Space source-ACL rechecking and generated-answer resharing boundaries were not tested. Sources: omnifact:omnifact:share, omnifact:omnifact:mcp, omnifact:omnifact:sync.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:spaces, omnifact:omnifact:share, omnifact:omnifact:mcp, omnifact:omnifact:sync.

WORK-08 Interface languages and accessibility

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

English and German UI are documented; language quality and accessibility are untested.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • admin_ui_languages: A separate German admin documentation tree is published; this does not verify complete German in-app admin translation.
  • Unverified dach_language_quality, accessibility_statement: No DE/FR/IT UI-quality fixture or WCAG conformance statement was obtained. French/Italian UI is not in the documented EN/DE selector.
  • ui_languages Which UI languages are offered? [supported]: Account language selector offers English/German, otherwise browser-language default. Sources: omnifact:omnifact:account.
  • dach_language_quality Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. No DE/FR/IT UI-quality fixture or WCAG conformance statement was obtained. French/Italian UI is not in the documented EN/DE selector.
  • accessibility_statement Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No DE/FR/IT UI-quality fixture or WCAG conformance statement was obtained. French/Italian UI is not in the documented EN/DE selector.
  • admin_ui_languages Is the admin interface available in German? [partial]: A separate German admin documentation tree is published; this does not verify complete German in-app admin translation. Sources: omnifact:omnifact:account.

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

Administration and governance

ADM-01 Single sign-on and authentication

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Enterprise SAML2.0 uses identity-provider MFA and conditional-access policies; nativeTOTP entitlement is outside this finding.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise SAML/SSO only; nativeTOTP entitlement excluded; add_ons=Enterprise SSO enablement; identity-provider MFA/conditional access; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • The supported MFA path here is the Enterprise identity provider. Native password/TOTP accounts require separate plan verification.
  • sso_protocols Which SSO protocols and identity providers work? [supported]: SAML2.0 via SSO Ready; Entra ID, Okta, Keycloak and SAML-compatible Id Ps. OIDC was not established. Sources: omnifact:omnifact:users, omnifact:omnifact:sso-blog, omnifact:omnifact:public-sector.
  • sso_plan Which plan includes SSO? [supported]: SSO/SCIM exclusive to Enterprise and support-enabled configuration. Sources: omnifact:omnifact:users.
  • mfa Can MFA be enforced? [partial]: For Enterprise SAML/SSO users, authentication and MFA are controlled by the identity provider; Omnifact native2FA setup is hidden. No nativeTOTP entitlement for Pro or Enterprise is asserted. Sources: omnifact:omnifact:security-rev2, omnifact:omnifact:sso-blog.
  • conditional_access Do Entra conditional-access policies apply? [partial]: SSO announcement says existing Id P conditional access/MFA/password rules apply; Entra device/location combinations were not tested. Sources: omnifact:omnifact:sso-blog.
  • domain_capture Can the company claim its email domain? [unknown]: Can the company claim its email domain? Unknown. No verified company-domain capture/ownership process was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:users, omnifact:omnifact:sso-blog, omnifact:omnifact:public-sector, omnifact:omnifact:security-rev2, omnifact:omnifact:auth.

ADM-02 User provisioning and lifecycle

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Enterprise SCIM synchronizes users/groups; deactivation blocks login while detailed asset disposition remains unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • jit_provisioning: Provisioned status includes SSO/SCIM-created accounts before first login; invitations are skipped for SSO. Exact just-in-time account trigger not specified.
  • deprovisioning: Deactivated users cannot log in; only unaccepted invitees can be permanently deleted from user list. Space removal keeps prior contributions; full leaver private data/agent ownership effects unspecified.
  • seat_assignment: Active and invited users count as seats; adding prorates cost, removal credits next invoice. Deactivated-seat billing treatment not fully specified.
  • scim Is SCIM provisioning supported? [supported]: Dedicated sso-sync creates, updates anddeactivates users automatically; manual creation/profile/role/CSV changes are locked under SCIM. Sources: omnifact:omnifact:users.
  • group_sync Are identity-provider groups synced? [supported]: Entra, Okta or Google Workspace groups mirror into immutable-membership Synced Groups with Omnifact-managed permissions. Sources: omnifact:omnifact:groups.
  • jit_provisioning Are users created at first login? [partial]: Provisioned status includes SSO/SCIM-created accounts before first login; invitations are skipped for SSO. Exact just-in-time account trigger not specified. Sources: omnifact:omnifact:users.
  • deprovisioning What happens to a removed user's data and shared assets? [partial]: Deactivated users cannot log in; only unaccepted invitees can be permanently deleted from user list. Space removal keeps prior contributions; full leaver private data/agent ownership effects unspecified. Sources: omnifact:omnifact:users, omnifact:omnifact:share.
  • seat_assignment Can admins assign and reclaim seats? [partial]: Active and invited users count as seats; adding prorates cost, removal credits next invoice. Deactivated-seat billing treatment not fully specified. Sources: omnifact:omnifact:billing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:users, omnifact:omnifact:groups, omnifact:omnifact:share, omnifact:omnifact:billing.

ADM-03 Roles, groups and feature permissions

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Owner/Admin/Member and Space roles combine with additive groups.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • multi_entity: Organization tenant separation and department Space/group boundaries are described; terms prohibit multiple accounts for one company and usage beyond own personnel without agreement. Multi-subsidiary contract rights were not established.
  • admin_roles Which admin roles exist, and can admin rights be delegated? [supported]: Owner includes Admin/Member, Admin includes Member; Admin manages team users/settings except Owner. Space Admin/Editor is separate, with optional Knowledge Base Manager in DPA. Sources: omnifact:omnifact:users, omnifact:omnifact:share, omnifact:omnifact:dpa.
  • groups Can permissions be set per group? [supported]: Everyone, SCIM-synced andmanual groups; permissions union rather than deny. Sources: omnifact:omnifact:groups.
  • feature_toggles Which features can be switched on or off per group? [supported]: Group grants file/image uploads, audio, web, imagegeneration, code, dictation, modeltiers, USmodels, filterexemption; organization models/features must also be enabled. Sources: omnifact:omnifact:groups.
  • multi_entity Can subsidiaries or departments be separated within one contract? [partial]: Organization tenant separation and department Space/group boundaries are described; terms prohibit multiple accounts for one company and usage beyond own personnel without agreement. Multi-subsidiary contract rights were not established. Sources: omnifact:omnifact:dpa, omnifact:omnifact:terms, omnifact:omnifact:share.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:users, omnifact:omnifact:share, omnifact:omnifact:dpa, omnifact:omnifact:groups, omnifact:omnifact:terms.

ADM-04 Usage and adoption analytics

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Enterprise adoption analytics show active users and message counts; deeper breakdown/export controls are unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise Usage Analytics & Insights; Pro excluded; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • Dashboard scope is organization/day level; additional model/group/assistant breakdowns and export remain unverified.
  • adoption_dashboard Is there an adoption dashboard? [supported]: Analytics provides date-range totals and daily active-user/message charts with interactive metric toggles; Enterprise-only in pricing. Sources: omnifact:omnifact:analytics-rev2, omnifact:omnifact:pricing-rev2.
  • breakdowns Can usage be broken down by group, model, feature and assistant? [partial]: Documented dashboard is organization/day level. Model, group, feature andassistant breakdown matrix was not established. Sources: omnifact:omnifact:analytics-rev2.
  • export Can usage data be exported? [unknown]: Can usage data be exported? Unknown. No documented analytics export/API or configurable individual-reporting controls were established. Direct HTML retrieval returned403; public cached official page was retrieved through the web tool.
  • privacy_modes Can per-person reporting be limited or pseudonymised? [partial]: DPA describes anonymized PostHog feature-use analytics without individual attribution; separate customer-visible reporting privacy toggles were not established. Sources: omnifact:omnifact:dpa-rev2.

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

ADM-05 Spend controls and cost allocation

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Shared pooled credits and model permissions constrain spend; individual financial allocation is unspecified.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • cost_visibility: Billing shows pooled real-time consumption andforecast; Enterprise detailed real-time dashboard is described as forthcoming, while total used is available.
  • budgets: Organization pooled allowance and manual additional-credit recharge. Model-tier and USroute access can be group-controlled, but per-user/group monetary hard caps were not established.
  • Unverified chargeback: No cost-centre chargeback export or complete cost-per-user/group allocation interface was established.
  • cost_visibility Can admins see cost or consumption per user and group? [partial]: Billing shows pooled real-time consumption andforecast; Enterprise detailed real-time dashboard is described as forthcoming, while total used is available. Sources: omnifact:omnifact:billing.
  • budgets Can budgets be set per user or group? [partial]: Organization pooled allowance and manual additional-credit recharge. Model-tier and USroute access can be group-controlled, but per-user/group monetary hard caps were not established. Sources: omnifact:omnifact:billing, omnifact:omnifact:groups.
  • budget_enforcement Does reaching a budget alert, block or downgrade? [supported]: Monthly budget: chat downgrades to enabled fallbacks; Gateway hard-blocks all calls on exhausted credits. Daily message quota disables send until reset. Sources: omnifact:omnifact:limits, omnifact:omnifact:gateway, omnifact:omnifact:chat.
  • chargeback Can costs be exported per cost centre? [unknown]: Can costs be exported per cost centre? Unknown. No cost-centre chargeback export or complete cost-per-user/group allocation interface was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:billing, omnifact:omnifact:groups, omnifact:omnifact:limits, omnifact:omnifact:gateway, omnifact:omnifact:chat.

ADM-06 Audit logs and compliance export

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

DPA documents append-only admin logs for at least 90 days; content compliance export is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • log_retention: Administrative logs retained at least 90 days; content retention is customer-configured but not a published compliance archive.
  • Unverified content_logging, siem_export, ediscovery: No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports.
  • admin_events Are admin and security events logged? [supported]: TOM2.5 records user-status changes/resource deletions with user attribution, UTC timestamps, encrypted transport/storage and append-only protection; event coverage can expand. Sources: omnifact:omnifact:dpa.
  • content_logging Can prompts and answers be retained for compliance, and is it configurable? [unknown]: Can prompts and answers be retained for compliance, and is it configurable? Unknown. No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports.
  • siem_export Can logs stream to a SIEM or be exported? [unknown]: Can logs stream to a SIEM or be exported? Unknown. No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports.
  • ediscovery Are eDiscovery and legal hold supported? [unknown]: Are e Discovery and legal hold supported? Unknown. No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports.
  • log_retention How long are logs kept? [partial]: Administrative logs retained at least 90 days; content retention is customer-configured but not a published compliance archive. Sources: omnifact:omnifact:dpa.

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

ADM-07 Data loss prevention and personal data

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Default Privacy Filter combines local NER/regex masking with several explicit bypass paths.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise, filter defaults enabled; user exemptions/advanced feature flags qualified; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • pii_detection: Names, addresses, email, phone, IPv4, US/German IDs/passports, tax/pensionnumbers, IBAN/BIC/card/routing/account numbers, companies anddocument filenames. Media bytes are not scanned; AHV recognition untested.
  • pii_action: Detected strings replaced with placeholders then restored in output; web queries containing masked values are blocked. Click-to-Reveal confirms sending individual terms; optional%%exemption defaults off andrequires Support. Group exemptions may disable filtering per agent/Space.
  • custom_patterns: Vendor detector uses custom-trained SLMNER andregex, but customer-defined pattern/dictionary UI/API was not established. Optional%%syntax bypasses rather than adds detection.
  • filter_location: DPA places filter within Azure Germany West Central, Frankfurt before external model. MCP arguments/results, code, sandbox, images/audio bytes, personalization and Published Space API bypass filtering by design.
  • Unverified dlp_integration: No existing third-party DLP/Purview integration or synthetic AHV/IBAN accuracy fixture was established.
  • pii_detection Is personal data detected in prompts and files? [partial]: Names, addresses, email, phone, IPv4, US/German IDs/passports, tax/pensionnumbers, IBAN/BIC/card/routing/account numbers, companies anddocument filenames. Media bytes are not scanned; AHV recognition untested. Sources: omnifact:omnifact:dpa, omnifact:omnifact:files, omnifact:omnifact:privacy.
  • pii_action Is it redacted, masked, blocked or only warned? [partial]: Detected strings replaced with placeholders then restored in output; web queries containing masked values are blocked. Click-to-Reveal confirms sending individual terms; optional%%exemption defaults off andrequires Support. Group exemptions may disable filtering per agent/Space. Sources: omnifact:omnifact:privacy, omnifact:omnifact:web, omnifact:omnifact:groups, omnifact:omnifact:dpa.
  • custom_patterns Can admins add custom patterns or terms? [partial]: Vendor detector uses custom-trained SLMNER andregex, but customer-defined pattern/dictionary UI/API was not established. Optional%%syntax bypasses rather than adds detection. Sources: omnifact:omnifact:dpa.
  • dlp_integration Does it integrate with an existing DLP product? [unknown]: Does it integrate with an existing DLP product? Unknown. No existing third-party DLP/Purview integration or synthetic AHV/IBAN accuracy fixture was established.
  • filter_location Where does filtering run? [partial]: DPA places filter within Azure Germany West Central, Frankfurt before external model. MCP arguments/results, code, sandbox, images/audio bytes, personalization and Published Space API bypass filtering by design. Sources: omnifact:omnifact:dpa, omnifact:omnifact:privacy, omnifact:omnifact:published, omnifact:omnifact:account.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa, omnifact:omnifact:files, omnifact:omnifact:privacy, omnifact:omnifact:web, omnifact:omnifact:groups, omnifact:omnifact:published, omnifact:omnifact:account.

ADM-08 AI policy and guardrails

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Company/Space instructions and privacy/tool governance exist; mandatory policy workflows are unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • org_instructions: Teamdescription supplies businesscontext; Spaceinstructions set response behavior and strict grounding. No guaranteed immutable organization safety instruction hierarchy was established.
  • content_filters: Organization PIImasking, group capabilities/modelroutes andper-tool approval/block settings are documented. General topic/abusefilter customization was not established.
  • Unverified usage_notice, violation_reporting: No mandatory AI-use-policy acknowledgement, admin policy-hit dashboard or configurable general content-filter taxonomy was established.
  • org_instructions Can admins set organisation-wide instructions? [partial]: Teamdescription supplies businesscontext; Spaceinstructions set response behavior and strict grounding. No guaranteed immutable organization safety instruction hierarchy was established. Sources: omnifact:omnifact:company, omnifact:omnifact:create, omnifact:omnifact:retrieval.
  • usage_notice Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? Unknown. No mandatory AI-use-policy acknowledgement, admin policy-hit dashboard or configurable general content-filter taxonomy was established.
  • content_filters Are content filters configurable? [partial]: Organization PIImasking, group capabilities/modelroutes andper-tool approval/block settings are documented. General topic/abusefilter customization was not established. Sources: omnifact:omnifact:privacy, omnifact:omnifact:groups, omnifact:omnifact:mcp.
  • violation_reporting Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. No mandatory AI-use-policy acknowledgement, admin policy-hit dashboard or configurable general content-filter taxonomy was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:company, omnifact:omnifact:create, omnifact:omnifact:retrieval, omnifact:omnifact:privacy, omnifact:omnifact:groups, omnifact:omnifact:mcp.

Data protection and sovereignty

DATA-01 Hosting location and data residency

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Hosted primary workspace storage is in Azure EU. Germany-only processing and complete backup/log/support residency are not established; model and metadata routes differ.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise hosted Azure platform storage; model and edge-metadata routes separately scoped; add_ons=Enterprise AI Gateway where named; provider/model route and eu/ prefix selected explicitly; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • The storage finding covers primary workspace content, not every model/edge/support processing path. No Germany-only or whole-service EU-only guarantee is made.
  • storage_region Where are chats, files and indexes stored? [partial]: Hosted raw chats/files/indexed workspace content uses Azure infrastructure in the EU. DPA identifies GermanyWestCentral/Frankfurt; the live infrastructure register also names NL/SE/IE. Only EU primary-platform storage is claimed here; a Germany-only deployment footprint is not established. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:trust-rev2.
  • inference_region Where do model calls run, per provider? [supported]: EU routes include Azure OpenAI, Google Cloud EU for Gemini/Anthropic, and Mistral EU. Direct OpenAI/Anthropic US and Google API global routes also exist. Gateway needs eu/ prefix; unprefixed IDs never use EU backends. Sources: omnifact:omnifact:models, omnifact:omnifact:vertex, omnifact:omnifact:gateway, omnifact:omnifact:trust-rev2.
  • backups_logs_region Where are backups, logs and telemetry? [unknown]: Unknown per-service backup/log geography for a particular contract. DPA Frankfurt/EU wording and the broader Azure DE/NL/SE/IE register do not map each backup stream. Cloudflare EU/US edge metadata/security logs are separate from platform document storage.
  • support_access_region From where can vendor staff access data? [partial]: Pricing names German and US service teams; DPA permits justified, time-limited production access. Staff physical access locations by task are not specified. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:dpa-rev2.
  • swiss_hosting Is Swiss hosting available? [unknown]: Is Swiss hosting available? Unknown. No full Swiss platform/backup/support hosting option was established.
  • residency_plan Which plan or option provides residency? [partial]: Pro/Enterprise pricing offers EU cloud storage and EU model routes. This does not establish all-service EU residency. Enterprise Gateway requests require eu/ model IDs for EU backends; direct/global model routes and edge metadata have different geography. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:gateway, omnifact:omnifact:providers-rev2, omnifact:omnifact:trust-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:models, omnifact:omnifact:vertex, omnifact:omnifact:gateway, omnifact:omnifact:trust-rev2, omnifact:omnifact:pricing-rev2, omnifact:omnifact:groups-rev2, omnifact:omnifact:providers-rev2.

DATA-02 Deployment options

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

  • Remaining atomic gaps: multi_tenant_saas.

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

Omnifact

Agent cross-checked Support: partial

Saa S, customer-cloud and on-premise are offered without published private-deployment minimums.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace, Omnifact Enterprise customer-cloud/on-premise; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise Saa S; Enterprise quoted private deployment; add_ons=Deployment/infrastructure/operator costs quoted; deployment_mode=not specified; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • dedicated_instance: Managed, own-cloud and on-premise are advertised; a distinct dedicated Saa S specification and seat threshold were not established.
  • customer_cloud: Own/private cloud is available on request; minimum seats/spend, operating roles and supported infrastructure are not public.
  • on_premise: Enterprise on-premise option includes municipal datacenters; numeric minimum and architecture requirements are unpublished.
  • Unverified air_gapped, mode_feature_gaps: Air-gapped operation and per-mode feature/egress parity were not established; a general self-hosting article is not a deployment specification.
  • multi_tenant_saas Is a shared SaaS offered? [supported]: Cloud Saa S uses logical organization/client separation. Sources: omnifact:omnifact:terms, omnifact:omnifact:dpa.
  • dedicated_instance Is a dedicated single-tenant instance offered, from what size? [partial]: Managed, own-cloud and on-premise are advertised; a distinct dedicated Saa S specification and seat threshold were not established. Sources: omnifact:omnifact:home.
  • customer_cloud Can it run in the customer's own cloud account, from what size? [partial]: Own/private cloud is available on request; minimum seats/spend, operating roles and supported infrastructure are not public. Sources: omnifact:omnifact:home, omnifact:omnifact:public-sector.
  • on_premise Can the whole platform run on customer infrastructure, from what size? [partial]: Enterprise on-premise option includes municipal datacenters; numeric minimum and architecture requirements are unpublished. Sources: omnifact:omnifact:pricing, omnifact:omnifact:public-sector.
  • air_gapped Can it run without internet access? [unknown]: Can it run without internet access? Unknown. Air-gapped operation and per-mode feature/egress parity were not established; a general self-hosting article is not a deployment specification.
  • mode_feature_gaps Which features are missing outside SaaS? [unknown]: Which features are missing outside Saa S? Unknown. Air-gapped operation and per-mode feature/egress parity were not established; a general self-hosting article is not a deployment specification.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:terms, omnifact:omnifact:dpa, omnifact:omnifact:home, omnifact:omnifact:public-sector, omnifact:omnifact:pricing.

DATA-03 Training use and provider retention

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Managed-route documentation promises no model training. Applicable upstream retention, ZDR eligibility and human-review exceptions remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise managed chat routes; AI Gateway statements apply only to the Enterprise API module; actual upstream retention unverified; add_ons=Enterprise AI Gateway enablement where explicitly named; BYOK under customer-provider agreement; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • No universal provider ZDR finding is made. The advertised ZDR option is not treated as unsupported; its applicable terms remain a gap.
  • vendor_training Does the vendor train on customer content? [supported]: Vendor says it never uses customer data to train its own models. Sources: omnifact:omnifact:privacy-intro.
  • provider_training Do model providers train on it under this product's contracts? [partial]: The vendor promises no underlying-provider training for the Enterprise AI Gateway. BYOK processing is under the customer-provider agreement; no managed-route promise is extended to arbitrary customer keys. Sources: omnifact:omnifact:gateway-web, omnifact:omnifact:dpa-rev2.
  • provider_retention How long do model providers keep prompts, including for abuse monitoring? [unknown]: Unknown applicable duration per enabled model/provider/project. The Trust register describes typical directOpenAI30-day retention and configuration-dependent Google logging, while EU-route pages advertise ZDR. These are not mapped to an actual customer route/contract, so no model-specific retention guarantee is asserted.
  • zero_retention Is zero data retention available, and on which plan? [unknown]: Unknown verified ZDR eligibility and scope per Pro/Enterprise model route. Gateway payload handling and EU-route marketing do not establish the upstream provider agreement or every safety/logging exception. Workspace database storage is separate.
  • human_review Can provider staff review content? [partial]: Provider processing summaries are request-only in Trust Center; human abuse-review exceptions by provider/model were not established. Sources: omnifact:omnifact:trust-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:privacy-intro, omnifact:omnifact:gateway-web, omnifact:omnifact:dpa-rev2, omnifact:omnifact:trust-rev2, omnifact:omnifact:vertex.

DATA-04 Retention and deletion

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

DPA contract-end return/approved-destruction duties are separate from support-request deletion and backup retention. A guaranteed runtime exit window remains unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise published DPA return/deletion obligations; actual runtime exit and account-deletion timing unverified; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • The finding states separate contractual and documented operational procedures. It does not turn a support-request clock into an exit grace period.
  • default_retention What is retained and for how long by default? [partial]: DPA: database PITR30 days with daily snapshots/continuous WAL; weekly pg_dump fallback; blob soft-delete14 days. Universal default chat/file retention is unspecified. Sources: omnifact:omnifact:dpa-rev2.
  • admin_retention Can admins set retention periods? [partial]: DPA permits organization administrators to set customer-data retention; UI range and per-object options are not published. Sources: omnifact:omnifact:dpa-rev2.
  • user_deletion Can users delete their chats and files permanently? [partial]: The Space uploaded-file guide describes permanent deletion of a selected file. Registered-user/profile and whole-organization runtime deletion semantics are not established here; the user-list Delete operation applies to unaccepted invitations. Sources: omnifact:omnifact:uploads, omnifact:omnifact:users.
  • contract_end_deletion What is deleted at contract end, and when? [partial]: DPA9.2 requires return or controller-approved destruction no later than contract end, except legal retention;9.3 permits proof-of-processing documentation retention. The TOM separately describes support-request organization deletion within30days and backups aging out. No guaranteed post-termination self-service access window or tested runtime completion time is inferred. Sources: omnifact:omnifact:dpa-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:users, omnifact:omnifact:uploads.

DATA-05 Sub-processors and foreign-law exposure

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

DPA defines processor-change notice and transfer safeguards; a complete current contract-specific supplier/entity/country register remains unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise standard hosted DPA; optional model-provider routes only under the applicable contract/instruction; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • Neither public list is silently treated as complete. Ordinary notification/transfer contract terms remain distinct from a verified current processing inventory.
  • subprocessor_list Is a dated sub-processor list published? [unknown]: Unknown complete current plan-specific processor inventory. DPAAnnex4 and the live Trust register publish different sets; no source establishes a consolidated applicable list or the role of every listed provider for a given contract.
  • subprocessor_countries Which countries do sub-processors operate in? [unknown]: Unknown complete country/legal-entity matrix for the scoped contract. Azure infrastructure and Cloudflare metadata have different roles, and optional model-provider routes depend on selection. The differing DPA/Trust entries are not combined into one asserted authoritative list.
  • change_notification Are customers notified of sub-processor changes? [supported]: DPA6.3 requires written/text notice at least 30 days before new/replaced subprocessor and objection opportunity before start. Sources: omnifact:omnifact:dpa-rev2.
  • parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: Omnifact Gmb H, Frankfurt, Germany, HRB131357. Ultimate parent/shareholding was not established. Sources: omnifact:omnifact:imprint.
  • transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [partial]: DPA1.4 permits nonEEA processing after prior information and safeguards under Articles44-49. Optional BYOK/provider routes depend on their applicable agreements. A specific current SCC/DPF basis for every Trust entry was not verified. Sources: omnifact:omnifact:dpa-rev2.
  • government_access_policy Is there a published government-access or transparency policy? [partial]: DPA11.2 requires seizure/confiscation notice unless prohibited by court/authority; Terms15.3 require advance compelled-disclosure notice where legal. Separate request statistics were not verified. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:terms.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:trust-rev2, omnifact:omnifact:imprint, omnifact:omnifact:terms.

DATA-06 Contracts and regulatory coverage

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Public GDPR DPA is binding in German; Swiss and sector-specific contract coverage remains incomplete.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • dpa: Article28 DPA accepted at registration. German text prevails; English is a translation. Written amendments are possible but negotiability is not promised.
  • revdsg_gdpr: GDPR is explicit; revised Swiss DSG coverage/addendum and Swiss SCC modifications were not established.
  • ai_act_materials: Public AI Act whitepaper and Academy literacy/certification training are advertised; these are not product conformity attestations.
  • sector_materials: Public-administration, banking and healthcare positioning/private hosting are advertised; actual FINMA/DORA/§203 contract pack was not verified.
  • dpa Is a DPA available, and is it negotiable? [partial]: Article28 DPA accepted at registration. German text prevails; English is a translation. Written amendments are possible but negotiability is not promised. Sources: omnifact:omnifact:dpa, omnifact:omnifact:dpa-de.
  • revdsg_gdpr Does the DPA cover revDSG and GDPR? [partial]: GDPR is explicit; revised Swiss DSG coverage/addendum and Swiss SCC modifications were not established. Sources: omnifact:omnifact:dpa.
  • governing_law Which law and court govern the contract? [supported]: German law and Frankfurt exclusive jurisdiction under Terms18; German legal version prevails. Sources: omnifact:omnifact:terms.
  • ai_act_materials Is EU AI Act documentation provided? [partial]: Public AI Act whitepaper and Academy literacy/certification training are advertised; these are not product conformity attestations. Sources: omnifact:omnifact:whitepapers, omnifact:omnifact:pricing.
  • sector_materials Are FINMA or other sector materials provided? [partial]: Public-administration, banking and healthcare positioning/private hosting are advertised; actual FINMA/DORA/§203 contract pack was not verified. Sources: omnifact:omnifact:home, omnifact:omnifact:public-sector.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa, omnifact:omnifact:dpa-de, omnifact:omnifact:terms, omnifact:omnifact:whitepapers, omnifact:omnifact:pricing, omnifact:omnifact:home, omnifact:omnifact:public-sector.

DATA-07 Certifications and attestations

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Public ISO27001 certificate verifies platform/Spaces ISMS through 2029-04-06.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • pentest: DPA states annual external pentests with remediation; actual report/period/summary was not verified.
  • Unverified soc2, c5, other_certifications: No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified.
  • iso_27001 ISO 27001 with scope and validity? [supported]: Prescient Security LLC certificate123228 issue1, ISO/IEC27001:2022, issued/certified 2026-04-07, valid until 2029-04-06 subject to surveillance. Covers ISMS supporting Platform/Spaces, data, Azure infrastructure, software, people and procedures; So A1.4 dated 2026-03-30. All in-scope activities conducted remotely. Sources: omnifact:omnifact:iso.
  • soc2 SOC 2 type, period and covered service? [unknown]: SOC 2 type, period and covered service? Unknown. No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified.
  • c5 BSI C5 attestation? [unknown]: BSI C5 attestation? Unknown. No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified.
  • other_certifications Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Unknown. No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified.
  • report_access How can customers obtain reports? [supported]: ISO PDF is public and downloadable through Trust Center. Eight AI-provider processing summaries are request-only and were not requested. Sources: omnifact:omnifact:trust.
  • pentest Are independent penetration test summaries available? [partial]: DPA states annual external pentests with remediation; actual report/period/summary was not verified. Sources: omnifact:omnifact:dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:iso, omnifact:omnifact:trust, omnifact:omnifact:dpa.

DATA-08 Encryption and key control

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

AES256/TLS and logical tenant separation are documented; customer-held keys remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • private_networking: Vendor internal services use NSGs/Private Endpoints and NetBird JIT VPN for privileged production access; public app is Cloudflare-fronted. A customer private-link/IP-allowlist option was not established.
  • Unverified customer_managed_keys: No customer-managed/held encryption-key configuration was established; sovereignty discussion does not establish key-management functionality.
  • encryption_at_rest Is data encrypted at rest? [supported]: DPA requires AES256 at rest for Postgre SQL, Blob Storage and other persistent Azure services; HTTPS/TLS in transit. Sources: omnifact:omnifact:dpa.
  • customer_managed_keys Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Unknown. No customer-managed/held encryption-key configuration was established; sovereignty discussion does not establish key-management functionality.
  • private_networking Is private connectivity or IP restriction available? [partial]: Vendor internal services use NSGs/Private Endpoints and NetBird JIT VPN for privileged production access; public app is Cloudflare-fronted. A customer private-link/IP-allowlist option was not established. Sources: omnifact:omnifact:dpa.
  • tenant_isolation How are customers separated in shared SaaS? [supported]: Organization-scoped data/roles, separate production/development/test Azure environments, no customer data in tests. This is logical tenant separation. Sources: omnifact:omnifact:dpa.

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

DATA-09 Professional secrecy

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

No public information found Support: not-published

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

Commercials and vendor

VEN-01 Pricing model and list prices

Judgment rule: Record pricing unit (per seat, per active user, usage-based, platform fee, hybrid), list prices per plan in original currency with date, included usage and credits, add-on prices (connectors, agents, image generation) and overage rates. Cite public prices or dated quotes. Per-seat versus usage is a fact, not a quality judgment.

Cohere North

Agent cross-checked Support: partial

North uses capacity and installation licensing with custom prices.

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Pro costs EUR25/user/month annually up to50users. Its binding credit currency/value and recharge tariff remain unknown; Enterprise Gateway costs are outside this offer.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro hosted workspace up to50users; Enterprise/API Gateway quote and markup excluded; add_ons=Optional Academy separately quoted; Enterprise terms require separate offer; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • Pro Chat/Spaces pricing is not mixed with Enterprise Gateway billing. The conflicting credit examples remain a named allowance gap.
  • pricing_unit What is the pricing unit? [supported]: Pro uses named seats with monthly or annual billing and pooled premium-model credit; this finding covers the hosted Chat/Spaces subscription. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing.
  • list_prices What are list prices per plan, with date and currency? [partial]: Checked2026-10-21: Pro EUR25/user/month billed annually, advertised16% discount versus monthly. Exact monthly rate was not verified. Pro up to50 users; Enterprise custom with unlimited team size. VAT excluded under terms. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms.
  • included_usage What usage is included? [partial]: Unknown applicable monetary allowance currency/value for the contract: pricing statesEUR5/user/month while Billing usesUSD5 examples. Pooling, monthly expiry and continued base-tier access subject to fair-use limits are documented, but no definitive currency-denominated allowance is asserted. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing.
  • add_ons Which features cost extra? [partial]: Academy training is separately quoted. Enterprise is a separate custom offer adding SSO/SCIM, BYOK/self-hosted models, analytics and custom deployment/SLA. No Enterprise Gateway markup is applied to Pro Chat/Spaces pricing. Sources: omnifact:omnifact:pricing-rev2.
  • overage What do usage beyond limits and premium models cost? [partial]: The Pro billing guide directs admins to discuss additional credits; a public recharge tariff was not established. Base-tier chat remains available after included premium credit is used subject to usage limits. Enterprise Gateway billing/markup is outside this Pro finding. Sources: omnifact:omnifact:billing, omnifact:omnifact:pricing-rev2, omnifact:omnifact:limits.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing, omnifact:omnifact:terms, omnifact:omnifact:limits, omnifact:omnifact:users, omnifact:omnifact:gateway, omnifact:omnifact:developer.

VEN-02 Scenario cost

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Shared v1.4 costs remain unknown for200/1000/5000 users because all exceed the50-seat Pro cap.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown.
  • ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21.
  • cost_200 Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown for 200 users:Pro caps50 users,so Enterprise licence,allowance and deployment/support quote are required. No quote requested; do not extrapolate EUR25 Pro rate. ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx.
  • cost_1000 Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown for 1000 users:Pro caps50 users,so Enterprise licence,allowance and deployment/support quote are required. No quote requested; do not extrapolate EUR25 Pro rate. ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx.
  • cost_5000 Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown for 5000 users:Pro caps50 users,so Enterprise licence,allowance and deployment/support quote are required. No quote requested; do not extrapolate EUR25 Pro rate. ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx.
  • variable_share Which part depends on usage? [partial]: Enterprise base,pooled credit allowance,model/route rates,additional credits and Gateway markup are unknown. Quote base plus usage beyond included credit plus deployment/services; convert known EUR components at0.9237 CHF/EUR. No substitute vendor tariff/model assumed. Sources: omnifact:omnifact:pricing, omnifact:omnifact:gateway, omnifact:omnifact:billing, omnifact:omnifact:ecb-fx.
  • unknown_parts Which costs could not be priced? [supported]: Enterprise seat/volume rate,minimum spend,credit allowance,recharge tariff,model/route rates,Gateway markup percentage,private hosting and Academy service fees are unknown. Sources: omnifact:omnifact:pricing, omnifact:omnifact:gateway, omnifact:omnifact:billing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx, omnifact:omnifact:gateway, omnifact:omnifact:billing.

VEN-03 Evaluation access

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Ten-day no-card Pro trial is self-serve; enterprise setup is gated.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • free_tier: Time-limited free trial; billing requires a paid subscription afterward. No permanent business free tier established.
  • trial_scope: Pro chat, Spaces, Privacy Filter and platform access advertised; terms call trial scope limited. Enterprise SSO/SCIM/BYOK/private deployment and support-enabled APIs are not established trial entitlements.
  • sales_gate: Base Pro trial is self-serve; Enterprise quotes, SSO and advanced API activation require vendor interaction. No vendor contact was made.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:billing, omnifact:omnifact:terms, omnifact:omnifact:developer, omnifact:omnifact:users.

VEN-04 Contract terms and pricing transparency

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Pro monthly/annual terms are public; Enterprise minimum and CHF invoicing are unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • minimum_commitment: Pro maximum 50 users, Enterprise no team-size cap; public Enterprise minimum seat/spend and private-deployment minimum not established.
  • local_invoicing: Omnifact Gmb H Frankfurt invoices EUR public prices, supports invoice/SEPA and payment within 14 days. CHF billing not established.
  • transparency_class: Partial: public Pro price/credits/team cap but Enterprise, deployment, additional credits and services quote-only; Gateway markup not quantified.
  • minimum_commitment What seat or spend minimum applies? [partial]: Pro maximum 50 users, Enterprise no team-size cap; public Enterprise minimum seat/spend and private-deployment minimum not established. Sources: omnifact:omnifact:pricing.
  • contract_length What contract lengths are offered? [supported]: Monthly/annual terms; Enterprise flexible agreement. Annual renews yearly, monthly renews monthly. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms.
  • cancellation How can the contract be cancelled or reduced? [supported]: Annual notice three months before term end; monthly cancel for following month; text/email accepted. Seat removal gives prorated credit on next invoice per billing doc. Sources: omnifact:omnifact:terms, omnifact:omnifact:billing.
  • local_invoicing Can it be invoiced in CHF or EUR from a European entity? [partial]: Omnifact Gmb H Frankfurt invoices EUR public prices, supports invoice/SEPA and payment within 14 days. CHF billing not established. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms, omnifact:omnifact:imprint.
  • transparency_class Is pricing transparent, partial, quote-only or unknown? [partial]: Partial: public Pro price/credits/team cap but Enterprise, deployment, additional credits and services quote-only; Gateway markup not quantified. Sources: omnifact:omnifact:pricing, omnifact:omnifact:gateway.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms, omnifact:omnifact:billing, omnifact:omnifact:imprint, omnifact:omnifact:gateway.

VEN-05 Source licence

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Platform is proprietary; four inspected public integration/client components have MIT licences.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync, Omnifact example embeddable widget; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise hosted licence; separately MIT-licensed client/integration tools at pinned revisions; API enablement required; add_ons=Customer-run CLI/widget tools; Published Spaces/API access and resource permissions as needed; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • Client/integration capabilities are documented in pinned README/licence files, not implementation-inspected or tested; they do not license the hosted platform.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:terms, omnifact:omnifact:cli-licence-rev2, omnifact:omnifact:widget-licence-rev2, omnifact:omnifact:n8n-nodes-omnifact-licence-rev2, omnifact:omnifact:xwiki-sync-licence-rev2, omnifact:omnifact:widget-rev2, omnifact:omnifact:pricing-rev2.

VEN-06 Data export and exit

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

DPA promises data handover; documented APIs do not establish a complete workspace export.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync, Omnifact example embeddable widget; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise hosted licence; separately MIT-licensed client/integration tools at pinned revisions; API enablement required; add_ons=Customer-run CLI/widget tools; Published Spaces/API access and resource permissions as needed; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • Client/integration capabilities are documented in pinned README/licence files, not implementation-inspected or tested; they do not license the hosted platform.
  • chat_export Can admins export all chats? [unknown]: Can admins export all chats? Unknown. No admin export-all-chats or reusable complete Space/agent/prompt export was established. No exit fixture was run.
  • assistant_export Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unknown. No admin export-all-chats or reusable complete Space/agent/prompt export was established. No exit fixture was run.
  • knowledge_export Can knowledge bases and their sources be exported? [partial]: Documents API/CLI list metadata and manage Space files, while native generated files download. Full original-source, index and ACL export bundle was not established. Sources: omnifact:omnifact:api-docs, omnifact:omnifact:cli-rev2, omnifact:omnifact:documents.
  • export_format Are formats documented and machine-readable? [partial]: Document metadata via JSON; native outputs DOCX/XLSX/PPTX and chart images. Widget stores only its own conversation in browser local Storage; this is not an admin export of platform chats. Sources: omnifact:omnifact:api-docs, omnifact:omnifact:documents, omnifact:omnifact:widget-rev2.
  • post_termination_window How long can data be retrieved after termination? [partial]: DPA9.2 requires handover or approved destruction at completion/end; no guaranteed post-termination self-service download window specified. TOM gives30-day support organization deletion. Sources: omnifact:omnifact:dpa-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:api-docs, omnifact:omnifact:cli-rev2, omnifact:omnifact:documents, omnifact:omnifact:widget-rev2, omnifact:omnifact:dpa-rev2.

VEN-07 Support and service levels

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Pro email support and Enterprise custom support are documented; a single applicable platform uptime SLA remains unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro published support terms; Enterprise support and negotiated SLA only under its contract; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • Network and system availability percentages are not interchangeable. Enterprise SLA terms require the actual contract.
  • support_channels Which support channels are available on each plan? [partial]: Pro pricing promises email within 24 hours; terms process M–F usually09–17 and answer within one working day. Enterprise dedicated support/account manager/custom SLA; timezone not specified in terms. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms.
  • support_languages Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. No verified public incident-history status page or contracted DE/FR/IT support-language matrix was located; status.omnifact.ai did not resolve.
  • regional_presence Is there a DACH or Swiss entity, team or partner? [partial]: Omnifact Gmb H Frankfurt, Germany; pricing also mentions German and US service teams. No Swiss entity established. Sources: omnifact:omnifact:imprint, omnifact:omnifact:pricing-rev2.
  • uptime_sla Is there an uptime SLA with credits? [unknown]: Unknown applicable end-to-end service guarantee. Terms7.3 specify99.5% annual pure-network availability while DPA TOM states99.9% system availability, and Enterprise offers a custom SLA. No order-form/service mapping or fixed credit schedule was retrieved, so no single platform SLA is asserted.
  • status_page Is there a public status page with history? [unknown]: Is there a public status page with history? Unknown. No verified public incident-history status page or contracted DE/FR/IT support-language matrix was located; status.omnifact.ai did not resolve.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms, omnifact:omnifact:imprint, omnifact:omnifact:dpa-rev2.

VEN-08 Onboarding, training and adoption

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

Cohere North

Agent cross-checked Support: partial

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

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

Limitations

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

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

Omnifact

Agent cross-checked Support: partial

Pro has learning material/webinar; Enterprise workshops and Academy are tailored.

Availability: generally-available · Delivery: native
Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified.

Limitations

  • user_training: Academy offers foundational/advanced courses, individual training and certificate options supporting AI literacy; complete delivery-language/volume entitlement not published.
  • adoption_programme: Enterprise rollout/admin enablement/use-case workshops and Academy strategy/governance workshops advertised; a formal champion programme was not established.
  • service_cost: Academy/additional training separately quoted; terms3.6 generally make installations, instruction/training chargeable under separate agreement.
  • onboarding_service Is guided onboarding included? [supported]: Pro onboarding documentation/e-learning and webinar; Enterprise custom onboarding/use-case workshops and account manager. Sources: omnifact:omnifact:pricing.
  • user_training Is end-user training offered, in which languages? [partial]: Academy offers foundational/advanced courses, individual training and certificate options supporting AI literacy; complete delivery-language/volume entitlement not published. Sources: omnifact:omnifact:pricing.
  • use_case_library Are role-based use cases and templates provided? [supported]: Space Starter templates include content creation, knowledge queries, professional development; release notes add meeting-minutes/mail-triage/helpdesk template previews. Sources: omnifact:omnifact:create, omnifact:omnifact:changes.
  • adoption_programme Is there a champion or adoption programme? [partial]: Enterprise rollout/admin enablement/use-case workshops and Academy strategy/governance workshops advertised; a formal champion programme was not established. Sources: omnifact:omnifact:home, omnifact:omnifact:pricing.
  • service_cost Which services cost extra? [partial]: Academy/additional training separately quoted; terms3.6 generally make installations, instruction/training chargeable under separate agreement. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:create, omnifact:omnifact:changes, omnifact:omnifact:home, omnifact:omnifact:terms.

Sources

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  9. Models: All Leading AI Models on One Platform – Omnifact omnifact:omnifact:models

    Current catalogue lists model families, tiers and EU/global region flags.

    OpenAI, Anthropic, Google and Mistral tables · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  10. Selecting an AI Model - Omnifact omnifact:omnifact:select

    Manual model picker shows provider/model/region and reasoning effort; browser stores per-model effort.

    Model selector, effort and reasoning trace · documented · Source date not stated · Retrieved 2026-10-21

  11. Attaching Documents & Images - Omnifact omnifact:omnifact:files

    Attachments have type-specific limits and media bypasses text filtering.

    Formats, input limits and privacy · documented · Source date not stated · Retrieved 2026-10-21

  12. Pricing Plans – Omnifact omnifact:omnifact:pricing-rev2

    Pro is EUR25/user/month annually up to50users. Enterprise adds BYOK/self-hosted models, analytics, SSO and custom SLA. The page is not used to establish an eligible Gateway markup or reconcile conflicting credit examples.

    Pro/Enterprise tier table, annual price and credit footnote · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  13. Providers - Omnifact omnifact:omnifact:providers-rev2

    Customer keys, custom OpenAI-compatible endpoints and self-hosted model connections require Enterprise BYOK; managed model access is separate.

    Supported Providers and Enterprise-only Bring Your Own Key · documented · Source date not stated · Retrieved 2026-10-21

  14. Group Management - Omnifact omnifact:omnifact:groups-rev2

    The Python/code execution tool is explicitly Experimental, has internet access and bypasses the Privacy Filter for sandbox inputs.

    Execute code (Experimental), tool controls and security note · documented · Source date not stated · Retrieved 2026-10-21

  15. Data Processing Agreement – Omnifact omnifact:omnifact:dpa-rev2

    DPA states return/approved destruction at contract end, distinct support-request deletion within30days, backup schedules and30-day subprocessor-change notice. This does not resolve runtime/plan-specific implementation or a complete current supplier mapping.

    Sections6.3,9.2/9.3; Annex3 deletion and backups; Annex4 subprocessor terms · documented · Source date 2026-04-21 · Retrieved 2026-10-21

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

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

  18. Release Notes – Omnifact omnifact:omnifact:changes

    Dated release notes through October 20 add models, agents, code, MCP, groups and 2FA.

    October–May2026 and earlier entries · documented · Source date 2026-10-20 · Retrieved 2026-10-21

  19. Blog – Omnifact omnifact:omnifact:blog

    Feature announcements include Gemini4Argon October 13 and integrations October 6.

    Current dated feature drops · documented · Source date not stated · Retrieved 2026-10-21

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

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

  22. Terms of Service – Omnifact omnifact:omnifact:terms

    Terms define proprietary rights,99.5% annual network availability, support and cancellation.

    Sections3/6–8/10–11/14–18 · documented · Source date 2024-08-01 · Retrieved 2026-10-21

  23. Providers - Omnifact omnifact:omnifact:providers

    Enterprise BYOK supports direct providers, Azure/Vertex and custom OpenAI-compatible endpoints.

    Supported Providers, BYOK and connection management · documented · Source date not stated · Retrieved 2026-10-21

  24. Model Management - Omnifact omnifact:omnifact:model-settings

    Model enablement applies to chat, Published Spaces and Gateway; image defaults and tiers are configurable.

    Availability, Image Models and Model Providers · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

  29. Pricing Plans – Omnifact omnifact:omnifact:pricing

    Pro annual EUR25 includes pooled EUR5 monthly AI credits per seat up to50 users; Enterprise and Academy are quoted.

    Pro, Enterprise, comparison and footnote1 · vendor-claimed · Source date not stated · Retrieved 2026-10-21

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

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

  32. Data Processing Agreement – Omnifact omnifact:omnifact:dpa

    DPA includes Frankfurt infrastructure/TOMs, retention, audit requirements and approved subprocessors.

    Sections1/6/9/11, Annex1, TOMs2.1–2.10 and Annex4 · documented · Source date 2026-04-21 · Retrieved 2026-10-21

  33. Group Management - Omnifact omnifact:omnifact:groups

    Additive groups govern capabilities, model tiers, US routes and filter exemptions; Enterprise SCIM mirrors groups.

    Group types, SCIM, permissions and sharing · documented · Source date not stated · Retrieved 2026-10-21

  34. AI Gateway - Omnifact omnifact:omnifact:gateway

    Enterprise opt-in OpenAI-compatible gateway uses eu/ routing and hard credit enforcement; V1 lacks tools/structured output.

    Prerequisites, EU routes, constraints, billing and errors · documented · Source date not stated · Retrieved 2026-10-21

  35. Published Spaces - Omnifact omnifact:omnifact:published

    Support-enabled Published Space APIs disable the Privacy Filter and use secret endpoint URLs.

    Activation, model management and security · documented · Source date not stated · Retrieved 2026-10-21

  36. Introduction to Chats - Omnifact omnifact:omnifact:chat

    Chat retains conversations and supports document output, sources and daily message quotas.

    Features, quotas and message limits · documented · Source date not stated · Retrieved 2026-10-21

  37. AI Credits and Usage Limits - Omnifact omnifact:omnifact:limits

    Exhausted monthly credits fall back in chat; Gateway blocks all calls without base fallback.

    Credit exhaustion and fallback models · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  41. Document Creation - Omnifact omnifact:omnifact:documents

    Isolated Python code creates XLSX/DOCX/PPTX/charts with internet egress and group controls.

    Document types, editing, formulas and sandbox · documented · Source date not stated · Retrieved 2026-10-21

  42. Managing Uploaded Files - Omnifact omnifact:omnifact:uploads

    Space file pipeline uses Tika OCR, chunking, embeddings and summaries; documents can be deleted permanently.

    Processing, deletion and FAQ · documented · Source date not stated · Retrieved 2026-10-21

  43. Uploaded Files Retrieval - Omnifact omnifact:omnifact:retrieval

    Agents retrieve source passages under Space membership and show citations/progress; strict no-answer grounding is instructed.

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

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

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

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

  47. Billing & Usage - Omnifact omnifact:omnifact:billing

    Billing describes proration, pooled credit and plan changes but uses USD5 examples and5000-page Pro quota.

    Seat Management, Monthly Usage Credit and Plan Management · documented · Source date not stated · Retrieved 2026-10-21

  48. What are Spaces? - Omnifact omnifact:omnifact:spaces

    Spaces persist instructions/knowledge and conversations with shared member access.

    Concepts, benefits and examples · documented · Source date not stated · Retrieved 2026-10-21

  49. Sharing Spaces with Colleagues - Omnifact omnifact:omnifact:share

    Organization users/groups share Spaces; group access is view-only and removal is immediate.

    Roles, group sharing and removal · documented · Source date not stated · Retrieved 2026-10-21

  50. Connected Sources - Omnifact omnifact:omnifact:sync

    Connected sources index selected Drive/OneDrive/SharePoint folders every five minutes and remove deleted content next cycle.

    Setup, privacy and FAQ · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

  56. Integrations - Omnifact omnifact:omnifact:integrations

    Curated first-party MCP and document connectors use separate live-versus-indexed access patterns.

    Catalog, integration types and privacy · documented · Source date not stated · Retrieved 2026-10-21

  57. Integrations: Connect the Tools Your Team Uses – Omnifact omnifact:omnifact:directory

    Current catalogue names cloud storage, Google, Atlassian, CRM, design, communications and developer systems.

    Integration cards and custom MCP · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  58. omnifact-xwiki-sync pinned README omnifact:omnifact:xwiki-sync-rev2

    omnifact-xwiki-sync documents incremental XWiki page/attachment ingestion with delete propagation. This finding is documented at the pinned revision; no implementation behavior was tested or inspected.

    Pinned README.md documentation at commit 599db2ec0c7f28ddb2a22c4a09a9242e5781316b; retrieved with GitHub file connector · documented · Source date 2026-08-25 · Retrieved 2026-10-21

  59. MCP Servers - Omnifact omnifact:omnifact:mcp-rev2

    Tools have Always/Approval/Disable policies; Approval shows the request payload. Documentation conflicts on initial discovery defaults, which remain unknown.

    Per-tool policies, authentication and later tool refresh; initial discovery defaults excluded · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

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

  67. MCP Servers - Omnifact omnifact:omnifact:mcp

    Remote MCP has personal OAuth/shared static credentials, per-tool Always/Approval/Disable policies and private-network restrictions.

    Setup, policies, OAuth, approvals and privacy boundaries · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

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

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

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

  77. Account Settings - Omnifact omnifact:omnifact:account

    English/German UI and persistent personal context/instructions are documented; personalization is unfiltered.

    Language Preferences and Personalization · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  81. User Management - Omnifact omnifact:omnifact:users

    User roles and Enterprise SSO/SCIM automate lifecycle while locking manual changes.

    Roles, statuses, lifecycle and SSO/SCIM · documented · Source date not stated · Retrieved 2026-10-21

  82. Creating New Spaces - Omnifact omnifact:omnifact:create

    Users create custom Space agents with instructions and starter examples.

    Space Starters and configuration · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  86. Image Generation - Omnifact omnifact:omnifact:images

    Images are generated/edited from references and retained in an Assets gallery.

    Generation, reference images and gallery · documented · Source date not stated · Retrieved 2026-10-21

  87. Web Search and Browsing - Omnifact omnifact:omnifact:web

    Web search displays citations and blocks queries with masked sensitive values.

    Search, privacy and limitations · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

  94. n8n-nodes-omnifact pinned README omnifact:omnifact:n8n-nodes-omnifact-rev2

    n8n-nodes-omnifact documents n8n community nodes for Gateway/chat/documents. This finding is documented at the pinned revision; no implementation behavior was tested or inspected.

    Pinned README.md documentation at commit 7a3947c620206d4e195064421db525aaa4dfb50a; retrieved with GitHub file connector · documented · Source date 2026-09-10 · Retrieved 2026-10-21

  95. Published Spaces Chat API - Omnifact omnifact:omnifact:api-chat

    Published chat provides JSON/SSE and optional inline sources/agentic workflow headers.

    Headers, responses and SSE events · documented · Source date not stated · Retrieved 2026-10-21

  96. Stopping and Regenerating Responses - Omnifact omnifact:omnifact:stop

    Send changes to a Stop button during response generation.

    How to Stop · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

  103. Developer Tools - Omnifact omnifact:omnifact:developer

    API enablement is gated and organization key regeneration/revocation is centralized.

    Activation and API key management · documented · Source date not stated · Retrieved 2026-10-21

  104. Documents API - Omnifact omnifact:omnifact:api-docs

    Document APIs upload/list/inspect/update/delete Space files asynchronously.

    Endpoints and schema examples · documented · Source date not stated · Retrieved 2026-10-21

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

  106. AI for the Public Sector & Regulated Industries – Omnifact omnifact:omnifact:home

    Platform offers governed multi-model chat, Spaces, Privacy Filter and private deployment.

    Product, governance and deployment overview · vendor-claimed · Source date not stated · Retrieved 2026-10-21

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

  108. Data Privacy - Omnifact omnifact:omnifact:privacy

    Filter defaults on but MCP, code, image/audio paths bypass it; code sandbox has internet egress.

    Privacy Filter Control and boundaries · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  112. Single Sign-On (SSO) for Enterprise Authentication – Omnifact omnifact:omnifact:sso-blog

    Enterprise SAML2.0 supports optional SCIM, Id P policies and disabled email sign-in.

    Setup, benefits and changes · documented · Source date 2024-11-25 · Retrieved 2026-10-21

  113. GDPR-Compliant AI for Public Administration – Omnifact omnifact:omnifact:public-sector

    Public-sector page names Entra/Okta/Keycloak and Germany/municipal on-premise options.

    SSO, deployment and onboarding · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  114. Authentication - Omnifact omnifact:omnifact:auth

    TOTP, recovery codes and account/IP-specific throttling are described.

    2FA setup and failure handling · documented · Source date not stated · Retrieved 2026-10-21

  115. Security and Access - Omnifact omnifact:omnifact:security-rev2

    SSO/SAML users rely on identity-provider authentication and MFA and do not see native2FA setup. This does not establish nativeTOTP inclusion in a plan.

    SSO/SAML identity-provider authentication; native2FA tier not established · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

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

  123. Analytics - Omnifact omnifact:omnifact:analytics-rev2

    Enterprise dashboard presents daily active users and messages with date ranges and toggles; export and additional breakdowns are not established.

    Analytics heading, date-range selector, summary cards, activity chart; HTTP200 re-read2026-10-21 · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

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

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

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

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

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

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

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

  131. Company Profile - Omnifact omnifact:omnifact:company

    Company description and business context shape AI responses.

    Team Description and company identity · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

  138. EU Data Residency for Claude and Gemini via Google Cloud – Omnifact omnifact:omnifact:vertex

    Google/Anthropic EU via Google Cloud are advertised with zero retention and EU-only configuration.

    What is new, compliance and EU model configuration · vendor-claimed · Source date 2026-04-01 · Retrieved 2026-10-21

  139. https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust omnifact:omnifact:trust-rev2

    Public register lists Azure DE/NL/SE/IE infrastructure and Cloudflare EU/US edge metadata, plus model-provider routes; it is not a plan-specific processor/data-flow inventory.

    Public JSON subprocessors, lastUpdatedAt; infrastructure/metadata roles distinguished · documented · Source date 2026-10-21 · Retrieved 2026-10-21

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

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

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

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

  144. AI Gateway: One API for Every Model – Omnifact omnifact:omnifact:gateway-web

    Gateway consumes organization budget, does not store payloads and requires ZDR-capable models for strict retention.

    Regional routing, budget and governance · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  145. Why Data Privacy Matters - Omnifact omnifact:omnifact:privacy-intro

    Vendor explicitly excludes training its own models on customer data and distinguishes EU/self-hosted routes.

    Privacy Commitment and FAQ · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

  151. Legal Notice – Omnifact omnifact:omnifact:imprint

    Omnifact Gmb H is registered in Frankfurt, Germany, HRB131357.

    Company address and register · documented · Source date not stated · Retrieved 2026-10-21

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

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

  154. Auftragsverarbeitungsvertrag – Omnifact omnifact:omnifact:dpa-de

    Binding German DPA confirms region, transfer, retention and processor terms.

    Anlagen and main agreement · documented · Source date 2026-04-21 · Retrieved 2026-10-21

  155. Get Instant Access to our Full Enterprise Whitepaper – Omnifact omnifact:omnifact:whitepapers

    Public library includes AI Act, workplace enablement, self-hosting and RAG guides.

    Whitepaper catalogue · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  156. https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust omnifact:omnifact:trust

    Public Trust Center JSON exposes certificate access and named processor locations, including US direct model routes and Cloudflare telemetry.

    documents, subprocessors and lastUpdatedAt · documented · Source date 2026-10-21 · Retrieved 2026-10-21

  157. Omnifact GmbH ISO/IEC27001:2022 official certificate omnifact:omnifact:iso

    Certificate123228 issue1 from Prescient Security LLC covers Omnifact Platform/Spaces and Azure ISMS; valid2026-04-07 through 2029-04-06 subject to surveillance.

    Public Trust Center certificate PDF, one page: scope, issuer, issue date and validity · certificate-verified · Source date 2026-04-07 · Retrieved 2026-10-21
    Issuer: Prescient Security LLC. Scope: ISMS supporting Omnifact GmbH, Omnifact Platform and Spaces, associated data, infrastructure, software, personnel and procedures, including Microsoft Azure; SoA1.4 dated2026-03-30.. Valid 2026-04-07 to 2029-04-06

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

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

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

  161. ECB historical euro reference rates, 20 October 2026 omnifact:omnifact:ecb-fx

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

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

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

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

  164. omnifact-widget pinned README omnifact:omnifact:widget-rev2

    omnifact-widget documents an unsupported demonstration web component with local Storage conversations. This finding is documented at the pinned revision; no implementation behavior was tested or inspected.

    Pinned README.md documentation at commit 9d53cadfbfe1bd9a0e31b7da49b74a1dfc2626f2; retrieved with GitHub file connector · documented · Source date 2026-02-06 · Retrieved 2026-10-21

  165. omnifact-cli MIT licence omnifact:omnifact:cli-licence-rev2

    MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected.

    Pinned LICENSE documentation at commit 576aea6a6c0ce195de08a1d2b9b385d18efe3d06; retrieved with GitHub file connector · documented · Source date 2026-05-12 · Retrieved 2026-10-21

  166. omnifact-widget MIT licence omnifact:omnifact:widget-licence-rev2

    MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected.

    Pinned LICENSE documentation at commit 9d53cadfbfe1bd9a0e31b7da49b74a1dfc2626f2; retrieved with GitHub file connector · documented · Source date 2026-02-06 · Retrieved 2026-10-21

  167. n8n-nodes-omnifact MIT licence omnifact:omnifact:n8n-nodes-omnifact-licence-rev2

    MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected.

    Pinned LICENSE documentation at commit 7a3947c620206d4e195064421db525aaa4dfb50a; retrieved with GitHub file connector · documented · Source date 2026-09-10 · Retrieved 2026-10-21

  168. omnifact-xwiki-sync MIT licence omnifact:omnifact:xwiki-sync-licence-rev2

    MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected.

    Pinned LICENSE documentation at commit 599db2ec0c7f28ddb2a22c4a09a9242e5781316b; retrieved with GitHub file connector · documented · Source date 2026-08-25 · Retrieved 2026-10-21

  169. omnifact-cli pinned README omnifact:omnifact:cli-rev2

    omnifact-cli documents document management and conversational CLI commands. This finding is documented at the pinned revision; no implementation behavior was tested or inspected.

    Pinned README.md documentation at commit 576aea6a6c0ce195de08a1d2b9b385d18efe3d06; retrieved with GitHub file connector · documented · Source date 2026-05-12 · Retrieved 2026-10-21

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

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

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

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