# Light Cloud Docs > Documentation for the Light Cloud deployment platform. Deploy web apps from Git: static sites, containers, and managed Postgres, with a preview for every branch and deploys you can run from Claude or GitHub Copilot. ## Getting started - [Introduction](https://docs.light-cloud.com/getting-started/introduction): Light Cloud is a deployment platform for web apps - connect a GitHub, GitLab or Bitbucket repo, push, and get a live URL for static sites, containers, and managed databases. - [Quickstart](https://docs.light-cloud.com/getting-started/quickstart): Deploy your first app in minutes - sign in with GitHub, GitLab or Bitbucket, pick a repository, confirm the detected build settings, and get a live URL on every push. - [How it works](https://docs.light-cloud.com/getting-started/how-it-works): The build and deploy pipeline - webhooks trigger Cloud Build, static sites go to the CDN, servers run as containers that scale to zero. - [FAQ](https://docs.light-cloud.com/getting-started/faq): Short answers to the questions people ask first - cost while idle, framework support, monorepos, custom domains, databases, and rollbacks. ## Creating resources - [Creating resources](https://docs.light-cloud.com/create/overview): How the Create page works - deploy from a Git repository, a .zip upload, or a template, or provision a database, with settings detected from your code. - [Application settings](https://docs.light-cloud.com/create/application-settings): Name, root directory, framework, instance size, and region - the settings that define what an application is and where it runs. - [Build settings](https://docs.light-cloud.com/create/build-settings): Port, install command, build command, and output directory - how Light Cloud turns your source into a static site or a running container. - [Scaling](https://docs.light-cloud.com/create/scaling): Min and max instances, concurrency, and CPU target - how container apps scale with traffic and scale to zero when idle to stop billing. - [Git automation](https://docs.light-cloud.com/create/git-automation): Deploy on push, a preview environment for every branch, and automatic cleanup when branches merge - the three Git automation toggles explained. - [Database settings](https://docs.light-cloud.com/create/database-settings): Every field on the database create form - engine (PostgreSQL or MySQL), shared vs dedicated size, storage, region, credentials, and seeding. - [Templates](https://docs.light-cloud.com/create/templates): Start from a working starter - a single app, or a stack like WordPress or Open SaaS that ships an app with a connected database in one create. - [Deploy from an upload](https://docs.light-cloud.com/create/upload): Deploy a local folder or .zip without a Git repository - from the Create page, from Claude via the MCP server, or from VS Code. ## Platform - [Deployments](https://docs.light-cloud.com/platform/deployments): Connect a GitHub, GitLab or Bitbucket repository and deploy on every push. Light Cloud detects the framework and build settings, and every environment can override them. - [Deployments: Git providers](https://docs.light-cloud.com/platform/deployments/git-providers): GitHub, GitLab and Bitbucket on Light Cloud - how each connects, what access it needs, how pushes reach your app, and how starter templates land in your own repository. - [Deployments: Builds](https://docs.light-cloud.com/platform/deployments/builds): What happens inside a build - Cloud Build steps, generated Dockerfiles, lockfile-exact installs, static uploads, and reading a failed build. - [Deployments: Rollbacks](https://docs.light-cloud.com/platform/deployments/rollbacks): Ship again or ship backwards - Redeploy for settings changes, git revert for bad code, and manual releases when deploy-on-push is off. - [Preview environments](https://docs.light-cloud.com/platform/preview-environments): A deployed environment and URL for every branch and pull request, created on push and cleaned up automatically when the branch is done. - [Databases](https://docs.light-cloud.com/platform/databases): Provision managed PostgreSQL 15 or MySQL 8.0 next to your apps - tiers from a $3 shared instance, running on Cloud SQL in four regions. - [Databases: Connect an app](https://docs.light-cloud.com/platform/databases/connect): Wire an application to a managed database - connection strings, TLS, CLI access from your laptop, and DATABASE_URL examples per framework. - [Databases: Backups](https://docs.light-cloud.com/platform/databases/backups): Daily automatic backups for every database, point-in-time recovery for PostgreSQL, and .sql import and export from the Backup tab. - [Custom domains](https://docs.light-cloud.com/platform/custom-domains): Point your own domain at any application or environment, with SSL certificates issued and renewed automatically - nothing to install or rotate. - [Frameworks](https://docs.light-cloud.com/platform/frameworks): Every framework Light Cloud detects and builds - full-stack and backend apps as containers, static frontends on the CDN, and Dockerfile for the rest. - [Frameworks: Next.js](https://docs.light-cloud.com/platform/frameworks/nextjs): Deploy Next.js on Light Cloud - server-rendered behind the edge CDN by default, or as a static export served entirely from the CDN. - [Frameworks: Nuxt](https://docs.light-cloud.com/platform/frameworks/nuxt): Deploy Nuxt on Light Cloud - detected from nuxt.config, built into a Node.js container behind the edge CDN, scaling to zero when idle. - [Frameworks: SvelteKit](https://docs.light-cloud.com/platform/frameworks/sveltekit): Deploy SvelteKit on Light Cloud - detected from svelte.config, built with the Node adapter into a container behind the edge CDN. - [Frameworks: Remix](https://docs.light-cloud.com/platform/frameworks/remix): Deploy Remix on Light Cloud - detected from the Remix dependencies, served by its Node server in a container behind the edge CDN. - [Frameworks: Astro](https://docs.light-cloud.com/platform/frameworks/astro): Deploy Astro on Light Cloud - static output on the CDN by default, or the Node adapter as a container under the SSR policy. - [Frameworks: Django](https://docs.light-cloud.com/platform/frameworks/django): Deploy Django on Light Cloud - a Python container on port 8000, with environment-driven settings, startup migrations, and WhiteNoise static files. - [Frameworks: Ruby on Rails](https://docs.light-cloud.com/platform/frameworks/rails): Deploy Ruby on Rails on Light Cloud - a Ruby container on port 3000, with DATABASE_URL wiring, startup migrations, and precompiled assets. - [Frameworks: Laravel](https://docs.light-cloud.com/platform/frameworks/laravel): Deploy Laravel on Light Cloud - a PHP container on port 8080, configured through environment variables instead of a committed .env file. - [Frameworks: Symfony](https://docs.light-cloud.com/platform/frameworks/symfony): Deploy Symfony on Light Cloud - a PHP container on port 8080, configured through environment variables, with DATABASE_URL for Doctrine. - [Frameworks: WordPress](https://docs.light-cloud.com/platform/frameworks/wordpress): Deploy WordPress on Light Cloud - a PHP container with one-click MySQL wiring, or the full stack created in one go from the template. - [Frameworks: Blazor](https://docs.light-cloud.com/platform/frameworks/blazor): Deploy Blazor on Light Cloud - a .NET container on port 8080, with Kestrel bound to the routed port and configuration from environment variables. - [Frameworks: Wasp](https://docs.light-cloud.com/platform/frameworks/wasp): Deploy Wasp on Light Cloud - a Node.js container on port 8080 with PostgreSQL, JWT secret generation, and URL variables derived on deploy. - [Frameworks: React](https://docs.light-cloud.com/platform/frameworks/react): Deploy a React app on Light Cloud - detected from the Vite or CRA setup, built to static files, and served from the global CDN for free bandwidth. - [Frameworks: Vue](https://docs.light-cloud.com/platform/frameworks/vue): Deploy a Vue app on Light Cloud - detected from the Vite setup, built to dist, and served from the global CDN with free bandwidth. - [Frameworks: Angular](https://docs.light-cloud.com/platform/frameworks/angular): Deploy an Angular app on Light Cloud - detected from angular.json, built to dist/browser, and served from the global CDN with free bandwidth. - [Frameworks: Svelte](https://docs.light-cloud.com/platform/frameworks/svelte): Deploy a Svelte app on Light Cloud - detected from the Vite setup, built to dist, and served from the global CDN with free bandwidth. - [Frameworks: SolidJS](https://docs.light-cloud.com/platform/frameworks/solidjs): Deploy a SolidJS app on Light Cloud - detected from the Vite setup, built to dist, and served from the global CDN with free bandwidth. - [Frameworks: Qwik](https://docs.light-cloud.com/platform/frameworks/qwik): Deploy a Qwik app on Light Cloud - detected from the Vite setup, built to dist as a static site, and served from the global CDN. - [Frameworks: Gatsby](https://docs.light-cloud.com/platform/frameworks/gatsby): Deploy Gatsby on Light Cloud - detected from gatsby-config, built to public, and served from the global CDN with free bandwidth. - [Frameworks: Docusaurus](https://docs.light-cloud.com/platform/frameworks/docusaurus): Deploy Docusaurus on Light Cloud - detected from docusaurus.config, built to build, and served from the global CDN with free bandwidth. - [Frameworks: Eleventy](https://docs.light-cloud.com/platform/frameworks/eleventy): Deploy Eleventy on Light Cloud - detected from the Eleventy config, built to _site, and served from the global CDN with free bandwidth. - [Frameworks: Static HTML](https://docs.light-cloud.com/platform/frameworks/static-html): Deploy plain HTML, CSS, and JavaScript on Light Cloud - no build step, files served straight from the global CDN with free bandwidth. - [Frameworks: Express](https://docs.light-cloud.com/platform/frameworks/express): Deploy Express on Light Cloud - detected from package.json, run as a Node.js container on port 8080, scaling to zero when idle. - [Frameworks: Fastify](https://docs.light-cloud.com/platform/frameworks/fastify): Deploy Fastify on Light Cloud - a Node.js container on port 3000, with the host binding Fastify needs to be reachable in a container. - [Frameworks: NestJS](https://docs.light-cloud.com/platform/frameworks/nestjs): Deploy NestJS on Light Cloud - built and run as a Node.js container on port 3000, with configuration from environment variables. - [Frameworks: AdonisJS](https://docs.light-cloud.com/platform/frameworks/adonisjs): Deploy AdonisJS on Light Cloud - built and run as a Node.js container on port 3333, with HOST and PORT wired from the environment. - [Frameworks: Hono](https://docs.light-cloud.com/platform/frameworks/hono): Deploy Hono on Light Cloud - a Node.js container on port 3000 using the Node server adapter, scaling to zero when idle. - [Frameworks: Node.js](https://docs.light-cloud.com/platform/frameworks/nodejs): Deploy a plain Node.js server on Light Cloud - no framework required, run as a container on port 8080 with lockfile-exact installs. - [Frameworks: FastAPI](https://docs.light-cloud.com/platform/frameworks/fastapi): Deploy FastAPI on Light Cloud - a Python container on port 8000, served by Uvicorn bound to the routed port. - [Frameworks: Flask](https://docs.light-cloud.com/platform/frameworks/flask): Deploy Flask on Light Cloud - a Python container on port 8000, served by Gunicorn bound to the routed port. - [Frameworks: Python](https://docs.light-cloud.com/platform/frameworks/python): Deploy any Python app on Light Cloud - the runtime behind Django, FastAPI, and Flask, run as a container on port 8000. - [Frameworks: Gin](https://docs.light-cloud.com/platform/frameworks/gin): Deploy Gin on Light Cloud - a compiled Go container on port 8080 with fast cold starts, ideal for scale to zero. - [Frameworks: Echo](https://docs.light-cloud.com/platform/frameworks/echo): Deploy Echo on Light Cloud - a compiled Go container on port 8080 with fast cold starts, ideal for scale to zero. - [Frameworks: Fiber](https://docs.light-cloud.com/platform/frameworks/fiber): Deploy Fiber on Light Cloud - a compiled Go container on port 8080 with fast cold starts, ideal for scale to zero. - [Frameworks: Go](https://docs.light-cloud.com/platform/frameworks/go): Deploy any Go app on Light Cloud - net/http or any framework, compiled into a container on port 8080 with sub-second cold starts. - [Frameworks: Spring Boot](https://docs.light-cloud.com/platform/frameworks/spring-boot): Deploy Spring Boot on Light Cloud - a Java container on port 8080, configured through environment variables and relaxed property binding. - [Frameworks: Quarkus](https://docs.light-cloud.com/platform/frameworks/quarkus): Deploy Quarkus on Light Cloud - a Java container on port 8080, with environment-variable config and fast startup in JVM or native mode. - [Frameworks: Java](https://docs.light-cloud.com/platform/frameworks/java): Deploy any Java app on Light Cloud - the JVM runtime behind Spring Boot and Quarkus, run as a container on port 8080. - [Frameworks: Sinatra](https://docs.light-cloud.com/platform/frameworks/sinatra): Deploy Sinatra on Light Cloud - a Ruby container on port 3000, served by Puma bound to the routed port. - [Frameworks: Ruby](https://docs.light-cloud.com/platform/frameworks/ruby): Deploy any Ruby app on Light Cloud - the runtime behind Rails and Sinatra, running Rack apps as containers on port 3000. - [Frameworks: ASP.NET](https://docs.light-cloud.com/platform/frameworks/aspnet): Deploy ASP.NET Core on Light Cloud - a .NET container on port 8080, with Kestrel on the routed port and configuration from environment variables. - [Frameworks: PHP](https://docs.light-cloud.com/platform/frameworks/php): Deploy any PHP app on Light Cloud - the runtime behind Laravel, Symfony, and WordPress, run as a container on port 8080. - [Frameworks: Dockerfile](https://docs.light-cloud.com/platform/frameworks/docker): A Dockerfile in the repository always wins - run anything as a container, with the port, PORT variable, and image-size rules that make it work. - [Environment variables](https://docs.light-cloud.com/platform/environment-variables): Set configuration and secrets per application, override them per environment, and bulk edit everything as a .env file in the console. - [Observability](https://docs.light-cloud.com/platform/observability): Build logs, searchable runtime logs with live tail, and per-environment metrics for production and every preview. ## Deploy with AI - [Overview](https://docs.light-cloud.com/deploy-with-ai/overview): Deploy without opening a dashboard - ask Claude via the MCP server, or use the @lightcloud extension in GitHub Copilot Chat in VS Code. - [Claude (MCP server)](https://docs.light-cloud.com/deploy-with-ai/mcp-server): Add the Light Cloud MCP server to Claude Code or Claude Desktop to create apps, deploy, and read logs from a conversation. - [GitHub Copilot (VS Code)](https://docs.light-cloud.com/deploy-with-ai/vscode-copilot): Install the Light Cloud VS Code extension and deploy from GitHub Copilot Chat with @lightcloud slash commands like /deploy and /status. ## Billing - [Pricing](https://docs.light-cloud.com/billing/pricing): Infrastructure at cost with no markup, billed by the hour - container, database, and bandwidth rates, plus a 30-day free trial. - [Billing](https://docs.light-cloud.com/billing/billing): How metering works - instance-hours, build minutes, bandwidth, scale to zero, trials, spending limits, and team member billing. ## Reference - [API](https://docs.light-cloud.com/reference/api): The Light Cloud HTTP API - base URL, bearer tokens, the organisation scope every call needs, request and response conventions, errors, and rate limits. - [API: Authentication](https://docs.light-cloud.com/reference/api/authentication): Authenticate against the Light Cloud API - creating and managing API keys, what a key can and cannot do, and the session tokens the console and MCP server use. - [API: Applications](https://docs.light-cloud.com/reference/api/applications): Application endpoints - list, retrieve, create, deploy, rename, move, delete, and manage custom domains. - [API: Environments](https://docs.light-cloud.com/reference/api/environments): Environment endpoints - list, create, update settings and variables, scale, deploy, read logs and metrics, and password-protect. - [API: Deployments](https://docs.light-cloud.com/reference/api/deployments): Deployment endpoints - list an environment's history, retrieve one deployment with its logs, and roll back to an earlier release. - [API: Databases](https://docs.light-cloud.com/reference/api/databases): Database endpoints - provision, retrieve, resize, get a connection string, rotate the password, dump, and inspect data. - [API: Uploads](https://docs.light-cloud.com/reference/api/uploads): Upload endpoints - request a signed URL, PUT the archive, complete the upload, then create an application from it. - [API: GitHub](https://docs.light-cloud.com/reference/api/github): GitHub App endpoints - installation status, linking an installation to an organisation, and listing repositories and branches. - [API: Errors](https://docs.light-cloud.com/reference/api/errors): What the API returns when a call fails - the error body, HTTP status codes, the full error code table, and the permission each endpoint checks. - [Limits](https://docs.light-cloud.com/reference/limits): Every platform number in one place - container sizes, scaling ranges, database tiers and storage, retention windows, and trial limits. - [Glossary](https://docs.light-cloud.com/reference/glossary): Every platform term defined in a sentence or two - application, environment, deployment, preview, scale to zero, cold start, and the rest. ## Labs - [ICE](https://docs.light-cloud.com/labs/ice): ICE is Light Cloud's open-source visual editor for cloud infrastructure - drag blocks, preview cost, and deploy to your own GCP, AWS, or Azure.