Frameworks

Ship the stack you already use

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 serverless containers. No build config to write first.

Free plan, no card. Google or GitHub sign-in.

Send me the link for my desktop
Create a free account
console.light-cloud.com/new
Light Cloud console: a repository detected as FastAPI

Pick a repo, no config: the files are read and the framework and build are filled in.

Frontend

Built once, served from the CDN.

A static build is uploaded to object storage and cached at the edge.

Full-stack

Rendered on the server, in containers.

Frameworks with a server side ship as containers that scale with traffic and down to zero when idle.

Backend

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.

How it works

Detection, not configuration.

The repo already describes the build. Light Cloud reads it instead of asking you to repeat it in a dashboard.

  1. 01

    Reads your repo

    Framework, runtime, and the right build and start commands are detected from the files in your project.

    package.json · next.config.ts

  2. 02

    Finds the package manager

    npm, yarn, pnpm, pip, or poetry. The matching install and build steps are used.

    pnpm-lock.yaml · poetry.lock

  3. 03

    Locates the output

    Config files are parsed to find where the build lands, so the right directory is served.

    dist/ · .next/

  4. 04

    Dockerfile wins

    If your repo has a Dockerfile, it is used as is and the app runs as a container.

    Dockerfile

ONE REPO · TWO TARGETSRepositorylight-cloud-templates/nextjs-app-router-starter · mainDetectionframework · manager · outputstaticbackendGlobal CDNstatic buildContainersscales to 0

Two targets

One repo, two targets.

A frontend build goes to the global CDN. A backend becomes a container that scales with traffic and stops billing at zero.

  • The target is picked from the repo. Override it when you know better.
  • Framework, package manager, build command, and output directory can each be set by hand.
  • A Dockerfile in the repo always wins and runs as a container.

Deploy your framework

Connect a repo and Light Cloud figures out the build. Start free, no card.