Deploy the dashboard, API, and durable scheduler on Vercel, with Neon PostgreSQL, private Cloudflare R2 storage, and Vercel Sandbox for agent execution.
Choose a starting point
| Goal | Guide |
|---|---|
| Try the product without provider accounts | Local development |
| Deploy a hosted service | Deployment walkthrough |
| Configure runtime settings | Environment reference |
| Set up the database | Neon and PostgreSQL |
| Register models, apps, GitHub, and billing | Provider integrations |
| Understand deployment artifacts and rollback | Deployment architecture |
| Plan capacity and recovery | Hosting and scaling |
Hosting responsibilities
The web application serves customer requests and dashboard streams. PostgreSQL owns state, leases, queues, and accounting. Workflow schedules bounded execution steps. Sandbox isolates native agents. R2 retains encrypted checkpoint content. Resend delivers identity email; Stripe manages paid subscriptions and top-ups when configured.
Keep the database, application, and storage in compatible regions. Set provider spending controls and a conservative execution ceiling before accepting work. The software's concurrency setting does not reserve vendor capacity.
The standalone Node/Docker control plane supports local simulation. Real non-Vercel execution currently requires an additional Sandbox credential adapter; see portability. Vercel is the supported production integration path described here.
Use the acceptance checklist to verify your deployment before opening access.