Open source
Same product. Your choice of operator.
TurboPanel's control plane, daemon, and product UI are open source under AGPL-3.0-only. Self-host the full stack or use TurboPanel High Availability — the console and APIs are the same.
License
How each repository is licensed
| Repository | License | Current notices (trunk) |
|---|---|---|
| TurboPanel/turbopanel API, auth, orchestration hub, daemon cell | AGPL-3.0-only | Current development (trunk) |
| TurboPanel/turbopaneld Host daemon, Ansible, deploy runtime, metrics | AGPL-3.0-only | Current development (trunk) |
| TurboPanel/ui Signed-in product console (Expo / Tamagui) | AGPL-3.0-only with Apple App Store additional permission | Current development (trunk) |
| TurboPanel/dev Contributor dev console (not production install) | AGPL-3.0-only | Current development (trunk) |
| TurboPanel/website Marketing site and documentation source | Apache-2.0 / CC BY 4.0 code / documentation | Current development (trunk) |
Third-party components shipped inside TurboPanel artifacts keep their own licenses; the notices column is the current-development file on trunk, not a relicense and not the notices for a shipped artifact. For a release, use the THIRD_PARTY_NOTICES.md that shipped with that tag, commit, or packaged artifact — packaged daemon releases stage it at /opt/turbopanel/share/THIRD_PARTY_NOTICES.md. Community health files in turbopanel/.github use the path-based map in LICENSES/README.md. Contributions are accepted under the Contributor License Agreement. The full model is in Licensing.
What self-hosting includes
You operate the control plane; TurboPanel operates it on High Availability.
Self-hosted operator runs
- Control plane (Deno + Postgres + Caddy)
- UI static export or dev proxy
- Backups, upgrades, and public TLS for the panel
- One daemon per managed server (including co-located CP host)
TurboPanel High Availability operates
- Workers control plane + Hyperdrive database path
- Global edge TLS and uptime
- Accounts, email, and panel upgrades
- You still run workload servers and enroll daemons
The signed-in app experience does not differ by deployment model.
Repositories
Where the code lives
- TurboPanel Control Plane — API, auth, orchestration hub, daemon cell
- TurboPanel Daemon — Host daemon, Ansible, deploy runtime, metrics
- TurboPanel UI — Signed-in product console (Expo / Tamagui)
- TurboPanel Development Environment — Contributor dev console (not production install)
- TurboPanel Website & Docs — Marketing site and documentation source
Brand
Trademark and logo use
The code is open; the TurboPanel name and logo are brand assets.
Open-source licenses do not grant permission to use the TurboPanel name, logos, or other trademarks. You may accurately state that a product is based on, compatible with, or derived from TurboPanel. Modified distributions must not use the TurboPanel name, logos, or trade dress in a way that suggests they are official TurboPanel products without prior written permission.
Third-party marks are never covered by TurboPanel’s licenses or by the UI App Store additional permission. OS identity artwork stays under its original copyright, license, and trademark terms — see assets/os/NOTICE.md in the UI repository.
See Logo & brand for download links, clear space, and do-not rules, and TRADEMARKS.md for the trademark policy.
FAQ
Can I use TurboPanel commercially?
Yes. The control plane, daemon, product UI, and contributor console are AGPL-3.0-only. If you modify that software and run it as a network service users interact with, you must offer corresponding source to those users. The website is Apache-2.0 (code) and CC BY 4.0 (documentation).
Does self-hosted include the full product?
Yes — by design, self-hosted operators run the same control plane, UI, and daemon stack as TurboPanel High Availability, with the difference being who operates the control-plane infrastructure. Both paths are currently in private alpha and not yet publicly available.
Can I redistribute TurboPanel?
Yes, under the license of each repository, including corresponding source where AGPL requires it. App Store copies of the UI are also covered by the Apple App Store additional permission in that repository. That permission applies only to material TurboPanel has authority to license — not third-party components or marks. Do not imply endorsement or use TurboPanel trademarks beyond what the license and brand guidelines allow.
Do third-party components use TurboPanel’s license?
No. Components shipped inside TurboPanel artifacts keep their own copyright and license terms. Use the THIRD_PARTY_NOTICES.md that shipped with that release, tag, or exact git revision — not the current trunk file. Packaged daemon releases stage the matching file at /opt/turbopanel/share/THIRD_PARTY_NOTICES.md. The website keeps a first-party NOTICE in addition to generated third-party notices.
Are third-party marks covered by TurboPanel licenses?
No. TurboPanel’s licenses and the UI App Store additional permission never grant rights in third-party trademarks or artwork. OS identity marks (for example the Debian swirl) are recorded in the UI repository’s assets/os/NOTICE.md and remain under their original terms.
Where is source for a published UI build?
Each store binary and production update publishes corresponding source for that exact revision. Native Settings → About names the license, version, and source URL for the git revision baked into that build — not the trunk branch.
Where is source for a deployed control plane?
GET /api/health returns the license and a revision object with commit and sourceUrl. sourceUrl points at the exact git tree for that revision, not trunk.