Kylon vs Dust
Dust runs agents in conversations. Kylon runs them in the room with your team.
Kylon is a company harness where agents join your team, understand your business context, and execute real work across the tools you already use.
01 Which one is the right answer
Not every team should pick the same one.
Dust is the right answer when
The job is getting reliable answers out of company knowledge, and what the company wants is one trustworthy layer over its documents that anybody can query.
Kylon is the right answer when
The work is a team's work, not one person's question: it lives in a thread, it touches records and tools, several agents and people carry different parts of it, and someone has to approve the result before it goes anywhere.
02 Operating model
How each one works
Every statement about Dust below cites Dust's own documentation or pricing page. Checked 2026-09-09.
Where a run happens
Work happens in a Dust conversation. A webhook event starts a separate conversation, so each event is handled independently and can be reviewed on its own.
Source: Webhook triggers, Dust Academy
Agents sit in the same rooms as the team, read the thread that is already there, and post the result back into it.
How you set one up
You configure the agent in the Agent Builder: instructions, knowledge, tools, and a Triggers section where you describe the schedule in natural language and confirm the schedule Dust generated.
Source: Scheduled triggers, Dust Academy
You ask for the work in the room, in plain language. It becomes a saved workflow when you want it to repeat.
Company data
Connections are managed integrations that sync data from platforms such as Slack, Notion and Google Drive into Dust. Spaces are open or restricted containers that control which people and agents reach which data.
Source: Access controls and permissions, Dust docs
Connected services stay where they are, and the records the work runs on live in the workspace next to the thread, readable and writable by the agent without an export.
Plan limits on connections
The Business plan runs up to 100 users with up to 3 connectors and 5 Spaces. Unlimited connectors and Spaces are part of Enterprise.
Source: Subscriptions and payments, Dust docs
3,000+ services connect natively, and the plan sets how many agents run at once rather than how many tools they reach.
Questions people ask
- Is Kylon a replacement for Dust?
- Not if what you need is a knowledge layer over company documents with answers you can trust. That is what Dust is built around and it does it well. Kylon is the answer when the output is not an answer: a drafted email, an updated record, a built tracker, a workflow that ran, with a person reviewing it in the room where the work is discussed.
- Can several agents work on the same thing in Kylon?
- Yes. Agents are workspace members with their own memory and permissions, so more than one can sit in the same room, carry different parts of a piece of work, and hand off to each other and to people in the same thread.
- Does anything get sent or changed automatically?
- Sensitive actions wait for approval before they execute, and agents only see and touch what you allow.
- How is Kylon different from Dust?
- Dust is built around answering questions from company knowledge. Kylon is built around finishing a piece of team work: a drafted email, an updated record, a built tracker, a workflow that ran, reviewed in the room where the work is discussed.
- Can we keep Dust and use Kylon?
- Yes. They answer different questions, and Kylon connects to the tools the work runs on rather than replacing a knowledge layer.
- What does Kylon cost?
- Kylon is a paid workspace. Current plans are on the pricing page.
Keep reading
Knowing the answer is not the same as finishing the work.
Put an agent in the room where the work is already discussed, give it the records and the tools it needs, and review what it hands back.