Collaborate

Preview environments

Get a full copy of your stack for every pull request, then tear it down on merge.

Start for free Talk to sales

PR #318

feature/new-billing

Checks passed

preview-318

webReady
apiReady
databaseReady
workerReady

Review real changes, not screenshots

Every pull request gets its own running stack, so reviewers can click through the change before it ships.

Full-stack copies
Web services, workers, and databases are cloned from your config for each branch.
Shareable URLs
Each preview gets a unique link that is posted back to the pull request.
Seeded databases
Start every preview from an empty schema, a seed script, or a recent snapshot.
Automatic cleanup
Previews stop on merge or after a period of inactivity that you choose.

How preview environments work

Open a pull request and the rest happens on its own.

Branch
Pull request
Config
Secrets

Configuration

Turn on previews in one line

Enable previews for the whole stack, then fine-tune plans and expiry for preview copies only.

Smaller plans for preview copies
Expiry after a set number of days
Seed scripts for preview databases

          
            
                1
                previews:
              
                2
                  generation: automatic
              
                3
                  expireAfterDays: 3
              
                4
                 
              
                5
                services:
              
                6
                  - type: web
              
                7
                    name: web
              
                8
                    previews:
              
                9
                      plan: starter
              
                10
                databases:
              
                11
                  - name: app-db
              
                12
                    previews:
              
                13
                      seedCommand: npm run db:seed

          
            
                1
                # List running previews
              
                2
                $ cloud previews ls
              
                3
                preview-318  feature/new-billing  ready   2h ago
              
                4
                preview-317  fix/login-redirect   ready   1d ago

Why previews change code review

Reading a diff tells you what changed. Clicking through a running copy tells you whether it works. Preview environments give designers, product managers, and QA the same view the end user will get, before anything reaches production.

What gets copied

Previews are created from the same config file as production, so the architecture always matches. You decide which services take part and how big they should be.

Every web service, worker, and cron job in your config
Databases created fresh, seeded, or restored from a snapshot
Environment variables from a dedicated preview group

Keeping costs low

Preview copies can run on smaller plans than production, and they stop automatically when the pull request closes or after the expiry you set. You pay per second only while a preview is running.

Preview environments

Review real changes, not screenshots

Full-stack copies

Shareable URLs

Seeded databases

Automatic cleanup

How preview environments work

Turn on previews in one line

Why previews change code review

What gets copied

Keeping costs low

Works well with

Infrastructure as code

Zero-downtime deploys

Private networking

Push code today. Be live before your coffee cools.