Project features

Deployments & rollback

Every build is a deployment with its own status, logs and commit. The previous healthy release keeps serving until a new one is up, and you can roll back at any time.

Deployment lifecycle

queued → building → deploying → healthy on success.
failedif the build or rollout fails — your previous healthy release stays live, so there's no downtime.
rolled_back when you promote an earlier release.

Triggering a deployment

From the dashboard, the CLI, or the API:

shell

# CLI
orizon deploy

# API
curl -X POST https://api.orizon.ng/api/v1/projects/proj_123/deployments \
  -H "Authorization: Bearer orz_pk_your_key" \
  -H "Content-Type: application/json" \
  -d '{"branch":"main"}'

Connected GitHub repos also deploy automatically on every push — see Deploy from GitHub.

Rolling back

Open the deployments list, find an earlier healthy deployment, and roll back to it. Orizon re-promotes that release as the live one. Because each build is immutable and kept, rollback is fast and safe.

Zero-downtime rolloutNew releases are built and started before traffic switches over, and a failed build never replaces what's already serving — so deploying is safe to do often.

Build & runtime logs

Stream logs for any deployment.

Screenshots

Each healthy deploy captures a preview.