Dust vs T3 Chat

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:models, dust:dust:eu-models, dust:dust:changelog, dust:dust:pricing, dust:dust:files.

T3 Chat

Agent cross-checked Support: partial

Paid-account vendor replies establish manual model switching and provider routes, while the current plan-specific catalogue is unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 vendor-support context; no Free or Premier catalogue parity asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• providers Which model providers are available? [partial]: Pro-context vendor replies discuss Gemini, Claude and GPT routes; the FAQ separately describes OpenAI/Anthropic/Google/OpenRouter data handling. Those policy/provider names are not a complete tier-entitlement or underlying-lab catalogue. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:faq-training, t3-chat:t3-chat:r2-paid-tier-controls.
• current_models Which current models are selectable on this plan? [unknown]: A complete current selectable-model list for Pro, Free or Premier is unverified. The FAQ claude-4.6-sonnet URL is an example, and undated support model names are not a current plan catalogue.
• user_choice Can users pick the model per chat? [partial]: In the USD8 context discussion the vendor recommends manually switching to Gemini Flash or summarizing into a new chat with another chosen model. This supports Pro model selection as described there, but not a current all-model, effort or Free/Premier entitlement matrix. Sources: t3-chat:t3-chat:r2-pro-context-byok.
• 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 public T3 FAQ, Terms, Privacy/Security policies, official feedback statuses and identifiable vendor replies did not establish this detail. No authenticated account, enterprise quote or bounded fixture was used.
• multimodal_input Which models accept images, audio or files? [unknown]: No current Pro model-by-model image/audio/file compatibility matrix was retrieved. The generic privacy upload categories do not establish a plan entitlement.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:faq-training, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:changelog, dust:dust:models.

T3 Chat

Agent cross-checked Support: partial

Public feature-release information is described; plan-specific pinning and version guarantees remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Public T3 Chat release information; no verified Free/Pro/Premier picker/pinning entitlement; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• 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 dates for the last three provider releases, fixed removal notice or contractual model-version retention was retrieved.
• changelog Is there a dated public model changelog? [partial]: A vendor reply says major-feature changelog lives in Discord and a website version is planned. No accessible dated model-by-model release ledger was retrieved. Sources: t3-chat:t3-chat:changelog.
• 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 dates for the last three provider releases, fixed removal notice or contractual model-version retention was retrieved.
• version_pinning Can an admin keep an older model version? [unknown]: The vendor describes pinning and a Legacy designation in the general picker discussion, without a named individual tier. Plan-specific pinning, retained model versions and admin locks remain unverified.

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

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.

T3 Chat

Agent cross-checked Support: partial

Vendor replies support a Pro own-OpenRouter-key route, without establishing universal provider/model coverage.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 with optional customer OpenRouter key; no Free BYOK entitlement asserted; add_ons=Customer-paid OpenRouter/provider usage; model routing and verification prerequisites apply; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• own_api_keys Can the customer use its own provider API keys? [supported]: In the paid USD8 usage discussion, staff explicitly offers a customer OpenRouter key for direct request billing; the USD8 context discussion describes OpenRouter fallback. No all-provider/all-model BYOK entitlement follows. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok.
• own_cloud_contract Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [unknown]: Can it use its own Azure OpenAI, Bedrock or Vertex deployment? No supported customer Azure OpenAI/Bedrock/Vertex setup or arbitrary OpenAI-compatible/custom endpoint configuration was retrieved.
• custom_endpoint Can an admin add any OpenAI-compatible endpoint? [unknown]: Can an admin add any OpenAI-compatible endpoint? No supported customer Azure OpenAI/Bedrock/Vertex setup or arbitrary OpenAI-compatible/custom endpoint configuration was retrieved.
• byo_pricing Does BYO change the licence price? [partial]: The paid subscription and direct-provider charges are separate in the vendor discussion. A discounted BYOK-only licence and exact customer provider rates are not verified. Sources: t3-chat:t3-chat:r2-paid-tier-controls.
• byo_restrictions Which features stop working with BYO? [unknown]: Current all-model BYOK compatibility is unknown: the OpenRouter-coverage request is marked Completed while the vendor says those model routes do not run through OpenRouter and rerouting requires future work. The old OpenAI GPT5 setup reply does not establish a complete current route matrix.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok.

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.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:tiers, dust:dust:eu-models, dust:dust:spaces, dust:dust:models, dust:dust:credits, dust:dust:credit-management.

T3 Chat

Agent cross-checked Support: partial

Individuals have cost-based refill limits; enterprise group governance is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 cost-limit discussion and Premier account bucket reply; Free excluded from this mechanics finding; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• model_allowlist_by_group Can admins limit models per group? [unknown]: Can admins limit models per group? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established.
• data_bound_models Can admins restrict which models receive connector or knowledge content? [unknown]: Can admins restrict which models receive connector or knowledge content? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established.
• default_model Can admins set the default model? [unknown]: Can admins set the default model? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established.
• user_limits What per-user message or token limits apply, and are they published? [supported]: Pro cost-limit replies and a Premier-specific vendor support reply tie paid usage to the FAQ Base/Overage mechanics: four-hour Base refill and monthly Overage refill. No fixed token/message allowance is published;20/200 example points are illustrative, not plan capacities. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets.
• limit_behaviour What happens when a limit is reached? [supported]: For these documented paid-account bucket routes, expected request cost is reserved then settled after completion; when both balances are exhausted the FAQ says to wait for refill. No Free-tier behaviour is inferred. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-premier-buckets, t3-chat:t3-chat:r2-paid-tier-controls.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:files, dust:dust:file-limits, dust:dust:computer, dust:dust:drive, dust:dust:search.

T3 Chat

Agent cross-checked Support: partial

Paid Pro context limits and own-key fallback are documented; plan-specific upload formats/caps remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 context restrictions and optional BYOK fallback; exact upload entitlement by tier unverified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• formats Which formats are accepted? [unknown]: The privacy policy mentions PDF/images/text and the request is Completed, but no current individual-tier format entitlement was verified. The earlier sentence attributing browser/file-specific PDF upload bugs to a vendor reply is withdrawn because no precise reply locator was reproduced.
• limits What size and count limits apply per file and chat? [partial]: Vendor replies distinguish context restrictions on USD8 Pro from higher-tier allowances and own-key fallback. They do not publish a complete current per-model file size/count or context-cap matrix; no32K or user-suggested MB cap is adopted. Sources: t3-chat:t3-chat:r2-pro-context-byok.
• ocr Are scanned PDFs read? [unknown]: Are scanned PDFs read? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits.
• spreadsheets Are Excel tables read with structure intact? [unknown]: Are Excel tables read with structure intact? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits.
• full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [unknown]: Is the whole file used or only retrieved parts, and does the user see which? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-pro-context-byok.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:spaces.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:microsoft, dust:dust:drive, dust:dust:credits, dust:dust:confluence, dust:dust:jira, dust:dust:sources, dust:dust:r2-bigquery, dust:dust:pricing, dust:dust:tools, dust:dust:permissions.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:drive, dust:dust:microsoft, dust:dust:permissions, dust:dust:credentials, dust:dust:spaces.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:permissions, dust:dust:files, dust:dust:tools, dust:dust:microsoft, dust:dust:drive, dust:dust:confluence, dust:dust:security.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:memory.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:governance, dust:dust:spaces, dust:dust:models.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:credits, dust:dust:computer, dust:dust:tools, dust:dust:credentials, dust:dust:changelog.

T3 Chat

Agent cross-checked Support: partial

Paid Pro search is discussed by the vendor; image-tier entitlement, custom actions and MCP remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 for evidenced search use; image and MCP plan entitlement unknown; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• builtin_tools Which tools are built in? [partial]: The Pro/Premier pricing discussion explicitly describes frequent search and search-token overhead in the USD8 paid context. An OpenAI image integration has separate support evidence, but its plan entitlement is not verified and is not included as a Pro tool promise. Sources: t3-chat:t3-chat:r2-paid-tier-controls.
• custom_actions Can admins add API actions? [unknown]: Can admins add API actions? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established.
• mcp_client Can it use remote MCP servers, and with what admin control? [unknown]: Can it use remote MCP servers, and with what admin control? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established.
• tool_auth Do tools act as the user or as a shared account? [unknown]: Do tools act as the user or as a shared account? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established.
• tool_approval Can admins approve or block tools, and can users confirm actions before they run? [unknown]: Can admins approve or block tools, and can users confirm actions before they run? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:web, dust:dust:deep.

T3 Chat

Agent cross-checked Support: partial

Search is user-selectable, with a documented one-to-five search limit; a separate deep-research product is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 paid-search discussion; no Free parity asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• web_search Is web search available? [partial]: Staff’s paid USD8 discussion confirms search consumes API/query and context costs. The FAQ exposes search on/off and1..5 URL limits, but a complete current tier-specific limit/feature matrix was not verified. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:faq-url.
• admin_toggle Can admins disable it per organisation or group? [unknown]: Can admins disable it per organisation or group? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness.
• search_provider Which search provider handles queries, and where? [unknown]: Which search provider handles queries, and where? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness.
• deep_research Is multi-step research with a report available? [unknown]: Is multi-step research with a report available? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness.
• web_citations Are web sources cited? [unknown]: Are web sources cited? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:faq-url.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep, dust:dust:triggers, dust:dust:changelog, dust:dust:schedules, dust:dust:webhooks.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep, dust:dust:computer, dust:dust:changelog, dust:dust:pods, dust:dust:credits.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:get-conversation, dust:dust:api-keys, dust:dust:upsert, dust:dust:models, dust:dust:credit-management, dust:dust:mcp-server.

T3 Chat

Agent cross-checked Support: partial

No official programmable enterprise interface was established; subscription-backed external-agent API usage was rejected.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

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

• chat_api Is there an API for chat and assistants? [partial]: An official feedback request asks to apply subscription quota to external coding agents/API; staff closes it because the economics do not work. The FAQ URL launches a browser chat and is not a documented chat API. Sources: t3-chat:t3-chat:api-request, t3-chat:t3-chat:faq-url.
• knowledge_api Can documents be loaded through an API? [unknown]: Can documents be loaded through an API? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence.
• api_governance Do audit, budgets and model rules apply to API use? [unknown]: Do audit, budgets and model rules apply to API use? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence.
• mcp_server Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:api-request, t3-chat:t3-chat:faq-url.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:models, dust:dust:browser.

T3 Chat

Agent cross-checked Support: partial

A browser client and iOS TestFlight beta are documented; desktop, Android release and managed clients remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application, T3 Chat iOS TestFlight beta; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Browser account plan; iOS TestFlight beta; enterprise SSO unverified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=iOS.

Limitations

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

• web Is a full web client available? [supported]: T3 Chat is delivered as a browser service; the FAQ documents launching new conversations through public URLs. Sources: t3-chat:t3-chat:faq-url.
• desktop_apps Windows and macOS apps? [unknown]: Windows and macOS apps? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients.
• mobile_apps iOS and Android apps with SSO? [partial]: The vendor’s September10,2026 announcement releases iOS via TestFlight explicitly as beta; Android beta is coming soon. Neither corporate SSO nor a production app-store release was verified. Sources: t3-chat:t3-chat:mobile.
• browser_extension Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients.
• managed_deployment Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients.
• client_feature_gaps Which features are missing on mobile? [unknown]: Which features are missing on mobile? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-url, t3-chat:t3-chat:mobile.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:teams.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:computer.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:images, dust:dust:governance.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:speech, dust:dust:meetings.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:computer, dust:dust:frames.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pod-chats, dust:dust:pods, dust:dust:permissions, dust:dust:credentials.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:changelog.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:sso, dust:dust:pricing, dust:dust:enterprise.

T3 Chat

Agent cross-checked Support: partial

The security policy asserts MFA support without documenting enterprise SAML/OIDC administration.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

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

• sso_protocols Which SSO protocols and identity providers work? [partial]: Security policy refers to OAuth provider accounts and standard authentication without naming enterprise SAML/OIDC protocols or supported corporate IdPs. Sources: t3-chat:t3-chat:security.
• sso_plan Which plan includes SSO? [unknown]: Which plan includes SSO? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved.
• mfa Can MFA be enforced? [partial]: The vendor asserts MFA support and recommends two-factor protection at the OAuth provider. Enforceable organization-wide MFA settings were not established. Sources: t3-chat:t3-chat:security.
• conditional_access Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved.
• domain_capture Can the company claim its email domain? [unknown]: Can the company claim its email domain? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:security.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:provision, dust:dust:spaces, dust:dust:seats.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:governance, dust:dust:tiers, dust:dust:spaces, dust:dust:pods.

T3 Chat

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.

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

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:analytics, dust:dust:credit-management, dust:dust:api-keys.

T3 Chat

Agent cross-checked Support: partial

Individual consumption indicators exist; organization budgets and chargeback remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 and Premier account consumption mechanics; no organization/admin budget offer asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• cost_visibility Can admins see cost or consumption per user and group? [partial]: The paid Pro discussion and Premier support reply describe per-account cost/bucket consumption. The FAQ describes separate balance displays; exact placement and model-cost indicators are not a customer organization reporting entitlement. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets.
• budgets Can budgets be set per user or group? [unknown]: Can budgets be set per user or group? No customer organization/user-group budget assignment or cost-centre export was retrieved.
• budget_enforcement Does reaching a budget alert, block or downgrade? [partial]: For the documented paid-account bucket routes, exhausting both balances requires waiting for refill. This does not establish configurable user/group currency budgets, alerts or downgrade policies. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-premier-buckets.
• chargeback Can costs be exported per cost centre? [unknown]: Can costs be exported per cost centre? No customer organization/user-group budget assignment or cost-centre export was retrieved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:audit, dust:dust:enterprise.

T3 Chat

Agent cross-checked Support: partial

The privacy policy describes vendor telemetry, not a customer compliance logging service.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; 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 customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access.
• content_logging Can prompts and answers be retained for compliance, and is it configurable? [partial]: The privacy policy collects prompts/uploads and Terms reserve review/removal for violations. A configurable customer prompt/answer compliance archive was not established. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.
• siem_export Can logs stream to a SIEM or be exported? [unknown]: Can logs stream to a SIEM or be exported? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access.
• ediscovery Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access.
• log_retention How long are logs kept? [unknown]: How long are logs kept? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.

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.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:governance, dust:dust:images.

T3 Chat

Agent cross-checked Support: partial

Acceptable-use terms apply, while organization policy controls remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

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

• org_instructions Can admins set organisation-wide instructions? [unknown]: Can admins set organisation-wide instructions? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved.
• usage_notice Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved.
• content_filters Are content filters configurable? [partial]: Terms prohibit categories of unlawful/harmful content and permit vendor review/removal or suspension. Customer configurable content filters are not established. Sources: t3-chat:t3-chat:terms.
• violation_reporting Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:security, dust:dust:eu-models, dust:dust:privacy.

T3 Chat

Agent cross-checked Support: partial

The privacy policy places the service under US/international processing; no EU/Swiss end-to-end option was established.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

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

• storage_region Where are chats, files and indexes stored? [partial]: The policy says services are provided in the United States and information is processed there or in other countries; Azure, AWS and Vercel are named. Component-specific chat/file/index storage regions are not enumerated. Sources: t3-chat:t3-chat:privacy.
• inference_region Where do model calls run, per provider? [partial]: The policy names OpenAI, Google, Anthropic and OpenRouter processing, but no provider-by-provider region, EU-only switch or customer region guarantee is supplied. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:faq-training.
• backups_logs_region Where are backups, logs and telemetry? [unknown]: Where are backups, logs and telemetry? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved.
• support_access_region From where can vendor staff access data? [unknown]: From where can vendor staff access data? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved.
• swiss_hosting Is Swiss hosting available? [unknown]: Is Swiss hosting available? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved.
• residency_plan Which plan or option provides residency? [unknown]: Which plan or option provides residency? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:faq-training.

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

T3 Chat

Agent cross-checked Support: partial

A hosted web service is offered; tenant architecture and alternative deployment contracts remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

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

• multi_tenant_saas Is a shared SaaS offered? [partial]: The public web service accepts individual accounts and processes content with hosting/model providers. Its exact multitenant architecture and boundaries are not documented in the retrieved public material. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:privacy.
• dedicated_instance Is a dedicated single-tenant instance offered, from what size? [unknown]: Is a dedicated single-tenant instance offered, from what size? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.
• 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? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.
• 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? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.
• air_gapped Can it run without internet access? [unknown]: Can it run without internet access? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.
• mode_feature_gaps Which features are missing outside SaaS? [unknown]: Which features are missing outside SaaS? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:privacy.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:training-policy.

T3 Chat

Agent cross-checked Support: partial

No vendor training is asserted, with provider exceptions and customer-key responsibility explicitly retained.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

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

• vendor_training Does the vendor train on customer content? [supported]: FAQ says T3 does not train its own models and the privacy policy says personal information is not used to train AI models. Sources: t3-chat:t3-chat:faq-training, t3-chat:t3-chat:privacy.
• provider_training Do model providers train on it under this product's contracts? [supported]: The FAQ says OpenAI/Anthropic defaults are not opted into training, Google paid models disable training and OpenRouter training routes are disabled. Some new models may require training and are labeled; BYOK customers manage their own provider settings. Sources: t3-chat:t3-chat:faq-training.
• provider_retention How long do model providers keep prompts, including for abuse monitoring? [unknown]: How long do model providers keep prompts, including for abuse monitoring? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred.
• zero_retention Is zero data retention available, and on which plan? [unknown]: Is zero data retention available, and on which plan? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred.
• human_review Can provider staff review content? [unknown]: Can provider staff review content? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-training, t3-chat:t3-chat:privacy.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:memory, dust:dust:pricing, dust:dust:delete-chat.

T3 Chat

Agent cross-checked Support: partial

Termination export responsibilities are contractual; plan-specific temporary-chat behaviour and retention remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual T3 Chat service Terms; temporary-chat Free/Pro/Premier entitlement not established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• default_retention What is retained and for how long by default? [unknown]: The generic URL FAQ distinguishes temporary and persisted threads but does not map that feature to a named individual tier or specify server/provider/file/backup retention. No plan-specific temporary-chat retention claim is made.
• admin_retention Can admins set retention periods? [unknown]: Can admins set retention periods? No administrator retention controls, user permanent-deletion completion guarantee, backup erasure interval or fixed contract-end deletion deadline was retrieved.
• user_deletion Can users delete their chats and files permanently? [unknown]: Can users delete their chats and files permanently? No administrator retention controls, user permanent-deletion completion guarantee, backup erasure interval or fixed contract-end deletion deadline was retrieved.
• contract_end_deletion What is deleted at contract end, and when? [partial]: Terms put responsibility on users to export before termination and endeavor to provide a reasonable retrieval opportunity only for vendor-convenience termination; deletion timing and certificate are unspecified. Sources: t3-chat:t3-chat:terms.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:privacy.

T3 Chat

Agent cross-checked Support: partial

Named providers and a US vendor address are public, without a complete processor-country or transfer contract matrix.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

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

• subprocessor_list Is a dated sub-processor list published? [partial]: The May31,2025 privacy policy names Azure, AWS, Vercel, OpenAI, Google, Anthropic and OpenRouter, explicitly non-exhaustively. This is not established as a complete Article28 subprocessor schedule. Sources: t3-chat:t3-chat:privacy.
• subprocessor_countries Which countries do sub-processors operate in? [unknown]: Which countries do sub-processors operate in? No exhaustive processor operation-country matrix, signed SCC/Swiss transfer mechanism or subprocessor objection schedule was retrieved.
• change_notification Are customers notified of sub-processor changes? [partial]: Privacy policy says material changes are posted with an updated effective date. A processor-addition notice period and objection right are not specified. Sources: t3-chat:t3-chat:privacy.
• parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: The policy and Terms identify T3 Tools Inc with a San Francisco address and US/California legal context. A separate parent entity, incorporation jurisdiction and ownership were not independently established. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.
• transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [unknown]: Which transfer mechanism applies to non-EU/CH processing? No exhaustive processor operation-country matrix, signed SCC/Swiss transfer mechanism or subprocessor objection schedule was retrieved.
• government_access_policy Is there a published government-access or transparency policy? [partial]: The policy allows disclosures for subpoenas, warrants and legal investigations. No separate transparency report or detailed challenge/notification policy was retrieved. Sources: t3-chat:t3-chat:privacy.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:security, dust:dust:privacy.

T3 Chat

Agent cross-checked Support: partial

Public consumer/service terms use California law; an enterprise GDPR/Swiss DPA remains unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

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

• dpa Is a DPA available, and is it negotiable? [unknown]: Is a DPA available, and is it negotiable? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence.
• revdsg_gdpr Does the DPA cover revDSG and GDPR? [unknown]: Does the DPA cover revDSG and GDPR? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence.
• governing_law Which law and court govern the contract? [supported]: Terms section19 uses California law and individual JAMS arbitration in Santa Clara County, with small-claims/injunction exceptions and state/federal Santa Clara courts where arbitration does not apply. Sources: t3-chat:t3-chat:terms.
• ai_act_materials Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence.
• sector_materials Are FINMA or other sector materials provided? [unknown]: Are FINMA or other sector materials provided? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

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

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:tools, dust:dust:pricing.

T3 Chat

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.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:privacy, dust:dust:training-policy, dust:dust:eu-models.

T3 Chat

Agent cross-checked Support: partial

Public policies describe vendor/provider content processing, but professional-secrecy contracts and a business plan remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual account service; no business/professional-secrecy offer verified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US/international policy; no DE/CH-specific arrangement verified; os=not specified.

Limitations

• No-training statements and personal account terms are not 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]: No public DPA or signed/signon §203 StGB/Art321 StGB professional-secrecy undertaking covering T3 staff was retrieved from the Terms, privacy/security policies or targeted first-party searches.
• subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The privacy policy names hosting/model services but does not establish a dedicated professional-secrecy undertaking binding them. Its existence and flow-down are unknown.
• secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: A team/business offer itself remains unverified; no professional-secrecy-specific tier, dedicated package or paid add-on was established.
• content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: Privacy policy sends input to selected OpenAI/Google/Anthropic/OpenRouter services; Terms reserve vendor review/removal of content upon apparent violations. This establishes processing/review possibilities, not an exhaustive plaintext staff/provider access matrix or protected-profession arrangement. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.
• secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Public consumer/service Terms and privacy/security pages were reviewed, with targeted §203/Art321/professional-secrecy searches. No specific template, protected-profession data-flow statement or professional-body guidance was retrieved; no private agreement was requested.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:credit-management, dust:dust:credits, dust:dust:seats.

T3 Chat

Agent cross-checked Support: partial

Individual subscription prices are supported by vendor replies; quotas are cost-based and checkout/organization details are incomplete.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Staff pricing replies are first-party but undated; current checkout amounts and tax/plan availability were not observed.

• pricing_unit What is the pricing unit? [supported]: Evidence describes monthly individual Pro/Premier subscriptions, optional customer provider keys and cost-based included use. No organizational seat/pool contract is established. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage.
• list_prices What are list prices per plan, with date and currency? [partial]: Vendor replies confirm USD8/month paid-tier context and Premier USD50/month plus applicable tax. No checkout was completed and no business price was retrieved; dates of the undated replies are unknown. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:price-visibility.
• included_usage What usage is included? [supported]: Included usage is represented by Base and Overage balances, refilling four-hourly/monthly. The FAQ’s20/200 example is not the actual plan quota and the former1500+100 message claim is not used. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:billing-change.
• add_ons Which features cost extra? [partial]: Customer OpenRouter/OpenAI API keys incur direct provider charges. Staff says a top-up product has not been offered since the new billing model and options are only being considered. Sources: t3-chat:t3-chat:premier, t3-chat:t3-chat:overage, t3-chat:t3-chat:byok-openai.
• overage What do usage beyond limits and premium models cost? [partial]: The Overage bucket is a monthly included-usage bucket, not an established published dollar-per-token overage tariff. Extra usage via own keys is billed by the customer provider; current model/route tariffs are not fully mapped. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:premier.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:overage, t3-chat:t3-chat:byok-openai.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:credits, dust:dust:credit-management, dust:dust:pricing, dust:dust:models, dust:dust:fx-ecb.

T3 Chat

Agent cross-checked Support: partial

Multiplying individual list prices yields conditional licence floors, not a verified organization quote or usage-complete TCO.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Conditional independent Pro/Premier account multiplication; no organization plan verified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Known price floor + unknown components; no complete year-one TCO, seat commitment or sufficient-usage guarantee.

• cost_200 Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4,2026-10-21:12 months,list prices,exVAT,no negotiated discounts;60% light100/30% regular400/10% power1500 messages/user/month =>330,each3000 input+600 output tokens incl retrieval. Vendor subscription usage remains subject to cost/refill limits; no fixed default/recommended model or complete tariff is published, so coverage and variable extra cost stay unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; divideUSD by1.1215 then multiplyEUR by0.9237. For200 separate accounts: Pro from USD19,200/EUR17,119.93/CHF15,813.68 + unknown; Premier reference USD120,000/EUR106,999.55/CHF98,835.49 + unknown. Bulk purchase and business-governance fit unverified. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx.
• cost_1000 Year-one cost at 1,000 users? [partial]: Same assumptions,1000 separate accounts: Pro from USD96,000/EUR85,599.64/CHF79,068.39 + unknown; Premier reference USD600,000/EUR534,997.77/CHF494,177.44 + unknown. Not a1000-seat quote. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx.
• cost_5000 Year-one cost at 5,000 users? [partial]: Same assumptions,5000 separate accounts: Pro from USD480,000/EUR427,998.22/CHF395,341.95 + unknown; Premier reference USD3,000,000/EUR2,674,988.85/CHF2,470,887.20 + unknown. Not a5000-seat quote. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx.
• variable_share Which part depends on usage? [partial]: Included usage consumes a cost meter with no complete published tariff/default model. For an optional direct-provider BYOK comparison only, the shared gpt-6-luna effort-none Standard proxy is USD0.10 input/USD0.50 output per1M and USD2.376/user/year at the shared mix, excluding cache/tools/embeddings/regional uplift. This exact model/route is not verified selectable in T3 and is not added to the subscription floor as though it were a vendor tariff. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:openai-price, t3-chat:t3-chat:openai-model.
• unknown_parts Which costs could not be priced? [supported]: Unpriced: enterprise/bulk entitlement, organization features, exact current checkout prices, model availability and complete token/search/file tariff, whether the shared workload fits refill quotas, direct-provider/OpenRouter route charges, regional processing and support/implementation. No assumed wholesale discount or model-cost subsidy. Sources: t3-chat:t3-chat:premier, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:byok-router.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx, t3-chat:t3-chat:openai-price, t3-chat:t3-chat:openai-model, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:byok-router.

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

T3 Chat

Agent cross-checked Support: partial

Free usage is in the Terms; a business-specific trial and enterprise evaluation path remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

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

• free_tier Is there a free tier for business use? [partial]: Terms say services are free up to unspecified usage limits and paid resources may be required. Organizational acceptance is allowed, but no free business admin entitlement is established. Sources: t3-chat:t3-chat:terms.
• self_serve_trial Is a self-serve business trial available? [unknown]: Is a self-serve business trial available? No timed self-serve business trial, SSO/connector/admin trial entitlement or enterprise evaluation agreement was retrieved. No account was created.
• trial_scope Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? No timed self-serve business trial, SSO/connector/admin trial entitlement or enterprise evaluation agreement was retrieved. No account was created.
• sales_gate Does meaningful evaluation require sales contact? [partial]: A public browser service and free-limited offer are documented; business-specific meaningful evaluation and any sales gate cannot be determined without an established business offer. Sources: t3-chat:t3-chat:terms.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:seats, dust:dust:privacy, dust:dust:credits.

T3 Chat

Agent cross-checked Support: partial

Individual monthly upgrades/downgrades are documented; business minimums and European invoicing remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

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

• minimum_commitment What seat or spend minimum applies? [partial]: The public evidence concerns individual accounts and monthly prices, not a minimum team-seat/spend commitment. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier.
• contract_length What contract lengths are offered? [supported]: Vendor replies confirm monthly Premier pricing and billing periods; no signed annual or business-term offer was retrieved. Sources: t3-chat:t3-chat:premier.
• cancellation How can the contract be cancelled or reduced? [supported]: Terms permit account cancellation at any time without refunds. Staff says upgrades take effect immediately and downgrades at the billing-period end. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier.
• 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? No team minimum, European contracting entity or CHF/EUR invoice entitlement was retrieved.
• transparency_class Is pricing transparent, partial, quote-only or unknown? [supported]: Partial: some individual prices are confirmed in undated staff replies, complete final checkout requires billing information, quotas are not a public token tariff, and a business offer remains unverified. Sources: t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:faq-usage.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:licence.

T3 Chat

Agent cross-checked Support: partial

The hosted service is proprietary; clone hackathons and T3 Code are separate products.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

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

• licence_type Which licence applies to each component? [supported]: Terms grant a personal nonassignable service licence and prohibit copying, modification, reverse engineering and source extraction, subject to third-party software rights. Sources: t3-chat:t3-chat:terms.
• branding_restrictions Do licence terms restrict branding or user counts? [supported]: Terms reserve vendor trademarks and prohibit sublicensing/renting/providing service access to others; each account is personal and cannot be shared. Sources: t3-chat:t3-chat:terms.
• enterprise_features_closed Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? No supported self-host licence, open-source core/enterprise split or enterprise edition licence was retrieved. Public third-party clones are not licensed distributions of the hosted product.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:get-conversation, dust:dust:pricing, dust:dust:get-document, dust:dust:analytics.

T3 Chat

Agent cross-checked Support: partial

Terms require pre-termination export, but a documented organizational export package was not established.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

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

• chat_export Can admins export all chats? [unknown]: Can admins export all chats? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees.
• assistant_export Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees.
• knowledge_export Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees.
• export_format Are formats documented and machine-readable? [unknown]: Are formats documented and machine-readable? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees.
• post_termination_window How long can data be retrieved after termination? [partial]: Users must export before termination. If the vendor terminates for convenience it will endeavor to allow a reasonable retrieval opportunity; no fixed post-termination window is guaranteed. Sources: t3-chat:t3-chat:terms.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:support, dust:dust:privacy, dust:dust:enterprise, dust:dust:models.

T3 Chat

Agent cross-checked Support: partial

Email support and official feedback are public, without a retrieved SLA or regional-language contract.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

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

• support_channels Which support channels are available on each plan? [supported]: The FAQ lists a support email and official feature/bug board; plan-specific response targets are not published there. Sources: t3-chat:t3-chat:faq-support.
• 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, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows.
• regional_presence Is there a DACH or Swiss entity, team or partner? [partial]: The vendor publishes a San Francisco contact address. A DACH/Swiss entity, partner or support team was not established. Sources: t3-chat:t3-chat:privacy.
• uptime_sla Is there an uptime SLA with credits? [unknown]: Is there an uptime SLA with credits? No German/French/Italian support commitment, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows.
• status_page Is there a public status page with history? [unknown]: Is there a public status page with history? No German/French/Italian support commitment, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-support, t3-chat:t3-chat:privacy.

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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:training, dust:dust:rollout, dust:dust:r2-department-guides, dust:dust:r2-sales-guide.

T3 Chat

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.