Dex Cloud
Long-running processes, built and run for you.
Describe a process and the Dex Playground builds the app that runs it. Or write it with a Dex SDK and run it on Dex Engine. Either way, we run the servers, and every case keeps going through delays and failures.
You
When a lead signs up, research their company and draft a personal email. A rep approves deals over $10k. If there is no reply in five days, follow up. When they reply, read it and book a meeting if they are interested.
The app it builds
- Research the companyAI
- Draft a personal emailAI
- Rep approves large dealsInbox
- Send, then wait for a reply5-day follow-up
- Read the replyAI
- Book the meetingCalendar
Start from a description or from your own code
Dex Playground
For the team that owns the process. Describe it, and an agent writes the app, tests it, runs a preview and publishes it when you approve.
“When a lead signs up, research their company and draft a personal email.”Try in Dex Playground
Dex Engine
For engineers with their own Dex code. Your Workers connect to a Dex server we operate, one endpoint per application, and your code stays with you.
lead-follow-up.From a description to a live app
- 1
Describe
Tell the agent what the process does in your own words. It asks about the cases you left out and writes a requirements card you can read and change.
- 2
Build and preview
The agent writes an app in its own sandbox, tests each process and runs a preview you can click through.
- 3
Publish
Publish a version to production. A new version rolls out while earlier runs are still in flight.
- 4
Improve Early access
State the app's goals. The platform measures the live app and proposes changes for a person to approve.
See every case and act on it, without asking an engineer
Dex Cloud draws each process from its code and places every run on it. Open a Step to see its input, its result, what it waits for and every retry. Apps built in the Dex Playground also get an operations view in Studio, so the people who own the process can see where each lead is and step in.
- Flow
- The app's processes as a map, drawn from its code.
- Runs
- Every lead: where it is, what it waits for and what happened before.
- Inbox
- Everything waiting for a person, such as a rep's approval, in one list.
- At any Step
- Retry a failed Step, ask the agent about it, have the agent fix it, or go back to an earlier Step and run again.
- Interface
- The app's own page, for the people who use it every day.
Works with the tools you already use
Apps call other systems through more than 100 open-source connectors. When one is missing, the agent writes it.
Safe to run your business on
Credentials stay with the platform
A team connects Slack, Gmail or Salesforce once. The platform stores and refreshes the tokens; apps request them when they call the service and never keep them.
Each app runs on its own
Every app is built and run apart from other apps, from the first preview to production.
Roles on every request
Apps belong to a team space. Members have roles, and the platform checks them on every request.
Your code
Every app is ordinary Dex code in its own Git repository.
No training on your data
Your apps' content is not used to train AI models.
Start with one process
Describe it in a few sentences. The agent takes it from there.