Deployments
A deployment is a workload you run — a web service, static site, worker, scheduled job, or internal TCP service. This section covers how to configure them, control who can reach them, watch them, and recover from bad releases.
What a deployment is, the lifecycle of a rollout, and the views you use to manage one.
Web services, static sites, workers, scheduled jobs, and internal TCP services — and when to use each.
Deploy a prebuilt static site — served straight from object storage at the edge, no container to run.
Put a Google-login gate in front of a deployment — restrict who can reach it by email or domain.
Image, resources, port, replicas, command, args, and the rest of the knobs a deployment exposes.
Per-deployment env, reusable env groups, and how partial updates work.
Every deploy creates an immutable revision. Roll back to any of them in one call.
Metrics, logs, and Kubernetes events for diagnosing live deployments.
Automatic Sentry-lite error tracking — deploys.app mines your logs for stack traces, or lets your app report errors directly, and groups them into deduplicated issues with counts, a triage lifecycle, and notifications.