# Dust — Platform for building and running company agents on connected tools, data and 20+ models.

> Source: The Agents Index — https://theagentsindex.com/dust (structured, researched, re-verified)
> Facts last verified: 2026-10-01

Dust is a hosted platform where teams build custom AI agents on connected company systems such as Slack, Notion, GitHub and Salesforce. Agents run on 20+ frontier and open-weight models, on schedules and triggers, inside shared workspaces with admin governance.

| Fact | Value |
| --- | --- |
| Website | https://dust.tt |
| Price | from €30/seat per month billed monthly, €24/seat per month billed annually |
| Free tier | Yes |

Free seat costs 0€ with a one-time lifetime allocation of 500 credits that does not reset; Free seats cannot draw from the workspace credit pool and are blocked once exhausted, then prompted to request an upgrade.

## What it does

**Writes code** · Partly — Agents author React components (Frames) and run code in a sandbox to produce files, but Dust documents no repository-level code authoring or commits.

> A Frame is an interactive file (a React component generated by an agent) that can be stored in the Pod's Files tab.
> — https://docs.dust.tt/docs/user-documentation/pods/frames · Frames page, opening definition

**Debugs and fixes** · Partly — The engineering page claims debugging support by surfacing code context, docs and recent issues in the IDE, which stops short of diagnosing and landing a fix itself.

> Streamline debugging within your IDE by surfacing relevant code context, documentation, and recent issues.
> — https://dust.tt/home/solutions/engineering · "Your use cases, your way" section, Code debugging card

**Reviews code** · Yes — GitHub tools let agents review pull requests against internal coding rules, and the engineering page presents automated code review as a supported use case.

> GitHub tools let your agents work with GitHub issues and pull requests. Use them to build agents that file issues when needed, or that review PRs based on internal coding rules.
> — https://docs.dust.tt/docs/user-documentation/agents/tools/github.md · GitHub tool page, Overview section

**Whole-codebase work** · Partly — It can ingest a repository's default-branch code for search, refreshed every eight hours, but no documented ability to carry a change across that repository.

> Code Synchronization: Repository code from the default branch
> — https://docs.dust.tt/docs/user-documentation/admins/connections-management/github · Data Synchronization list, Code Synchronization bullet

**Done-for-you service** · No — Dust sells software a buyer configures, self-serve for Business or sales-assisted for Enterprise; Enterprise adds a dedicated CSM and onboarding, not a team that builds agents for you.

> Choose self-serve plan for your team, or talk to us about enterprise-ready deployment, governance, and support
> — https://dust.tt/home/pricing · Pricing hero subtitle under "Pricing that scales with the work you get done"

_Not established: Writes tests, Ships it_

## How much it does unattended

**Runs autonomously** · Partly — Agents run unattended on schedules and event triggers, but a root task started from the web app or extension pauses for human confirmation once it reaches 600 credits of AI spend.

> Dust pauses a root task started from the web app or browser extension when its cumulative AI spend reaches 600 AWU credits.
> — https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/credits.md · Credits page, "Credit-spend checkpoints" section

**Multi-agent** · Yes — Multi-agent orchestration with scheduled and event-driven triggers is listed for both Business and Enterprise, and sub-agent credit costs accumulate across an agent chain.

> Multi-agent orchestration & triggers (scheduled + event-driven)
> — https://dust.tt/home/pricing · Compare plans table, Features group, "Multi-agent orchestration & triggers" row

**Agent permissions** · Partly — Admins separate what agents may access from who may use them, can restrict tools to skills, and the credit checkpoint asks a human before a long task continues; granular per-action approval policy is not published.

> Dust's dual-layer permission model separates what agents can access from who can use them. SCIM-synced groups, admin-gated overrides, zero privilege escalation, and audit logs let teams move quickly while keeping company data locked down.
> — https://dust.tt/ · Homepage, "Use AI on your terms, without giving up control of your data" section

## Which models it runs on

**Claude** · Yes — Claude is named in the plan feature list of frontier models, and the admin model tier tables list several Claude models across Basic through Ultra tiers.

> 20+ frontier models — GPT, Claude, Gemini, Mistral, DeepSeek
> — https://dust.tt/home/pricing · Business plan card, first feature bullet

**GPT** · Yes — GPT is named in the Business plan model bullet, and the model access tier tables list GPT variants in every tier including Ultra.

> 20+ frontier models — GPT, Claude, Gemini, Mistral, DeepSeek
> — https://dust.tt/home/pricing · Business plan card, first feature bullet

**Open models** · Yes — The homepage states agents can be built with open-source models, and the model tier tables list Mistral, DeepSeek, GLM and Kimi options served through Fireworks.

> Build agents with 20+ frontier and open-source models from OpenAI, Anthropic, Google, Mistral, and more.
> — https://dust.tt/ · Homepage, feature 03 "Model flexibility"

**Model choice** · Yes — The buyer picks the model per agent and nothing is gated behind a higher plan, though admins may cap which model tiers members can select and costlier models burn more credits.

> All plans include access to 20+ models from OpenAI, Anthropic, Google, Mistral, and DeepSeek. You choose the model per agent. No model is locked behind a higher plan, though higher-capability models may consume more credits per message.
> — https://dust.tt/home/pricing · FAQ, "Which AI models are included?"

## Where you use it

**In your editor** · Partly — There is no native IDE plugin documented; instead Dust exposes the workspace as a remote MCP server that IDEs and assistants can call, plus a browser and Raycast extension.

> This lets tools such as IDEs and AI assistants call Dust to search workspace knowledge, work with conversations, and access files or Pods through the Model Context Protocol.
> — https://docs.dust.tt/docs/user-documentation/agents/integrations/dust-mcp-server.md · Dust MCP Server page, opening paragraph

**On the command line** · Yes — A published npm CLI opens an interactive terminal chat with filesystem access, and takes single non-interactive messages that return JSON on stdout.

> When no command is provided, the chat command runs by default, opening an interactive chat with @Dust with access to your local filesystem.
> — https://docs.dust.tt/docs/developer-platform/dust-cli/dust-cli · Usage section

**In your pipeline** · Partly — Agents can be triggered by webhooks carrying GitHub, Jira or Slack events and can act on pull requests, but no first-party CI runner or pipeline step is documented.

> Build webhook endpoints to trigger agents from any external system. Receive events from GitHub, Jira, Slack, or your own services with full company context.
> — https://dust.tt/home/solutions/dust-platform · Developer platform page, "Custom Webhooks" section

**In a browser** · Yes — Dust is a hosted web application with collaborative workspaces, conversations and Frames dashboards, and the pricing page sells it as self-serve from the browser.

> Team collaboration workspaces
> — https://dust.tt/home/pricing · Business plan card, feature bullet list

## Whose machine it runs on

**Self-hosted** · Partly — The isolation option Dust sells is a dedicated single-tenant deployment it runs on Enterprise; the MIT-licensed source exists but no self-hosting guide is published.

> Single-tenant deployment
> — https://dust.tt/home/pricing · Compare plans table, Security & admin section, Single-tenant deployment row (Enterprise only; Business shows a dash)

**Open source** · Yes — The product's own source repository is public under the MIT licence and is linked from the Developers column of every page footer.

> MIT License
> — https://github.com/dust-tt/dust · Repository page, licence field beside the repo description

## What it costs to run

**How it meters** · Yes — Billing is per seat with a monthly credit allowance per seat type, and non-human usage is metered separately at a published per-credit rate on Business.

> Programmatic usage rate
> — https://dust.tt/home/pricing · Compare plans table, Developer tools group, "Programmatic usage rate" row ($0.01 / credit on Business)

**Free tier** · Yes — A Free seat type costs nothing and carries a one-time 500-credit lifetime allocation, so a buyer can start without a sales call but cannot run indefinitely.

> Free seat | 500 credits (one-time lifetime allocation)
> — https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/credits.md · Credits page, "Credit allocations by seat type" table

**API access** · Partly — Business plans get the Conversation API only; the Data Source API is added on Enterprise, and both sit on top of a documented REST platform with a JavaScript SDK.

> Conversation API
> — https://dust.tt/home/pricing · Compare plans table, Developer tools group, "Developer API" row, Business column (Enterprise reads "+ Data Source API")

**MCP server** · Yes — Dust publishes a remote MCP server per region so another agent can query workspace knowledge, conversations and files over OAuth, with admins able to disable it.

> Dust can expose your workspace as a remote MCP Server, so compatible MCP clients can use Dust where you already work.
> — https://docs.dust.tt/docs/user-documentation/agents/integrations/dust-mcp-server.md · Dust MCP Server page, opening paragraph

_Not established: Bring your own key_

## Buying it for a team

**A company can buy it** · Yes — The self-serve Business plan is sold to teams of up to 100 people with workspace seat administration, and Enterprise is purchased through sales with custom MSA and DPA terms.

> For teams up to 100 people
> — https://dust.tt/home/pricing · Business plan card subtitle

**Seat model** · Yes — Three seat types are priced per seat per month and can be mixed and reassigned within one workspace; no seat minimum is published, though SSO on Business is noted at 5+ seats.

> You can mix and match seat types across your workspace and reassign them anytime as usage changes.
> — https://dust.tt/home/pricing · FAQ, "What's the difference between Free, Pro, and Max seats?"

**Pooled budget** · Partly — Each paid seat has its own monthly credits first; a shared workspace pool exists but needs admin-purchased top-ups on Business and is contract-funded on Enterprise, and Free seats cannot touch it.

> The workspace credit pool is a shared credit reserve that Pro and Max seat members can draw from once their individual credits are exhausted.
> — https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/credit-management.md · Credit management page, "Workspace credit pool" section

**Admin controls** · Yes — Admins cap which models and reasoning efforts members may select at workspace, group or member level, set personal and programmatic spend limits, and restrict tools to named skills.

> As an administrator, you can cap how far up the model list each member can go.
> — https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/model-access-tiers.md · Model access tiers page, introduction

**Audit log** · Partly — A tamper-evident log distinguishing human from agent actions exists with CSV export and SIEM streaming, but the docs restrict it to the Enterprise plan.

> **Enterprise feature.** Audit Logs are only available to workspaces on the Enterprise plan.
> — https://docs.dust.tt/docs/user-documentation/admins/audit-logs/audit-logs.md · Audit Logs page, Info callout at top

**Single sign-on** · Partly — SAML single sign-on with Okta, Entra ID and Jumpcloud is supported and can be enforced workspace-wide, but on Business it is noted as 5+ seats on demand and OIDC is not mentioned.

> SSO (Okta, Entra ID, Jumpcloud)
> — https://dust.tt/home/pricing · Compare plans table, Security & admin group, SSO row (Business column reads "5+ seats on demand")

## What happens to your code

**Opt out of training** · Yes — The security page states customer data is never used for model training and that third-party providers retain nothing, so there is no opt-out to find because training is excluded by default.

> No Model Training Your data is never used to train models.
> — https://dust.tt/home/security · "Select trusted models, keep data protected" section, first bullet

**Data residency** · Yes — Data can be hosted in either the United States or the European Union, and the comparison table shows US/EU residency on both Business and Enterprise with single-tenant reserved for Enterprise.

> Regional Hosting Host in the EU or US to meet your regulatory needs.
> — https://dust.tt/home/security · "Ingest data on your terms" section, third bullet

**Getting out** · Partly — Analytics, audit logs and agent configurations can be exported via API or CSV, but credits are explicitly non-transferable, non-rolling and non-refundable, so unused balance is lost each period.

> Credits are not transferable between users, do not roll over to the next billing period, and are not refundable.
> — https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/credits.md · Credits page, "What is a credit?" section

**Certifications** · Yes — Dust states GDPR compliance and SOC 2 Type II certification, says it enables HIPAA compliance, and publishes a Trust Center; ISO 27001 is not claimed on the page read.

> GDPR Compliant & SOC2 Type II Certified. Enables HIPAA compliance.
> — https://dust.tt/home/security · Security page hero, bold line under "Enterprise-grade Security"

## Provenance

Every fact above comes from the vendor. Nothing here is independently corroborated yet.

## Coverage elsewhere

None recorded. Every fact above comes from the vendor and is not independently corroborated yet.

## What changed

- 2026-10-01 — Capabilities · Commercial terms · Free tier · Price
- 2026-09-09 — Capabilities · Commercial terms · Free tier · Price

## Correcting this record

Anything marked "Not established" is a question we have not answered — it is not a No. If you represent Dust, or anything here is wrong or out of date, you can supply it with a source: the operations this site accepts from an agent are listed at https://theagentsindex.com/.well-known/agents.json — that catalogue needs no key to read, and each entry states its own auth.

Supplying evidence is free. Nothing that can be bought here changes what a field says, whether a gap is closed, or how this record is scored.