# Deployments · Light Cloud

> Connect a GitHub repository and every push builds and deploys on its own. Static sites go to a global CDN, containers run on Cloud Run, and every deploy keeps its history.

## The whole loop

A push on `main` becomes `shop.light-cloud.io` in under a minute: push, build, deploy, live. Every deploy stays in history with its commit, duration, and status.

## How it works

1. **Connect a repository.** Sign in with GitHub, GitLab or Bitbucket and pick a repo. GitHub gets an App, GitLab and Bitbucket a webhook - either way Light Cloud builds on push. (`acme/storefront · main`)
2. **It detects the build.** Framework, package manager, build command, and output directory are read from the repo. Override any of them. (`Next.js · pnpm · .next`)
3. **Every push builds.** A push to a connected branch triggers a build with Cloud Build. The log streams while it runs. (`▸ pnpm build — 27s`)
4. **It goes live.** Static assets land on a global CDN, containers roll out on Cloud Run, and you get a URL. (`shop.light-cloud.io`)

Connect once. After that, a git push is the deploy. Nothing to trigger, no pipeline file to maintain.

## Static or container, one workflow

A static build is uploaded to object storage and served from a global CDN. A backend build becomes a container image on Cloud Run that scales with traffic — and down to zero when idle.

- Light Cloud reads the repo to decide which path fits. Set it yourself when you know better.
- Both targets share the same deploy record: commit, author, duration, status, and log.
- A Dockerfile in the repo is used as is; without one, Light Cloud writes one for your framework.

## What you get with every deploy

- **Push to deploy.** A commit on a connected branch is all it takes. No manual build step, no separate CI to wire up.
- **Build logs per deploy.** Follow each build as it runs and read the full log afterwards from the deploy record.
- **Deploy history.** Every deploy keeps its commit, message, author, duration, and status, so you can see what shipped and when.
- **Automatic Dockerfile.** No Dockerfile in the repo? Light Cloud generates one for your framework. Bring your own and it wins.
- **Deploy without a repo.** Push a local folder straight from the VS Code extension or the MCP server when a repo is not set up yet.
- **Roll back.** Redeploy any earlier commit from the history when a release needs to go back.

## Runs on Google Cloud

Managed infrastructure without touching a cloud console. Light Cloud wires these services together for every app:

- **Cloud Build** runs every build.
- **Artifact Registry** keeps container images.
- **Cloud Run** runs containers and scales to zero.
- **Cloudflare CDN** serves static sites worldwide.

## Start

Connect a repository, push, and watch it go live. Start free, no card, at https://console.light-cloud.com.