Skip to content

Agent-readable comparison

Dust vs TypingMind / TypingMind Teams

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

This comparison has 47 criteria with sourced findings for both products, including 47 that a second agent cross-checked for both. 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. No winner is declared. A missing sourced finding is not evidence that a capability is absent.

Same facts as Markdown and JSON. Methodology.

Models

MOD-01 Model catalogue and providers

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Teams is a customer-key multi-provider chat interface, with dated additions and explicit model selection.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • providers Which model providers are available? [supported]: Teams admin key setup lists OpenAI, Anthropic, Google, OpenRouter, DeepInfra, DeepSeek, Groq, Mistral, Moonshot, Perplexity, xAI and Z.ai, plus custom providers. Sources: typingmind:typingmind:set-up-api-keys.
  • current_models Which current models are selectable on this plan? [partial]: The dated October changelog records Gemini 4 Argon and Muse Wonder on October 14 and Claude Haiku 5.5, Mistral Large 4 and Nano Banana 2.1 on October 9. Actual availability depends on enabled endpoint and customer account; a complete Teams tenant model catalogue was not observed. Sources: typingmind:typingmind:release, typingmind:typingmind:set-up-api-keys.
  • user_choice Can users pick the model per chat? [supported]: Users select an available model for a chat; Teams administrators choose which models are exposed. Sources: typingmind:typingmind:manage-ai-models, typingmind:typingmind:restrict-model-access.
  • 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? The first-party Teams documentation, pricing, legal pages and dated changelog retrieved on 2026-10-21 do not establish this detail; no account or bounded fixture was used.
  • multimodal_input Which models accept images, audio or files? [partial]: Document upload, vision-capable model image input and transcription are documented as separate routes; the docs do not provide a complete per-model Teams image/audio/file matrix. Sources: typingmind:typingmind:chat-with-documents, typingmind:typingmind:voice.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:set-up-api-keys, typingmind:typingmind:release, typingmind:typingmind:manage-ai-models, typingmind:typingmind:restrict-model-access, typingmind:typingmind:chat-with-documents, typingmind:typingmind:voice.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Dated model additions are public; release lag and removal guarantees remain unestablished.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; 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? No matched first-party provider release dates for the last three releases, fixed deprecation-notice period or version-retention guarantee was retrieved.
  • changelog Is there a dated public model changelog? [supported]: The public changelog dates model and Teams feature releases through October 14, 2026 in the retrieved page. Sources: typingmind:typingmind:release.
  • deprecation_notice How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? No matched first-party provider release dates for the last three releases, fixed deprecation-notice period or version-retention guarantee was retrieved.
  • version_pinning Can an admin keep an older model version? [partial]: Customer custom-model endpoint configuration can name a provider model or deployment, but a contractual right to retain discontinued SaaS wrappers or provider versions is not established. Sources: typingmind:typingmind:manage-ai-models, typingmind:typingmind:azure-openai.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:release, typingmind:typingmind:manage-ai-models, typingmind:typingmind:azure-openai.

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

No public information found Support: not-published

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Teams uses customer provider keys; its Custom Admin documentation also describes Claude via the customer AWS Bedrock account.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams SaaS Starter/Growth/Professional custom-model setup; Bedrock Custom Admin route has no verified exact tier mapping. Separate Teams self-host licence for private endpoint configuration.; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Bedrock is documented for Custom Admin; no all-tier, all-Claude-model or self-host Bedrock entitlement is inferred. Provider-route feature parity was not tested.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:set-up-api-keys, typingmind:typingmind:r2-teams-custom-models, typingmind:typingmind:r3-custom-admin-bedrock, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:pricing, typingmind:typingmind:manage-ai-models, typingmind:typingmind:toolbox.

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

No public information found Support: not-published

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Customer model endpoints are supported; optional self-host knowledge uses documented OpenAI embeddings.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind personal browser app and PWA, TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Personal app local-model guides; Teams SaaS custom-model setup on Starter/Growth/Professional; separate annual commercial Teams self-host package; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=Personal browser/local network; US/EU Teams SaaS; customer-selected self-host placement and external API routes; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:r2-teams-custom-models, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:ollama, typingmind:typingmind:lmstudio, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:cloud-host-vs-self-host, typingmind:typingmind:toolbox, typingmind:typingmind:manage-ai-models.

MOD-05 Model control and usage limits

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Professional administrators govern model access and configurable consumption limits.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional for governance; customer-configured limits; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • model_allowlist_by_group Can admins limit models per group? [supported]: Admins restrict model availability by user group; the limits guide still points availability controls to the legacy model-limits section. Sources: typingmind:typingmind:restrict-model-access, typingmind:typingmind:usage-limits.
  • data_bound_models Can admins restrict which models receive connector or knowledge content? [partial]: Admins configure the models available to agents and their knowledge access. No content-classification or connector-label-based model egress rule was established. Sources: typingmind:typingmind:roles-and-permissions, typingmind:typingmind:connect-knowledge-base-to-your-ai-agents.
  • default_model Can admins set the default model? [unknown]: No Teams administrator control setting the default model for new chats was established. The October multi-model finalization default is a different feature; the plan matrix and model-management documents do not resolve this atom.
  • user_limits What per-user message or token limits apply, and are they published? [supported]: Reusable limit groups configure message, character and token limits per time period, across users/groups, models, agents and plugins. Published examples are admin settings, not plan-wide quotas. Sources: typingmind:typingmind:usage-limits.
  • limit_behaviour What happens when a limit is reached? [partial]: Users see a configurable limitation notice and can inspect details. Exact block, downgrade, overshoot and reset semantics at exhaustion were not established. Sources: typingmind:typingmind:usage-limits.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:restrict-model-access, typingmind:typingmind:usage-limits, typingmind:typingmind:roles-and-permissions, typingmind:typingmind:connect-knowledge-base-to-your-ai-agents.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Document text can be attached to chat; full-context training files and RAG are distinct.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:chat-with-documents, typingmind:typingmind:how-knowledge-base-works-in-typingmind-team, typingmind:typingmind:toolbox, typingmind:typingmind:training-files-vs-knowledge-base.

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

Agent cross-checked Support: partial

Spaces persist shared knowledge and bind it to agent tools.

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Growth and above provide a tagged organization KB bound to agents; the technical guide still labels it Early Access.

Availability: beta · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Growth/Professional: RAG and tagged agent KB; Professional additionally supplies group/resource visibility restrictions; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Current plan matrix sells RAG in Growth/Professional, while the technical KB guide (updated2025-11-10) still labels it Early Access. No dated GA transition or tenant rollout was verified; findings retain beta/Early Access qualification.
  • No source-user permission fixture was run.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:get-started-with-knowledge-base, typingmind:typingmind:training-files-vs-knowledge-base, typingmind:typingmind:connect-knowledge-base-to-your-ai-agents, typingmind:typingmind:restrict-ai-agents-access, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:how-knowledge-base-works-in-typingmind-team.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Named knowledge integrations and extensible tools exist; broad source mentions lack enterprise permission detail.

Availability: beta · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Growth/Professional SaaS RAG; separate annual commercial Teams self-host licence with optional KB and customer-managed connector credentials; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Current plan matrix sells RAG in Growth/Professional, while the technical KB guide (updated2025-11-10) still labels it Early Access. No dated GA transition or tenant rollout was verified; findings retain beta/Early Access qualification.
  • A reachable self-host plugin endpoint is not a native file-share crawler.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:training-files-vs-knowledge-base, typingmind:typingmind:get-started-with-knowledge-base, typingmind:typingmind:setup-external-connectors-for-knowledge-base, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:connect-with-your-notion-pages, typingmind:typingmind:mcp, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:overview.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Documented access control is by tagged knowledge and agent/group visibility; per-user source ACL enforcement is unproven.

Availability: beta · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Growth/Professional RAG data/tag selection; Professional adds group-based resource restrictions; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Current plan matrix sells RAG in Growth/Professional, while the technical KB guide (updated2025-11-10) still labels it Early Access. No dated GA transition or tenant rollout was verified; findings retain beta/Early Access qualification.
  • No two-user source-permission or revocation fixture.
  • source_permissions_respected Are source permissions enforced per user? [unknown]: Are source permissions enforced per user? No two-user permission/revocation fixture, source ACL mirror, revocation SLA or Microsoft Purview-label enforcement documentation was retrieved. Do not equate agent access with source-user permissions.
  • enforcement_point Does the source system, a mirrored index or nothing enforce them? [partial]: Growth/Professional bind data tags to agents; Professional adds agent availability by user/group. This application-side mechanism does not establish synchronized source-user ACLs. Sources: typingmind:typingmind:connect-knowledge-base-to-your-ai-agents, typingmind:typingmind:restrict-ai-agents-access, typingmind:typingmind:r2-plan-matrix.
  • revocation_delay How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? No two-user permission/revocation fixture, source ACL mirror, revocation SLA or Microsoft Purview-label enforcement documentation was retrieved. Do not equate agent access with source-user permissions.
  • admin_scope_controls Can admins exclude sites, folders or labels? [supported]: Admins choose the Notion pages/databases to ingest and select knowledge tags for each agent. Sources: typingmind:typingmind:connect-with-your-notion-pages, typingmind:typingmind:connect-knowledge-base-to-your-ai-agents.
  • sensitivity_labels Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? No two-user permission/revocation fixture, source ACL mirror, revocation SLA or Microsoft Purview-label enforcement documentation was retrieved. Do not equate agent access with source-user permissions.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:connect-knowledge-base-to-your-ai-agents, typingmind:typingmind:restrict-ai-agents-access, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:connect-with-your-notion-pages.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

The KB indexes copies, refreshes connected content daily and uses selected SaaS or customer-hosted storage.

Availability: beta · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Growth/Professional SaaS RAG; separately quoted annual Teams self-host licence and optional PostgreSQL KB; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Current plan matrix sells RAG in Growth/Professional, while the technical KB guide (updated2025-11-10) still labels it Early Access. No dated GA transition or tenant rollout was verified; findings retain beta/Early Access qualification.
  • No synchronization/deletion latency fixture.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:training-files-vs-knowledge-base, typingmind:typingmind:how-knowledge-base-works-in-typingmind-team, typingmind:typingmind:connect-with-your-notion-pages, typingmind:typingmind:eu-data-center, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:cloud-host-vs-self-host.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Clickable source references are documented, but retrieval quality has no observed multilingual fixture.

Availability: beta · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Growth/Professional SaaS RAG and reference display; model-followed instructions separate from retrieval guarantees; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Current plan matrix sells RAG in Growth/Professional, while the technical KB guide (updated2025-11-10) still labels it Early Access. No dated GA transition or tenant rollout was verified; findings retain beta/Early Access qualification.
  • No shared multilingual/citation-accuracy fixture.
  • citations Are answers linked to specific sources? [supported]: Admins may enable reference display for knowledge responses so users can follow source links. Sources: typingmind:typingmind:get-started-with-knowledge-base.
  • citation_accuracy Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? No shared German/French/English question set, source-support check, cross-language retrieval test or measured answer count was run.
  • cross_language Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? No shared German/French/English question set, source-support check, cross-language retrieval test or measured answer count was run.
  • no_answer_behaviour Does it say when the corpus has no answer? [partial]: Admins can instruct the model to refrain from answering when knowledge is insufficient; the system-prompt guide gives an example. This is prompt configuration, not a tested no-answer guarantee. Sources: typingmind:typingmind:system-prompts-on-admin-panel.
  • observed_accuracy How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? No shared German/French/English question set, source-support check, cross-language retrieval test or measured answer count was run.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:get-started-with-knowledge-base, typingmind:typingmind:system-prompts-on-admin-panel, typingmind:typingmind:r2-plan-matrix.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Persistent agent and global admin instructions are documented; named-tier cross-chat memory and its controls remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams SaaS Starter/Growth/Professional instructions and shared agents; exact commercial entitlement for non-project memory and its controls unverified; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Persistent instructions are distinct from learned cross-chat memory. The Memory guide and release do not establish its named-tier entitlement.
  • custom_instructions Can users set persistent instructions? [supported]: Persistent agent instructions and global admin instructions are documented; agents can include full-context training files. Sources: typingmind:typingmind:system-prompts-on-admin-panel, typingmind:typingmind:training-files-vs-knowledge-base.
  • cross_chat_memory Does the product remember facts across chats? [unknown]: The October 14 Teams release and Memory guide describe cross-chat memory, but no named Starter/Growth/Professional entitlement for that capability was established. The Growth/Professional Projects gate does not establish non-project memory availability.
  • user_memory_controls Can users view, edit and delete memories? [unknown]: The Memory guide describes saved-memory settings, but their named Teams tier entitlement and complete edit/delete behavior remain unverified. No personal-app control is inferred to be a Teams entitlement.
  • admin_memory_controls Can admins turn memory off? [unknown]: The October 14 Teams release describes an admin Memory switch, but the current plan matrix does not map it to a named tier. Organization-wide memory-control entitlement remains unknown.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:system-prompts-on-admin-panel, typingmind:typingmind:training-files-vs-knowledge-base, typingmind:typingmind:release, typingmind:typingmind:memory, typingmind:typingmind:r2-plan-matrix.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: supported

Teams admins publish agents and prompts, with delegated creation permissions and group access.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Starter/Growth/Professional shared agents and prompts; Growth/Professional RAG; Professional delegated roles and resource visibility; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:build-a-shared-ai-agent-collection, typingmind:typingmind:training-files-vs-knowledge-base, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:roles-and-permissions, typingmind:typingmind:restrict-ai-agents-access, typingmind:typingmind:build-a-shared-prompt-library.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Built-in plugins and custom HTTP/JavaScript/MCP tools are available; authentication varies by connector.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, TypingMind personal browser app and PWA; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Starter/Growth/Professional plugins and remote MCP; Professional group restrictions; personal Private MCP Connector route separate; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=Remote server/provider regions depend on configuration; personal local MCP is not a verified Teams local route; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:toolbox, typingmind:typingmind:deep-research, typingmind:typingmind:image, typingmind:typingmind:voice, typingmind:typingmind:overview, typingmind:typingmind:mcp, typingmind:typingmind:pricing, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:restrict-plugin-access.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Deep Research is a configurable search/read/report plugin with separate provider accounts.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams plugin access on Starter/Growth/Professional; Professional for group availability/limits; add_ons=Customer SerpAPI and Firecrawl keys; model API charges; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • web_search Is web search available? [supported]: The Deep Research plugin performs iterative web search and page reading. Sources: typingmind:typingmind:deep-research.
  • admin_toggle Can admins disable it per organisation or group? [supported]: Professional admins restrict the research/search plugin to selected user groups through Plugin Access and Limits. Sources: typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:r2-plan-matrix.
  • search_provider Which search provider handles queries, and where? [partial]: This plugin requires SerpAPI for search and Firecrawl for page retrieval; processing countries for queries/content were not established. Sources: typingmind:typingmind:deep-research.
  • deep_research Is multi-step research with a report available? [supported]: The plugin plans and iterates search/reading into a report, within its documented two-minute execution bound. Sources: typingmind:typingmind:deep-research.
  • web_citations Are web sources cited? [partial]: The research plugin produces a sourced report, but link completeness and citation accuracy were not independently checked. Sources: typingmind:typingmind:deep-research.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:deep-research, typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:r2-plan-matrix.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

The documented automation layer uses agents and plugins rather than an established visual scheduling system.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, TypingMind Teams REST API; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams plugins/agents on Starter/Growth/Professional; Professional external REST API integration; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • workflow_builder Is there a workflow or chain builder? [partial]: Docs describe composing AI interactions with JavaScript/HTTP/MCP plugins and business automation examples. A visual DAG/chain builder was not established. Sources: typingmind:typingmind:overview.
  • scheduled_tasks Can prompts or assistants run on a schedule? [unknown]: Can prompts or assistants run on a schedule? No native recurring scheduler, durable workflow engine or supported event trigger setup was established.
  • event_triggers Can external events start a workflow? [partial]: Professional external REST integration lets an external application call a Teams chat/agent API. This is a developer invocation route, not an established native managed trigger engine. Sources: typingmind:typingmind:api-integration-overview, typingmind:typingmind:r2-plan-matrix.
  • builder_audience Is building aimed at business users, IT or developers? [supported]: Team users use shared agents; technical builders configure JavaScript/HTTP plugins and credentials. Professional custom roles delegate administration, and its API supports developer integrations. Sources: typingmind:typingmind:overview, typingmind:typingmind:roles-and-permissions, typingmind:typingmind:r2-plan-matrix.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:overview, typingmind:typingmind:api-integration-overview, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:roles-and-permissions.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Multi-step tool workflows exist; universal side-effect confirmation and run controls remain unproven.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • agent_mode Is there an agent mode for multi-step tasks? [supported]: The Deep Research plugin repeatedly searches/reads, and automation docs describe tool-driven multistep business actions. Sources: typingmind:typingmind:deep-research, typingmind:typingmind:overview.
  • visible_steps Are steps and tool calls shown? [partial]: The research workflow is described as iterative search and page reading, but a complete visible execution trace for all agents/tools was not established. Sources: typingmind:typingmind:deep-research.
  • side_effect_confirmation Must the user confirm actions with side effects? [unknown]: Must the user confirm actions with side effects? No bounded run verified visible traces, stop behaviour, rollback or mandatory side-effect confirmation for all custom tools.
  • stop_control Can the user stop a running task? [unknown]: Can the user stop a running task? No bounded run verified visible traces, stop behaviour, rollback or mandatory side-effect confirmation for all custom tools.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:deep-research, typingmind:typingmind:overview.

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

Agent cross-checked Support: supported

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

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

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

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:get-conversation, dust:dust:api-keys, dust:dust:upsert, dust:dust:models, dust:dust:credit-management, dust:dust:mcp-server.

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

The Teams REST API creates chat/agent responses with governed api-users.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams REST API; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional API integration; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • chat_api Is there an API for chat and assistants? [supported]: Teams REST endpoints produce model or agent responses, including configured plugins, KB and MCP capabilities. Sources: typingmind:typingmind:api-integration-overview.
  • knowledge_api Can documents be loaded through an API? [unknown]: Can documents be loaded through an API? The retrieved API overview did not establish a supported knowledge-upload API or an MCP server exposing TypingMind itself.
  • api_governance Do audit, budgets and model rules apply to API use? [partial]: An API key creates an api-user subject to the same user restrictions and usage limits. Complete audit coverage, currency budgets and all API routes were not established. Sources: typingmind:typingmind:api-integration-overview.
  • mcp_server Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? The retrieved API overview did not establish a supported knowledge-upload API or an MCP server exposing TypingMind itself.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:api-integration-overview.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

The primary client is a browser app; installable PWAs are documented separately from native apps.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, TypingMind personal browser app and PWA; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams SaaS Starter/Growth/Professional browser chat; PWA installation findings only for personal typingmind.com (licence feature gates separate); add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • web Is a full web client available? [supported]: Teams supplies a branded browser chat interface and separate Admin Panel. Sources: typingmind:typingmind:typingmind-vs-typingmind-team.
  • desktop_apps Windows and macOS apps? [partial]: The personal typingmind.com app has browser-PWA installation instructions for Windows/macOS; this is not evidence of a Teams native desktop app or Teams PWA deployment entitlement. Sources: typingmind:typingmind:install, typingmind:typingmind:r2-personal-bulk-licence.
  • mobile_apps iOS and Android apps with SSO? [partial]: Personal typingmind.com can be added to iOS/Android home screens as a browser PWA. Teams Professional SSO is a separate entitlement; no Teams installable mobile client or mobile SSO fixture was verified. Sources: typingmind:typingmind:install, typingmind:typingmind:r2-personal-bulk-licence, typingmind:typingmind:r2-plan-matrix.
  • browser_extension Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? No MDM packaging/configuration, supported browser sidebar/extension or mobile feature-parity matrix was established.
  • managed_deployment Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? No MDM packaging/configuration, supported browser sidebar/extension or mobile feature-parity matrix was established.
  • client_feature_gaps Which features are missing on mobile? [unknown]: Which features are missing on mobile? No MDM packaging/configuration, supported browser sidebar/extension or mobile feature-parity matrix was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:typingmind-vs-typingmind-team, typingmind:typingmind:install, typingmind:typingmind:r2-personal-bulk-licence, typingmind:typingmind:r2-plan-matrix.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

No public information found Support: not-published

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

WORK-03 Translation and writing

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Configurable model instructions support writing workflows; dedicated translation fidelity is unestablished.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; 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? No whole-document formatting-preserving translation fixture, company glossary engine or Swiss language-quality test was retrieved.
  • translation_engine Which engine translates? [partial]: Writing/translation prompts are handled by the customer-selected LLM; no separate translation engine or formatting-preserving document pipeline was established. Sources: typingmind:typingmind:manage-ai-models, typingmind:typingmind:system-prompts-on-admin-panel.
  • glossaries Are company glossaries supported? [unknown]: Are company glossaries supported? No whole-document formatting-preserving translation fixture, company glossary engine or Swiss language-quality test was retrieved.
  • formality_and_variants Can formality and regional variants (de-CH) be set? [partial]: Global and agent instructions can specify tone and language, but no dedicated de-CH/formality switch or quality guarantee was established. Sources: typingmind:typingmind:system-prompts-on-admin-panel.
  • writing_tools Are dedicated rewrite and proofreading tools available? [partial]: Shared prompts and marketing-writing workflows support rewriting tasks; a dedicated proofreading interface and correction-quality fixture were not established. Sources: typingmind:typingmind:build-a-shared-prompt-library, typingmind:typingmind:ad-creative-generator.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:manage-ai-models, typingmind:typingmind:system-prompts-on-admin-panel, typingmind:typingmind:build-a-shared-prompt-library, typingmind:typingmind:ad-creative-generator.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

GPT Image generation and editing use customer API credentials and controllable plugins.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams plugin access on Starter/Growth/Professional; Professional for group-based image-plugin governance; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:image, typingmind:typingmind:release, typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:terms-of-service.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Dictation, read-aloud and audio-summary workflows are documented; live meetings and Swiss German quality are unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • dictation Can users dictate prompts? [supported]: Dictation uses browser speech recognition or customer OpenAI Whisper, Groq or Azure transcription credentials; Teams admins configure keys. Sources: typingmind:typingmind:voice.
  • read_aloud Can answers be read aloud? [supported]: Browser speech, ElevenLabs or OpenAI TTS reads answers aloud with playback/autoplay controls. Sources: typingmind:typingmind:tts.
  • voice_conversation Is a live voice mode available? [unknown]: Is a live voice mode available? No full-duplex live voice mode, Swiss German audio fixture or native meeting-attendance integration was established.
  • meeting_summaries Are meetings transcribed and summarised? [partial]: The meeting-summarizer workflow uses recorded audio transcription and LLM summaries; Whisper upload is capped at 25MB. No live meeting bot or diarization quality test was established. Sources: typingmind:typingmind:meeting-summarizer, typingmind:typingmind:voice.
  • swiss_german_speech Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? No full-duplex live voice mode, Swiss German audio fixture or native meeting-attendance integration was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:voice, typingmind:typingmind:tts, typingmind:typingmind:meeting-summarizer.

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

Agent cross-checked Support: supported

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: supported

Toolbox executes code locally and produces charts and Office documents; Growth includes Canvas.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Growth/Professional for Canvas; Toolbox on tool-capable models with separate API usage; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

  • data_analysis Can it analyse spreadsheets with executed code? [supported]: Toolbox runs Python/JavaScript in the browser, including tabular analysis libraries. Network is disabled by default; analysis is not a vendor EU code-execution guarantee. Sources: typingmind:typingmind:toolbox.
  • charts Can it produce charts? [supported]: Toolbox supports chart generation with Plotly and Bokeh. Sources: typingmind:typingmind:toolbox.
  • office_file_output Can it create Word, Excel or PowerPoint files? [supported]: Toolbox creates/edits documents, spreadsheets, presentations and PDFs, including Office formats. Sources: typingmind:typingmind:toolbox.
  • canvas_editing Is there a document or canvas editor for iterating on output? [supported]: The Teams plan comparison lists Canvas and Artifacts for Growth and Professional. Sources: typingmind:typingmind:compare-typingmind-team-plans.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:toolbox, typingmind:typingmind:compare-typingmind-team-plans.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Shared agents and prompt libraries are documented, but collaborative project/chat boundaries are not established.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • share_chats Can chats be shared inside the organisation? [unknown]: Can chats be shared inside the organisation? No Teams-specific shared-chat recipient ACL/redaction guarantee, simultaneous multi-person AI conversation or source-permission sharing fixture was established.
  • team_spaces Are shared projects or workspaces available? [partial]: Teams share an agent catalogue and prompt library; project-scoped memory is documented. Shared project membership and cross-user workspace semantics were not established. Sources: typingmind:typingmind:build-a-shared-ai-agent-collection, typingmind:typingmind:build-a-shared-prompt-library, typingmind:typingmind:release.
  • group_chat Can several people chat together with the AI? [unknown]: Can several people chat together with the AI? No Teams-specific shared-chat recipient ACL/redaction guarantee, simultaneous multi-person AI conversation or source-permission sharing fixture was established.
  • share_permission_boundary Does sharing respect the recipient's access to sources? [unknown]: Does sharing respect the recipient's access to sources? No Teams-specific shared-chat recipient ACL/redaction guarantee, simultaneous multi-person AI conversation or source-permission sharing fixture was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:build-a-shared-ai-agent-collection, typingmind:typingmind:build-a-shared-prompt-library, typingmind:typingmind:release.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Multilingual capability is advertised without a verified DACH UI or accessibility matrix.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • ui_languages Which UI languages are offered? [partial]: Teams plan documentation advertises a multilingual chat interface and a public translation collaboration project exists. A complete current language list was not established. Sources: typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:translations.
  • dach_language_quality Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? No complete German/French/Italian UI review, German Admin Panel guarantee, WCAG conformance statement or assistive-technology fixture was retrieved.
  • accessibility_statement Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? No complete German/French/Italian UI review, German Admin Panel guarantee, WCAG conformance statement or assistive-technology fixture was retrieved.
  • admin_ui_languages Is the admin interface available in German? [unknown]: Is the admin interface available in German? No complete German/French/Italian UI review, German Admin Panel guarantee, WCAG conformance statement or assistive-technology fixture was retrieved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:translations.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Teams Professional provides SAML SSO and OAuth/OIDC options.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional identity features; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • sso_protocols Which SSO protocols and identity providers work? [supported]: SAML SSO accepts IdP metadata and multiple connections; OAuth/OIDC includes Microsoft, Google and custom provider configuration. Sources: typingmind:typingmind:sso, typingmind:typingmind:o-auth-2-0.
  • sso_plan Which plan includes SSO? [supported]: The plan comparison places SSO/OAuth and Directory Sync in Professional. Sources: typingmind:typingmind:compare-typingmind-team-plans.
  • mfa Can MFA be enforced? [partial]: The DPA security measures mention MFA and SSO; documented tenant-level enforcement settings and IdP MFA propagation were not verified. Sources: typingmind:typingmind:data-processing-agreement.
  • conditional_access Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? No Entra conditional-access test or verified-domain capture/mandatory login policy was established.
  • domain_capture Can the company claim its email domain? [unknown]: Can the company claim its email domain? No Entra conditional-access test or verified-domain capture/mandatory login policy was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:sso, typingmind:typingmind:o-auth-2-0, typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:data-processing-agreement.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Professional supports SCIM, group sync and JIT; OAuth revocation alone does not remove a seat.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional Directory Sync; distinguish SCIM suspension from OAuth revocation; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • scim Is SCIM provisioning supported? [supported]: SCIM v2 creates, updates and suspends users from a compatible IdP. Sources: typingmind:typingmind:scim.
  • group_sync Are identity-provider groups synced? [supported]: Directory Sync assigns users to corresponding groups received from the identity provider. Sources: typingmind:typingmind:scim.
  • jit_provisioning Are users created at first login? [supported]: OAuth login can create a user on first sign-in and consumes an available seat; creation fails without a free seat. Sources: typingmind:typingmind:o-auth-2-0.
  • deprovisioning What happens to a removed user's data and shared assets? [partial]: SCIM suspends users; separate OAuth docs warn that revoking IdP authorization alone does not remove an existing user, requiring admin removal. Shared asset ownership, deletion and session-revocation timing are not established. Sources: typingmind:typingmind:scim, typingmind:typingmind:o-auth-2-0.
  • seat_assignment Can admins assign and reclaim seats? [partial]: Admins invite/manage users and JIT consumes purchased seats. Exact seat reclamation timing, licence proration and asset transfer were not established. Sources: typingmind:typingmind:invite-team-members, typingmind:typingmind:o-auth-2-0.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:scim, typingmind:typingmind:o-auth-2-0, typingmind:typingmind:invite-team-members.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Custom admin roles and user groups provide delegated management and feature availability controls.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional custom roles, resource groups and usage limits; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:roles-and-permissions, typingmind:typingmind:create-and-manage-user-groups, typingmind:typingmind:restrict-model-access, typingmind:typingmind:restrict-ai-agents-access, typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:r2-plan-matrix.

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

Agent cross-checked Support: partial

Consumption analytics has detailed attribution and exports without message content.

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Teams analytics reports adoption and consumption, including identifiable user breakdowns.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional analytics; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • adoption_dashboard Is there an adoption dashboard? [supported]: Dashboard counts active users, messages, conversations, characters and estimated tokens over a selected period. Sources: typingmind:typingmind:chatbot-analytics.
  • breakdowns Can usage be broken down by group, model, feature and assistant? [supported]: Reporting filters by user, group, model and agent; a complete per-feature cost map was not established. Sources: typingmind:typingmind:chatbot-analytics.
  • export Can usage data be exported? [partial]: Charts can be downloaded; a complete raw usage ledger export format was not established. Sources: typingmind:typingmind:chatbot-analytics.
  • privacy_modes Can per-person reporting be limited or pseudonymised? [unknown]: Can per-person reporting be limited or pseudonymised? No pseudonymised reporting mode or enforceable per-person aggregation threshold was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:chatbot-analytics.

ADM-05 Spend controls and cost allocation

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Admins can inspect estimated consumption and set token/message limits; monetary budgets are unestablished.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional; API charges billed directly by customer providers; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • cost_visibility Can admins see cost or consumption per user and group? [partial]: Analytics shows estimated token and character usage per user/group/model/agent. Customer model bills remain external; reconciled currency cost is not established. Sources: typingmind:typingmind:chatbot-analytics.
  • budgets Can budgets be set per user or group? [partial]: Admins configure reusable token/message/character limits for users/groups and resources, rather than an evidenced currency-denominated budget. Sources: typingmind:typingmind:usage-limits.
  • budget_enforcement Does reaching a budget alert, block or downgrade? [partial]: Users are shown applicable limits, but hard monetary blocking, alerts, downgrade and in-flight overshoot semantics were not established. Sources: typingmind:typingmind:usage-limits.
  • chargeback Can costs be exported per cost centre? [unknown]: Can costs be exported per cost centre? No cost-centre chargeback ledger or exact monetary budget-enforcement documentation was retrieved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:chatbot-analytics, typingmind:typingmind:usage-limits.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Optional chat recording exposes prompts and answers to authorized admins with retention and JSON export.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional chat logs; logging must be enabled; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • admin_events Are admin and security events logged? [unknown]: Are admin and security events logged? No first-party security/admin event catalogue, legal hold or eDiscovery workflow was established.
  • content_logging Can prompts and answers be retained for compliance, and is it configurable? [supported]: Record all chats is opt-in and off by default; authorized Admin Panel roles can view saved user prompts and model responses. Sources: typingmind:typingmind:view-and-export-user-chat-logs, typingmind:typingmind:export-chat-logs, typingmind:typingmind:roles-and-permissions.
  • siem_export Can logs stream to a SIEM or be exported? [partial]: An API exports recorded chats as JSON, last 100 matching conversations per request with date filtering. Native SIEM streaming and complete audit-event export were not established. Sources: typingmind:typingmind:export-chat-logs.
  • ediscovery Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? No first-party security/admin event catalogue, legal hold or eDiscovery workflow was established.
  • log_retention How long are logs kept? [partial]: Admins set chat retention and old records are permanently deleted. A default duration and separate admin/security log retention were not established. Sources: typingmind:typingmind:view-and-export-user-chat-logs.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:view-and-export-user-chat-logs, typingmind:typingmind:export-chat-logs, typingmind:typingmind:roles-and-permissions.

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

No public information found Support: not-published

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

TypingMind / TypingMind Teams

No public information found Support: not-published

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

ADM-08 AI policy and guardrails

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Global instructions can govern chat behaviour, but policy acceptance and violation reporting remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams SaaS global instructions; Professional for group/resource plugin restrictions; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • org_instructions Can admins set organisation-wide instructions? [supported]: Admins set hidden global system instructions, few-shot examples and post-message reminders across chats and agents. Sources: typingmind:typingmind:system-prompts-on-admin-panel.
  • usage_notice Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? No mandatory policy-acceptance record, enforcement-grade content filter or admin policy-hit report was established.
  • content_filters Are content filters configurable? [partial]: Admins configure model-followed instructions; Professional separately restricts plugin availability by group. Neither establishes deterministic PII/content filtering or a policy-enforcement engine. Sources: typingmind:typingmind:system-prompts-on-admin-panel, typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:r2-plan-matrix.
  • violation_reporting Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? No mandatory policy-acceptance record, enforcement-grade content filter or admin policy-hit report was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:system-prompts-on-admin-panel, typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:r2-plan-matrix.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

EU SaaS storage is optional; inference, tools and support are separate residency questions.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • storage_region Where are chats, files and indexes stored? [partial]: Teams offers US and opt-in EU instances. The EU guide names Vercel web hosting and AWS database resources; exact file/index/backup components are not fully enumerated. Sources: typingmind:typingmind:eu-data-center, typingmind:typingmind:privacy-policy.
  • inference_region Where do model calls run, per provider? [supported]: The EU guide explicitly warns model calls may go outside the EU. Customers can choose an EU Azure endpoint or private/local model; this is not an all-provider EU inference promise. Sources: typingmind:typingmind:eu-data-center.
  • backups_logs_region Where are backups, logs and telemetry? [unknown]: Where are backups, logs and telemetry? Backup, telemetry, support-access country matrix and contractual Swiss-only end-to-end processing were not established.
  • support_access_region From where can vendor staff access data? [partial]: The DPA identifies the processor at a Da Nang, Vietnam address and requires need-to-know confidentiality; actual operational staff access countries and restrictions were not established. Sources: typingmind:typingmind:data-processing-agreement.
  • swiss_hosting Is Swiss hosting available? [partial]: Customer self-host can run on operator-selected infrastructure, but no vendor-operated Swiss SaaS region or complete CH-only processing undertaking was established. Sources: typingmind:typingmind:selfhost, typingmind:typingmind:get-started-with-self-host-installation-instruct.
  • residency_plan Which plan or option provides residency? [supported]: The EU instance is an account/instance choice for Teams SaaS. Self-host is a separate quoted annual commercial licence, not the personal licence. Sources: typingmind:typingmind:eu-data-center, typingmind:typingmind:selfhost.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:eu-data-center, typingmind:typingmind:privacy-policy, typingmind:typingmind:data-processing-agreement, typingmind:typingmind:selfhost, typingmind:typingmind:get-started-with-self-host-installation-instruct.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Teams offers multitenant SaaS and a separate commercial self-host package; offline operation is not established.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Marketing language about data staying on customer infrastructure must be read with model, embedding, licence and update egress requirements.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:privacy-policy, typingmind:typingmind:selfhost, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:setup-external-connectors-for-knowledge-base.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

TypingMind asserts no vendor training; customer provider contracts control training and retention.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • vendor_training Does the vendor train on customer content? [supported]: The published policy says TypingMind does not use conversations for AI training. This is a vendor policy assertion, not an independently verified contract-wide audit. Sources: typingmind:typingmind:data-usage-and-model-training-policy.
  • provider_training Do model providers train on it under this product's contracts? [partial]: Teams uses customer provider keys and direct customer provider contracts. The policy summarizes provider-specific training defaults; this pass did not verify every provider contract or free/paid API variant. Sources: typingmind:typingmind:set-up-api-keys, typingmind:typingmind:data-usage-and-model-training-policy.
  • provider_retention How long do model providers keep prompts, including for abuse monitoring? [partial]: The policy discusses provider-dependent abuse monitoring, retention and paid/unpaid distinctions; no uniform current retention duration applies to every customer-selected route. Sources: typingmind:typingmind:data-usage-and-model-training-policy.
  • zero_retention Is zero data retention available, and on which plan? [partial]: A customer may select a provider/endpoint with suitable terms, but no TypingMind-wide ZDR entitlement, plan or complete exception matrix was established. Sources: typingmind:typingmind:data-usage-and-model-training-policy, typingmind:typingmind:eu-data-center.
  • human_review Can provider staff review content? [partial]: TypingMind’s provider summary says OpenAI authorized employees may review API data for abuse/legal compliance. Its Gemini section distinguishes paid no-training from unpaid improvement use and says human reviewers may read/annotate/process inputs and outputs for quality improvement. These are qualified vendor summaries, not verified terms for every customer paid/unpaid endpoint, ZDR approval or actual account. Sources: typingmind:typingmind:data-usage-and-model-training-policy.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:data-usage-and-model-training-policy, typingmind:typingmind:set-up-api-keys, typingmind:typingmind:eu-data-center.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Admins control recorded chat retention; termination deletion/return is contractual without a fixed public completion window.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional for admin chat recording/retention; general service privacy/DPA rights separate from personal/local history; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:export-chat-logs, typingmind:typingmind:privacy-policy, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:view-and-export-user-chat-logs, typingmind:typingmind:data-processing-agreement.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

A public DPA lists processors and transfer measures; vendor legal jurisdiction differs from hosting region.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • subprocessor_list Is a dated sub-processor list published? [partial]: DPA Appendix II publishes a subprocessor list; no standalone dated list revision was visible in the retrieved document. Sources: typingmind:typingmind:data-processing-agreement.
  • subprocessor_countries Which countries do sub-processors operate in? [supported]: The list includes AWS US/Germany, Render US, Vercel US/EU, US services including Sentry/Axiom/Customer.io/Stripe/HelpScout/Mailgun and Paddle US/UK. EU storage does not remove these separate vendor paths. Sources: typingmind:typingmind:data-processing-agreement.
  • change_notification Are customers notified of sub-processor changes? [supported]: DPA 7.8 says the processor will endeavor to give 30 days’ notice of additions/replacements, with 15 days for objections; preserve the qualified notice wording. Sources: typingmind:typingmind:data-processing-agreement.
  • parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: Terms identify Typing Technology Co Ltd with Singapore governing law; the DPA gives a Vietnam processor address. Parent ownership/jurisdiction and actual staff locations were not independently established. Sources: typingmind:typingmind:terms-of-service, typingmind:typingmind:data-processing-agreement.
  • transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [supported]: DPA 7.9 and its SCC appendix provide EU transfer safeguards, subject to actual processing configuration; a Swiss-specific addendum was not established. Sources: typingmind:typingmind:data-processing-agreement.
  • government_access_policy Is there a published government-access or transparency policy? [partial]: The privacy policy allows disclosures for authorized legal requests; no separate transparency report or detailed government-request policy was retrieved. Sources: typingmind:typingmind:privacy-policy.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:data-processing-agreement, typingmind:typingmind:terms-of-service, typingmind:typingmind:privacy-policy.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

A public GDPR DPA and Singapore-law business terms are available; Swiss and sector-specific undertakings remain gaps.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • dpa Is a DPA available, and is it negotiable? [partial]: A public fillable GDPR Article 28 DPA names the processor, security measures and SCCs. Whether bespoke negotiation is available was not established. Sources: typingmind:typingmind:data-processing-agreement.
  • revdsg_gdpr Does the DPA cover revDSG and GDPR? [partial]: The DPA expressly addresses GDPR and SCCs; explicit revised Swiss FADP/revDSG coverage was not established. Sources: typingmind:typingmind:data-processing-agreement.
  • governing_law Which law and court govern the contract? [supported]: The September 17, 2026 Terms use Singapore law, with SIAC English-language business arbitration; the DPA SCC appendix separately uses EU exporter-state law/forum where applicable. Sources: typingmind:typingmind:terms-of-service, typingmind:typingmind:data-processing-agreement.
  • ai_act_materials Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? No EU AI Act compliance package, FINMA outsourcing materials or dedicated professional-secrecy agreement was retrieved.
  • sector_materials Are FINMA or other sector materials provided? [unknown]: Are FINMA or other sector materials provided? No EU AI Act compliance package, FINMA outsourcing materials or dedicated professional-secrecy agreement was retrieved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:data-processing-agreement, typingmind:typingmind:terms-of-service.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

The self-host page claims SOC 2 Type II. A report with auditor, period and covered-service scope was not retrieved, and other attestations remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Commercial self-hosted TypingMind Teams server; version=Public self-host page retrieved 2026-10-26; no certificate verified; plan=Commercial Teams self-host marketing assurance claim; no customer report or SaaS certificate scope inferred; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Vendor assertion only. No independently verified report, certificate scope or validity was accessed; trust.typingmind.com returned HTTP 403.
  • iso_27001 ISO 27001 with scope and validity? [unknown]: ISO 27001 with scope and validity? Trust Center access returned HTTP 403. The retrieved DPA security appendix is not an ISO/SOC/C5 certificate. Issuer, service scope, validity/report period, report-access process and independent penetration-test summary were not retrieved.
  • soc2 SOC 2 type, period and covered service? [partial]: The vendor advertises SOC 2 Type II on the Teams self-host page. Auditor, report period, covered entity/service and applicability to a customer-operated deployment are unverified. Sources: typingmind:typingmind:r4-soc2-selfhost-claim.
  • c5 BSI C5 attestation? [unknown]: BSI C5 attestation? Trust Center access returned HTTP 403. The retrieved DPA security appendix is not an ISO/SOC/C5 certificate. Issuer, service scope, validity/report period, report-access process and independent penetration-test summary were not retrieved.
  • other_certifications Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Trust Center access returned HTTP 403. The retrieved DPA security appendix is not an ISO/SOC/C5 certificate. Issuer, service scope, validity/report period, report-access process and independent penetration-test summary were not retrieved.
  • report_access How can customers obtain reports? [unknown]: How can customers obtain reports? Trust Center access returned HTTP 403. The retrieved DPA security appendix is not an ISO/SOC/C5 certificate. Issuer, service scope, validity/report period, report-access process and independent penetration-test summary were not retrieved.
  • pentest Are independent penetration test summaries available? [unknown]: Are independent penetration test summaries available? Trust Center access returned HTTP 403. The retrieved DPA security appendix is not an ISO/SOC/C5 certificate. Issuer, service scope, validity/report period, report-access process and independent penetration-test summary were not retrieved.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: typingmind:typingmind:r4-soc2-selfhost-claim.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Encryption and private self-host infrastructure are documented without a SaaS customer-key guarantee.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server, TypingMind personal browser app and PWA; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams SaaS US/EU storage; separately quoted annual Teams self-host network controls; personal local-key claims explicitly separate; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Teams OpenAI route: server requests using centrally configured admin keys. Personal direct-browser/local-key assertions are not inherited by Teams.
  • The generic policy versus Teams FAQ scope discrepancy remains visible pending policy clarification.
  • encryption_at_rest Is data encrypted at rest? [partial]: The EU guide says stored information is encrypted; exact cipher, key ownership and component coverage were not established. Personal optional cloud encryption is a different surface. Sources: typingmind:typingmind:eu-data-center, typingmind:typingmind:privacy-policy.
  • customer_managed_keys Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? No Teams SaaS customer-managed/held encryption-key option or complete private-connectivity configuration was established.
  • private_networking Is private connectivity or IP restriction available? [partial]: Self-host permits customer network placement; localhost/private custom endpoints require ALLOW_UNSAFE_USER_ENDPOINTS. SaaS private links, IP allowlisting and private model routing were not established. Sources: typingmind:typingmind:get-started-with-self-host-installation-instruct.
  • tenant_isolation How are customers separated in shared SaaS? [partial]: The privacy policy calls Teams multitenant; logical isolation implementation and independent tenant-boundary testing were not established. Sources: typingmind:typingmind:privacy-policy.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:eu-data-center, typingmind:typingmind:privacy-policy, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:r2-teams-server-route.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

General GDPR confidentiality and configurable admin/model access are documented; a specific §203 or Art321 undertaking is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams SaaS Professional chat governance and separately quoted self-host licence; ordinary public DPA; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US/EU SaaS or customer self-host placement; customer provider contracts separate; os=not specified.

Limitations

  • DPA confidentiality, direct provider contracts and self-host placement alone do not establish professional-secrecy suitability.
  • 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]: DPA7.4(c) limits personnel access and requires confidentiality/statutory duties. No signed/signon §203 StGB or Art321 StGB professional-secrecy undertaking was retrieved; ordinary GDPR confidentiality is not treated as that agreement.
  • subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [unknown]: DPA7.8(d)-(e) requires substantially equivalent data-protection obligations and allows a redacted subprocessor agreement on request. A dedicated professional-secrecy undertaking flowing to subprocessors was not established.
  • secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: No specific professional-secrecy package/add-on or SaaS/self-host plan entitlement was established. Customer-operated infrastructure and the commercial self-host licence do not by themselves prove that undertaking.
  • content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: SaaS authorized personnel may access data only as needed under the DPA; customer admins with chat-log permission may inspect recorded prompts/answers when logging is enabled. Selected customer API providers process content; self-host placement changes operator access but model/embedding/blob routes remain relevant. A complete plaintext support/subprocessor/provider human-access matrix was not retrieved. Sources: typingmind:typingmind:dpa-confidentiality, typingmind:typingmind:view-and-export-user-chat-logs, typingmind:typingmind:roles-and-permissions, typingmind:typingmind:set-up-api-keys, typingmind:typingmind:get-started-with-self-host-installation-instruct.
  • secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Public DPA, security appendix, processor list and self-host data-flow guides were retrieved. Targeted first-party search did not establish a professional-secrecy contract template, DE/CH-specific data-flow addendum or professional-body guidance.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:dpa-confidentiality, typingmind:typingmind:view-and-export-user-chat-logs, typingmind:typingmind:roles-and-permissions, typingmind:typingmind:set-up-api-keys, typingmind:typingmind:get-started-with-self-host-installation-instruct.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Teams subscriptions, personal one-time licences and self-host annual quotes are separate cost structures.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server, TypingMind personal browser app and PWA; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams SaaS Starter/Growth/Professional/quoted Business; separate annual Teams self-host quote; personal Standard/Extended/Premium one-time licences and separate bulk pack; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:pricing, typingmind:typingmind:cloud-host-vs-self-host, typingmind:typingmind:r2-personal-bulk-licence, typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:how-knowledge-base-works-in-typingmind-team, typingmind:typingmind:selfhost, typingmind:typingmind:deep-research, typingmind:typingmind:set-up-api-keys.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

A conditional Professional monthly licence-plus-BYOK floor is calculable; Business and self-host totals remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Conditional documented Professional monthly list route; not a large-scale quote; add_ons=Model usage proxy; other add-ons unknown; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Known price floor plus explicitly unpriced parts; no complete year-one TCO or negotiated price claim.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:pricing, typingmind:typingmind:openai-price, typingmind:typingmind:openai-model, typingmind:typingmind:fx, typingmind:typingmind:set-up-api-keys, typingmind:typingmind:selfhost, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:deep-research.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Teams SaaS has a self-serve trial; self-host evaluation is a separate sales-gated route.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:pricing, typingmind:typingmind:typingmind-vs-typingmind-team, typingmind:typingmind:cloud-host-vs-self-host, typingmind:typingmind:selfhost.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Cloud supports monthly/annual subscriptions; self-host is annual and commercial.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Starter/Growth/Professional monthly or annual SaaS; quoted Business and separate annual commercial Teams self-host; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • minimum_commitment What seat or spend minimum applies? [supported]: Cloud plan cards and self-host licence include five users. Business advertises a USD18,700/year starting quote; no all-scenario minimum was established. Sources: typingmind:typingmind:pricing, typingmind:typingmind:selfhost.
  • contract_length What contract lengths are offered? [supported]: Cloud-host vs Self-host explicitly describes monthly SaaS and annual quoted self-host subscriptions; the current SaaS landing also offers annual billing. Teams Terms specify renewal of the agreed term. Sources: typingmind:typingmind:cloud-host-vs-self-host, typingmind:typingmind:pricing, typingmind:typingmind:terms-of-service.
  • cancellation How can the contract be cancelled or reduced? [partial]: Cloud billing settings manage subscriptions; Terms make fixed-term Teams/self-host fees generally nonrefundable. Exact mid-term seat-reduction proration and notice deadline were not established. Sources: typingmind:typingmind:manage-your-subscription, typingmind:typingmind:terms-of-service.
  • local_invoicing Can it be invoiced in CHF or EUR from a European entity? [unknown]: Can it be invoiced in CHF or EUR from a European entity? CHF/EUR invoicing from a European entity, tax handling and bespoke contract negotiation were not established.
  • transparency_class Is pricing transparent, partial, quote-only or unknown? [supported]: Partial: public small-plan SaaS seat pricing with separate API bills, quote-only Business and self-host, and unpriced optional support/knowledge services. Sources: typingmind:typingmind:pricing, typingmind:typingmind:selfhost.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:pricing, typingmind:typingmind:selfhost, typingmind:typingmind:cloud-host-vs-self-host, typingmind:typingmind:terms-of-service, typingmind:typingmind:manage-your-subscription.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

TypingMind is commercial proprietary software; self-host access is not an open-source licence.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind personal browser app and PWA, TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Commercial personal licence, separate bulk pack, Teams SaaS Starter/Growth/Professional and separate commercial Teams self-host licence; personal user/device allowance unverified; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • The personal user/device allowance is unknown. No five-user or one-user allowance is published as a reconciled finding; Teams and annual self-host seat rights remain separate.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:end-user-license-agreement, typingmind:typingmind:terms-of-service, typingmind:typingmind:selfhost, typingmind:typingmind:custom-branding, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:r2-personal-bulk-licence, typingmind:typingmind:compare-typingmind-team-plans.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Recorded Teams chats have a JSON API export; generic app exports do not prove full organizational portability.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams REST API, TypingMind Teams SaaS chat and Admin Panel, TypingMind personal browser app and PWA; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional recorded-chat API/export; separate personal app JSON backups (feature licence gate not mapped); add_ons=Professional chat recording enabled before export; authorized API key; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • chat_export Can admins export all chats? [partial]: Professional includes chat logs/data export and API integration. Authorized admins export recorded conversation JSON via the API, last100 matching conversations/request plus date filters; complete tenant history and pagination were not tested. Sources: typingmind:typingmind:export-chat-logs, typingmind:typingmind:r2-plan-matrix.
  • assistant_export Can assistants and prompts be exported in a reusable format? [partial]: The personal-app backup guide exports user agents, prompts/plugins/model settings as JSON. That is not evidence of bulk centrally managed Teams asset export; its personal feature gate is not mapped here. Sources: typingmind:typingmind:export-import-data.
  • knowledge_export Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? A bulk reusable organization KB/source export and complete centrally managed agent/prompt export were not established.
  • export_format Are formats documented and machine-readable? [supported]: Professional recorded-chat API responses are JSON; the separate personal backup/import also uses JSON. Formats do not establish complete organization portability. Sources: typingmind:typingmind:export-chat-logs, typingmind:typingmind:export-import-data, typingmind:typingmind:r2-plan-matrix.
  • post_termination_window How long can data be retrieved after termination? [partial]: The DPA allows deletion/return at termination but does not publish a fixed retrieval grace period. Terms allow content deletion after termination. Sources: typingmind:typingmind:data-processing-agreement, typingmind:typingmind:terms-of-service.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:export-chat-logs, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:export-import-data, typingmind:typingmind:data-processing-agreement, typingmind:typingmind:terms-of-service.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Email support is documented; self-host SLA is optional and public incident data was inaccessible.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Starter/Growth/Professional public email support/material; separate quoted annual Teams self-host Enterprise Support add-on; add_ons=Commercial Teams self-host Enterprise Support (SLA/SLO/dedicated queue), separately quoted; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Self-host support package is distinct from SaaS support/onboarding; no public numerical uptime/credit or adoption-service tariff established.
  • support_channels Which support channels are available on each plan? [supported]: Cloud plan comparison lists email support. Self-host dedicated support/SLA is a separate option; exact Business response targets were not established. Sources: typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:selfhost.
  • support_languages Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? No German/French/Italian support commitment, DACH/Swiss support entity or public credit-bearing SLA terms were retrieved.
  • regional_presence Is there a DACH or Swiss entity, team or partner? [unknown]: Is there a DACH or Swiss entity, team or partner? No German/French/Italian support commitment, DACH/Swiss support entity or public credit-bearing SLA terms were retrieved.
  • uptime_sla Is there an uptime SLA with credits? [partial]: Self-host marketing offers a paid SLA/SLO/dedicated-support add-on; a public uptime percentage, credit schedule or standard SaaS SLA was not retrieved. Sources: typingmind:typingmind:selfhost.
  • status_page Is there a public status page with history? [partial]: A public status site loads but returned an error fetching status data in this pass, so history and measured availability are unknown. Sources: typingmind:typingmind:status.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:selfhost, typingmind:typingmind:status, typingmind:typingmind:pricing, typingmind:typingmind:cloud-host-vs-self-host.

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

Agent cross-checked Support: partial

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

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

Limitations

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

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

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Public setup guides and role examples exist; managed adoption services are not fully specified.

Availability: generally-available · Delivery: native
Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Starter/Growth/Professional public email support/material; separate quoted annual Teams self-host Enterprise Support add-on; add_ons=Commercial Teams self-host Enterprise Support (SLA/SLO/dedicated queue), separately quoted; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified.

Limitations

  • Self-host support package is distinct from SaaS support/onboarding; no public numerical uptime/credit or adoption-service tariff established.
  • onboarding_service Is guided onboarding included? [unknown]: Is guided onboarding included? No included guided-onboarding scope, multilingual training commitment or champion/adoption programme was established.
  • user_training Is end-user training offered, in which languages? [partial]: Public documentation teaches setup, use, agents and workflows. A contracted live user-training service and languages were not established. Sources: typingmind:typingmind:typingmind-vs-typingmind-team, typingmind:typingmind:overview.
  • use_case_library Are role-based use cases and templates provided? [supported]: The documentation provides marketing ad creation, meeting-summary and business automation examples and role/permission examples. Sources: typingmind:typingmind:ad-creative-generator, typingmind:typingmind:meeting-summarizer, typingmind:typingmind:overview, typingmind:typingmind:roles-and-permissions.
  • adoption_programme Is there a champion or adoption programme? [unknown]: Is there a champion or adoption programme? No included guided-onboarding scope, multilingual training commitment or champion/adoption programme was established.
  • service_cost Which services cost extra? [partial]: Self-host dedicated support/SLA is an optional extra; onboarding/training/adoption-program prices were not established. Sources: typingmind:typingmind:selfhost.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:typingmind-vs-typingmind-team, typingmind:typingmind:overview, typingmind:typingmind:ad-creative-generator, typingmind:typingmind:meeting-summarizer, typingmind:typingmind:roles-and-permissions, typingmind:typingmind:selfhost, typingmind:typingmind:pricing, typingmind:typingmind:cloud-host-vs-self-host.

Sources

  1. Auto models and the model picker dust:dust:models

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

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

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

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

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

  3. Dust changelog dust:dust:changelog

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

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

  4. Conversation Files dust:dust:files

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

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

  5. Dust Pricing dust:dust:pricing

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

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

  6. Set up API Keys typingmind:typingmind:set-up-api-keys

    Teams admins preset customer provider keys; end users cannot enter their own key in the chat interface.

    Set up API Keys · documented · Source date not stated · Retrieved 2026-10-21

  7. Manage AI Models typingmind:typingmind:manage-ai-models

    The app has a per-chat model selector and configurable model endpoints; provider examples are not a complete current catalogue.

    Manage AI Models · documented · Source date not stated · Retrieved 2026-10-21

  8. TypingMind changelog typingmind:typingmind:release

    Dated releases include Teams memory administration, new models, browser-local code and office outputs, and GPT Image editing.

    2026-10-14 Memory for Teams and new models; 2026-10-13 Toolbox; 2026-10-02 image editing · documented · Source date 2026-10-14 · Retrieved 2026-10-21

  9. Restrict Model access typingmind:typingmind:restrict-model-access

    Teams admins restrict available models by user group.

    Restrict Model access · documented · Source date not stated · Retrieved 2026-10-21

  10. Chat with documents typingmind:typingmind:chat-with-documents

    Uploads accept PDF, Markdown, CSV, XLSX, TXT, DOCX, JSON and HTML, with document text added as chat context.

    Chat with documents · documented · Source date not stated · Retrieved 2026-10-21

  11. Voice input typingmind:typingmind:voice

    Browser speech recognition or customer OpenAI, Groq and Azure transcription keys enable dictation; uploaded Whisper recordings have a 25MB limit.

    Transcription models and Teams configuration · documented · Source date not stated · Retrieved 2026-10-21

  12. Azure OpenAI typingmind:typingmind:azure-openai

    A customer Azure OpenAI endpoint and deployment can be configured.

    Azure OpenAI · documented · Source date not stated · Retrieved 2026-10-21

  13. TypingMind Teams pricing typingmind:typingmind:pricing

    Annual selected prices display USD83/166/249 per month for Starter/Growth/Professional, five users, USD8 extra seats; Business starts USD18,700/year.

    Annual selector, plan cards, Add-ons and Business card · documented · Source date not stated · Retrieved 2026-10-21

  14. Self-host installation instructions typingmind:typingmind:get-started-with-self-host-installation-instruct

    A NodeJS service needs MySQL 8, optional PostgreSQL 16 pgvector KB, OpenAI embeddings and S3-compatible blobs; private endpoints are blocked by default.

    Self-host installation instructions · documented · Source date not stated · Retrieved 2026-10-21

  15. Toolbox typingmind:typingmind:toolbox

    A free built-in plugin executes Python and JavaScript locally in the browser with network disabled by default and creates Office/PDF files and charts.

    Local execution, network control and file capabilities · documented · Source date not stated · Retrieved 2026-10-21

  16. Teams API Keys Setup typingmind:typingmind:r2-teams-custom-models

    Teams-specific instructions name Azure OpenAI, Hugging Face and Ollama custom-model setup in the Admin Panel; this is distinct from personal local-server guides.

    Use with other models; Add Custom Model in Admin Panel · documented · Source date not stated · Retrieved 2026-10-21

  17. Compare Teams Plans typingmind:typingmind:r2-plan-matrix

    All SaaS tiers list custom models and shared resources; Growth adds RAG/projects; Professional adds roles, restrictions, logs and external API integration.

    Full Feature Comparison · documented · Source date not stated · Retrieved 2026-10-21

  18. AWS Bedrock Anthropic typingmind:typingmind:r3-custom-admin-bedrock

    The Custom Admin route configures Claude via Bedrock with customer AWS access/secret keys, region and approved model access; current model and commercial tier coverage are not enumerated.

    Custom Admin restriction and steps 2-4, including custom.typingmind.com/manage · documented · Source date not stated · Retrieved 2026-10-21

  19. Ollama typingmind:typingmind:ollama

    A customer Ollama model endpoint can be added; network accessibility must be configured.

    Ollama · documented · Source date not stated · Retrieved 2026-10-21

  20. LM Studio typingmind:typingmind:lmstudio

    Customer local LM Studio can supply an OpenAI-compatible model endpoint.

    LM Studio · documented · Source date not stated · Retrieved 2026-10-21

  21. Cloud host vs self host typingmind:typingmind:cloud-host-vs-self-host

    SaaS has a self-serve 14-day trial; self-host has no free trial and carries a quoted annual licence and update/support conditions.

    Cloud host vs self host · documented · Source date not stated · Retrieved 2026-10-21

  22. Model access tiers dust:dust:tiers

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

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

  23. Spaces management dust:dust:spaces

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

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

  24. Credits dust:dust:credits

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

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

  25. Credit management dust:dust:credit-management

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

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

  26. Usage limits typingmind:typingmind:usage-limits

    Reusable limit groups cover messages, characters and tokens by period, applicable globally or to users, groups, models, agents and plugins.

    Usage limits · documented · Source date not stated · Retrieved 2026-10-21

  27. Connect Knowledge Base to your AI Agents typingmind:typingmind:connect-knowledge-base-to-your-ai-agents

    Tagged knowledge is assigned to agents through Knowledge Base Access.

    Connect Knowledge Base to your AI Agents · documented · Source date not stated · Retrieved 2026-10-21

  28. Roles and Permissions typingmind:typingmind:roles-and-permissions

    Owners delegate granular Admin Panel permissions through custom roles; group-role assignment is described as coming soon.

    Roles and Permissions · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  30. Computer dust:dust:computer

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

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

  31. Google Drive dust:dust:drive

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

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

  32. Search data sources dust:dust:search

    Agents search selected knowledge sources and retrieve relevant document context.

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

  33. How Knowledge Base works in TypingMind Team typingmind:typingmind:how-knowledge-base-works-in-typingmind-team

    The early-access KB uses RAG, about 3,000-word chunks and up to five retrieved chunks, 50MB uploads and daily source refresh.

    Early Access; indexing; limits and refresh · documented · Source date 2025-11-10 · Retrieved 2026-10-21

  34. Training Files vs Knowledge Base typingmind:typingmind:training-files-vs-knowledge-base

    Agent training-file text is injected into system context; the separate KB retrieves chunks and advertises multiple source integrations.

    Training Files vs Knowledge Base · documented · Source date not stated · Retrieved 2026-10-21

  35. Get started with Knowledge Base typingmind:typingmind:get-started-with-knowledge-base

    Admins add documents or connected sources, tag data, bind tags to agents and optionally show clickable references.

    Get started with Knowledge Base · documented · Source date not stated · Retrieved 2026-10-21

  36. Restrict AI Agents access typingmind:typingmind:restrict-ai-agents-access

    Agent access and usage can be limited for groups.

    Restrict AI Agents access · documented · Source date not stated · Retrieved 2026-10-21

  37. Access Controls and Permissions dust:dust:permissions

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

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

  38. Microsoft dust:dust:microsoft

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

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

  39. Confluence dust:dust:confluence

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

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

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

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

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

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

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

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

  42. Adding an MCP Server dust:dust:tools

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

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

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

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

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

  44. Connect with Notion pages typingmind:typingmind:connect-with-your-notion-pages

    Admins select Notion pages/databases for an instance, with initial sync taking a few minutes.

    Connect with Notion pages · documented · Source date not stated · Retrieved 2026-10-21

  45. Self-host external knowledge connectors typingmind:typingmind:setup-external-connectors-for-knowledge-base

    Optional self-host KB external connectors need separate OAuth configuration and Firecrawl for web scraping.

    Self-host external knowledge connectors · documented · Source date not stated · Retrieved 2026-10-21

  46. LLM Automated Workflows overview typingmind:typingmind:overview

    JavaScript, HTTP and MCP plugins can perform multi-step business actions; example flows are not evidence of a scheduler.

    LLM Automated Workflows overview · documented · Source date not stated · Retrieved 2026-10-21

  47. MCP in TypingMind typingmind:typingmind:mcp

    The client connects remote HTTP or local-command MCP servers, supports OAuth and individual tool controls, and separates Teams sessions per user/chat.

    Remote and local connectors; Teams sessions; tool control · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  49. Dust Security dust:dust:security

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

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

  50. EU data center typingmind:typingmind:eu-data-center

    EU instances use Vercel and AWS EU storage but model API calls may leave the EU.

    EU data center · documented · Source date not stated · Retrieved 2026-10-21

  51. Deep-dive Agent dust:dust:deep

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

    Research flow; citations; limitations · documented · Source date not stated · Retrieved 2026-10-21

  52. System Prompts on Admin Panel typingmind:typingmind:system-prompts-on-admin-panel

    Global system instructions, few-shot examples and post-message reminders apply across chats and agents.

    System Prompts on Admin Panel · documented · Source date not stated · Retrieved 2026-10-21

  53. Agent Memory dust:dust:memory

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

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

  54. Create your first agent dust:dust:builder

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

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

  55. Memory typingmind:typingmind:memory

    Users can enable memory globally or for an agent/project and inspect saved memories.

    Memory · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  57. Build a Shared AI Agent collection typingmind:typingmind:build-a-shared-ai-agent-collection

    Admins create an agent collection exposed in the team chat interface and control group access.

    Build a Shared AI Agent collection · documented · Source date not stated · Retrieved 2026-10-21

  58. Build a Shared Prompt Library typingmind:typingmind:build-a-shared-prompt-library

    Admins can publish reusable prompts to the team interface.

    Build a Shared Prompt Library · documented · Source date not stated · Retrieved 2026-10-21

  59. Restrict Plugin access typingmind:typingmind:restrict-plugin-access

    Plugins can be made available or unavailable to specified user groups.

    Restrict Plugin access · documented · Source date not stated · Retrieved 2026-10-21

  60. Deep Research plugin typingmind:typingmind:deep-research

    A multi-step search/read/report plugin requires customer SerpAPI and Firecrawl keys and has a two-minute execution limit.

    Requirements and operation · documented · Source date not stated · Retrieved 2026-10-21

  61. GPT Image 2.5 plugin typingmind:typingmind:image

    The plugin generates and edits images using the customer OpenAI API route.

    Image generation, editing and API key · documented · Source date not stated · Retrieved 2026-10-21

  62. Web Search & Browse dust:dust:web

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

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

  63. Triggers dust:dust:triggers

    Agents can run automatically from schedule or event triggers.

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

  64. Schedules dust:dust:schedules

    Agents can run on recurring schedules.

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

  65. Webhooks dust:dust:webhooks

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

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

  66. API integration overview typingmind:typingmind:api-integration-overview

    REST chat/agent API uses API-key-associated api-users subject to user restrictions and usage limits.

    API integration overview · documented · Source date not stated · Retrieved 2026-10-21

  67. Pods overview dust:dust:pods

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

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

  68. API keys dust:dust:api-keys

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

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

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

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

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

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

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

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

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

    The API retrieves accessible conversation messages with pagination.

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

  72. Browser Extension dust:dust:browser

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

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

  73. TypingMind vs TypingMind Team typingmind:typingmind:typingmind-vs-typingmind-team

    The personal app and Teams with an Admin Panel, managed users and centrally preset keys are separate offerings.

    TypingMind vs TypingMind Team · documented · Source date not stated · Retrieved 2026-10-21

  74. Install TypingMind app typingmind:typingmind:install

    Installation uses browser PWA technology; browser storage remains separate and this does not establish native app-store clients.

    PWA installation on Windows, Mac, iOS and Android · documented · Source date not stated · Retrieved 2026-10-21

  75. TypingMind personal licence checkout typingmind:typingmind:r2-personal-bulk-licence

    Personal licences normally cover five devices for one user; a separate shareable Bulk License is offered, without establishing a Teams Admin Panel entitlement.

    How many devices/users? and Team/Bulk License FAQ; self-host FAQ · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  76. Dust in Teams dust:dust:teams

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

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

  77. Ad creative generator workflow typingmind:typingmind:ad-creative-generator

    Public examples include marketing automation built with AI and plugins.

    Ad creative generator workflow · documented · Source date not stated · Retrieved 2026-10-21

  78. Image Generation dust:dust:images

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

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

  79. Terms of Service typingmind:typingmind:terms-of-service

    Typing Technology Co Ltd contracts under Singapore law and business SIAC arbitration; Teams renews and self-host code has restricted licence rights.

    Sections 1, 4-6, 13 and 16 · documented · Source date 2026-09-17 · Retrieved 2026-10-21

  80. Voice and sound generation dust:dust:speech

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

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

  81. Meeting transcripts dust:dust:meetings

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

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

  82. Text to speech typingmind:typingmind:tts

    Answers can be read aloud using browser speech, ElevenLabs or OpenAI TTS.

    Browser, ElevenLabs and OpenAI options · documented · Source date not stated · Retrieved 2026-10-21

  83. Meeting summarizer workflow typingmind:typingmind:meeting-summarizer

    The guide offers an audio-transcription and summarisation workflow, not a demonstrated meeting bot.

    Meeting summarizer workflow · documented · Source date not stated · Retrieved 2026-10-21

  84. Frames overview dust:dust:frames

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

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

  85. Compare TypingMind Team plans typingmind:typingmind:compare-typingmind-team-plans

    The comparison lists monthly USD99/199/299, five users plus USD8 additional users, Growth knowledge and Professional identity/governance.

    Compare TypingMind Team plans · documented · Source date not stated · Retrieved 2026-10-21

  86. Pod conversations dust:dust:pod-chats

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

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

  87. Translation collaboration typingmind:typingmind:translations

    A translation project exists, but the retrieved page does not establish completeness of German, French, Italian or Admin Panel translations.

    Multilingual app translation project · documented · Source date not stated · Retrieved 2026-10-21

  88. Single Sign-On dust:dust:sso

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

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

  89. Dust for Enterprise dust:dust:enterprise

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

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

  90. Single Sign-On (SSO) typingmind:typingmind:sso

    SAML identity-provider metadata, entity ID and reply URL are configured in Teams.

    SAML configuration and multiple connections · documented · Source date not stated · Retrieved 2026-10-21

  91. OAuth 2.0 typingmind:typingmind:o-auth-2-0

    OAuth/OIDC supports built-in Microsoft and Google logins and JIT seats; revoking IdP authorization alone does not remove the user.

    OAuth 2.0 · documented · Source date not stated · Retrieved 2026-10-21

  92. Data Processing Agreement typingmind:typingmind:data-processing-agreement

    The public GDPR processor form includes confidentiality, subprocessor flow-down, SCC transfers and customer-choice deletion or return.

    Clauses 7.4, 7.8-7.10 and Appendices I-IV · documented · Source date not stated · Retrieved 2026-10-21

  93. Users and groups provisioning dust:dust:provision

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

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

  94. Seat management dust:dust:seats

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

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

  95. Directory Sync (SCIM v2) typingmind:typingmind:scim

    SCIM sync creates and suspends users, updates profiles and assigns corresponding groups from the IdP.

    Create, update, suspend users and groups · documented · Source date not stated · Retrieved 2026-10-21

  96. Invite team members typingmind:typingmind:invite-team-members

    Teams admins invite members to the instance and manage seats.

    Invite team members · documented · Source date not stated · Retrieved 2026-10-21

  97. Create and manage user groups typingmind:typingmind:create-and-manage-user-groups

    Groups control access and are usable for limits and analytics.

    Create and manage user groups · documented · Source date not stated · Retrieved 2026-10-21

  98. Analytics dust:dust:analytics

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

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

  99. Chatbot analytics typingmind:typingmind:chatbot-analytics

    Reporting covers active users, messages, conversations, estimated tokens and characters, with model/agent/group/user breakdowns and chart downloads.

    Chatbot analytics · documented · Source date not stated · Retrieved 2026-10-21

  100. Audit Logs dust:dust:audit

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

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

  101. View and export user chat logs typingmind:typingmind:view-and-export-user-chat-logs

    Opt-in Record all chats exposes user prompts and responses to authorized admins and configurable retention permanently deletes old records.

    View and export user chat logs · documented · Source date not stated · Retrieved 2026-10-21

  102. Export chat logs typingmind:typingmind:export-chat-logs

    Chat logging is off by default; the API exports JSON conversation content and dates, limited to the last 100 matching conversations per request.

    Export chat logs · documented · Source date not stated · Retrieved 2026-10-21

  103. Dust Platform Privacy Policy dust:dust:privacy

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

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

  104. TypingMind Teams Self Host typingmind:typingmind:selfhost

    Commercial self-host requires an annual quote, includes five users, uses compiled/minified code, checks licence/updates externally and can use customer model endpoints.

    Technical requirements, licensing, network, updates and pricing FAQ · documented · Source date not stated · Retrieved 2026-10-21

  105. Privacy policy typingmind:typingmind:privacy-policy

    The policy distinguishes personal local storage from Teams multitenant server storage, and lists inactive unpaid account deletion.

    Storage scope, API keys and section on account deletion · documented · Source date 2026-09-19 · Retrieved 2026-10-21

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

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

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

  107. Data Usage and Model Training Policy typingmind:typingmind:data-usage-and-model-training-policy

    The vendor says it does not train on conversations; customers contract directly with model providers and their retention/training terms vary.

    TypingMind role and provider API comparison · vendor-claimed · Source date not stated · Retrieved 2026-10-21

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

    Users can delete or rename their conversations.

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

  109. TypingMind Teams self-host typingmind:typingmind:r4-soc2-selfhost-claim

    The self-host marketing page claims SOC 2 Type II; no auditor, reporting period, covered legal entity or report was retrieved. This is a vendor claim rather than verified attestation.

    Maximum security, SOC 2 Type II badge; updates and licence checks · vendor-claimed · Source date not stated · Retrieved 2026-10-26

  110. TypingMind Teams pricing FAQ typingmind:typingmind:r2-teams-server-route

    The Teams-specific FAQ says users do not see the key and OpenAI requests are sent from the Teams server.

    Do my users see my OpenAI API key? · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  111. TypingMind DPA confidentiality typingmind:typingmind:dpa-confidentiality

    Staff have need-to-know confidentiality duties and subprocessor contracts carry substantially the same data-protection obligations; a specific professional-secrecy agreement is not established.

    7.4(c),7.8(d)-(e); AppendixII andIII · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  113. OpenAI API pricing typingmind:typingmind:openai-price

    gpt-6-luna Standard input is USD0.10 and output USD0.50 per million tokens, excluding cache and optional regional uplifts.

    Standard short-context gpt-6-luna row · documented · Source date not stated · Retrieved 2026-10-21

  114. GPT-6 Luna model documentation typingmind:typingmind:openai-model

    Reasoning effort none is the lowest option; the shared cost proxy does not use reasoning tokens.

    Reasoning effort and API support · documented · Source date not stated · Retrieved 2026-10-21

  115. ECB reference exchange rates typingmind:typingmind:fx

    EUR1 equals USD1.1215 and CHF0.9237.

    Cube time=2026-10-20 · documented · Source date 2026-10-20 · Retrieved 2026-10-21

  116. Manage your subscription typingmind:typingmind:manage-your-subscription

    Cloud customers manage the recurring subscription through billing settings.

    Manage your subscription · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  118. End User License Agreement typingmind:typingmind:end-user-license-agreement

    The software is commercially licensed with restrictions on redistribution and modification.

    End User License Agreement · documented · Source date not stated · Retrieved 2026-10-21

  119. Custom branding typingmind:typingmind:custom-branding

    Teams supports instance logo, theme and branded presentation within its commercial licence.

    Custom branding · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  121. Export and import data typingmind:typingmind:export-import-data

    User app settings export/import chats, prompts, plugins, folders, agents and model settings as JSON.

    Export and import data · documented · Source date not stated · Retrieved 2026-10-21

  122. Dust Support dust:dust:support

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

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

  123. TypingMind status typingmind:typingmind:status

    The status site loaded a status shell but reported an error fetching data; incident history and measured uptime were not retrieved.

    Public status shell · documented · Source date not stated · Retrieved 2026-10-21

  124. Dust Rollout Guide dust:dust:rollout

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

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

  125. Team onboarding material dust:dust:training

    Dust provides reusable team-onboarding material.

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

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

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

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

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

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

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