Preview environments
Push a branch and get a live URL built from it. Open a pull request and reviewers get a link. Delete the branch and the environment goes away. Each preview is password protected.
Push a branch, get a password-protected preview on its own light-cloud.io subdomain, merge, and it is gone.
From branch to review link, and back to nothing.
Connect a repository once. Every branch after that comes with a URL and leaves without a trace.
Connect the branch and push. Light Cloud creates an environment for it, separate from production.
git push origin feature/checkout
The branch is built the same way production is, so what a reviewer sees is what ships.
checkout-shop.light-cloud.io
Open a pull request and reviewers get a link to click instead of a branch to pull.
Light Cloud · Preview ready
Delete the branch and its environment is removed. Stale previews do not pile up.
environment removed
One environment per branch.
An application can have many environments, one for each branch you connect. Each is a full copy of the setup, not a shared staging box.
What comes with every preview.
Every preview sits behind a password, so a review link is safe to share without exposing unfinished work.
Every branch gets its own environment with its own address, built from that branch and nothing else.
Open a pull request and the preview builds automatically, so reviewers click a link instead of pulling the branch.
Delete the branch and its environment is removed. Stale previews do not pile up.
The production environment is separate and is not touched by branch activity.
Container previews scale to zero when no one is using them, so you are not paying for review apps overnight.
A preview is built the same way production is, so what a reviewer sees is what ships.
Set it once.
Both are on by default. Turn them off per application if you want to control when previews come and go.
Connect a repository and open a pull request. The preview builds itself.