Deploying overview
Orizon takes code in almost any shape and ships it. Point it at a repo, hand it a Dockerfile, or drop a folder — it detects the stack, builds it, and gives you a live URL with TLS.
Ways to deploy
- From GitHub — connect a repo and Orizon auto-deploys every push, reporting status back to GitHub.
- From a Git URL — paste any public
.gitURL (GitHub, GitLab, Bitbucket). - Dockerfile — full control over the build when you want it.
- Docker Compose — multi-service apps with one web service exposed.
- Upload — push a folder or zip from the dashboard or CLI; the stack is detected on the real files.
- PHP & WordPress — composer / public-docroot apps.
- Static sites — any folder with an
index.html. - Bun — Bun-based apps run on the Bun runtime.
Automatic stack detection
Whichever route you use, Orizon inspects your files to pick a build strategy — checking for a Dockerfile or docker-compose.yml, a Next.js config, go.mod, Cargo.toml, composer.json, Python project files, a Procfile, or a lone index.html. You can review and override the detected build before deploying. See Supported stacks for the full list.
PORT environment variable. Orizon runs your container with PORT=3000and routes public traffic to it. Static and PHP apps are served directly and don't need this.What happens on a deploy
Each deploy creates a deployment record, builds an image on a build node, pushes it to an internal registry, and runs it on a runtime node behind Caddy. The previous healthy release keeps serving until the new one is up, so a failed build never causes downtime. You can roll back to any earlier healthy deployment at any time — see Deployments & rollback.