Getting help and following the work
Everything about running apps on Light Cloud in one place: the docs, support that can see your deployments, the blog, and a roadmap we keep honest. ICE, our open-source editor, is developed in the open on GitHub.
Framework guides, build settings, databases, domains, limits. Start here before anything else.
Read the docsQuestions about your own apps, builds, databases, or billing. Asking from the console attaches your account and deployment history.
Open the consoleWhat shipped, how it is built, and the occasional argument about cloud pricing.
Read the blogWhat is live, what is next, and what we decided against. Public and kept current.
See the roadmapICE is the visual cloud editor behind Light Cloud: design infrastructure on a canvas, preview the cost, deploy to your own cloud accounts. It is PolyForm Noncommercial 1.0.0 and built in the open — issues, PRs, and Discussions all live on GitHub. The hosted platform is a separate, closed codebase, so platform questions belong in the console rather than the repository.
Source, issues, releases. PolyForm Noncommercial 1.0.0.
Star and watchAsk, share canvases, propose features. Lower friction than an issue.
Open DiscussionsBugs and feature requests for the editor. Triaged by the maintainers.
Open an issueVulnerabilities in ICE follow the disclosure process in SECURITY.md. For the hosted platform, use the contact form.
Read SECURITY.mdStart small. A typo fix is a contribution. So is a sketch of an interface change in an issue.
Six files: definition, blueprint, info, resource mapping, per-provider handler, node renderer. static-site is the simplest reference implementation.
Implement the deployer interface in packages/providers/<cloud> with create / update / delete per service. Open an issue first so the maintainers can coordinate scope.
Templates live in packages/templates/src/. A template is a typed composition of blocks with edges and default properties. Useful patterns are always welcome.
docs/ in the repo. Architecture, core engine, deploying-to-gcp, AI assistant, blocks reference. Smaller PRs that fix a single confusion are the best kind.
Be civil. Be specific. Assume good faith. The full text is in the repo.
CODE_OF_CONDUCT.mdNode 22+, pnpm 10+, then pnpm dev:all. Full setup is in the contributing guide.