Before you deploy

dx runs its web application and durable state in your Cloudflare account. Agent workspaces (Orbs) run on providers people connect in Settings (E2B), and optionally on providers the deployment offers itself: E2B, Cloudflare Containers in the same Cloudflare account, or both.

Prerequisites

• A Cloudflare account that can create Workers, D1 databases, R2 buckets, and Durable Objects. Workers AI is optional.

• Optionally, Orb providers on the deployment’s own account:

  • E2B: an E2B account and API key.
  • Cloudflare Containers: the Workers Paid plan, and a running Docker daemon with buildx on the deploying machine to build the Orb image.

  Without one, each person or workspace connects their own E2B account.

• Git, Node.js 22.19 or newer, and pnpm 12.14.

• Rust, zig (pip install ziglang), and cargo install --locked cargo-zigbuild only when you build dxd locally instead of using the release asset.

Install the repository dependencies from a clean checkout:

pnpm install --frozen-lockfile

Know what can cost money

Cloudflare and E2B bill your accounts under their current plans. Cloudflare Containers run and are billed in your Cloudflare account. Model providers may charge separately. A deployment can incur charges while no browser is open because stored data and running or paused workspaces follow provider billing rules.

Before continuing, check:

1. Cloudflare Workers, D1, R2, Durable Objects, and Workers AI pricing.
2. E2B concurrency, template, CPU, memory, storage, and runtime limits.
3. The pricing and spending limits for each model provider you enable.

Stopping a local command does not cancel provider resources. Use the explicit destroy workflow when you no longer want the deployment.