Documentation
Deploy to your own server, without touching a terminal
One install script turns a fresh VPS into a portal that builds and runs Dockerised web applications behind an automatic TLS reverse proxy, with server and container monitoring. These pages cover installing it, deploying to it, running it, and every value you can configure.
Where to start
Getting started
What the platform is, what it needs, installing it on a fresh machine, claiming the first account, and deploying something to prove it works.
Deploying applications
Projects and environments, ZIP and Git sources, how a build type is detected, what the compose sanitiser rewrites, domains and TLS, variables, volumes, and rollback.
Running the platform
Monitoring, alerts and notification channels, managed PostgreSQL, Redis and MinIO, backups, upgrades, and the incident procedures.
Reference
Every environment variable, the API surface, the installer, the agent, plan limits, and the architecture the rest of it follows from.
One thing to know before you install it
The control plane holds the Docker socket, so anyone with admin access to the portal has root on the server. Everything else in the design follows from that: the compose file you wrote is never run as written, archive extraction refuses the whole archive on the first entry that escapes its destination, and every traefik label a user file declares is stripped. Each of the three has a regression suite whose purpose is to stay unbroken.
Read the security model →