Preview Environments

Every pull request gets its own cloud environment. Reviewers can test changes against real infrastructure before approving, catching issues that unit tests miss.

Start building

See how it could work for your team.

Book a demo

Add receipt storage to orders#482

Openwants to merge 3 commits into main from feat/receipts

Building appRunning

Running testsRunning

Starting preview environmentRunning

encore-botcommented just nowBOT

Preview environment for this pull request

waiting for checksOpen

Waiting for checks to pass

Test in production-like environments

When you open a pull request, Encore automatically creates a dedicated cloud environment with its own databases, queues, and infrastructure. The PR gets a comment with a link to the live environment.Reviewers can click through the app, test API changes against real data, and verify database migrations work correctly. Seed the environment, clone from staging, or start fresh, so “works on my machine” surprises show up before the merge rather than after it.

~2minto spin up

100%isolated

Preview environments documentation

Spun up per pull request

Your servicesall of them

A fresh databasemigrated

Pub/Sub topicsisolated

Object storageempty buckets

Secretsenvironment-scoped

Seed or cloned datareal schemas

External systemssandbox credentials

A public URLshareable on the PR

Automatic cleanup, no wasted spend

Preview environments are created when PRs open and automatically destroyed when PRs close or merge. No more forgotten staging environments running up cloud bills.Resources scale to zero when not in use, so you only pay for what you actually use during testing.

PR opened

environment created

active development

PR merged/closed

environment destroyed

Created on open, destroyed on merge. Nothing lingers.