The AI operating system for business processes Build. Run. Observe. Govern.
Turn how your business works into production-grade processes with durable execution.
Want help with your first process? Talk to us →
Your process, your way
Use Dex AI Platform to turn how your business works into highly customized agentic processes.
- 01
Describe it Tell Dex AI Platform how your business works.
- 02
AI builds it Dex AI Platform turns it into a working process.
- 03
It runs reliably It keeps running from start to finish.
See how Dex compares to traditional automation
| Automation tools: configured | Dex AI Platform: written in code | |
|---|---|---|
| What you get | A workflow assembled from the tool's building blocks | A Dex process: real code in a private repository |
| Who builds it | You, in a visual editor | A coding agent, from your natural language; you check the result in a live preview |
| When the work needs something the tool can't do | Workarounds: a sheet as memory, flags, extra automations | The agent changes the code to fit the work. |
| How you review it | The canvas | A process flow drawn from the code, and custom UI interface along with it |
See Dex AI Platform in action
This is the process we use to publish our own tech blog and newsletter. Someone asks for a post in Slack, and the process researches what we shipped on GitHub, writes a draft and posts it back to the Slack thread. Reviewers reply with feedback for a new draft or polish it in an editor, and once they approve, the newsletter goes out to every subscriber by email.
Most business work runs in the background
It isn't just an application; it's a process. Coding agents make building applications easy. Dex makes the processes behind it run reliably.
A process waits days, weeks or months for a person or a reply, then picks up exactly where it was.
People have roles: a case pauses for one, that person answers from their queue, and the case resumes.
Work queue in Dex Web today · sign-in and acting in Studio (planned)
Steps retry, and if unsure something went through, they check first or hand the case to a person.
AI only works in steps marked for it; fixed rules or a person act on what it suggests.
Connectors for the systems you already use report every outcome, so nothing fails silently.
Each can fail, answer late or answer twice
Checking, de-duplicating, following up and stopping when asked are process steps, so they happen every time.
You can see every case and the path it took, in Dex Web
Every team has the power to turn their work into durable processes
- HR
New-employee onboarding
From signed offer to a ready first day: equipment, accounts, documents, and reminders to the new hire.
- HR / Recruiting
Interview loop
Schedules interviews, chases feedback, escalates when it's late, and cancels everything if the candidate withdraws.
- Legal
Contract review
Routes each contract for review and approval by value, sends it for signature, and keeps the signed version with its approvals.
- Customer service
Refund with a manager's approval
Checks the order, sends exceptions to a manager, and issues the refund once.
- Sales
Deal desk
Gets pricing, legal and security sign-off on a non-standard deal at the same time, and closes only when all are done.
- Customer success
Enterprise customer onboarding
Security review, data agreement and sign-in setup side by side; the account goes live only when all are done.
- Security
Finding remediation
Assigns each finding, reminds and escalates on a schedule, and closes it only after a re-scan passes.
- Finance
Month-end close
Opens every reconciliation, chases each sign-off, and locks the period when all are signed.
Our own
Customer onboarding
Our signup process: sign-in, AI fit check, a reviewer's approval, credits, tracking sheet.
Newsletter
Every Friday, an AI-drafted email per customer that cites only their real activity, never sent twice.
AI Agent coming next
Processes where AI chooses the next step itself, within guardrails you set: which steps it may use, what it can never skip, and where a person must approve.
Not sure Dex can support your process? Talk to us →
A growing library of connectors
Your process talks to the systems you already use through connectors.
- Available in alpha
Our onboarding, as a Dex flow
The whole onboarding · one running copy per customer
- Sign upsign-in answerwait: sign-in answerdo: create accountsignup screen: checking…
- Read profileGitHub · LinkedIn
- Fit checkAI · OpenAIfit score · evidence
- ReviewReviewerApprove · work queuedecision · usage limit
- CreditsUsage limitcheck when unclear: did that go through?
- SheetGoogle Sheets
- This customer's weekly check-in, tracked on its ownevery Friday at noonWeekly check-inAI draft · Gmailunsubscribe click
Any step survives a restart and carries onDurable execution
The code that calls GitHub, OpenAI, Sheets and Gmail
The step names follow our own onboarding design. Dex Web's run list and graph support processes written in Go today.
Dex concepts
| Element in the flow | Dex term | In plain words |
|---|---|---|
| The whole onboarding (one running copy per customer) | Flow | The process: one living record per customer, from signup until they unsubscribe |
| Each box: Sign up, Read profile, Fit check, Review, Credits, Sheet, Weekly check-in | Step | One stage of the work |
| Inside "Sign up": wait for the sign-in answer, then create the account | WaitFor / Execute | Each step has a waiting half and a doing half. The waiting half only says what it waits for; the doing half is where it acts, such as calling an outside system |
| Fit score, evidence, the reviewer's decision, the usage limit | Attribute | Case details the process remembers, saved automatically; searchable if you choose |
| The sign-in answer arriving; the unsubscribe click | Channel | An incoming message, delivered to the step waiting for it, once and in order |
| "Every Friday at noon" | Timer | A scheduled wait; nothing runs while it waits, for hours or weeks |
| The reviewer's Approve button in the work queue | RPC | How a person or system asks a running process something, or tells it to act now |
| The live "checking…" progress on the signup screen | Stream | Live updates for screens. Best effort, so never the official record |
| This customer's weekly check-in, tracked on its own | SubFlow | A process started by another, so big work splits into tracked pieces |
| The code that calls GitHub, OpenAI, Sheets and Gmail | Worker | Your app's engine: your software does the work, and Dex says what runs next |
| Any step survives a restart and carries on | Durable execution | Progress is saved after every step, so a crash, an update or a failed call picks up where it stopped |
| The map itself, and the list of every customer's case | Dex Web | Where people see every case and the path it took |
Lineage. Dex was created by our cofounder, Quanzheng Long, a founding engineer of Uber's Cadence project, to make durable execution accessible to application developers.
Turn your team's expertise into agentic processes
Start with the one that lives in a spreadsheet, a shared inbox and someone's memory. Describe it, and Dex AI Platform writes it as a process that keeps its place until the work is done.
Want help with your first process? Talk to us →