Full environments for every PR
Each preview environment includes isolated databases, dedicated pub/sub topics, and separate infrastructure. Test changes against real services before merging.
- ✓Isolated PostgreSQL databases
- ✓Dedicated pub/sub topics
- ✓Environment-specific secrets
- ✓Automatic cleanup on merge
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 with real data, and verify database migrations work correctly. No more "works on my machine" surprises after merging.
- ✓Isolated PostgreSQL databases
- ✓Dedicated pub/sub topics
- ✓Separate cron job schedules
- ✓Environment-specific secrets
- ✓Full tracing and metrics
- ✓Automatic cleanup on merge
Test with realistic data
Preview environments can be configured to start with seed data, clone data from staging, or start fresh. This means you can test database migrations against real schemas and verify your changes work with actual data shapes.
- ✓ Start with empty databases for testing migrations
- ✓ Clone data from staging for realistic testing
- ✓ Run seed scripts to create test data
- ✓ Use production-like data volumes for performance testing
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.
Lifecycle Management
Preview environments are created when PRs open and automatically destroyed when PRs close or merge. No more forgotten staging environments running up cloud bills.
