Skip to content

Agent-readable comparison

Dust vs meinGPT

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

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

Same facts as Markdown and JSON. Methodology.

Models

MOD-01 Model catalogue and providers

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Curated multi-provider models are selected per chat or by context-length routing; the signed DPA and admin approvals affect availability.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Business and individually contracted Enterprise web workspace; permitted models depend on workspace approval and DPA; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • auto_routing: Bestes Modell starts with GPT-5 and changes to Gemini 3.5 Flash-Lite only when context is too long. This is length routing, not task routing; visibility of the final routed identity is not established.
  • providers Which model providers are available? [supported]: Model authors include OpenAI, Anthropic, Google, Mistral, DeepSeek, Moonshot, Qwen, GLM and MiniMax. Hosts are separate from authors. Sources: meingpt:meingpt:models-rev2, meingpt:meingpt:lifecycle-rev2.
  • current_models Which current models are selectable on this plan? [supported]: Active table lists GPT-4.1, GPT-4o/Mini, GPT-5/mini/Nano/Thinking/5.2/5.4/5.5/5.6 Luna/Sol/Terra, GPT-6 Luna/Sol/Astra, GPT-6.1 Sol; o3; Claude Haiku 5.5, Opus 4.5/4.6/4.7/4.8/5/5.5, Sonnet 4.6/5/5.5; Gemini 3.5 Flash/Flash-Lite, 3.6/3.7/3.8 Flash and 4 Argon; MeinGPT Web; Mistral Medium 3.5/CodeStral; GPT-OSS 120B; Kimi K2.6/K3; DeepSeek V3.2/V4 Flash/V4 Pro/V4.1 Flash; GLM-5.3/Flash, MiniMax-M3 and Qwen3.8 Max. Duplicate EU/provider routes exist. GPT-6 Astra requires accepted AVV 2.0. Model labels do not guarantee one-to-one public provider variant names. Sources: meingpt:meingpt:lifecycle-rev2, meingpt:meingpt:models-rev2, meingpt:meingpt:rates.
  • user_choice Can users pick the model per chat? [supported]: Users select and switch a permitted model per chat. Sources: meingpt:meingpt:models-rev2.
  • auto_routing Does the product route between models automatically, and is the chosen model shown? [partial]: Bestes Modell starts with GPT-5 and changes to Gemini 3.5 Flash-Lite only when context is too long. This is length routing, not task routing; visibility of the final routed identity is not established. Sources: meingpt:meingpt:models-rev2.
  • multimodal_input Which models accept images, audio or files? [supported]: GPT-4o/5, Claude, Gemini and Mistral Medium/Magistral accept JPEG/PNG/GIF/WEBP; DeepSeek, GPT-OSS, CodeStral and older Kimi K2 do not. Audio uses separate transcription. Sources: meingpt:meingpt:models-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:models-rev2, meingpt:meingpt:lifecycle-rev2, meingpt:meingpt:rates.

MOD-02 Model freshness

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

A dated changelog and explicit retirement rules exist; comparative release-lag medians were not established.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • version_pinning: An available model can be selected, but retirement automatically substitutes a successor in assistants, workflows and chats; indefinite retention of a retired model is excluded.
  • Unverified release_lag_days: Provider release dates for the last three major releases per provider were not reconciled against product release dates, so no lag or median is asserted.
  • release_lag_days What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? Unknown. Provider release dates for the last three major releases per provider were not reconciled against product release dates, so no lag or median is asserted.
  • changelog Is there a dated public model changelog? [supported]: Public releases include v2.67.0 dated 2026-10-18. Sources: meingpt:meingpt:changes.
  • deprecation_notice How much notice is given before a model is removed? [supported]: Normally four weeks, then reminders at two and one week; provider short notice can shorten this. Opus 4.5 is listed for 23 November retirement; other future dates are in the table. Sources: meingpt:meingpt:lifecycle.
  • version_pinning Can an admin keep an older model version? [partial]: An available model can be selected, but retirement automatically substitutes a successor in assistants, workflows and chats; indefinite retention of a retired model is excluded. Sources: meingpt:meingpt:lifecycle.

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

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

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

Dust

No public information found Support: not-published

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

meinGPT

Agent cross-checked Support: partial

Customer LLM API keys, cloud contracts and arbitrary model endpoints are explicitly excluded from the hosted catalogue.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • own_api_keys: The hosted workspace does not accept customer OpenAI, Azure OpenAI or Anthropic keys. DeepL translation BYOK is separate.
  • own_cloud_contract: LLM requests use meinGPT-managed provider accounts, not customer Azure/OpenAI contracts.
  • custom_endpoint: Admins cannot add a model or provider key to the catalogue. Custom MCP adds tools, not LLM endpoints.
  • byo_pricing: There is no hosted LLM BYOK licence schedule because LLM BYOK is excluded. DeepL BYOK bills translation directly through DeepL.
  • byo_restrictions: Only DeepL has a documented BYOK exception; it does not replace the workspace model route.
  • own_api_keys Can the customer use its own provider API keys? [unsupported]: The hosted workspace does not accept customer OpenAI, Azure OpenAI or Anthropic keys. DeepL translation BYOK is separate. Sources: meingpt:meingpt:models.
  • own_cloud_contract Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [unsupported]: LLM requests use meinGPT-managed provider accounts, not customer Azure/OpenAI contracts. Sources: meingpt:meingpt:models.
  • custom_endpoint Can an admin add any OpenAI-compatible endpoint? [unsupported]: Admins cannot add a model or provider key to the catalogue. Custom MCP adds tools, not LLM endpoints. Sources: meingpt:meingpt:models.
  • byo_pricing Does BYO change the licence price? [partial]: There is no hosted LLM BYOK licence schedule because LLM BYOK is excluded. DeepL BYOK bills translation directly through DeepL. Sources: meingpt:meingpt:models, meingpt:meingpt:translation.
  • byo_restrictions Which features stop working with BYO? [partial]: Only DeepL has a documented BYOK exception; it does not replace the workspace model route. Sources: meingpt:meingpt:models.

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

MOD-04 Local and self-hosted models

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

Dust

No public information found Support: not-published

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

meinGPT

Agent cross-checked Support: partial

Vendor-operated open-model routes exist; customer-hosted LLM and embedding routes were not verified.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • vendor_hosted_open_models: Open-weight routes include GPT-OSS via Nebius in Finland, DeepSeek/Kimi via TensorX in Ireland and custom models via Verda in Finland; the active table also lists Melious routes. These are vendor-selected routes, with exact region absent for Melious.
  • Unverified self_hosted_chat, self_hosted_embeddings, feature_parity: Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference.
  • self_hosted_chat Can chat use a customer-hosted model? [unknown]: Can chat use a customer-hosted model? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference.
  • self_hosted_embeddings Can retrieval use customer-hosted embeddings? [unknown]: Can retrieval use customer-hosted embeddings? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference.
  • feature_parity Which features fail with self-hosted models? [unknown]: Which features fail with self-hosted models? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference.
  • vendor_hosted_open_models Does the vendor host open-weight models in EU/CH? [partial]: Open-weight routes include GPT-OSS via Nebius in Finland, DeepSeek/Kimi via TensorX in Ireland and custom models via Verda in Finland; the active table also lists Melious routes. These are vendor-selected routes, with exact region absent for Melious. Sources: meingpt:meingpt:lifecycle, meingpt:meingpt:subprocessors.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:lifecycle, meingpt:meingpt:subprocessors.

MOD-05 Model control and usage limits

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Admins set model access and defaults; personal category limits have documented exceptions.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • limit_behaviour: Zero blocks the category; API budget exhaustion returns 403. Running/concurrent meeting recordings can exceed personal limits; scheduled tasks consume workspace credit outside personal categories.
  • Unverified data_bound_models: A separate rule binding particular knowledge sources to approved models was not documented; no two-user restriction test was run.
  • model_allowlist_by_group Can admins limit models per group? [supported]: Per-team/person allow and deny rules are documented. Workspace admins and free models are exempt; denied chat models fall back, denied API models fail. Sources: meingpt:meingpt:config.
  • data_bound_models Can admins restrict which models receive connector or knowledge content? [unknown]: Can admins restrict which models receive connector or knowledge content? Unknown. A separate rule binding particular knowledge sources to approved models was not documented; no two-user restriction test was run.
  • default_model Can admins set the default model? [supported]: Workspace admins set the default model and chat standards. Sources: meingpt:meingpt:config.
  • user_limits What per-user message or token limits apply, and are they published? [supported]: Six usage levels set monthly EUR limits for text, images, API, other services and meeting bots; no single universal message cap. Sources: meingpt:meingpt:limits.
  • limit_behaviour What happens when a limit is reached? [partial]: Zero blocks the category; API budget exhaustion returns 403. Running/concurrent meeting recordings can exceed personal limits; scheduled tasks consume workspace credit outside personal categories. Sources: meingpt:meingpt:limits, meingpt:meingpt:api.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:config, meingpt:meingpt:limits, meingpt:meingpt:api.

Company knowledge

KNOW-01 Files in chat

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Chat uploads and direct sandbox processing have different document behavior.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • spreadsheets: Text extraction loses layout; the sandbox reads original Excel files using code and can preserve formulas. No fixture result is claimed.
  • full_vs_chunked: Direct attachments enter model context after extraction and are constrained by the context window; pools retrieve passages instead. Long-chat compression can drop earlier attachment context.
  • Unverified ocr: No scanned contract or structured spreadsheet fixture was uploaded; OCR behavior for direct scanned attachments was not bounded by a test.
  • formats Which formats are accepted? [supported]: Text/PDF, images, Word, PowerPoint, Excel, CSV, TXT and URLs are listed; sandbox is needed to read archives and raw mail formats. Sources: meingpt:meingpt:flow.
  • limits What size and count limits apply per file and chat? [supported]: 50 files per chat, 50 MB per non-image file; JPEG/PNG/WEBP/GIF are model-readable images. Provider PDF/page/image limits still apply. Sources: meingpt:meingpt:chat, meingpt:meingpt:models.
  • ocr Are scanned PDFs read? [unknown]: Are scanned PDFs read? Unknown. No scanned contract or structured spreadsheet fixture was uploaded; OCR behavior for direct scanned attachments was not bounded by a test.
  • spreadsheets Are Excel tables read with structure intact? [partial]: Text extraction loses layout; the sandbox reads original Excel files using code and can preserve formulas. No fixture result is claimed. Sources: meingpt:meingpt:chat, meingpt:meingpt:sandbox.
  • full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [partial]: Direct attachments enter model context after extraction and are constrained by the context window; pools retrieve passages instead. Long-chat compression can drop earlier attachment context. Sources: meingpt:meingpt:chat, meingpt:meingpt:models, meingpt:meingpt:pools.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:flow, meingpt:meingpt:chat, meingpt:meingpt:models, meingpt:meingpt:sandbox, meingpt:meingpt:pools.

KNOW-02 Knowledge bases and shared collections

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

Dust

Agent cross-checked Support: partial

Spaces persist shared knowledge and bind it to agent tools.

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

Limitations

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

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

meinGPT

Agent cross-checked Support: supported

Cloud pools persist across chats and attach to assistants; Outpost is a separate local index.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

  • persistent_collections Can users keep document collections across chats? [supported]: Persistent cloud data sources index SharePoint/OneDrive, Drive, Confluence, S3, WebDAV and web content. Sources: meingpt:meingpt:pools.
  • sharing_scope Can collections be shared with users, groups or the whole organisation? [supported]: Admins share data sources with teams; workspace admins have broad visibility. Sources: meingpt:meingpt:pools.
  • size_limits What are the collection limits? [supported]: Standard cloud raw-data budget is 300 GB across the workspace; indexing new content stops when full. Sources: meingpt:meingpt:pools.
  • assistant_binding Can collections be bound to an assistant? [supported]: Pools bind to assistants or can be selected in a chat; projects themselves cannot bind pools. Sources: meingpt:meingpt:assistants, meingpt:meingpt:projects.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pools, meingpt:meingpt:assistants, meingpt:meingpt:projects.

KNOW-03 Enterprise connectors

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

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.

KNOW-04 Permission-aware retrieval

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Live OAuth preserves source access; indexed permissions require a separate, default-off setting.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • source_permissions_respected: Live M365 tools use each user account. Cloud SharePoint/Drive pools enforce imported source permissions only when request-enabled and switched on; other source types do not inherit them. No two-user test was run.
  • Unverified revocation_delay, sensitivity_labels: No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown.
  • source_permissions_respected Are source permissions enforced per user? [partial]: Live M365 tools use each user account. Cloud SharePoint/Drive pools enforce imported source permissions only when request-enabled and switched on; other source types do not inherit them. No two-user test was run. Sources: meingpt:meingpt:m365, meingpt:meingpt:pool-controls.
  • enforcement_point Does the source system, a mirrored index or nothing enforce them? [supported]: Live tools execute under user OAuth. Indexed SharePoint/Drive permissions are mirrored and fail closed when stale; source-permission mode is off by default. Sources: meingpt:meingpt:pool-controls.
  • revocation_delay How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? Unknown. No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown.
  • admin_scope_controls Can admins exclude sites, folders or labels? [supported]: Admins select imported sources/folders and control team sharing. Sources: meingpt:meingpt:pools.
  • sensitivity_labels Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? Unknown. No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:m365, meingpt:meingpt:pool-controls, meingpt:meingpt:pools.

KNOW-05 Freshness and sync model

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Live connectors query the source; cloud pools copy an index to Germany.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • Unverified deletion_propagation: No edit/delete fixture was run and an end-to-end deletion-propagation bound was not verified.
  • live_or_indexed Is content searched live or copied into an index? [supported]: Native connectors fetch live; cloud data pools index imported documents. Sources: meingpt:meingpt:pools.
  • sync_interval How often does an index refresh? [supported]: Cloud import runs every 15 minutes. Sources: meingpt:meingpt:pools.
  • deletion_propagation How quickly does a deleted document disappear? [unknown]: How quickly does a deleted document disappear? Unknown. No edit/delete fixture was run and an end-to-end deletion-propagation bound was not verified.
  • index_location Where is indexed content stored? [supported]: Cloud pools run at Hetzner in Germany; local Outpost pools stay in the customer network. Sources: meingpt:meingpt:pools.

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

KNOW-06 Grounding and retrieval quality

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Source display is documented; grounding quality remains untested.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • no_answer_behaviour: The guide says source search reports no matching result; actual refusals were not tested.
  • Unverified citation_accuracy, cross_language, observed_accuracy: The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown.
  • citations Are answers linked to specific sources? [supported]: Cloud source answers always display sources and this cannot be disabled. Sources: meingpt:meingpt:pool-controls.
  • citation_accuracy Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown.
  • cross_language Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unknown. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown.
  • no_answer_behaviour Does it say when the corpus has no answer? [partial]: The guide says source search reports no matching result; actual refusals were not tested. Sources: meingpt:meingpt:pools.
  • observed_accuracy How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pool-controls, meingpt:meingpt:pools.

KNOW-07 Memory and personal context

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Personal instructions and user-specific assistant memory are documented.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • user_memory_controls: Users view and delete one/all memories; direct editing is unavailable in settings, but an assistant can update entries.
  • custom_instructions Can users set persistent instructions? [supported]: Preferences store a persistent system instruction applied with workspace and assistant context. Sources: meingpt:meingpt:preferences.
  • cross_chat_memory Does the product remember facts across chats? [supported]: Enabled assistants share a personal user memory store across chats, not a team store. Sources: meingpt:meingpt:memory.
  • user_memory_controls Can users view, edit and delete memories? [partial]: Users view and delete one/all memories; direct editing is unavailable in settings, but an assistant can update entries. Sources: meingpt:meingpt:memory.
  • admin_memory_controls Can admins turn memory off? [supported]: Admins can disable or remove Memory from the permitted tools. Sources: meingpt:meingpt:memory.

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

Assistants and agents

AGT-01 Custom assistants

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: supported

Assistants combine model, instructions, tools and knowledge, with governed creation and sharing.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

  • create_assistants Can users create assistants with instructions, knowledge and tools? [supported]: The editor supports instructions, model, files, pools, connectors and built-in tools. Sources: meingpt:meingpt:assistants.
  • creator_permissions Can admins limit who creates them? [supported]: Request-enabled permissions restrict assistant creation/sharing/publication by team or person; admins are exempt. Sources: meingpt:meingpt:permissions.
  • sharing_scope Can assistants be shared with users, groups or everyone? [supported]: Team and direct-person assistant sharing are documented; workspace-wide publication is admin-only by default. Sources: meingpt:meingpt:permissions, meingpt:meingpt:roles.
  • catalogue Is there an internal assistant directory? [supported]: The navigation lists personal assistants and shared resources. Sources: meingpt:meingpt:assistants.
  • prompt_library Are shared prompt templates available? [supported]: Prompt folders can be personal, workspace or department scoped. Sources: meingpt:meingpt:prompts.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:assistants, meingpt:meingpt:permissions, meingpt:meingpt:roles, meingpt:meingpt:prompts.

AGT-02 Tools, actions and MCP

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

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.

AGT-03 Web search and deep research

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: supported

Linkup powers cited web search and Deep Research; admins can restrict app access.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

  • web_search Is web search available? [supported]: Search can be switched on in chat, is always on in MeinGPT Web and runs in the Recherche app. Sources: meingpt:meingpt:web.
  • admin_toggle Can admins disable it per organisation or group? [supported]: Request-enabled per-team/person app controls include Web search. Sources: meingpt:meingpt:permissions.
  • search_provider Which search provider handles queries, and where? [supported]: Linkup processes search; the register lists Azure France. Prompt terms can enter generated search queries. Sources: meingpt:meingpt:web, meingpt:meingpt:subprocessors.
  • deep_research Is multi-step research with a report available? [supported]: The research app has a user-controlled multi-step Deep Research mode. Sources: meingpt:meingpt:web.
  • web_citations Are web sources cited? [supported]: Results include source previews and page references. Sources: meingpt:meingpt:web.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:web, meingpt:meingpt:permissions, meingpt:meingpt:subprocessors.

AGT-04 Workflows and automation

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: supported

Multi-step workflows are documented; scheduled/event automations are request-enabled beta.

Availability: beta · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • Workflow editor is documented separately from request-enabled beta scheduled tasks; beta is not universal plan availability.
  • workflow_builder Is there a workflow or chain builder? [supported]: A project editor chains prompts with variables and per-step models, or Buddy drafts the workflow. Sources: meingpt:meingpt:workflows.
  • scheduled_tasks Can prompts or assistants run on a schedule? [supported]: Support enables beta tasks with daily, weekly, monthly or selected calendar schedules. Sources: meingpt:meingpt:scheduled.
  • event_triggers Can external events start a workflow? [supported]: Beta tasks accept tokenized webhooks and task-specific email addresses. Sources: meingpt:meingpt:scheduled.
  • builder_audience Is building aimed at business users, IT or developers? [supported]: Members can build with natural-language Buddy help or manual steps, subject to admin rights. Sources: meingpt:meingpt:workflows.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:workflows, meingpt:meingpt:scheduled.

AGT-05 Agentic task execution

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Assistants can execute successive tool calls, show progress and stop; per-action confirmation is absent.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • side_effect_confirmation: No built-in method-specific permission popup exists at runtime; admin-approved write/dangerous methods can run without an additional dialog.
  • agent_mode Is there an agent mode for multi-step tasks? [supported]: Assistant tools run multiple sequential steps within a response and stop at a bounded tool-call budget. Sources: meingpt:meingpt:assistants.
  • visible_steps Are steps and tool calls shown? [supported]: Tool/reasoning steps and progress are shown in chat. Sources: meingpt:meingpt:assistants, meingpt:meingpt:chat.
  • side_effect_confirmation Must the user confirm actions with side effects? [unsupported]: No built-in method-specific permission popup exists at runtime; admin-approved write/dangerous methods can run without an additional dialog. Sources: meingpt:meingpt:tools.
  • stop_control Can the user stop a running task? [supported]: The input button changes to Abbrechen and stops response generation while preserving text. Sources: meingpt:meingpt:chat.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:assistants, meingpt:meingpt:chat, meingpt:meingpt:tools.

AGT-06 Programmable access

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

Dust

Agent cross-checked Support: supported

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

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

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

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

meinGPT

Agent cross-checked Support: partial

Enterprise-enabled APIs cover chat, assistants and workflows with model and budget enforcement.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT Enterprise API; version=Public documentation checked 2026-10-21; plan=Enterprise API, explicitly enabled; no public add-on price; add_ons=Enterprise API; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • api_governance: Model permission failures return 403; API has a separate personal budget and shared token-rate ceilings; compliance-content logging coverage was not fully established.
  • Unverified knowledge_api, mcp_server: A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide.
  • chat_api Is there an API for chat and assistants? [supported]: Bearer-key chat completions, assistants, workflow runs, embeddings and transcription are documented; personal keys require Enterprise enablement. Sources: meingpt:meingpt:api, meingpt:meingpt:outlook.
  • knowledge_api Can documents be loaded through an API? [unknown]: Can documents be loaded through an API? Unknown. A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide.
  • api_governance Do audit, budgets and model rules apply to API use? [partial]: Model permission failures return 403; API has a separate personal budget and shared token-rate ceilings; compliance-content logging coverage was not fully established. Sources: meingpt:meingpt:api, meingpt:meingpt:config, meingpt:meingpt:audit.
  • mcp_server Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? Unknown. A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:api, meingpt:meingpt:outlook, meingpt:meingpt:config, meingpt:meingpt:audit.

Daily work

WORK-01 Clients and access points

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

The platform is browser-based; Outlook has a separate centrally deployed add-in.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace, meinGPT Outlook add-in, meinGPT Enterprise API; version=Public documentation checked 2026-10-21; plan=Business/Enterprise web workspace; Outlook add-in requires Enterprise API enablement and personal API key; add_ons=Enterprise API enabled for Outlook add-in; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • managed_deployment: The Outlook add-in can be assigned to users or groups in Microsoft 365 integrated apps; general desktop/mobile MDM configuration was not found.
  • Unverified desktop_apps, mobile_apps, browser_extension, client_feature_gaps: No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.
  • web Is a full web client available? [supported]: The terms define a browser-accessible workspace. Sources: meingpt:meingpt:terms.
  • desktop_apps Windows and macOS apps? [unknown]: Windows and macOS apps? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.
  • mobile_apps iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.
  • browser_extension Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.
  • managed_deployment Can IT deploy and configure clients through MDM? [partial]: The Enterprise API-enabled Outlook add-in can be assigned to users/groups through Microsoft365 integrated apps. It supports Outlook web, Windows classic/new and Mac; each user needs a personal meinGPT API key. General desktop/mobile MDM configuration was not established. Sources: meingpt:meingpt:outlook.
  • client_feature_gaps Which features are missing on mobile? [unknown]: Which features are missing on mobile? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:terms, meingpt:meingpt:outlook.

WORK-02 Office suite and Teams integration

Judgment rule: Record presence inside Word, Excel, PowerPoint, Outlook and Teams (and Google Docs, Gmail), with what the assistant can do in each: read the open document, write into it, act on mail. Record extra licences and admin consent needed. A connector that searches Office files is KNOW-03, not WORK-02.

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

A documented Outlook add-in operates in the received-message view and needs Enterprise API access.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT Outlook add-in; version=Public documentation checked 2026-10-21; plan=Enterprise API enabled workspace; add_ons=Enterprise API; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • licence_prerequisites: Personal meinGPT API key and Enterprise API enablement are required; tenant admins can centrally deploy the add-in. A separate Microsoft licence price is not stated.
  • Unverified word_excel_powerpoint, teams, google_workspace_apps: Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03.
  • word_excel_powerpoint Does it work inside Word, Excel and PowerPoint? [unknown]: Does it work inside Word, Excel and PowerPoint? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03.
  • outlook Does it work inside Outlook? [supported]: Outlook Web, Windows classic/new and Mac support summarizing the selected received email and drafting replies; compose view is excluded. Sources: meingpt:meingpt:outlook.
  • teams Is there a Teams app or bot? [unknown]: Is there a Teams app or bot? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03.
  • google_workspace_apps Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03.
  • licence_prerequisites Which licences or consents are needed? [partial]: Personal meinGPT API key and Enterprise API enablement are required; tenant admins can centrally deploy the add-in. A separate Microsoft licence price is not stated. Sources: meingpt:meingpt:outlook.

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

WORK-03 Translation and writing

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Dedicated text/document translation uses EU Google/DeepL routes and managed glossaries.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • document_translation: DeepL document translation preserves layout for DOC/DOCX, PPT/PPTX, XLS/XLSX, PDF, HTML, TXT, SRT and XLIFF. Layout quality was not fixture-tested.
  • writing_tools: Quick Actions rewrite answers, including more formal and improve options.
  • Unverified formality_and_variants: Formality settings within the translator and guaranteed de-CH spelling were not established; no DE-to-FR/IT contract fixture was translated.
  • document_translation Can whole documents be translated with formatting kept? [partial]: DeepL document translation preserves layout for DOC/DOCX, PPT/PPTX, XLS/XLSX, PDF, HTML, TXT, SRT and XLIFF. Layout quality was not fixture-tested. Sources: meingpt:meingpt:translation.
  • translation_engine Which engine translates? [supported]: Default Google Cloud Translate for text and DeepL for documents; own DeepL key switches both to DeepL. Sources: meingpt:meingpt:translation.
  • glossaries Are company glossaries supported? [supported]: Workspace admins create per-language-pair glossaries and import CSV; exact word forms must match. Sources: meingpt:meingpt:translation.
  • formality_and_variants Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Unknown. Formality settings within the translator and guaranteed de-CH spelling were not established; no DE-to-FR/IT contract fixture was translated.
  • writing_tools Are dedicated rewrite and proofreading tools available? [partial]: Quick Actions rewrite answers, including more formal and improve options. Sources: meingpt:meingpt:chat.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:translation, meingpt:meingpt:chat.

WORK-04 Image generation and editing

Judgment rule: Record available image models, editing (inpainting, reference images), admin control and per-image cost visibility, and licence or usage terms for generated images.

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Twelve named image variants include reference editing with administrator model controls.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • image_editing: Reference image generation supports model-dependent uploads; app lacks post-generation crop/color editing.
  • usage_terms: Terms warn third-party output may carry rights; no blanket unrestricted-use warranty is made. C2PA metadata labels generated output.
  • image_generation Can users generate images, with which models? [supported]: FLUX.2 Klein/Pro/Flex/Max, FLUX 1.1 Pro, FLUX.1 Kontext Max; GPT Image 1/Mini/1.5/2; Gemini 2.5 Flash Image and 3 Pro Image. Sources: meingpt:meingpt:images.
  • image_editing Can users edit uploaded images? [partial]: Reference image generation supports model-dependent uploads; app lacks post-generation crop/color editing. Sources: meingpt:meingpt:images.
  • admin_control Can admins restrict image generation? [supported]: Admins enable models and default; request-enabled permissions can restrict Image app use by teams or persons. Sources: meingpt:meingpt:image-admin, meingpt:meingpt:permissions.
  • usage_terms What usage rights apply to output? [partial]: Terms warn third-party output may carry rights; no blanket unrestricted-use warranty is made. C2PA metadata labels generated output. Sources: meingpt:meingpt:terms, meingpt:meingpt:images.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:images, meingpt:meingpt:image-admin, meingpt:meingpt:permissions, meingpt:meingpt:terms.

WORK-05 Voice and meetings

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Dictation and meeting transcription are documented; speech quality was not tested.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • Unverified read_aloud, voice_conversation, swiss_german_speech: No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established.
  • dictation Can users dictate prompts? [supported]: A microphone transcribes prompts into the input field. Sources: meingpt:meingpt:chat.
  • read_aloud Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established.
  • voice_conversation Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established.
  • meeting_summaries Are meetings transcribed and summarised? [supported]: Audio/video/transcript uploads and meeting-bot notes are documented; storage Hetzner Germany, Gladia transcription France, Vertex EU summaries. Sources: meingpt:meingpt:meeting.
  • swiss_german_speech Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:chat, meingpt:meingpt:meeting.

WORK-06 Data analysis and document output

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

Dust

Agent cross-checked Support: supported

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

An isolated EU sandbox executes analysis code and generates downloadable Office files.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • canvas_editing: Downloaded artifacts and an Excel editor exist; editor changes stay local until downloaded and the chat card keeps the original.
  • data_analysis Can it analyse spreadsheets with executed code? [supported]: Python/JavaScript sandbox reads original spreadsheets with pandas/openpyxl and executes code. Sources: meingpt:meingpt:sandbox.
  • charts Can it produce charts? [supported]: Executed matplotlib charts can be returned as PNG. Sources: meingpt:meingpt:sandbox.
  • office_file_output Can it create Word, Excel or PowerPoint files? [supported]: Sandbox libraries support DOCX/XLSX/PPTX; workflows also generate Word/PDF/Excel/CSV/PowerPoint/JSON. Sources: meingpt:meingpt:sandbox, meingpt:meingpt:workflows.
  • canvas_editing Is there a document or canvas editor for iterating on output? [partial]: Downloaded artifacts and an Excel editor exist; editor changes stay local until downloaded and the chat card keeps the original. Sources: meingpt:meingpt:sandbox.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:sandbox, meingpt:meingpt:workflows.

WORK-07 Sharing and team spaces

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Chat links and shared projects exist; projects preserve private member chat histories.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • group_chat: Each project member has a separate private chat list; shared project chats are not a simultaneous group conversation.
  • Unverified share_permission_boundary: No cross-group chat-sharing test was run; recipient access to source attachments and restricted knowledge was not verified.
  • Project chat privacy does not prove absence of every group-chat surface.
  • share_chats Can chats be shared inside the organisation? [supported]: A share toggle creates a link displaying the shared conversation. Sources: meingpt:meingpt:chat.
  • team_spaces Are shared projects or workspaces available? [supported]: Projects share instructions and workflows with Owner/Editor/Member roles. Sources: meingpt:meingpt:projects.
  • group_chat Can several people chat together with the AI? [partial]: Within Projects,each member has a separate private chat list. Simultaneous multi-user group conversation elsewhere was not established. Sources: meingpt:meingpt:projects.
  • share_permission_boundary Does sharing respect the recipient's access to sources? [unknown]: Does sharing respect the recipient's access to sources? Unknown. No cross-group chat-sharing test was run; recipient access to source attachments and restricted knowledge was not verified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:chat, meingpt:meingpt:projects.

WORK-08 Interface languages and accessibility

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Platform-language choice exists, but the full UI and accessibility matrix remains unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • ui_languages: Preferences provide a platform-language selector distinct from response language; a complete named language list is not published on this page.
  • Unverified dach_language_quality, accessibility_statement, admin_ui_languages: No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested.
  • ui_languages Which UI languages are offered? [partial]: Preferences provide a platform-language selector distinct from response language; a complete named language list is not published on this page. Sources: meingpt:meingpt:preferences.
  • dach_language_quality Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested.
  • accessibility_statement Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested.
  • admin_ui_languages Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested.

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

Administration and governance

ADM-01 Single sign-on and authentication

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Microsoft/Google login is included; custom OIDC is enabled on request and SAML is excluded.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • sso_plan: Platform pricing includes Microsoft/Google/Magic Link; own OIDC needs workspace enablement, while Governance prices Entra group sync and provisioning. Exact custom-OIDC fee is not stated.
  • sso_protocols Which SSO protocols and identity providers work? [supported]: Google and Microsoft sign-in plus custom OpenID Connect for Entra, Keycloak, Okta, PingFederate and Authentik. SAML is not supported. Sources: meingpt:meingpt:sso.
  • sso_plan Which plan includes SSO? [partial]: Platform pricing includes Microsoft/Google/Magic Link; own OIDC needs workspace enablement, while Governance prices Entra group sync and provisioning. Exact custom-OIDC fee is not stated. Sources: meingpt:meingpt:sso, meingpt:meingpt:prices.
  • mfa Can MFA be enforced? [supported]: MFA is enforced at the customer IdP; disabling a user prevents new sign-ins but does not immediately invalidate an existing session. Sources: meingpt:meingpt:sso.
  • conditional_access Do Entra conditional-access policies apply? [supported]: Customer IdP controls Conditional Access. Existing sessions expire normally unless separately removing the membership. Sources: meingpt:meingpt:sso.
  • domain_capture Can the company claim its email domain? [supported]: DNS TXT verification enables domain auto-join and optional rejection of invitations into other workspaces; existing external memberships remain. Sources: meingpt:meingpt:sso.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:sso, meingpt:meingpt:prices.

ADM-02 User provisioning and lifecycle

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Governance includes SCIM; user provisioning and login-time group sync have separate effects.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform plus Governance provisioning add-on; add_ons=Governance; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • group_sync: Entra group-to-team synchronization is separate from user-only SCIM and adds memberships on login. It is not a general bidirectional SCIM-group sync.
  • deprovisioning: SCIM deactivates membership, preserves data and releases the seat. Shared-asset transfer behavior was not trial-tested.
  • scim Is SCIM provisioning supported? [supported]: Entra SCIM v1 creates/updates/deactivates users, requires a verified domain and workspace enablement, and replaces manual invitations. Sources: meingpt:meingpt:scim, meingpt:meingpt:prices.
  • group_sync Are identity-provider groups synced? [partial]: Entra group-to-team synchronization is separate from user-only SCIM and adds memberships on login. It is not a general bidirectional SCIM-group sync. Sources: meingpt:meingpt:scim, meingpt:meingpt:sso.
  • jit_provisioning Are users created at first login? [supported]: Custom OIDC can join a verified-domain workspace on first authenticated login; plain Microsoft sign-in alone does not grant workspace membership. Sources: meingpt:meingpt:sso, meingpt:meingpt:scim.
  • deprovisioning What happens to a removed user's data and shared assets? [partial]: SCIM deactivates membership, preserves data and releases the seat. Shared-asset transfer behavior was not trial-tested. Sources: meingpt:meingpt:scim.
  • seat_assignment Can admins assign and reclaim seats? [supported]: New SCIM users start as unlicensed viewers unless automatic seat assignment is on; admins can assign seats. Sources: meingpt:meingpt:scim.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:scim, meingpt:meingpt:prices, meingpt:meingpt:sso.

ADM-03 Roles, groups and feature permissions

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Role and group controls include request-enabled app permissions and model restrictions.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • multi_entity: Multiple workspaces can represent separate companies, but each has separate credit and billing; a unified multi-entity contract was not established.
  • admin_roles Which admin roles exist, and can admin rights be delegated? [supported]: Admin, Member and Viewer; unlimited workspace admins and separate team administrators are documented. Workspace admins consume a seat and bypass restrictions. Sources: meingpt:meingpt:roles, meingpt:meingpt:permissions.
  • groups Can permissions be set per group? [supported]: Teams control shared resources and models; admins see all team-shared assets. Sources: meingpt:meingpt:roles, meingpt:meingpt:config.
  • feature_toggles Which features can be switched on or off per group? [supported]: Request-enabled controls restrict image, meeting notes/bot, translation, web, Voice Agent, Buddy and automation use by teams or persons. Sources: meingpt:meingpt:permissions.
  • multi_entity Can subsidiaries or departments be separated within one contract? [partial]: Multiple workspaces can represent separate companies, but each has separate credit and billing; a unified multi-entity contract was not established. Sources: meingpt:meingpt:sso.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:roles, meingpt:meingpt:permissions, meingpt:meingpt:config, meingpt:meingpt:sso.

ADM-04 Usage and adoption analytics

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

Dust

Agent cross-checked Support: partial

Consumption analytics has detailed attribution and exports without message content.

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Adoption metrics and cost CSVs have team and anonymization options.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • breakdowns: Usage-based plans report costs by user, team, model and platform/API; complete assistant/feature breakdown is not demonstrated.
  • adoption_dashboard Is there an adoption dashboard? [supported]: Cockpit lists prompts, active users, daily prompts/workflow runs and popular workflows. Sources: meingpt:meingpt:analytics.
  • breakdowns Can usage be broken down by group, model, feature and assistant? [partial]: Usage-based plans report costs by user, team, model and platform/API; complete assistant/feature breakdown is not demonstrated. Sources: meingpt:meingpt:analytics.
  • export Can usage data be exported? [supported]: User/team cost statistics export to CSV. Sources: meingpt:meingpt:analytics.
  • privacy_modes Can per-person reporting be limited or pseudonymised? [supported]: Metric anonymization replaces names with IDs; top-user metrics depend on that setting. Sources: meingpt:meingpt:analytics.

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

ADM-05 Spend controls and cost allocation

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Personal category budgets and pooled credit provide controls with documented exceptions.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • budget_enforcement: Zero blocks new category use and API exhaustion returns 403; running meeting bots can overshoot and automated runs are outside personal categories.
  • chargeback: CSV cost exports exist by user/team; formal cost-centre coding is not established.
  • cost_visibility Can admins see cost or consumption per user and group? [supported]: Usage-based plans show EUR costs per user/model and team, separately for platform and API. Sources: meingpt:meingpt:analytics.
  • budgets Can budgets be set per user or group? [supported]: Six personal usage levels configure monthly budgets across five categories and are assigned singly or in bulk. Sources: meingpt:meingpt:limits.
  • budget_enforcement Does reaching a budget alert, block or downgrade? [partial]: Zero blocks new category use and API exhaustion returns 403; running meeting bots can overshoot and automated runs are outside personal categories. Sources: meingpt:meingpt:limits, meingpt:meingpt:api.
  • chargeback Can costs be exported per cost centre? [partial]: CSV cost exports exist by user/team; formal cost-centre coding is not established. Sources: meingpt:meingpt:analytics.

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

ADM-06 Audit logs and compliance export

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Administrative change exports and a separate Outpost search log have distinct retention.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • admin_events: Administrative settings and SCIM changes are logged with actor and changes; a login/security-event coverage inventory and tamper-evidence model were not found.
  • content_logging: The settings-change log explicitly excludes conversation contents; a separate API-logging setting exists but prompt/response compliance-retention coverage is unclear.
  • siem_export: CSV/JSON filtered audit export, 10000 entries/20 MiB/two minutes per export; SIEM streaming is not established.
  • Unverified ediscovery: No legal-hold or eDiscovery documentation was located; immutable audit storage and full content-logging configuration were not established.
  • admin_events Are admin and security events logged? [partial]: Administrative settings and SCIM changes are logged with actor and changes; a login/security-event coverage inventory and tamper-evidence model were not found. Sources: meingpt:meingpt:audit, meingpt:meingpt:scim.
  • content_logging Can prompts and answers be retained for compliance, and is it configurable? [partial]: The settings-change log explicitly excludes conversation contents; a separate API-logging setting exists but prompt/response compliance-retention coverage is unclear. Sources: meingpt:meingpt:audit.
  • siem_export Can logs stream to a SIEM or be exported? [partial]: CSV/JSON filtered audit export, 10000 entries/20 MiB/two minutes per export; SIEM streaming is not established. Sources: meingpt:meingpt:audit-export.
  • ediscovery Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Unknown. No legal-hold or eDiscovery documentation was located; immutable audit storage and full content-logging configuration were not established.
  • log_retention How long are logs kept? [supported]: Administrative settings changes are retained indefinitely; Governance Outpost query records are retained 90 days from enablement. Sources: meingpt:meingpt:audit.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:audit, meingpt:meingpt:scim, meingpt:meingpt:audit-export.

ADM-07 Data loss prevention and personal data

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

Dust

No public information found Support: not-published

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

meinGPT

No public information found Support: not-published

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

ADM-08 AI policy and guardrails

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Workspace instructions and Governance acknowledgements are documented; policy enforcement breadth is limited.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • org_instructions: Additional Chat Context is a workspace-wide system instruction, not a guaranteed enforcement layer.
  • content_filters: Provider content filtering can stop output; configurable organization-wide topic filters were not established.
  • Unverified violation_reporting: Admin policy-violation reporting was not established in Compliance Controls; no guardrail fixture was run.
  • org_instructions Can admins set organisation-wide instructions? [partial]: Additional Chat Context is a workspace-wide system instruction, not a guaranteed enforcement layer. Sources: meingpt:meingpt:config.
  • usage_notice Can users be required to accept a usage policy? [supported]: Governance includes multilingual acceptable-use policies for acknowledgement and mandatory courses that block other pages until complete. Sources: meingpt:meingpt:prices, meingpt:meingpt:audit.
  • content_filters Are content filters configurable? [partial]: Provider content filtering can stop output; configurable organization-wide topic filters were not established. Sources: meingpt:meingpt:api.
  • violation_reporting Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. Admin policy-violation reporting was not established in Compliance Controls; no guardrail fixture was run.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:config, meingpt:meingpt:prices, meingpt:meingpt:audit, meingpt:meingpt:api.

Data protection and sovereignty

DATA-01 Hosting location and data residency

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Germany platform storage and model-specific EU/global routes must be scoped separately.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • inference_region: Azure Sweden/France, Vertex Frankfurt, Mistral France/Sweden, OpenAI EU endpoint, Nebius Finland, TensorX Ireland and other conditional routes. Some image variants remain Global; the accepted DPA governs authorized exceptions.
  • backups_logs_region: Scaleway France is conditional backup infrastructure; log/telemetry locations are not separately specified.
  • residency_plan: DPA 2.0.1 governs new acceptance since 24 September; existing customers retain agreed versions. EU inference depends on selected/approved routes; section 4(3) permits listed/instructed third-country transfers.
  • Unverified support_access_region, swiss_hosting: No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found.
  • storage_region Where are chats, files and indexes stored? [supported]: Hetzner Germany hosts chats, accounts, documents and cloud indexes; register identifies Nürnberg/Falkenstein. Sources: meingpt:meingpt:pools, meingpt:meingpt:subprocessors.
  • inference_region Where do model calls run, per provider? [partial]: Azure Sweden/France, Vertex Frankfurt, Mistral France/Sweden, OpenAI EU endpoint, Nebius Finland, TensorX Ireland and other conditional routes. Some image variants remain Global; the accepted DPA governs authorized exceptions. Sources: meingpt:meingpt:subprocessors, meingpt:meingpt:image-admin, meingpt:meingpt:dpa.
  • backups_logs_region Where are backups, logs and telemetry? [partial]: Scaleway France is conditional backup infrastructure; log/telemetry locations are not separately specified. Sources: meingpt:meingpt:subprocessors, meingpt:meingpt:dpa.
  • support_access_region From where can vendor staff access data? [unknown]: From where can vendor staff access data? Unknown. No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found.
  • swiss_hosting Is Swiss hosting available? [unknown]: Is Swiss hosting available? Unknown. No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found.
  • residency_plan Which plan or option provides residency? [partial]: DPA 2.0.1 governs new acceptance since 24 September; existing customers retain agreed versions. EU inference depends on selected/approved routes; section 4(3) permits listed/instructed third-country transfers. Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pools, meingpt:meingpt:subprocessors, meingpt:meingpt:image-admin, meingpt:meingpt:dpa, meingpt:meingpt:dpa-page.

DATA-02 Deployment options

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

SaaS is offered; terms permit individually agreed on-premise use, while Outpost is a connector.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace, meinGPT Outpost local connector; version=Public documentation checked 2026-10-21; plan=Public SaaS; on-premise only if specifically contracted; add_ons=none stated; deployment_mode=not specified; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • on_premise: Terms section 1a permits the whole software in customer data centres when agreed in the licence contract. The linked on-premise-requirements URL redirects to the generic security page; minimum seats and setup/operator terms are not public.
  • mode_feature_gaps: The code sandbox remains in Frankfurt cloud even for on-premise customers; there is no complete mode parity list.
  • Unverified dedicated_instance, customer_cloud, air_gapped: Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes.
  • multi_tenant_saas Is a shared SaaS offered? [supported]: The public web workspace and shared organization API limits establish the managed SaaS offer. Sources: meingpt:meingpt:terms, meingpt:meingpt:api.
  • dedicated_instance Is a dedicated single-tenant instance offered, from what size? [unknown]: Is a dedicated single-tenant instance offered, from what size? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes.
  • 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? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes.
  • on_premise Can the whole platform run on customer infrastructure, from what size? [partial]: Terms section 1a permits the whole software in customer data centres when agreed in the licence contract. The linked on-premise-requirements URL redirects to the generic security page; minimum seats and setup/operator terms are not public. Sources: meingpt:meingpt:terms.
  • air_gapped Can it run without internet access? [unknown]: Can it run without internet access? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes.
  • mode_feature_gaps Which features are missing outside SaaS? [partial]: The code sandbox remains in Frankfurt cloud even for on-premise customers; there is no complete mode parity list. Sources: meingpt:meingpt:sandbox.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:terms, meingpt:meingpt:api, meingpt:meingpt:sandbox.

DATA-03 Training use and provider retention

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

DPA 2.0.1 prohibits training and marks conditional AI services for no permanent provider content copy.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • provider_retention: Annex 4 defines ZDR as no permanent copy on the provider infrastructure; exact abuse-monitoring time and exceptions are not specified.
  • zero_retention: Conditional AI/function services in Annex 4 carry ZDR, while SelectCode-controlled storage remains separate; applies to the accepted DPA version.
  • Unverified human_review: Human provider-review rights and per-model transient/abuse-retention durations are not disclosed in the accepted-form DPA or data-flow guide.
  • vendor_training Does the vendor train on customer content? [supported]: Section 5(5) restricts processing to service delivery and excludes other purposes. Sources: meingpt:meingpt:dpa.
  • provider_training Do model providers train on it under this product's contracts? [supported]: Section 5(5) states no subprocessor uses customer data to train its own AI model. Sources: meingpt:meingpt:dpa.
  • provider_retention How long do model providers keep prompts, including for abuse monitoring? [partial]: Annex 4 defines ZDR as no permanent copy on the provider infrastructure; exact abuse-monitoring time and exceptions are not specified. Sources: meingpt:meingpt:dpa.
  • zero_retention Is zero data retention available, and on which plan? [partial]: Conditional AI/function services in Annex 4 carry ZDR, while SelectCode-controlled storage remains separate; applies to the accepted DPA version. Sources: meingpt:meingpt:dpa.
  • human_review Can provider staff review content? [unknown]: Can provider staff review content? Unknown. Human provider-review rights and per-model transient/abuse-retention durations are not disclosed in the accepted-form DPA or data-flow guide.

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

DATA-04 Retention and deletion

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Ordinary chat removal archives; admin retention and contractual deletion use different mechanisms.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • user_deletion: Chat removal does not permanently delete messages or attachments; final account deletion is requested by the administrator via support. Generated images/text translations have their own deletion controls.
  • default_retention What is retained and for how long by default? [supported]: Chat/file data stays until instructed deletion; UI Chat löschen archives. Text translations remain until user deletion; document translations persist until account/workspace deletion. Sources: meingpt:meingpt:flow, meingpt:meingpt:translation.
  • admin_retention Can admins set retention periods? [supported]: Release 2.67.0 adds disabled-by-default deletion periods for chats, meetings and automation runs, with a 24-hour wait before a new/shorter period applies. Sources: meingpt:meingpt:changes.
  • user_deletion Can users delete their chats and files permanently? [partial]: Chat removal does not permanently delete messages or attachments; final account deletion is requested by the administrator via support. Generated images/text translations have their own deletion controls. Sources: meingpt:meingpt:flow, meingpt:meingpt:security, meingpt:meingpt:images, meingpt:meingpt:translation.
  • contract_end_deletion What is deleted at contract end, and when? [supported]: DPA section 12 requires return or requested deletion, including backups, within 30 days after termination or an agreed export window; statutory retention exceptions apply and proof is available on request. Sources: meingpt:meingpt:dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:flow, meingpt:meingpt:translation, meingpt:meingpt:changes, meingpt:meingpt:security, meingpt:meingpt:images, meingpt:meingpt:dpa.

DATA-05 Sub-processors and foreign-law exposure

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

DPA and processing register name providers, conditional use and advance change notices.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • parent_jurisdiction: SelectCode GmbH is a German entity; the security site describes it as independent. A separately owned parent was not identified.
  • subprocessor_list Is a dated sub-processor list published? [supported]: DPA Annex 4 is dated 24 September 2026; live function/region register is also public. Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors.
  • subprocessor_countries Which countries do sub-processors operate in? [supported]: Contract entities include Germany, Netherlands, Slovenia, Luxembourg, France, Ireland and Finland. Processing register names Germany platform, France backups, Finland, Ireland, Sweden/France and Frankfurt inference routes; EU symbol is processing, not ownership. Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors.
  • change_notification Are customers notified of sub-processor changes? [supported]: Section 9 requires notice before additions/replacements and gives two weeks to object on important data-protection grounds, with specified termination rights. Sources: meingpt:meingpt:dpa.
  • parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: SelectCode GmbH is a German entity; the security site describes it as independent. A separately owned parent was not identified. Sources: meingpt:meingpt:terms, meingpt:meingpt:subprocessors.
  • transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [supported]: DPA section 4(3) uses GDPR Article 45 adequacy or Article 46 safeguards for disclosed/instructed transfers; it does not promise a blanket absence of third-country processing. Sources: meingpt:meingpt:dpa.
  • government_access_policy Is there a published government-access or transparency policy? [supported]: Section 7 requires notification where lawful, review/challenge of disproportionate requests, minimization and no compliance with unrecognized third-country requests. Sources: meingpt:meingpt:dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors, meingpt:meingpt:terms.

DATA-06 Contracts and regulatory coverage

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

A public GDPR DPA and German-law terms are available; sector coverage needs qualification.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • dpa: Version 2.0.1 is a public signed-form or electronic-acceptance DPA; negotiability is not promised.
  • revdsg_gdpr: GDPR Article 28 governs the DPA; an explicit Swiss revDSG annex was not found.
  • ai_act_materials: Governance includes usage policies and mandatory training; automated EU AI Act use-case checks are labelled Coming soon, so a complete current provider/deployer dossier was not established.
  • sector_materials: Governance offers a separate section 203 German professional-secrecy agreement; FINMA-specific materials were not found.
  • dpa Is a DPA available, and is it negotiable? [partial]: Version 2.0.1 is a public signed-form or electronic-acceptance DPA; negotiability is not promised. Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa.
  • revdsg_gdpr Does the DPA cover revDSG and GDPR? [partial]: GDPR Article 28 governs the DPA; an explicit Swiss revDSG annex was not found. Sources: meingpt:meingpt:dpa.
  • governing_law Which law and court govern the contract? [supported]: DPA section 13 uses German law; terms choose the competent court at the vendor seat. Sources: meingpt:meingpt:dpa, meingpt:meingpt:terms.
  • ai_act_materials Is EU AI Act documentation provided? [partial]: Governance includes usage policies and mandatory training; automated EU AI Act use-case checks are labelled Coming soon, so a complete current provider/deployer dossier was not established. Sources: meingpt:meingpt:prices.
  • sector_materials Are FINMA or other sector materials provided? [partial]: Governance offers a separate section 203 German professional-secrecy agreement; FINMA-specific materials were not found. Sources: meingpt:meingpt:prices.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa, meingpt:meingpt:terms, meingpt:meingpt:prices.

DATA-07 Certifications and attestations

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

ISO and penetration-test documents are advertised behind email access; certificates were not independently verified.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • iso_27001: DPA Annex 3 states ISO/IEC 27001:2022 certificate DE-IS-20250256, Proks Certification GmbH, development/operation of MeinGPT SaaS and custom services, valid to 2028-12-16. The certificate/issuer record was not obtained, so this remains a vendor claim.
  • c5: The register attributes BSI C5 to Hetzner infrastructure, not to the MeinGPT service.
  • pentest: A SySS 2025 penetration-test certificate is listed but its result/scope and validity were not retrieved.
  • Unverified soc2, other_certifications: SOC 2 and other product attestations were not established. No email-gated report was requested.
  • iso_27001 ISO 27001 with scope and validity? [partial]: DPA Annex 3 states ISO/IEC 27001:2022 certificate DE-IS-20250256, Proks Certification GmbH, development/operation of MeinGPT SaaS and custom services, valid to 2028-12-16. The certificate/issuer record was not obtained, so this remains a vendor claim. Sources: meingpt:meingpt:dpa, meingpt:meingpt:trust.
  • soc2 SOC 2 type, period and covered service? [unknown]: SOC 2 type, period and covered service? Unknown. SOC 2 and other product attestations were not established. No email-gated report was requested.
  • c5 BSI C5 attestation? [partial]: The register attributes BSI C5 to Hetzner infrastructure, not to the MeinGPT service. Sources: meingpt:meingpt:subprocessors.
  • other_certifications Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Unknown. SOC 2 and other product attestations were not established. No email-gated report was requested.
  • report_access How can customers obtain reports? [supported]: The trust centre asks for email-based access for ISO and SySS 2025 penetration-test documents. Sources: meingpt:meingpt:trust.
  • pentest Are independent penetration test summaries available? [partial]: A SySS 2025 penetration-test certificate is listed but its result/scope and validity were not retrieved. Sources: meingpt:meingpt:trust.

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

DATA-08 Encryption and key control

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Encryption and logical tenancy are documented; key and private-networking details remain incomplete.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Business/Enterprise hosted workspace; CMK entitlement excluded from verified findings; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • CMK is an access/entitlement gap, not an absent capability.
  • encryption_at_rest Is data encrypted at rest? [supported]: Security guide states AES-256 at rest and TLS 1.3; DPA Annex 3 includes encryption at rest/transit. Sources: meingpt:meingpt:security, meingpt:meingpt:dpa.
  • customer_managed_keys Can the customer manage or hold the keys? [unknown]: Unknown for Business or Enterprise. The security FAQ says Customer Managed Keys are on request but does not identify an eligible tier, price, key custody or location. No plan-scoped CMK commitment was verified.
  • private_networking Is private connectivity or IP restriction available? [unknown]: Is private connectivity or IP restriction available? Unknown. A private-link/IP allowlist/VPN product entitlement was not established; Outpost outbound TLS is a source connector rather than a private SaaS endpoint.
  • tenant_isolation How are customers separated in shared SaaS? [partial]: DPA Annex 3 specifies logical tenant separation and network segmentation; no independent isolation test was run. Sources: meingpt:meingpt:dpa.

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

DATA-09 Professional secrecy

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

The base AGB contains conditional professional-secrecy duties. Eligibility and executed terms of the separately marketed Governance addendum remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked2026-10-21; plan=Business/Enterprise customer contracts incorporating AGB section12(4); only the base-terms obligation is assessed; add_ons=Separate Governance addendum excluded from verified entitlement; contract required; deployment_mode=multi-tenant-saas; region=Germany/EU platform; model route and deployment exceptions apply; os=not specified.

Limitations

  • The base-terms duties and a separately executed Governance addendum are separate legal documents. No claim that one depends on purchase of the other is made.
  • secrecy_undertaking Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [partial]: For contracts incorporating the published AGB, section12(4) applies when processed data fall under professional secrecy, including §203. It imposes indefinite confidentiality, access only as necessary to perform services and acknowledgement of criminal duties. The clause states no Governance prerequisite. It does not establish a separately executed addendum or Swiss Art321 coverage. Sources: meingpt:meingpt:secrecy-contract-rev2.
  • subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [partial]: Section12(4) requires staff/subcontractors who can access covered data to be bound in at least text form. Subcontracting and services outside the EU require text consent, deemed granted for known providers at contract start. Provider-specific executed undertakings were not retrieved. Sources: meingpt:meingpt:secrecy-contract-rev2.
  • secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: Unknown whether the separate Governance §203 addendum is available with self-service Business or only a contracted platform offer. The calculator lists it under Governance at EUR1.35/user/month annually, but this is not proof of eligibility or a fee for the base AGB duties. Sources: meingpt:meingpt:prices-rev2.
  • content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: The base AGB restrict knowledge of covered data to what is necessary for the contracted service. The clause does not promise that staff or model providers can never see plaintext. Agreement-specific access restrictions beyond section12(4) were not verified. Sources: meingpt:meingpt:secrecy-contract-rev2.
  • secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [partial]: The public AGB section12(4) is the verified contract text. A separately executed/template Governance addendum and provider-by-provider undertakings were not obtained. Sources: meingpt:meingpt:secrecy-contract-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:secrecy-contract-rev2, meingpt:meingpt:prices-rev2.

Commercials and vendor

VEN-01 Pricing model and list prices

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Self-service Business costs EUR29/user/month excluding VAT and includes standard-model use. Enterprise and platform-module pricing are outside this scoped offer.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Self-service Business, monthly billing only; contracted Enterprise/platform calculator excluded; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • The progressive platform calculator is not used as a Business tariff. Its contract eligibility remains outside this finding.
  • pricing_unit What is the pricing unit? [supported]: Business is sold per user per month through self-service Stripe checkout. Premium/reasoning models, API use and meeting-bot recordings are separately metered. Sources: meingpt:meingpt:billing-rev2.
  • list_prices What are list prices per plan, with date and currency? [supported]: Self-service Business is EUR29/user/month, excluding VAT, on monthly billing. No annual discount or progressive marginal tiers are applied to this offer. Sources: meingpt:meingpt:billing-rev2.
  • included_usage What usage is included? [partial]: Standard-model use in Business is unlimited according to the billing guide. Premium/reasoning models, API and meeting bots remain additional; the exact standard-model catalog and any applicable workload restrictions are not fixed by this page. Sources: meingpt:meingpt:billing-rev2.
  • add_ons Which features cost extra? [unknown]: Unknown for self-service Business. The separate platform calculator has Governance/Outpost modules, but their Business eligibility and package prices were not established.
  • overage What do usage beyond limits and premium models cost? [partial]: Business standard models do not consume additional billed usage under the billing guide. Premium/reasoning, API and meeting-bot use draw on workspace credit; meeting bots cost EUR0.80/audio hour. Other route-specific charges depend on the selected service. Sources: meingpt:meingpt:billing-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:billing-rev2.

VEN-02 Scenario cost

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Business-only seat floors are EUR69600 / EUR348000 / EUR1740000 for200/1000/5000 users over12months, each plus unknown workload and contract components.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Self-service Business at EUR29/user/month, paid monthly for12months; Business standard-chat floor only; add_ons=No paid add-ons included; required extras unknown; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • ALM-14 shared cost assumptions v1.4, 2026-10-21:12months, list prices, excluding VAT;60% light100,30% regular400,10% power1500 messages/user/month;3000 input and600 output tokens/message. Weighted330messages,0.99M input/0.198M output per user/month. Token mix is used only on separately billed routes; this Business standard-chat floor has included usage.
  • ECB2026-10-20 EUR1=USD1.1215=CHF0.9237. Vendor currency EUR is primary. Contract-specific extras remain unknown.
  • cost_200 Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 200 users over12months: from EUR69600.00 / CHF64289.52 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx.
  • cost_1000 Year-one cost at 1,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 1000 users over12months: from EUR348000.00 / CHF321447.60 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx.
  • cost_5000 Year-one cost at 5,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 5000 users over12months: from EUR1740000.00 / CHF1607238.00 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx.
  • variable_share Which part depends on usage? [partial]: Business standard-model chat is included. A model-preserving workload outside that standard catalog, premium/reasoning models, API and meeting-bot charges cannot be quantified without the actual route and contract; the variable remainder stays unknown. No provider proxy or progressive-platform tariff is substituted. Sources: meingpt:meingpt:billing-rev2.
  • unknown_parts Which costs could not be priced? [partial]: Business eligibility for200/1000/5000 users, standard-model mapping, premium/tool use, required Governance/Outpost, rollout and Enterprise services remain unknown. No progressive-platform amount is mixed into the Business floor. Sources: meingpt:meingpt:billing-rev2.

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

VEN-03 Evaluation access

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

A self-serve 10-day trial exists, while several enterprise features still need enablement.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • free_tier: Trial expiry locks the workspace even for free models; the guide does not describe a permanent free business workspace.
  • trial_scope: Most base functions are included; personal API keys are off, and request-only meeting/live recording and automations are initially off as in paid plans. SCIM/SSO enterprise enablement is not guaranteed.
  • sales_gate: Base trial is self-serve; request-enabled features and Enterprise terms are not self-service. No sales contact was made.
  • free_tier Is there a free tier for business use? [partial]: Trial expiry locks the workspace even for free models; the guide does not describe a permanent free business workspace. Sources: meingpt:meingpt:billing.
  • self_serve_trial Is a self-serve business trial available? [supported]: 10 days, EUR 5 after phone verification, no payment details or automatic paid conversion, up to ten emailed invitees. Sources: meingpt:meingpt:billing.
  • trial_scope Do trials include SSO, connectors and admin features? [partial]: Most base functions are included; personal API keys are off, and request-only meeting/live recording and automations are initially off as in paid plans. SCIM/SSO enterprise enablement is not guaranteed. Sources: meingpt:meingpt:billing.
  • sales_gate Does meaningful evaluation require sales contact? [partial]: Base trial is self-serve; request-enabled features and Enterprise terms are not self-service. No sales contact was made. Sources: meingpt:meingpt:billing.

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

VEN-04 Contract terms and pricing transparency

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Public price fields and German contract defaults exist; customer-specific terms and CHF invoicing remain open.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • minimum_commitment: Public calculator starts at one user; individually negotiated Enterprise or on-prem minimums are not stated.
  • local_invoicing: SelectCode GmbH is the German contracting entity and prices are EUR; CHF invoices were not confirmed.
  • transparency_class: Partially specified: public marginal seat/model/add-on rates, but PII base, services and deployments are quote-only and Business packaging differs.
  • minimum_commitment What seat or spend minimum applies? [partial]: Public calculator starts at one user; individually negotiated Enterprise or on-prem minimums are not stated. Sources: meingpt:meingpt:prices.
  • contract_length What contract lengths are offered? [supported]: Public calculator has annual/monthly options; terms default to one year absent another agreement. Sources: meingpt:meingpt:prices, meingpt:meingpt:terms.
  • cancellation How can the contract be cancelled or reduced? [supported]: Absent other terms, three months before term-end, text/email or admin cancellation; downgrades/user reductions effective following month, no current-month refund. Price changes require the stated notice/consent procedure. Sources: meingpt:meingpt:terms.
  • local_invoicing Can it be invoiced in CHF or EUR from a European entity? [partial]: SelectCode GmbH is the German contracting entity and prices are EUR; CHF invoices were not confirmed. Sources: meingpt:meingpt:terms.
  • transparency_class Is pricing transparent, partial, quote-only or unknown? [partial]: Partially specified: public marginal seat/model/add-on rates, but PII base, services and deployments are quote-only and Business packaging differs. Sources: meingpt:meingpt:prices, meingpt:meingpt:billing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:prices, meingpt:meingpt:terms, meingpt:meingpt:billing.

VEN-05 Source licence

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

The public AGB establish a commercial subscription/rental use licence with contract-limited rights. Public component source licences and a distinct enterprise source-edition mapping remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • Contractual service-use rights do not establish the licence of every server/client/connector dependency.
  • No public implementation repository or enterprise source-edition map was identified.
  • licence_type Which licence applies to each component? [partial]: SelectCode AGB describe the software as a subscription/rental and grant a non-exclusive use right limited to the contract term. Public display, adaptation, translation and decompilation of the software are restricted subject to statutory rights. This establishes the commercial service-use licence; a client/server/connector source-licence inventory and current implementation revision remain unpublished. Sources: meingpt:meingpt:terms-20261026.
  • branding_restrictions Do licence terms restrict branding or user counts? [partial]: AGB require purchased licences for majority-owned affiliates and give no independent right to sublicense or transfer usage rights. They restrict adapting the software. A numerical user cap or a component-specific branding licence is not established by these clauses. Sources: meingpt:meingpt:terms-20261026.
  • enterprise_features_closed Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Unknown. The public commercial terms describe rented software, but no public client/server/connector source licence or current repository revision was located. Repository visibility was not treated as a licence. Rechecked 2026-10-26 in Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. Official links and targeted first-party searches yielded no further plan-scoped specification for the remaining atom.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: meingpt:meingpt:terms-20261026.

VEN-06 Data export and exit

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Individual downloads exist but a bulk chat export is explicitly unavailable.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • chat_export: Security FAQ explicitly says there is currently no function to export all chats at once.
  • export_format: Individual artifacts/slides/files/images can be downloaded; administrative logs have CSV/JSON exports. This does not establish portable assistants or a complete knowledge export.
  • post_termination_window: Terms permit export until termination takes effect; later access is blocked. DPA allows an individually agreed export window and return/deletion within 30 days after it.
  • Unverified assistant_export, knowledge_export: No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run.
  • chat_export Can admins export all chats? [unsupported]: Security FAQ explicitly says there is currently no function to export all chats at once. Sources: meingpt:meingpt:security.
  • assistant_export Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unknown. No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run.
  • knowledge_export Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? Unknown. No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run.
  • export_format Are formats documented and machine-readable? [partial]: Individual artifacts/slides/files/images can be downloaded; administrative logs have CSV/JSON exports. This does not establish portable assistants or a complete knowledge export. Sources: meingpt:meingpt:security, meingpt:meingpt:audit-export.
  • post_termination_window How long can data be retrieved after termination? [partial]: Terms permit export until termination takes effect; later access is blocked. DPA allows an individually agreed export window and return/deletion within 30 days after it. Sources: meingpt:meingpt:terms, meingpt:meingpt:dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:security, meingpt:meingpt:audit-export, meingpt:meingpt:terms, meingpt:meingpt:dpa.

VEN-07 Support and service levels

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

German vendor support and a public incident history are documented; an uptime credit schedule was not found.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • support_channels: Terms provide email support Monday-Friday 09:00-17:00; timezone and plan-specific guaranteed response times are not stated.
  • Unverified support_languages, uptime_sla: Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage.
  • support_channels Which support channels are available on each plan? [partial]: Terms provide email support Monday-Friday 09:00-17:00; timezone and plan-specific guaranteed response times are not stated. Sources: meingpt:meingpt:terms.
  • support_languages Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage.
  • regional_presence Is there a DACH or Swiss entity, team or partner? [supported]: SelectCode GmbH contracts from Unterhaching, Germany. Sources: meingpt:meingpt:terms.
  • uptime_sla Is there an uptime SLA with credits? [unknown]: Is there an uptime SLA with credits? Unknown. Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage.
  • status_page Is there a public status page with history? [supported]: Public status.meingpt.com lists the platform and historical incidents; uptime is not an SLA. Sources: meingpt:meingpt:status.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:terms, meingpt:meingpt:status.

VEN-08 Onboarding, training and adoption

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

Dust

Agent cross-checked Support: partial

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

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

Limitations

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

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

meinGPT

Agent cross-checked Support: partial

Learning paths and business examples are built in; personal rollout services are quote-based.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • onboarding_service: Personal guidance covers selection, pilot and rollout on an individual offer; universal included consulting is not promised.
  • user_training: The learning area has guided practical courses; Governance enables mandatory assignments. Complete course language coverage was not stated.
  • adoption_programme: Pilot/adoption workspaces typically run a three-month fixed-price pilot with workshops; a defined champion programme was not found.
  • onboarding_service Is guided onboarding included? [partial]: Personal guidance covers selection, pilot and rollout on an individual offer; universal included consulting is not promised. Sources: meingpt:meingpt:prices.
  • user_training Is end-user training offered, in which languages? [partial]: The learning area has guided practical courses; Governance enables mandatory assignments. Complete course language coverage was not stated. Sources: meingpt:meingpt:academy, meingpt:meingpt:audit.
  • use_case_library Are role-based use cases and templates provided? [supported]: Role/department personalization and business-use-case material are documented. Sources: meingpt:meingpt:academy.
  • adoption_programme Is there a champion or adoption programme? [partial]: Pilot/adoption workspaces typically run a three-month fixed-price pilot with workshops; a defined champion programme was not found. Sources: meingpt:meingpt:billing.
  • service_cost Which services cost extra? [supported]: Personal guidance is quote-only; terms bill services by time/person-days or individually agreed fixed price. Sources: meingpt:meingpt:prices, meingpt:meingpt:terms.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:prices, meingpt:meingpt:academy, meingpt:meingpt:audit, meingpt:meingpt:billing, meingpt:meingpt:terms.

Sources

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

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

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

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

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

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

  3. Dust changelog dust:dust:changelog

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

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

  4. Conversation Files dust:dust:files

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

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

  5. Dust Pricing dust:dust:pricing

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

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

  6. Alle Modelle | MeinGPT Docs meingpt:meingpt:rates

    Public EUR token and service rates include GPT-5 mini at EUR 0.30 input and EUR 2.40 output per million tokens.

    Text-generation, translation, images and other-functions tables · documented · Source date not stated · Retrieved 2026-10-21

  7. Modelle | MeinGPT Docs meingpt:meingpt:models-rev2

    Current documentation lists selectable non-Meta model families, per-chat selection and context-length routing; the lifecycle table contains no current selectable Meta model.

    Model picker, model tables and own-LLM-key FAQ · documented · Source date not stated · Retrieved 2026-10-21

  8. Modell-Lifecycle | MeinGPT Docs meingpt:meingpt:lifecycle-rev2

    Active models, future retirement dates and automatic replacement rules are published.

    Phases, notice period and current-model table · documented · Source date not stated · Retrieved 2026-10-21

  9. Modell-Lifecycle | MeinGPT Docs meingpt:meingpt:lifecycle

    Active models, future retirement dates and automatic replacement rules are published.

    Phases, notice period and current-model table · documented · Source date not stated · Retrieved 2026-10-21

  10. Was wir zuletzt released haben | MeinGPT | KI-Use-Case-Plattform für den Mittelstand meingpt:meingpt:changes

    Release 2.67.0 on 18 October adds Gemini 4 Argon, retires named models and adds configurable deletion periods.

    v2.67.0, model retirement and deletion periods · documented · Source date 2026-10-18 · Retrieved 2026-10-21

  11. Modelle | MeinGPT Docs meingpt:meingpt:models

    Users choose models per chat; automatic selection is based on context length; customer LLM keys and endpoints cannot be added.

    Model picker, model tables and own-LLM-key FAQ · documented · Source date not stated · Retrieved 2026-10-21

  12. Übersetzer | MeinGPT Docs meingpt:meingpt:translation

    Default text translation uses Google Cloud Translate and document translation uses DeepL through EU endpoints; glossaries and layout preservation are documented.

    Engine/hosting, formats and glossary management · documented · Source date not stated · Retrieved 2026-10-21

  13. Subdienstleister & Verarbeitungsregionen | MeinGPT meingpt:meingpt:subprocessors

    The register separates Germany platform storage, France backups and provider-specific EU inference regions.

    Register by function and processing region · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  14. Model access tiers dust:dust:tiers

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

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

  15. Spaces management dust:dust:spaces

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

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

  16. Credits dust:dust:credits

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

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

  17. Credit management dust:dust:credit-management

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

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

  18. Workspace-Konfiguration | MeinGPT Docs meingpt:meingpt:config

    Admins can restrict models by teams or people and supply workspace-wide instructions; denied API models return an error.

    Model access, default settings and additional chat context · documented · Source date not stated · Retrieved 2026-10-21

  19. Nutzungslimits | MeinGPT Docs meingpt:meingpt:limits

    Personal category budgets block new use at zero; running meeting bots can overrun limits and scheduled runs are outside personal categories.

    Usage levels, meeting limits and user consumption table · documented · Source date not stated · Retrieved 2026-10-21

  20. Einführung | MeinGPT Docs meingpt:meingpt:api

    Chat, embeddings, assistants, workflows and transcription APIs use bearer keys and published token rate limits; translation is UI-only.

    API overview, rate limits and errors · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  22. Computer dust:dust:computer

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

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

  23. Google Drive dust:dust:drive

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

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

  24. Search data sources dust:dust:search

    Agents search selected knowledge sources and retrieve relevant document context.

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

  25. Datenquellen & RAG | MeinGPT Docs meingpt:meingpt:pools

    Cloud pools index six source types in Germany, refresh every 15 minutes and share a 300 GB raw-data budget.

    Cloud-source table, connector comparison and normal-chat search · documented · Source date not stated · Retrieved 2026-10-21

  26. Eingabefeld | MeinGPT Docs meingpt:meingpt:chat

    Chat has stop, model choice, file upload, dictation and sharing links, with 50 files and 50 MB per non-image file.

    Input controls, file limits, dictation and sharing · documented · Source date not stated · Retrieved 2026-10-21

  27. Datenfluss bei MeinGPT Chats | MeinGPT Docs meingpt:meingpt:flow

    Chat deletion archives content; prompts have provider-dependent processing, and platform data stays until instructed deletion.

    Processing steps, providers and deletion rights · documented · Source date not stated · Retrieved 2026-10-21

  28. Code-Sandbox | MeinGPT Docs meingpt:meingpt:sandbox

    Python/JavaScript analysis and Office generation run in an isolated Unikraft Cloud VM in Frankfurt, including for on-premise customers.

    Execution flow, hosting, lifetime and limitations · documented · Source date not stated · Retrieved 2026-10-21

  29. Assistenten | MeinGPT Docs meingpt:meingpt:assistants

    Assistants combine model, instructions, files, pools, connectors, tools and memory.

    Creation guide and editor sections · documented · Source date not stated · Retrieved 2026-10-21

  30. Projekte | MeinGPT Docs meingpt:meingpt:projects

    Projects share instructions and workflows while each member keeps a private chat history.

    Collaboration, roles and deletion · documented · Source date not stated · Retrieved 2026-10-21

  31. Access Controls and Permissions dust:dust:permissions

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

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

  32. Microsoft dust:dust:microsoft

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

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

  33. Confluence dust:dust:confluence

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

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

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

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

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

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

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

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

  36. Adding an MCP Server dust:dust:tools

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

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

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

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

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

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

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

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

  39. Microsoft 365 | MeinGPT Docs meingpt:meingpt:m365

    Separate Outlook, Teams, SharePoint and OneDrive connectors run under user OAuth; Outlook can write, the other three read.

    Overview, setup, tenant consent and permission model · documented · Source date not stated · Retrieved 2026-10-21

  40. Sucheinstellungen am Datenpool | MeinGPT Docs meingpt:meingpt:pool-controls

    Source-permission import is off by default and request-enabled for SharePoint and Drive only; answers always show sources.

    Settings table and source-permission section · documented · Source date not stated · Retrieved 2026-10-21

  41. Dust Security dust:dust:security

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

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

  42. Deep-dive Agent dust:dust:deep

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

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

  43. Agent Memory dust:dust:memory

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

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

  44. Create your first agent dust:dust:builder

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

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

  45. Memory | MeinGPT Docs meingpt:meingpt:memory

    Memory persists per user across enabled assistants; users can inspect/delete it and admins can disable the tool.

    How memory works, management and admin controls · documented · Source date not stated · Retrieved 2026-10-21

  46. Präferenzen | MeinGPT Docs meingpt:meingpt:preferences

    Users can set persistent system instructions and a platform-language preference.

    Chat settings and appearance · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  48. Rollen & Zugriffsmodell | MeinGPT Docs meingpt:meingpt:roles

    Admin, Member and Viewer roles differ in settings access and seat use; admins see all team-shared assets.

    Role table, admin exception and support visibility · documented · Source date not stated · Retrieved 2026-10-21

  49. Berechtigungen | MeinGPT Docs meingpt:meingpt:permissions

    Support-enabled permissions control creation, sharing and app use per person or team.

    Availability, permissions table and app restrictions · documented · Source date not stated · Retrieved 2026-10-21

  50. Prompt-Bibliothek | MeinGPT Docs meingpt:meingpt:prompts

    Saved prompt folders have private, workspace or department visibility.

    Core functions, visibility and sharing · documented · Source date not stated · Retrieved 2026-10-21

  51. Web Search & Browse dust:dust:web

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

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

  52. Websuche | MeinGPT Docs meingpt:meingpt:web

    Linkup powers chat search and a multi-step Deep Research app with cited sources.

    Three routes, query creation, Linkup and research app · documented · Source date not stated · Retrieved 2026-10-21

  53. Triggers dust:dust:triggers

    Agents can run automatically from schedule or event triggers.

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

  54. Schedules dust:dust:schedules

    Agents can run on recurring schedules.

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

  55. Webhooks dust:dust:webhooks

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

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

  56. Workflows erstellen und ausführen | MeinGPT Docs meingpt:meingpt:workflows

    Project workflows support multiple models, variables, documents and downloadable Office, PDF or JSON output.

    Workflow editor and output format · documented · Source date not stated · Retrieved 2026-10-21

  57. Geplante Aufgaben | MeinGPT Docs meingpt:meingpt:scheduled

    Scheduled tasks are support-enabled beta with schedule, webhook and email triggers under the creator account.

    Beta availability, triggers and execution account · documented · Source date not stated · Retrieved 2026-10-21

  58. Pods overview dust:dust:pods

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

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

  59. Tool-Zugriffsrichtlinien | MeinGPT Docs meingpt:meingpt:tools

    Tool methods are intersected across admin and assistant policies; there is no interactive per-action permission dialog.

    Security warning and four enforcement layers · documented · Source date not stated · Retrieved 2026-10-21

  60. API keys dust:dust:api-keys

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

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

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

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

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

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

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

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

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

    The API retrieves accessible conversation messages with pagination.

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

  64. Compliance Controls | MeinGPT Docs meingpt:meingpt:audit

    Administrative settings logs exclude chat contents and are retained indefinitely; Governance Outpost search records are retained 90 days.

    Core controls and Outpost search log · documented · Source date not stated · Retrieved 2026-10-21

  65. Outlook Add-in | MeinGPT Docs meingpt:meingpt:outlook

    The Outlook add-in requires Enterprise API enablement and a personal API key and works in the received-mail reading view.

    Prerequisites, supported clients and central deployment · documented · Source date not stated · Retrieved 2026-10-21

  66. Browser Extension dust:dust:browser

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

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

  67. Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand meingpt:meingpt:terms

    German commercial terms distinguish SaaS from contract-agreed on-premise deployment and describe subscriptions, export and termination.

    Sections 1a, 2, 3, 5 and final provisions · documented · Source date not stated · Retrieved 2026-10-21

  68. Dust in Teams dust:dust:teams

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

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

  69. Image Generation dust:dust:images

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

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

  70. Bilder Generieren | MeinGPT Docs meingpt:meingpt:images

    The image app supports FLUX, GPT Image and Gemini image models with reference images and downloadable files.

    Model list, references and output management · documented · Source date not stated · Retrieved 2026-10-21

  71. Bildmodelle verwalten | MeinGPT Docs meingpt:meingpt:image-admin

    Admins enable image models and set a default; the table distinguishes manufacturer, host and EU/global processing.

    Image-model controls and complete table · documented · Source date not stated · Retrieved 2026-10-21

  72. Voice and sound generation dust:dust:speech

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

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

  73. Meeting transcripts dust:dust:meetings

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

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

  74. Meetings | MeinGPT Docs meingpt:meingpt:meeting

    Recordings and transcripts become searchable meeting notes; Hetzner, Gladia and Vertex EU form the processing path.

    Formats/limits, data flow and prices · documented · Source date not stated · Retrieved 2026-10-21

  75. Frames overview dust:dust:frames

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

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

  76. Pod conversations dust:dust:pod-chats

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

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

  77. Single Sign-On dust:dust:sso

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

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

  78. Dust for Enterprise dust:dust:enterprise

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

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

  79. prices meingpt:meingpt:prices

    The public calculator uses marginal seat tiers plus model consumption and optional Governance and Outpost fees.

    Annual price tiers, included functions, add-ons and model-cost sections · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  80. Access & Login Security | MeinGPT Docs meingpt:meingpt:sso

    OIDC, Google and Microsoft login, verified domains and additive Entra group synchronization are documented; SAML is explicitly excluded.

    Own identity provider, authentication methods and Entra synchronization · documented · Source date not stated · Retrieved 2026-10-21

  81. Users and groups provisioning dust:dust:provision

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

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

  82. Seat management dust:dust:seats

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

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

  83. Entra ID SCIM-Provisionierung | MeinGPT Docs meingpt:meingpt:scim

    SCIM v1 provisions users only; deactivated accounts retain data and release their seat.

    SCIM versus SSO, prerequisites, effects and seat assignment · documented · Source date not stated · Retrieved 2026-10-21

  84. Analytics dust:dust:analytics

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

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

  85. KI-Cockpit | MeinGPT Docs meingpt:meingpt:analytics

    Adoption and cost reports include user, model, API/platform and team breakdowns with CSV and ID-based anonymization.

    Typical metrics, user/team costs and knowledge search · documented · Source date not stated · Retrieved 2026-10-21

  86. Audit Logs dust:dust:audit

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

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

  87. Änderungsprotokoll exportieren | MeinGPT Docs meingpt:meingpt:audit-export

    Admins export filtered administrative changes as CSV or JSON, capped at 10000 entries, 20 MiB and two minutes.

    Export procedure, fields and limits · documented · Source date not stated · Retrieved 2026-10-21

  88. Dust Platform Privacy Policy dust:dust:privacy

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

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

  89. Auftragsverarbeitungsvertrag | MeinGPT | KI-Use-Case-Plattform für den Mittelstand meingpt:meingpt:dpa-page

    DPA 2.0.1 dated 24 September 2026 needs signature or recorded electronic acceptance; existing customers retain their agreed version.

    Version and effectiveness · documented · Source date 2026-09-24 · Retrieved 2026-10-21

  90. MeinGPT DPA 2.0.1 meingpt:meingpt:dpa

    The signed-form DPA prohibits training, lists conditional subprocessors, defines authority-request handling and requires return or deletion within 30 days.

    Version 2.0.1; sections 4, 5(5), 7, 9, 12, 13 and Annexes 3/4, pages 3-12 · documented · Source date 2026-09-24 · Retrieved 2026-10-21

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

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

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

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

    Users can delete or rename their conversations.

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

  93. Sind meine Daten sicher? | MeinGPT Docs meingpt:meingpt:security

    Security documentation states TLS 1.3, AES-256, customer-managed keys on request, and no bulk chat/file export.

    Technical security, deletion and data portability · documented · Source date not stated · Retrieved 2026-10-21

  94. Sicherheitsnachweise & Trust Center | MeinGPT meingpt:meingpt:trust

    ISO 27001 and a 2025 SySS penetration-test certificate are listed behind email-gated access.

    Certificates, assessments and document access · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  95. Preise für Plattform, Add-ons und KI-Nutzung | MeinGPT meingpt:meingpt:prices-rev2

    The contracted platform is offered with optional Governance and Outpost modules; local files are Early Access and local MCP/PostgreSQL Private Beta. The price calculator requires a binding individual offer.

    Feature table: Outpost release states; Governance separate agreement; calculator explicitly nonbinding · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  96. meinGPT terms: professional secrecy meingpt:meingpt:secrecy-contract-rev2

    Section12(4) itself imposes indefinite professional secrecy and text-form staff/subcontractor obligations when covered data are processed; it does not state a Governance prerequisite. A separate addendum is outside the verified base-terms finding.

    Section12(4), conditional duties for professional-secret data; no Governance prerequisite stated · documented · Source date not stated · Retrieved 2026-10-21

  97. Abrechnung verwalten | MeinGPT Docs meingpt:meingpt:billing-rev2

    Self-service Business is EUR29 per user/month excluding VAT, billed monthly, with unlimited standard-model use; premium/reasoning, API and meeting-bot use are separately metered.

    Workspace types; Business upgrade card; standard-model inclusion · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  99. ECB historical euro reference rates, 20 October 2026 meingpt:meingpt:ecb-fx

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

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

  100. Abrechnung verwalten | MeinGPT Docs meingpt:meingpt:billing

    A separate Business offer includes standard models; the trial lasts 10 days with EUR 5 credit and no payment details.

    Workspace types, trial differences and Business upgrade · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  102. Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand meingpt:meingpt:terms-20261026

    German commercial terms distinguish SaaS from contract-agreed on-premise deployment and describe subscriptions, export and termination.

    Sections 1a, 2, 3, 5 and final provisions · documented · Source date not stated · Retrieved 2026-10-26

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

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

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

  104. Dust Support dust:dust:support

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

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

  105. status meingpt:meingpt:status

    A public service-status page exposes incident history.

    Platform component and incidents · documented · Source date not stated · Retrieved 2026-10-21

  106. Dust Rollout Guide dust:dust:rollout

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

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

  107. Team onboarding material dust:dust:training

    Dust provides reusable team-onboarding material.

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

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

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

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

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

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

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

  110. Lernen & Entdecken | MeinGPT Docs meingpt:meingpt:academy

    The learning area includes guided learning paths and business use cases.

    Learning area content and personalization · documented · Source date not stated · Retrieved 2026-10-21