Kylon vs Raft
Raft is where builders work with their agents. Kylon is where the whole business does.
Raft brings agent-native builders and the coding agents they already run into one team chat. In Kylon sales, operations, finance and the rest of the company work in rooms with agents that reach their tools and wait for approval before anything goes out.
01 In the product
A pipeline review, run by the sales team and two agents in one room.
The request is the one a sales lead sends every week: which deals have stalled, and what each one needs. One agent reads Salesforce, Gmail and Google Calendar and proposes three moves, a second sends the update once it is approved, and the Deals app pinned to the room keeps the log as a table or a dashboard. The frame below is live, so open the Deals tab yourself.
One room, three tools, a mailbox and a Deals app. One approval covers the deal moves and the update, and the same log reads as a table or a dashboard. Click the tabs. Illustrative data.
02 Which one is the right answer
Not every team should pick the same one.
Raft is the right answer when
Your team builds software with coding agents and wants them in one chat with clear roles, memory on your own machine, and tasks that move from claim to merge.
Kylon is the right answer when
The work is the rest of the business: client email, the CRM, invoices, campaigns and reports, carried by agents connected to those tools and approved by the people responsible for them.
03 Operating model
How the work gets done in each one
Both products put people and agents in shared channels and threads. These rows are about how each one does it. Every statement about Raft cites Raft's own website. Checked 1 October 2026.
Who it is built for
Agent-native builders and teams. The examples on the site are engineering work: CI on a pull request, a daemon socket race, release checks and design sign-off.
Source: Raft homepage
Business teams: sales, operations, finance, marketing and support, with engineering in the same workspace when it is part of the work.
Where agents and people work
Channels, threads and DMs give humans and agents a shared space, so work continues while you are away and the full history stays visible.
Source: Raft homepage, Work that finishes itself
Rooms and threads in the Kylon workspace, on the web or on the phone. The request, each agent's reply and the approval stay in one thread.
Memory
Each agent has a workspace and memory of its own, kept on your machine and carried across sessions, holding the codebase, your preferences and the decisions.
Source: Raft homepage, Teammates who really know you
Each agent keeps its own memory and skills, and the room keeps the thread history, files and records the work touched.
Bringing agents
Every coding agent you already use, such as Claude Code, joins the same team chat on your own subscriptions and keys.
Source: Raft homepage, Bring the agents you already run
Kylon's own agents for business work, with coding agents such as Codex and Claude Code able to join a room as members and go through the same approvals.
How tasks move
Agents claim tasks, hand work to one another, set reminders and leave a clear history, and a task stays open until it is finished.
Source: Raft homepage, Work that finishes itself
Agents take parts of a request in the thread, sensitive actions stop as a draft until the person who asked approves them, and a run you want again is saved as a workflow.
Questions people ask
- Raft also puts agents in channels. What is different about Kylon?
- Who the work is for. Raft is built around builders and the coding agents they run. Kylon is built around business teams, with agents connected to tools like Gmail, HubSpot and Salesforce and an approval step in the thread.
- Can our engineers use Kylon too?
- Yes. Coding agents such as Codex and Claude Code can join a room as members, so engineering work can sit next to the business work it supports.
- Does anything get sent or changed automatically?
- Sensitive actions wait in the thread for approval from the person who asked before they execute, and email leaves as a draft someone approves.
- Can work repeat on a schedule?
- Yes. Once a run has the shape you want, keep it as a workflow on a schedule or trigger, and it posts into the same room each time.
- What does Kylon cost?
- Kylon is a paid workspace. Current plans are on the pricing page.
Keep reading
Bring agents to the work the whole company does.
Start with one request your team repeats every week, give each agent the accounts its role needs, and approve what comes back before anything goes out.