TurboPanel Docs
Getting Started

Terminology

TurboPanel uses one name for each part. Docs, the app, error messages, emails and the installer all follow this page.

The parts

NameWhat it is
TurboPanelThe whole product: the control plane, the web app and the daemons on your servers.
Control planeThe program that runs the API and the database and serves the web app. On Self-hosted it is the turbopanel binary on its own host; on TurboPanel High Availability it runs on Cloudflare Workers.
AppWhat you sign in to and use. Web app means the bundle the control plane serves to your browser.
Daemonturbopaneld, the program on each server TurboPanel manages. The co-located daemon is the one on the control plane's own host.
ServerA machine TurboPanel manages. Say host only when you mean the operating system itself, as in "host firewall".
AdministratorThe person who runs a self-hosted control plane.

The two ways to run it

NameMeaning
Self-hostedYou run the control plane on your own host.
TurboPanel High AvailabilityTurboPanel runs the control plane for you, always on.

Always use these two names. "High Availability" describes the control plane only; it never means your own apps become highly available.

Words TurboPanel does not use

Not thisSay
consoleapp (or web app)
panel, for the appapp
instance, in customer copycontrol plane; administrator for "instance owner"
hosted instance, hosted control planeTurboPanel High Availability
node, remote nodeserver
dashboardthe page's own name, such as Overview
fleetservers
agentdaemon

Names you may still see in URLs, API paths, environment variables, file names and log lines, such as /api/daemon/v1/instance, TURBOPANEL_INSTANCE_URL or turbopanel-instance.service, are fixed for compatibility. The words there are not customer-facing names.

The certificate authority the control plane issues for daemons is the Platform CA.

Edit on GitHub

Last updated on

On this page