Light Cloud reimagines the cloud console as a file system

What launched

A new platform called Light Cloud reached Hacker News's front page on 27 September 2026 with a Show HN post describing itself as a cloud console organised like a file system. The idea is to apply the mental model of folders and files, the interface developers already know from their own machines, to managing deployed applications and infrastructure. The details below come from the company's own marketing pages, and the product has not been independently reviewed.

One project, three pieces

According to the Light Cloud site, a project can hold a frontend, a backend and a database together. Static assets are served from a global CDN, container workloads run on Cloud Run, and the platform decides which target to use by reading the connected repository. Deployments start from a push to GitHub, GitLab or Bitbucket.

Databases are treated as first-class citizens rather than an afterthought: a managed Postgres instance is provisioned with a tier, a region and a storage size, and its credentials are encrypted and supplied to the application automatically.

From push to running service

The pipeline is deliberately thin. Once a repository is connected, every push starts a build. Light Cloud detects the framework, chooses a builder, and produces either a container image or a static bundle. The result is rolled out to Cloud Run or the CDN, and each deployment keeps the commit, the author and the logs attached to it. The site emphasises that there is no YAML to write and no CI runners to babysit.

Previews and idle costs

Every branch and pull request gets its own preview URL, built on push and removed when the branch is deleted. Containers scale to zero when idle, so billing stops when there is no traffic, and the next request wakes the instance back up. Cost therefore tracks actual runtime rather than permanently provisioned capacity.

Deployment through AI agents

The most contemporary feature is agent-driven deployment. Light Cloud ships an MCP server that can be added to Claude Code with a single command, after which a plain-language request to deploy the project handles sign-up, asks two setup questions and returns a live URL. The same server works in GitHub Copilot and Claude Desktop, and a CLI covers conventional shells.

ICE, an open-source side project

The company's Labs section also features ICE, an open-source visual editor for designing cloud infrastructure on a canvas, previewing its cost and deploying it to your own cloud accounts. ICE and its building blocks and templates are free under the PolyForm Noncommercial 1.0.0 licence.

Why it matters

Consoles at the major cloud providers are organised around services, not around your application, and that mismatch is a persistent source of friction. Treating infrastructure as something you browse like a file system is a small but genuinely different UX bet, and it arrives alongside features the market now expects from push-to-deploy platforms: per-branch previews, scale-to-zero billing and a managed database sitting next to the app. The MCP integration also points at where deployment tooling is heading, toward agents that can ship code rather than just write it. The caveats are real, though. This is a launch announcement drawn from a single marketing source, and pricing beyond a free Hobby plan is not detailed. The concept deserves attention; the execution remains unproven.