Home›Agents›Dust Agents

AgentenCode evidence profileEnterprise

✓ Editorially reviewedChecked: October 1, 2026

Agent profile · Enterprise

Dust Agents

Dust Agents is classified by AgentenCode as an enterprise agent platform from Dust. It belongs to the Enterprise & Productivity category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.

DustEnterpriseBusinesses & teams

View profile ↓Check sources ↓

Enterpriseeditorial classification

Dustprovider

5 primary sourcessource status

October 1, 2026last verification

AgentenTrust 2.0 · EU & governance evidence

Trust, privacy and control evidence for Dust Agents

Direct answer: AgentenCode currently documents 12 of 36 normalized trust controls for this profile. Missing fields remain Unknown and are never automatically interpreted as “no”.

EU AI ActEvidence context only. AgentenCode does not infer legal applicability or compliance from individual product controls.

GDPRPrivacy and security signals are documented field by field. Data residency alone is not a compliance or transfer assessment.

Privacy contextPrivacy & data3 of 8 documentedResidency, training, retention, DPA, subprocessors and processing scope.

Security contextSecurity & access7 of 10 documentedEncryption, SSO, SCIM, RBAC, roles and credential handling.

Human controlHuman control0 of 10 documentedApproval, oversight, permissions and stop or rollback controls.

TraceabilityAudit & traceability2 of 8 documentedAudit logs, APIs, SIEM, observability, tracing and activity history.

Important: these numbers show evidence coverage, not a product rating. 0 of 10 means that no field-level public evidence is stored for those ten controls in the current dataset. It does not mean the product lacks those capabilities.

Field-level evidence

Documented controls and values from primary sources.

Documented yesDocumented valueUnknown remains unknown

High confidence

API · Rest

Yes — documented

Dust documents a developer-facing RESTful API; the former api.public/api.type split is consolidated into api.rest.

Scope: business_and_enterprise · verified 2026-10-01 · Primary source ↗

High confidence

API · Webhooks

Yes — documented

Webhook-based integrations are supported.

Scope: business_and_enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Audit logs · Available

Yes — documented

Audit logs are documented.

Scope: enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Audit logs · Retention days

365

Audit-log retention is documented as 365 days.

Scope: enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Governance · RBAC

Yes — documented

RBAC is documented.

Scope: enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Governance · SCIM

Yes — documented

SCIM provisioning is documented.

Scope: enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Governance · SSO · Oidc

Yes — documented

OIDC SSO is documented.

Scope: enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Governance · SSO · Saml

Yes — documented

SAML SSO is documented.

Scope: enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Single Tenant

Yes — documented

A single-tenant deployment option is documented.

Scope: enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Available

Yes — documented

Regional data residency is documented.

Scope: business_and_enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Region

EU residency is available.

Scope: business_and_enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Region

US residency is available.

Scope: business_and_enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Training · Customer Data

No — explicitly documented

Customer data is documented as not used for model training.

Scope: enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · Mcp · Client

Yes — documented

Dust acts as an MCP client for agent tool access.

Scope: business_and_enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · Mcp · Remote

Yes — documented

Remote MCP servers are supported.

Scope: business_and_enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · Mcp · Server

Yes — documented

Dust documents MCP server capability in addition to client use.

Scope: platform · verified 2026-10-01 · Primary source ↗

High confidence

Security · Encryption · At rest

AES-256

Encryption at rest is documented as AES-256.

Scope: enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Security · Encryption · In transit

TLS 1.3

Encryption in transit is documented as TLS 1.3.

Scope: enterprise · verified 2026-10-01 · Primary source ↗

Evidence-backed overview

What is Dust Agents?

Product-specific evidence for Dust Agents

This profile links 5 unique primary sources across the product profile, field-level evidence, trust controls and documented relations. The points below describe this product’s stored evidence rather than generic characteristics of Enterprise & Produktivität.

Data Residency

Yes · Scope: business_and_enterprise · verified 2026-10-01.

Primary source ↗

Dokumentierte Region

EU · Scope: business_and_enterprise · verified 2026-10-01.

Primary source ↗

Dokumentierte Region

US · Scope: business_and_enterprise · verified 2026-10-01.

Primary source ↗

Kundendaten für Training

No · Scope: enterprise · verified 2026-10-01.

Primary source ↗

Verschlüsselung at rest

AES-256 · Scope: enterprise · verified 2026-10-01.

Primary source ↗

Verschlüsselung in transit

TLS 1.3 · Scope: enterprise · verified 2026-10-01.

Primary source ↗

AgentenCode treats this page as a reference profile rather than a ranking. Product facts are separated from editorial classification, and the profile is tied to a specific verification date. If a capability is not backed by sufficiently precise public evidence, it remains unknown instead of being inferred from marketing language or from similar products.

3primary sources

19field-level evidence claims

12documented trust controls

3history events

How to read the evidence

The field-level evidence layer records a value, a scope, a confidence level, a verification date and one or more primary sources. Scope matters: an enterprise-only security feature must not be generalized to every plan or deployment surface. The same rule applies to hosting, privacy, audit and protocol claims.

AgentenCode also keeps Unknown distinct from false. A missing claim means the public dataset does not currently contain sufficiently precise evidence for that field. A negative value is used only when a reliable primary source explicitly documents a restriction or non-availability.

Decision context

Provider and category

Dust Agents is documented under Enterprise and is associated with Dust. Category labels help navigation but do not replace product-specific evidence.

Verification status

The public profile is marked editorially reviewed and was last checked on October 1, 2026.

Trust coverage

12 of 36 normalized trust controls currently have field-level public evidence. The remaining controls are not treated as negative findings.

Source-first use

For procurement, security or legal decisions, use the linked primary sources and verify the plan, region and configuration that apply to your organization.

Capabilities, strengths and deployment checks for Dust Agents

Dust Agents is classified as Enterprise Agent Platform from Dust. The profile’s editorial layer is derived from the stored use cases, strengths and checks below; claims about security, privacy or governance remain separate and require field-level evidence.

Unternehmenswissen durchsuchen

This use case is part of the stored profile for Dust Agents. The related strength is “Spezialisierte Agenten für Teams”. In a production evaluation, the practical boundary to verify is: Datenquellen und Workspace-Rechte sauber segmentieren.

Marketing- und Content-Operationen

This use case is part of the stored profile for Dust Agents. The related strength is “Agent Builder mit Skills und Tools”. In a production evaluation, the practical boundary to verify is: Trigger und automatisierte Aktionen überwachen.

Daten- und Analyseaufgaben

This use case is part of the stored profile for Dust Agents. The related strength is “Trigger für automatisierte Ausführung”. In a production evaluation, the practical boundary to verify is: Agentenanweisungen und Skills versionieren und testen.

Automatisierte agentische Workflows

This use case is part of the stored profile for Dust Agents. The related strength is “Anbindung an Unternehmenswissen”. In a production evaluation, the practical boundary to verify is: Datenquellen und Workspace-Rechte sauber segmentieren.

What to verify before adoption

Datenquellen und Workspace-Rechte sauber segmentieren. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Trigger und automatisierte Aktionen überwachen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Agentenanweisungen und Skills versionieren und testen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.

Editorial boundary: The use-case and strength descriptions are product-specific editorial context based on the stored profile. Trust, privacy and governance statements are only presented as facts when field-level primary-source evidence exists.

Verified history

The public history layer records only confirmed profile changes and verification events. Monitoring signals are not published as product facts until they have been reviewed.

October 1, 2026 · Source Maintenance
September 30, 2026 · Verification Update
September 28, 2026 · Initial

Official sources

This profile links 5 unique primary sources across the product profile, field-level evidence, trust layer and documented relations. Provider documentation remains authoritative when the product changes between verification cycles.

Frequently asked questions

What is Dust Agents?

Dust Agents is listed by AgentenCode as an enterprise agent or agentic product from Dust.

How much trust evidence is documented for Dust Agents?

The current trust layer documents 12 of 36 normalized controls. Missing controls remain unknown rather than being treated as false.

When was this profile last checked?

The current profile verification date is October 1, 2026. The linked primary sources remain authoritative if the product changes between checks.

Method note: AgentenCode does not certify GDPR or EU AI Act compliance. It documents evidence that can support a separate legal, security or procurement assessment.