Deployments
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.
A push on main becomes shop.light-cloud.io in under a minute. Every deploy stays in history.
From commit to URL, in four steps.
Connect once. After that, a git push is the deploy. Nothing to trigger, no pipeline file to maintain.
Sign in with GitHub and pick a repo. Light Cloud installs a GitHub App so it can build on push.
acme/storefront · main
Framework, package manager, build command, and output directory are read from the repo. Override any of them.
Next.js · pnpm · .next
A push to a connected branch triggers a build with Cloud Build. The log streams while it runs.
▸ pnpm build — 27s
Static assets land on a global CDN, containers roll out on Cloud Run, and you get a URL.
shop.light-cloud.io
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.
What you get with every deploy.
A commit on a connected branch is all it takes. No manual build step, no separate CI to wire up.
Follow each build as it runs and read the full log afterwards from the deploy record.
Every deploy keeps its commit, message, author, duration, and status, so you can see what shipped and when.
No Dockerfile in the repo? Light Cloud generates one for your framework. Bring your own and it wins.
Push a local folder straight from the VS Code extension or the MCP server when a repo is not set up yet.
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.
Connect a repository, push, and watch it go live. Start free on the Free plan.