Frameworks
Light Cloud reads your repo and picks the right build for 40+ frameworks. Frontends go to a global CDN, full-stack apps and backends run as containers on Cloud Run. No build config to write first.
Three repos, no config: the files are read, the build is filled in, and the right target lights up.
Built once, served from the CDN.
A static build is uploaded to object storage and cached at the edge.
Rendered on the server, on Cloud Run.
Frameworks with a server side ship as containers that scale with traffic and down to zero when idle.
SSR
Any runtime, as a container.
APIs and services in Node, Python, Go, Java, Ruby, PHP, or .NET — or bring a Dockerfile and it is used as is.
bring your own
Detection, not configuration.
The repo already describes the build. Light Cloud reads it instead of asking you to repeat it in a dashboard.
Framework, runtime, and the right build and start commands are detected from the files in your project.
package.json · next.config.ts
npm, yarn, pnpm, pip, or poetry. The matching install and build steps are used.
pnpm-lock.yaml · poetry.lock
Config files are parsed to find where the build lands, so the right directory is served.
dist/ · .next/
If your repo has a Dockerfile, it is used as is and the app runs as a container.
Dockerfile
One repo, two targets.
A frontend build goes to the global CDN. A backend becomes a container on Cloud Run that scales with traffic and stops billing at zero.
Connect a repo and Light Cloud figures out the build. Start free on the Free plan.