Run your own Macrofold deployment on infrastructure you control. The deployment guide uses Vercel, Neon PostgreSQL, private Cloudflare R2 storage, and Vercel Sandbox.
If you want to use the managed service, follow Macrofold Cloud setup. Calling Cloud does not require deploying these services yourself.
Connect your application
After deployment, create a scoped API key in your dashboard and set your SDK's base URL to your HTTPS origin, without /v1. The API quickstart, SDKs, CLI, and product guides apply unchanged. Keys and resource IDs belong to the deployment that issued them; changing a URL does not move data between deployments.
Choose a starting point
| Goal | Guide |
|---|---|
| Try the product without provider accounts | Local development |
| Deploy your own 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 local Docker profile also runs real harnesses through the API without Vercel. It is a trusted development environment, not a production multi-tenant deployment recipe. Vercel is the production integration path described here; see portability for its boundaries.
Use the acceptance checklist to verify your deployment before opening access.