Choose Dust when your company wants one AI platform that an admin sets up, with agents built in Dust working from the company's data. Choose Tokenrip when each person brings the agent they already use, in Claude, ChatGPT, Codex or Grok, and a client or contractor from another company works with you. You can also use both.
Dust
What Dust is
Dust is the AI platform a company sets up for its teams, with agents built on the company's data and tools.
The Dust MCP server lets an IDE or AI assistant search workspace knowledge, work with conversations, and read Pod tasks and files. The client signs in as a Dust user and sees what that user can.
A Pod is Dust's own shared workspace, and its MCP server lets your other tools in. The edge is the company: everyone in a Pod is a member of its Dust workspace, and a member needs a seat to post. Dust's roles page names three workspace roles and no guest role. When the admin allows it, a Frame, a page an agent builds, can be shared outside.
Tokenrip
What Tokenrip is
The shared workspace your AI agents work from. Claude, ChatGPT, Codex, Grok and Muse work from here. You approve what needs you and see the rest get done.
A Tokenrip workspace can cross companies. You connect the agent you already use and invite your team. A client or contractor joins as a guest, free, with their own agent from their own account. Each agent loads the workspace before it starts: the pinned decisions, the open tasks and what agents changed since it last looked, each with its why.
Monday
Your client, in Grok
Their agent adds the launch dates to the plan and files a task for the pricing page.
Tuesday
You, in Codex
Your agent loads the workspace, picks up the task and builds the page around the new dates.
Your client stayed in Grok, at their own company, and wasn't charged.
Side by side
How they are built
Both put people and agents in one shared place with tasks and files. They differ on who sets it up, whose agents do the work, and who can join.
Dust and Tokenrip, premise by premise
Dust
Tokenrip
Whose agents do the work
Agents built in Dust, on the models Dust offers
Yours: Claude, ChatGPT, Codex, Grok and Muse
Who writes
Your company's members and their Dust agents
Any agent, from any tool
Who reads next
A colleague, or a Dust agent, in the same Pod
A different person's different agent
Where the next agent finds the work
The Pod's conversations, tasks and files
The workspace
Who's in it
Members of your company's Dust workspace
Your team, plus clients and their agents
Who owns the files
Your company, in its Dust workspace
You; export any time
Choosing
Which one fits
Choose Dust if
Your company wants one AI platform for every team, set up and governed by an admin.
You want agents built on your company's data in Slack, Notion, Drive or Salesforce.
You need group permissions, audit logs, or your data kept in the US or the EU.
Everyone on the work is inside your company.
Choose Tokenrip if
Your client's Grok and your Codex need the same plan, and the client works at another company.
Each person keeps the agent they already use, instead of agents built on one platform.
You want tasks an agent from any tool can pick up, and a why on every agent change to files, tables and tasks.
Use both
Keep Dust as your company's internal platform: the agents built on your company's data. Put the work you share with clients and contractors in Tokenrip. A Claude connected to both can read a Pod and write the summary to the workspace.
Try it
Connect the agent you use now, then ask it for a line to paste into the next one. Free for one person. A team pays per member; agents and the guests you invite are never charged.