--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/anythingllm-vs-cohere-north/" data_url: "https://onaihq.com/compare/agents/anythingllm-vs-cohere-north/data.json" generated_at: 2026-10-27 last_checked_at: 2026-10-26 last_cross_checked_at: 2026-10-26 next_check_at: 2026-12-20 publisher: "onAI" --- # AnythingLLM vs Cohere North > 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. > Cohere North lifecycle: sunset. Version-scoped component migration: legacy Jira removed in North 2.0; legacy Google Drive and guardrail REST slated for removal in 2.1, Salesforce legacy and Data Interpreter deprecated without a fixed date. Whole North continues. Scope: Legacy North connectors/APIs/Data Interpreter only; customer upgrade version determines removal. Continuation: New Jira/Google Drive/Salesforce tools, guardrail gRPC and Code sandbox replace legacy paths; connection recreation or application migration may be required. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-north-changelog, cohere-north:cohere-north:n-doc-36. This comparison has 45 criteria with sourced findings for both products, including 45 that a second agent cross-checked for both. 50 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. It does not declare a winner. A missing sourced finding is not evidence that a capability is absent. - AnythingLLM source checks: 2026-10-21 to 2026-10-26. - Cohere North source checks: 2026-10-21 to 2026-10-26. - Canonical HTML: https://onaihq.com/compare/agents/anythingllm-vs-cohere-north/ - Machine-readable JSON: https://onaihq.com/compare/agents/anythingllm-vs-cohere-north/data.json - Methodology: https://onaihq.com/compare/agents/methodology/ ## Models ### MOD-01: Model catalogue and providers Judgment rule: List each available model by provider and plan, including reasoning, fast and multimodal variants. Record whether the user picks the model, the product routes automatically, or both. A provider counts only if at least one of its current models is selectable on the scoped plan. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The customer selects provider/model combinations at system, workspace and Agent level; optional routing can choose per message. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - providers: Documented integrations include OpenAI, Azure, Anthropic, Google, Bedrock, Mistral, Cohere, OpenRouter, LiteLLM and local servers. Actual selectable models require configured accounts/endpoints; no endpoint was exercised. - current_models: Which current models are selectable on this plan? A complete current selectable-model catalog was not captured from configured provider accounts. - auto_routing: Model Router supports ordered rules and a fallback model, including LLM-classified rules. A complete chosen-model display/test was not established. - multimodal_input: System/workspace routes can accept image input with compatible models; exact audio/file and per-model behavior was not tested. - providers — Which model providers are available? [partial]: Documented integrations include OpenAI, Azure, Anthropic, Google, Bedrock, Mistral, Cohere, OpenRouter, LiteLLM and local servers. Actual selectable models require configured accounts/endpoints; no endpoint was exercised. Sources: anythingllm:anythingllm:models, anythingllm:anythingllm:llmconfig. - current_models — Which current models are selectable on this plan? [unknown]: current_models: Which current models are selectable on this plan? A complete current selectable-model catalog was not captured from configured provider accounts. - user_choice — Can users pick the model per chat? [supported]: System/workspace/Agent selections are configurable; the current built-in provider also has a chat model picker. Sources: anythingllm:anythingllm:llmconfig, anythingllm:anythingllm:built-in. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [partial]: Model Router supports ordered rules and a fallback model, including LLM-classified rules. A complete chosen-model display/test was not established. Sources: anythingllm:anythingllm:router. - multimodal_input — Which models accept images, audio or files? [partial]: System/workspace routes can accept image input with compatible models; exact audio/file and per-model behavior was not tested. Sources: anythingllm:anythingllm:models, anythingllm:anythingllm:constants-pin. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:models, anythingllm:anythingllm:llmconfig, anythingllm:anythingllm:built-in, anythingllm:anythingllm:router, anythingllm:anythingllm:constants-pin #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North supports customer-configured Cohere and external providers; deployed models determine availability. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha model-tier aliases and direct image input; North Mini separately Beta; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - current_models: The model card documents North Large 01-2026, and the October 16 release adds North Mini Beta. The Skills guide recommends additional external model identifiers, but those do not establish what any customer deployment has installed or licensed. - auto_routing: Documented resolution is group default, Default alias, then deployment default; inaccessible aliases silently fall back to provider default with a log warning. Automatic task-based routing across providers and UI disclosure of that fallback remain unknown. - multimodal_input: North Large 01-2026 accepts text/images,256K input and32K text output. Alpha image input is Cohere-only; visual parser handles PDF/DOCX/PPTX, including OCR. Dictation uses configured ASR; complete per-model matrix unknown. - providers — Which model providers are available? [supported]: Provider types include customer Cohere containers, Cohere Platform/compatibility, vLLM, Azure Cohere, Bedrock, SageMaker, Azure OpenAI, OpenAI and Anthropic. Sources: cohere-north:cohere-north:n-doc-177-20261026. - current_models — Which current models are selectable on this plan? [partial]: The model card documents North Large 01-2026, and the October 16 release adds North Mini Beta. The Skills guide recommends additional external model identifiers, but those do not establish what any customer deployment has installed or licensed. Sources: cohere-north:cohere-north:n-doc-32-20261026, cohere-north:cohere-north:north-release-html-20261026, cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:n-doc-134-20261026. - user_choice — Can users pick the model per chat? [supported]: Default-agent chat has a model picker; custom agents choose models in settings. Alpha tier picker aliases Default/Alternate/Legacy and can expose additional permitted models. Sources: cohere-north:cohere-north:n-doc-1-20261026, cohere-north:cohere-north:n-doc-134-20261026. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [partial]: Documented resolution is group default, Default alias, then deployment default; inaccessible aliases silently fall back to provider default with a log warning. Automatic task-based routing across providers and UI disclosure of that fallback remain unknown. Sources: cohere-north:cohere-north:n-doc-134-20261026. - multimodal_input — Which models accept images, audio or files? [partial]: North Large 01-2026 accepts text/images,256K input and32K text output. Alpha image input is Cohere-only; visual parser handles PDF/DOCX/PPTX, including OCR. Dictation uses configured ASR; complete per-model matrix unknown. Sources: cohere-north:cohere-north:n-doc-32-20261026, cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-97-20261026. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-177-20261026, cohere-north:cohere-north:n-doc-32-20261026, cohere-north:cohere-north:north-release-html-20261026, cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-1-20261026, cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-97-20261026 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dated releases and version-specific changelogs are public, but the three-release lag benchmark was not measured. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - release_lag_days: What was the lag for each of the last three major releases, per provider? No paired last-three-major-release availability dates or guaranteed model-deprecation notice window was established. The built-in Desktop engine migration removes old downloaded models when accepted. - deprecation_notice: How much notice is given before a model is removed? No paired last-three-major-release availability dates or guaranteed model-deprecation notice window was established. The built-in Desktop engine migration removes old downloaded models when accepted. - version_pinning: Operators choose remote model IDs or download local GGUF models. Provider retention of old remote snapshots is outside the application’s control. - release_lag_days — What was the lag for each of the last three major releases, per provider? [unknown]: release_lag_days: What was the lag for each of the last three major releases, per provider? No paired last-three-major-release availability dates or guaranteed model-deprecation notice window was established. The built-in Desktop engine migration removes old downloaded models when accepted. - changelog — Is there a dated public model changelog? [supported]: GitHub releases and Desktop changelogs document dated changes; v1.18.0 was published 2026-10-13. Sources: anythingllm:anythingllm:releases, anythingllm:anythingllm:changelog. - deprecation_notice — How much notice is given before a model is removed? [unknown]: deprecation_notice: How much notice is given before a model is removed? No paired last-three-major-release availability dates or guaranteed model-deprecation notice window was established. The built-in Desktop engine migration removes old downloaded models when accepted. - version_pinning — Can an admin keep an older model version? [partial]: Operators choose remote model IDs or download local GGUF models. Provider retention of old remote snapshots is outside the application’s control. Sources: anythingllm:anythingllm:generic, anythingllm:anythingllm:built-in. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:releases, anythingllm:anythingllm:changelog, anythingllm:anythingllm:generic, anythingllm:anythingllm:built-in #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dated platform notes and operator-pinned model artifacts exist; provider release lag is unknown. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: release_lag_days, deprecation_notice. - release_lag_days — What was the lag for each of the last three major releases, per provider? [unknown]: Unknown for release_lag_days. No matched provider/product dates for the last three releases or contractual model-removal notice period was retrieved. - changelog — Is there a dated public model changelog? [supported]: Public North release notes through October 20 v2.0.1 include model and feature changes. Sources: cohere-north:cohere-north:n-north-changelog. - deprecation_notice — How much notice is given before a model is removed? [unknown]: Unknown for deprecation_notice. No matched provider/product dates for the last three releases or contractual model-removal notice period was retrieved. - version_pinning — Can an admin keep an older model version? [partial]: Self-hosted serving images/model artifacts are versioned independently; operators select image tags/digests. This does not guarantee retention of external API model versions. Sources: cohere-north:cohere-north:n-doc-168. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-north-changelog, cohere-north:cohere-north:n-doc-168 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial BYO provider keys, customer cloud contracts and generic compatible endpoints are documented; provider spend is separate from software licensing. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - byo_restrictions: Tool use and modalities depend on provider/model support; Cloud has additional explicit platform limits. No universal BYO feature-parity guarantee was established. - own_api_keys — Can the customer use its own provider API keys? [supported]: Customers configure credentials for their selected cloud providers. Managed Cloud also asks customers to bring an LLM API key. Sources: anythingllm:anythingllm:models, anythingllm:anythingllm:cloud. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [supported]: Azure OpenAI, AWS Bedrock and Vertex have distinct documented configuration routes using customer accounts. Sources: anythingllm:anythingllm:azure, anythingllm:anythingllm:bedrock, anythingllm:anythingllm:vertex. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [supported]: Generic OpenAI supports an operator-configured compatible provider URL and settings. Sources: anythingllm:anythingllm:generic. - byo_pricing — Does BYO change the licence price? [supported]: The self-hosted repository is MIT with no per-seat fee; customer provider/hosting costs remain separate. Cloud charges for the managed instance and still uses BYO inference. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cloud. - byo_restrictions — Which features stop working with BYO? [partial]: Tool use and modalities depend on provider/model support; Cloud has additional explicit platform limits. No universal BYO feature-parity guarantee was established. Sources: anythingllm:anythingllm:cloud-limits, anythingllm:anythingllm:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:models, anythingllm:anythingllm:cloud, anythingllm:anythingllm:azure, anythingllm:anythingllm:bedrock, anythingllm:anythingllm:vertex, anythingllm:anythingllm:generic, anythingllm:anythingllm:license, anythingllm:anythingllm:cloud-limits #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North documents own keys, cloud deployments and OpenAI-compatible endpoints. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha direct image input restriction; provider registration is separately scoped; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - own_cloud_contract: Own Azure OpenAI, Bedrock Cohere/Anthropic and SageMaker endpoints documented. Foundry can bill supported inference to customer Azure subscription; Vertex integration not established. - byo_pricing: Unknown for byo_pricing. Provider configuration is documented; commercial BYO discounts and complete feature parity across every provider remain unknown. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/models?format=html, https://private.docs.cohere.com/north/docs/advanced/headless-configuration/model-providers?format=html, https://private.docs.cohere.com/north/docs/admin/bedrock-anthropic?format=html. No additional scoped evidence established this answer. - byo_restrictions: Alpha direct image input currently requires Cohere models. Foundry lacks North Large/sparse and Compass keyless model authentication; complete per-provider feature parity remains unknown. - own_api_keys — Can the customer use its own provider API keys? [supported]: Provider registration accepts customer API keys or identity tokens; declarative providers reference Kubernetes Secrets. Sources: cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-177-20261026. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Own Azure OpenAI, Bedrock Cohere/Anthropic and SageMaker endpoints documented. Foundry can bill supported inference to customer Azure subscription; Vertex integration not established. Sources: cohere-north:cohere-north:n-doc-177-20261026, cohere-north:cohere-north:n-doc-135-20261026, cohere-north:cohere-north:n-doc-218-20261026. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [supported]: OpenAI provider base_url can point at compatible endpoints; vLLM and Cohere compatibility provider types also supported. Actual compatibility still depends on model/tool schema. Sources: cohere-north:cohere-north:n-doc-177-20261026. - byo_pricing — Does BYO change the licence price? [unknown]: Unknown for byo_pricing. Provider configuration is documented; commercial BYO discounts and complete feature parity across every provider remain unknown. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/models?format=html, https://private.docs.cohere.com/north/docs/advanced/headless-configuration/model-providers?format=html, https://private.docs.cohere.com/north/docs/admin/bedrock-anthropic?format=html. No additional scoped evidence established this answer. - byo_restrictions — Which features stop working with BYO? [partial]: Alpha direct image input currently requires Cohere models. Foundry lacks North Large/sparse and Compass keyless model authentication; complete per-provider feature parity remains unknown. Sources: cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-218-20261026. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-177-20261026, cohere-north:cohere-north:n-doc-135-20261026, cohere-north:cohere-north:n-doc-218-20261026, cohere-north:cohere-north:n-doc-14-20261026 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Local chat and local CPU embeddings are documented; built-in-engine availability differs by client and release. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - feature_parity: Chat/RAG are local-capable, but tools and vision depend on model support and optional online services. Cloud explicitly has no bundled built-in LLM. No full offline fixture was run. - vendor_hosted_open_models: Does the vendor host open-weight models in EU/CH? No vendor-hosted open-weight model service with verified EU/Swiss inference was established. - self_hosted_chat — Can chat use a customer-hosted model? [supported]: Ollama and other local providers work as configured endpoints. Desktop’s current built-in engine uses Lemonade/llama.cpp; Docker built-in is opt-in on the latest images and releases after v1.18.0 according to current docs. Sources: anythingllm:anythingllm:ollama, anythingllm:anythingllm:built-in. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [supported]: The built-in all-MiniLM-L6-v2 embedder runs locally on CPU; other local embedding routes are configurable. Sources: anythingllm:anythingllm:local-embed, anythingllm:anythingllm:embed. - feature_parity — Which features fail with self-hosted models? [partial]: Chat/RAG are local-capable, but tools and vision depend on model support and optional online services. Cloud explicitly has no bundled built-in LLM. No full offline fixture was run. Sources: anythingllm:anythingllm:models, anythingllm:anythingllm:cloud-limits, anythingllm:anythingllm:built-in. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [unknown]: vendor_hosted_open_models: Does the vendor host open-weight models in EU/CH? No vendor-hosted open-weight model service with verified EU/Swiss inference was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:ollama, anythingllm:anythingllm:built-in, anythingllm:anythingllm:local-embed, anythingllm:anythingllm:embed, anythingllm:anythingllm:models, anythingllm:anythingllm:cloud-limits #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North chat and retrieval models can run in customer infrastructure. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: vendor_hosted_open_models. - self_hosted_chat — Can chat use a customer-hosted model? [supported]: Customer Cohere serving containers and vLLM endpoints are supported; independent model chart deploys generative services in customer GPU clusters. Sources: cohere-north:cohere-north:n-doc-177, cohere-north:cohere-north:n-doc-168. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [partial]: Packed Compass provides local dense embeddings, sparse and rerank. Operator connects North/Compass to these services; arbitrary embedding model compatibility was not established. Sources: cohere-north:cohere-north:n-doc-168. - feature_parity — Which features fail with self-hosted models? [partial]: Local visual processing needs parser/GPU deployment; hosted search/MCP needs egress. Foundry lacks sparse/North Large, so mixed inference required there. No full disconnected parity matrix retrieved. Sources: cohere-north:cohere-north:n-doc-14, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-218. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [unknown]: Unknown for vendor_hosted_open_models. Self-hosted Cohere models and Compass are documented; arbitrary embedding-model compatibility and a Cohere-operated EU/CH open-model hosting SKU were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-177, cohere-north:cohere-north:n-doc-168, cohere-north:cohere-north:n-doc-14, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-218 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workspace models and admin roles control settings; non-admin multi-user message quotas have a source-inspected blocking path. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - model_allowlist_by_group: Can admins limit models per group? A group-based model allow-list and hard source-data/provider-binding policy were not established in the role and workspace guides. No two-group quota or model restriction fixture was run. - data_bound_models: Can admins restrict which models receive connector or knowledge content? A group-based model allow-list and hard source-data/provider-binding policy were not established in the role and workspace guides. No two-group quota or model restriction fixture was run. - model_allowlist_by_group — Can admins limit models per group? [unknown]: model_allowlist_by_group: Can admins limit models per group? A group-based model allow-list and hard source-data/provider-binding policy were not established in the role and workspace guides. No two-group quota or model restriction fixture was run. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [unknown]: data_bound_models: Can admins restrict which models receive connector or knowledge content? A group-based model allow-list and hard source-data/provider-binding policy were not established in the role and workspace guides. No two-group quota or model restriction fixture was run. - default_model — Can admins set the default model? [supported]: The system LLM is the default, overridden by workspace and Agent model configuration. Sources: anythingllm:anythingllm:llmconfig. - user_limits — What per-user message or token limits apply, and are they published? [supported]: A dailyMessageLimit may be set per user, is system-wide across workspaces, uses a trailing 24-hour count and exempts admins; null means no limit in the inspected function. Sources: anythingllm:anythingllm:user-pin. - limit_behaviour — What happens when a limit is reached? [supported]: Pinned chat endpoints send an abort/quota message and return before generation when the user cannot send another chat. Sources: anythingllm:anythingllm:chat-pin. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:llmconfig, anythingllm:anythingllm:user-pin, anythingllm:anythingllm:chat-pin #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Group model controls have additive and shared-agent exceptions; alpha limits require deployment. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha model RBAC and Flow control; Models UI separately Beta; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - data_bound_models: Unknown for data_bound_models. Model RBAC and alpha rate limits are documented; content-bound model exclusion and measured enforcement were not tested. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/models?format=html, https://private.docs.cohere.com/north/docs/get-started/agents/creating-custom-agents?format=html, https://private.docs.cohere.com/north/docs/admin/flow-control?format=html. No additional scoped evidence established this answer. - user_limits: Alpha Flow control supports requests/input/output tokens by user/group/model/source/provider and time window. Limits default unlimited; no fixed commercial message allowance was retrieved. - limit_behaviour: Configured limits block until window resets. Enforcement requires Helm proxy services; UI alone does nothing. Failure policy may allow or deny requests and token estimation is optional; actual overshoot untested. - model_allowlist_by_group — Can admins limit models per group? [supported]: Beta Models UI configures provider/model user/group access; alpha model RBAC must be enabled. Provider OR model grants access, admins bypass; shared agents use owner permissions, not each recipient. Sources: cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-18-20261026. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [unknown]: Unknown for data_bound_models. Model RBAC and alpha rate limits are documented; content-bound model exclusion and measured enforcement were not tested. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/models?format=html, https://private.docs.cohere.com/north/docs/get-started/agents/creating-custom-agents?format=html, https://private.docs.cohere.com/north/docs/admin/flow-control?format=html. No additional scoped evidence established this answer. - default_model — Can admins set the default model? [supported]: Group defaults precede Default tier and deployment default. Aliases are per deployment and initially empty. Sources: cohere-north:cohere-north:n-doc-134-20261026. - user_limits — What per-user message or token limits apply, and are they published? [partial]: Alpha Flow control supports requests/input/output tokens by user/group/model/source/provider and time window. Limits default unlimited; no fixed commercial message allowance was retrieved. Sources: cohere-north:cohere-north:n-doc-137-20261026. - limit_behaviour — What happens when a limit is reached? [partial]: Configured limits block until window resets. Enforcement requires Helm proxy services; UI alone does nothing. Failure policy may allow or deny requests and token estimation is optional; actual overshoot untested. Sources: cohere-north:cohere-north:n-doc-137-20261026. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-18-20261026, cohere-north:cohere-north:n-doc-137-20261026 ## 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Files can enter full context or workspace RAG; converters and a PDF OCR fallback are present, with fidelity untested. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - limits: What size and count limits apply per file and chat? No universal file/count limit was established across these deployments. Cloud documents CPU/memory limits, but they do not define a tested per-file allowance. Shared long/scanned/Excel/PowerPoint fixtures were not uploaded. - ocr: The PDF implementation attempts OCR when initial text extraction returns no pages. No scanned contract or mixed-content PDF was tested. - spreadsheets: XLSX conversion is registered and v1.18.0 reports spreadsheet parsing fixes; preservation of formula semantics and layout was not tested. - formats — Which formats are accepted? [supported]: Pinned converters register PDF, DOCX, PPTX, XLSX, EPUB, text/CSV/JSON, image and audio formats. Legacy DOC is not in the active registered converter map. Sources: anythingllm:anythingllm:constants-pin. - limits — What size and count limits apply per file and chat? [unknown]: limits: What size and count limits apply per file and chat? No universal file/count limit was established across these deployments. Cloud documents CPU/memory limits, but they do not define a tested per-file allowance. Shared long/scanned/Excel/PowerPoint fixtures were not uploaded. - ocr — Are scanned PDFs read? [partial]: The PDF implementation attempts OCR when initial text extraction returns no pages. No scanned contract or mixed-content PDF was tested. Sources: anythingllm:anythingllm:pdf-pin. - spreadsheets — Are Excel tables read with structure intact? [partial]: XLSX conversion is registered and v1.18.0 reports spreadsheet parsing fixes; preservation of formula semantics and layout was not tested. Sources: anythingllm:anythingllm:constants-pin, anythingllm:anythingllm:changelog. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [supported]: Current attachment mode injects full extracted text. On context overflow the UI offers cancellation, pruning or embedding; embedded documents retrieve chunks and become workspace-wide. Sources: anythingllm:anythingllm:docchat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:constants-pin, anythingllm:anythingllm:pdf-pin, anythingllm:anythingllm:changelog, anythingllm:anythingllm:docchat #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Broad file formats and optional OCR are documented; the effective My files size limit for a deployment remains unknown. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - limits: The effective My files default is unknown: its dedicated guide states 50 MB/file subject to configuration, while Supported files describes a 100 MB limit across all files. Neither is asserted as the verified deployment limit. Separately, chat images are limited to 20/message, 5 MB/image and 20 MB total; the supported-files guide lists 500 MB for SharePoint/OneDrive. - ocr: Vision parser can OCR scanned PDFs and extract visual tables; alpha setup requires smart parser and hosted vision parser. More than500 visual pages fall back to pure text processing. No scan test run. - spreadsheets: The supported-files guide says spreadsheet rows are not indexed for ordinary search and requires Data Interpreter for tabular prompts. Beta Skills also provide spreadsheet/CSV file operations through the code sandbox. Workbook formula/structure fidelity has not been tested. - full_vs_chunked: The SharePoint and OneDrive implementation guides remain inaccessible in Markdown, HTML and page-level index forms on 2026-10-26. Retrieved My files and multimodality guides do not establish universal full-file/chunk thresholds or prompt-context disclosure. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/get-started/supported-files?format=html, https://private.docs.cohere.com/north/docs/get-started/north-automations/building-automations/north-multimodality?format=html, https://private.docs.cohere.com/north/docs/get-started/tools/my-files/home?format=html. No additional scoped evidence established this answer. - formats — Which formats are accepted? [supported]: Office/PDF/text/HTML/email/JSON/XML/EPUB and tabular formats; common images, audio/video with parser enabled. Upload/index support differs from preview and individual vision model support. Sources: cohere-north:cohere-north:n-doc-73-20261026, cohere-north:cohere-north:n-doc-14-20261026. - limits — What size and count limits apply per file and chat? [partial]: The effective My files default is unknown: its dedicated guide states 50 MB/file subject to configuration, while Supported files describes a 100 MB limit across all files. Neither is asserted as the verified deployment limit. Separately, chat images are limited to 20/message, 5 MB/image and 20 MB total; the supported-files guide lists 500 MB for SharePoint/OneDrive. Sources: cohere-north:cohere-north:n-doc-66-20261026, cohere-north:cohere-north:n-doc-73-20261026, cohere-north:cohere-north:n-doc-1-20261026. - ocr — Are scanned PDFs read? [partial]: Vision parser can OCR scanned PDFs and extract visual tables; alpha setup requires smart parser and hosted vision parser. More than500 visual pages fall back to pure text processing. No scan test run. Sources: cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-100-20261026. - spreadsheets — Are Excel tables read with structure intact? [partial]: The supported-files guide says spreadsheet rows are not indexed for ordinary search and requires Data Interpreter for tabular prompts. Beta Skills also provide spreadsheet/CSV file operations through the code sandbox. Workbook formula/structure fidelity has not been tested. Sources: cohere-north:cohere-north:n-doc-73-20261026, cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:north-release-html-20261026. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [unknown]: The SharePoint and OneDrive implementation guides remain inaccessible in Markdown, HTML and page-level index forms on 2026-10-26. Retrieved My files and multimodality guides do not establish universal full-file/chunk thresholds or prompt-context disclosure. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/get-started/supported-files?format=html, https://private.docs.cohere.com/north/docs/get-started/north-automations/building-automations/north-multimodality?format=html, https://private.docs.cohere.com/north/docs/get-started/tools/my-files/home?format=html. No additional scoped evidence established this answer. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-73-20261026, cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-66-20261026, cohere-north:cohere-north:n-doc-1-20261026, cohere-north:cohere-north:n-doc-100-20261026, cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:north-release-html-20261026 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workspace embeddings persist across chats and are shared with every authorized workspace user. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - size_limits: What are the collection limits? No fixed collection storage allowance was established; capacity depends on local hardware or managed-instance tier. - persistent_collections — Can users keep document collections across chats? [supported]: Embedding a document into a workspace makes it reusable across that workspace’s threads. Sources: anythingllm:anythingllm:docchat. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: In Docker multi-user mode, assigned workspace users can use its embedded documents. Admin/Manager roles have broader access; per-original-source ACLs were not established. Sources: anythingllm:anythingllm:docchat, anythingllm:anythingllm:security. - size_limits — What are the collection limits? [unknown]: size_limits: What are the collection limits? No fixed collection storage allowance was established; capacity depends on local hardware or managed-instance tier. - assistant_binding — Can collections be bound to an assistant? [supported]: Each workspace has configurable chat/Agent models and its embedded knowledge. Sources: anythingllm:anythingllm:llmconfig, anythingllm:anythingllm:docchat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:docchat, anythingllm:anythingllm:security, anythingllm:anythingllm:llmconfig #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Beta Libraries persist shared source collections; alpha Projects are separate private workspaces. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha Projects; Libraries separately Beta; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - size_limits: Alpha Projects default to a 2 GiB aggregate allowance per user across projects. Beta Libraries/uploads use administrator-configured file-size/count settings; complete effective deployment limits were not retrieved. - persistent_collections — Can users keep document collections across chats? [supported]: Libraries reuse uploaded/My files/Google/Microsoft collections across agents/chats/nodes. Alpha Projects index separate private project files. Sources: cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-11-20261026. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: Libraries support user/group/company access with source-dependent roles; Outlook/Exchange remain private. Attaching library to shared agent does not grant library access. Sources: cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-133-20261026. - size_limits — What are the collection limits? [partial]: Alpha Projects default to a 2 GiB aggregate allowance per user across projects. Beta Libraries/uploads use administrator-configured file-size/count settings; complete effective deployment limits were not retrieved. Sources: cohere-north:cohere-north:n-doc-11-20261026, cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-66-20261026. - assistant_binding — Can collections be bound to an assistant? [supported]: Agent Resources bind persistent libraries; composer attachment applies to one chat only. Shared recipients must already have library Viewer access. Sources: cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-18-20261026. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-11-20261026, cohere-north:cohere-north:n-doc-133-20261026, cohere-north:cohere-north:n-doc-66-20261026, cohere-north:cohere-north:n-doc-18-20261026 ### 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). #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The source registers import connectors and SQL tools. Mail integrations are single-user features, not verified enterprise multi-user content search. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=Source-specific credentials/registrations, Mail skills require single-user mode; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - microsoft_365: An Outlook skill searches/reads/modifies the connected mailbox, but is explicitly single-user only. SharePoint, OneDrive and Teams connectors were not verified for the multi-user deployment. - google_workspace: The Gmail skill is single-user only. A maintained Google Drive enterprise connector and source ACL sync were not verified. - atlassian: The pinned connector catalog includes Confluence import. Jira was not established and Confluence per-user permission synchronization was not tested. - other_systems: The connector catalog includes GitHub/GitLab/Gitea, websites, YouTube, Obsidian and other import sources; registration does not establish tested source access controls. - on_prem_sources: Self-hosted deployments can upload files and connect the SQL Agent to a reachable database. Automatic local-file watching is Desktop-only, not Docker browser upload. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: An Outlook skill searches/reads/modifies the connected mailbox, but is explicitly single-user only. SharePoint, OneDrive and Teams connectors were not verified for the multi-user deployment. Sources: anythingllm:anythingllm:outlook. - google_workspace — Which Google sources are connected? [partial]: The Gmail skill is single-user only. A maintained Google Drive enterprise connector and source ACL sync were not verified. Sources: anythingllm:anythingllm:gmail. - atlassian — Confluence and Jira? [partial]: The pinned connector catalog includes Confluence import. Jira was not established and Confluence per-user permission synchronization was not tested. Sources: anythingllm:anythingllm:connectors-pin, anythingllm:anythingllm:sync. - other_systems — Which other business systems? [partial]: The connector catalog includes GitHub/GitLab/Gitea, websites, YouTube, Obsidian and other import sources; registration does not establish tested source access controls. Sources: anythingllm:anythingllm:connectors-pin. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Self-hosted deployments can upload files and connect the SQL Agent to a reachable database. Automatic local-file watching is Desktop-only, not Docker browser upload. Sources: anythingllm:anythingllm:sql, anythingllm:anythingllm:sync, anythingllm:anythingllm:localdocker. - connector_provider — Who builds and maintains each connector? [supported]: These are built-in Mintplex project skills/import modules; third-party MCP servers remain separately maintained integrations. Sources: anythingllm:anythingllm:connectors-pin, anythingllm:anythingllm:outlook, anythingllm:anythingllm:gmail, anythingllm:anythingllm:mcp. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:outlook, anythingllm:anythingllm:gmail, anythingllm:anythingllm:connectors-pin, anythingllm:anythingllm:sync, anythingllm:anythingllm:sql, anythingllm:anythingllm:localdocker, anythingllm:anythingllm:mcp #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North has first-party connectors, custom MCP and an on-prem SharePoint Server path. Availability: unknown Delivery: official-integration Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North 2.0.1; Notion/Linear first-party MCP Beta; SharePoint Server Alpha; other connector states per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - microsoft_365: The North 2 announcement names SharePoint, OneDrive, Outlook and Exchange. The October 16 release separately documents read-only Outlook Calendar as alpha. Teams connector entitlement was not established. - google_workspace: The retrieved sync guide distinguishes indexed Google Drive Libraries from live Full Access Drive queries. Gmail is documented, but its storage/sync behavior remains unknown because the Syncing and Sharing guides disagree. Google Calendar was not established. - atlassian: North 2 names Jira among its connectors. Versioned release notes remove the legacy Jira path in 2.0; no Confluence connector entitlement was established. - other_systems: The current North 2 announcement names Slack, Linear, Notion and GitHub. The October 16 release describes Salesforce and PitchBook as alpha features. Customer/third-party MCP connections remain separately configured and licensed. - on_prem_sources: The SharePoint Server connector setup is explicitly Alpha. Customer in-network MCP may expose other systems; a native SMB/database inventory and its source-permission guarantees remain unverified. - connector_provider: Cohere documents its North connector families and a distinct customer/third-party remote MCP setup. Exact connector-specific maintenance and service commitments require the applicable contract. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: The North 2 announcement names SharePoint, OneDrive, Outlook and Exchange. The October 16 release separately documents read-only Outlook Calendar as alpha. Teams connector entitlement was not established. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:north-release-html-20261026. - google_workspace — Which Google sources are connected? [partial]: The retrieved sync guide distinguishes indexed Google Drive Libraries from live Full Access Drive queries. Gmail is documented, but its storage/sync behavior remains unknown because the Syncing and Sharing guides disagree. Google Calendar was not established. Sources: cohere-north:cohere-north:n-doc-151-20261026, cohere-north:cohere-north:n-doc-152-20261026, cohere-north:cohere-north:north-release-html-20261026. - atlassian — Confluence and Jira? [partial]: North 2 names Jira among its connectors. Versioned release notes remove the legacy Jira path in 2.0; no Confluence connector entitlement was established. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:north-release-html-20261026. - other_systems — Which other business systems? [partial]: The current North 2 announcement names Slack, Linear, Notion and GitHub. The October 16 release describes Salesforce and PitchBook as alpha features. Customer/third-party MCP connections remain separately configured and licensed. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:north-release-html-20261026, cohere-north:cohere-north:n-doc-126-20261026. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: The SharePoint Server connector setup is explicitly Alpha. Customer in-network MCP may expose other systems; a native SMB/database inventory and its source-permission guarantees remain unverified. Sources: cohere-north:cohere-north:n-doc-53-20261026, cohere-north:cohere-north:n-doc-126-20261026. - connector_provider — Who builds and maintains each connector? [partial]: Cohere documents its North connector families and a distinct customer/third-party remote MCP setup. Exact connector-specific maintenance and service commitments require the applicable contract. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:n-doc-126-20261026. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:north-release-html-20261026, cohere-north:cohere-north:n-doc-151-20261026, cohere-north:cohere-north:n-doc-152-20261026, cohere-north:cohere-north:n-doc-126-20261026, cohere-north:cohere-north:n-doc-53-20261026 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workspace access is enforced as the product sharing boundary; original source permissions after copying remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - source_permissions_respected: Are source permissions enforced per user? No restricted-document two-user fixture or grant/revocation propagation test was run. Purview label enforcement and source ACL fidelity remain unknown. - enforcement_point: Default users only access assigned workspaces, and an embedded file becomes available to every user assigned to its workspace. Continuing source-system ACL checks were not established. - revocation_delay: How quickly does a removed permission take effect? No restricted-document two-user fixture or grant/revocation propagation test was run. Purview label enforcement and source ACL fidelity remain unknown. - admin_scope_controls: Admins control workspace membership and selected documents. Source site/folder/sensitivity-label exclusion was not established. - sensitivity_labels: Are Microsoft Purview or similar labels respected? No restricted-document two-user fixture or grant/revocation propagation test was run. Purview label enforcement and source ACL fidelity remain unknown. - source_permissions_respected — Are source permissions enforced per user? [unknown]: source_permissions_respected: Are source permissions enforced per user? No restricted-document two-user fixture or grant/revocation propagation test was run. Purview label enforcement and source ACL fidelity remain unknown. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [partial]: Default users only access assigned workspaces, and an embedded file becomes available to every user assigned to its workspace. Continuing source-system ACL checks were not established. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:docchat. - revocation_delay — How quickly does a removed permission take effect? [unknown]: revocation_delay: How quickly does a removed permission take effect? No restricted-document two-user fixture or grant/revocation propagation test was run. Purview label enforcement and source ACL fidelity remain unknown. - admin_scope_controls — Can admins exclude sites, folders or labels? [partial]: Admins control workspace membership and selected documents. Source site/folder/sensitivity-label exclusion was not established. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:docchat. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [unknown]: sensitivity_labels: Are Microsoft Purview or similar labels respected? No restricted-document two-user fixture or grant/revocation propagation test was run. Purview label enforcement and source ACL fidelity remain unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:docchat #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Indexed retrieval adds runtime source checks; shared snapshots have a separate visibility boundary. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: sensitivity_labels. - source_permissions_respected — Are source permissions enforced per user? [partial]: Atlas retrieval checks agent scope and user source access; permission-check errors exclude files. This does not re-protect already generated shared chat snapshots; no ACL fixture run. Sources: cohere-north:cohere-north:n-doc-152, cohere-north:cohere-north:n-doc-4. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: Compass retrieves indexed candidates, then Atlas/source API checks filter permissioned documents. Google Drive Full Access queries source directly; local uploads use North sharing rules. Sources: cohere-north:cohere-north:n-doc-152, cohere-north:cohere-north:n-doc-151. - revocation_delay — How quickly does a removed permission take effect? [partial]: Authorization guide claims external permission changes apply immediately; token/group membership refresh and caches are separate. No measured revocation SLA or fixture. Sources: cohere-north:cohere-north:n-doc-149, cohere-north:cohere-north:n-doc-111. - admin_scope_controls — Can admins exclude sites, folders or labels? [partial]: Selected sites/folders/files scope Atlas ingestion; library and tool grants scope users/groups. Label-based exclusions not established. Sources: cohere-north:cohere-north:n-doc-64, cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-126. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [unknown]: Unknown for sensitivity_labels. No two-user ACL revocation or sensitivity-label fixture was run; source API permission claims remain documented, not observed. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-152, cohere-north:cohere-north:n-doc-4, cohere-north:cohere-north:n-doc-151, cohere-north:cohere-north:n-doc-149, cohere-north:cohere-north:n-doc-111, cohere-north:cohere-north:n-doc-64, cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-126 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Knowledge is a copied index. Automatic source refresh is preview and differs between remote sources and Desktop local files. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=Live document sync preview explicitly enabled for automatic refresh; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - Automatic sync is a preview, not a guaranteed freshness SLA. - No source edit/delete timing fixture was run. - live_or_indexed — Is content searched live or copied into an index? [supported]: Embedded knowledge copies parsed chunks into the selected vector store; attachments instead inject extracted text. Sources: anythingllm:anythingllm:docchat, anythingllm:anythingllm:vector. - sync_interval — How often does an index refresh? [partial]: Preview watched remote sources are checked hourly for staleness, defined as no refresh in seven days; Desktop local watched files are checked every ten minutes while running. No latency fixture was run. Sources: anythingllm:anythingllm:sync. - deletion_propagation — How quickly does a deleted document disappear? [partial]: Deleting a watched local original marks it Not Found and unwatches it while retaining existing content/embeddings. System deletion must be explicit; remote-source deletion timing was not established. Sources: anythingllm:anythingllm:sync, anythingllm:anythingllm:privacy. - index_location — Where is indexed content stored? [supported]: Self-hosting selects the configured local or external vector store and its country. Default local storage is distinct from any selected cloud database. Sources: anythingllm:anythingllm:vector, anythingllm:anythingllm:localdocker. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:docchat, anythingllm:anythingllm:vector, anythingllm:anythingllm:sync, anythingllm:anythingllm:privacy, anythingllm:anythingllm:localdocker #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Atlas file connectors copy selected content to Compass; Drive Full Access uses live API calls. Effective Gmail storage/sync behavior remains unknown. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - live_or_indexed: Atlas file connectors copy selected files to Compass. Google Drive Full Access calls the live API instead. Gmail storage is unknown: the Data Syncing guide says no Compass copy by default, while Data Sharing and the tools overview describe stored/synced email. No live-only Gmail guarantee is asserted. - sync_interval: The accessible Data Syncing guide describes periodic Atlas updates and source changes appearing within minutes to hours depending on volume. Drive Full Access is request-time. The previously cited SharePoint/OneDrive 10-minute implementation detail could not be re-retrieved and is not asserted. - deletion_propagation: The source-specific SharePoint/OneDrive implementation and Data Deletion pages remain inaccessible in public Markdown/HTML/index forms. General sync documentation does not establish a bounded delete-to-answer or purge interval. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/security/data-syncing?format=html, https://private.docs.cohere.com/north/docs/security/data-sharing?format=html, https://private.docs.cohere.com/north/docs/get-started/tools-overview.md. No additional scoped evidence established this answer. - index_location: Compass runs with the customer-controlled North deployment, whose cloud/on-premise placement is selected by the operator. Foundry inference is separately routed to the customer Azure subscription. A universal vendor-hosted index country is not established. - live_or_indexed — Is content searched live or copied into an index? [partial]: Atlas file connectors copy selected files to Compass. Google Drive Full Access calls the live API instead. Gmail storage is unknown: the Data Syncing guide says no Compass copy by default, while Data Sharing and the tools overview describe stored/synced email. No live-only Gmail guarantee is asserted. Sources: cohere-north:cohere-north:n-doc-151-20261026, cohere-north:cohere-north:n-doc-152-20261026, cohere-north:cohere-north:n-doc-33. - sync_interval — How often does an index refresh? [partial]: The accessible Data Syncing guide describes periodic Atlas updates and source changes appearing within minutes to hours depending on volume. Drive Full Access is request-time. The previously cited SharePoint/OneDrive 10-minute implementation detail could not be re-retrieved and is not asserted. Sources: cohere-north:cohere-north:n-doc-151-20261026. - deletion_propagation — How quickly does a deleted document disappear? [unknown]: The source-specific SharePoint/OneDrive implementation and Data Deletion pages remain inaccessible in public Markdown/HTML/index forms. General sync documentation does not establish a bounded delete-to-answer or purge interval. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/security/data-syncing?format=html, https://private.docs.cohere.com/north/docs/security/data-sharing?format=html, https://private.docs.cohere.com/north/docs/get-started/tools-overview.md. No additional scoped evidence established this answer. - index_location — Where is indexed content stored? [partial]: Compass runs with the customer-controlled North deployment, whose cloud/on-premise placement is selected by the operator. Foundry inference is separately routed to the customer Azure subscription. A universal vendor-hosted index country is not established. Sources: cohere-north:cohere-north:n-doc-165-20261026, cohere-north:cohere-north:n-doc-218-20261026. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-151-20261026, cohere-north:cohere-north:n-doc-152-20261026, cohere-north:cohere-north:n-doc-33, cohere-north:cohere-north:n-doc-165-20261026, cohere-north:cohere-north:n-doc-218-20261026 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The client renders source citations and Query mode documents a no-relevant-content response; quality is untested. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - citation_accuracy: Do the cited passages support the answer? The shared DE/FR/EN factual/cross-document/no-answer corpus was not run. Citation correctness, link accuracy, cross-language retrieval and numerical observed accuracy remain unknown; the default embedder is primarily English-trained. - cross_language: Does a question in one language find documents in another? The shared DE/FR/EN factual/cross-document/no-answer corpus was not run. Citation correctness, link accuracy, cross-language retrieval and numerical observed accuracy remain unknown; the default embedder is primarily English-trained. - no_answer_behaviour: Query mode documentation says it reports when no relevant information is found. This is documented behavior, not a passed no-answer fixture. - observed_accuracy: How many of the question set were answered correctly? The shared DE/FR/EN factual/cross-document/no-answer corpus was not run. Citation correctness, link accuracy, cross-language retrieval and numerical observed accuracy remain unknown; the default embedder is primarily English-trained. - citations — Are answers linked to specific sources? [supported]: Pinned client code renders document/link citation details and source metadata. Sources: anythingllm:anythingllm:citation-pin. - citation_accuracy — Do the cited passages support the answer? [unknown]: citation_accuracy: Do the cited passages support the answer? The shared DE/FR/EN factual/cross-document/no-answer corpus was not run. Citation correctness, link accuracy, cross-language retrieval and numerical observed accuracy remain unknown; the default embedder is primarily English-trained. - cross_language — Does a question in one language find documents in another? [unknown]: cross_language: Does a question in one language find documents in another? The shared DE/FR/EN factual/cross-document/no-answer corpus was not run. Citation correctness, link accuracy, cross-language retrieval and numerical observed accuracy remain unknown; the default embedder is primarily English-trained. - no_answer_behaviour — Does it say when the corpus has no answer? [partial]: Query mode documentation says it reports when no relevant information is found. This is documented behavior, not a passed no-answer fixture. Sources: anythingllm:anythingllm:chatmodes. - observed_accuracy — How many of the question set were answered correctly? [unknown]: observed_accuracy: How many of the question set were answered correctly? The shared DE/FR/EN factual/cross-document/no-answer corpus was not run. Citation correctness, link accuracy, cross-language retrieval and numerical observed accuracy remain unknown; the default embedder is primarily English-trained. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:citation-pin, anythingllm:anythingllm:chatmodes #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Citations are documented but have model-specific limitations; quality remains unmeasured. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: citation_accuracy, cross_language, no_answer_behaviour, observed_accuracy. - citations — Are answers linked to specific sources? [partial]: Chat highlights open source previews and Project citations exact passages. North Large card acknowledges missing citations in long multi-turn chats and Document Mode. Correctness not tested. Sources: cohere-north:cohere-north:n-doc-1, cohere-north:cohere-north:n-doc-11, cohere-north:cohere-north:n-doc-32. - citation_accuracy — Do the cited passages support the answer? [unknown]: Unknown for citation_accuracy. Shared DE/FR/EN fixture was not run; citation accuracy, cross-language retrieval, abstention and measured accuracy remain unobserved. - cross_language — Does a question in one language find documents in another? [unknown]: Unknown for cross_language. Shared DE/FR/EN fixture was not run; citation accuracy, cross-language retrieval, abstention and measured accuracy remain unobserved. - no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Unknown for no_answer_behaviour. Shared DE/FR/EN fixture was not run; citation accuracy, cross-language retrieval, abstention and measured accuracy remain unobserved. - observed_accuracy — How many of the question set were answered correctly? [unknown]: Unknown for observed_accuracy. Shared DE/FR/EN fixture was not run; citation accuracy, cross-language retrieval, abstention and measured accuracy remain unobserved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-1, cohere-north:cohere-north:n-doc-11, cohere-north:cohere-north:n-doc-32 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: supported Opt-in personalization stores private global/workspace memories with user controls and admin enablement. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. - custom_instructions — Can users set persistent instructions? [supported]: Workspaces keep model/system instructions and may include user/time variables. Sources: anythingllm:anythingllm:systemprompt, anythingllm:anythingllm:llmconfig. - cross_chat_memory — Does the product remember facts across chats? [supported]: User memories apply across chats within a workspace or globally; limits are 20 workspace and five global memories per user. Sources: anythingllm:anythingllm:memory. - user_memory_controls — Can users view, edit and delete memories? [supported]: Users can add, edit, delete and move memories; selected memories are sent to the configured model in the system prompt. Sources: anythingllm:anythingllm:memory. - admin_memory_controls — Can admins turn memory off? [supported]: Memories are off by default; in multi-user mode only admins enable/disable personalization. Sources: anythingllm:anythingllm:memory. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:systemprompt, anythingllm:anythingllm:llmconfig, anythingllm:anythingllm:memory #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Alpha memory separates editable personal memories from inaccessible agent archival memory. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The vendor marks this control alpha. The catalogue availability field stays unknown because its enum has no alpha value; this does not mean unsupported. - custom_instructions — Can users set persistent instructions? [supported]: Agents persist instructions; optional company preamble applies across models. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-86. - cross_chat_memory — Does the product remember facts across chats? [supported]: Alpha personal memory learns across chats; archival memory per agent is generated in background, typically daily. Sources: cohere-north:cohere-north:n-doc-8, cohere-north:cohere-north:n-doc-96. - user_memory_controls — Can users view, edit and delete memories? [partial]: Personal categories can be viewed/edited; pause retains or Delete removes memory. Archival memories cannot be viewed/edited; manual personal edits can be overwritten by later extraction. Sources: cohere-north:cohere-north:n-doc-8. - admin_memory_controls — Can admins turn memory off? [supported]: Instance admin can jointly toggle core/archival/conversation memory and configure extraction frequency. Sources: cohere-north:cohere-north:n-doc-96. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-86, cohere-north:cohere-north:n-doc-8, cohere-north:cohere-north:n-doc-96 ## 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workspaces combine instructions, a model, knowledge and configured Agent skills; a distinct shareable assistant object/catalog was not fully established. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - creator_permissions: Admin/Manager roles manage workspaces; Default users only chat in assigned workspaces. A separate assistant-creator permission matrix was not established. - sharing_scope: Docker workspaces can be assigned to users; Desktop is single-user. Group/everyone assistant-sharing and versioned assistant publishing were not established. - catalogue: Is there an internal assistant directory? A complete internal assistant directory/versioning contract and the HR assistant fixture were not verified. - prompt_library: Workspace prompts and no-code Agent Flows can be reused, but a separate organization prompt-template catalog was not verified. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Workspace and Agent settings combine a model, instructions, embedded knowledge and enabled skills/tools. Sources: anythingllm:anythingllm:llmconfig, anythingllm:anythingllm:agent-setup, anythingllm:anythingllm:docchat. - creator_permissions — Can admins limit who creates them? [partial]: Admin/Manager roles manage workspaces; Default users only chat in assigned workspaces. A separate assistant-creator permission matrix was not established. Sources: anythingllm:anythingllm:security. - sharing_scope — Can assistants be shared with users, groups or everyone? [partial]: Docker workspaces can be assigned to users; Desktop is single-user. Group/everyone assistant-sharing and versioned assistant publishing were not established. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:desktop. - catalogue — Is there an internal assistant directory? [unknown]: catalogue: Is there an internal assistant directory? A complete internal assistant directory/versioning contract and the HR assistant fixture were not verified. - prompt_library — Are shared prompt templates available? [partial]: Workspace prompts and no-code Agent Flows can be reused, but a separate organization prompt-template catalog was not verified. Sources: anythingllm:anythingllm:flow, anythingllm:anythingllm:systemprompt. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:llmconfig, anythingllm:anythingllm:agent-setup, anythingllm:anythingllm:docchat, anythingllm:anythingllm:security, anythingllm:anythingllm:desktop, anythingllm:anythingllm:flow, anythingllm:anythingllm:systemprompt #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North offers versioned custom agents, scoped sharing and an internal catalogue. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The partial atomic answers state their documentation or verification limits. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Users create agents with instructions, model, tools, libraries and output modes; drafts publish as versioned releases with restore/evaluations. Sources: cohere-north:cohere-north:n-doc-18. - creator_permissions — Can admins limit who creates them? [supported]: Can create agents and separate sharing grants control creation/publication audiences. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-114. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Published agents share to users/groups/company subject to grants; libraries need separate recipient access and email libraries remain private. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-42. - catalogue — Is there an internal assistant directory? [supported]: Agent directory has Starred/My/Shared with me/Company tabs, search and duplication. Sources: cohere-north:cohere-north:n-doc-21. - prompt_library — Are shared prompt templates available? [partial]: Agents expose up to four starter prompts and reusable Skills; a separate central prompt-template catalogue not established. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-12. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-21, cohere-north:cohere-north:n-doc-12 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Self-hosted/desktop supports built-in skills, API-call flows and MCP. Managed Cloud explicitly excludes custom coded Agents and MCP. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=Separate MCP servers or custom skill configuration, Mail integrations require single-user mode; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - Cloud does not support MCP or custom coded Agents. - Single-user mail approvals do not establish a complete multi-user side-effect policy. - builtin_tools — Which tools are built in? [supported]: Skills include RAG/document search, web browsing, chart/document generation and SQL; single-user mail skills have a narrower scope. Sources: anythingllm:anythingllm:agent-setup, anythingllm:anythingllm:sql, anythingllm:anythingllm:docgen, anythingllm:anythingllm:chart, anythingllm:anythingllm:outlook. - custom_actions — Can admins add API actions? [supported]: No-code flows provide an API-call block and custom skills can be developed for self-hosted/desktop; Cloud excludes custom coded Agents. Sources: anythingllm:anythingllm:flow-api, anythingllm:anythingllm:cloud-limits. - mcp_client — Can it use remote MCP servers, and with what admin control? [partial]: Self-hosted/desktop supports stdio, SSE and Streamable remote MCP with management controls. Managed Cloud explicitly does not support MCP. Sources: anythingllm:anythingllm:mcp, anythingllm:anythingllm:cloud-limits. - tool_auth — Do tools act as the user or as a shared account? [partial]: MCP accepts environment variables/HTTP headers; single-user Outlook uses delegated Entra authorization. A general per-user OAuth model for every multi-user tool was not established. Sources: anythingllm:anythingllm:mcp, anythingllm:anythingllm:outlook. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Outlook/Gmail modifying actions explicitly require approval in single-user mode. A mandatory approval policy for every custom/MCP action was not verified. Sources: anythingllm:anythingllm:outlook, anythingllm:anythingllm:gmail, anythingllm:anythingllm:mcp. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:agent-setup, anythingllm:anythingllm:sql, anythingllm:anythingllm:docgen, anythingllm:anythingllm:chart, anythingllm:anythingllm:outlook, anythingllm:anythingllm:flow-api, anythingllm:anythingllm:cloud-limits, anythingllm:anythingllm:mcp, anythingllm:anythingllm:gmail #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial MCP, code and enterprise tools have scoped authentication and configurable approvals. Availability: unknown Delivery: official-integration Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; always-on MCP policies are Alpha; guide recommends testing/staging initially; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The partial atomic answers state their documentation or verification limits. - Approval-parameter editing is an interface affordance only in this finding. No execution guarantee is credited without a corrected guide or a bounded tool-call fixture. - Always-on MCP configuration is Alpha with a testing/staging recommendation until the organization is ready for broader adoption. Criterion availability remains unknown; this subfact does not establish production readiness. - builtin_tools — Which tools are built in? [supported]: Built-in search, source connectors, code sandbox, Skills and output capabilities documented with individual states. Sources: cohere-north:cohere-north:n-doc-33, cohere-north:cohere-north:n-doc-34. - custom_actions — Can admins add API actions? [supported]: Custom MCP servers expose APIs/actions; admin configures tools and auth, with action hints for approval. Sources: cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-150. - mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: North registers custom/remote MCP; remote OAuth dynamic registration needs outbound access and is unavailable fully air-gapped. Tool access policies can target groups. Always-on MCP policies are Alpha; the guide recommends enabling them only in testing/staging until the organization is ready for broader adoption. Sources: cohere-north:cohere-north:n-doc-126. - tool_auth — Do tools act as the user or as a shared account? [supported]: Static headers, per-user ID/connector tokens, OAuth client credentials or remote OAuth supported. Shared/static credentials require separate source-policy assessment. Sources: cohere-north:cohere-north:n-doc-126. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Destructive-hint tools can pause for approval or denial, and the modal offers parameter editing. Whether edited values execute is unknown: the guide says both that modifications replace the original request and that original keys/values are submitted. Allow Always and advance automation action permissions can bypass later prompts; universal per-action confirmation is not guaranteed. Sources: cohere-north:cohere-north:n-doc-150, cohere-north:cohere-north:n-doc-30. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-33, cohere-north:cohere-north:n-doc-34, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-150, cohere-north:cohere-north:n-doc-30 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The web-browsing skill supports explicit search-provider configuration. This claim covers the pinned self-hosted DuckDuckGo route; it makes no assertion about an unconfigured default. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Self-hosted v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba, explicitly configured agent_search_provider=duckduckgo-engine; plan=MIT self-hosted deployment with an explicitly selected DuckDuckGo provider; auto-selected defaults, Desktop and managed Cloud defaults are outside this claim; add_ons=Enabled web-browsing skill; explicit agent_search_provider=duckduckgo-engine setting; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - The scope is an explicitly configured provider at one release pin, not an assertion about default routing in other installations. - Search queries leave the application for the selected external endpoint; processing region and a per-group enforcement fixture were not established. - Dedicated research-report quality and citation completeness remain untested. - web_search — Is web search available? [supported]: The Agent web-browsing skill can search the web; this scoped self-hosted configuration explicitly selects the DuckDuckGo engine. Sources: anythingllm:anythingllm:browsing, anythingllm:anythingllm:search-configured-r2. - admin_toggle — Can admins disable it per organisation or group? [partial]: The documented Agent Skills settings and chat prompt controls toggle skills. Separate per-group web-search enforcement under the standard role model was not established. Sources: anythingllm:anythingllm:agent-skills-r2, anythingllm:anythingllm:security. - search_provider — Which search provider handles queries, and where? [partial]: At the pinned v1.18.0 revision, explicit agent_search_provider=duckduckgo-engine invokes _duckDuckGoEngine and sends the query to html.duckduckgo.com/html. Query processing country and a CH/EU residency commitment were not verified. Unconfigured defaults are outside this finding. Sources: anythingllm:anythingllm:search-configured-r2. - deep_research — Is multi-step research with a report available? [partial]: Agent tools/flows can chain research steps; a dedicated tested report workflow and accuracy result were not established. Sources: anythingllm:anythingllm:flow, anythingllm:anythingllm:agent-usage. - web_citations — Are web sources cited? [partial]: The client renders source citations including links; correctness and completeness of web-source citations were not tested. Sources: anythingllm:anythingllm:citation-pin. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:browsing, anythingllm:anythingllm:search-configured-r2, anythingllm:anythingllm:agent-skills-r2, anythingllm:anythingllm:security, anythingllm:anythingllm:flow, anythingllm:anythingllm:agent-usage, anythingllm:anythingllm:citation-pin #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial GA web search and alpha Deep Research are distinct capabilities. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Web search GA; Deep Research alpha. - web_search — Is web search available? [supported]: GA web search supports live URL/search retrieval; text-only and no authenticated websites. Sources: cohere-north:cohere-north:n-doc-74. - admin_toggle — Can admins disable it per organisation or group? [partial]: Admins enable provider/tool; Deep Research additionally needs user/group grants. Complete group-specific web-search matrix unverified. Sources: cohere-north:cohere-north:n-doc-74, cohere-north:cohere-north:n-doc-15. - search_provider — Which search provider handles queries, and where? [partial]: Tavily defaultGA; Brave/LinkUp alpha, own API keys and one active provider. Provider processing countries not retrieved. Sources: cohere-north:cohere-north:n-doc-74. - deep_research — Is multi-step research with a report available? [supported]: Alpha Deep Research delegates multi-step subqueries and creates reports; requires enabled sources, admin/user grants and may queue. Sources: cohere-north:cohere-north:n-doc-15. - web_citations — Are web sources cited? [supported]: Live web and Deep Research include source citations; quality untested. Sources: cohere-north:cohere-north:n-doc-74, cohere-north:cohere-north:n-doc-15. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-74, cohere-north:cohere-north:n-doc-15 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial No-code Agent Flows are available on Docker/Desktop. Scheduled Jobs are explicitly single-user only. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=Scheduled Jobs require single-user mode; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - scheduled_tasks: Scheduled Jobs run recurring Agent prompts with cron, tool allow-lists and saved traces in single-user mode. They are unavailable in self-hosted multi-user mode. - event_triggers: Can external events start a workflow? A maintained incoming email/form/business-system event-trigger contract was not established; an API call alone is not a named trigger integration. - workflow_builder — Is there a workflow or chain builder? [supported]: The visual flow editor builds reusable agentic skills with steps such as API calls, scraping and file operations. Sources: anythingllm:anythingllm:flow. - scheduled_tasks — Can prompts or assistants run on a schedule? [partial]: Scheduled Jobs run recurring Agent prompts with cron, tool allow-lists and saved traces in single-user mode. They are unavailable in self-hosted multi-user mode. Sources: anythingllm:anythingllm:job. - event_triggers — Can external events start a workflow? [unknown]: event_triggers: Can external events start a workflow? A maintained incoming email/form/business-system event-trigger contract was not established; an API call alone is not a named trigger integration. - builder_audience — Is building aimed at business users, IT or developers? [supported]: Flows target non-coders; custom skill code targets technical users and developers. Sources: anythingllm:anythingllm:flow. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:flow, anythingllm:anythingllm:job #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Node workflows support schedules, API invocation and human review. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The partial atomic answers state their documentation or verification limits. - workflow_builder — Is there a workflow or chain builder? [supported]: Visual node builder combines LLM/agent/tool/conditional/loop steps, versioning and JSON import/export. Sources: cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-29. - scheduled_tasks — Can prompts or assistants run on a schedule? [supported]: Users schedule hourly/daily/weekly or cron; optional natural-language suggestions require confirmation. Repeated failure can disable schedules. Sources: cohere-north:cohere-north:n-doc-30. - event_triggers — Can external events start a workflow? [partial]: Authenticated execute API enables custom external event integrations. A native inbox/file-change webhook listener was not established. Sources: cohere-north:cohere-north:n-api-run. - builder_audience — Is building aimed at business users, IT or developers? [supported]: Business builders use visual/natural-language tools and Human Review; IT provisions connectors/models and developers call APIs. Sources: cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-26, cohere-north:cohere-north:n-api-run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-29, cohere-north:cohere-north:n-doc-30, cohere-north:cohere-north:n-api-run, cohere-north:cohere-north:n-doc-26 ### 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. #### AnythingLLM Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North executes multi-step work with visible tasks, approval options and workflow cancellation. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The partial atomic answers state their documentation or verification limits. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: Agents use tools/code; Deep Research decomposes tasks and delegates subagents; automations execute multiple nodes. Sources: cohere-north:cohere-north:n-doc-15, cohere-north:cohere-north:n-doc-34, cohere-north:cohere-north:n-doc-16. - visible_steps — Are steps and tool calls shown? [supported]: Sandbox activity expands executed code; automation run viewer shows node inputs/outputs; shared chat includes thinking trace. Sources: cohere-north:cohere-north:n-doc-34, cohere-north:cohere-north:n-doc-30, cohere-north:cohere-north:n-doc-4. - side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Tool hints trigger approval; global Allow Always bypasses it and workflows accept action permissions at launch. Human Review nodes can add deliberate checkpoints. Sources: cohere-north:cohere-north:n-doc-150, cohere-north:cohere-north:n-doc-30, cohere-north:cohere-north:n-doc-26. - stop_control — Can the user stop a running task? [partial]: Running automations have Cancel. General chat stop behavior and rollback of already executed external actions were not tested. Sources: cohere-north:cohere-north:n-doc-30. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-15, cohere-north:cohere-north:n-doc-34, cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-30, cohere-north:cohere-north:n-doc-4, cohere-north:cohere-north:n-doc-150, cohere-north:cohere-north:n-doc-26 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Instance APIs manage workspaces, upload/embed content and run chats using provisioned API keys. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - api_governance: API keys are provisioned by authorized accounts and confer access to their holder. Full UI/API quota, model, audit and per-user boundary parity was not tested. - mcp_server: Does the product expose itself to other agents over MCP? A native product-wide MCP server was not established from the client-MCP and API guides. - chat_api — Is there an API for chat and assistants? [supported]: The documented developer API supports workspace management and chat, with instance OpenAPI docs at /api/docs. Sources: anythingllm:anythingllm:api. - knowledge_api — Can documents be loaded through an API? [supported]: The developer API documents embedding/document management alongside workspace operations. Sources: anythingllm:anythingllm:api. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: API keys are provisioned by authorized accounts and confer access to their holder. Full UI/API quota, model, audit and per-user boundary parity was not tested. Sources: anythingllm:anythingllm:api, anythingllm:anythingllm:config. - mcp_server — Does the product expose itself to other agents over MCP? [unknown]: mcp_server: Does the product expose itself to other agents over MCP? A native product-wide MCP server was not established from the client-MCP and API guides. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:api, anythingllm:anythingllm:config #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North has its own authenticated REST APIs for responses, agents, files, libraries and workflows. Availability: unknown Delivery: native Scope: surfaces=North instance REST API and SDK access; version=North 2.0.1 docs; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: mcp_server. - chat_api — Is there an API for chat and assistants? [supported]: Instance REST API supports chat/agents/automations; response endpoint exposes models/tools and SDK access. Separate from Cohere model Platform API. Sources: cohere-north:cohere-north:n-north-api, cohere-north:cohere-north:n-api-response. - knowledge_api — Can documents be loaded through an API? [supported]: Authenticated file upload stores content with IDs; library APIs create collections under library permissions. Sources: cohere-north:cohere-north:n-api-upload, cohere-north:cohere-north:n-api-libraries, cohere-north:cohere-north:n-doc-114. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: APIs return permission/rate-limit errors and use North identities; sharing restrictions cover API, audit GET exists. Full guardrail/budget/content logging parity not tested. Sources: cohere-north:cohere-north:n-api-response, cohere-north:cohere-north:n-doc-89, cohere-north:cohere-north:n-doc-140. - mcp_server — Does the product expose itself to other agents over MCP? [unknown]: Unknown for mcp_server. North REST APIs are public. Full API guardrail/audit/rate-limit parity and a turnkey North-as-MCP server were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-north-api, cohere-north:cohere-north:n-api-response, cohere-north:cohere-north:n-api-upload, cohere-north:cohere-north:n-api-libraries, cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-89, cohere-north:cohere-north:n-doc-140 ## 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Docker serves a browser client, Desktop has native installers and Mobile is Android-only; these are different access/governance modes. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Mobile for Android, AnythingLLM browser content collection extension; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=Windows, macOS, Linux, Android. Limitations: - mobile_apps: A separate free Android app can run local models or pair with Desktop/Cloud/self-hosted servers. iOS and a tested native company-SSO flow were not established. - managed_deployment: Windows silent installer switches are documented for scripted/MDM packaging. Current User install is required; all-users install is unsupported and Enterprise/Server OS use has caveats. No Intune deployment was tested. - web — Is a full web client available? [supported]: Docker provides the browser-accessible multi-user UI; Desktop network discovery exposes API endpoints rather than a web UI. Sources: anythingllm:anythingllm:desktop, anythingllm:anythingllm:docker. - desktop_apps — Windows and macOS apps? [supported]: Desktop installers support Windows, macOS and Linux; the app is single-user rather than a shared company-login client. Sources: anythingllm:anythingllm:desktop. - mobile_apps — iOS and Android apps with SSO? [partial]: A separate free Android app can run local models or pair with Desktop/Cloud/self-hosted servers. iOS and a tested native company-SSO flow were not established. Sources: anythingllm:anythingllm:mobile. - browser_extension — Is there a browser extension or sidebar? [supported]: A content collection extension supports Chrome/Edge/Brave/Firefox and connects with an instance API key. Sources: anythingllm:anythingllm:ext. - managed_deployment — Can IT deploy and configure clients through MDM? [partial]: Windows silent installer switches are documented for scripted/MDM packaging. Current User install is required; all-users install is unsupported and Enterprise/Server OS use has caveats. No Intune deployment was tested. Sources: anythingllm:anythingllm:windows. - client_feature_gaps — Which features are missing on mobile? [supported]: Desktop lacks multi-user/workspace administration; Android is a separate local/pairing client; Desktop-only meeting features currently target Windows/macOS. Sources: anythingllm:anythingllm:desktop, anythingllm:anythingllm:mobile, anythingllm:anythingllm:meeting-intro. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:desktop, anythingllm:anythingllm:docker, anythingllm:anythingllm:mobile, anythingllm:anythingllm:ext, anythingllm:anythingllm:windows, anythingllm:anythingllm:meeting-intro #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North has web and mobile access; desktop/MDM coverage is unknown. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, North iOS and alpha Android app; version=not specified; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: desktop_apps, browser_extension, managed_deployment. - web — Is a full web client available? [supported]: Full browser chat, Admin and builders documented. Sources: cohere-north:cohere-north:n-doc-1, cohere-north:cohere-north:n-doc-18. - desktop_apps — Windows and macOS apps? [unknown]: Unknown for desktop_apps. Web and alpha mobile are documented; no desktop package, browser extension, MDM deployment matrix or mobile SSO test was retrieved. - mobile_apps — iOS and Android apps with SSO? [partial]: October 16 release documents Android alpha with iOS feature parity for agents/automations/record/translate. Mobile SSO/installation workflow not tested. Sources: cohere-north:cohere-north:n-north-changelog. - browser_extension — Is there a browser extension or sidebar? [unknown]: Unknown for browser_extension. Web and alpha mobile are documented; no desktop package, browser extension, MDM deployment matrix or mobile SSO test was retrieved. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Unknown for managed_deployment. Web and alpha mobile are documented; no desktop package, browser extension, MDM deployment matrix or mobile SSO test was retrieved. - client_feature_gaps — Which features are missing on mobile? [partial]: Mobile record/translate and document review are documented; complete web/admin/builders parity and managed-client matrix not retrieved. Sources: cohere-north:cohere-north:n-north-changelog, cohere-north:cohere-north:n-doc-97. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-1, cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-north-changelog, cohere-north:cohere-north:n-doc-97 ### 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. #### AnythingLLM Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Cohere North Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Optional Desktop Magic tools support system-wide rewriting, but layout-preserving translation and company glossary controls remain unverified. Availability: generally-available Delivery: native Scope: surfaces=AnythingLLM Desktop; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=Desktop free Magic allowances; optional Desktop Pro; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=Windows, macOS. Limitations: - document_translation: Can whole documents be translated with formatting kept? No whole-contract DE-to-FR/IT formatting test, company glossary, formality/de-CH control or dedicated layout-preserving translation service was verified. - translation_engine: Generative rewrite work uses the selected model. A dedicated document translation engine/workflow was not established. - glossaries: Are company glossaries supported? No whole-contract DE-to-FR/IT formatting test, company glossary, formality/de-CH control or dedicated layout-preserving translation service was verified. - formality_and_variants: Can formality and regional variants (de-CH) be set? No whole-contract DE-to-FR/IT formatting test, company glossary, formality/de-CH control or dedicated layout-preserving translation service was verified. - document_translation — Can whole documents be translated with formatting kept? [unknown]: document_translation: Can whole documents be translated with formatting kept? No whole-contract DE-to-FR/IT formatting test, company glossary, formality/de-CH control or dedicated layout-preserving translation service was verified. - translation_engine — Which engine translates? [partial]: Generative rewrite work uses the selected model. A dedicated document translation engine/workflow was not established. Sources: anythingllm:anythingllm:pro, anythingllm:anythingllm:llmconfig. - glossaries — Are company glossaries supported? [unknown]: glossaries: Are company glossaries supported? No whole-contract DE-to-FR/IT formatting test, company glossary, formality/de-CH control or dedicated layout-preserving translation service was verified. - formality_and_variants — Can formality and regional variants (de-CH) be set? [unknown]: formality_and_variants: Can formality and regional variants (de-CH) be set? No whole-contract DE-to-FR/IT formatting test, company glossary, formality/de-CH control or dedicated layout-preserving translation service was verified. - writing_tools — Are dedicated rewrite and proofreading tools available? [supported]: Desktop Magic Echo/Beacon/Tab offer dictation cleanup, selected-text revision and writing completion, with free allowances and optional Desktop Pro. Sources: anythingllm:anythingllm:pro. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:pro, anythingllm:anythingllm:llmconfig #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Document mode supports translation and writing; controlled layout-preserving translation is unverified. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: translation_engine, glossaries. - document_translation — Can whole documents be translated with formatting kept? [partial]: Document mode can translate whole generated documents or selections; shortcut is alpha. Preservation of uploaded document layout, tables and glossary terms untested. Sources: cohere-north:cohere-north:n-doc-9. - translation_engine — Which engine translates? [unknown]: Unknown for translation_engine. Document mode supports translation/rewriting. Layout-preserving file translation, managed glossary, dedicated engine and de-CH controls were not established. - glossaries — Are company glossaries supported? [unknown]: Unknown for glossaries. Document mode supports translation/rewriting. Layout-preserving file translation, managed glossary, dedicated engine and de-CH controls were not established. - formality_and_variants — Can formality and regional variants (de-CH) be set? [partial]: Tone actions include professional/friendly/concise/persuasive and prompts can request formal rewrites. Dedicated de-CH/regional controls not established. Sources: cohere-north:cohere-north:n-doc-9. - writing_tools — Are dedicated rewrite and proofreading tools available? [supported]: Document editor supports rewriting, tone/length actions, manual edits and prompt-guided revision with history. Sources: cohere-north:cohere-north:n-doc-9. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-9 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Configured image providers generate pictures and can edit references where supported. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - image_editing: OpenAI/OpenRouter and compatible Lemonade models use reference-image editing. The documented Ollama route drops image references and generates from text only. - admin_control: Admins configure provider credentials and model. A separate per-group image-generation cost/permission policy was not established. - usage_terms: What usage rights apply to output? Output rights and complete per-image cost visibility depend on the model/provider contract and were not established here. - image_generation — Can users generate images, with which models? [supported]: The /img command uses configured OpenAI, OpenRouter, Ollama or Lemonade providers and an operator-selected model. Sources: anythingllm:anythingllm:images. - image_editing — Can users edit uploaded images? [partial]: OpenAI/OpenRouter and compatible Lemonade models use reference-image editing. The documented Ollama route drops image references and generates from text only. Sources: anythingllm:anythingllm:images. - admin_control — Can admins restrict image generation? [partial]: Admins configure provider credentials and model. A separate per-group image-generation cost/permission policy was not established. Sources: anythingllm:anythingllm:images, anythingllm:anythingllm:security. - usage_terms — What usage rights apply to output? [unknown]: usage_terms: What usage rights apply to output? Output rights and complete per-image cost visibility depend on the model/provider contract and were not established here. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:images, anythingllm:anythingllm:security #### Cohere North Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Audio transcription/read-aloud are configurable. Free meeting capture and local transcription are Desktop-only on Windows/macOS. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=Desktop-only Meeting Assistant; downloaded transcription models, Optional provider-specific audio services; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - dictation: Transcription providers and Desktop Magic Echo support spoken input; exact supported dialects and a shared dictation fixture were not verified. - voice_conversation: Is a live voice mode available? No continuous live conversational voice mode or Swiss German recognition quality was verified. - swiss_german_speech: Is Swiss German speech recognised? No continuous live conversational voice mode or Swiss German recognition quality was verified. - dictation — Can users dictate prompts? [partial]: Transcription providers and Desktop Magic Echo support spoken input; exact supported dialects and a shared dictation fixture were not verified. Sources: anythingllm:anythingllm:stt, anythingllm:anythingllm:pro. - read_aloud — Can answers be read aloud? [supported]: System-native, local/browser Piper, self-hosted Kokoro and cloud TTS routes are documented; the chosen engine determines processing. Sources: anythingllm:anythingllm:tts. - voice_conversation — Is a live voice mode available? [unknown]: voice_conversation: Is a live voice mode available? No continuous live conversational voice mode or Swiss German recognition quality was verified. - meeting_summaries — Are meetings transcribed and summarised? [supported]: Desktop Meeting Assistant records/imports meetings, transcribes locally and summarizes with the chosen local/cloud model. A cloud summary sends the transcript to that provider; Linux is not currently supported. Sources: anythingllm:anythingllm:meeting-intro, anythingllm:anythingllm:meeting. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: swiss_german_speech: Is Swiss German speech recognised? No continuous live conversational voice mode or Swiss German recognition quality was verified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:stt, anythingllm:anythingllm:pro, anythingllm:anythingllm:tts, anythingllm:anythingllm:meeting-intro, anythingllm:anythingllm:meeting #### Cohere North Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-97, cohere-north:cohere-north:n-doc-1 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Built-in Agent skills generate charts and downloadable Office/PDF documents; executed spreadsheet analysis and iterative canvas editing were not tested. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - data_analysis: Can it analyse spreadsheets with executed code? No shared spreadsheet execution/formula analysis, editable PowerPoint fidelity or document-canvas fixture was run. Built-in chart creation does not establish a general code interpreter. - canvas_editing: Is there a document or canvas editor for iterating on output? No shared spreadsheet execution/formula analysis, editable PowerPoint fidelity or document-canvas fixture was run. Built-in chart creation does not establish a general code interpreter. - data_analysis — Can it analyse spreadsheets with executed code? [unknown]: data_analysis: Can it analyse spreadsheets with executed code? No shared spreadsheet execution/formula analysis, editable PowerPoint fidelity or document-canvas fixture was run. Built-in chart creation does not establish a general code interpreter. - charts — Can it produce charts? [supported]: An enabled chart skill creates charts from prompts or workspace data. Sources: anythingllm:anythingllm:chart. - office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: The built-in Document Generation skill lists text, PDF, Excel, DOCX and PowerPoint outputs; the guide recommends capable models for PowerPoint. Sources: anythingllm:anythingllm:docgen. - canvas_editing — Is there a document or canvas editor for iterating on output? [unknown]: canvas_editing: Is there a document or canvas editor for iterating on output? No shared spreadsheet execution/formula analysis, editable PowerPoint fidelity or document-canvas fixture was run. Built-in chart creation does not establish a general code interpreter. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:chart, anythingllm:anythingllm:docgen #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Beta sandbox/Skills create Office files. Document mode supports iteration, with alpha incremental editing distinguished from the broader document workflow. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha incremental document editing; sandbox/Skills separately Beta; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - data_analysis: Beta Skills run file-producing work through sandbox_run_python or sandbox_run_command and provide spreadsheet/CSV operations. The sandbox service and skills permission must be enabled. Analysis correctness and formula preservation were not benchmarked. - charts: The document-mode guide describes Data Interpreter creating a chart and embedding it in the editor. The inaccessible sandbox/interpreter guides do not establish a complete plotting-library inventory; chart correctness was not tested. - data_analysis — Can it analyse spreadsheets with executed code? [partial]: Beta Skills run file-producing work through sandbox_run_python or sandbox_run_command and provide spreadsheet/CSV operations. The sandbox service and skills permission must be enabled. Analysis correctness and formula preservation were not benchmarked. Sources: cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:north-release-html-20261026. - charts — Can it produce charts? [partial]: The document-mode guide describes Data Interpreter creating a chart and embedding it in the editor. The inaccessible sandbox/interpreter guides do not establish a complete plotting-library inventory; chart correctness was not tested. Sources: cohere-north:cohere-north:n-doc-9-20261026. - office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: Beta Skills include DOCX/PPTX/XLSX/CSV creation/editing; model and sandbox prerequisites apply. Sources: cohere-north:cohere-north:n-doc-12-20261026. - canvas_editing — Is there a document or canvas editor for iterating on output? [supported]: Document mode combines direct editing, prompted edits, version history and PDF/DOCX/MD/HTML export. Incremental document-editing controls are alpha; this does not make the whole criterion beta or generally available. Sources: cohere-north:cohere-north:n-doc-9-20261026, cohere-north:cohere-north:n-north-changelog-20261026. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:north-release-html-20261026, cohere-north:cohere-north:n-doc-9-20261026, cohere-north:cohere-north:n-north-changelog-20261026 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Docker workspaces share knowledge with assigned users; shared live conversation behavior remains unverified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - share_chats: Can chats be shared inside the organisation? Authenticated chat-share links, simultaneous multi-person AI conversation and recipient transcript/source visibility were not established by the workspace and chat-log guides. - group_chat: Can several people chat together with the AI? Authenticated chat-share links, simultaneous multi-person AI conversation and recipient transcript/source visibility were not established by the workspace and chat-log guides. - share_permission_boundary: Embedded files become accessible to every assigned workspace user; this does not preserve an arbitrary original source ACL. A cross-group chat-sharing fixture was not run. - share_chats — Can chats be shared inside the organisation? [unknown]: share_chats: Can chats be shared inside the organisation? Authenticated chat-share links, simultaneous multi-person AI conversation and recipient transcript/source visibility were not established by the workspace and chat-log guides. - team_spaces — Are shared projects or workspaces available? [supported]: Multi-user workspaces can be assigned to users, who share the embedded knowledge available there. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:docchat. - group_chat — Can several people chat together with the AI? [unknown]: group_chat: Can several people chat together with the AI? Authenticated chat-share links, simultaneous multi-person AI conversation and recipient transcript/source visibility were not established by the workspace and chat-log guides. - share_permission_boundary — Does sharing respect the recipient's access to sources? [partial]: Embedded files become accessible to every assigned workspace user; this does not preserve an arbitrary original source ACL. A cross-group chat-sharing fixture was not run. Sources: anythingllm:anythingllm:docchat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:docchat #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared snapshots and source collections have different access boundaries. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: group_chat. - share_chats — Can chats be shared inside the organisation? [supported]: Signed-in colleagues open read-only snapshot links with messages, citations, thinking and presented sandbox files; subsequent changes need a new link. Sources: cohere-north:cohere-north:n-doc-4. - team_spaces — Are shared projects or workspaces available? [partial]: Beta Libraries share collections via user/group/company roles. Alpha Projects are private per-user workspaces; not shared team Projects. Sources: cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-11. - group_chat — Can several people chat together with the AI? [unknown]: Unknown for group_chat. Chat links are static read-only snapshots. Concurrent human group chat and rechecking original-source ACLs on all shared-answer content were not established. - share_permission_boundary — Does sharing respect the recipient's access to sources? [partial]: Shared chat exposes existing answer text/files to signed-in recipients; no original-source ACL recheck established. Library/agent retrieval separately checks source and library access. Sources: cohere-north:cohere-north:n-doc-4, cohere-north:cohere-north:n-doc-152. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-4, cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-11, cohere-north:cohere-north:n-doc-152 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The pinned frontend registers English, German, French and Italian, with fallback behavior; translation quality and WCAG conformance remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=New code findings at v1.19.0 / 9b1fcab141000eaba9f78ed131151de04904454b (published 2026-10-26); earlier accepted facts retain their own pins; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - German administrator labels are present in pinned source; full German/French/Italian screen coverage and naturalness were not observed. - No WCAG conformance statement or full accessibility walkthrough was verified. - ui_languages — Which UI languages are offered? [supported]: The locale implementation registers en, de, fr and it among other resources. Sources: anythingllm:anythingllm:i18n-pin. - dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: dach_language_quality: Are German, French and Italian UIs complete and natural? No full DE/FR/IT UI walkthrough, German admin-screen completeness review or WCAG conformance report was verified. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: accessibility_statement: Is there a WCAG conformance statement? No full DE/FR/IT UI walkthrough, German admin-screen completeness review or WCAG conformance report was verified. - admin_ui_languages — Is the admin interface available in German? [partial]: The pinned German locale includes user management, invitations, event logs and administrator settings labels. Complete admin-screen coverage, translation quality and WCAG conformance were not observed. Sources: anythingllm:anythingllm:r4-german-admin. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: anythingllm:anythingllm:i18n-pin, anythingllm:anythingllm:r4-german-admin #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial User UI offers German and French among eight languages; accessibility and admin translation remain gaps. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: accessibility_statement, admin_ui_languages. - ui_languages — Which UI languages are offered? [supported]: Guide lists English default, Spanish, French, Portuguese, Arabic, Japanese, Korean and German. Italian is not in this documented selector list. Sources: cohere-north:cohere-north:n-doc-1. - dach_language_quality — Are German, French and Italian UIs complete and natural? [partial]: German/French available; Italian not listed. Completeness/naturalness was not tested and model language support does not prove UI quality. Sources: cohere-north:cohere-north:n-doc-1. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Unknown for accessibility_statement. Eight user UI languages are listed. No WCAG conformance statement, complete German admin UI inventory or DE/FR/IT usability assessment was retrieved. - admin_ui_languages — Is the admin interface available in German? [unknown]: Unknown for admin_ui_languages. Eight user UI languages are listed. No WCAG conformance statement, complete German admin UI inventory or DE/FR/IT usability assessment was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-1 ## 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The standard Docker project documents a privileged simple-SSO passthrough; the commercial Enterprise offer advertises SSO without public protocol details. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=Custom trusted login integration for Simple SSO, Quote-only Enterprise for the advertised SSO offer; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - sso_protocols: Simple SSO generates one-use temporary links for existing users through an API key. It is not evidence of built-in SAML/OIDC/LDAP federation; those protocol details were not verified. - sso_plan: Simple passthrough is documented for self-hosted multi-user mode. Quote-only Enterprise separately advertises SSO, with public protocol/feature scope unspecified. - mfa: Can MFA be enforced? MFA enforcement, conditional-access compatibility and company-domain capture were not established from the standard authentication or public Enterprise offer. - conditional_access: Do Entra conditional-access policies apply? MFA enforcement, conditional-access compatibility and company-domain capture were not established from the standard authentication or public Enterprise offer. - domain_capture: Can the company claim its email domain? MFA enforcement, conditional-access compatibility and company-domain capture were not established from the standard authentication or public Enterprise offer. - sso_protocols — Which SSO protocols and identity providers work? [partial]: Simple SSO generates one-use temporary links for existing users through an API key. It is not evidence of built-in SAML/OIDC/LDAP federation; those protocol details were not verified. Sources: anythingllm:anythingllm:config. - sso_plan — Which plan includes SSO? [partial]: Simple passthrough is documented for self-hosted multi-user mode. Quote-only Enterprise separately advertises SSO, with public protocol/feature scope unspecified. Sources: anythingllm:anythingllm:config, anythingllm:anythingllm:cloud. - mfa — Can MFA be enforced? [unknown]: mfa: Can MFA be enforced? MFA enforcement, conditional-access compatibility and company-domain capture were not established from the standard authentication or public Enterprise offer. - conditional_access — Do Entra conditional-access policies apply? [unknown]: conditional_access: Do Entra conditional-access policies apply? MFA enforcement, conditional-access compatibility and company-domain capture were not established from the standard authentication or public Enterprise offer. - domain_capture — Can the company claim its email domain? [unknown]: domain_capture: Can the company claim its email domain? MFA enforcement, conditional-access compatibility and company-domain capture were not established from the standard authentication or public Enterprise offer. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:config, anythingllm:anythingllm:cloud #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North supports OIDC, SAML and hybrid identity patterns in customer deployments. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: conditional_access, domain_capture. - sso_protocols — Which SSO protocols and identity providers work? [supported]: Dex-based broker supports OIDC preferred/SAML legacy, LDAP shim, Entra-LDAP hybrid and authentication proxy; interactive SSO uses authorization-code PKCE. Sources: cohere-north:cohere-north:n-doc-105. - sso_plan — Which plan includes SSO? [partial]: SSO is documented for deployed North; no public commercial tier restriction or included-price matrix retrieved. Sources: cohere-north:cohere-north:n-doc-105. - mfa — Can MFA be enforced? [partial]: Authentication proxy supports external MFA chains; no standalone North-enforced MFA policy was retrieved. Sources: cohere-north:cohere-north:n-doc-105. - conditional_access — Do Entra conditional-access policies apply? [unknown]: Unknown for conditional_access. SSO protocols and IdP integration are documented. Tenant MFA/conditional-access enforcement and domain capture were not exercised. - domain_capture — Can the company claim its email domain? [unknown]: Unknown for domain_capture. SSO protocols and IdP integration are documented. Tenant MFA/conditional-access enforcement and domain capture were not exercised. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-105 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Admins or API clients create users and assign workspaces; provisioning standards and leaver asset transfer remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - scim: Is SCIM provisioning supported? SCIM and identity-provider group synchronization were not established in the public configuration and Enterprise offer. - group_sync: Are identity-provider groups synced? SCIM and identity-provider group synchronization were not established in the public configuration and Enterprise offer. - jit_provisioning: Simple SSO explicitly requires a user to exist before login; an external system can create the user through the API. This is custom provisioning, not a verified automatic IdP JIT flow. - deprovisioning: Admin routes implement user deletion and log the event. A fixture verifying chat/knowledge ownership transfer and active-session revocation was not run. - scim — Is SCIM provisioning supported? [unknown]: scim: Is SCIM provisioning supported? SCIM and identity-provider group synchronization were not established in the public configuration and Enterprise offer. - group_sync — Are identity-provider groups synced? [unknown]: group_sync: Are identity-provider groups synced? SCIM and identity-provider group synchronization were not established in the public configuration and Enterprise offer. - jit_provisioning — Are users created at first login? [partial]: Simple SSO explicitly requires a user to exist before login; an external system can create the user through the API. This is custom provisioning, not a verified automatic IdP JIT flow. Sources: anythingllm:anythingllm:config. - deprovisioning — What happens to a removed user's data and shared assets? [partial]: Admin routes implement user deletion and log the event. A fixture verifying chat/knowledge ownership transfer and active-session revocation was not run. Sources: anythingllm:anythingllm:admin-pin. - seat_assignment — Can admins assign and reclaim seats? [supported]: Admins create/manage users and workspace membership under the no-seat-fee self-hosted licence. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:admin-pin, anythingllm:anythingllm:license. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:config, anythingllm:anythingllm:admin-pin, anythingllm:anythingllm:security, anythingllm:anythingllm:license #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial JIT and alpha SCIM provision users/groups; deletion preserves selected shared assets. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - SCIM alpha; graceful deletion settings beta. Commercial seat assignment unverified. - Remaining atomic gaps: seat_assignment. - scim — Is SCIM provisioning supported? [supported]: SCIM2 alpha provides user/group lifecycle and is bidirectional; incompatible with some connector group-filter settings. Sources: cohere-north:cohere-north:n-doc-112. - group_sync — Are identity-provider groups synced? [partial]: JIT groups hydrate at login/session refresh; SCIM can sync groups including matching preregistered names. No propagation measurement. Sources: cohere-north:cohere-north:n-doc-111, cohere-north:cohere-north:n-doc-112. - jit_provisioning — Are users created at first login? [supported]: First successful login automatically creates user linked to external ID; no pre-invite required in this documented mode. Sources: cohere-north:cohere-north:n-doc-111. - deprovisioning — What happens to a removed user's data and shared assets? [supported]: Disable removes access reversibly; delete uses grace policy, keeps shared agents/workflows/files but removes Microsoft libraries even if shared. Admin can transfer preserved assets; cleanup asynchronous. Sources: cohere-north:cohere-north:n-doc-112, cohere-north:cohere-north:n-doc-90, cohere-north:cohere-north:n-doc-153. - seat_assignment — Can admins assign and reclaim seats? [unknown]: Unknown for seat_assignment. JIT and alpha bidirectional SCIM are documented. Commercial seat assignment and measured identity-propagation timing were not retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-112, cohere-north:cohere-north:n-doc-111, cohere-north:cohere-north:n-doc-90, cohere-north:cohere-north:n-doc-153 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Standard Docker multi-user governance uses Admin, Manager and Default roles plus workspace membership. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - groups: Can permissions be set per group? An independently configurable local/IdP group object and two-group permission fixture were not established. - feature_toggles: Operators configure available Agent skills, providers and workspaces. A fine-grained per-group feature matrix was not established for standard roles. - multi_entity: Workspaces separate access within one installation; legal-entity tenancy, separate operator boundaries and a multi-entity contract were not verified. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Admins control the whole system; Managers manage workspaces but cannot change the system LLM/embedder/vector settings; Default users chat in assigned workspaces. Sources: anythingllm:anythingllm:security. - groups — Can permissions be set per group? [unknown]: groups: Can permissions be set per group? An independently configurable local/IdP group object and two-group permission fixture were not established. - feature_toggles — Which features can be switched on or off per group? [partial]: Operators configure available Agent skills, providers and workspaces. A fine-grained per-group feature matrix was not established for standard roles. Sources: anythingllm:anythingllm:agent-setup, anythingllm:anythingllm:security. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Workspaces separate access within one installation; legal-entity tenancy, separate operator boundaries and a multi-entity contract were not verified. Sources: anythingllm:anythingllm:security. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:agent-setup #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North delegates fine-grained roles/groups; separately administered subsidiaries count as application instances. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The partial atomic answers state their documentation or verification limits. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: System roles include Agent/Automation/Tools managers, Compliance Requester/Approver and Library Access Manager; custom roles and individual temporary assignments. Some grants, including model configuration, must be assigned directly. Sources: cohere-north:cohere-north:n-doc-114. - groups — Can permissions be set per group? [supported]: Permissions/roles/resources assign users, IdP groups or company. JIT group membership updates with token/session refresh; rename/delete needs configuration review. Sources: cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-111. - feature_toggles — Which features can be switched on or off per group? [supported]: Group grants control agents, tools, libraries, automation and some admin capabilities; models additionally have alpha RBAC and inherited-owner exceptions. Sources: cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-134, cohere-north:cohere-north:n-doc-18. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Separate administered installation with its own users/config/data is a separate licensed Application Instance, including business units/subsidiaries. Single-contract multi-instance price unknown. Sources: cohere-north:cohere-north:n-doc-158. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-111, cohere-north:cohere-north:n-doc-134, cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-158 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Authorized accounts can inspect chat/event activity and export chat logs; a full adoption/cost dashboard was not verified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - adoption_dashboard: Is there an adoption dashboard? A dedicated adoption dashboard and pseudonymized/aggregated per-person reporting controls were not established; optional anonymous product telemetry is a separate data flow. - breakdowns: Chat logs are available per workspace/user to authorized accounts; complete model/feature/assistant/group adoption breakdowns were not established. - privacy_modes: Can per-person reporting be limited or pseudonymised? A dedicated adoption dashboard and pseudonymized/aggregated per-person reporting controls were not established; optional anonymous product telemetry is a separate data flow. - adoption_dashboard — Is there an adoption dashboard? [unknown]: adoption_dashboard: Is there an adoption dashboard? A dedicated adoption dashboard and pseudonymized/aggregated per-person reporting controls were not established; optional anonymous product telemetry is a separate data flow. - breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Chat logs are available per workspace/user to authorized accounts; complete model/feature/assistant/group adoption breakdowns were not established. Sources: anythingllm:anythingllm:logs, anythingllm:anythingllm:event. - export — Can usage data be exported? [supported]: Chat logs export as CSV, JSON, Alpaca JSON or OpenAI-style JSONL once at least ten logs exist. Sources: anythingllm:anythingllm:logs. - privacy_modes — Can per-person reporting be limited or pseudonymised? [unknown]: privacy_modes: Can per-person reporting be limited or pseudonymised? A dedicated adoption dashboard and pseudonymized/aggregated per-person reporting controls were not established; optional anonymous product telemetry is a separate data flow. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:logs, anythingllm:anythingllm:event #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Alpha analytics offers detailed adoption/usage exports with named-user visibility. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The vendor marks this control alpha. The catalogue availability field stays unknown because its enum has no alpha value; this does not mean unsupported. - adoption_dashboard — Is there an adoption dashboard? [supported]: Separate Helm/ClickHouse analytics stack reports adoption, agents, automations, tools and libraries with date/group filters. Sources: cohere-north:cohere-north:n-doc-78. - breakdowns — Can usage be broken down by group, model, feature and assistant? [supported]: Groups/models/sources/agents/workflows/tools and user leaderboards documented; sampled/capped cards have explicit limitations. Sources: cohere-north:cohere-north:n-doc-78. - export — Can usage data be exported? [supported]: Cards export CSV data or PNG; CSV includes user names and capped tables export only loaded scope. Sources: cohere-north:cohere-north:n-doc-78. - privacy_modes — Can per-person reporting be limited or pseudonymised? [partial]: Raw analytics event collection can be disabled and retention configured. This does not establish pseudonymisation or removal of named-user reporting in the dashboard. Sources: cohere-north:cohere-north:n-doc-95, cohere-north:cohere-north:n-doc-78. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-78, cohere-north:cohere-north:n-doc-95 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Per-user message quotas control consumption; monetary budgets and cost-centre allocation were not established. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - cost_visibility: Authorized users see chat activity by workspace/user. The reviewed sources do not establish actual billed currency cost by group. - budgets: Admins can set per-user daily message quotas. This is a count limit, not a documented CHF/EUR budget or pooled cost-centre allowance. - chargeback: Can costs be exported per cost centre? Monetary spend caps, model downgrades and cost-centre chargeback export were not verified. - cost_visibility — Can admins see cost or consumption per user and group? [partial]: Authorized users see chat activity by workspace/user. The reviewed sources do not establish actual billed currency cost by group. Sources: anythingllm:anythingllm:logs. - budgets — Can budgets be set per user or group? [partial]: Admins can set per-user daily message quotas. This is a count limit, not a documented CHF/EUR budget or pooled cost-centre allowance. Sources: anythingllm:anythingllm:user-pin. - budget_enforcement — Does reaching a budget alert, block or downgrade? [supported]: The inspected non-admin multi-user chat route aborts before generation when the trailing-24-hour message quota is reached. Sources: anythingllm:anythingllm:chat-pin, anythingllm:anythingllm:user-pin. - chargeback — Can costs be exported per cost centre? [unknown]: chargeback: Can costs be exported per cost centre? Monetary spend caps, model downgrades and cost-centre chargeback export were not verified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:logs, anythingllm:anythingllm:user-pin, anythingllm:anythingllm:chat-pin #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North reports token use and can limit capacity; a currency budget ledger is unverified. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The vendor marks this control alpha. The catalogue availability field stays unknown because its enum has no alpha value; this does not mean unsupported. - Remaining atomic gaps: chargeback. - cost_visibility — Can admins see cost or consumption per user and group? [partial]: Analytics shows user/group/agent/model token activity; Prometheus/Grafana has provider/model billed/raw counters without per-user labels and can undercount. Currency cost reconciliation unknown. Sources: cohere-north:cohere-north:n-doc-78, cohere-north:cohere-north:n-doc-207. - budgets — Can budgets be set per user or group? [partial]: Alpha Flow control caps requests/input/output tokens by user/group/rules, not a verified CHF/EUR spend budget. Sources: cohere-north:cohere-north:n-doc-137. - budget_enforcement — Does reaching a budget alert, block or downgrade? [partial]: Limits block for the window only when Helm proxy deployed; unlimited default/failure allow option can admit use. Currency overshoot bounds and chargeback not tested. Sources: cohere-north:cohere-north:n-doc-137. - chargeback — Can costs be exported per cost centre? [unknown]: Unknown for chargeback. Token metrics and alpha capacity limits are documented. Currency budgets, billing reconciliation and cost-centre allocation were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-78, cohere-north:cohere-north:n-doc-207, cohere-north:cohere-north:n-doc-137 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Event logs record named administrative/security activity and chats are exportable. Immutable audit retention and legal hold remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - siem_export: Can logs stream to a SIEM or be exported? No complete log retention period, tamper-evident integrity model, SIEM streaming contract or eDiscovery/legal-hold workflow was verified. These are event/chat logs, not a certified audit archive. - ediscovery: Are eDiscovery and legal hold supported? No complete log retention period, tamper-evident integrity model, SIEM streaming contract or eDiscovery/legal-hold workflow was verified. These are event/chat logs, not a certified audit archive. - log_retention: How long are logs kept? No complete log retention period, tamper-evident integrity model, SIEM streaming contract or eDiscovery/legal-hold workflow was verified. These are event/chat logs, not a certified audit archive. - admin_events — Are admin and security events logged? [supported]: Pinned admin routes log user creation/deletion, invitation and API-key events; docs also name logins, setting changes and uploads. Sources: anythingllm:anythingllm:admin-pin, anythingllm:anythingllm:event. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [supported]: Workspace chat history/logs retain prompts/responses and expose permissioned exports. Retention and external copies depend on the deployment. Sources: anythingllm:anythingllm:logs. - siem_export — Can logs stream to a SIEM or be exported? [unknown]: siem_export: Can logs stream to a SIEM or be exported? No complete log retention period, tamper-evident integrity model, SIEM streaming contract or eDiscovery/legal-hold workflow was verified. These are event/chat logs, not a certified audit archive. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: ediscovery: Are eDiscovery and legal hold supported? No complete log retention period, tamper-evident integrity model, SIEM streaming contract or eDiscovery/legal-hold workflow was verified. These are event/chat logs, not a certified audit archive. - log_retention — How long are logs kept? [unknown]: log_retention: How long are logs kept? No complete log retention period, tamper-evident integrity model, SIEM streaming contract or eDiscovery/legal-hold workflow was verified. These are event/chat logs, not a certified audit archive. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:admin-pin, anythingllm:anythingllm:event, anythingllm:anythingllm:logs #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Alpha audits and approval-controlled compliance export coexist with operator log forwarding. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - content_logging: Alpha Compliance uses a request/approval workflow for 24-hour conversation review and CSV export, including guardrail-blocked/redacted messages. Self-approval is forbidden; view access and self-grants are restricted. Exact Organization admin approval rights remain unknown because the permission table and Reviewing requests prerequisite disagree. - siem_export: Audit records can be queried through GET /v1/admin/audits, with an actions endpoint and date/action filters. A complete supported SIEM integration, delivery/retry guarantee or content-stream schema was not established. - ediscovery: Compliance supports investigation/preservation downloads; specific eDiscovery/legal hold preventing deletion was not established. - log_retention: Retrieved Audits and Compliance pages do not state numeric audit-log retention or immutability. Analytics-event retention is a different dataset, and the general Security page could not be retrieved in public representations. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/audits?format=html, https://private.docs.cohere.com/north/docs/admin/compliance?format=html, https://private.docs.cohere.com/north/docs/admin/permissions?format=html. No additional scoped evidence established this answer. - admin_events — Are admin and security events logged? [supported]: Audits records identity, permission, configuration, model/tool, sharing and compliance events; filters and GET audit API exist. Sources: cohere-north:cohere-north:n-doc-140-20261026. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [partial]: Alpha Compliance uses a request/approval workflow for 24-hour conversation review and CSV export, including guardrail-blocked/redacted messages. Self-approval is forbidden; view access and self-grants are restricted. Exact Organization admin approval rights remain unknown because the permission table and Reviewing requests prerequisite disagree. Sources: cohere-north:cohere-north:n-doc-139-20261026. - siem_export — Can logs stream to a SIEM or be exported? [partial]: Audit records can be queried through GET /v1/admin/audits, with an actions endpoint and date/action filters. A complete supported SIEM integration, delivery/retry guarantee or content-stream schema was not established. Sources: cohere-north:cohere-north:n-doc-140-20261026. - ediscovery — Are eDiscovery and legal hold supported? [partial]: Compliance supports investigation/preservation downloads; specific eDiscovery/legal hold preventing deletion was not established. Sources: cohere-north:cohere-north:n-doc-139-20261026. - log_retention — How long are logs kept? [unknown]: Retrieved Audits and Compliance pages do not state numeric audit-log retention or immutability. Analytics-event retention is a different dataset, and the general Security page could not be retrieved in public representations. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/audits?format=html, https://private.docs.cohere.com/north/docs/admin/compliance?format=html, https://private.docs.cohere.com/north/docs/admin/permissions?format=html. No additional scoped evidence established this answer. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-140-20261026, cohere-north:cohere-north:n-doc-139-20261026 ### 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. #### AnythingLLM Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Selected-customer beta HiddenLayer can detect/block/redact PII, with permissive defaults and failure paths. Availability: beta Delivery: native Scope: surfaces=Customer-hosted North and Compass Kubernetes deployment, North 2 web application and Admin console; version=not specified; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=Selected-customer HiddenLayer beta deployment; commercial cost unverified; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: custom_patterns. - pii_detection — Is personal data detected in prompts and files? [partial]: HiddenLayer scans configured prompt/response/tool content and PII entity types; beta available to selected customers after deployment. File coverage depends on what reaches scanned requests, not a verified whole-file DLP pipeline. Sources: cohere-north:cohere-north:n-doc-138. - pii_action — Is it redacted, masked, blocked or only warned? [partial]: ALLOW/BLOCK/REDACT supported. Default monitor_only does not enforce; background scans and timeouts can occur after delivery, unsupported entities fail open. Effectiveness not tested. Sources: cohere-north:cohere-north:n-doc-138. - custom_patterns — Can admins add custom patterns or terms? [unknown]: Unknown for custom_patterns. Selected-customer beta HiddenLayer scanning is documented. Custom regex/customer dictionaries and an external enterprise DLP integration matrix were not retrieved. - dlp_integration — Does it integrate with an existing DLP product? [partial]: HiddenLayer AIDR integration documented; generic existing-DLP/Purview connector not established. Sources: cohere-north:cohere-north:n-doc-138, cohere-north:cohere-north:n-doc-193. - filter_location — Where does filtering run? [supported]: Documented self-contained GPU engine runs inside customer cluster with external HiddenLayer cloud disabled; requires both HiddenLayer and cohere-guardrails releases. Sources: cohere-north:cohere-north:n-doc-193. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-138, cohere-north:cohere-north:n-doc-193 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workspace instructions can guide models; a mandatory organization-wide policy and violation system remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - org_instructions: Admins/Managers configure workspace/system prompt context and model defaults. A single unavoidable organization policy and its enforcement were not established. - usage_notice: Can users be required to accept a usage policy? Required policy acknowledgement, semantic content filters and administrator policy-violation reporting were not established by the configuration/security sources. Model instructions are not a demonstrated content-control guarantee. - content_filters: Are content filters configurable? Required policy acknowledgement, semantic content filters and administrator policy-violation reporting were not established by the configuration/security sources. Model instructions are not a demonstrated content-control guarantee. - violation_reporting: Are policy hits visible to admins? Required policy acknowledgement, semantic content filters and administrator policy-violation reporting were not established by the configuration/security sources. Model instructions are not a demonstrated content-control guarantee. - org_instructions — Can admins set organisation-wide instructions? [partial]: Admins/Managers configure workspace/system prompt context and model defaults. A single unavoidable organization policy and its enforcement were not established. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:systemprompt, anythingllm:anythingllm:llmconfig. - usage_notice — Can users be required to accept a usage policy? [unknown]: usage_notice: Can users be required to accept a usage policy? Required policy acknowledgement, semantic content filters and administrator policy-violation reporting were not established by the configuration/security sources. Model instructions are not a demonstrated content-control guarantee. - content_filters — Are content filters configurable? [unknown]: content_filters: Are content filters configurable? Required policy acknowledgement, semantic content filters and administrator policy-violation reporting were not established by the configuration/security sources. Model instructions are not a demonstrated content-control guarantee. - violation_reporting — Are policy hits visible to admins? [unknown]: violation_reporting: Are policy hits visible to admins? Required policy acknowledgement, semantic content filters and administrator policy-violation reporting were not established by the configuration/security sources. Model instructions are not a demonstrated content-control guarantee. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:systemprompt, anythingllm:anythingllm:llmconfig #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Organisation instructions/policy acceptance exist; content safety checks are advisory. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The vendor marks this control alpha. The catalogue availability field stays unknown because its enum has no alpha value; this does not mean unsupported. - org_instructions — Can admins set organisation-wide instructions? [supported]: Optional company instructions append to preamble across all models; agent instructions also apply. Sources: cohere-north:cohere-north:n-doc-86. - usage_notice — Can users be required to accept a usage policy? [supported]: Alpha hosted terms can require acceptance at sign-up/tool use and re-acceptance after versions. External terms URL overrides hosted terms. Sources: cohere-north:cohere-north:n-doc-145. - content_filters — Are content filters configurable? [partial]: Alpha Content Compliance Auditor offers Contextual/Strict, targeted user/group rules and qualified models. Model chooses whether to check/refuse; unavailable/error verdict can be safe, so not mandatory enforcement. Sources: cohere-north:cohere-north:n-doc-138. - violation_reporting — Are policy hits visible to admins? [supported]: Guardrail Events list conversation decisions/categories/actions. Safety Block means unsafe verdict to model, not proof response was prevented. Sources: cohere-north:cohere-north:n-doc-138. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-86, cohere-north:cohere-north:n-doc-145, cohere-north:cohere-north:n-doc-138 ## 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Self-hosted locations are customer-selected. Managed Cloud uses AWS, but a guaranteed country for all storage/inference/support was not established. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - backups_logs_region: Self-hosted logs/storage follow deployment choices; telemetry is optional. Cloud backup/log geography and actual egress were not audited. - support_access_region: Cloud privacy explicitly allows necessary Mintplex team access for debugging/maintenance; support-access country restrictions were not established. - swiss_hosting: Customers can self-host on Swiss infrastructure. A vendor-managed Swiss Cloud region and Swiss inference/support commitment were not established. - residency_plan: Customer-operated placement is available with self-hosting. Public Basic/Pro/Enterprise offers do not establish a complete Swiss/EU data-boundary package. - storage_region — Where are chats, files and indexes stored? [supported]: Docker data/embedding storage is customer configured; Desktop uses its local OS data directory. Managed Cloud documentation identifies AWS but does not establish a country. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:storage, anythingllm:anythingllm:cloud-overview. - inference_region — Where do model calls run, per provider? [supported]: Local endpoints run where the operator deploys them; Azure/AWS/Vertex routes and cloud APIs use the selected provider. Self-hosting the UI does not fix inference geography. Sources: anythingllm:anythingllm:built-in, anythingllm:anythingllm:azure, anythingllm:anythingllm:bedrock, anythingllm:anythingllm:vertex. - backups_logs_region — Where are backups, logs and telemetry? [partial]: Self-hosted logs/storage follow deployment choices; telemetry is optional. Cloud backup/log geography and actual egress were not audited. Sources: anythingllm:anythingllm:privacy, anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:localdocker. - support_access_region — From where can vendor staff access data? [partial]: Cloud privacy explicitly allows necessary Mintplex team access for debugging/maintenance; support-access country restrictions were not established. Sources: anythingllm:anythingllm:privacy-cloud. - swiss_hosting — Is Swiss hosting available? [partial]: Customers can self-host on Swiss infrastructure. A vendor-managed Swiss Cloud region and Swiss inference/support commitment were not established. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:cloud-overview. - residency_plan — Which plan or option provides residency? [partial]: Customer-operated placement is available with self-hosting. Public Basic/Pro/Enterprise offers do not establish a complete Swiss/EU data-boundary package. Sources: anythingllm:anythingllm:docker, anythingllm:anythingllm:cloud. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:storage, anythingllm:anythingllm:cloud-overview, anythingllm:anythingllm:built-in, anythingllm:anythingllm:azure, anythingllm:anythingllm:bedrock, anythingllm:anythingllm:vertex, anythingllm:anythingllm:privacy, anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:docker, anythingllm:anythingllm:cloud #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Private North follows customer infrastructure placement; external inference and support need separate scope. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The partial atomic answers state their documentation or verification limits. - storage_region — Where are chats, files and indexes stored? [partial]: North/Compass data resides in customer VPC/on-prem storage. Customer chooses country; no fixed vendor-hosted North region matrix retrieved. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-168. - inference_region — Where do model calls run, per provider? [partial]: Local model chart stays in customer environment; optional Vault/Foundry/other APIs route inference to separately configured regions. Actual contracted provider region unverified. Sources: cohere-north:cohere-north:n-doc-168, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-doc-218. - backups_logs_region — Where are backups, logs and telemetry? [partial]: Operators configure backups, logs and telemetry collectors in their environment. Docs do not fix country or require all exports remain local. Sources: cohere-north:cohere-north:n-doc-214, cohere-north:cohere-north:n-doc-208, cohere-north:cohere-north:n-doc-146. - support_access_region — From where can vendor staff access data? [partial]: Private-deployment commitment says Cohere does not receive customer prompts; optional Vault processes inference and support bundles may be shared. Support-staff countries/contract access rules unknown. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-217. - swiss_hosting — Is Swiss hosting available? [partial]: Customer can place private infrastructure in its chosen country, but a Cohere-operated Swiss North hosting SKU/residency promise was not established. Sources: cohere-north:cohere-north:n-private. - residency_plan — Which plan or option provides residency? [partial]: Customer-managed private deployment controls location; optional external inference/telemetry/connector routes require separate governance. No named residency add-on price retrieved. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-217. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-168, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-doc-218, cohere-north:cohere-north:n-doc-214, cohere-north:cohere-north:n-doc-208, cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-commitments ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Docker supports customer-cloud/on-premise operation; Cloud sells isolated managed instances and Desktop is a separate local client. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - multi_tenant_saas: Is a shared SaaS offered? A shared multi-tenant SaaS was not established: the public managed offer describes private isolated instances. - air_gapped: Local models/embeddings can run after assets are downloaded. A full disconnected fixture was not run; online tools and optional periodically validated Desktop Pro need separate treatment. - multi_tenant_saas — Is a shared SaaS offered? [unknown]: multi_tenant_saas: Is a shared SaaS offered? A shared multi-tenant SaaS was not established: the public managed offer describes private isolated instances. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [supported]: The managed Cloud overview describes one isolated AWS instance per customer. Current pricing lists Basic and Pro, with Enterprise custom services; no numeric seat minimum is published in the reviewed offer. Sources: anythingllm:anythingllm:cloud-overview, anythingllm:anythingllm:cloud. - customer_cloud — Can it run in the customer's own cloud account, from what size? [supported]: Docker can run on customer-selected servers/cloud accounts without an MIT software seat minimum. Sources: anythingllm:anythingllm:docker, anythingllm:anythingllm:localdocker, anythingllm:anythingllm:license. - on_premise — Can the whole platform run on customer infrastructure, from what size? [supported]: Customers can operate the Docker stack with local providers; commercial Enterprise also advertises on-premise support. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:models, anythingllm:anythingllm:cloud. - air_gapped — Can it run without internet access? [partial]: Local models/embeddings can run after assets are downloaded. A full disconnected fixture was not run; online tools and optional periodically validated Desktop Pro need separate treatment. Sources: anythingllm:anythingllm:built-in, anythingllm:anythingllm:local-embed, anythingllm:anythingllm:pro-key. - mode_feature_gaps — Which features are missing outside SaaS? [supported]: Desktop is single-user; Docker provides multi-user administration; Cloud explicitly excludes built-in inference, custom coded Agents and MCP. Scheduled Jobs and mail skills are single-user only. Sources: anythingllm:anythingllm:desktop, anythingllm:anythingllm:cloud-limits, anythingllm:anythingllm:job, anythingllm:anythingllm:outlook. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:cloud-overview, anythingllm:anythingllm:cloud, anythingllm:anythingllm:docker, anythingllm:anythingllm:localdocker, anythingllm:anythingllm:license, anythingllm:anythingllm:models, anythingllm:anythingllm:built-in, anythingllm:anythingllm:local-embed, anythingllm:anythingllm:pro-key, anythingllm:anythingllm:desktop, anythingllm:anythingllm:cloud-limits, anythingllm:anythingllm:job, anythingllm:anythingllm:outlook #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North can run in customer cloud, on-prem or air-gapped; optional managed inference changes that boundary. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: multi_tenant_saas. - multi_tenant_saas — Is a shared SaaS offered? [unknown]: Unknown for multi_tenant_saas. Private VPC/on-prem/air-gapped deployment is documented. Seat floors, full SaaS offers and every disconnected-mode feature exception were not established. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [partial]: Customer-managed North instance supported; Model Vault inference is dedicated Cohere-managed. Minimum seat/capacity size unpriced. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-vault. - customer_cloud — Can it run in the customer's own cloud account, from what size? [partial]: North Helm installs on customer Kubernetes/VPC; infrastructure/network/security operated by customer. No minimum seats retrieved. Sources: cohere-north:cohere-north:n-doc-165, cohere-north:cohere-north:n-private. - on_premise — Can the whole platform run on customer infrastructure, from what size? [partial]: Whole North app plus Compass/models documented for customer on-prem Kubernetes; component/GPU dependencies apply. No seat floor retrieved. Sources: cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-doc-168. - air_gapped — Can it run without internet access? [partial]: Vendor explicitly offers air-gapped on-prem deployment. External API/search/remote MCP unavailable without egress; registry/image supply needs mirroring. Contracted disconnected feature matrix not retrieved. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-159. - mode_feature_gaps — Which features are missing outside SaaS? [partial]: Remote MCP needs internet; external search/inference also need provider access. Local visual parsing/guardrails require extra models/GPU services. Full parity unknown. Sources: cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-14, cohere-north:cohere-north:n-doc-193. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-vault, cohere-north:cohere-north:n-doc-165, cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-doc-168, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-159, cohere-north:cohere-north:n-doc-14, cohere-north:cohere-north:n-doc-193 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Application locality and provider retention are separate; no universal no-training or zero-retention contract was verified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - vendor_training: The Desktop policy describes local chat/document storage and optional anonymous telemetry. Cloud terms grant platform-improvement usage rights without a specific reviewed model-training exclusion. This is not a blanket no-training assurance. - provider_training: Do model providers train on it under this product's contracts? No configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. - provider_retention: How long do model providers keep prompts, including for abuse monitoring? No configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. - zero_retention: Is zero data retention available, and on which plan? No configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. - human_review: Can provider staff review content? No configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. - vendor_training — Does the vendor train on customer content? [partial]: The Desktop policy describes local chat/document storage and optional anonymous telemetry. Cloud terms grant platform-improvement usage rights without a specific reviewed model-training exclusion. This is not a blanket no-training assurance. Sources: anythingllm:anythingllm:privacy-desktop, anythingllm:anythingllm:terms-cloud. - provider_training — Do model providers train on it under this product's contracts? [unknown]: provider_training: Do model providers train on it under this product's contracts? No configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [unknown]: provider_retention: How long do model providers keep prompts, including for abuse monitoring? No configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. - zero_retention — Is zero data retention available, and on which plan? [unknown]: zero_retention: Is zero data retention available, and on which plan? No configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. - human_review — Can provider staff review content? [unknown]: human_review: Can provider staff review content? No configured provider agreement was reviewed for training use, abuse-retention/human review or zero-data-retention eligibility. Cloud summary models receive meeting transcripts, and memories are sent to the selected chat provider. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:privacy-desktop, anythingllm:anythingllm:terms-cloud #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Private North and hosted model APIs have different data-use policies. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The partial atomic answers state their documentation or verification limits. - vendor_training — Does the vendor train on customer content? [partial]: Private deployment commitments say Cohere receives no prompts/outputs. Cohere Platform API separately permits opt-out training; do not apply that SaaS default to private North. Optional Vault processes inference. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-217. - provider_training — Do model providers train on it under this product's contracts? [partial]: Self-hosted inference does not call external provider. If operator configures third-party APIs, their customer contracts govern; no blanket no-training assurance retrieved. Sources: cohere-north:cohere-north:n-doc-177, cohere-north:cohere-north:n-commitments. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [partial]: Separate Cohere SaaS model Platform logs default30 days with legal/contract/abuse exceptions; private North retention configured locally. Other configured provider retention unverified. Sources: cohere-north:cohere-north:n-commitments. - zero_retention — Is zero data retention available, and on which plan? [partial]: North↔Model Vault guide documents optional ZDR for inference; North app data remains stored locally. Platform ZDR approval applies separately; not zero chat persistence. Sources: cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-commitments. - human_review — Can provider staff review content? [partial]: Private prompts do not reach Cohere by default. Platform security teams may review flagged logs; local admins/investigators can review under North compliance process. Third-party staff rules unknown. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-139. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-doc-177, cohere-north:cohere-north:n-doc-139 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Removing workspace access differs from full document erasure; managed Cloud states immediate unrecoverable deletion on cancellation. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - default_retention: Self-hosted documents/history remain in local storage until removed; a universal duration covering chats, indexes, logs, backups and memory was not established. - admin_retention: Can admins set retention periods? A general time-based admin retention scheduler and verified deletion of backups/external-provider copies were not established. - default_retention — What is retained and for how long by default? [partial]: Self-hosted documents/history remain in local storage until removed; a universal duration covering chats, indexes, logs, backups and memory was not established. Sources: anythingllm:anythingllm:privacy, anythingllm:anythingllm:storage. - admin_retention — Can admins set retention periods? [unknown]: admin_retention: Can admins set retention periods? A general time-based admin retention scheduler and verified deletion of backups/external-provider copies were not established. - user_deletion — Can users delete their chats and files permanently? [supported]: Workspace removal deletes that workspace’s vectors but retains the reusable document. My Documents deletion removes the parsed source/cache and all workspace copies according to the privacy guide. Sources: anythingllm:anythingllm:privacy. - contract_end_deletion — What is deleted at contract end, and when? [supported]: For managed Cloud only, the current policy and generic terms state permanent non-recoverable instance/data deletion at cancellation, nonpayment or manual termination. No grace period is promised. Sources: anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:terms-cloud. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:privacy, anythingllm:anythingllm:storage, anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:terms-cloud #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Retention and deletion are operator-configured with separate conversation and user policies. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Conversation retention alpha; graceful account deletion beta. Commercial exit deadline unknown. - Remaining atomic gaps: contract_end_deletion. - default_retention — What is retained and for how long by default? [partial]: Automatic conversation age retention off by default; manually deleted conversations still hard-delete on hourly job with zero effective timeout. Backup/shared-resource retention differs. Sources: cohere-north:cohere-north:n-doc-88, cohere-north:cohere-north:n-doc-153. - admin_retention — Can admins set retention periods? [supported]: Alpha enabled defaults90 days from creation plus30-day soft-delete timeout; configurable1+days and0–365days. Retroactive changes and batch queues can affect timing. Sources: cohere-north:cohere-north:n-doc-88. - user_deletion — Can users delete their chats and files permanently? [partial]: Users delete conversations; hourly hard cleanup removes messages/metadata with best-effort external resources. Account private-data cleanup follows beta grace policy; shared assets can persist. Sources: cohere-north:cohere-north:n-doc-153, cohere-north:cohere-north:n-doc-90. - contract_end_deletion — What is deleted at contract end, and when? [unknown]: Unknown for contract_end_deletion. Conversation/user deletion policies are documented. Commercial contract-end deletion and guaranteed backup purge deadlines were not retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-88, cohere-north:cohere-north:n-doc-153, cohere-north:cohere-north:n-doc-90 ### 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. #### AnythingLLM Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Published terms name Cohere Inc. and the Trust Center lists subprocessors; ultimate post-combination ownership and the complete contracted North inventory remain unknown. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=Published Cohere terms and Trust Center as retrieved 2026-10-21; post-combination ownership excluded as unverified; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - subprocessor_list: Trust Center exposes subprocessors but no visible revision date; complete North-specific contracted inventory not verified. - subprocessor_countries: Visible rows list Google Cloud, Fullstory, LaunchDarkly, New Relic, Retool, Sentry, Segment, Sendgrid and Vercel in USA. Scope mainly hosted services, not automatic private North content recipients. - change_notification: Unknown for change_notification. Public Trust Center lists subprocessors without a visible revision date. Full contracted North scope, change notices and post-combination legal structure remain unverified. Search on 2026-10-26: https://trustcenter.cohere.com/?format=html, https://cohere.com/terms-of-use, https://cohere.com/blog/cohere-and-aleph-alpha-sign-agreement. No additional scoped evidence established this answer. - parent_jurisdiction: The public terms name Cohere Inc. and Ontario/Toronto law. The September 16 Aleph Alpha business-combination agreement remains described as subject to final regulatory approvals in that announcement. Current October 15 AISLE copy calls Aleph Alpha a partnership, not a completed acquisition; no subsequent first-party closing notice was located. A post-combination parent/jurisdiction is not asserted. - transfer_mechanism: Trust Center says its multi-jurisdictional DPA incorporates2021 EU SCCs and describes a TIA. NDA-gated DPA and exact Swiss adaptations not inspected. - government_access_policy: Trust FAQ describes prompt customer notice of government requests unless prohibited, within DPA commitments. Actual North contract/transparency statistics unverified. - subprocessor_list — Is a dated sub-processor list published? [partial]: Trust Center exposes subprocessors but no visible revision date; complete North-specific contracted inventory not verified. Sources: cohere-north:cohere-north:n-trust-20261026. - subprocessor_countries — Which countries do sub-processors operate in? [partial]: Visible rows list Google Cloud, Fullstory, LaunchDarkly, New Relic, Retool, Sentry, Segment, Sendgrid and Vercel in USA. Scope mainly hosted services, not automatic private North content recipients. Sources: cohere-north:cohere-north:n-trust-20261026. - change_notification — Are customers notified of sub-processor changes? [unknown]: Unknown for change_notification. Public Trust Center lists subprocessors without a visible revision date. Full contracted North scope, change notices and post-combination legal structure remain unverified. Search on 2026-10-26: https://trustcenter.cohere.com/?format=html, https://cohere.com/terms-of-use, https://cohere.com/blog/cohere-and-aleph-alpha-sign-agreement. No additional scoped evidence established this answer. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: The public terms name Cohere Inc. and Ontario/Toronto law. The September 16 Aleph Alpha business-combination agreement remains described as subject to final regulatory approvals in that announcement. Current October 15 AISLE copy calls Aleph Alpha a partnership, not a completed acquisition; no subsequent first-party closing notice was located. A post-combination parent/jurisdiction is not asserted. Sources: cohere-north:cohere-north:n-terms-20261026, cohere-north:cohere-north:n-combination-20261026, cohere-north:cohere-north:corporate-aisle-20261026. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [partial]: Trust Center says its multi-jurisdictional DPA incorporates2021 EU SCCs and describes a TIA. NDA-gated DPA and exact Swiss adaptations not inspected. Sources: cohere-north:cohere-north:n-trust-20261026. - government_access_policy — Is there a published government-access or transparency policy? [partial]: Trust FAQ describes prompt customer notice of government requests unless prohibited, within DPA commitments. Actual North contract/transparency statistics unverified. Sources: cohere-north:cohere-north:n-trust-20261026. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-trust-20261026, cohere-north:cohere-north:n-terms-20261026, cohere-north:cohere-north:n-combination-20261026, cohere-north:cohere-north:corporate-aisle-20261026 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Generic Cloud terms specify California law; a negotiated DPA and regulatory or sector package were not verified. Availability: generally-available Delivery: native Scope: surfaces=AnythingLLM Cloud managed instance, Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - dpa: Is a DPA available, and is it negotiable? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. - revdsg_gdpr: Does the DPA cover revDSG and GDPR? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. - governing_law: Managed Cloud terms specify California, United States law and explicitly exclude self-hosted deployments. A specific court and enterprise override were not established. - ai_act_materials: Is EU AI Act documentation provided? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. - sector_materials: Are FINMA or other sector materials provided? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. - dpa — Is a DPA available, and is it negotiable? [unknown]: dpa: Is a DPA available, and is it negotiable? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [unknown]: revdsg_gdpr: Does the DPA cover revDSG and GDPR? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. - governing_law — Which law and court govern the contract? [partial]: Managed Cloud terms specify California, United States law and explicitly exclude self-hosted deployments. A specific court and enterprise override were not established. Sources: anythingllm:anythingllm:terms-cloud. - ai_act_materials — Is EU AI Act documentation provided? [unknown]: ai_act_materials: Is EU AI Act documentation provided? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. - sector_materials — Are FINMA or other sector materials provided? [unknown]: sector_materials: Are FINMA or other sector materials provided? No reviewed/negotiable DPA, revDSG/GDPR processing annex, EU AI Act role documentation or FINMA/sector secrecy agreement was obtained. Privacy-policy rights are not substituted for a DPA. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:terms-cloud #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA and regulatory resources are listed, but North-specific contract terms remain unverified. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The partial atomic answers state their documentation or verification limits. - dpa — Is a DPA available, and is it negotiable? [partial]: Trust Center says DPA available on request with NDA; Enterprise Data Commitments offers SaaS DPA but says private deployment receives no input processing. No contact/request made; North negotiated terms unknown. Sources: cohere-north:cohere-north:n-trust, cohere-north:cohere-north:n-commitments. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: Vendor says multi-jurisdictional DPA/GDPR compliance. Explicit revised Swiss DSG terms not retrieved from gated DPA. Sources: cohere-north:cohere-north:n-trust. - governing_law — Which law and court govern the contract? [partial]: General 2022website/service terms choose Ontario/Canadian law and Toronto courts, subject to subscription agreement. Binding North commercial agreement not retrieved. Sources: cohere-north:cohere-north:n-terms. - ai_act_materials — Is EU AI Act documentation provided? [partial]: Trust Center lists EU AI Act/GPAI Code of Practice FAQs. Contents and North deployment obligations not inspected. Sources: cohere-north:cohere-north:n-trust. - sector_materials — Are FINMA or other sector materials provided? [partial]: Trust FAQ says BAA only for approved custom model development and excludes Cohere-hosted SaaS/PHI. North-specific health/FINMA contract not retrieved. Sources: cohere-north:cohere-north:n-trust. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-trust, cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-terms ### 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. #### AnythingLLM Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Trust Center lists attestations; certificates and reports were not verified. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: c5. - iso_27001 — ISO 27001 with scope and validity? [partial]: ISO 27001 certificate listed behind request; issuer, scope and validity unknown. Sources: cohere-north:cohere-north:n-trust. - soc2 — SOC 2 type, period and covered service? [partial]: SOC 2 Type II annual audit/report listed, request and signed mutual NDA needed; report period/scope not inspected. Sources: cohere-north:cohere-north:n-trust. - c5 — BSI C5 attestation? [unknown]: Unknown for c5. Trust Center lists certificates and reports behind requests. Issuer, scope, validity and independent report contents were not inspected. - other_certifications — Which other certificates (27701, 42001, TISAX)? [partial]: ISO 42001 and UK Cyber Essentials for Cohere Inc./Cohere UK listed. Certificate validity/scope not inspected. Sources: cohere-north:cohere-north:n-trust. - report_access — How can customers obtain reports? [supported]: Trust Center requests gate reports; SOC 2 requires signed mutual NDA, DPA also NDA-gated. No request made. Sources: cohere-north:cohere-north:n-trust. - pentest — Are independent penetration test summaries available? [partial]: Latest API and web penetration test reports listed behind request; findings/scope/date not inspected. Sources: cohere-north:cohere-north:n-trust. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-trust ### 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). #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Private deployment and managed-instance isolation are documented; default encryption of all content and a product key-custody service were not verified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - encryption_at_rest: Is data encrypted at rest? Default encryption-at-rest/transit settings for every database, file, backup and provider route were not verified. - customer_managed_keys: Self-hosted operators control infrastructure/secrets. A product-level BYOK/HYOK content-encryption contract was not established. - tenant_isolation: Managed Cloud describes private isolated AWS instances and resources per customer. This was not independently tested and is separate from source/workspace access control. - encryption_at_rest — Is data encrypted at rest? [unknown]: encryption_at_rest: Is data encrypted at rest? Default encryption-at-rest/transit settings for every database, file, backup and provider route were not verified. - customer_managed_keys — Can the customer manage or hold the keys? [partial]: Self-hosted operators control infrastructure/secrets. A product-level BYOK/HYOK content-encryption contract was not established. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:config. - private_networking — Is private connectivity or IP restriction available? [supported]: Docker can be placed on customer infrastructure; Desktop API listens on loopback unless optional network discovery is enabled. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:desktop. - tenant_isolation — How are customers separated in shared SaaS? [partial]: Managed Cloud describes private isolated AWS instances and resources per customer. This was not independently tested and is separate from source/workspace access control. Sources: anythingllm:anythingllm:cloud-overview. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:config, anythingllm:anythingllm:desktop, anythingllm:anythingllm:cloud-overview #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Customer keys can encrypt chat columns; workflows and other stores need separate controls. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The partial atomic answers state their documentation or verification limits. - encryption_at_rest — Is data encrypted at rest? [partial]: Optional deployment-level AES256GCM envelope encryption covers sensitive PostgreSQL chat columns, excluding automations/workflows. Operator must secure object/index/backups and database volumes separately. Sources: cohere-north:cohere-north:n-doc-154, cohere-north:cohere-north:n-doc-146. - customer_managed_keys — Can the customer manage or hold the keys? [partial]: Operator supplies32-byte master key in Kubernetes Secret or chart generates it; wrapped DEKs stay in database, key rotation supported. Hardware-held external-KMS entitlement not established. Sources: cohere-north:cohere-north:n-doc-154. - private_networking — Is private connectivity or IP restriction available? [partial]: Customer manages VPC, ingress/egress, TLS and Kubernetes network policies; private/on-prem operation documented. These are deployment tasks, not proof every installation enforces them. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-doc-159. - tenant_isolation — How are customers separated in shared SaaS? [partial]: Each separately administered installation has own users/config/data; customer operates cluster/network isolation. Multi-tenant hosted North architecture not established. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-doc-146. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-154, cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-159, cohere-north:cohere-north:n-doc-158 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Local/self-hosted and managed Cloud content-access paths differ. Cloud permits necessary operational team access; a Mintplex staff/sub-processor professional-secrecy undertaking and its plan/add-on terms remain unverified. Availability: unknown Delivery: unknown Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation and managed-service terms retrieved 2026-10-21; this row does not infer contract terms from the source-code licence; plan=Mixed modes identified per answer: Docker/Desktop on customer infrastructure; Basic/Pro managed Cloud dedicated AWS instance; Enterprise custom services checked separately; add_ons=none stated; deployment_mode=not specified; region=Customer-selected Docker/Desktop location; managed Cloud AWS country and provider/support staff locations unverified; no DE/CH secrecy-contract variant established; os=not specified. Limitations: - The secrecy undertaking, sub-processor coverage, offering and professional-secrecy-specific documentation remain unknown. - content_access: Exact Cloud staff/sub-processor plain-text access, provider human access and deployment-specific operator grants remain unverified. - Technical data controls, a DPA, privacy wording and no-training statements do not establish the requested contractual undertaking. No legal compliance assessment is made. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: No § 203 StGB / Art. 321 StGB or equivalent professional-secrecy undertaking binding Mintplex staff was obtained from the reviewed Cloud terms/privacy, Desktop privacy, pricing and product documentation. Generic privacy commitments are not recorded as that undertaking. Sources: anythingllm:anythingllm:terms-cloud, anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:privacy-desktop. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The Cloud policy names AWS, Stripe and PostHog, but no professional-secrecy undertaking extending to covered sub-processors and their personnel was obtained. Customer-selected model/tool services require separate terms; coverage of their staff remains unknown. Sources: anythingllm:anythingllm:privacy-cloud. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: The public Basic, Pro and quote-only Enterprise descriptions did not establish a professional-secrecy package, paid add-on, plan entitlement or price. Availability under a separately negotiated Enterprise agreement remains unknown; no sales contact was made. Sources: anythingllm:anythingllm:cloud. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: Docker data is held on customer-mounted storage; Desktop documents local chat/file storage. Local or external models can be selected. For the separate managed Cloud service, the policy permits necessary Mintplex team instance access for debugging and maintenance and names AWS infrastructure; configured remote models process inference requests. The documents do not establish exactly which plain-text fields operational staff/sub-processors can see or each provider’s human-access permissions. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:privacy-desktop, anythingllm:anythingllm:secrecy-cloud-access, anythingllm:anythingllm:secrecy-model-routing. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Public Cloud terms/privacy, Desktop privacy and setup guides provide general data-handling information. No product-scoped DE/CH secrecy contract template, staff/sub-processor annex or professional-body guidance was located in the reviewed public sources and targeted searches. Sources: anythingllm:anythingllm:terms-cloud, anythingllm:anythingllm:privacy-desktop, anythingllm:anythingllm:secrecy-cloud-access. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:terms-cloud, anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:privacy-desktop, anythingllm:anythingllm:cloud, anythingllm:anythingllm:localdocker, anythingllm:anythingllm:secrecy-cloud-access, anythingllm:anythingllm:secrecy-model-routing #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Profession-specific secrecy undertaking and add-on remain unknown; general confidentiality and scoped content-access controls do not establish §203 StGB or Art.321 StGB coverage. Availability: unknown Delivery: unknown Scope: surfaces=Customer-hosted North and Compass Kubernetes deployment, North 2 web application and Admin console, Optional Cohere-managed Model Vault inference with customer-hosted North; version=North 2.0.1; plan=Customer-hosted North 2.0.1 under custom commercial contract; optional Model Vault/external models separately scoped; add_ons=none stated; deployment_mode=not specified; region=No profession-specific DE/CH contractual scope verified; deployment/provider regions follow the other scoped claims.; os=not specified. Limitations: - Contract facts only; no legal suitability assessment. No profession-specific commitment or paid option inferred from generic confidentiality, hosting, encryption or no-training terms. - Public, unauthenticated source pass only; no sales contact, NDA request or authenticated access-control test. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: Unknown. Reviewed North security/encryption/compliance and private-deployment data flows, Trust Center and Enterprise Data Commitments, plus targeted first-party professional-secrecy searches. DPA is request/NDA-gated. No public North §203 StGB or Art.321 StGB undertaking or profession-specific add-on was retrieved; none requested. A DPA or no-training clause alone does not answer whether a profession-specific undertaking is signed. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: Unknown. No retrieved §203/Art.321 undertaking establishes flow-down to all relevant subcontractors/model providers. General DPA confidentiality is not equivalent. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: Unknown. No documented profession-specific plan, dedicated instance option or paid secrecy add-on and its entitlements/pricing were established. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: Private-deployment commitments say Cohere does not receive customer prompts/outputs; the local North app decrypts configured chat columns for use and authorised investigators can export conversations. Optional Model Vault processes inference despite ZDR, and external model endpoints follow their contracts. No complete staff/subprocessor plaintext matrix or secrecy undertaking was inspected. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-154, cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-trust. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Unknown. Reviewed North security/encryption/compliance and private-deployment data flows, Trust Center and Enterprise Data Commitments, plus targeted first-party professional-secrecy searches. DPA is request/NDA-gated. No public North §203 StGB or Art.321 StGB undertaking or profession-specific add-on was retrieved; none requested. General data-flow/security pages are available but do not document such a secrecy offering. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-154, cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-trust ## 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The current public offer page advertises Cloud Basic at $50/month and Pro at $99/month. These are advertised card prices; legacy tier identities, capacities and checkout entitlements are not mapped here. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public offer cards and Desktop Pro documentation retrieved 2026-10-21; no inference of renamed checkout/legacy tier equivalence; plan=MIT self-hosted/core Desktop; advertised Cloud Basic/Pro cards and quote-only Enterprise; optional Desktop Pro is a separate offer; add_ons=none stated; deployment_mode=not specified; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - This claim quotes advertised offer-card prices only; it does not assert that Basic/Pro and Starter/Professional are equivalent SKUs. - Legacy-tier capacity limits are excluded. Current-card capacity, model-credit allowances, ISO currency and Desktop Pro numeric pricing remain unverified. - pricing_unit — What is the pricing unit? [supported]: Self-hosted software has no per-seat MIT licence fee. The current Cloud cards quote a private instance per month; optional Desktop Pro is a separate licence. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cloud-cards-r2, anythingllm:anythingllm:pro. - list_prices — What are list prices per plan, with date and currency? [partial]: As retrieved 2026-10-21, the public Cloud cards advertise Basic $50/month and Pro $99/month; Enterprise requires a quote. The page does not give an ISO currency code. These prices are not mapped to Starter/Professional checkout identifiers; Desktop Pro pricing remains unverified. Sources: anythingllm:anythingllm:cloud-cards-r2, anythingllm:anythingllm:pro-key. - included_usage — What usage is included? [partial]: The Basic card explicitly requires a customer LLM API key. Included model credits, overage tariffs and quantified capacity/entitlements for the current Basic/Pro cards were not established. Legacy limitations-page tier names are not used to infer them. Sources: anythingllm:anythingllm:cloud-cards-r2. - add_ons — Which features cost extra? [partial]: Optional Desktop Pro removes Magic-feature daily limits and document watermarks. Its price and custom Enterprise integration/support prices remain unverified; Cloud Pro is a separate product offer. Sources: anythingllm:anythingllm:pro, anythingllm:anythingllm:cloud-cards-r2. - overage — What do usage beyond limits and premium models cost? [partial]: Customer-selected model/tool accounts incur their own provider charges. No current-card included allowance or AnythingLLM token-overage tariff was verified. Sources: anythingllm:anythingllm:models, anythingllm:anythingllm:cloud-cards-r2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cloud-cards-r2, anythingllm:anythingllm:pro, anythingllm:anythingllm:pro-key, anythingllm:anythingllm:models #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North uses capacity and installation licensing with custom prices. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: overage. - pricing_unit — What is the pricing unit? [supported]: Compute Units cover model GPU capacity via hardware/model factors; Application Instances count separate administered North installations. Not documented as a universal per-seat tariff. Sources: cohere-north:cohere-north:n-doc-158. - list_prices — What are list prices per plan, with date and currency? [partial]: North pricing page says custom enterprise pricing; numeric North licence rates not published in retrieved sources. Separate Model Vault/API rates are not North total. Sources: cohere-north:cohere-north:n-pricing. - included_usage — What usage is included? [partial]: Licensed capacity depends on GPUs/model factors, application instances and contract; no public included-message allowance retrieved. Sources: cohere-north:cohere-north:n-doc-158. - add_ons — Which features cost extra? [partial]: Model Vault inference, external provider/search API contracts, extra parser/guardrail GPUs and deployment services may add cost; exact included entitlements/rates unknown. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-193, cohere-north:cohere-north:n-doc-14. - overage — What do usage beyond limits and premium models cost? [unknown]: Unknown for overage. Compute units/application instances and custom pricing are documented. North rates, included usage, minimums and extras were not quoted or invented. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-193, cohere-north:cohere-north:n-doc-14 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial ALM-14 shared cost assumptions v1.4, 2026-10-21: zero standard licence plus a disclosed Swiss infrastructure/operations and direct-BYO-model budget. Annual CHF/EUR figures are floors plus named unknown costs. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=Analyst-selected direct OpenAI API proxy, not a bundled model, Assumed operations staffing; optional commercial services excluded; deployment_mode=customer-cloud; region=Azure Switzerland North for the reference application infrastructure; standard OpenAI API inference has no Swiss/EU residency assumption; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21 are analyst inputs, not vendor sizing or an uptime promise. - The budget is a floor because named infrastructure and service costs are unpriced. - cost_200 — Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 200 users, 12 months excluding VAT: from CHF 34778.28 / EUR 37651.06 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 4749.26, operations CHF 30000.00, and BYO model usage USD 475.20. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cost-vm, anythingllm:anythingllm:cost-pg, anythingllm:anythingllm:cost-fx, anythingllm:anythingllm:cost-model, anythingllm:anythingllm:cost-effort. - cost_1000 — Year-one cost at 1,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 1,000 users, 12 months excluding VAT: from CHF 88600.40 / EUR 95919.02 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 12605.23, operations CHF 75000.00, and BYO model usage USD 2376.00. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cost-vm, anythingllm:anythingllm:cost-pg, anythingllm:anythingllm:cost-fx, anythingllm:anythingllm:cost-model, anythingllm:anythingllm:cost-effort. - cost_5000 — Year-one cost at 5,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 5,000 users, 12 months excluding VAT: from CHF 189541.24 / EUR 205197.83 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 32214.49, operations CHF 150000.00, and BYO model usage USD 11880.00. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cost-vm, anythingllm:anythingllm:cost-pg, anythingllm:anythingllm:cost-fx, anythingllm:anythingllm:cost-model, anythingllm:anythingllm:cost-effort. - variable_share — Which part depends on usage? [partial]: Shared mix is 60% light at 100, 30% regular at 400 and 10% power at 1,500 messages/user/month, or 330 weighted messages. Each message is 3,000 input and 600 output tokens. Direct BYO proxy is gpt-6-luna, reasoning effort none, Standard short-context uncached rates USD 0.10/0.50 per million input/output tokens. It costs USD 2.376/user/year before optional tools, embedding, caching or regional processing. This proxy is an analyst assumption, not the product default. Sources: anythingllm:anythingllm:cost-model, anythingllm:anythingllm:cost-effort. - unknown_parts — Which costs could not be priced? [partial]: Unpriced additions are file/object storage beyond the assumed 500 GB PostgreSQL storage, VM OS/data disks, backup excess, egress/load balancers, Redis or additional database services, high availability, embeddings, OCR, search, audio/images, integration work and optional commercial services. The shared PostgreSQL reference budget is not AnythingLLM’s default storage architecture; application/vector storage, extra services and capacity validation remain unpriced. Paid Desktop Pro, managed Cloud and Enterprise are excluded from this self-hosted scenario. The shared VM/PG sizes have not been load-tested and do not replace each product’s documented runtime dependencies. Sources: anythingllm:anythingllm:cost-vm, anythingllm:anythingllm:cost-pg, anythingllm:anythingllm:license. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cost-vm, anythingllm:anythingllm:cost-pg, anythingllm:anythingllm:cost-fx, anythingllm:anythingllm:cost-model, anythingllm:anythingllm:cost-effort #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared-scenario North totals remain unknown because the commercial rates and capacity sizing are not public. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The partial atomic answers state their documentation or verification limits. - cost_200 — Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21: twelve months, excl VAT, no discounts, 330 messages/user/month. At 200 users, North licence/capacity, infrastructure, implementation and support are unknown in EUR/CHF. No total or nonzero floor can be calculated without North tariff and sizing. Separate Model Vault/API prices are not substitutes. FX basis: ECB 2026-10-20 EUR1=USD1.1215=CHF0.9237. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:fx-ecb. - cost_1000 — Year-one cost at 1,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21: twelve months, excl VAT, no discounts, 330 messages/user/month. At 1,000 users, North licence/capacity, infrastructure, implementation and support are unknown in EUR/CHF. No total or nonzero floor can be calculated without North tariff and sizing. Separate Model Vault/API prices are not substitutes. FX basis: ECB 2026-10-20 EUR1=USD1.1215=CHF0.9237. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:fx-ecb. - cost_5000 — Year-one cost at 5,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21: twelve months, excl VAT, no discounts, 330 messages/user/month. At 5,000 users, North licence/capacity, infrastructure, implementation and support are unknown in EUR/CHF. No total or nonzero floor can be calculated without North tariff and sizing. Separate Model Vault/API prices are not substitutes. FX basis: ECB 2026-10-20 EUR1=USD1.1215=CHF0.9237. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:fx-ecb. - variable_share — Which part depends on usage? [partial]: Capacity, replicas and external model/search usage vary;330 messages/user does not determine GPUs, parallelism or tool calls. Vendor-recommended model cannot price unknown North commercial terms; variable currency share remains unknown. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-pricing. - unknown_parts — Which costs could not be priced? [partial]: North licence per CU/instance, minimum capacity, model translation factors for chosen current models, HA/GPU sizing, external usage, storage/network, support, rollout and taxes outside excl VAT basis. No quote/contact requested. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:fx-ecb ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Self-installation and free Desktop permit evaluation without sales; managed Cloud offers paid self-serve instance checkout. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - self_serve_trial: Free self-install has no software trial clock/card requirement. Cloud has paid self-serve signup links, but a free business Cloud trial and its card/duration terms were not established. - trial_scope: Docker self-install includes standard multi-user administration and workspace knowledge; Enterprise SSO/custom service scope is quote-only and Cloud excludes MCP/custom Agents. - sales_gate: Standard self-install and paid public Cloud tiers have self-serve paths. Custom Enterprise services require a quote; no vendor was contacted. - free_tier — Is there a free tier for business use? [supported]: MIT self-hosting and the core Desktop download are free; Magic features have a free allowance with optional Desktop Pro. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:desktop, anythingllm:anythingllm:pro. - self_serve_trial — Is a self-serve business trial available? [partial]: Free self-install has no software trial clock/card requirement. Cloud has paid self-serve signup links, but a free business Cloud trial and its card/duration terms were not established. Sources: anythingllm:anythingllm:localdocker, anythingllm:anythingllm:cloud. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Docker self-install includes standard multi-user administration and workspace knowledge; Enterprise SSO/custom service scope is quote-only and Cloud excludes MCP/custom Agents. Sources: anythingllm:anythingllm:security, anythingllm:anythingllm:cloud, anythingllm:anythingllm:cloud-limits. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Standard self-install and paid public Cloud tiers have self-serve paths. Custom Enterprise services require a quote; no vendor was contacted. Sources: anythingllm:anythingllm:cloud, anythingllm:anythingllm:localdocker. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:desktop, anythingllm:anythingllm:pro, anythingllm:anythingllm:localdocker, anythingllm:anythingllm:cloud, anythingllm:anythingllm:security, anythingllm:anythingllm:cloud-limits #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public demo and model API trial do not verify a full North tenant trial. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - The partial atomic answers state their documentation or verification limits. - free_tier — Is there a free tier for business use? [partial]: Pricing page distinguishes free rate-limited model API trial from paid production; trial key prohibited for commercial/production use. A free North business tier not established. Sources: cohere-north:cohere-north:n-pricing. - self_serve_trial — Is a self-serve business trial available? [partial]: North links instant demo/custom pricing; no self-serve North tenant with SSO/admin/connectors was provisioned or established. Sources: cohere-north:cohere-north:n-home, cohere-north:cohere-north:n-pricing. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Free model API trial does not establish North SSO, connectors or administration. Full North evaluation scope unknown. Sources: cohere-north:cohere-north:n-pricing. - sales_gate — Does meaningful evaluation require sales contact? [partial]: North custom pricing and private rollout route through sales; whether an independent full tenant evaluation can start without contact remains unknown. No contact made. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-private. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-home, cohere-north:cohere-north:n-private ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The self-hosted MIT grant has no seat commitment; Cloud publishes monthly prices and cancellation terms, with immediate deletion. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Desktop, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - minimum_commitment: The MIT grant has no user-count minimum; Cloud per-instance pricing lists no numeric seat floor. Enterprise minima were not established. - local_invoicing: Can it be invoiced in CHF or EUR from a European entity? CHF/EUR billing from a European contracting entity and Enterprise-specific renewal/price-change terms were not established. - transparency_class: Self-host licensing and Cloud Basic/Pro headlines are disclosed. Enterprise service scope, Desktop Pro tariff and full all-in provider spend are only partially specified or unknown. - minimum_commitment — What seat or spend minimum applies? [partial]: The MIT grant has no user-count minimum; Cloud per-instance pricing lists no numeric seat floor. Enterprise minima were not established. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cloud. - contract_length — What contract lengths are offered? [supported]: Cloud Basic/Pro are listed monthly; MIT software use has no subscription term. Sources: anythingllm:anythingllm:cloud, anythingllm:anythingllm:license. - cancellation — How can the contract be cancelled or reduced? [supported]: Cloud can be cancelled via the dashboard or email under the generic terms, with immediate non-recoverable deletion and a stated prorated-current-cycle refund provision. Self-hosted service contracts are separate. Sources: anythingllm:anythingllm:terms-cloud, anythingllm:anythingllm:privacy-cloud. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [unknown]: local_invoicing: Can it be invoiced in CHF or EUR from a European entity? CHF/EUR billing from a European contracting entity and Enterprise-specific renewal/price-change terms were not established. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: Self-host licensing and Cloud Basic/Pro headlines are disclosed. Enterprise service scope, Desktop Pro tariff and full all-in provider spend are only partially specified or unknown. Sources: anythingllm:anythingllm:cloud, anythingllm:anythingllm:pro-key, anythingllm:anythingllm:license. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:cloud, anythingllm:anythingllm:terms-cloud, anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:pro-key #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North contract minimums, term and local billing are unverified; pricing is quote-only. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: contract_length, cancellation, local_invoicing. - minimum_commitment — What seat or spend minimum applies? [partial]: Each separately administered installation counts as an Application Instance; compute-unit licence metric exists, but numeric minimum/spend not retrieved. Sources: cohere-north:cohere-north:n-doc-158. - contract_length — What contract lengths are offered? [unknown]: Unknown for contract_length. North custom enterprise contract was not public in retrieved sources; minimums, term, reduction and invoice currencies remain unknown. - cancellation — How can the contract be cancelled or reduced? [unknown]: Unknown for cancellation. North custom enterprise contract was not public in retrieved sources; minimums, term, reduction and invoice currencies remain unknown. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [unknown]: Unknown for local_invoicing. North custom enterprise contract was not public in retrieved sources; minimums, term, reduction and invoice currencies remain unknown. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [supported]: Quote-only for North licence/deployment. Separate Model Vault instance rates and model API tariffs do not make North pricing transparent. Sources: cohere-north:cohere-north:n-pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-pricing ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial The pinned main repository is MIT. Paid hosted/Desktop entitlements must be distinguished from that source licence. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - enterprise_features_closed: Cloud Enterprise and Desktop Pro add commercial services/entitlements. Whether particular enterprise-only implementations are closed or separately licensed was not established from the main MIT file. - licence_type — Which licence applies to each component? [supported]: The pinned main client/server repository at v1.18.0 uses MIT. Mobile, browser extension and optional paid-service components require their own component licence review. Sources: anythingllm:anythingllm:license. - branding_restrictions — Do licence terms restrict branding or user counts? [supported]: MIT requires notice preservation but has no UI-branding or user-count clause. Optional Desktop Pro removes watermarks from generated documents; that is a paid feature entitlement, not a restriction in the main MIT source licence. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:pro. - enterprise_features_closed — Are enterprise features in a separate closed edition? [partial]: Cloud Enterprise and Desktop Pro add commercial services/entitlements. Whether particular enterprise-only implementations are closed or separately licensed was not established from the main MIT file. Sources: anythingllm:anythingllm:cloud, anythingllm:anythingllm:pro, anythingllm:anythingllm:license. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:license, anythingllm:anythingllm:pro, anythingllm:anythingllm:cloud #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial North is commercially licensed; component source rights and branding terms need contract review. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: enterprise_features_closed. - licence_type — Which licence applies to each component? [partial]: Commercial CU/Application Instance licence documented; full North application/model/component licence texts not retrieved. Sources: cohere-north:cohere-north:n-doc-158. - branding_restrictions — Do licence terms restrict branding or user counts? [partial]: White-label settings configure product branding; entitlement, use restrictions and licence fee terms unverified. Separate installations count for licensing, with no public per-user cap retrieved. Sources: cohere-north:cohere-north:n-doc-142, cohere-north:cohere-north:n-doc-158. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Unknown for enterprise_features_closed. North is commercially licensed by capacity/installations. Full application/model component licences and branding rights were not publicly retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-doc-142 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Authorized accounts can export chat logs; a complete assistant/knowledge exit fixture was not run. Cloud cancellation leaves no recovery window. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Cloud managed instance; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - assistant_export: Can assistants and prompts be exported in a reusable format? No reusable complete assistant/prompt export, knowledge/source fidelity export or admin leaver/exit fixture was verified. Export Cloud data before cancellation under its current terms. - knowledge_export: Can knowledge bases and their sources be exported? No reusable complete assistant/prompt export, knowledge/source fidelity export or admin leaver/exit fixture was verified. Export Cloud data before cancellation under its current terms. - chat_export — Can admins export all chats? [supported]: Permissioned exports cover workspace/user chat logs in CSV, JSON, Alpaca JSON or OpenAI-style JSONL once at least ten logs exist. No all-organization export fixture was run. Sources: anythingllm:anythingllm:logs. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: assistant_export: Can assistants and prompts be exported in a reusable format? No reusable complete assistant/prompt export, knowledge/source fidelity export or admin leaver/exit fixture was verified. Export Cloud data before cancellation under its current terms. - knowledge_export — Can knowledge bases and their sources be exported? [unknown]: knowledge_export: Can knowledge bases and their sources be exported? No reusable complete assistant/prompt export, knowledge/source fidelity export or admin leaver/exit fixture was verified. Export Cloud data before cancellation under its current terms. - export_format — Are formats documented and machine-readable? [supported]: Documented chat-log formats are machine-readable. This does not establish complete source-file, assistant or index portability. Sources: anythingllm:anythingllm:logs. - post_termination_window — How long can data be retrieved after termination? [supported]: Managed Cloud policy states permanent unrecoverable data deletion at cancellation/nonpayment/termination, so no post-termination retrieval window is promised. Self-hosted data remains under operator control. Sources: anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:terms-cloud. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:logs, anythingllm:anythingllm:privacy-cloud, anythingllm:anythingllm:terms-cloud #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial APIs and approved exports provide some portability; full tenant exit is unverified. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: post_termination_window. - chat_export — Can admins export all chats? [partial]: Alpha compliance approves targeted user/agent conversations for24 hours and downloadsCSV. API lists/retrieves conversations; a single complete admin export and preservation hold not established. Sources: cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-north-api. - assistant_export — Can assistants and prompts be exported in a reusable format? [partial]: Automation definitions export reusableJSON graph/dependencies but omit credentials and schedules. Agent configurations have API access/version history; full portable agent export not established. Sources: cohere-north:cohere-north:n-doc-29, cohere-north:cohere-north:n-north-api. - knowledge_export — Can knowledge bases and their sources be exported? [partial]: File API retrieves content and library metadata APIs exist; complete all-index/source bulk export and permission preservation not established. Sources: cohere-north:cohere-north:n-api-upload, cohere-north:cohere-north:n-api-libraries. - export_format — Are formats documented and machine-readable? [partial]: AutomationJSON, complianceCSV, original file API content and documentPDF/DOCX/HTML/TXT/MD are documented. These do not constitute complete tenant-state export. Sources: cohere-north:cohere-north:n-doc-29, cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-doc-9. - post_termination_window — How long can data be retrieved after termination? [unknown]: Unknown for post_termination_window. Automation JSON, API files and approved compliance CSV are documented. Complete bulk tenant export, agent portability and post-exit recovery window remain unverified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-north-api, cohere-north:cohere-north:n-doc-29, cohere-north:cohere-north:n-api-upload, cohere-north:cohere-north:n-api-libraries, cohere-north:cohere-north:n-doc-9 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public community/team support routes and the generic managed Cloud no-offline-credit terms are documented. No bespoke Enterprise SLA or Pro response-time entitlement is established by this claim. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, AnythingLLM Cloud managed instance; version=Public support guide and generic Cloud terms (last updated 2024-07-01) retrieved 2026-10-21; plan=Self-hosted community/team support and managed Cloud under the published generic terms only; separately negotiated Enterprise SLAs and advertised Pro response terms are outside verified contractual scope; add_ons=none stated; deployment_mode=not specified; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - Generic Cloud contract facts are not extended to a bespoke Enterprise agreement. - Advertised support timing is excluded from contractual uptime/compensation findings. - Support languages, hours, regional staffing and a status history remain unverified. - support_channels — Which support channels are available on each plan? [supported]: The public guide lists GitHub issues, team email and community Discord, recommending GitHub/email for direct team assistance. These channels do not establish contracted response hours. Sources: anythingllm:anythingllm:support-r2. - support_languages — Is support available in German, French or Italian? [unknown]: Contracted German, French or Italian support coverage, service hours and time zones were not established in the scoped guide and generic terms. - regional_presence — Is there a DACH or Swiss entity, team or partner? [unknown]: A CH/DACH support entity, staffed local presence or named support partner was not verified from these sources. - uptime_sla — Is there an uptime SLA with credits? [partial]: The generic managed Cloud terms deny refunds/credits for an offline instance and do not establish an uptime percentage/credit schedule. This is a finding about those generic terms only; no executed Enterprise override or contractual definition of advertised Pro support timing was reviewed. Sources: anythingllm:anythingllm:cloud-terms-r2. - status_page — Is there a public status page with history? [unknown]: A first-party public service-status page with incident history was not verified in the support/contract sources. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:support-r2, anythingllm:anythingllm:cloud-terms-r2 #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Support resources exist; North SLA, regional entity and support languages remain unknown. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: support_languages, uptime_sla. - support_channels — Which support channels are available on each plan? [partial]: Private deployments include access to solution architects, applied ML and customer success; public security/support resources exist. Contracted response times unknown. Sources: cohere-north:cohere-north:n-private. - support_languages — Is support available in German, French or Italian? [unknown]: Unknown for support_languages. Public support/status resources and deployment assistance exist; response languages, North SLA credits and contracted DACH entity were not established. - regional_presence — Is there a DACH or Swiss entity, team or partner? [partial]: September 16 agreement plans Berlin/Toronto headquarters and Heidelberg research subject to close. A North-contract Swiss/DACH delivery entity or completed combination was not verified. Sources: cohere-north:cohere-north:n-combination. - uptime_sla — Is there an uptime SLA with credits? [unknown]: Unknown for uptime_sla. Public support/status resources and deployment assistance exist; response languages, North SLA credits and contracted DACH entity were not established. - status_page — Is there a public status page with history? [partial]: Cohere has a public hosted API status page. Customer-hosted North availability is operator-managed; a North-wide hosted status/SLA not established. Sources: cohere-north:cohere-north:n-status, cohere-north:cohere-north:n-doc-165. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-combination, cohere-north:cohere-north:n-status, cohere-north:cohere-north:n-doc-165 ### 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. #### AnythingLLM Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public setup/skill tutorials are available and Enterprise advertises custom services; a priced workforce adoption package was not verified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v1.18.0 / 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba; plan=MIT self-hosted Docker multi-user unless explicitly identified as single-user, Desktop, Mobile or Cloud; add_ons=none stated; deployment_mode=on-premise; region=Self-hosted location selected by customer; managed Cloud AWS country and external provider processing require separate confirmation; os=not specified. Limitations: - onboarding_service: Is guided onboarding included? No included guided rollout, DE/FR/IT end-user training, champion programme or change-management package was verified. - user_training: Is end-user training offered, in which languages? No included guided rollout, DE/FR/IT end-user training, champion programme or change-management package was verified. - use_case_library: Public Agent Flow, SQL, mail, document-generation and meeting guides provide use-case examples. A formal role-based workforce curriculum was not established. - adoption_programme: Is there a champion or adoption programme? No included guided rollout, DE/FR/IT end-user training, champion programme or change-management package was verified. - service_cost: Enterprise premium service/custom integrations/on-premise support are quote-only. Included rollout/training deliverables and prices were not established. - onboarding_service — Is guided onboarding included? [unknown]: onboarding_service: Is guided onboarding included? No included guided rollout, DE/FR/IT end-user training, champion programme or change-management package was verified. - user_training — Is end-user training offered, in which languages? [unknown]: user_training: Is end-user training offered, in which languages? No included guided rollout, DE/FR/IT end-user training, champion programme or change-management package was verified. - use_case_library — Are role-based use cases and templates provided? [partial]: Public Agent Flow, SQL, mail, document-generation and meeting guides provide use-case examples. A formal role-based workforce curriculum was not established. Sources: anythingllm:anythingllm:flow, anythingllm:anythingllm:docgen, anythingllm:anythingllm:meeting, anythingllm:anythingllm:sql. - adoption_programme — Is there a champion or adoption programme? [unknown]: adoption_programme: Is there a champion or adoption programme? No included guided rollout, DE/FR/IT end-user training, champion programme or change-management package was verified. - service_cost — Which services cost extra? [partial]: Enterprise premium service/custom integrations/on-premise support are quote-only. Included rollout/training deliverables and prices were not established. Sources: anythingllm:anythingllm:cloud. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: anythingllm:anythingllm:flow, anythingllm:anythingllm:docgen, anythingllm:anythingllm:meeting, anythingllm:anythingllm:sql, anythingllm:anythingllm:cloud #### Cohere North Verification status: Agent cross-checked (agent-cross-checked) Support: partial Deployment assistance and public user/builder guides are offered; included service scope is unknown. Availability: unknown Delivery: native Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified. Limitations: - Remaining atomic gaps: adoption_programme, service_cost. - onboarding_service — Is guided onboarding included? [partial]: Vendor describes rollout support from architects, applied ML and customer success. Included hours/fees are not published. Sources: cohere-north:cohere-north:n-private. - user_training — Is end-user training offered, in which languages? [partial]: Public user/agent/workflow guides support self-learning. Live end-user training and language entitlement not established. Sources: cohere-north:cohere-north:n-guide, cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-16. - use_case_library — Are role-based use cases and templates provided? [supported]: Agent guide gives ticket deflection/sales/legal examples and internal agent catalogue permits sharing; document/Skills guides include task examples. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-21, cohere-north:cohere-north:n-doc-12. - adoption_programme — Is there a champion or adoption programme? [unknown]: Unknown for adoption_programme. Vendor offers rollout assistance and guides; service language, included hours, adoption programme and costs were not retrieved. - service_cost — Which services cost extra? [unknown]: Unknown for service_cost. Vendor offers rollout assistance and guides; service language, included hours, adoption programme and costs were not retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-guide, cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-21, cohere-north:cohere-north:n-doc-12 ## Sources ### anythingllm:anythingllm:models Language models. The product documents multiple cloud and local provider integrations, with selected models supplied by the connected account/server. - URL: https://docs.anythingllm.com/features/language-models - Locator: Supported local/cloud providers - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:llmconfig LLM configuration. System defaults can be overridden per workspace and separately for agent use. - URL: https://docs.anythingllm.com/setup/llm-configuration/overview - Locator: System, Workspace and Agent LLMs - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:built-in Built-in local model engine. Desktop is moving its built-in engine from Ollama to Lemonade/llama.cpp; current Docker documentation describes opt-in local inference on images after v1.18.0. - URL: https://docs.anythingllm.com/setup/llm-configuration/local/built-in - Locator: Lemonade/llama.cpp; Desktop migration; Docker opt-in - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:router Model Router. Self-hosted and Desktop installations can route messages by ordered calculated or model-classified rules, with a fallback provider/model. - URL: https://docs.anythingllm.com/model-router/overview - Locator: Availability; rule types; fallback - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:constants-pin AnythingLLM file converter registration. The pinned collector registers PDF, DOCX, PPTX, XLSX, EPUB, text, image and audio converters; legacy DOC is commented out. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/collector/utils/constants.js - Locator: collector/utils/constants.js, accepted MIME and converter maps - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: collector/utils/constants.js ### cohere-north:cohere-north:n-doc-177-20261026 Headless model providers. Operators register Cohere, vLLM, Azure, Bedrock, SageMaker, OpenAI and Anthropic endpoints with customer secrets. - URL: https://private.docs.cohere.com/north/docs/advanced/headless-configuration/model-providers?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-32-20261026 North Large 01-2026. North partnership model accepts text/images with256K input/32K output and48 languages; citation gaps acknowledged. - URL: https://private.docs.cohere.com/north/docs/north-large-01-2026?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-134-20261026 Models and providers. Custom endpoints/providers, group access and defaults; grants additive and alias may silently fall back to provider default. - URL: https://private.docs.cohere.com/north/docs/admin/models?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-1-20261026 Chat. Chat model choice, source-linked responses, eight UI languages and configurable voice/image input are documented. - URL: https://private.docs.cohere.com/north/docs/get-started/north-chat?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-14-20261026 North multimodal features. Vision/OCR requires configured models/parser; third-party image input planned, document visual pages limited500. - URL: https://private.docs.cohere.com/north/docs/get-started/north-automations/building-automations/north-multimodality?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-97-20261026 Voice settings. Dictation and long-form mobile recording are separately off by default and require configured transcription service. - URL: https://private.docs.cohere.com/north/docs/admin/configuring_voice_settings?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-12-20261026 Skills. Built-in/custom skills create/edit DOCX/PPTX/XLSX/CSV using code sandbox and supported models. - URL: https://private.docs.cohere.com/north/docs/get-started/skills?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:north-release-html-20261026 North release notes, public HTML. 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. - URL: https://private.docs.cohere.com/north/changelog - Locator: 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 - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-26 ### anythingllm:anythingllm:generic Generic OpenAI configuration. Operators can configure an OpenAI-compatible provider, with endpoint-specific behavior and configuration caveats. - URL: https://docs.anythingllm.com/setup/llm-configuration/cloud/openai-generic - Locator: Compatible API route - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:changelog Desktop v1.18.0 changelog. Desktop v1.18.0 changes the built-in engine from Ollama to Lemonade/llama.cpp and records format/sync fixes. - URL: https://docs.anythingllm.com/changelog/v1.18.0 - Locator: Lemond/Lemonade migration; reasoning controls; fixes - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:releases AnythingLLM v1.18.0 release. The latest retrieved stable GitHub release is v1.18.0, published 2026-10-13. - URL: https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.18.0 - Locator: Release date and change list - Evidence kind: documented - Source date: 2026-10-13 - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-north-changelog North release notes. Dated releases document new models, beta/alpha capabilities and removal/deprecation of legacy connectors and APIs. - URL: https://private.docs.cohere.com/north/changelog.md - Locator: October 20 v2.0.1 andOctober 16 v2.0.0; migrations - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-168 Deploy models chart. Customer GPU model chart supports local chat/embed/rerank; serving containers version independently. - URL: https://private.docs.cohere.com/north/docs/install/models.md - Locator: In-cluster generative/Compass components and pinned artifacts - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:azure Azure OpenAI configuration. The Azure route uses the customer Azure subscription and its model access. - URL: https://docs.anythingllm.com/setup/llm-configuration/cloud/azure-openai - Locator: Customer Azure subscription - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:bedrock AWS Bedrock configuration. Bedrock is a separately configured customer cloud-account route. - URL: https://docs.anythingllm.com/setup/llm-configuration/cloud/aws-bedrock - Locator: Credentials and provider settings - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:vertex Google Vertex AI configuration. Vertex uses customer Google Cloud credentials and deployment configuration. - URL: https://docs.anythingllm.com/setup/llm-configuration/cloud/google-vertex - Locator: Service account, project and region - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cloud AnythingLLM Cloud pricing. Current public pricing lists private Cloud Basic at $50/month, Pro at $99/month and quote-only Enterprise with SSO/custom services. - URL: https://anythingllm.com/cloud - Locator: Basic, Pro and Enterprise offer table - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cloud-limits Cloud limitations. Managed Cloud explicitly excludes built-in inference, custom coded Agents and MCP; local/self-hosted capabilities cannot be assumed there. - URL: https://docs.anythingllm.com/cloud/limitations - Locator: No built-in LLM; no custom Agents; no MCP - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:license AnythingLLM v1.18.0 licence. The pinned main repository is MIT licensed with copyright/permission notice preservation and an as-is disclaimer. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/LICENSE - Locator: LICENSE, MIT grant and notice - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-135-20261026 Bedrock Anthropic setup. Own AWS account/region and authorized Claude models support chat, agents and automations. - URL: https://private.docs.cohere.com/north/docs/admin/bedrock-anthropic?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-218-20261026 Microsoft Foundry with North. Customer Azure billing supports chat/embed/rerank/Parse5; sparse and North Large unavailable there, mixed hosting required. - URL: https://private.docs.cohere.com/north/docs/microsoft-foundry-with-north.md - Locator: Customer Azure inference and feature gaps; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 e717dddf6149bafdb68a613b1268d366565e212be0e292d989d1c2a8d960f35e on 2026-10-26 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### anythingllm:anythingllm:ollama Ollama configuration. A separately installed Ollama endpoint can provide customer-operated chat inference. - URL: https://docs.anythingllm.com/setup/llm-configuration/local/ollama - Locator: Local provider setup - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:local-embed Built-in embedding provider. The built-in all-MiniLM-L6-v2 embedder runs on CPU and is primarily trained on English; it must first be downloaded. - URL: https://docs.anythingllm.com/setup/embedder-configuration/local/built-in - Locator: CPU model and download - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:embed Embedding models. Retrieval embedding providers are configured separately from chat inference. - URL: https://docs.anythingllm.com/features/embedding-models - Locator: Local and cloud embedding options - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-177 Headless model providers. Operators register Cohere, vLLM, Azure, Bedrock, SageMaker, OpenAI and Anthropic endpoints with customer secrets. - URL: https://private.docs.cohere.com/north/docs/advanced/headless-configuration/model-providers.md - Locator: Provider types, endpoint and credentials - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-14 North multimodal features. Vision/OCR requires configured models/parser; third-party image input planned, document visual pages limited500. - URL: https://private.docs.cohere.com/north/docs/get-started/north-automations/building-automations/north-multimodality.md - Locator: Cohere-only image input and visual parser - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-218 Microsoft Foundry with North. Customer Azure billing supports chat/embed/rerank/Parse5; sparse and North Large unavailable there, mixed hosting required. - URL: https://private.docs.cohere.com/north/docs/microsoft-foundry-with-north.md - Locator: Customer Azure inference and feature gaps - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-126 MCP server administration. Customer/remote MCP support scoped OAuth/tokens/static headers; remote registration needs internet and dynamic registration. - URL: https://private.docs.cohere.com/north/docs/admin/tools-mcp-servers.md - Locator: Registration, custom headers, permissions and remote limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:user-pin AnythingLLM user quota implementation. The pinned user quota counts chats over the preceding 24 hours for non-admin multi-user accounts; null limits and admins are exempt. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/server/models/user.js - Locator: server/models/user.js, canSendChat and dailyMessageLimit validation - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: server/models/user.js ### anythingllm:anythingllm:chat-pin AnythingLLM chat quota enforcement. The pinned chat endpoints abort before generation when a multi-user account reaches its configured 24-hour quota. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/server/endpoints/chat.js - Locator: server/endpoints/chat.js, multiUserMode and canSendChat checks - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: server/endpoints/chat.js ### cohere-north:cohere-north:n-doc-18-20261026 Creating custom agents. Agents combine instructions/models/tools/libraries; shared agents inherit owner model access. - URL: https://private.docs.cohere.com/north/docs/get-started/agents/creating-custom-agents?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-137-20261026 Flow control. User/group/model/source/provider rules enforce request/input/output token limits only after Helm services deployed; fail-open option and unlimited default. - URL: https://private.docs.cohere.com/north/docs/admin/flow-control?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### anythingllm:anythingllm:docchat Documents in chat, current interface. Attachments inject full text while embedded documents are retrieved as chunks and become available to every authorized workspace user. - URL: https://docs.anythingllm.com/chatting-with-documents/introduction - Locator: v1.8.5+; attachment vs embedding; context; workspace scope - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:pdf-pin AnythingLLM PDF extraction implementation. The pinned PDF handler attempts OCR when its initial text loader returns no pages, without establishing scan accuracy. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/collector/processSingleFile/convert/asPDF/index.js - Locator: collector/processSingleFile/convert/asPDF/index.js, no-text fallback - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: collector/processSingleFile/convert/asPDF/index.js ### cohere-north:cohere-north:n-doc-73-20261026 Supported files. Documents text/Office/tabular/image/audio formats and configurable processing; My files limit differs from its dedicated guide. - URL: https://private.docs.cohere.com/north/docs/get-started/supported-files?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-66-20261026 My files. Guide states50 MB/file and configured totals; image-only PDFs require parser setup and images are not indexed for general Smart Search. - URL: https://private.docs.cohere.com/north/docs/get-started/tools/my-files/home?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-100-20261026 Multimodality configuration. Image input currently limited to Cohere vision models; smart parser and infrastructure are separately required. - URL: https://private.docs.cohere.com/north/docs/admin/multimodality?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### anythingllm:anythingllm:security Security and access. Docker multi-user roles are Admin, Manager and Default; Default users only chat in explicitly assigned workspaces. - URL: https://docs.anythingllm.com/features/security-and-access - Locator: Docker only; single-user vs multi-user; roles - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-42-20261026 Libraries. Libraries bind to agents/chats/nodes; source libraries and uploads have different sharing/access rules. - URL: https://private.docs.cohere.com/north/docs/get-started/tools/libraries?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-11-20261026 Projects. Private indexed project files are isolated to the project; default per-user aggregate storage2 GiB. - URL: https://private.docs.cohere.com/north/docs/get-started/projects?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-133-20261026 Admin library directory. Admins manage library access without seeing contents; groups and company access supported, email libraries private. - URL: https://private.docs.cohere.com/north/docs/admin/libraries.md - Locator: Beta user/group access; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 f4248f5cd4bf98f610b6f39c57494e2834de07e117db292498eca4707a592b8f on 2026-10-26 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### anythingllm:anythingllm:sync Automatic document sync preview. Preview sync refreshes watched sources; removing a watched Desktop original leaves existing parsed content and embeddings in place. - URL: https://docs.anythingllm.com/beta-preview/active-features/live-document-sync - Locator: Docker vs Desktop scope; intervals; missing local file - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:mcp MCP compatibility. Self-hosted/desktop MCP supports local stdio and remote SSE/Streamable transports with configured credentials/headers. - URL: https://docs.anythingllm.com/mcp-compatibility/overview - Locator: Configuration file; management UI; transport types - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:outlook Outlook Agent. The single-user Outlook skill uses a customer Entra application and requests approval for mailbox-modifying operations. - URL: https://docs.anythingllm.com/agent/usage/outlook-agent - Locator: Single-user only; delegated scopes; approvals - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:gmail Gmail Agent. The Gmail skill is single-user only and distinguishes read actions from modifying actions requiring approval. - URL: https://docs.anythingllm.com/agent/usage/gmail-agent - Locator: Single-user only; setup; action approvals - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:sql SQL Agent. A configurable SQL Agent can query a separately connected database. - URL: https://docs.anythingllm.com/agent/usage/sql-agent - Locator: Database connection and tool use - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:localdocker Local Docker installation. Self-hosting runs the application in customer-controlled infrastructure and mounted storage. - URL: https://docs.anythingllm.com/installation-docker/local-docker - Locator: Volumes; local network; configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:connectors-pin AnythingLLM connector registration. The pinned UI registers Confluence, repository, website, YouTube, Obsidian and other import connectors; no source ACL test was performed. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/frontend/src/components/Modals/ManageWorkspace/DataConnectors/index.jsx - Locator: frontend/src/components/Modals/ManageWorkspace/DataConnectors/index.jsx - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: frontend/src/components/Modals/ManageWorkspace/DataConnectors/index.jsx ### cohere-north:cohere-north:n-doc-151-20261026 Data syncing. Atlas periodic indexing differs from live APIs; generic freshness minutes to hours. - URL: https://private.docs.cohere.com/north/docs/security/data-syncing?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-126-20261026 MCP server administration. Customer/remote MCP support scoped OAuth/tokens/static headers; remote registration needs internet and dynamic registration. - URL: https://private.docs.cohere.com/north/docs/admin/tools-mcp-servers.md - Locator: Registration, custom headers, permissions and remote limits; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 8b401a0257b45f4b284dd89368b795118eb74b1a2b0d193d56a9b1687e804ea9 on 2026-10-26 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-53-20261026 SharePoint Server connector setup. Documents customer-network SharePoint Server integration with deployment/auth prerequisites. - URL: https://private.docs.cohere.com/north/docs/get-started/tools/microsoft-connectors/sharepoint-server-connector-setup?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-152-20261026 Data sharing. Atlas/source permission checks fail closed for retrieval; old email storage descriptions conflict with live Gmail guide. - URL: https://private.docs.cohere.com/north/docs/security/data-sharing?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:north2-launch-20261026 North 2 product launch. 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. - URL: https://cohere.com/blog/introducing-north-2 - Locator: Core feature and connector lists; model and governance sections - Evidence kind: vendor-claimed - Source date: 2026-10-05 - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-64 SharePoint implementation. Selected content is indexed;10-minute sync detects updates/deletes, after source-side indexing permits discovery. - URL: https://private.docs.cohere.com/north/docs/get-started/tools/atlas-sharepoint/atlas-sharepoint-implementation.md - Locator: Compass indexing,10-minute sync and source search dependency - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-42 Libraries. Libraries bind to agents/chats/nodes; source libraries and uploads have different sharing/access rules. - URL: https://private.docs.cohere.com/north/docs/get-started/tools/libraries.md - Locator: Beta persistence, source/sharing and binding - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-151 Data syncing. Atlas periodic indexing differs from live APIs; generic freshness minutes to hours. - URL: https://private.docs.cohere.com/north/docs/security/data-syncing.md - Locator: Atlas copies versus live Gmail/Google Drive Full Access - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-152 Data sharing. Atlas/source permission checks fail closed for retrieval; old email storage descriptions conflict with live Gmail guide. - URL: https://private.docs.cohere.com/north/docs/security/data-sharing.md - Locator: Agent/library scope, runtime checks and private email - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-4 Sharing and collaborating with chat. Shared snapshots expose full messages, citations, thinking trace and sandbox files to signed-in recipients. - URL: https://private.docs.cohere.com/north/docs/get-started/sharing-collaborating-chat.md - Locator: Snapshot contents and debug visibility - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-149 Tool authorization. Per-user access and runtime source checks documented; revocation immediacy not independently measured. - URL: https://private.docs.cohere.com/north/docs/security/tool-authorization.md - Locator: OAuth/source permission checks - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-111 JIT provisioning. First successful login creates users; groups refresh at authentication/session renewal; admin deprovisioning APIs documented. - URL: https://private.docs.cohere.com/north/docs/admin/identity/sso/user-provisioning.md - Locator: First login and refreshed groups - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:vector Vector databases. The application supports configurable local and external vector databases rather than a single fixed vendor region. - URL: https://docs.anythingllm.com/features/vector-databases - Locator: Local and cloud storage choices - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:privacy Privacy and data handling. Telemetry is optional; deleting a document from a workspace differs from deleting it from My Documents and all workspaces. - URL: https://docs.anythingllm.com/features/privacy-and-data-handling - Locator: Telemetry; document removal vs full erasure - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-33 North tools overview. Names first-party sources and states, including Jira/Slack MCP beta, Atlas SharePointGA and Gmail alpha. - URL: https://private.docs.cohere.com/north/docs/get-started/tools-overview.md - Locator: Per-tool state and categories - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-165-20261026 Deployment model. North application Helm chart deployed on customer Kubernetes; GitOps/ArgoCD recommended for production. - URL: https://private.docs.cohere.com/north/docs/deployment-model.md - Locator: Helm and production GitOps; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 39b2586fa7cca8f9c540e2c02dc9471ed0b3c89484c9f776421e78e477711721 on 2026-10-26 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### anythingllm:anythingllm:chatmodes Chat modes. Agent mode uses configured tools; Query mode is documented to report when it finds no relevant document information. - URL: https://docs.anythingllm.com/features/chat-modes - Locator: Agent, Chat and Query modes - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:citation-pin AnythingLLM source citation rendering. The pinned client renders citation sources with file/link/provider metadata and source-detail controls. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/frontend/src/components/WorkspaceChat/ChatContainer/ChatHistory/Citation/index.jsx - Locator: frontend/src/components/WorkspaceChat/ChatContainer/ChatHistory/Citation/index.jsx - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: frontend/src/components/WorkspaceChat/ChatContainer/ChatHistory/Citation/index.jsx ### cohere-north:cohere-north:n-doc-32 North Large 01-2026. North partnership model accepts text/images with256K input/32K output and48 languages; citation gaps acknowledged. - URL: https://private.docs.cohere.com/north/docs/north-large-01-2026.md - Locator: Model card and limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-1 Chat. Chat model choice, source-linked responses, eight UI languages and configurable voice/image input are documented. - URL: https://private.docs.cohere.com/north/docs/get-started/north-chat.md - Locator: Model picker, UI languages, image input and dictation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-11 Projects. Private indexed project files are isolated to the project; default per-user aggregate storage2 GiB. - URL: https://private.docs.cohere.com/north/docs/get-started/projects.md - Locator: Alpha workspace and storage - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:memory Memories and personalization. Admins enable user-scoped workspace/global memory, and users can edit/delete it; selected memories go to the configured model. - URL: https://docs.anythingllm.com/features/memories - Locator: Off by default; user scope; limits; extraction - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:systemprompt System prompt variables. Workspace system prompts can include dynamic user/time context; this does not establish a mandatory organization policy. - URL: https://docs.anythingllm.com/features/system-prompt-variables - Locator: Workspace prompt variables and context - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-18 Creating custom agents. Agents combine instructions/models/tools/libraries; shared agents inherit owner model access. - URL: https://private.docs.cohere.com/north/docs/get-started/agents/creating-custom-agents.md - Locator: Instructions, versioning, sharing and model permission model - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-86 Preamble and prompt settings. Optional organisation instructions apply across models alongside platform/agent preambles. - URL: https://private.docs.cohere.com/north/docs/admin/configuring_preamble_prompt_settings.md - Locator: Company instructions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-8 Memory. Personal memories can be edited or deleted; agent archival memory cannot be viewed or edited. - URL: https://private.docs.cohere.com/north/docs/get-started/memory.md - Locator: Alpha personal/archival memory - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-96 Memory settings. Instance toggles jointly control core/archival/conversation memory and extraction timing. - URL: https://private.docs.cohere.com/north/docs/admin/configuring_memory_settings.md - Locator: Alpha admin controls - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:agent-setup Agent setup. Operators configure Agent models and skills per workspace; the setup guide still names DuckDuckGo as the default search engine. - URL: https://docs.anythingllm.com/agent/setup - Locator: Workspace model; enabled skills; search configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:flow Agent Flows. A visual no-code flow editor creates reusable Agent skills; code skills remain a separate developer route. - URL: https://docs.anythingllm.com/agent-flows/overview - Locator: No-code builder; Desktop vs Docker - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:desktop Desktop installation overview. Desktop supports Windows/macOS/Linux, is single-user and exposes only its API when optional LAN discovery is enabled. - URL: https://docs.anythingllm.com/installation-desktop/overview - Locator: OS support; single-player; network discovery - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-12 Skills. Built-in/custom skills create/edit DOCX/PPTX/XLSX/CSV using code sandbox and supported models. - URL: https://private.docs.cohere.com/north/docs/get-started/skills.md - Locator: Beta skills and Office file packages - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-114 Roles and permissions. Roles/groups delegate permissions; some direct grants cannot be packaged into roles; individual role assignment can expire. - URL: https://private.docs.cohere.com/north/docs/admin/permissions.md - Locator: System/custom roles and grants - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-21 Browsing agents. Internal starred/personal/shared/company agent directory supports search and duplication. - URL: https://private.docs.cohere.com/north/docs/get-started/agents/agent-library.md - Locator: Agent catalogue and duplication - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:flow-api Agent Flow API-call block. A flow block calls a configured API and passes its result into later flow steps. - URL: https://docs.anythingllm.com/agent-flows/blocks/api-call - Locator: HTTP action configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:docgen Document generation skill. The enabled built-in skill generates text, PDF, Excel, DOCX and PowerPoint files, with model-dependent results. - URL: https://docs.anythingllm.com/agent/usage/document-generation-agent - Locator: Availability; document types - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:chart Chart generation skill. An Agent chart skill generates charts from prompts and workspace data. - URL: https://docs.anythingllm.com/agent/usage/chart-generation - Locator: Examples and workspace data - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-34 Code sandbox. Persistent per-chat Python/bash runtime creates files/charts and shows executed code; admin deployment/access required. - URL: https://private.docs.cohere.com/north/docs/get-started/tools/code-sandbox/home.md - Locator: Beta execution, files and activity visibility - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-150 Tool action approvals. Approval modal can edit/deny action parameters, but tool hints and persistent global bypass limit per-action assurance. - URL: https://private.docs.cohere.com/north/docs/security/tool-action-approvals.md - Locator: Destructive actions and global Allow Always - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-30 Consuming automations. Schedules support cron/natural language; run viewer shows inputs/outputs and cancellation; action permission accepted at launch. - URL: https://private.docs.cohere.com/north/docs/get-started/north-automations/consuming-automations.md - Locator: Run, cron schedule, approval and cancel - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:agent-usage Using agents. Agent sessions use configured skills and tool-capable models. - URL: https://docs.anythingllm.com/agent/usage/overview - Locator: Skills and tool use - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:browsing Agent web browsing. The web-browsing skill searches the internet from an Agent request. - URL: https://docs.anythingllm.com/agent/usage/web-browsing - Locator: Built-in search skill - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:search-configured-r2 AnythingLLM v1.18.0 explicitly configured DuckDuckGo route. At the pinned revision, explicit agent_search_provider=duckduckgo-engine routes queries to the DuckDuckGo HTML search endpoint; this finding makes no default-provider claim. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/server/utils/agents/aibitat/plugins/web-browsing.js - Locator: agent_search_provider lookup; duckduckgo-engine switch case at lines 96-98; _duckDuckGoEngine at lines 1117-1210 - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: server/utils/agents/aibitat/plugins/web-browsing.js ### anythingllm:anythingllm:agent-skills-r2 AnythingLLM Agent skill controls. The setup guide documents skill selection in Settings > Agent Skills and tool toggles from the chat prompt menu. - URL: https://docs.anythingllm.com/agent/setup - Locator: Configure your available skills, excluding the unversioned default-search example - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-74 Web search. Tavily defaultGA; Brave/LinkUp alpha; API keys needed; live web page content is not ingested. - URL: https://private.docs.cohere.com/north/docs/get-started/tools/websearch/home.md - Locator: GA provider choices and handling - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-15 Deep research. Multi-step cited research requires enabled sources and user/group access, with downloadable reports. - URL: https://private.docs.cohere.com/north/docs/get-started/deep-research.md - Locator: Alpha feature and administrator grants - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:job Scheduled Jobs. Recurring Agent jobs are available only in single-user mode, with allowed tools, execution history and generated-file downloads. - URL: https://docs.anythingllm.com/scheduled-jobs/overview - Locator: Single-user restriction; schedules; run traces - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-16 Automations. Node-based workflows combine models, tools and reusable versioned definitions. - URL: https://private.docs.cohere.com/north/docs/get-started/north-automations.md - Locator: Visual builder, roles and workflow lifecycle - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-29 Saving and publishing automations. Automation definitions export JSON with graph/dependencies; credentials and schedules excluded. - URL: https://private.docs.cohere.com/north/docs/get-started/north-automations/building-automations/saving-publishing-monitoring-automations.md - Locator: Versioning and JSON import/export - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-api-run North execute automation API. External authenticated clients can start workflows with typed inputs; this is not a native source-event watcher. - URL: https://private.docs.cohere.com/north/reference/automations/execute.md - Locator: POST /v1/automations/{id}/execute - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-26 Human-in-the-loop automations. Workflows can pause for review and route by human decisions; review timeouts apply. - URL: https://private.docs.cohere.com/north/docs/get-started/north-automations/building-automations/human-in-the-loop-automations.md - Locator: Human Review node - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:api Developer API. Instance APIs manage workspaces, document embedding and chat; API keys confer access and must be protected. - URL: https://docs.anythingllm.com/features/api - Locator: Instance /api/docs; key management; workspace APIs - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:config Configuration. Simple SSO issues short-lived one-use login links for already-provisioned users through a privileged API key; it is not a native SAML/OIDC protocol implementation. - URL: https://docs.anythingllm.com/configuration - Locator: Simple SSO passthrough; multi-user prerequisites - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-north-api About the North API. Instance REST API covers chat, agents, automations and files with bearer/OAuth/workload identity. - URL: https://private.docs.cohere.com/reference/overview.md - Locator: Authentication and API scope - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-api-response North create response API. North exposes model response API with tool and reasoning parameters and permission/rate-limit errors. - URL: https://private.docs.cohere.com/north/reference/responses/create.md - Locator: Request/response and authentication - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-api-upload North file upload API. Authenticated multipart upload stores a file with ID and downloadable content endpoints. - URL: https://private.docs.cohere.com/north/reference/files/create.md - Locator: POST /v1/files - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-api-libraries North library API. Authenticated library creation complements file APIs and library permissions. - URL: https://private.docs.cohere.com/north/reference/libraries/create.md - Locator: Create library endpoint - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-89 Data controls. Blocks new API/web share links; existing conversation links stop, existing automation/table links remain. - URL: https://private.docs.cohere.com/north/docs/admin/configuring_data_controls.md - Locator: Alpha sharing restrictions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-140 Audits. Admin changes/compliance decisions have searchable event rows and programmatic audit endpoints. - URL: https://private.docs.cohere.com/north/docs/admin/audits.md - Locator: Alpha admin events and GET API - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:docker Docker installation overview. Docker provides the shared browser/server deployment with multi-user administration; Desktop is a separate single-user application. - URL: https://docs.anythingllm.com/installation-docker/overview - Locator: Desktop/Docker comparison; server deployment - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:windows Windows installation. Silent installation can support MDM packaging, but all-users installation is explicitly unsupported and Enterprise/Server OS use has caveats. - URL: https://docs.anythingllm.com/installation-desktop/windows - Locator: Current User only; silent install and uninstall - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:ext Browser extension installation. The extension sends pages/selected text into workspaces using an API connection; it does not by itself enforce original web content ACLs. - URL: https://docs.anythingllm.com/browser-extension/install - Locator: Supported browsers; API connection; collected content - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:mobile Mobile overview. A separate Android app runs local models and can pair with Desktop or server instances; iOS is not currently available. - URL: https://docs.anythingllm.com/mobile/overview - Locator: Android only; local models; pairing; feature set - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:meeting-intro Meeting Assistant introduction. Free Desktop meeting recording/transcription is local on Windows/macOS; a selected cloud summary model receives the transcript. - URL: https://docs.anythingllm.com/meeting-assistant/introduction - Locator: Desktop exclusivity; supported OS; privacy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-97 Voice settings. Dictation and long-form mobile recording are separately off by default and require configured transcription service. - URL: https://private.docs.cohere.com/north/docs/admin/configuring_voice_settings.md - Locator: Alpha dictation and beta mobile recording - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:pro AnythingLLM Pro overview. Optional Desktop Pro removes daily Magic-feature limits and generated-document watermarks; it is separate from Cloud Pro. - URL: https://docs.anythingllm.com/pro/overview - Locator: Desktop v1.15+; Magic features; document watermarks - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-9 Document mode. Canvas supports manual/prompt edits, tone/translation actions, versions and DOCX/PDF/MD/HTML exports. - URL: https://private.docs.cohere.com/north/docs/get-started/north-document-mode.md - Locator: Editing, quick actions and exports - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:images Image generation. Configured OpenAI/OpenRouter/Lemonade tools can edit reference images, while the documented Ollama route generates without using references. - URL: https://docs.anythingllm.com/features/image-generation - Locator: Provider table; reference-image editing; /img - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:tts Text to speech. Read-aloud uses configured local/browser or external TTS engines, depending on the selected provider. - URL: https://docs.anythingllm.com/features/text-to-speech - Locator: Provider engines and configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:stt Transcription models. Audio transcription is a separately configurable provider route. - URL: https://docs.anythingllm.com/features/transcription-models - Locator: Transcription provider overview - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:meeting Meeting Assistant features. The Desktop meeting workflow records/imports audio, identifies speakers, allows transcript corrections and summarizes meetings. - URL: https://docs.anythingllm.com/meeting-assistant/features - Locator: Transcription; speakers; editable text; summaries - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-north-changelog-20261026 North release notes. Dated releases document new models, beta/alpha capabilities and removal/deprecation of legacy connectors and APIs. - URL: https://private.docs.cohere.com/north/changelog?format=html - Locator: 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 - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-9-20261026 Document mode. Canvas supports manual/prompt edits, tone/translation actions, versions and DOCX/PDF/MD/HTML exports. - URL: https://private.docs.cohere.com/north/docs/get-started/north-document-mode?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### anythingllm:anythingllm:i18n-pin AnythingLLM locale registration. The pinned frontend registers English, German, French and Italian resources; completeness and naturalness are not established. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/frontend/src/locales/resources.js - Locator: frontend/src/locales/resources.js, English/German/French/Italian imports - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: frontend/src/locales/resources.js ### anythingllm:anythingllm:r4-german-admin AnythingLLM German administrator locale. German locale resources include user/invite/event-log and administrator settings labels. This establishes partial admin localization, not completeness or naturalness. - URL: https://github.com/Mintplex-Labs/anything-llm/blob/9b1fcab141000eaba9f78ed131151de04904454b/frontend/src/locales/de/common.js - Locator: settings users, invites, event-logs and role/admin labels - Evidence kind: source-inspected - Source date: 2026-10-25 - Retrieved: 2026-10-26 - Commit: 9b1fcab141000eaba9f78ed131151de04904454b - Path: frontend/src/locales/de/common.js ### cohere-north:cohere-north:n-doc-105 About SSO. OIDC preferred; SAML, LDAP shim/hybrid and authentication proxy documented; group claims required for group access. - URL: https://private.docs.cohere.com/north/docs/admin/identity/overview.md - Locator: Protocols and Dex identity broker - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:admin-pin AnythingLLM administrative events. The pinned admin routes record user creation/deletion, invitation and API-key lifecycle events. - URL: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba/server/endpoints/admin.js - Locator: server/endpoints/admin.js, user, invite and API-key routes - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: 3e4f9411b67f2dd7fa9fc6f2b95dfacbda0633ba - Path: server/endpoints/admin.js ### cohere-north:cohere-north:n-doc-153 Data deletion. Deletion has asynchronous external cleanup and explicit preserved shared-resource exceptions. - URL: https://private.docs.cohere.com/north/docs/security/data-deletion.md - Locator: Conversation, user and connector cleanup - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-112 SCIM provisioning. Bidirectional user/group sync; disable is reversible, delete re-creates a new identity if later added. - URL: https://private.docs.cohere.com/north/docs/admin/identity/scim/overview.md - Locator: Alpha SCIM2 and deactivation/deletion - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-90 Graceful delete settings. Access ends immediately; configurable private cleanup grace period, shared resources preserved except nontransferable Microsoft libraries. - URL: https://private.docs.cohere.com/north/docs/admin/configuring_graceful_delete_settings.md - Locator: Beta account removal and shared-resource exceptions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-134 Models and providers. Custom endpoints/providers, group access and defaults; grants additive and alias may silently fall back to provider default. - URL: https://private.docs.cohere.com/north/docs/admin/models.md - Locator: Beta UI, alpha RBAC, aliases and fallback - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-158 Compute requirements. North licensed by compute units and separately administered application instances; licence rates absent. - URL: https://private.docs.cohere.com/north/docs/compute-requirements.md - Locator: Sizing and licensing metrics - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:logs Workspace chat logs. Authorized users export workspace/user chat logs in CSV, JSON, Alpaca JSON or JSONL once at least ten logs are available. - URL: https://docs.anythingllm.com/features/chat-logs - Locator: Permissions; export formats; minimum log count - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:event Event logs. The UI records login attempts, messages, setting changes and uploads with user/time details, without a stated immutable retention model. - URL: https://docs.anythingllm.com/features/event-logs - Locator: Events and fields - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-78 Analytics v2. Self-hosted analytics reports users/groups/models/agents/tools; named-user CSV and sampled metrics have limits. - URL: https://private.docs.cohere.com/north/docs/admin/north_analytics_v2.md - Locator: Alpha metrics and CSV/PNG exports - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-95 Analytics settings. Operators can turn event collection off and configure retention for database analytics events. - URL: https://private.docs.cohere.com/north/docs/admin/configuring_analytics_settings.md - Locator: Alpha event collection and retention - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-137 Flow control. User/group/model/source/provider rules enforce request/input/output token limits only after Helm services deployed; fail-open option and unlimited default. - URL: https://private.docs.cohere.com/north/docs/admin/flow-control.md - Locator: Alpha model rate-limit proxy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-207 Token usage monitoring. Operators collect billed/raw tokens by model/provider/operation; no per-user labels, scrape gaps and incomplete paths prevent billing-ledger equivalence. - URL: https://private.docs.cohere.com/north/docs/observability/token-usage.md - Locator: Prometheus/Grafana collection and limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-140-20261026 Audits. Admin changes/compliance decisions have searchable event rows and programmatic audit endpoints. - URL: https://private.docs.cohere.com/north/docs/admin/audits?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-139-20261026 Compliance. Approved investigators get24-hour conversation access/CSV including blocked/redacted content; self-approval forbidden. - URL: https://private.docs.cohere.com/north/docs/admin/compliance?format=html - Locator: 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 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-doc-138 Guardrails admin. HiddenLayer supports allow/block/redact with monitor-only default; timeouts/unsupported entities and advisory content safety can fail open. - URL: https://private.docs.cohere.com/north/docs/admin/north-guardrails.md - Locator: Selected-customer beta PII and alpha content safety - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-193 Guardrails deployment. GPU scanning engine runs inside customer cluster without external HiddenLayer cloud traffic in documented configuration. - URL: https://private.docs.cohere.com/north/docs/advanced/feature-enablement/guardrails.md - Locator: Selected-customer beta in-cluster HiddenLayer - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-145 Terms and conditions. Sign-up/tool-specific multilingual terms require acceptance again after new versions; external URL overrides hosted terms. - URL: https://private.docs.cohere.com/north/docs/admin/terms-and-conditions.md - Locator: Alpha required policy acceptance - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cloud-overview Cloud overview. Mintplex describes each managed customer instance as isolated AWS infrastructure operated and updated by its team. - URL: https://docs.anythingllm.com/cloud/overview - Locator: Private managed instance - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:privacy-cloud Cloud privacy policy. The managed-service policy excludes self-hosting, names AWS/Stripe/PostHog, permits necessary team access and states deletion at cancellation. - URL: https://docs.anythingllm.com/cloud/privacy-policy - Locator: Service scope; AWS; operational access; deletion - Evidence kind: documented - Source date: 2024-07-01 - Retrieved: 2026-10-21 ### anythingllm:anythingllm:storage Desktop storage. Desktop data is stored in an OS-specific local data directory controlled by its user. - URL: https://docs.anythingllm.com/installation-desktop/storage - Locator: Data location and backup - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-146 North security. Recommends operator encryption/network/SSO controls and stdout-to-SIEM forwarding; no observed hardened configuration implied. - URL: https://private.docs.cohere.com/north/docs/security.md - Locator: Customer deployment hardening and log forwarding - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-private Cohere private deployments. Vendor offers customer-managed VPC and air-gapped on-prem delivery with deployment assistance. - URL: https://cohere.com/private-deployments - Locator: VPC/on-prem/air-gap and rollout support - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-217 Model Vault with North. North stays customer-hosted; Cohere processes model inputs in dedicated Vault; ZDR option removes prompt retention. - URL: https://private.docs.cohere.com/north/docs/model-vault-with-north.md - Locator: Customer app plus Cohere inference - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-214 Backup and restore. Operator controls backup placement and retention; encryption master key needed for restore. - URL: https://private.docs.cohere.com/north/docs/backup-restore.md - Locator: Database, secrets and object storage - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-208 Distributed tracing. Optional tracing sends deployment telemetry to operator-selected collectors; geographic placement is not fixed. - URL: https://private.docs.cohere.com/north/docs/observability/traces.md - Locator: Operator OpenTelemetry export - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-commitments Enterprise data 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. - URL: https://cohere.com/enterprise-data-commitments - Locator: Private/third-party versus SaaS Platform; retention and ZDR FAQ - Evidence kind: documented - Source date: 2025-12-05 - Retrieved: 2026-10-21 ### anythingllm:anythingllm:pro-key Desktop Pro activation. A purchased Desktop Pro key is periodically validated; free feature allowances remain without a subscription. - URL: https://docs.anythingllm.com/pro/getting-started - Locator: Periodic licence validation; free allowances - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-vault Model Vault overview. Cohere-managed dedicated inference is separate from the North control plane. - URL: https://docs.cohere.com/docs/model-vault.md - Locator: Dedicated inference deployment and choices - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-165 Deployment model. North application Helm chart deployed on customer Kubernetes; GitOps/ArgoCD recommended for production. - URL: https://private.docs.cohere.com/north/docs/deployment-model.md - Locator: Helm and production GitOps - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-159 Networking requirements. Operator network/DNS/TLS controls; hosted model API optional, image supply needs mirroring for disconnected installations. - URL: https://private.docs.cohere.com/north/docs/networking-requirements.md - Locator: Optional external model API and registry access - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:terms-cloud Cloud terms. Managed-service terms name Mintplex Labs Inc in California, California law, cancellation deletion and no credits for offline service under the generic terms. - URL: https://docs.anythingllm.com/cloud/terms-and-conditions - Locator: Scope; entity; payment; cancellation; offline credits; law - Evidence kind: documented - Source date: 2024-07-01 - Retrieved: 2026-10-21 ### anythingllm:anythingllm:privacy-desktop Desktop privacy policy. The policy describes local Desktop data and optional telemetry; connected external models still need separately scoped data processing. - URL: https://docs.anythingllm.com/installation-desktop/privacy - Locator: Desktop-only scope; telemetry - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-139 Compliance. Approved investigators get24-hour conversation access/CSV including blocked/redacted content; self-approval forbidden. - URL: https://private.docs.cohere.com/north/docs/admin/compliance.md - Locator: Alpha dual-control investigation and CSV - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-88 Data retention settings. Age-based retention off by default; enabled defaults90day soft-delete plus30-day timeout; hourly hard-delete still runs for manually deleted conversations. - URL: https://private.docs.cohere.com/north/docs/admin/configuring_data_retention_settings.md - Locator: Alpha conversation retention and jobs - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-combination-20261026 Cohere and Aleph Alpha combination agreement. Combination remains subject to regulatory approvals; future dual headquarters and leadership depend on closing. - URL: https://cohere.com/blog/cohere-and-aleph-alpha-sign-agreement - Locator: September 16 definitive agreement and closing conditions; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 972ee8d4e3dd868bf9d5986f00e66c0543ffd55cf519b78909aa7ec0cad9c399 on 2026-10-26 - Evidence kind: documented - Source date: 2026-09-16 - Retrieved: 2026-10-26 ### cohere-north:cohere-north:corporate-aisle-20261026 Cohere AISLE proposed acquisition announcement. 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. - URL: https://cohere.com/blog/cohere-and-aisle-sign-letter-of-intent-to-advance-cyber-resilient-sovereign-ai - Locator: October 15 announcement, opening paragraphs and closing transaction conditions; HTTP 200, body SHA256 e17b07229ecb36abb9f98b4d36e6541d3c74db64f0758fa93b8b48df3c7ccf58 - Evidence kind: vendor-claimed - Source date: 2026-10-15 - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-terms-20261026 Cohere public terms of use. Public general terms identify Cohere Inc and Ontario/Toronto law; North commercial subscription terms were not retrieved. - URL: https://cohere.com/terms-of-use - Locator: 2022 terms; scope and choice of law; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 09c6e9b556c82d0e47438f044477298abb536b98fb30622371806a82ea1f3cbd on 2026-10-26 - Evidence kind: documented - Source date: 2022-09-07 - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-trust-20261026 Cohere Trust Center. 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. - URL: https://trustcenter.cohere.com/?format=html - Locator: Reports, subprocessors and regulatory FAQs; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 be106d8cf80369b1d1adf72c7912bf7c8af1221b76a8a381c6a95455d2666401 on 2026-10-26 - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-26 ### cohere-north:cohere-north:n-trust Cohere Trust Center. 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. - URL: https://trustcenter.cohere.com/?format=html - Locator: Reports, subprocessors and regulatory FAQs - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-terms Cohere public terms of use. Public general terms identify Cohere Inc and Ontario/Toronto law; North commercial subscription terms were not retrieved. - URL: https://cohere.com/terms-of-use - Locator: 2022 terms; scope and choice of law - Evidence kind: documented - Source date: 2022-09-07 - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-154 Data encryption at rest. Customer-held Kubernetes master key encrypts chat columns; automation/workflow data excluded. - URL: https://private.docs.cohere.com/north/docs/security/data-encryption-at-rest.md - Locator: Optional AES256GCM chat-column envelope encryption - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:secrecy-cloud-access AnythingLLM Cloud operational access policy. The managed-only policy permits operational team instance access, names AWS infrastructure and excludes self-hosted deployments; it does not enumerate plain-text field permissions. - URL: https://docs.anythingllm.com/cloud/privacy-policy - Locator: Instance Access and Management; Third-Party Services; Data Storage and Security; policy scope - Evidence kind: documented - Source date: 2024-07-01 - Retrieved: 2026-10-21 ### anythingllm:anythingllm:secrecy-model-routing AnythingLLM local and cloud model routing. System, workspace and agent models can use local or cloud providers; the selected inference path is separate from where the application is hosted. - URL: https://docs.anythingllm.com/setup/llm-configuration/overview - Locator: System LLM; Workspace LLM; Agent LLM; Supported LLM Providers - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cloud-cards-r2 AnythingLLM advertised Cloud plan cards. The current offer page advertises Basic at $50/month and Pro at $99/month, with Enterprise by quote; Basic explicitly asks for an LLM API key. - URL: https://anythingllm.com/cloud - Locator: Basic $50/month, Pro $99/month and quote-only Enterprise cards; Basic BYO LLM key - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-pricing Cohere pricing. North pricing is custom; model API trials and Model Vault instance rates are separate products. - URL: https://cohere.com/pricing - Locator: North custom pricing; separate Model Vault/API tables - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cost-vm Azure Retail Prices, Switzerland North Linux VMs. EUR hourly PAYG rates retrieved 2026-10-21 are 0.2226, 0.4453 and 0.8905 for D4s, D8s and D16s v5 respectively. - URL: https://prices.azure.com/api/retail/prices?currencyCode=EUR&%24filter=armRegionName+eq+%27switzerlandnorth%27+and+serviceName+eq+%27Virtual+Machines%27+and+%28armSkuName+eq+%27Standard_D4s_v5%27+or+armSkuName+eq+%27Standard_D8s_v5%27+or+armSkuName+eq+%27Standard_D16s_v5%27%29+and+priceType+eq+%27Consumption%27 - Locator: Consumption; Virtual Machines Dsv5 Series; Standard_D4s_v5/D8s_v5/D16s_v5 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cost-pg Azure Retail Prices, PostgreSQL Flexible Server. EUR hourly PAYG GP compute is 0.2288, 0.4576 and 0.9152 for 2/4/8 vCore; storage is EUR 0.1325 per GB-month. - URL: https://prices.azure.com/api/retail/prices?currencyCode=EUR&%24filter=armRegionName+eq+%27switzerlandnorth%27+and+serviceName+eq+%27Azure+Database+for+PostgreSQL%27+and+priceType+eq+%27Consumption%27 - Locator: General Purpose Ddsv5 Series Compute, 2/4/8 vCore; Flex Server Storage - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cost-fx ECB euro reference rate history. The 2026-10-20 reference rates are EUR 1 = USD 1.1215 and CHF 0.9237. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time=2026-10-20; USD and CHF - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cost-model OpenAI API pricing. Standard gpt-6-luna API price is USD 0.10 per million input tokens and USD 0.50 per million output tokens; caching, batch and regional premiums are separate. - URL: https://developers.openai.com/api/docs/pricing - Locator: Standard, short-context gpt-6-luna row - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cost-effort GPT-6 Luna model documentation. The model accepts reasoning effort none, the lowest documented effort, and lists the same standard text-token rates. - URL: https://developers.openai.com/api/docs/models/gpt-6-luna - Locator: Reasoning effort and text-token pricing - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:fx-ecb ECB historical FX. EUR1=USD1.1215=CHF0.9237; rates recorded without inventing an unpriced North total. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: 2026-10-20 USD/CHF rates - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-home North 2 product page. North offers agents, automations, libraries, applications and private deployment. - URL: https://cohere.com/north - Locator: Platform and private deployment overview - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-142 White labeling. Operators configure branding; commercial branding licence terms not established. - URL: https://private.docs.cohere.com/north/docs/admin/whitelabeling.md - Locator: Branding configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### anythingllm:anythingllm:cloud-terms-r2 AnythingLLM generic managed Cloud contract scope. The published generic terms cover managed Cloud, exclude self-hosting and deny offline-service credits; no bespoke Enterprise override was reviewed. - URL: https://docs.anythingllm.com/cloud/terms-and-conditions - Locator: Scope of Agreement; Instance Offline Recovery; last-updated date - Evidence kind: documented - Source date: 2024-07-01 - Retrieved: 2026-10-21 ### anythingllm:anythingllm:support-r2 AnythingLLM public support channels. Public support routes are GitHub, team email and community Discord; the guide recommends GitHub/email for direct team assistance. - URL: https://docs.anythingllm.com/support - Locator: GitHub Issues; team email; Discord Community; direct-assistance note - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-combination Cohere and Aleph Alpha combination agreement. Combination remains subject to regulatory approvals; future dual headquarters and leadership depend on closing. - URL: https://cohere.com/blog/cohere-and-aleph-alpha-sign-agreement - Locator: September 16 definitive agreement and closing conditions - Evidence kind: documented - Source date: 2026-09-16 - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-status Cohere status. Public hosted service status is available; it does not establish customer-hosted North SLA. - URL: https://status.cohere.com/ - Locator: Hosted API service status - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-guide North user guide. Lists planned November 13 v2.1 andDecember 11 v2.2 releases, subject to change; not individual feature delivery promises. - URL: https://private.docs.cohere.com/docs/get-started/north-user-guide.md - Locator: Release calendar and feature-state definitions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### cohere-north:cohere-north:n-doc-36 Data Interpreter. Legacy spreadsheet Python tool is deprecated in favor of code sandbox; whole-sheet analysis differs from indexed metadata search. - URL: https://private.docs.cohere.com/north/docs/get-started/tools/data-interpreter/home.md - Locator: Deprecated tool and successor - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21