One command from image to URL on GCP, AWS, Azure, or Cloudflare. Apps scale to zero when idle. Open source, works standalone - and connects to your org's Portal when credentials shouldn't live on laptops anymore.
Uses App Runner, Cloud Run, Container Apps and Containers - no Kubernetes or custom runtimes. Apps sleep when idle, wake on the next request. Cold starts in 1-3 seconds on Cloudflare, 3-5 on GCP, 2-5 on Azure. Instant on AWS.
Deploy to your own GCP, AWS, Azure, or Cloudflare account. Resources land where you can see, tag, and delete them with your existing tooling. In solo mode your cloud token stays on your machine; connect a Portal and credentials leave laptops entirely.
Push a local Docker image straight to the cloud and run it. Declare the database or bucket you need, and Relight provisions the right service per provider and injects the credentials as env vars.
One CLI, one workflow across Cloudflare, AWS, GCP, and Azure. Move an app to another provider without relearning anything.
Paste your API token. Cloudflare, GCP, AWS, Azure - one command to authenticate.
Any Docker app. Relight builds the image, pushes it to your registry, and deploys. You get a URL.
No traffic? Your app sleeps. Cost drops to zero. Next request wakes it.
On your own, the CLI is the fastest path from Docker image to URL. Connected to a Relight Portal, the same commands deploy through it instead - credentials move off your laptop and every deploy gets attributed, with nothing about the workflow to relearn.
Paste a cloud API token and deploy. The token never leaves your laptop, and every resource is created in your own account - visible, taggable, and deletable like anything else you run.
Point the CLI at your organization's Portal once. From then on cloud credentials live on the Portal instead of laptops, every deploy is attributed and audited, and apps can sit behind the Gateway's SSO.
Ready for the connected path? See the Portal and the Gateway.
Deploy into whichever clouds your organization already runs. Use one provider end-to-end - usually the org standard - or split layers across providers when there's a reason to.
These providers can host your entire app end-to-end - compute, database, DNS, and container registry.
| Layer | GCP | AWS | Azure |
|---|---|---|---|
| DNS | Cloud DNS | Route 53 | Azure DNS |
| APP | Cloud Run | App Runner* | Container Apps |
| DB | Cloud SQL (Postgres) | RDS (Postgres) | Flexible Server (Postgres) |
| Registry | Artifact Registry | ECR | ACR |
* Not true scale-to-zero. ~$2.55/mo minimum per idle app, but no cold starts.
Cloudflare, DigitalOcean, and GitHub can each cover individual layers (DNS, database, registry). Provider-by-provider details, pricing, and regions live in the provider comparison docs.
Simplest deploy
One API key, one bill. Everything runs in the same cloud with low latency between services. The simplest setup when you're already on a provider or just getting started.
Separate infra without moving DNS
Keep your domain on Cloudflare for free DNS and edge caching, while running compute and database on AWS. Common when you already manage DNS on Cloudflare but want AWS infrastructure.
Database managed separately
Compute on GCP Cloud Run with scale-to-zero, managed Postgres on DigitalOcean billed and operated separately, DNS on Cloudflare. Useful when the database outlives the apps in front of it.
Free and open source, every feature included. One command to install, one command to deploy.