--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/dust-vs-swissgpt/" data_url: "https://onaihq.com/compare/agents/dust-vs-swissgpt/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" --- # Dust vs AlpineAI / SwissGPT > Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI. This comparison has 28 criteria with sourced findings for both products, including 28 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. - Dust source checks: 2026-10-21. - AlpineAI / SwissGPT source checks: 2026-10-21 to 2026-10-26. - Canonical HTML: https://onaihq.com/compare/agents/dust-vs-swissgpt/ - Machine-readable JSON: https://onaihq.com/compare/agents/dust-vs-swissgpt/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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust offers per-message model choice and ordered auto-model lists, with access-tier and region controls. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit plan (Free/Pro/Max); Enterprise model access inherits the published catalogue; model-tier and EU eligibility separately constrained; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - The catalogue finding is restricted to named documentation entries; conflicting Gemini4 Argon EU eligibility is an explicit gap. - providers — Which model providers are available? [supported]: Docs list OpenAI, Anthropic, Google, Mistral and Fireworks-served models; exact enabled models depend on workspace and tier. Sources: dust:dust:models, dust:dust:eu-models. - current_models — Which current models are selectable on this plan? [partial]: The model-selection document lists GPT6.1 Sol, Claude Opus5.5/Sonnet5.5, Gemini3.8 Flash and Mistral models. Gemini4 Argon is excluded from this current-EU availability finding: its release note conflicts with the EU table, and the documented authoritative picker flag was not observed. No complete current tenant catalogue is claimed. Sources: dust:dust:models, dust:dust:changelog, dust:dust:eu-models, dust:dust:pricing. - user_choice — Can users pick the model per chat? [supported]: The composer chooses a model for the next message; Agent Builder sets a persistent agent default. Sources: dust:dust:models. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [supported]: Basic/Standard/Premium use ordered candidate lists and availability fallback, not prompt-dependent task routing. A replacement indicator names the fallback during a detected outage. Sources: dust:dust:models. - multimodal_input — Which models accept images, audio or files? [partial]: Conversation files support images, documents and audio transcripts; the exact input capability for every current model is not fully tabulated. Sources: dust:dust:files. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:models, dust:dust:eu-models, dust:dust:changelog, dust:dust:pricing, dust:dust:files #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial AlpineAI names Mistral Large 3 as its primary model and says it operates all models itself in Switzerland. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - The FAQ does not enumerate all models, expose a per-chat picker, explain routing visibility or map multimodal inputs to models. - providers — Which model providers are available? [partial]: Mistral is the named current provider. Other providers are not enumerated. Sources: swissgpt:swissgpt:product. - current_models — Which current models are selectable on this plan? [partial]: Mistral Large 3 is named as the primary model; this does not establish a user-selectable catalogue. Sources: swissgpt:swissgpt:product. - user_choice — Can users pick the model per chat? [unknown]: Can users pick the model per chat? Unknown. The FAQ does not enumerate all models, expose a per-chat picker, explain routing visibility or map multimodal inputs to models. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [unknown]: Does the product route between models automatically, and is the chosen model shown? Unknown. The FAQ does not enumerate all models, expose a per-chat picker, explain routing visibility or map multimodal inputs to models. - multimodal_input — Which models accept images, audio or files? [unknown]: Which models accept images, audio or files? Unknown. The FAQ does not enumerate all models, expose a per-chat picker, explain routing visibility or map multimodal inputs to models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial The public changelog and exact agent model selection are documented; release-lag and removal notice remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - release_lag_days — What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? The dated changelog and model-selection docs were checked; last-three-release/provider lag measurements and a fixed advance deprecation-notice period were not established. - changelog — Is there a dated public model changelog? [supported]: The public changelog contains dated model releases including Gemini 4 Argon on October 14, 2026. Sources: dust:dust:changelog. - deprecation_notice — How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? The dated changelog and model-selection docs were checked; last-three-release/provider lag measurements and a fixed advance deprecation-notice period were not established. - version_pinning — Can an admin keep an older model version? [partial]: An agent can select a specific model and keeps it until changed, subject to continued provider/workspace availability. No indefinite old-version entitlement is established. Sources: dust:dust:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:changelog, dust:dust:models #### AlpineAI / SwissGPT 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. ### 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. #### Dust 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. #### AlpineAI / SwissGPT 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. ### 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. #### Dust 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. #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial AlpineAI says it hosts open models on its own Swiss hardware. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Customer-hosted chat and embedding routes, supported runtimes and their feature parity are not documented in the reviewed current offer. - self_hosted_chat — Can chat use a customer-hosted model? [unknown]: Can chat use a customer-hosted model? Unknown. Customer-hosted chat and embedding routes, supported runtimes and their feature parity are not documented in the reviewed current offer. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [unknown]: Can retrieval use customer-hosted embeddings? Unknown. Customer-hosted chat and embedding routes, supported runtimes and their feature parity are not documented in the reviewed current offer. - feature_parity — Which features fail with self-hosted models? [unknown]: Which features fail with self-hosted models? Unknown. Customer-hosted chat and embedding routes, supported runtimes and their feature parity are not documented in the reviewed current offer. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [supported]: The vendor identifies Mistral Large 3 as its current primary open model, operated on AlpineAI-owned hardware in Switzerland without foreign model APIs. Sources: swissgpt:swissgpt:product. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Admins cap models by workspace, group and member, with explicit published-agent exceptions and credit limits. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No two-user enforcement test. Published agents can run above member tiers if the separate admin setting permits it. - model_allowlist_by_group — Can admins limit models per group? [supported]: Model access ceilings apply to the workspace, groups or individuals and cover reasoning efforts as well as auto selections. Sources: dust:dust:tiers. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [partial]: EU-only mode restricts all active agents and pickers to EU-hosted models. Spaces bound knowledge and agent access; arbitrary per-data-class model rules were not established. Sources: dust:dust:eu-models, dust:dust:spaces. - default_model — Can admins set the default model? [supported]: Builders configure an agent default, which may be exact or Basic/Standard/Premium. Composer changes do not edit it for others. Sources: dust:dust:models. - user_limits — What per-user message or token limits apply, and are they published? [supported]: Free seats have 500 lifetime credits, Pro 8,000/month and Max 40,000/month, plus applicable shared-pool rules and member spend limits. Sources: dust:dust:credits, dust:dust:credit-management. - limit_behaviour — What happens when a limit is reached? [supported]: Members block when applicable sources/caps are exhausted. A message begun under a cap can finish above it; new messages then block. A separate root-task checkpoint can pause at 600 AWU. Sources: dust:dust:credit-management, dust:dust:credits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:tiers, dust:dust:eu-models, dust:dust:spaces, dust:dust:models, dust:dust:credits, dust:dust:credit-management #### AlpineAI / SwissGPT 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. ## 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Conversation files and code/OCR handling are documented; conflicting effective upload caps are explicitly unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No common PDF/scan/Excel/PowerPoint fixture run. - Do not use either disputed cap set as the effective Business upload limit. - formats — Which formats are accepted? [supported]: Conversation uploads accept documents/PDF, text/code, Excel/CSV/TSV, images and supported audio. Direct video uploads are explicitly excluded by the limits FAQ. Sources: dust:dust:files, dust:dust:file-limits. - limits — What size and count limits apply per file and chat? [unknown]: Effective image/audio/tabular maximums and file counts are unknown: Conversation Files lists5/25/50MB while File size limits lists20/100/350MB. Both mention50MB general data files, but neither resolves the actual current per-plan upload route. No logged-in upload test was performed. - ocr — Are scanned PDFs read? [partial]: Computer documents OCR for English, French and mixed scans with page-level caveats. Drive connector itself ignores image-only files; upload to a conversation is the documented route. Sources: dust:dust:computer, dust:dust:drive. - spreadsheets — Are Excel tables read with structure intact? [partial]: Computer can read, calculate and edit uploaded Excel with code. Formula/style preservation must be checked; no fixture fidelity result is available. Sources: dust:dust:computer. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [partial]: Conversation uploads are not indexed in workspace sources. Computer can inspect full files, while knowledge search retrieves relevant context; complete chunk visibility was not verified. Sources: dust:dust:files, dust:dust:computer, dust:dust:search. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:files, dust:dust:file-limits, dust:dust:computer, dust:dust:drive, dust:dust:search #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Document upload is advertised for assistants and chat. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - The published 50-document/100 MB assistant limit does not define per-file and per-chat limits. OCR, embedded images, formula/table fidelity and full-file versus chunked processing need technical documentation or the shared upload fixture. - formats — Which formats are accepted? [partial]: PDF, Word, text and Excel are named across the product and sector pages. This is not an exhaustive format matrix. Sources: swissgpt:swissgpt:product, swissgpt:swissgpt:university. - limits — What size and count limits apply per file and chat? [unknown]: What size and count limits apply per file and chat? Unknown. The published 50-document/100 MB assistant limit does not define per-file and per-chat limits. OCR, embedded images, formula/table fidelity and full-file versus chunked processing need technical documentation or the shared upload fixture. - ocr — Are scanned PDFs read? [unknown]: Are scanned PDFs read? Unknown. The published 50-document/100 MB assistant limit does not define per-file and per-chat limits. OCR, embedded images, formula/table fidelity and full-file versus chunked processing need technical documentation or the shared upload fixture. - spreadsheets — Are Excel tables read with structure intact? [unknown]: Are Excel tables read with structure intact? Unknown. The published 50-document/100 MB assistant limit does not define per-file and per-chat limits. OCR, embedded images, formula/table fidelity and full-file versus chunked processing need technical documentation or the shared upload fixture. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [unknown]: Is the whole file used or only retrieved parts, and does the user see which? Unknown. The published 50-document/100 MB assistant limit does not define per-file and per-chat limits. OCR, embedded images, formula/table fidelity and full-file versus chunked processing need technical documentation or the shared upload fixture. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product, swissgpt:swissgpt:university ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Spaces persist shared knowledge and bind it to agent tools. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - persistent_collections — Can users keep document collections across chats? [supported]: Open and restricted Spaces retain connected sources, folders and other data across conversations. Sources: dust:dust:spaces. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: Open Spaces are workspace-wide; restricted Spaces have explicit members or provisioned groups. Sources: dust:dust:spaces. - size_limits — What are the collection limits? [partial]: Business supports five Spaces and Enterprise 100. Complete per-Space storage/document quotas were not established. Sources: dust:dust:spaces. - assistant_binding — Can collections be bound to an assistant? [supported]: An agent tool can use selected Space data; Space membership governs agent visibility and use. Sources: dust:dust:spaces. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:spaces #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Standard and Premium include document-backed assistants with published collection limits. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - User/group/organisation sharing and Enterprise collection limits are not specified. The wording does not clearly distinguish per-file from aggregate 100 MB. - persistent_collections — Can users keep document collections across chats? [supported]: Assistants retain their own reference-document workspace for later questions. Sources: swissgpt:swissgpt:product. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [unknown]: Can collections be shared with users, groups or the whole organisation? Unknown. User/group/organisation sharing and Enterprise collection limits are not specified. The wording does not clearly distinguish per-file from aggregate 100 MB. - size_limits — What are the collection limits? [partial]: Standard has 2 assistants and Premium 5; each is listed as 50 documents / max. 100 MB. Enterprise limits are not published. Sources: swissgpt:swissgpt:university. - assistant_binding — Can collections be bound to an assistant? [supported]: Users place documents in an assistant workspace and questions use those sources. Sources: swissgpt:swissgpt:product. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product, swissgpt:swissgpt:university ### 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). #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Managed content connectors coexist with MCP tools and beta imports; Microsoft content indexing is account-scoped. Availability: generally-available Delivery: official-integration Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business: up to3 connections and5 remote MCP servers; Enterprise: unlimited connection/MCP packaging; beta imports identified separately; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - Managed sources, metadata/table-query connections, MCP tools and beta imports are separate routes; no all-systems managed-index promise. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: The Microsoft connection syncs selected SharePoint drives/documents within the connecting account permissions. Teams-associated SharePoint content is described; this does not establish Outlook mail or all Teams messages as indexed sources. Sources: dust:dust:microsoft. - google_workspace — Which Google sources are connected? [partial]: Drive documents, Sheets, Slides and text PDFs can sync. Gmail is separately available as an MCP tool in the credits/tool catalog, not established as the same managed content index. Sources: dust:dust:drive, dust:dust:credits. - atlassian — Confluence and Jira? [partial]: Confluence indexes selected global spaces, excluding restricted pages. Jira has a beta custom import and MCP tool route; do not count the beta import as a general managed connector. Sources: dust:dust:confluence, dust:dust:jira, dust:dust:credits. - other_systems — Which other business systems? [partial]: Documented routes include managed Slack/Notion/GitHub and Salesforce/Zendesk/Snowflake sources/tools. BigQuery specifically uses a dedicated-service-account table-query connection: Dust keeps metadata, not a synchronized table-content index; queries stay within the chosen BigQuery dataset location and Space admins select tables. General Business/Enterprise connection limits apply; a BigQuery-specific commercial add-on is not separately specified. Sources: dust:dust:sources, dust:dust:credits, dust:dust:r2-bigquery, dust:dust:pricing. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Admins can connect a customer-hosted MCP server at a reachable secured URL. This is tool access, not evidence of a native SMB/file-share connector or on-premises Dust deployment. Sources: dust:dust:tools. - connector_provider — Who builds and maintains each connector? [supported]: Dust manages built-in connections; external MCP servers can be vendor/community/customer hosted and authenticated separately. Sources: dust:dust:permissions, dust:dust:tools. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:microsoft, dust:dust:drive, dust:dust:credits, dust:dust:confluence, dust:dust:jira, dust:dust:sources, dust:dust:r2-bigquery, dust:dust:pricing, dust:dust:tools, dust:dust:permissions #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise sector pages name production REST integrations with eGeKo and five healthcare systems. A public standard connector matrix for M365, Google, Atlassian and on-premise sources remains unverified. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - The production integration names are vendor claims on the sector pages, not a tested connector inventory. - Individual integrations require the Enterprise package from 10 licences; no API account, customer deployment or fixture was accessed. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [unknown]: Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? Unknown. The current FAQ does not identify shipped SharePoint, OneDrive, Outlook-search, Teams, Google, Atlassian or on-prem-source connectors, their consent scopes or maintainers. The Outlook add-in is recorded under WORK-02. Rechecked 2026-10-26 in AlpineAI product, public-administration and healthcare feature/licence FAQs and Security page. No extra technical/admin documentation was identified in official links or targeted first-party searches; no account fixture was run. - google_workspace — Which Google sources are connected? [unknown]: Which Google sources are connected? Unknown. The current FAQ does not identify shipped SharePoint, OneDrive, Outlook-search, Teams, Google, Atlassian or on-prem-source connectors, their consent scopes or maintainers. The Outlook add-in is recorded under WORK-02. Rechecked 2026-10-26 in AlpineAI product, public-administration and healthcare feature/licence FAQs and Security page. No extra technical/admin documentation was identified in official links or targeted first-party searches; no account fixture was run. - atlassian — Confluence and Jira? [unknown]: Confluence and Jira? Unknown. The current FAQ does not identify shipped SharePoint, OneDrive, Outlook-search, Teams, Google, Atlassian or on-prem-source connectors, their consent scopes or maintainers. The Outlook add-in is recorded under WORK-02. Rechecked 2026-10-26 in AlpineAI product, public-administration and healthcare feature/licence FAQs and Security page. No extra technical/admin documentation was identified in official links or targeted first-party searches; no account fixture was run. - other_systems — Which other business systems? [partial]: The public-administration FAQ names eGeKo as an integration in production. The healthcare FAQ names Axenita, Aeskulap, Ines, Logival and Mediway as production integrations through the AlpineAI REST API. Individual integrations are part of Enterprise from 10 licences and planned with the customer IT team. Public consent scopes, per-system configuration and a self-service connector matrix are not supplied. Sources: swissgpt:swissgpt:public-pricing-20261026, swissgpt:swissgpt:health-pricing-20261026. - on_prem_sources — Can on-prem file shares or databases be connected? [unknown]: Can on-prem file shares or databases be connected? Unknown. The current FAQ does not identify shipped SharePoint, OneDrive, Outlook-search, Teams, Google, Atlassian or on-prem-source connectors, their consent scopes or maintainers. The Outlook add-in is recorded under WORK-02. Rechecked 2026-10-26 in AlpineAI product, public-administration and healthcare feature/licence FAQs and Security page. No extra technical/admin documentation was identified in official links or targeted first-party searches; no account fixture was run. - connector_provider — Who builds and maintains each connector? [partial]: AlpineAI plans custom Enterprise integrations with the institution IT team. The university FAQ mentions expanding prebuilt connectors without naming them. Sources: swissgpt:swissgpt:university. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:public-pricing-20261026, swissgpt:swissgpt:health-pricing-20261026, swissgpt:swissgpt:product-20261026, swissgpt:swissgpt:security-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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Knowledge access is documented through connection-account scope and Dust Spaces; per-user source-ACL mirroring is unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Connector access through one account is not counted as demonstrated per-user source permission preservation. - source_permissions_respected — Are source permissions enforced per user? [partial]: Drive and Microsoft content available to Dust follows the connecting account and admin-selected data. Users then access agent knowledge through Space membership. Individual source ACL inheritance for each querying user was not established. Sources: dust:dust:drive, dust:dust:microsoft, dust:dust:permissions. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: Managed content is synchronized under the connection identity and gated through open/restricted Spaces; personal tool credentials are a separate per-user route. Sources: dust:dust:permissions, dust:dust:credentials. - revocation_delay — How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? No two-user restricted-document or revocation fixture was run. Checked connector/Space docs did not establish per-query source ACL mirrors, a source-permission revocation SLA, or Microsoft Purview-label enforcement. - admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins choose connector folders/documents/sites and control restricted Space membership. Sources: dust:dust:spaces, dust:dust:microsoft. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? No two-user restricted-document or revocation fixture was run. Checked connector/Space docs did not establish per-query source ACL mirrors, a source-permission revocation SLA, or Microsoft Purview-label enforcement. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:drive, dust:dust:microsoft, dust:dust:permissions, dust:dust:credentials, dust:dust:spaces #### AlpineAI / SwissGPT 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. ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Managed connectors copy and synchronize content, with source-specific refresh and deletion timing. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - live_or_indexed — Is content searched live or copied into an index? [supported]: Connections synchronize content into Dust; conversation uploads remain scoped to the chat. MCP tools can access live services separately. Sources: dust:dust:permissions, dust:dust:files, dust:dust:tools. - sync_interval — How often does an index refresh? [supported]: Microsoft describes five-minute sync cycles; Drive says a few minutes; Confluence describes event updates plus an approximate hourly check. Sources: dust:dust:microsoft, dust:dust:drive, dust:dust:confluence. - deletion_propagation — How quickly does a deleted document disappear? [partial]: Microsoft changes/deletions appear on a subsequent sync and large batches can take longer. Drive deletions occur during its sync. No measured end-to-end bound was tested. Sources: dust:dust:microsoft, dust:dust:drive. - index_location — Where is indexed content stored? [partial]: Dust markets EU or US hosting; exact per-index country, cloud provider and backup location were not established. Sources: dust:dust:security. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:permissions, dust:dust:files, dust:dust:tools, dust:dust:microsoft, dust:dust:drive, dust:dust:confluence, dust:dust:security #### AlpineAI / SwissGPT 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. ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Knowledge and research tools cite sources; observed retrieval quality remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - citations — Are answers linked to specific sources? [supported]: Deep-dive documents citations to documents, web pages and data queries. Sources: dust:dust:deep. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test. - cross_language — Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test. - no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The vendor describes source citations in Listener transcript search; retrieval accuracy was not tested. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - No shared corpus was loaded. Citation correctness, cross-language retrieval, refusal behaviour and observed question-set accuracy remain unmeasured. - citations — Are answers linked to specific sources? [partial]: The Listener FAQ advertises full-text search with source references over transcribed recordings. General document-RAG citation coverage is unspecified. Sources: swissgpt:swissgpt:product. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No shared corpus was loaded. Citation correctness, cross-language retrieval, refusal behaviour and observed question-set accuracy remain unmeasured. - cross_language — Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unknown. No shared corpus was loaded. Citation correctness, cross-language retrieval, refusal behaviour and observed question-set accuracy remain unmeasured. - no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? Unknown. No shared corpus was loaded. Citation correctness, cross-language retrieval, refusal behaviour and observed question-set accuracy remain unmeasured. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No shared corpus was loaded. Citation correctness, cross-language retrieval, refusal behaviour and observed question-set accuracy remain unmeasured. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agent-specific private memory persists across chats and can be viewed or deleted. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - custom_instructions — Can users set persistent instructions? [partial]: Agent instructions persist in the agent configuration and saved memory can contain user preferences; a separate personal global-instructions setting was not established. Sources: dust:dust:builder, dust:dust:memory. - cross_chat_memory — Does the product remember facts across chats? [supported]: The Memory tool retains user-specific information across conversations per agent. Sources: dust:dust:memory. - user_memory_controls — Can users view, edit and delete memories? [partial]: Users can view and delete agent memories, which persist until deletion. Direct editing or a global personal off switch was not established. Sources: dust:dust:memory. - admin_memory_controls — Can admins turn memory off? [unknown]: Can admins turn memory off? The Agent Memory and governance guides were checked; an admin-wide switch to disable all memory was not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:memory #### AlpineAI / SwissGPT 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. ## 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Custom agents have instructions, models, knowledge and tools with group-governed creation and sharing. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Agent Builder configures instructions, models, knowledge and tools. Sources: dust:dust:builder. - creator_permissions — Can admins limit who creates them? [supported]: Create/publish agent and skill permissions can be Everyone, Groups or Admin only. Sources: dust:dust:governance. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Agents and their knowledge access are controlled by sharing and Space memberships; group governance regulates publishing. Sources: dust:dust:builder, dust:dust:spaces, dust:dust:governance. - catalogue — Is there an internal assistant directory? [partial]: Published/shared agents and default agents are discoverable in the workspace; exact catalog configuration was not observed. Sources: dust:dust:builder, dust:dust:models. - prompt_library — Are shared prompt templates available? [partial]: Reusable agents and skills package instructions, knowledge and tools. A separate legacy prompt-library feature is not assumed. Sources: dust:dust:governance, dust:dust:builder. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:governance, dust:dust:spaces, dust:dust:models #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Users can create document-backed assistants and use prompt templates. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Creator restrictions, sharing boundaries, versioning, tool configuration and an organisation-managed directory are not established in the public pages. - create_assistants — Can users create assistants with instructions, knowledge and tools? [partial]: Users create workspaces with their own reference documents; configurable instructions and external tools are not described. Sources: swissgpt:swissgpt:product. - creator_permissions — Can admins limit who creates them? [unknown]: Can admins limit who creates them? Unknown. Creator restrictions, sharing boundaries, versioning, tool configuration and an organisation-managed directory are not established in the public pages. - sharing_scope — Can assistants be shared with users, groups or everyone? [unknown]: Can assistants be shared with users, groups or everyone? Unknown. Creator restrictions, sharing boundaries, versioning, tool configuration and an organisation-managed directory are not established in the public pages. - catalogue — Is there an internal assistant directory? [partial]: Premium adds preconfigured assistants; an organisation directory is not established. Sources: swissgpt:swissgpt:product. - prompt_library — Are shared prompt templates available? [partial]: Chat includes prompt templates for recurring tasks; shared-team template administration is not specified. Sources: swissgpt:swissgpt:product. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust supports built-in tools, customer MCP servers and personal or shared credentials. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No external-tool call or access-boundary fixture was run. - builtin_tools — Which tools are built in? [supported]: Documented tools include knowledge search, table queries, web search, Computer, images, speech and agent orchestration. Sources: dust:dust:credits, dust:dust:computer. - custom_actions — Can admins add API actions? [supported]: Admins can connect customer-written MCP tools over secured publicly reachable URLs. Sources: dust:dust:tools. - mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: Admins add remote MCP servers with automatic/static OAuth or bearer-token authentication and can restrict tools to skills. Sources: dust:dust:tools. - tool_auth — Do tools act as the user or as a shared account? [supported]: Shared credentials act as one service account; personal credentials use each user OAuth after initial admin setup. Sources: dust:dust:credentials. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Computer network domains can require user approval; dated connector releases describe approval for writes. A universal confirmation rule for every tool and unattended trigger was not established. Sources: dust:dust:computer, dust:dust:changelog. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:credits, dust:dust:computer, dust:dust:tools, dust:dust:credentials, dust:dust:changelog #### AlpineAI / SwissGPT 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. ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents can search the web and run multi-step Deep-dive research. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - web_search — Is web search available? [supported]: Web Search & Browse runs Google queries and reads result pages. Sources: dust:dust:web. - admin_toggle — Can admins disable it per organisation or group? [partial]: Web tools are selected in agent configuration; default Deep-dive can be disabled by admins. A universal per-group web-off rule was not established. Sources: dust:dust:web, dust:dust:deep. - search_provider — Which search provider handles queries, and where? [partial]: The guide calls the search a Google query. The intermediary provider and countries handling queries/crawling were not established. Sources: dust:dust:web. - deep_research — Is multi-step research with a report available? [supported]: Deep-dive plans, spawns parallel specialists and produces a research report. It searches Company Data and cannot use Table Query. Sources: dust:dust:deep. - web_citations — Are web sources cited? [supported]: Deep-dive promises citations to web and company sources. Sources: dust:dust:deep. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:web, dust:dust:deep #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web search is included but requires organisation activation and user consent; queries can leave AlpineAI infrastructure. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Group-specific controls, a multi-step research/report mode and general web citation behaviour are not documented. - web_search — Is web search available? [supported]: Included across licence models and optional at use time. Sources: swissgpt:swissgpt:product, swissgpt:swissgpt:terms. - admin_toggle — Can admins disable it per organisation or group? [supported]: Administrator must enable the instance; can disable it instance-wide. Users consent per search and again for detected sensitive content. Sources: swissgpt:swissgpt:terms. - search_provider — Which search provider handles queries, and where? [supported]: DPA Annex 3 names Brave Software, Inc., US, for Brave Search API; activated search sends query/chat content outside AlpineAI infrastructure. Sources: swissgpt:swissgpt:dpa, swissgpt:swissgpt:terms. - deep_research — Is multi-step research with a report available? [unknown]: Is multi-step research with a report available? Unknown. Group-specific controls, a multi-step research/report mode and general web citation behaviour are not documented. - web_citations — Are web sources cited? [unknown]: Are web sources cited? Unknown. Group-specific controls, a multi-step research/report mode and general web citation behaviour are not documented. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product, swissgpt:swissgpt:terms, swissgpt:swissgpt:dpa ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents support schedules and webhook automation with admin-created event sources. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - workflow_builder — Is there a workflow or chain builder? [partial]: Agents orchestrate tools and sub-agents; external n8n and trigger workflows are documented. A separate visual multi-step chain canvas was not established. Sources: dust:dust:deep, dust:dust:triggers, dust:dust:changelog. - scheduled_tasks — Can prompts or assistants run on a schedule? [supported]: Agents can run on recurring schedules. Sources: dust:dust:schedules. - event_triggers — Can external events start a workflow? [supported]: Built-in webhook sources include GitHub, Jira, Linear, Zendesk and Fathom; signed custom webhooks are supported. Sources: dust:dust:webhooks. - builder_audience — Is building aimed at business users, IT or developers? [supported]: Admins connect event sources; builders/members attach filtered triggers in Agent Builder and can use natural-language trigger creation through Dust Default. Sources: dust:dust:webhooks, dust:dust:changelog. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep, dust:dust:triggers, dust:dust:changelog, dust:dust:schedules, dust:dust:webhooks #### AlpineAI / SwissGPT 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. ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Multi-step agent work and visible Deep-dive progress are documented; safety controls depend on tool and trigger. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No shared gather/documents/email fixture or side-effect audit was run. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: Deep-dive plans, delegates and synthesizes, and Computer can execute deterministic file/code work. Sources: dust:dust:deep, dust:dust:computer. - visible_steps — Are steps and tool calls shown? [supported]: Deep-dive documentation shows reasoning and sub-agent progress in real time. Sources: dust:dust:deep. - side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Computer domains may require user approval and selected connector write actions ask for approval. Pods agents can also act without a human, so universal write confirmation is not claimed. Sources: dust:dust:computer, dust:dust:changelog, dust:dust:pods. - stop_control — Can the user stop a running task? [partial]: The 600-AWU root-task checkpoint offers Stop or Continue. A complete general stop/rollback behavior was not tested. Sources: dust:dust:credits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep, dust:dust:computer, dust:dust:changelog, dust:dust:pods, dust:dust:credits #### AlpineAI / SwissGPT 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. ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: supported Dust offers conversation/knowledge APIs, enforceable API-key caps and OAuth MCP access. Availability: generally-available Delivery: native Scope: surfaces=Dust APIs and MCP server; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business conversation API; Enterprise adds Data Source API per pricing; MCP subject to workspace enablement; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. - chat_api — Is there an API for chat and assistants? [supported]: Documented APIs retrieve/create conversations and messages with scoped API keys. Sources: dust:dust:get-conversation, dust:dust:api-keys. - knowledge_api — Can documents be loaded through an API? [supported]: The data-source API upserts documents into scoped data sources. Sources: dust:dust:upsert. - api_governance — Do audit, budgets and model rules apply to API use? [supported]: Per-key caps reject further API usage at the limit. Model overrides obey workspace/tier rules; programmatic usage uses the workspace pool and does not count toward beta pooled group budgets. Sources: dust:dust:api-keys, dust:dust:models, dust:dust:credit-management. - mcp_server — Does the product expose itself to other agents over MCP? [supported]: Global and EU MCP URLs expose authorized Dust knowledge, conversations, agents, files and Pods via OAuth; admins can disable access and control redirects. Sources: dust:dust:mcp-server. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:get-conversation, dust:dust:api-keys, dust:dust:upsert, dust:dust:models, dust:dust:credit-management, dust:dust:mcp-server #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial A separate AlpineAI API platform is advertised. Custom application integrations are explicitly offered under Enterprise from 10 licences; standalone API entitlement remains unknown and new accounts are activated gradually. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI API platform; version=not specified; plan=Enterprise custom application integrations from 10 licences; standalone API tariff/entitlement not established; add_ons=Individually contracted integration; API account activation required; deployment_mode=not specified; region=API portal advertises Swiss processing; endpoint-specific processing and contractual entitlement unverified; os=not specified. Limitations: - Enterprise custom integration is documented; a universal API entitlement across chat licence tiers is not. - No authenticated endpoint documentation, API account, rate-limit data or governance fixture was accessed. - chat_api — Is there an API for chat and assistants? [partial]: The product page describes requests/results through its separate API platform and explicitly places custom integrations in Enterprise. The public API landing page supports REST/SDK positioning but requires sign-in and gradual account activation. Specific chat/assistant endpoints, auth methods, standalone licensing and inclusion in Standard/Premium were not verified. Sources: swissgpt:swissgpt:review2-product, swissgpt:swissgpt:review2-api-access, swissgpt:swissgpt:university. - knowledge_api — Can documents be loaded through an API? [unknown]: No unauthenticated document-ingestion endpoint reference was retrieved from the API portal; naming general integrations is not proof of an ingestion API. - api_governance — Do audit, budgets and model rules apply to API use? [unknown]: The API landing page advertises monitoring of usage and costs, but scope of chat audit, budgets and model rules for API calls was not established without authenticated documentation. - mcp_server — Does the product expose itself to other agents over MCP? [unknown]: No AlpineAI-provided MCP server exposing the product to external agents was documented in the retrieved product or API landing pages. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:review2-product, swissgpt:swissgpt:review2-api-access, swissgpt:swissgpt:university ## 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web, browser extension and Teams access are documented; native desktop/mobile availability remains unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust browser extension; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - web — Is a full web client available? [supported]: Dust provides the hosted web workspace, including the EU region. Sources: dust:dust:pricing, dust:dust:models. - desktop_apps — Windows and macOS apps? [unknown]: Windows and macOS apps? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established. - mobile_apps — iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established. - browser_extension — Is there a browser extension or sidebar? [supported]: The extension guide covers Chrome, Firefox and Chromium browsers. Sources: dust:dust:browser. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established. - client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:models, dust:dust:browser #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The FAQ lists web and iOS/Android access. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client, AlpineAI iOS and Android apps; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland; mobile clients on user devices; os=iOS, Android. Limitations: - Desktop OS support is only package-dependent in AGB 2.1. Browser extension, MDM/Intune deployment and mobile parity are not documented. - web — Is a full web client available? [supported]: Works in Chrome, Firefox, Safari or Edge on internet-connected computers and mobile devices. Sources: swissgpt:swissgpt:product. - desktop_apps — Windows and macOS apps? [unknown]: Windows and macOS apps? Unknown. Desktop OS support is only package-dependent in AGB 2.1. Browser extension, MDM/Intune deployment and mobile parity are not documented. - mobile_apps — iOS and Android apps with SSO? [partial]: iOS and Android apps are advertised; company SSO in those apps was not verified. Sources: swissgpt:swissgpt:product. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. Desktop OS support is only package-dependent in AGB 2.1. Browser extension, MDM/Intune deployment and mobile parity are not documented. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? Unknown. Desktop OS support is only package-dependent in AGB 2.1. Browser extension, MDM/Intune deployment and mobile parity are not documented. - client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? Unknown. Desktop OS support is only package-dependent in AGB 2.1. Browser extension, MDM/Intune deployment and mobile parity are not documented. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial An official Teams integration runs agents in Teams; document connectors do not imply Office add-ins. Availability: generally-available Delivery: official-integration Scope: surfaces=Dust in Microsoft Teams; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [unknown]: Does it work inside Word, Excel and PowerPoint? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately. - outlook — Does it work inside Outlook? [unknown]: Does it work inside Outlook? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately. - teams — Is there a Teams app or bot? [supported]: Dust in Teams has an official integration guide and admin setup. Sources: dust:dust:teams. - google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately. - licence_prerequisites — Which licences or consents are needed? [partial]: The Teams guide requires integration/admin authorization in a Dust workspace. Extra Microsoft/Dust licence charges were not established. Sources: dust:dust:teams. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:teams #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Standard and Premium include an Outlook add-in for reading, drafting and translating email. Availability: generally-available Delivery: official-integration Scope: surfaces=AlpineAI Outlook add-in; version=not specified; plan=Standard and Premium; Enterprise packaging unspecified; add_ons=none stated; deployment_mode=not specified; region=Content processed on AlpineAI hardware in Switzerland; os=not specified. Limitations: - Word, Excel, PowerPoint, Teams and Google application integrations are not specified. Outlook add-in consent and compatibility requirements remain unverified. - word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [unknown]: Does it work inside Word, Excel and PowerPoint? Unknown. Word, Excel, PowerPoint, Teams and Google application integrations are not specified. Outlook add-in consent and compatibility requirements remain unverified. - outlook — Does it work inside Outlook? [supported]: Add-in summarises messages/threads, drafts replies and translates within Outlook. The FAQ describes Get Add-Ins installation. Sources: swissgpt:swissgpt:product. - teams — Is there a Teams app or bot? [unknown]: Is there a Teams app or bot? Unknown. Word, Excel, PowerPoint, Teams and Google application integrations are not specified. Outlook add-in consent and compatibility requirements remain unverified. - google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Unknown. Word, Excel, PowerPoint, Teams and Google application integrations are not specified. Outlook add-in consent and compatibility requirements remain unverified. - licence_prerequisites — Which licences or consents are needed? [partial]: Included with Standard and Premium. Microsoft licence/version prerequisites and tenant consent requirements are not stated. Sources: swissgpt:swissgpt:product. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents can perform language work, but document-translation fidelity and controlled terminology are untested. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - document_translation — Can whole documents be translated with formatting kept? [unknown]: Can whole documents be translated with formatting kept? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established. - translation_engine — Which engine translates? [unknown]: Which engine translates? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established. - glossaries — Are company glossaries supported? [unknown]: Are company glossaries supported? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established. - formality_and_variants — Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Configurable agent instructions and Computer document editing support writing workflows; a separate dedicated proofreading product was not established. Sources: dust:dust:builder, dust:dust:computer. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:computer #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The platform and Outlook add-in offer drafting, summaries and translations. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Whole-document layout preservation, a dedicated translation engine, company glossaries, formality and de-CH controls were not specified or tested. - document_translation — Can whole documents be translated with formatting kept? [unknown]: Can whole documents be translated with formatting kept? Unknown. Whole-document layout preservation, a dedicated translation engine, company glossaries, formality and de-CH controls were not specified or tested. - translation_engine — Which engine translates? [unknown]: Which engine translates? Unknown. Whole-document layout preservation, a dedicated translation engine, company glossaries, formality and de-CH controls were not specified or tested. - glossaries — Are company glossaries supported? [unknown]: Are company glossaries supported? Unknown. Whole-document layout preservation, a dedicated translation engine, company glossaries, formality and de-CH controls were not specified or tested. - formality_and_variants — Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Unknown. Whole-document layout preservation, a dedicated translation engine, company glossaries, formality and de-CH controls were not specified or tested. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: The FAQ advertises drafting and replying to email, summaries and translations into Swiss national languages and English. Proofreading controls are not detailed. Sources: swissgpt:swissgpt:product. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Image tools use reference images and parallel generation; exact model and output-right terms need further evidence. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - image_generation — Can users generate images, with which models? [partial]: Image Generation is a configurable agent capability with SynthID-marked output. The exact current model identifier is not named in the checked guide. Sources: dust:dust:images. - image_editing — Can users edit uploaded images? [partial]: Uploaded and prior generated images can be used as references, with up to 14 references. Precise inpainting/masking controls were not established. Sources: dust:dust:images. - admin_control — Can admins restrict image generation? [partial]: Builders enable image tools in an agent, while group governance controls who creates/publishes agents. A separate organization/group image-off switch was not established. Sources: dust:dust:images, dust:dust:governance. - usage_terms — What usage rights apply to output? [unknown]: What usage rights apply to output? The image guide and legal entry points were checked. Current model identifier, per-image tariff and contractual output usage rights were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:images, dust:dust:governance #### AlpineAI / SwissGPT 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Speech generation and meeting-transcript integrations are documented; live voice and Swiss German recognition remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - dictation — Can users dictate prompts? [unknown]: Can users dictate prompts? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established. - read_aloud — Can answers be read aloud? [partial]: Speech Generator converts written text to MP3 audio with selectable voices/languages; a one-click read-aloud mode for all responses was not established. Sources: dust:dust:speech. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established. - meeting_summaries — Are meetings transcribed and summarised? [supported]: Connected Granola/Fathom/Gong/Praiz transcripts can feed summaries; private Gong transcripts are excluded. This is not a native meeting recorder claim. Sources: dust:dust:meetings. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:speech, dust:dust:meetings #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Premium Listener records audio, transcribes Swiss German and creates minutes or summaries. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client, AlpineAI iOS and Android apps; version=not specified; plan=Premium Listener; Enterprise inclusion per order; add_ons=none stated; deployment_mode=not specified; region=Audio processing on AlpineAI-owned hardware in Switzerland; os=not specified. Limitations: - Read-aloud and live bidirectional voice conversation are undocumented; recognition quality was not independently tested. - dictation — Can users dictate prompts? [partial]: Listener records dictation through the microphone and accepts existing audio files. Direct dictation into a chat prompt was not established. Sources: swissgpt:swissgpt:product. - read_aloud — Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. Read-aloud and live bidirectional voice conversation are undocumented; recognition quality was not independently tested. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. Read-aloud and live bidirectional voice conversation are undocumented; recognition quality was not independently tested. - meeting_summaries — Are meetings transcribed and summarised? [supported]: Advertises complete transcripts and structured minutes, summaries, key facts and to-dos; recordings process on AlpineAI hardware in Switzerland. Sources: swissgpt:swissgpt:product. - swiss_german_speech — Is Swiss German speech recognised? [supported]: Vendor claims Swiss German and other dialect recognition, with transcript output in German, English, French or Italian. Sources: swissgpt:swissgpt:product. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: supported Computer executes analysis and creates real Office files; Frames provide editable interactive output. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No Excel/PowerPoint fixture or artifact fidelity test. File Generation is deprecated in favor of Computer as of October 14, 2026. - data_analysis — Can it analyse spreadsheets with executed code? [supported]: Computer executes code to inspect and transform Excel/CSV, compute every-row results and return edited workbooks. Sources: dust:dust:computer. - charts — Can it produce charts? [supported]: Computer documents chart generation from spreadsheet data and inclusion in reports/decks. Sources: dust:dust:computer. - office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: Computer creates/edits Word, Excel and PowerPoint files and returns downloadable artifacts, with fidelity caveats. Sources: dust:dust:computer. - canvas_editing — Is there a document or canvas editor for iterating on output? [supported]: Frames are persistent interactive content that can be revised through agents and shared. Sources: dust:dust:frames. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:computer, dust:dust:frames #### AlpineAI / SwissGPT 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-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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pods provide shared team conversations, files and tasks; source-sharing effects still need testing. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No cross-group sharing fixture. Do not infer source-ACL propagation from Pod membership. - share_chats — Can chats be shared inside the organisation? [supported]: Pod conversations are visible to all members, who can contribute. Sources: dust:dust:pod-chats. - team_spaces — Are shared projects or workspaces available? [supported]: Open/Restricted Pods group conversations, files and tasks; restricted access is invite-only. Sources: dust:dust:pods. - group_chat — Can several people chat together with the AI? [supported]: Teammates and agents participate in the same Pod thread and can be mentioned. Sources: dust:dust:pod-chats. - share_permission_boundary — Does sharing respect the recipient's access to sources? [partial]: All Pod members read conversation contents. Spaces restrict source/agent use and personal tools act under their user; recipient-safe redaction of previously generated text was not established. Sources: dust:dust:pod-chats, dust:dust:permissions, dust:dust:credentials. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pod-chats, dust:dust:pods, dust:dust:permissions, dust:dust:credentials #### AlpineAI / SwissGPT 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-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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial German and French UI releases are documented alongside English, with remaining English areas. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - ui_languages — Which UI languages are offered? [supported]: October 21, 2026 release adds German; October 16 adds French alongside English US/UK, across product, Frames, extension, Sidekick and Slack/Teams. Sources: dust:dust:changelog. - dach_language_quality — Are German, French and Italian UIs complete and natural? [partial]: Release notes explicitly leave agent/skill names and instructions in English. German/French naturalness and completeness were not observed; Italian UI was not established. Sources: dust:dust:changelog. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? The dated locale announcements were checked; Italian UI and a WCAG conformance statement/report were not established. - admin_ui_languages — Is the admin interface available in German? [partial]: Admins can set a workspace default language. A complete German admin-screen walkthrough was not observed. Sources: dust:dust:changelog. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:changelog #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Terms specify a German and English interface; language quality was not observed. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - No authenticated German/French/Italian UI review, WCAG conformance statement or German admin-interface specification was located. - ui_languages — Which UI languages are offered? [partial]: AGB 2.1 explicitly names German and English UI. Sector pages advertise processing of Swiss national languages and English; that does not establish French/Italian UI coverage. Sources: swissgpt:swissgpt:terms. - dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. No authenticated German/French/Italian UI review, WCAG conformance statement or German admin-interface specification was located. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No authenticated German/French/Italian UI review, WCAG conformance statement or German admin-interface specification was located. - admin_ui_languages — Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. No authenticated German/French/Italian UI review, WCAG conformance statement or German admin-interface specification was located. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:terms ## 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial SAML SSO can be enforced; Business offers it from five seats on demand. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No self-serve SSO login test. - sso_protocols — Which SSO protocols and identity providers work? [supported]: SAML SSO is documented, with Okta, Entra ID and JumpCloud named on pricing. Enterprise marketing also names OIDC; a full provider/protocol matrix was not verified. Sources: dust:dust:sso, dust:dust:pricing, dust:dust:enterprise. - sso_plan — Which plan includes SSO? [supported]: Business pricing lists SSO for 5+ seats on demand; Enterprise includes it. Sources: dust:dust:pricing. - mfa — Can MFA be enforced? [partial]: Enforced SAML routes sign-in through the IdP. Specific MFA enforcement behavior was not tested or established in the checked setup guide. Sources: dust:dust:sso. - conditional_access — Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? SSO and plan guides were checked; conditional-access compatibility and verified-domain capture/migration semantics were not established. - domain_capture — Can the company claim its email domain? [unknown]: Can the company claim its email domain? SSO and plan guides were checked; conditional-access compatibility and verified-domain capture/migration semantics were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:sso, dust:dust:pricing, dust:dust:enterprise #### AlpineAI / SwissGPT 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. ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise SCIM and group roles are documented, with specific annual-seat reclaim behavior. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Enterprise for SCIM; seat-management differences stated; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - scim — Is SCIM provisioning supported? [supported]: SCIM 2.0 creates, updates and deactivates users from an IdP as an Enterprise feature. Sources: dust:dust:provision. - group_sync — Are identity-provider groups synced? [supported]: Provisioned IdP groups govern Space access and can map to Admin/Manager roles. Sources: dust:dust:provision, dust:dust:spaces. - jit_provisioning — Are users created at first login? [unknown]: Are users created at first login? Provisioning and seat docs were checked. First-login JIT creation and complete leaver-data transfer were not established. - deprovisioning — What happens to a removed user's data and shared assets? [partial]: SCIM deactivates users; removal/reassignment affects seats but exact chat/agent/knowledge ownership transfer was not tested. Sources: dust:dust:provision, dust:dust:seats. - seat_assignment — Can admins assign and reclaim seats? [supported]: Admins assign seat types independent of roles. Unassigned members cannot interact with agents; annual seats return to stock, and already-granted credits can persist to period end. Sources: dust:dust:seats. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:provision, dust:dust:spaces, dust:dust:seats #### AlpineAI / SwissGPT 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. ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust separates Admin, Manager, Member and group-manager permissions and supports restricted knowledge spaces. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Admins control all governance; Managers delegate member/group/usage administration; group managers administer selected groups. Sources: dust:dust:governance. - groups — Can permissions be set per group? [supported]: Permissions go to manual or provisioned groups using Everyone, Groups or Admin-only modes. Multiple grants combine additively. Sources: dust:dust:governance. - feature_toggles — Which features can be switched on or off per group? [partial]: Group controls cover agent/skill creation and publishing, automation charging, billing/security and model ceilings. An exhaustive per-feature toggle matrix for uploads/web/images was not established. Sources: dust:dust:governance, dust:dust:tiers. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Restricted Spaces and Pods separate audiences inside a workspace; separate legal/subsidiary tenant boundaries within one contract were not established. Sources: dust:dust:spaces, dust:dust:pods. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:governance, dust:dust:tiers, dust:dust:spaces, dust:dust:pods #### AlpineAI / SwissGPT 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. ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Consumption analytics has detailed attribution and exports without message content. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - adoption_dashboard — Is there an adoption dashboard? [partial]: Pricing lists usage/adoption reporting; the Analytics guide focuses on credit consumption and attribution rather than a complete active-user adoption scorecard. Sources: dust:dust:pricing, dust:dust:analytics. - breakdowns — Can usage be broken down by group, model, feature and assistant? [supported]: Analytics filters/ranks agents, members, groups, models, tools, sources, API keys, skills and Pods. Group attribution may count a member in several groups. Sources: dust:dust:analytics. - export — Can usage data be exported? [supported]: Raw CSV consumption export and API analytics export are documented, with workspace enablement and key-scope restrictions. Sources: dust:dust:analytics. - privacy_modes — Can per-person reporting be limited or pseudonymised? [partial]: Analytics exports omit message content, but contain member/message/conversation identifiers. Pseudonymous or works-council privacy modes were not established. Sources: dust:dust:analytics. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:analytics #### AlpineAI / SwissGPT 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. ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Credit plans offer consumption visibility, member limits and plan-specific pooled budgets, with programmatic exceptions. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Group budgets are beta and exclude programmatic usage. No budget fixture test. - cost_visibility — Can admins see cost or consumption per user and group? [supported]: Analytics and Credits show consumed credits by member, group, model, tool and agent. Credits are not assumed to be invoice currency. Sources: dust:dust:analytics, dust:dust:credit-management. - budgets — Can budgets be set per user or group? [supported]: Members have shared-pool spend limits; beta group budgets require Enterprise Pooled. Programmatic monthly and API-key caps are separate. Sources: dust:dust:credit-management, dust:dust:api-keys. - budget_enforcement — Does reaching a budget alert, block or downgrade? [supported]: Pool limits/group budgets block further requests; an in-progress message can finish above its starting cap. API calls reject at per-key caps. Optional automatic seat upgrades may increase billed subscriptions. Sources: dust:dust:credit-management, dust:dust:api-keys. - chargeback — Can costs be exported per cost centre? [partial]: Consumption CSV includes groups and identifiers, but group attribution can duplicate usage and is not a guaranteed invoice-ready cost-center chargeback. Sources: dust:dust:analytics. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:analytics, dust:dust:credit-management, dust:dust:api-keys #### AlpineAI / SwissGPT 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. ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise has documented event logs and SIEM delivery; content logging and legal hold remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust APIs and MCP server; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Enterprise; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - admin_events — Are admin and security events logged? [supported]: Enterprise Audit Logs record significant admin/security, user, API-key, system and tool events with timestamps, targets and actor metadata. Sources: dust:dust:audit. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [unknown]: Can prompts and answers be retained for compliance, and is it configurable? Audit, analytics and public legal entry points were checked. Prompt/response compliance capture, eDiscovery/legal hold and detailed log-integrity implementation/retention contract were not established. - siem_export — Can logs stream to a SIEM or be exported? [supported]: CSV export and continuous destinations include Datadog, Splunk, S3, GCS and custom HTTPS. Sources: dust:dust:audit. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Audit, analytics and public legal entry points were checked. Prompt/response compliance capture, eDiscovery/legal hold and detailed log-integrity implementation/retention contract were not established. - log_retention — How long are logs kept? [partial]: Enterprise marketing states 365-day audit retention; no underlying report/contract or configurable retention details were retrieved. Sources: dust:dust:enterprise. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:audit, dust:dust:enterprise #### AlpineAI / SwissGPT 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. ### 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. #### Dust 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. #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web search has a sensitive-content consent step; general PII/DLP handling is unverified. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Custom patterns, external DLP integration, detection coverage and filter location are not documented; no AHV/IBAN fixture was used. - pii_detection — Is personal data detected in prompts and files? [partial]: AGB 2.5 says the system can detect potentially sensitive search-query content; it does not specify personal-data types or uploaded-file detection. Sources: swissgpt:swissgpt:terms. - pii_action — Is it redacted, masked, blocked or only warned? [partial]: Detected potentially sensitive web-search content requires renewed user consent before transmission. Redaction or blocking is not established. Sources: swissgpt:swissgpt:terms. - custom_patterns — Can admins add custom patterns or terms? [unknown]: Can admins add custom patterns or terms? Unknown. Custom patterns, external DLP integration, detection coverage and filter location are not documented; no AHV/IBAN fixture was used. - dlp_integration — Does it integrate with an existing DLP product? [unknown]: Does it integrate with an existing DLP product? Unknown. Custom patterns, external DLP integration, detection coverage and filter location are not documented; no AHV/IBAN fixture was used. - filter_location — Where does filtering run? [unknown]: Where does filtering run? Unknown. Custom patterns, external DLP integration, detection coverage and filter location are not documented; no AHV/IBAN fixture was used. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:terms ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents have persistent instructions and workspace governance; broad enforced content-policy administration is unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - org_instructions — Can admins set organisation-wide instructions? [partial]: Admins/builders configure agent instructions; an enforced single organization-wide instruction applied to every agent/message was not established. Sources: dust:dust:builder, dust:dust:governance. - usage_notice — Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? Agent, governance and security pages were checked. Mandatory usage-policy acknowledgement and administrator policy-violation reporting were not established. - content_filters — Are content filters configurable? [partial]: Image Generation documents NSFW/celebrity safety filtering. Custom organization-wide topic/content rules were not established. Sources: dust:dust:images. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Agent, governance and security pages were checked. Mandatory usage-policy acknowledgement and administrator policy-violation reporting were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:governance, dust:dust:images #### AlpineAI / SwissGPT 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. ## 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial EU workspace and EU model controls are distinct from general hosting and global subprocessing. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - storage_region — Where are chats, files and indexes stored? [partial]: Pricing/security advertise EU or US workspace hosting. Exact cloud provider, storage country and index location were not established. Sources: dust:dust:pricing, dust:dust:security. - inference_region — Where do model calls run, per provider? [supported]: EU credit-priced workspaces using Dust-hosted models can enable EU-hosted models only after all active agents comply. BYOK is outside this setting; not every model is eligible. Sources: dust:dust:eu-models. - backups_logs_region — Where are backups, logs and telemetry? [unknown]: Where are backups, logs and telemetry? Hosting, EU-model and privacy pages were checked. Backup/log/telemetry countries, customer-content support-access geography and Swiss hosting were not established. - support_access_region — From where can vendor staff access data? [partial]: The controller privacy policy permits non-EEA access/processing including the US; it does not establish customer-content support access by staff country. Sources: dust:dust:privacy. - swiss_hosting — Is Swiss hosting available? [unknown]: Is Swiss hosting available? Hosting, EU-model and privacy pages were checked. Backup/log/telemetry countries, customer-content support-access geography and Swiss hosting were not established. - residency_plan — Which plan or option provides residency? [supported]: Business and Enterprise list EU/US residency; EU-only model restrictions additionally require EU region and credit pricing with Dust model hosting. Sources: dust:dust:pricing, dust:dust:eu-models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:security, dust:dust:eu-models, dust:dust:privacy #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Swiss RIZ application hosting is consistently described. Green/RZO Swiss inference is a vendor security-page statement; a current contracted inference-site schedule is unverified because the July DPA does not list RZO. Storage, inference, support and optional search are scoped separately. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client, AlpineAI API platform; version=Public infrastructure page and DPA Annex 3 dated 10 July 2026; no tenant contract inspected; plan=Current AlpineAI sector offer; contract-specific residency and secret-data supplement conditional on signature; add_ons=none stated; deployment_mode=not specified; region=Advertised Swiss application hosting; current contracted inference map unverified; DPA CH/EEA with conditional third-country processing and optional external search; os=not specified. Limitations: - RZO is described as colocation, not as a foreign model API. Its absence from the July annex is not evidence of overseas inference or unauthorised processing. - The currently contracted complete inference-site list, per-index/log/telemetry locations and exhaustive staff access countries remain unknown. - storage_region — Where are chats, files and indexes stored? [partial]: The security page describes application/data storage on AlpineAI hardware at two Swiss RIZ sites. July DPA Annex 3 independently lists RIZ CH for platform hosting and support. Separate per-index/log topology and a tenant-specific deployment schedule were not established. Sources: swissgpt:swissgpt:review2-security, swissgpt:swissgpt:review2-dpa. - inference_region — Where do model calls run, per provider? [unknown]: The security page names Swiss Green and RZO GPU colocation on AlpineAI-owned/operated hardware without logical access by site operators. July DPA Annex 3 names Green and expressly describes pure colocation, but omits RZO. No newer public annex or contract-specific RZO authorisation was retrieved. The currently contracted complete inference-site map is therefore unknown; the marketing statement is not a verified current contract commitment. - backups_logs_region — Where are backups, logs and telemetry? [partial]: July DPA Annex 3 lists cloudscale.ch CH for backup; Annex 2 describes daily offsite backups. This dated schedule does not establish every current log/telemetry or backup location. Sources: swissgpt:swissgpt:review2-dpa. - support_access_region — From where can vendor staff access data? [partial]: The dated annex assigns RIZ CH to customer support and EU Atlassian/Custify to helpdesk/account functions. Physical staff access countries are not fully mapped. A separately signed secret-data supplement requires Swiss services where secret data is in plaintext. Sources: swissgpt:swissgpt:review2-dpa, swissgpt:swissgpt:secrecy. - swiss_hosting — Is Swiss hosting available? [partial]: Swiss application hosting at RIZ is supported by both public sources. The full current inference-site inventory is withheld pending a current applicable schedule, so this is not an all-processing CH-residency assurance. Sources: swissgpt:swissgpt:review2-security, swissgpt:swissgpt:review2-dpa. - residency_plan — Which plan or option provides residency? [partial]: DPA 1.5 permits CH/EEA processing with conditional third-country safeguards. Optional Brave search is separately listed with US processing. The secret-data supplement, only when signed and applicable, narrows plaintext services including APIs to Switzerland. A current tenant-specific inference schedule is still missing. Sources: swissgpt:swissgpt:review2-dpa, swissgpt:swissgpt:secrecy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:review2-security, swissgpt:swissgpt:review2-dpa, swissgpt:swissgpt:secrecy ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Hosted Business and Enterprise single-tenant offers are public; supported customer-operated whole-platform modes are unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust Enterprise single-tenant deployment; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=not specified; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - multi_tenant_saas — Is a shared SaaS offered? [partial]: Business is a self-serve hosted workspace; exact shared-infrastructure isolation architecture is not documented in the checked pages. Sources: dust:dust:pricing, dust:dust:privacy. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [supported]: Enterprise pricing advertises single-tenant deployment. Numerical seat/spend minimum, supported countries and operating terms were not established. Sources: dust:dust:pricing. - customer_cloud — Can it run in the customer's own cloud account, from what size? [unknown]: Can it run in the customer's own cloud account, from what size? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment. - on_premise — Can the whole platform run on customer infrastructure, from what size? [unknown]: Can the whole platform run on customer infrastructure, from what size? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment. - air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment. - mode_feature_gaps — Which features are missing outside SaaS? [partial]: Business/Enterprise packaging differs in connectors, MCP, Spaces, APIs and governance. No customer-operated hosting feature-parity contract was established. Sources: dust:dust:pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:privacy #### AlpineAI / SwissGPT 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. ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust publishes no-training and provider-retention claims; the customer DPA was not retrieved. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Controller privacy-policy scope is distinct from processor DPA coverage. - vendor_training — Does the vendor train on customer content? [partial]: The security page claims customer data is never used for model training. This remains vendor-claimed because no customer DPA/contract clause was retrieved. Sources: dust:dust:security. - provider_training — Do model providers train on it under this product's contracts? [partial]: The privacy policy names OpenAI, Anthropic, Mistral, Google and Fireworks as prohibited from training on customer/personal content; BYOK arrangements need separate confirmation. Sources: dust:dust:training-policy. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [partial]: The policy states providers do not log Customer Content for human review or save it to disk. Exception/abuse-retention periods were not established from customer contracts. Sources: dust:dust:training-policy. - zero_retention — Is zero data retention available, and on which plan? [partial]: Security and privacy pages assert provider zero retention, but applicable plan/model exceptions were not contract-verified. Sources: dust:dust:security, dust:dust:training-policy. - human_review — Can provider staff review content? [partial]: The published policy says listed providers do not log Customer Content for human review. This is a vendor assertion, not an independently reviewed model-provider contract. Sources: dust:dust:training-policy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:training-policy #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The terms prohibit model training on customer inputs. API zero retention has a narrow signed secrecy-agreement scope. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client, AlpineAI API platform; version=not specified; plan=Current hosted plans; zero retention only AI API services under signed secret-data supplement; add_ons=Signed supplementary agreement for legally secret data, where applicable; deployment_mode=not specified; region=CH for plaintext secret-data services; general DPA CH/EEA with conditional third countries; os=not specified. Limitations: - Ordinary-chat/provider retention and general staff-review practice outside the signed secret-data scope are not documented. DPA anonymised-data use must be read alongside the narrower no-training clause. - vendor_training — Does the vendor train on customer content? [supported]: AGB 4.4 says customer inputs do not feed back into language-model development. DPA 2.4 separately permits anonymisation and use for service/product development; this is not a blanket prohibition on every secondary use. Sources: swissgpt:swissgpt:terms, swissgpt:swissgpt:dpa. - provider_training — Do model providers train on it under this product's contracts? [partial]: Vendor says models run on AlpineAI hardware without foreign model APIs; a separate third-party model-provider training contract is not established. Sources: swissgpt:swissgpt:product. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [partial]: Signed secrecy agreement forbids storing/logging AI API input and output for secret data. Ordinary web-chat and general API retention periods are unspecified. Sources: swissgpt:swissgpt:secrecy. - zero_retention — Is zero data retention available, and on which plan? [supported]: Available contractually for AI API services processing legally secret data when the supplementary agreement is signed. It is not a general chat-history promise. Sources: swissgpt:swissgpt:secrecy. - human_review — Can provider staff review content? [supported]: For secret data under the signed supplement, plaintext access needs individual approval, unavoidable BCM emergency or a binding Swiss order; staff abuse monitoring with plaintext access is forbidden. Sources: swissgpt:swissgpt:secrecy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:terms, swissgpt:swissgpt:dpa, swissgpt:swissgpt:product, swissgpt:swissgpt:secrecy ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Some user deletion and memory retention behavior is documented; tenant-wide retention schedules remain open. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - default_retention — What is retained and for how long by default? [partial]: Agent memories persist until manually deleted. This does not define default retention for all conversations, files, indexes or logs. Sources: dust:dust:memory. - admin_retention — Can admins set retention periods? [partial]: Enterprise pricing offers custom data retention; periods, deletion mechanics and exceptions were not retrieved. Sources: dust:dust:pricing. - user_deletion — Can users delete their chats and files permanently? [partial]: Users can delete conversations and agent memories. Backup erasure timing and all attached-file deletion behavior were not established. Sources: dust:dust:delete-chat, dust:dust:memory. - contract_end_deletion — What is deleted at contract end, and when? [unknown]: What is deleted at contract end, and when? Conversation/memory docs, Enterprise pricing and unreadable legal entry points were checked. Contract-end erasure timing and complete storage/index/log retention defaults remain unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:memory, dust:dust:pricing, dust:dust:delete-chat #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The DPA requires deletion after contract end with a backup-cycle exception. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Default chat/file/index/log periods, customer retention settings, permanent user deletion and the backup-cycle deadline are not specified. - default_retention — What is retained and for how long by default? [unknown]: What is retained and for how long by default? Unknown. Default chat/file/index/log periods, customer retention settings, permanent user deletion and the backup-cycle deadline are not specified. - admin_retention — Can admins set retention periods? [unknown]: Can admins set retention periods? Unknown. Default chat/file/index/log periods, customer retention settings, permanent user deletion and the backup-cycle deadline are not specified. - user_deletion — Can users delete their chats and files permanently? [unknown]: Can users delete their chats and files permanently? Unknown. Default chat/file/index/log periods, customer retention settings, permanent user deletion and the backup-cycle deadline are not specified. - contract_end_deletion — What is deleted at contract end, and when? [partial]: DPA 9.1 requires deletion of provided customer data on termination. Backup copies delete on restoration and ultimately as backup cycles expire; no cycle duration is given. AGB 7.5 offers written confirmation on request with legal-retention exceptions. Sources: swissgpt:swissgpt:dpa, swissgpt:swissgpt:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:dpa, swissgpt:swissgpt:terms ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust identifies a French operating entity; customer subprocessor inventory and notice rules remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - subprocessor_list — Is a dated sub-processor list published? [unknown]: Is a dated sub-processor list published? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established. - subprocessor_countries — Which countries do sub-processors operate in? [unknown]: Which countries do sub-processors operate in? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established. - change_notification — Are customers notified of sub-processor changes? [unknown]: Are customers notified of sub-processor changes? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: The public policy identifies Permutation Labs at a Paris, France address. A separate parent company or controlling entity was not established. Sources: dust:dust:privacy. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [partial]: For its controller processing, the privacy policy describes adequacy or EU SCC safeguards for non-EU transfers, including the US. Customer processor transfer terms were not retrieved. Sources: dust:dust:privacy. - government_access_policy — Is there a published government-access or transparency policy? [partial]: The controller policy allows legally required disclosure to authorities; a dedicated government-request transparency policy for customer content was not established. Sources: dust:dust:privacy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:privacy #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial A public July 2026 DPA annex lists operational suppliers and contract notification/transfer terms. It is a dated source, not proof of the complete current provider list: RZO appears only on the security page and its current contractual status remains unknown. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client, AlpineAI API platform; version=DPA Annex 3 dated 10 July 2026; re-retrieved 21 October 2026; plan=AlpineAI platform contracts; current tenant-specific supplier schedule not inspected; add_ons=none stated; deployment_mode=not specified; region=Dated annex CH/EU/US supplier locations; current complete country/supplier schedule unverified; os=not specified. Limitations: - No current complete provider/country schedule or RZO-specific authorisation was retrieved; no inference is made that RZO is approved, unauthorised or a separate model provider. - Ultimate ownership and supplier-specific US transfer instruments remain unknown. - subprocessor_list — Is a dated sub-processor list published? [partial]: A public Annex 3 dated 10 July 2026 is downloadable through /avv/. It includes RIZ hosting/support and Green colocation. The security page additionally names RZO. No updated public annex, RZO approval notice or tenant-specific schedule was obtained, so completeness/current applicability is unknown. Sources: swissgpt:swissgpt:review2-dpa, swissgpt:swissgpt:review2-security. - subprocessor_countries — Which countries do sub-processors operate in? [partial]: The dated annex lists CH data locations for RIZ, Green, cloudscale, accounting and IT operations; EU for helpdesk/payments/customer success; US for CRM and opt-in Brave search. Green is described as rack/power/network colocation without logical access, not model-provider API processing. These are the annex entries, not an exhaustive current content-processing country map. Sources: swissgpt:swissgpt:review2-dpa. - change_notification — Are customers notified of sub-processor changes? [supported]: DPA 7.3 requires text notice of intended additions/replacements and gives 14 days for an objection supported by an important reason. No customer-specific change notice was inspected. Sources: swissgpt:swissgpt:review2-dpa. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: The contracting entity is AlpineAI AG in Davos, Switzerland; ultimate parent/beneficial-owner jurisdiction was not established. Sources: swissgpt:swissgpt:imprint, swissgpt:swissgpt:terms. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [partial]: DPA 1.5 conditions third-country processing on prior written notice and adequate safeguards such as SCCs or adequacy. It does not map a particular transfer instrument to each US supplier. Sources: swissgpt:swissgpt:review2-dpa. - government_access_policy — Is there a published government-access or transparency policy? [supported]: DPA 2.1 requires notice of legally mandated processing unless prohibited. The separately signed secret-data supplement adds Swiss-order notice, challenge assistance and minimal disclosure, within its Swiss secret-data scope. Sources: swissgpt:swissgpt:review2-dpa, swissgpt:swissgpt:secrecy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:review2-dpa, swissgpt:swissgpt:review2-security, swissgpt:swissgpt:imprint, swissgpt:swissgpt:terms, swissgpt:swissgpt:secrecy ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise offers custom MSA/DPA terms, while the underlying legal materials were inaccessible. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - dpa — Is a DPA available, and is it negotiable? [partial]: Enterprise pricing explicitly offers custom MSA/DPA terms. The form, sign-up incorporation and negotiability boundaries were not inspected. Sources: dust:dust:pricing. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: Marketing and privacy materials reference GDPR; explicit Swiss revDSG coverage in the customer DPA was not established. Sources: dust:dust:security, dust:dust:privacy. - governing_law — Which law and court govern the contract? [unknown]: Which law and court govern the contract? Official Terms & Policies redirects to a Notion page that returned no readable terms; trust.dust.com also exposed no report text. Governing law/court and EU AI Act technical/role materials were not established. - ai_act_materials — Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? Official Terms & Policies redirects to a Notion page that returned no readable terms; trust.dust.com also exposed no report text. Governing law/court and EU AI Act technical/role materials were not established. - sector_materials — Are FINMA or other sector materials provided? [partial]: Security marketing says the service enables HIPAA compliance. A BAA, FINMA or banking-secrecy outsourcing pack was not retrieved. Sources: dust:dust:security. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:security, dust:dust:privacy #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public DPA and secrecy supplement address Swiss data protection and professional/official secrecy. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - DPA negotiability, EU AI Act provider/deployer documents and a FINMA-specific pack are not provided in the reviewed public materials. - dpa — Is a DPA available, and is it negotiable? [partial]: A public DPA applies to individuals without AlpineAI signature; companies may obtain a countersigned copy. Negotiation rights are not established. Sources: swissgpt:swissgpt:dpa. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [supported]: DPA expressly cites Art. 9 Swiss DSG and Art. 28 GDPR and defines controller/processor roles. Sources: swissgpt:swissgpt:dpa. - governing_law — Which law and court govern the contract? [supported]: DPA 11.4 specifies Swiss law and exclusive Zürich jurisdiction; AGB 11.4 preserves AlpineAI rights to sue elsewhere. Sources: swissgpt:swissgpt:dpa, swissgpt:swissgpt:terms. - ai_act_materials — Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? Unknown. DPA negotiability, EU AI Act provider/deployer documents and a FINMA-specific pack are not provided in the reviewed public materials. - sector_materials — Are FINMA or other sector materials provided? [partial]: Public signed supplement covers legally secret data including official/professional secrecy, CH plaintext services and annual assurance evidence. No FINMA-specific outsourcing dossier was located. Sources: swissgpt:swissgpt:secrecy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:dpa, swissgpt:swissgpt:terms, swissgpt:swissgpt:secrecy ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial SOC 2 Type II is claimed publicly, without a verified report or certificate. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - iso_27001 — ISO 27001 with scope and validity? [unknown]: ISO 27001 with scope and validity? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified. - soc2 — SOC 2 type, period and covered service? [partial]: Dust security/pricing claim SOC 2 Type II. Auditor, reporting period and exact service scope were not verified. Sources: dust:dust:security, dust:dust:pricing. - c5 — BSI C5 attestation? [unknown]: BSI C5 attestation? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified. - other_certifications — Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified. - report_access — How can customers obtain reports? [partial]: The security page directs customers to trust.dust.com; underlying reports were not accessible in this public source pass. Sources: dust:dust:security. - pentest — Are independent penetration test summaries available? [unknown]: Are independent penetration test summaries available? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:pricing #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial AlpineAI claims ISO 27001:2022 and VDSZ issued by SQS; certificates were not inspected. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - No issuer certificate or full report was obtained. ISO/VDSZ validity and scope, SOC 2 type/period, C5 and independent penetration-test summary remain unverified. - iso_27001 — ISO 27001 with scope and validity? [partial]: Vendor identifies AlpineAI AG, SQS and ISO 27001:2022. Certificate scope and validity were not retrieved, so this remains vendor-claimed. Sources: swissgpt:swissgpt:security. - soc2 — SOC 2 type, period and covered service? [unknown]: SOC 2 type, period and covered service? Unknown. No issuer certificate or full report was obtained. ISO/VDSZ validity and scope, SOC 2 type/period, C5 and independent penetration-test summary remain unverified. - c5 — BSI C5 attestation? [unknown]: BSI C5 attestation? Unknown. No issuer certificate or full report was obtained. ISO/VDSZ validity and scope, SOC 2 type/period, C5 and independent penetration-test summary remain unverified. - other_certifications — Which other certificates (27701, 42001, TISAX)? [partial]: Vendor claims VDSZ, issued by SQS. No certificate number, scope or expiry was retrieved. Sources: swissgpt:swissgpt:security. - report_access — How can customers obtain reports? [supported]: DPA 6.1 permits documentary assurance such as ISO records/internal audits; signed secret-data supplement promises annual certification/report covering the processing without extra charge. Sources: swissgpt:swissgpt:dpa, swissgpt:swissgpt:secrecy. - pentest — Are independent penetration test summaries available? [partial]: DPA Annex 2 promises regular penetration testing; independence and a public summary are not established. Sources: swissgpt:swissgpt:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:security, swissgpt:swissgpt:dpa, swissgpt:swissgpt:secrecy ### 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). #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust claims AES-256/TLS and advertises Enterprise single tenancy; customer key custody is unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - encryption_at_rest — Is data encrypted at rest? [supported]: The security page states AES-256 at rest and TLS in transit; this is a vendor claim. Sources: dust:dust:security. - customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Security, pricing and network/MCP docs were checked. Customer-managed/held data-encryption keys and key-location guarantees were not established. Provider API BYOK is not encryption-key custody. - private_networking — Is private connectivity or IP restriction available? [partial]: Custom MCP servers can restrict access and use documented static egress on verified domains. This is tool connectivity, not proof of private connectivity to the whole service. Sources: dust:dust:tools. - tenant_isolation — How are customers separated in shared SaaS? [partial]: Enterprise offers single tenancy; shared Business tenancy and lower-level isolation mechanics were not established. Sources: dust:dust:pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:tools, dust:dust:pricing #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The vendor describes AES-256 at rest, TLS in transit and isolation on its own hardware. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Customer-managed or customer-held keys, key location, customer private connectivity and technical tenant-isolation model remain unspecified. - encryption_at_rest — Is data encrypted at rest? [supported]: Security page names AES-256 at rest and TLS between clients and platform; DPA Annex 2 requires encryption. Sources: swissgpt:swissgpt:security, swissgpt:swissgpt:dpa. - customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Unknown. Customer-managed or customer-held keys, key location, customer private connectivity and technical tenant-isolation model remain unspecified. - private_networking — Is private connectivity or IP restriction available? [partial]: GPU partners are described as VPN-only infrastructure. A customer Private Link, VPN or IP allow-list option is not established. Sources: swissgpt:swissgpt:security. - tenant_isolation — How are customers separated in shared SaaS? [partial]: Vendor claims isolated/private-cloud environments and least-privilege RBAC. Exact shared-SaaS tenant separation and single-tenancy guarantees are not documented. Sources: swissgpt:swissgpt:security. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:security, swissgpt:swissgpt:dpa ### DATA-09: Professional secrecy Judgment rule: For professional secrecy holders (Berufsgeheimnisträger: lawyers, doctors, auditors, tax advisers) under § 203 StGB (DE) and Art. 321 StGB (CH), record whether the vendor signs a contractual secrecy undertaking or a § 203 agreement that binds its staff and its sub-processors; whether this comes as a dedicated offering or a paid add-on, and on which plan; who can access content in plain text (vendor staff, sub-processors, model providers); and the documentation provided. A DPA or a no-training clause alone is not a secrecy undertaking. Banking secrecy and FINMA outsourcing belong to DATA-06, not here. Record contract facts, not a legal assessment. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public personnel/model handling statements exist; an explicit professional-secrecy contract and subprocessor flow-down remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Dust Business/Enterprise public policy; Enterprise and BYOK routes differ; add_ons=none stated; deployment_mode=multi-tenant-saas; region=EU/US storage and provider routes; no DE/CH-specific secrecy contract verified; os=not specified. Limitations: - No-training, ZDR marketing/policy assertions, EU hosting and a general privacy policy do not establish a professional-secrecy undertaking. - No legal suitability or compliance conclusion. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: The public security and platform privacy pages do not establish a signed §203 StGB/Art321 StGB professional-secrecy undertaking covering Dust staff. The Terms/Policies link did not expose readable contractual text in this pass. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The privacy policy describes service-provider data-protection agreements and model no-training/retention conditions, but no dedicated professional-secrecy undertaking or its binding subprocessor flow-down was retrieved. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: No publicly documented German/Swiss professional-secrecy-specific plan or paid add-on was established. Enterprise single-tenancy/EU model options are not treated as such a contractual undertaking. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: The platform privacy policy limits personnel access to authorized staff and says customer context is processed by selected foundation-model providers; it asserts no provider disk retention/human-review logging. This vendor statement does not establish the complete customer-content plaintext access matrix, support countries, private contracts or every BYOK/MCP/tool route. Sources: dust:dust:privacy, dust:dust:training-policy, dust:dust:eu-models. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Reviewed public security, privacy, EU-hosted model documentation and Enterprise plan scope plus targeted first-party secrecy search. Trust Center content was not available and Terms/Policies routed to unreadable external content. No public §203/Art321 template or professional-body guidance was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:privacy, dust:dust:training-policy, dust:dust:eu-models #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial AlpineAI publishes a separate bilateral undertaking for Swiss official, professional and other statutory secret data. It binds staff and subcontractors, restricts plaintext access and requires Swiss plaintext services when signed. Plan eligibility, any supplement fee and German § 203 coverage remain unverified. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client, AlpineAI API platform; version=Supplement printed 30 March 2026; plan=AlpineAI platform under a signed main contract and supplementary secrecy agreement; eligible plan tiers unpublished; add_ons=Signed supplementary secrecy agreement; price unpublished; deployment_mode=not specified; region=Swiss statutory secrecy; services exposing secret data in plaintext, including APIs, exclusively in Switzerland; os=not specified. Limitations: - The supplement is conditional on both signatures and processing Swiss legally secret data. Its Swiss Art. 320 ff. reference is not evidence of a German § 203 agreement or a legal suitability assessment for a particular profession. - Plan eligibility, any supplement fee, executed customer agreements and the actual downstream staff/subcontractor agreements remain unverified. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [supported]: The public two-party signature template supplements the platform main contract and DPA. It takes effect on the last signature and only while the customer processes data subject to Swiss official, professional or other statutory secrecy (example: Art. 320 ff. Swiss StGB). Section 3 requires equivalent contractual obligations for AlpineAI staff who may access plaintext. This establishes a published undertaking for signature, not an inspected executed customer agreement or an express German § 203 instrument. Sources: swissgpt:swissgpt:secrecy. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [supported]: Section 3 requires AlpineAI to impose at least equivalent contractual obligations on its subcontractors and staff who may access secret data in plaintext. The DPA safeguards also apply to secret data, with the stronger secrecy supplement taking priority. Actual downstream signed agreements were not public and were not inspected. Sources: swissgpt:swissgpt:secrecy. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [partial]: The security page offers corporate customers an additional secrecy agreement; the public template is separate from the main contract and DPA and requires both parties to sign. No named eligible package, paid add-on tariff or general supplement fee was established. The annual assurance evidence is promised without extra cost, which does not establish that the agreement itself is free. Sources: swissgpt:swissgpt:security, swissgpt:swissgpt:secrecy. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [supported]: Under the signed supplement, AlpineAI and subcontractor staff may access plaintext only on a need-to-know basis plus individual prior customer approval, an unavoidable urgent business-continuity emergency, or a binding Swiss authority order. AlpineAI must take reasonable measures to prevent third-party plaintext access. AI API inputs and outputs must not be stored or logged, human abuse monitoring with plaintext access is prohibited, and plaintext services including APIs must remain in Switzerland. The security page separately says AlpineAI operates the models and colocation providers have no logical access to systems or data. These are contract terms and vendor disclosures, not a hands-on verification of every data flow. Sources: swissgpt:swissgpt:secrecy, swissgpt:swissgpt:security. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [supported]: A public two-page contract template, printed 30 March 2026, sets scope, precedence, secrecy duties, staff/subcontractor flow-down, plaintext access, Swiss processing, API retention and signature blocks. Section 3 also promises annual assurance evidence covering secret-data processing at no extra cost and a customer audit right at customer expense. The security page explains the supplementary agreement. No executed customer contract was inspected. Sources: swissgpt:swissgpt:secrecy, swissgpt:swissgpt:security. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:secrecy, swissgpt:swissgpt:security ## 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business seat prices are public; only the documented prepaid route is described here, while conflicting Business overage eligibility remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business Free/Pro/Max seat list pricing; Enterprise quoted pool and programmatic contracts are separate; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - Do not present Business PAYG as established; retain list seat prices separately from the unresolved overage route. - pricing_unit — What is the pricing unit? [partial]: Business publishes per-seat subscriptions and included credits. Detailed Credit management describes prepaid Business top-ups and Enterprise PAYG; pricing FAQ separately describes enabled Business workspace overage, so Business post-allocation billing eligibility is unverified. Sources: dust:dust:pricing, dust:dust:credit-management. - list_prices — What are list prices per plan, with date and currency? [supported]: As retrieved 2026-10-21, ex-VAT Business Free is EUR 0; Pro EUR 30/month or EUR 24/month annually; Max EUR 150/month or EUR 120/month annually. Enterprise is quote-only. Sources: dust:dust:pricing. - included_usage — What usage is included? [supported]: Free has 500 lifetime credits, Pro 8,000/month and Max 40,000/month. Monthly credits do not roll over; Workspace seats draw from a contracted pool. Sources: dust:dust:credits, dust:dust:seats. - add_ons — Which features cost extra? [partial]: Business limits include three connectors, five remote MCP servers and five Spaces. Enterprise adds unlimited connector/MCP packaging, SCIM, audit, retention and support. Individual add-on tariffs are not published. Sources: dust:dust:pricing. - overage — What do usage beyond limits and premium models cost? [unknown]: Effective Business post-allocation billing is unknown: current pricing FAQ allows Pro/Max workspace overage, while Credit management reserves PAYG for Enterprise and describes prepaid Business top-ups. The USD0.01/credit Business programmatic rate does not resolve whether interactive overage is PAYG or prepaid. No account/contract test resolved this. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:credit-management, dust:dust:credits, dust:dust:seats #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Prices differ by sector and billing period; Enterprise is quoted from 10 licences. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Enterprise rates, VAT treatment, university monthly-toggle verification, model/search quotas, overage prices and integration charges are not established. Do not treat the annual default shown by text extraction as monthly billing. - pricing_unit — What is the pricing unit? [supported]: Standard/Premium price per individual user licence. Enterprise package starts at 10 licences. Sources: swissgpt:swissgpt:public-pricing, swissgpt:swissgpt:health-pricing, swissgpt:swissgpt:university. - list_prices — What are list prices per plan, with date and currency? [partial]: As retrieved 2026-10-21: administration Standard/Premium CHF 79/89 per user/month with monthly billing, CHF 74/80 per month with annual billing. Healthcare CHF 89/99 monthly or CHF 80/90 per month annual. University page displays annual CHF 74/80; monthly amounts were not independently toggled. Tax inclusion is not stated clearly, so no ex-VAT conversion is asserted. Sources: swissgpt:swissgpt:public-pricing, swissgpt:swissgpt:health-pricing, swissgpt:swissgpt:university. - included_usage — What usage is included? [partial]: Standard has chat/search, uploads, Outlook and 2 assistants; Premium adds Listener, prebuilt assistants and 5 assistants, each listed at 50 documents / max. 100 MB. General inference/search token allowances are not published. Sources: swissgpt:swissgpt:university. - add_ons — Which features cost extra? [partial]: Premium adds Listener and preconfigured assistants; Enterprise covers custom integrations. AGB 2.3 permits charges for new major functionality; numeric integration/service fees are unspecified. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:terms. - overage — What do usage beyond limits and premium models cost? [unknown]: What do usage beyond limits and premium models cost? Unknown. Enterprise rates, VAT treatment, university monthly-toggle verification, model/search quotas, overage prices and integration charges are not established. Do not treat the annual default shown by text extraction as monthly billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:public-pricing, swissgpt:swissgpt:health-pricing, swissgpt:swissgpt:university, swissgpt:swissgpt:terms ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial ALM-14 shared cost assumptions v1.4, 2026-10-21 apply; all three target seat counts require unpriced Enterprise terms. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - cost_200 — Year-one cost at 200 users? [unknown]: Year-one cost at 200 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope. - cost_1000 — Year-one cost at 1,000 users? [unknown]: Year-one cost at 1,000 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope. - cost_5000 — Year-one cost at 5,000 users? [unknown]: Year-one cost at 5,000 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope. - variable_share — Which part depends on usage? [supported]: Consumption adds token and action credits, including sub-agent work. Programmatic use and Enterprise PAYG draw from workspace pools separately from personal seat allocations. Sources: dust:dust:credits, dust:dust:credit-management. - unknown_parts — Which costs could not be priced? [supported]: Business is scoped to 100 people, so 200/1,000/5,000 seat Enterprise fees, committed pool and PAYG tariffs are unknown. The default Standard auto list is published, but a complete token-to-credit tariff is not, so no proxy replaces vendor-billed usage. Sources: dust:dust:pricing, dust:dust:models, dust:dust:credits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:credits, dust:dust:credit-management, dust:dust:pricing, dust:dust:models, dust:dust:fx-ecb #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial ALM-14 shared cost assumptions v1.4, 2026-10-21. The required 200, 1,000 and 5,000-seat annual scenarios cannot be priced from the public individual plans. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_200 — Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_1000 — Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_5000 — Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - variable_share — Which part depends on usage? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - unknown_parts — Which costs could not be priced? [supported]: Enterprise applies from 10 licences and is quote-only; fixed package, usage, integrations, service charges and tax treatment remain unknown. No sales quote was requested. Sources: swissgpt:swissgpt:university. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:ecb-fx ### VEN-03: Evaluation access Judgment rule: Distinguish free tier, self-serve trial, sales-led pilot, paid proof of concept and open-source self-install. Record card requirement, duration, seat limit, and which features (SSO, connectors, admin) the trial includes. Map which shared scenarios can be run without sales approval. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial A limited Business free option enables self-serve evaluation; Enterprise features remain contract-scoped. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - free_tier — Is there a free tier for business use? [supported]: Business free supports up to five members with 500 lifetime credits per Free seat. Credits do not reset and a user cannot return to Free after upgrading. Sources: dust:dust:seats. - self_serve_trial — Is a self-serve business trial available? [partial]: The public site offers self-serve free workspace access, not a documented time-limited fully featured Enterprise trial. No card requirement was established. Sources: dust:dust:pricing, dust:dust:seats. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Business lists up to three connectors/five Spaces/five remote MCP servers and SSO at 5+ seats on demand. SCIM, audit and custom retention are Enterprise. Sources: dust:dust:pricing. - sales_gate — Does meaningful evaluation require sales contact? [supported]: Enterprise terms, pooled credits, advanced governance and support are sales-led; a small-team free evaluation is self-serve. Sources: dust:dust:pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:seats, dust:dust:pricing #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Sector pages offer online free tests; Enterprise evaluation scope is not published. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - A permanent business free tier, trial duration/card requirements, Enterprise SSO/admin/connector coverage and fixture access are not established. - free_tier — Is there a free tier for business use? [unknown]: Is there a free tier for business use? Unknown. A permanent business free tier, trial duration/card requirements, Enterprise SSO/admin/connector coverage and fixture access are not established. - self_serve_trial — Is a self-serve business trial available? [partial]: Standard/Premium pages link free testing through Stripe and AGB 3.1 allows self-registration. Trial duration, card requirement and quotas were not verified. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:terms. - trial_scope — Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? Unknown. A permanent business free tier, trial duration/card requirements, Enterprise SSO/admin/connector coverage and fixture access are not established. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Individual plans can be purchased by self-registration; the Enterprise integration offer routes to consultation. No account or sales contact was used. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:terms ### VEN-04: Contract terms and pricing transparency Judgment rule: Record minimum seats or commitment, contract length, monthly versus annual billing, price-change rules, cancellation and downgrade terms, and invoicing in CHF/EUR. Classify pricing as transparent, partially specified, quote-only or unknown, naming the missing fields. Quote-only pricing is a disclosed constraint. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business monthly and annual subscriptions are public; Enterprise seats are annual and prices contractual. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - minimum_commitment — What seat or spend minimum applies? [partial]: The free option has up to five members and Business targets up to 100 people; Enterprise numerical seat/spend minimum was not established. Sources: dust:dust:pricing, dust:dust:seats. - contract_length — What contract lengths are offered? [supported]: Business offers monthly and annual seats together; Enterprise seats are annual only. Sources: dust:dust:seats. - cancellation — How can the contract be cancelled or reduced? [supported]: Monthly seats unassign immediately with a prorated credit; annual seats return to stock for reassignment and are not refunded when someone leaves. Sources: dust:dust:seats. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: Prices are displayed in EUR and the privacy policy identifies a French entity; CHF invoicing and the actual invoicing entity/currency were not contract-verified. Sources: dust:dust:pricing, dust:dust:privacy. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [supported]: Partially specified: Business seat prices/credit allowances are public, while Enterprise pricing, complete usage conversion and negotiated terms require a quote. Sources: dust:dust:pricing, dust:dust:credits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:seats, dust:dust:privacy, dust:dust:credits #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Small plans renew monthly or yearly; Enterprise starts at 10 licences with quoted terms. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Seat-reduction/downgrade timing, future price-change rules, EUR invoicing and complete Enterprise commitments are not specified. - minimum_commitment — What seat or spend minimum applies? [supported]: Standard/Premium cover up to 9 individual licences; Enterprise starts at 10. Sources: swissgpt:swissgpt:university. - contract_length — What contract lengths are offered? [supported]: AGB 3.1 defaults to one calendar month or twelve months with renewal for the same term; an order may set other terms. Sources: swissgpt:swissgpt:terms. - cancellation — How can the contract be cancelled or reduced? [partial]: Either party may cancel for term end through the platform where available or support; prepaid fees are not refunded. Downgrade rules are not specified. Sources: swissgpt:swissgpt:terms. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: Prices are displayed in CHF and AlpineAI AG is Swiss. Standard offers use credit card; invoices can be offered case by case with 14-day payment. EUR invoicing is unverified. Sources: swissgpt:swissgpt:terms, swissgpt:swissgpt:public-pricing. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [supported]: Partially specified individual-sector prices; quote-only Enterprise from 10 licences. Public prices do not establish tax or all usage/service charges. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:public-pricing, swissgpt:swissgpt:health-pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:terms, swissgpt:swissgpt:public-pricing, swissgpt:swissgpt:health-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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial The pinned public repository has an MIT root licence; hosted licensing and complete component coverage are separate. Availability: generally-available Delivery: native Scope: surfaces=Public dust-tt/dust repository root licence; version=dust-tt/dust commit2b1a4973af824f8ff970d585c5eb1f40ae76186c; root LICENSE only; plan=Public source component, not Business/Enterprise hosted-service rights; add_ons=none stated; deployment_mode=not specified; region=Repository licence has no deployment-region entitlement; os=not specified. Limitations: - MIT applies to the pinned repository root grant only; dependencies, supported self-host deployment, hosted terms and any closed Enterprise boundary remain unverified. - licence_type — Which licence applies to each component? [partial]: dust-tt/dust root LICENSE is MIT at commit 2b1a4973af824f8ff970d585c5eb1f40ae76186c. This does not classify every dependency or the contracted hosted service. Sources: dust:dust:licence. - branding_restrictions — Do licence terms restrict branding or user counts? [supported]: The MIT root grant requires preserving copyright and permission notices and does not itself impose branding or user-count caps. Sources: dust:dust:licence. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? The pinned root LICENSE and README were retrieved; a complete nested-component licence inventory and separate closed Enterprise edition boundary were not established. Hosted terms were inaccessible. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:licence #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Terms grant a contractual right to use a proprietary platform. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Component licences, branding or user-count restrictions beyond purchased licences, and a separate enterprise source edition are not published. No public implementation repository was identified. - licence_type — Which licence applies to each component? [supported]: AGB 4.1-4.3 grants non-exclusive, non-transferable access during the contract and reserves platform software, algorithms, documentation and branding rights to AlpineAI. Open-model use is separate. Sources: swissgpt:swissgpt:terms. - branding_restrictions — Do licence terms restrict branding or user counts? [unknown]: Do licence terms restrict branding or user counts? Unknown. Component licences, branding or user-count restrictions beyond purchased licences, and a separate enterprise source edition are not published. No public implementation repository was identified. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Unknown. Component licences, branding or user-count restrictions beyond purchased licences, and a separate enterprise source edition are not published. No public implementation repository was identified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:terms ### VEN-06: Data export and exit Judgment rule: Record admin export of chats, assistants, knowledge bases, prompts and audit logs, formats, export completeness, user self-export, and what survives contract end. Run an admin export on a trial. Exported chats alone do not make assistants and knowledge portable. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business Conversation API and Enterprise Data Source API provide scoped data retrieval; agent export entitlement and complete tenant exit remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust APIs and MCP server, Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business Conversation API and web analytics; Enterprise adds Data Source API. Agent-YAML endpoint entitlement is unverified.; add_ons=API keys with appropriate workspace/resource permissions; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Conversation and document retrieval require the corresponding plan and resource permissions. Complete organization coverage, agent-export entitlement and the post-termination retrieval window remain unknown. - chat_export — Can admins export all chats? [partial]: Business pricing includes Conversation API; authorized API users retrieve accessible conversation messages with pagination. This does not establish one-click all-tenant admin export. Sources: dust:dust:get-conversation, dust:dust:pricing. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: The agent-YAML endpoint and public pricing were checked on 2026-10-21. Neither establishes its Business or Enterprise entitlement. Reusable assistant/prompt export for a named plan remains unknown. - knowledge_export — Can knowledge bases and their sources be exported? [partial]: Enterprise pricing adds Data Source API; the documented endpoint retrieves accessible data-source documents as JSON. Complete source/credential/permission portability and an all-tenant export are unverified. Sources: dust:dust:get-document, dust:dust:pricing. - export_format — Are formats documented and machine-readable? [partial]: Business Conversation API and Enterprise Data Source API return JSON for accessible resources. Web analytics separately exports CSV. These formats do not establish complete tenant export; no plan-scoped agent-YAML export is claimed. Sources: dust:dust:get-conversation, dust:dust:get-document, dust:dust:analytics, dust:dust:pricing. - post_termination_window — How long can data be retrieved after termination? [unknown]: How long can data be retrieved after termination? No trial admin exit/export was run; complete tenant coverage and the post-termination retrieval window were not established from the accessible API docs or unreadable contract route. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:get-conversation, dust:dust:pricing, dust:dust:get-document, dust:dust:analytics #### AlpineAI / SwissGPT 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. ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business email support and Enterprise priority/SLA service are advertised; credit terms and local-language support remain open. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - support_channels — Which support channels are available on each plan? [supported]: Pricing lists Business email and Enterprise priority support with dedicated CSM; public support/community resources are available. Sources: dust:dust:pricing, dust:dust:support. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Support/pricing/Enterprise pages and the official status URL were checked. German/French/Italian staffed support and detailed credited SLA terms were not established. - regional_presence — Is there a DACH or Swiss entity, team or partner? [partial]: The public policy identifies a Paris, France entity. A DACH/Swiss support team or named regional partner was not established. Sources: dust:dust:privacy. - uptime_sla — Is there an uptime SLA with credits? [partial]: Enterprise marketing claims 99.9% uptime and pricing includes an SLA; service-credit amounts, exclusions and claim rules were not retrieved. Sources: dust:dust:enterprise, dust:dust:pricing. - status_page — Is there a public status page with history? [partial]: Model-selection docs link https://dust.statuspage.io for incidents. Direct retrieval timed out, so incident history was not verified. Sources: dust:dust:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:support, dust:dust:privacy, dust:dust:enterprise, dust:dust:models #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Support uses a service portal and email fallback; terms promise 99% availability. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - DE/FR/IT support guarantees, support hours, response times, SLA credits and an official public status/incident history were not located. - support_channels — Which support channels are available on each plan? [supported]: Service Desk/email is listed in sector plans. AGB 9.2 requires support-portal tickets, with email when the portal is technically unreachable. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:terms. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. DE/FR/IT support guarantees, support hours, response times, SLA credits and an official public status/incident history were not located. - regional_presence — Is there a DACH or Swiss entity, team or partner? [supported]: AlpineAI AG lists a Davos, Switzerland address. Sources: swissgpt:swissgpt:imprint. - uptime_sla — Is there an uptime SLA with credits? [partial]: AGB 9.1 promises 99% availability during the licence term with planned/urgent maintenance exceptions. No credit schedule or response-time commitment was located. Sources: swissgpt:swissgpt:terms. - status_page — Is there a public status page with history? [unknown]: Is there a public status page with history? Unknown. DE/FR/IT support guarantees, support hours, response times, SLA credits and an official public status/incident history were not located. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:terms, swissgpt:swissgpt:imprint ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust has rollout and training material, with hands-on support packaged for Enterprise. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Public learning material (no paid entitlement required to read); contracted CSM/onboarding is Enterprise; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - onboarding_service — Is guided onboarding included? [supported]: Enterprise pricing includes dedicated CSM and onboarding; exact hours and scope are contractual. Sources: dust:dust:pricing. - user_training — Is end-user training offered, in which languages? [partial]: Public team onboarding and education resources are available. Course/live-session language coverage was not established. Sources: dust:dust:training, dust:dust:rollout. - use_case_library — Are role-based use cases and templates provided? [supported]: The public Use Cases and Guides index lists departmental guides for Sales, Support, Marketing, Engineering, Data Analytics, Knowledge, People, Product and Collaboration; the Sales guide supplies concrete agent examples and build links. This establishes public role-based guidance, not a separately verified in-product template entitlement. Sources: dust:dust:r2-department-guides, dust:dust:r2-sales-guide. - adoption_programme — Is there a champion or adoption programme? [partial]: The rollout guide covers launch, builder community, education and expansion; a contracted champion programme entitlement was not established. Sources: dust:dust:rollout. - service_cost — Which services cost extra? [partial]: Hands-on CSM/onboarding is Enterprise packaging; a numerical professional-services tariff was not established. Sources: dust:dust:pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:training, dust:dust:rollout, dust:dust:r2-department-guides, dust:dust:r2-sales-guide #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Sector offers describe guided rollout, workshops and a six-lesson e-learning course. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Champion programmes, training languages, mandatory onboarding scope and separate professional-service charges are not published. - onboarding_service — Is guided onboarding included? [partial]: University and healthcare pages offer implementation help and onsite team training; inclusion in licence price is not stated. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:health-pricing. - user_training — Is end-user training offered, in which languages? [partial]: Six e-learning lessons and prompting/use-case workshops are offered; delivery languages are not specified. Sources: swissgpt:swissgpt:product, swissgpt:swissgpt:university. - use_case_library — Are role-based use cases and templates provided? [supported]: Sector pages describe university, authority and healthcare use cases; Premium adds preconfigured assistants. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:product. - adoption_programme — Is there a champion or adoption programme? [unknown]: Is there a champion or adoption programme? Unknown. Champion programmes, training languages, mandatory onboarding scope and separate professional-service charges are not published. - service_cost — Which services cost extra? [unknown]: Which services cost extra? Unknown. Champion programmes, training languages, mandatory onboarding scope and separate professional-service charges are not published. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:health-pricing, swissgpt:swissgpt:product ## Sources ### dust:dust:models Auto models and the model picker. Users select a model per message or agent; auto choices use maintained ordered lists rather than task-based routing. - URL: https://docs.dust.tt/docs/user-documentation/agents/model-selection - Locator: Auto model lists; availability; API overrides - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:eu-models EU-hosted models. EU credit-plan workspaces using Dust model hosting can restrict agents and auto choices to EU-hosted models; BYOK is excluded from this setting. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/eu-hosted-models - Locator: Availability; supported/excluded model table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:changelog Dust changelog. Recent dated changes include German/French UI, Gemini 4 Argon and migration from File Generation to Computer. - URL: https://docs.dust.tt/docs/changelog - Locator: October 21, 16 and 14, 2026 entries - Evidence kind: documented - Source date: 2026-10-21 - Retrieved: 2026-10-21 ### dust:dust:files Conversation Files. Conversation uploads are scoped to one conversation and support documents, tabular data, images and audio. - URL: https://docs.dust.tt/docs/user-documentation/data-sources/conversation-files/conversation-files - Locator: Formats; size table; generating files - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:pricing Dust Pricing. Business supports up to 100 people with Free/Pro/Max seats; Enterprise pricing is sales-led and adds pooled credits, SCIM, audit, single tenancy and support. - URL: https://dust.tt/home/pricing - Locator: Business/Enterprise table and FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:product AlpineAI product and FAQ. Describes browser and mobile access, Mistral Large 3 on AlpineAI hardware, document assistants, Outlook, Listener and Enterprise integrations. - URL: https://alpineai.swiss/produkt/ - Locator: Chat; Assistants; Listener; FAQs on models, Outlook, licences - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:tiers Model access tiers. Admins restrict models and reasoning efforts at workspace, group or member level, with a separate published-agent bypass setting. - URL: https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/model-access-tiers - Locator: Workspace, group and individual ceilings - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:spaces Spaces management. Spaces control knowledge and agent access; Business allows five and Enterprise 100 spaces. - URL: https://docs.dust.tt/docs/user-documentation/admins/spaces-management - Locator: Open/restricted spaces; limits; visibility - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:credits Credits. Consumption adds token and tool credits; a 600-AWU checkpoint can pause user-started root tasks, with exceptions. - URL: https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/credits - Locator: Token/action credits; checkpoints - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:credit-management Credit management. Credit sources and block behavior vary by plan; beta Enterprise Pooled group budgets exclude programmatic consumption. - URL: https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/credit-management - Locator: Personal caps; group budgets; programmatic use - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:file-limits File size limits. The dedicated limits FAQ gives different image, audio and tabular caps than Conversation Files and excludes direct video uploads. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/faq/file-size-limits - Locator: Upload caps; audio-only restriction - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:computer Computer. Computer executes code in temporary workspaces, handles Office/PDF files, performs documented OCR and restricts network access by allowlist. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/computer - Locator: File work; OCR; network control; secrets - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:drive Google Drive. Drive sync follows a dedicated connection account and selected content; scanned documents need conversation upload for OCR and Excel table queries need conversion to Sheets. - URL: https://docs.dust.tt/docs/user-documentation/admins/connections-management/google-drive - Locator: Connection identity; refresh; OCR; spreadsheet limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:search Search data sources. Agents search selected knowledge sources and retrieve relevant document context. - URL: https://docs.dust.tt/docs/user-documentation/agents/knowledge/search-data-sources - Locator: Document selection; retrieval - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:university AlpineAI universities. Lists licence limits and Enterprise threshold, university integration process and onboarding. - URL: https://alpineai.swiss/en/universities/ - Locator: Prices; Integration & Licenses; Features & Languages - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:permissions Access Controls and Permissions. Knowledge access is organized through admin-selected connection content and membership of open/restricted Spaces. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/access-controls-and-permissions - Locator: Access policy; connection account; Spaces - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:microsoft Microsoft. Microsoft data is scoped to the connecting account and selected SharePoint sources; changes synchronize on a five-minute cycle. - URL: https://docs.dust.tt/docs/user-documentation/admins/connections-management/microsoft - Locator: Connection account; delegated and service-principal setup; sync - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:confluence Confluence. Confluence sync covers selected global spaces, excluding private spaces and pages with view restrictions. - URL: https://docs.dust.tt/docs/user-documentation/admins/connections-management/confluence - Locator: Scope; restricted pages; refresh - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:jira Beta: Import Jira issues. A separately documented beta route imports Jira issues as a custom connection. - URL: https://docs.dust.tt/docs/user-documentation/data-sources/custom-connections/beta-import-jira-issues - Locator: Import path - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:sources What data sources can be connected to Dust?. Official guides identify managed connections and custom API/import routes. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/faq/general-questions/what-data-sources-can-be-connected-to-dust - Locator: Named sources - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:tools Adding an MCP Server. Admins add remote MCP servers with OAuth or bearer credentials and can restrict tools to skills. - URL: https://docs.dust.tt/docs/user-documentation/admins/tools-management/adding-an-mcp-server - Locator: Remote/custom servers; auth; tool restriction - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:r2-bigquery Dust BigQuery connection. Dust stores BigQuery metadata and runs table queries through a dedicated service account; dataset content is not synchronized into the index. - URL: https://docs.dust.tt/docs/user-documentation/admins/connections-management/bigquery.md - Locator: No content sync; service-account setup, one location and Space table selection - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:product-20261026 AlpineAI product and FAQ. Describes browser and mobile access, Mistral Large 3 on AlpineAI hardware, document assistants, Outlook, Listener and Enterprise integrations. - URL: https://alpineai.swiss/produkt/ - Locator: Chat; Assistants; Listener; FAQs on models, Outlook, licences - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-26 ### swissgpt:swissgpt:security-20261026 AlpineAI security and compliance. Separates RIZ application hosting from Green and RZO inference and describes encryption, access restrictions and external-search opt-in. - URL: https://alpineai.swiss/sicherheit/ - Locator: Infrastructure; isolation; encryption; security FAQ - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-26 ### swissgpt:swissgpt:public-pricing-20261026 AlpineAI authorities and institutions. Monthly billing is CHF 79 Standard or CHF 89 Premium per user; annual billing displays CHF 74 or CHF 80 per month; Enterprise is quoted from 10 licences. - URL: https://alpineai.swiss/behoerden/ - Locator: Prices; pricing-toggle applyMode(monthly/yearly) and billing labels in delivered HTML - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### swissgpt:swissgpt:health-pricing-20261026 AlpineAI healthcare. Healthcare monthly billing is CHF 89 Standard or CHF 99 Premium per user; annual billing displays CHF 80 or CHF 90 per month. - URL: https://alpineai.swiss/gesundheitswesen/ - Locator: Prices; pricing-toggle applyMode(monthly/yearly) and billing labels in delivered HTML - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### dust:dust:credentials Personal vs Shared Credentials for Tools & MCP Servers. Tools can use a shared account or each user OAuth identity; even personal auth needs initial admin setup. - URL: https://docs.dust.tt/docs/user-documentation/admins/tools-management/personal-vs-shared-credentials - Locator: Shared versus personal authentication - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:security Dust Security. Dust claims EU/US hosting, AES-256/TLS, no model training, provider zero retention and SOC 2 Type II. - URL: https://dust.tt/home/security - Locator: Hosting, training, encryption and certification statements - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:deep Deep-dive Agent. Deep-dive plans, delegates and writes cited reports, using Company Data knowledge and selected tools; Table Query is excluded. - URL: https://docs.dust.tt/docs/user-documentation/agents/default-agents/deep-dive-agent - Locator: Research flow; citations; limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:memory Agent Memory. Enabled agents retain user-private memory across conversations; users can view and delete it and it persists until deletion. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/agent-memory - Locator: Adding the tool; viewing/deleting; privacy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:builder Create your first agent. Agents combine instructions, models, knowledge and tools with controlled sharing. - URL: https://docs.dust.tt/docs/user-documentation/agents/create-your-first-agent - Locator: Instructions; tools; sharing - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:governance Workspace Governance: Roles, Groups & Permissions. Admins delegate manager/group permissions for agents, skills, models, billing and security; grants are additive. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/workspace-governance-roles-groups-and-permissions - Locator: Roles; permission matrix; additive access - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:web Web Search & Browse. The tool runs Google queries and browses results, with agent-level configuration and format options. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/web-search-and-browse - Locator: Search and browsing flow - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:terms AlpineAI general terms. Defines cloud licensing, no-training promise, web-search consent and quotas, subscription cancellation, 99 percent availability and Swiss law. - URL: https://alpineai.swiss/agb/ - Locator: Sections 2.1-2.5, 3, 4, 7.5, 9 and 11 - Evidence kind: documented - Source date: 2026-05-25 - Retrieved: 2026-10-21 ### swissgpt:swissgpt:dpa AlpineAI data processing agreement. Sets CH/EEA processing with a third-country exception, anonymised-data use, deletion and backup exception, safeguards and a dated subprocessor list. - URL: https://alpineai.swiss/wp-content/uploads/2026/07/AlpineAI-AVV_zu_GTC_2026-07-10.pdf - Locator: Pages 1-4 sections 1.5, 2.4, 7, 9 and 11; pages 6-7 Annexes 2-3 - Evidence kind: documented - Source date: 2026-07-10 - Retrieved: 2026-10-21 ### dust:dust:triggers Triggers. Agents can run automatically from schedule or event triggers. - URL: https://docs.dust.tt/docs/user-documentation/agents/triggers/index - Locator: Schedules and events - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:schedules Schedules. Agents can run on recurring schedules. - URL: https://docs.dust.tt/docs/user-documentation/agents/triggers/schedules - Locator: Schedule setup - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:webhooks Webhooks. Admins configure webhook sources; members attach filtered triggers to agents, with optional signature verification for custom sources. - URL: https://docs.dust.tt/docs/user-documentation/agents/triggers/webhooks/index - Locator: Built-in and custom event sources - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:pods Pods overview. Pods combine shared conversations, tasks and files; open Pods are workspace-browsable and restricted Pods require invitation. - URL: https://docs.dust.tt/docs/user-documentation/pods/overview - Locator: Shared workspace and visibility - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:api-keys API keys. Dust API keys have read/admin scopes, data access and enforceable per-key monthly caps. - URL: https://docs.dust.tt/docs/user-documentation/admins/api-keys - Locator: Scopes; Space access; caps - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:mcp-server Dust MCP Server. Dust exposes workspace knowledge, agents, conversations, files and Pods to OAuth MCP clients under the authenticated user permissions. - URL: https://docs.dust.tt/docs/user-documentation/agents/integrations/dust-mcp-server - Locator: Region URLs; OAuth; user permissions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:upsert Upsert a document in a data source. The API loads or updates documents in a scoped data source. - URL: https://docs.dust.tt/api-reference/datasources/upsert-a-document-in-a-data-source - Locator: Endpoint and authentication - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:get-conversation Get a conversation. The API retrieves accessible conversation messages with pagination. - URL: https://docs.dust.tt/api-reference/conversations/get-a-conversation - Locator: Response schema - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:review2-product AlpineAI product and FAQ. The product page assigns Standard/Premium to assistants, not autonomous agents; it explicitly assigns custom integrations to Enterprise. - URL: https://alpineai.swiss/produkt/ - Locator: Integrations; Assistants & Agents; Operations & Licences - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:review2-api-access AlpineAI API platform. Public API portal redirects to authentication and states that access is limited with gradual account activation; no authenticated endpoint/entitlement documentation was accessed. - URL: https://platform.prod.alpineai.ch/ - Locator: Authentication landing page; limited access notice - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:browser Browser Extension. An official extension supports Chrome, Firefox and Chromium-based browsers. - URL: https://docs.dust.tt/docs/user-documentation/agents/integrations/browser-extension - Locator: Browsers and capabilities - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:teams Dust in Teams. An official Teams integration runs Dust agents within Microsoft Teams after admin setup. - URL: https://docs.dust.tt/docs/user-documentation/agents/integrations/dust-in-teams - Locator: Setup and usage - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:images Image Generation. Agents generate images from text or references, up to 14 reference images, with SynthID and content restrictions. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/image-generation - Locator: Reference images; parallel generation; safety - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:speech Voice and sound generation. The speech tool generates MP3 narration or multi-speaker dialogue with selectable languages and styles. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/voice-and-sound-generation - Locator: Speech Generator - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:meetings Meeting transcripts. Dust consumes transcripts from connected notetaker and sales tools; Gong private transcripts are excluded. - URL: https://docs.dust.tt/docs/user-documentation/agents/integrations/meeting-transcripts - Locator: Providers and scope - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:frames Frames overview. Frames provide persistent interactive agent output that can be refined and shared. - URL: https://docs.dust.tt/docs/user-documentation/agents/frames/overview - Locator: Creating and editing interactive content - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:pod-chats Pod conversations. All Pod members can read and contribute to Pod conversations, which are automatically indexed. - URL: https://docs.dust.tt/docs/user-documentation/pods/conversations - Locator: Visibility; indexing; participation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:sso Single Sign-On. Admins configure and enforce SAML SSO, which disables other social sign-in paths for the workspace. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/single-sign-on-sso/single-sign-on-sso - Locator: Setup; enforcement - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:enterprise Dust for Enterprise. The Enterprise marketing page claims 365-day audit retention, 99.9% uptime and support for 10,000+ users. - URL: https://dust.tt/home/enterprise - Locator: Security and scale - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:provision Users and groups provisioning. Enterprise SCIM creates, updates and deactivates users and syncs groups; groups can grant Admin/Manager roles. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/users-and-groups-provisioning - Locator: SCIM 2.0; group role mapping - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:seats Seat management. Admins assign independent roles and Free/Pro/Max seats; annual stock and already-allocated credits have specific reclaim rules. - URL: https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/seat-management - Locator: Seat assignments; billing cycles; leaving - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:analytics Analytics. Consumption reports break down users, groups, models, tools, agents and Pods; exports omit message content and can double-attribute group usage. - URL: https://docs.dust.tt/analytics - Locator: Attribution; CSV; content exclusion - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:audit Audit Logs. Enterprise logs distinguish users, API keys and system actors with CSV and continuous SIEM delivery. - URL: https://docs.dust.tt/docs/user-documentation/admins/audit-logs/audit-logs - Locator: Enterprise scope; actor types; SIEM - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:privacy Dust Platform Privacy Policy. The policy identifies Permutation Labs in Paris and distinguishes its controller processing from customer processor processing, with non-EEA transfer safeguards. - URL: https://dust.tt/home/platform-privacy - Locator: About Us; sections 2, 6 and 7 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:secrecy AlpineAI supplementary agreement for secret data. When signed for legally secret data, requires Swiss plaintext services, restricted access and zero prompt/response retention for AI API services. - URL: https://alpineai.swiss/wp-content/uploads/2026/03/AlpineAI_Zusatzvereinbarung_Geheimnisdaten.2025-03-30-1.pdf - Locator: Printed version 30 March 2026; section 3 on both pages - Evidence kind: documented - Source date: 2026-03-30 - Retrieved: 2026-10-21 ### swissgpt:swissgpt:review2-security AlpineAI security and compliance. Security page describes RIZ application hosting and Green/RZO inference as colocation on AlpineAI-owned/operated hardware, without logical access by site operators. This is a vendor infrastructure disclosure, not an updated DPA schedule. - URL: https://alpineai.swiss/sicherheit/ - Locator: Certified infrastructure; FAQ on storage and processing - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:review2-dpa AlpineAI data processing agreement. Re-retrieved July 10 Annex 3 lists RIZ hosting/support and Green pure colocation with no logical data access, plus CH/EU/US operational suppliers; RZO is not listed. No newer public schedule or RZO approval was retrieved. - URL: https://alpineai.swiss/wp-content/uploads/2026/07/AlpineAI-AVV_zu_GTC_2026-07-10.pdf - Locator: Annex 3 page 7, dated 10 July 2026; section 1.5 and 7.3 - Evidence kind: documented - Source date: 2026-07-10 - Retrieved: 2026-10-21 ### dust:dust:training-policy Dust Platform Privacy Policy. The policy asserts listed providers do not train, retain or log Customer Content for human review; this source pass did not retrieve the customer DPA. - URL: https://dust.tt/home/platform-privacy - Locator: Section 6, Foundational Model Providers - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:delete-chat Can I delete or rename a conversation?. Users can delete or rename their conversations. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/faq/managing-agents/can-i-delete-or-rename-a-conversation - Locator: Conversation actions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:imprint AlpineAI imprint. Identifies AlpineAI AG at Obere Strasse 22b in Davos, Switzerland. - URL: https://alpineai.swiss/impressum/ - Locator: Address - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:security AlpineAI security and compliance. Separates RIZ application hosting from Green and RZO inference and describes encryption, access restrictions and external-search opt-in. - URL: https://alpineai.swiss/sicherheit/ - Locator: Infrastructure; isolation; encryption; security FAQ - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:public-pricing AlpineAI authorities and institutions. Monthly billing is CHF 79 Standard or CHF 89 Premium per user; annual billing displays CHF 74 or CHF 80 per month; Enterprise is quoted from 10 licences. - URL: https://alpineai.swiss/behoerden/ - Locator: Prices; pricing-toggle applyMode(monthly/yearly) and billing labels in delivered HTML - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:health-pricing AlpineAI healthcare. Healthcare monthly billing is CHF 89 Standard or CHF 99 Premium per user; annual billing displays CHF 80 or CHF 90 per month. - URL: https://alpineai.swiss/gesundheitswesen/ - Locator: Prices; pricing-toggle applyMode(monthly/yearly) and billing labels in delivered HTML - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:fx-ecb ECB historical euro reference rates. EUR 1 = USD 1.1215 = CHF 0.9237 on October 20, 2026. - 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 ### swissgpt:swissgpt:ecb-fx ECB euro foreign exchange reference rates, 20 October 2026. ECB records EUR 1 = USD 1.1215 and CHF 0.9237 on 20 October 2026; derived USD to EUR is 1/1.1215 and CHF to EUR is 1/0.9237. - 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 ### dust:dust:licence Dust repository LICENSE at pinned commit. The pinned public repository root licence is MIT; hosted service terms and third-party components are separate. - URL: https://github.com/dust-tt/dust/blob/2b1a4973af824f8ff970d585c5eb1f40ae76186c/LICENSE - Locator: Root LICENSE, MIT permission grant - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:get-document Retrieve a document from a data source. The API retrieves a source document; this does not establish a complete one-click tenant export. - URL: https://docs.dust.tt/api-reference/datasources/retrieve-a-document-from-a-data-source - Locator: Endpoint and response - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:support Dust Support. The vendor provides public support entry points and community/documentation resources. - URL: https://dust.tt/home/support - Locator: Support channels - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:rollout Dust Rollout Guide. Public rollout guidance covers setup, launch, team education and measurement. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/dust-rollout-guide/index - Locator: Rollout phases - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:training Team onboarding material. Dust provides reusable team-onboarding material. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/dust-rollout-guide/team-onboarding-material - Locator: Training resources - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:r2-department-guides Dust Use Cases and Guides. Public guides are organized by Sales, Support, Marketing, Engineering, Data, Knowledge, People, Product and Collaboration. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/use-cases-and-guides/index.md - Locator: Use Cases by Department - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:r2-sales-guide Dust Sales use-case guide. The Sales guide provides concrete role-based agent examples; this is public learning material, not a contracted training entitlement. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/use-cases-and-guides/sales.md - Locator: Sales agent examples and build links - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21