Push. Build. Live.

Every push ships your app

Connect a GitHub repository and every push to your production branch builds and ships automatically. Watch the build live, inject secrets at release, and roll back when you need to.

Start deploying Deployments quickstart

setcloud deploy

$ setcloud deploy storefront
✔ Push credentials obtained
✔ Image built
✔ Image pushed
✔ Deployment triggered

✓ Deployed deploy-1765432100 to storefront
  Monitor with: setcloud logs storefront --follow

// 01 — git-connected

Connect once, ship on every push.

Link a repository from the dashboard and the platform inspects it, builds it, and runs it. From then on, every push to your production branch goes live automatically — no build pipelines to configure, no build server to run. Prefer the terminal? setcloud deploy ships the folder you're working in.

+ Connect a GitHub repository in the dashboard
+ Every push to your production branch builds and releases
+ Full deploy history per project
+ Link a domain you registered here — or bring an external one

// 02 — builds

Watch the build, line by line.

Build output streams to your dashboard as it happens, so a failing build tells you why while it's failing — not in an email afterward. Builds use the current per-minute rate, rounded up to whole minutes and then to cents per job; build charges are separate from runtime and storage usage.

+ Live build and release logs, streamed
+ Whole build minutes, deducted from your credit balance at the current rate

// 03 — configuration

Config without commits.

Environment variables live with the service, not in the repo. Values from your secrets vault are injected at release, and when you attach a managed database, its connection string arrives as DATABASE_URL — already set.

+ Per-service environment variables
+ Secrets injected from the vault at release
+ Attached databases inject DATABASE_URL automatically

# set in the dashboard, injected at release
NODE_ENV=production
DATABASE_URL=postgres://app:••••@db.internal:5432/app
SESSION_SECRET=••••••••  (from your secrets vault)

// 04 — rollbacks

Roll back in one command.

Previous releases remain in deployment history; their instances are not kept warm. When a deploy goes sideways, setcloud rollback — or one click in the dashboard — returns the previous revision to production.

+ setcloud rollback <name> restores the previous revision
+ Same control from the dashboard deploy history

Current pricing

USD rates from the current billing catalog. Regional references vary with attributed usage.

Loading current rates…

Ship on your next push.

Connect a repository and go live in minutes. See the current build-minute rate below.

Start deploying Deployments quickstart