Durable execution.
No replay.

Add Dex to your AI agent or workflow to make it resilient to any disruptions.

Built for reliable agents

Keep your agent framework. Wrap the agent in one call, and Dex runs each model call and tool call as its own Step.

  • A crash reruns only the call in flight.
  • Tool calls that need approval wait as long as it takes.
  • New code takes effect at the next Step.
$ pip install dex-agents-pydantic-ai "pydantic-ai-slim[openai]"
agent.pyPydantic AI · Python
agent = Agent("openai:gpt-5.2", instructions="You help customers with their orders.")
# @agent.tool find_order, refund_order, email_customer: unchanged

flow = pydantic_ai_session_flow(
    agent,
    flow_type="OrderAgent",
    tool_policies={
        "find_order": ToolPolicy(ToolEffect.READ),
        "refund_order": ToolPolicy(ToolEffect.IDEMPOTENT_WRITE, requires_approval=True),
        "email_customer": ToolPolicy(ToolEffect.NON_IDEMPOTENT_WRITE),
    },
)

Durable execution, done differently

  • Change code safely

    No replay, so you deploy while runs wait. Each run picks up the new code at its next step.

  • Write ordinary code

    No determinism rules. A Step is plain code: call any API or library, check the time, generate IDs.

  • See the business process

    Dex Web draws every flow from its code and shows where each run is on it.

  • Data-native

    Attributes are a fast, low-cost key-value store that syncs to your database of choice.

Compare Dex with replay-based engines

Zero dependencies

Dex Server is one Rust binary. S3 holds the data and RocksDB is its write-through cache, so there is no database, queue or search cluster to run beside it.

Your application
ClientStarts Flows and talks to them
WorkerHosts Flows and runs their Steps and RPCs
Dex SDK
Local blob cache
Dex Engine
Dex ServerOne Rust binary
S3Blob storage
RocksDBWrite-through cache

Build with what you already use

The Dex skills teach Claude Code, Codex and Cursor how Dex works, from the first Flow to the connectors. Or write it yourself with an SDK and the Dex CLI.

  • Go
  • Python
  • TypeScript
  • Java
  • Rust
$ brew install superdurable/tap/dexcli
$ dexcli dev

Quick start

$ claude plugin marketplace add superdurable/dex-skills
$ claude plugin install superdurable-dex@superdurable

A growing library of connectors

  • Google Sheets
  • Gmail
  • Slack
  • Google Drive
  • Google Calendar
  • HubSpot
  • Airtable
  • Notion
  • Salesforce
  • OpenAI
  • Jira
  • Zendesk Support
  • LLM
  • Asana
  • Mailchimp
  • Trello
  • Calendly
  • Stripe
  • Zoom
  • PostgreSQL
  • MySQL
  • monday.com
  • Typeform
  • Twilio Messaging
  • Google Forms
  • LinkedIn
  • Microsoft SQL Server
  • Amazon S3
  • Microsoft Outlook Mail
  • GitHub
  • Gemini
  • Freshdesk
  • Google Docs
  • Microsoft Teams
  • Webhook
  • Intercom
  • Microsoft Excel
  • Zoho Desk
  • Help Scout
  • Spotify
  • Xero
  • Email (IMAP and SMTP)
  • BambooHR
  • Confluence
  • Microsoft OneDrive and SharePoint
  • Google Workspace Admin
  • Hacker News Daily
  • Microsoft Entra ID
  • Algolia
  • Alpha Vantage
  • Amazon SQS
  • Bitbucket
  • Brevo
  • ClickUp
  • Close
  • Cloudflare
  • Coda
  • Cohere
  • Contentful
  • Datadog
  • Discord
  • DocuSign eSignature
  • ElevenLabs
  • Figma
  • Front
  • GitLab
  • Gorgias
  • Harvest
  • Hiver
  • Jira Service Management
  • Klaviyo
  • Linear
  • Mailgun
  • Microsoft Outlook Calendar
  • Mixpanel
  • Netlify
  • NewsAPI
  • OAuth 2.0 HTTP
  • OpenWeatherMap
  • PagerDuty
  • PayPal
  • Pinecone
  • Pipedrive
  • Postmark
  • QuickBooks Online
  • Re:amaze
  • Resend
  • SendGrid
  • Sentry
  • Shopify
  • Smartsheet
  • Snowflake
  • Square
  • Supabase
  • TMDB
  • Todoist
  • Unsplash
  • Vercel
  • Webflow
  • WooCommerce
  • YouTube
  • Zoho CRM

How Dex differs from replay-based engines

Replay-based enginesDex
Changing code of running processesRecovery replays workflow code against its history, so a change that alters the sequence of steps needs a version branch in the code.Each Step's result is recorded. Running Flows continue on new code from their next Step.
Seeing a runA list or timeline of history events.A graph generated from the code, with each run drawn on it: where it is, what it waits for, what happened.
Business dataKept in workflow variables or in your own database; searching across runs needs extra setup.Attributes: durable, indexable and searchable across runs, with optional writes to PostgreSQL, MySQL, Snowflake, Databricks or MongoDB.
Calling other systemsYou write the client code.More than 100 open-source connectors, such as Slack, Gmail, Salesforce and Stripe.
Running the serverA server cluster with a database, often with a search cluster beside it.A single binary that stores everything in object storage such as S3, managed for you or run yourself.

Run it where you want

Dex Cloud

We run the engine and its storage. Your code and workers stay with you.

How Dex Cloud works

Run it yourself

Dex is source available: one binary and your own S3. Your code does not change.

Self-hosting guide