Deployment options
How a self-hosted Orchestrator can be deployed, which choices you make (database, file storage, TLS, front door) and what you are responsible for.
The Orchestrator runs on infrastructure you control: in your data center or in a cloud account you own. Robots and Studio run on your Windows machines and only make outbound connections to the Orchestrator over HTTPS 443; you never open inbound ports on Robot machines.
The supported deployment#
The release ships one Docker Compose file, docker-compose.core.yml, that runs four containers on one Linux host:
| Container | Role |
|---|---|
| Caddy | The TLS front door. Terminates HTTPS, passes WebSocket connections, and can obtain certificates automatically. |
Orchestrator (api) |
The API, web app, Robot gateway and all background work, in one process. |
| PostgreSQL 18 | All relational data. |
| Redis | Optional live-update support; the stack keeps working (readiness Degraded) without it. |
A host with 4 vCPU, 8 GB RAM and 40 GB of disk (plus room for your packages) is the documented minimum. For fleet sizing, see Sizing. Install it with Install on-premises.
Choices you make#
| Choice | Options |
|---|---|
| Database | The bundled PostgreSQL container, or your own managed PostgreSQL 18 with the pg_trgm extension. |
| Package and file storage | A local volume, an S3-compatible bucket (AWS S3, MinIO, Cloudflare R2, Wasabi, Ceph) or Azure Blob Storage. Chosen once, on first sign-in; it cannot change after files are stored. |
| TLS certificate | Let's Encrypt (public name, issued automatically), Caddy's own CA (internal name), or your own certificate. |
| Front door | The bundled Caddy, or your own load balancer or reverse proxy in front of the API. |
| Outbound email | SMTP for invitations, password resets and alert emails, or log-only mode while commissioning. |
What you are responsible for#
- Host sizing, patching and monitoring. See Monitoring and health.
- TLS certificates and DNS.
- Generating and escrowing the key-encryption key (
VELOPHEX_KEK) and token pepper before anyone stores a credential. - Backups and restore drills. See Backup and restore.
- Applying each release's schema script and image. See Upgrade the Orchestrator.
Try it on a developer machine#
To evaluate the platform on Windows with Docker Desktop, run .\build\Start-Evaluation.ps1 from a checkout. It builds the image, generates secrets, starts the stack on https://localhost:8443, creates a tenant, a workspace and a machine, and prints an enrolment command. It uses a development certificate and writes the administrator password to .env, so never use it for production.
Moving to a new host#
Back up the old host, deploy the same release on the new host with the escrowed .env, restore, and point DNS at it with the same public address. Robots reconnect on their own. See Restore onto a new host.
Next steps#
The supported deployment
Choices you make
What you are responsible for
Try it on a developer machine
Moving to a new host
Next steps