"Multiplayer AI for human-agent collaboration."
Dust is an enterprise platform for AI agents, internal knowledge search, and teamwork. Teams connect data sources, tools, conversations, and company knowledge with agents that can research, analyze, write, and execute workflows.
Dust
Multiplayer AI for human-agent collaboration.
Limited workspace for initial agents, conversations, and tests Subscription Pro Pro usage for individuals and team members with a higher agent and credit quota.
Max Higher usage capacities for intensive agent and tool usage. Other Enterprise Custom offering with governance, connectors, security features, SSO, SCIM, and enterprise support.
Programmatic Usage Separately billed API and workflow usage for automated agent calls.
Connectors Connection of data sources such as Slack, Notion, Google Drive, GitHub, Salesforce, Microsoft 365, and other systems.
Target audience
Dust is aimed at knowledge workers, product teams, sales and support teams, research teams, consultancies, and large organizations that want to make company knowledge accessible more securely and productively.
Outstanding features
Dust connects AI agents with company data, structured tables, knowledge sources, tools, and communication channels. Among other things, agents can perform SQL-like table queries, document search, web research, email, CRM, and project management actions.
Main application areas
Typical use cases include internal knowledge search, research, sales enablement, support triage, recruiting, product management, data analysis, content production, competitor monitoring, and process automation.
Usage & notes
Dust should be introduced with clear spaces, roles, data sources, tool permissions, and agent policies. Data access, prompt contents, logs, and external tool scopes must be carefully restricted, especially when dealing with CRM, HR, financial, and customer data.
| Target audience | Assessment |
|---|---|
| Private individuals | Rather no – Dust is clearly aimed at teams and companies. |
| Self-employed / freelancers | Conditionally – useful with many knowledge sources, client projects, or recurring automations. |
| SMEs | Very well suited – for internal search, team knowledge, marketing, sales, HR, and support. |
| Large enterprises | Very well suited – strong role, permission, connector, and governance features. |
| Developers / IT teams | Yes – API, MCP, agents, tools, integrations, and programmatic use are available. |
| Knowledge management / internal search | Very well suited – Dust’s core use case. |
| Privacy-sensitive organizations | Well suited with EU region and Enterprise contract – no training use of company data is promised. |
Hosting & Data
1) On-prem / local hosting
Meaning: The company operates the solution on its own hardware or within its own infrastructure. In the strictest sense, not only the application runs locally, but ideally the model as well.
2) Private cloud / data center
Meaning: The solution runs in a dedicated or more clearly separated cloud environment, often with a hosting provider or hyperscaler, but in a German data center or in a particularly controlled environment.
3) EU SaaS / managed
Meaning: The provider operates the solution itself as a service. The company uses the tool as a ready-made cloud service, ideally with EU data residency.
4) Hybrid
Meaning: One part of the processing remains internal / local / in a private cloud, while another part runs in an external cloud or EU SaaS.
5) AVV / DPA
Meaning: This is the data processing agreement or Data Processing Addendum. It governs that the provider processes personal data on behalf of the customer and is bound by the customer's instructions.
6) No training
Meaning: The provider does not use your prompts, uploads, attachments, chat histories, or outputs for training or improving the general model — ideally excluded by contract.
7) Open-source / transparency path
Meaning: There is a path toward greater technical transparency and sovereignty, for example through:
- open models
- documented components
- self-hostable parts
- traceable architecture
- export / switching options
| On-prem / local hosting | ❓ |
| Private cloud / data center | ⚠️ |
| EU SaaS / Managed | ⚠️ |
| Hybrid | ❓ |
| DPA / AVV | ⚠️ |
| No training on customer data | ✅ |
| Open source / transparency path | ❓ |
On-Prem / local hosting: indirect / not available
An on-prem/local self-hosting option is not specified on the website. Instead, the website contained references to hosted variants and even the note that there is 'No self-hosted option'.
Private Cloud / data center: partial
There is an EU data hosting option for enterprise customers and EU routes under 'eu.dust.tt'. This suggests a separate regional hosting variant, but a dedicated private cloud architecture or customer-specifically isolated environment is not clearly described on the reviewed pages.
EU SaaS / managed: partial
Dust operates the solution as SaaS and mentions an EU hosting option on European servers. According to the website, however, this is exclusive to enterprise customers; for standard SaaS, EU data residency is not generally documented as the default.
Hybrid: indirect / not available
The website describes integrations, spaces, data sources, and external model providers, but no clearly defined hybrid operating model in which substantial processing remains internal/local at the customer and only partial processing takes place externally.
DPA / data processing agreement: partial
The platform privacy policy mentions the role as a processor for customer data and describes that Dust enters into data processing agreements with its own service providers. However, a directly accessible, standalone DPA/data processing agreement for customers was not clearly specified on the reviewed pages.
No training: covered
The website states multiple times that customer data is not used for model training. The platform privacy policy states that model providers may not use customer data for training and apply 'Zero Data Retention'; blog/security pages also confirm 'no data fed into training' and that prompts, documents, and outputs are not used for training.
Open source / transparency path: indirect / not available
A genuine open-source, self-hostable, or technically open sovereignty path is not specified on the website. There are APIs, export/integration options, and documented connections, but no clearly identified open-source components or self-hostable product parts.
Data processing
According to the website, Dust is primarily a managed cloud service. Customer data is processed in workspaces, can be synchronized from numerous data sources, and is passed on for model calls to selected foundation model providers. For enterprise, there is an EU hosting option for databases, files, and vectors; according to the changelog, model access still takes place via provider APIs. The website emphasizes that customer data is not used to train general models and that EU routing or EU hosting is available where offered.
Conclusion
For users across the EU/EEA, based on its own website Dust generally appears to be aligned with GDPR suitability, but not universally straightforward for every usage scenario. The best documented option is the enterprise variant with EU hosting. Without this option, important points such as the standard server location, the specific provision of a DPA/data processing agreement, and transparent subprocessor documentation remain too incomplete. Therefore, overall 'conditional'.
Sources
- https://dust.tt/home/platform-privacy
- https://dust.tt/home/security
- https://docs.dust.tt/changelog/eu-data-hosting-option-available
- https://docs.dust.tt/docs/snowflake-connection
- https://dust.tt/blog/what-is-data-sovereignty
- https://dust.tt/blog/secure-enterprise-platform-ai-agents
- https://dust.tt/blog/ai-solutions-built-in-privacy-governance
- https://dust.tt/blog/top-ai-platforms-model-agnostic-architecture
Strengths & weaknesses at a glance
| Strengths | Weaknesses |
|---|---|
| • Very strong internal knowledge search and enterprise agents | • No publicly documented on-premises path |
| • Many productive data sources and business integrations | • Strongly SaaS-oriented |
| • EU hosting and no model training on customer data according to the provider | • Data access and permissions must be carefully modeled for each connected source |
| • Audit logs, roles, SSO, and governance for teams | • Enterprise DPAs and individual contracts are primarily relevant for larger customers |
| • Good integration of chat, agents, and automation |
Reviews
0 reviews in total
There are no confirmed reviews for this tool yet.
Submit review
Your review will only become visible after email confirmation. This protects the portal against abuse.
Report review
Please select the reason why this review should be checked.
GDPR-compliant usage possible?
Dust documents several building blocks on its own website that are relevant for the GDPR in the EU/EEA area: a platform privacy policy based in France, references to GDPR compliance, an EU hosting option for enterprise customers, EU routes under 'eu.dust.tt', DPA/contract references via the documentation, as well as statements that customer data is not used for model training. However, the documentation is not strong enough for fully straightforward GDPR use throughout the entire EU/EEA, because EU data residency is only mentioned as an option for Enterprise, the standard SaaS variant is not clearly described as EU-resident, and a clearly linked AVV/DPA text or a standalone subprocessors overview on the website could not be found unambiguously. Therefore, GDPR-compliant use is plausible under conditions, especially via the Enterprise/EU hosting option.
Positive
Positive aspects include the provider's EU connection with an address in Paris, the explicit references to 'GDPR Compliant', the available EU hosting option, documented EU routes under 'eu.dust.tt', statements about 'no model training' and 'Zero Data Retention' with model providers, as well as the mention of SOC 2 Type II.
Negative
Negative or limiting is that the website does not provide a clearly complete, easily findable DPA/AVV page and no clearly named subprocessors list with locations. In addition, according to the website, EU data residency is only explicitly available for Enterprise; for standard SaaS use, the server location is not documented consistently and unambiguously. An on-prem/self-hosting option is not stated on the website.
Server location
The website mentions an EU hosting option. On the changelog page, it states that since February 7, 2025, there has been a data hosting option on European servers, exclusively for enterprise customers, for databases, files, and vectors. In the Snowflake documentation, EU routes with 'https://eu.dust.tt' are also mentioned. A specific country/data center is not consistently stated on the reviewed pages; in a blog post, servers in the EU or Frankfurt are mentioned as examples, but no generally binding standard server location for all plans is specified.
