Self-hosting - BMA Developer Docs

Self-hosting is not yet a supported product path. The BMA source repository is private during early access, and the steps below describe how the code base is structured to run, not a tested self-hosting release. Talk to the BMA team before planning a self-hosted deployment.

Components

Process	Role
`api`	Native REST API, SSE, executor and daemon connections, terminal and desktop relays
`managed-agents`	The `/v1` Managed Agents–compatible facade; translates to the native API and stores no state
`worker`	Runs agent turns: claims work, builds context, calls the model, runs tools. Stateless; scale horizontally.
`maintenance`	Reaps expired leases, reconciles machine pools, pauses and deletes idle machines, cleans up storage
`migrate`	Applies schema migrations before the other processes start
`bmad`	The machine daemon on every machine

What you need

PostgreSQL (the migrator must connect to the writer directly, not through a transaction pooler), Redis, and an S3-compatible bucket.
A filesystem shared by api, every worker and maintenance for memory stores (BMA_MEMORY_DIR).
A public origin (BMA_PUBLIC_URL) reachable by browsers and by bmad on your machines.
At least one model provider and one machine source.
For the /v1 facade: an organization, a default project, a default model provider config and an environment template pool (BMA_ENVIRONMENT_TEMPLATE_POOL). Without a template pool, POST /v1/environments returns 400.

Current limits

Area	Limit
Local quick start	The repository’s Docker Compose file starts the control plane, but there is no local sandbox provider: you need a cloud sandbox account or a BYO machine running `bmad` before an agent can run tools.
Sandbox providers	BeeOS operates and tests E2B (including a self-hosted E2B cluster with its own templates). The code base contains adapters for other providers inherited from the upstream project; they are not validated by BeeOS.
Machine templates	The desktop-capable templates and `bmad` builds are produced by BeeOS release workflows; there is no public template registry yet.
Desktop live view	WebRTC requires a reachable TURN server; without one, the viewer falls back to RFB over WebSocket.
Packaging	Releases, published images and upgrade notes for self-hosters are not yet published.

Open-sourcing the platform is on the roadmap.

​Components

​What you need

​Current limits

Components

What you need

Current limits