Self-hosting configurator

Deploy OpenMA

Pick the runtime boundary. We will turn it into a reviewed topology, an executable handoff, and a concrete health check.

Secrets never leave your machine. Choices stay in this tab; secret values go directly to the provider.

Step 1 of 3

Where should the control plane live?

Choose the deployment target. Sandbox providers can still be swapped later.

Cloudflare Recommended The complete edge topology, provisioned in your account. Three Workers, Durable Objects, Containers, D1, KV, R2, and Queue. Docker Fastest A durable Node deployment for one host or private network. OpenMA server and vault proxy with a shared persistent data directory. Fly.io Ready Run the Node topology on Fly Machines with a persistent volume. Fly Launch reads the checked-in Machine adapter and provisions its first volume. Vercel Beta A bounded serverless control plane with the agent loop inside Sandbox. Vercel provisions Neon Postgres; object storage stays explicit; Sandbox executes claimed Work.

Step 3 of 3

Your deployment handoff

Run this locally. The CLI opens provider authentication and reports each resource it creates.

Ready

git clone https://github.com/openma-ai/open-managed-agents.git
cd open-managed-agents
pnpm install
pnpm setup:cloudflare

Verify after deploy curl https://<your-main-worker>.workers.dev/health

Full guide

Deploy OpenMA

Where should the control plane live?

Choose safe defaults

Your deployment handoff

OpenMA project created