Deployment
Guides for operators who run TurboPanel in production. TurboPanel High Availability and self-hosted control planes are both in private alpha and not yet publicly available — these pages document planned and preview paths as we work toward a beta release.
Private alpha
Neither TurboPanel High Availability nor self-hosted is publicly available yet. Contributor development uses Vagrant + sibling repos; production daemon installs use turbopanel.sh once you have a control plane.
Self-hosted overview
When to run your own control plane and what you operate
Control plane
Control plane, Caddy, Postgres, and API surfaces
Daemon setup
Install turbopaneld on managed servers with turbopanel.sh
Hostnames and TLS
Control-plane names on port 8443; port 80 only while Let's Encrypt issues or renews
Security
TLS, install gate, sockets, and secret handling
Typical operator flow
Choose self-hosted or TurboPanel High Availability (waitlist at pricing).
Provision the control plane on your infrastructure or use the TurboPanel High Availability when available.
Enroll each managed server with Daemon setup (turbopanel.sh +
license).
Harden with Security, pair versions via Compatibility, and plan upgrades.
Also in this section
- Daemon update — Refresh or recover a stuck server
- Metrics — Host metrics storage and queries
- Server metrics glossary — What each chart in the app means
- Troubleshooting — Common deployment issues
- Purge — Purge TurboPanel from a host
Last updated on