Skip to main content
Compute deploys an app from a GitHub repository on every push by default, or from a container image you built yourself. Connect the repository, pick the branch, and each push becomes a you can follow in the dashboard until it’s ready. You get a production and a preview , automatic domains, promote and rollback, and a gateway in front of every deployment. The is the service inside a .

​
Get started

Deploy from GitHub

Connect a repository and let every push deploy.

Deploy a container image

Ship an image you built yourself, from the dashboard or the CLI.

Compute plans

What you need before you can deploy, and what each plan allows.

​
Concepts

Projects, apps, and environments

How projects, apps, and environments nest.

Deployments

The thirteen lifecycle statuses, the build queue, and why a deployment fails.

Production and preview

Promote, roll back, stop, wake, and what happens on a timer.

Instances and autoscaling

Replicas, resource limits, health probes, and the autoscaler.

Regions

How regions are chosen, capped, and used for readiness and failover.

​
Build

Builds

Automatic builds or your Dockerfile, the build queue, caching, failures.

Dockerfile builds

Build context, the runtime contract, and the errors Unkey explains.

Build-time secrets

Use environment variables during the build without baking them in.

GitHub integration

Install, connect, branch mapping, fork approval, and what Unkey writes back.

​
Configure

Build settings

Dockerfile, root directory, build command, watch paths, auto deploy.

Runtime settings

Port, CPU, memory, disk, command, protocol, regions, replicas.

Health checks

The probe that gates traffic and restarts unhealthy instances.

Environment variables

Kinds, limits, import, and the variables Unkey injects.

Compute limits

Per-instance and workspace ceilings, per plan.

Spend budget

Alerts and an optional stop on monthly usage spend.
Last modified on October 22, 2026