Introduction
TurboPanel is one place to run everything you host. Deploy websites, applications, and databases across your servers, choose where projects run, and ship from one console.
A lightweight TurboPanel daemon on each server connects it to your control plane and runs approved operations locally. Your workloads stay on your servers.
Private alpha — not yet publicly available
Both deployment models below are in private alpha and not yet publicly available. This page describes where we are headed as we work toward a beta release — see the roadmap for current progress.
Deployment models
TurboPanel High Availability
Planned default when TurboPanel operates the control plane worldwide. Private alpha — not yet publicly available; join the waitlist for access updates.
Self-hosted
Run the control plane on infrastructure you operate. Same product experience — your team owns uptime, upgrades, backups, and public access. Private alpha — preview docs only until a public release.
TurboPanel High Availability
- Control plane on a global edge network — fast and always on, close to your team worldwide (planned)
- No control-plane infrastructure, upgrades, backups, or public TLS for you to manage
- Private alpha · Not yet available — join the waitlist
Self-hosted
- Run the control plane on infrastructure you operate
- Same product experience as TurboPanel High Availability
- You are responsible for control-plane uptime, upgrades, backups, and public access
- Planned to be free, unlimited servers once it ships — you pay for the infrastructure you run
- Private alpha · Not yet available — preview self-hosted docs
Not sure which to choose?
TurboPanel High Availability is the planned default when you want TurboPanel to operate the control plane. Choose self-hosted when your team wants full operational custody — same product, your infrastructure. Neither path is publicly available yet.
What you get
- One console — servers, deploys, networks, and access in a single UI
- Fast worldwide access — the control plane is served from a global edge network, so it stays quick for distributed teams (planned for TurboPanel High Availability)
- Managed servers — enroll hosts with the production daemon installer when your control plane is available
- Private networking — securely link cloud, datacenter, and office infrastructure
- Automation when you need it — use the API to plug TurboPanel into your workflow
Architecture overview
Next steps
- Installation paths — Contributor dev, self-hosted preview, and TurboPanel High Availability status
- Self-hosted overview — Control plane and node setup (preview)
- Local development — Contributor Vagrant + dev console workflow
- Daemon setup — Adding managed servers
- Licensing — Repository licenses, notices, and Corresponding Source
Last updated on