Production-grade preview environments created automatically from Git

Upsun Preview Environments create isolated, full-stack environments for every branch or pull request. Each environment mirrors production at the platform level, including application configuration and services, so teams can validate real changes under real conditions. This replaces shared staging environments with on-demand previews that are safer, faster, and easier to govern.

How it works

Git-driven creation

Automatically create environments from Git branches and pull requests. Each update triggers a rebuild so previews stay aligned with code changes.

Full-stack replicas

Each preview is a production-accurate copy of your application environment. Code, configuration, and services are cloned to reflect real behavior.

Environment isolation

Every preview runs in its own isolated environment. Changes cannot impact production or other previews.

What this solves

Staging drift

Traditional staging environments often diverge from production over time. Upsun’s environments are created from the same source and configuration as production, reducing discrepancies and unexpected behavior at release time.

Risky releases

Testing against partial environments or mocked data increases deployment risk. Preview Environments make it possible to validate real changes against real conditions before they are merged.

Slow reviews and approvals

Reviewers no longer need to rely on screenshots or local setups. Each change can be reviewed in a running environment, speeding up code review, QA, and stakeholder sign-off with live links that can be shared.

Key capabilities

Automatic environment creation from branches and pull requests
Byte-for-byte environment cloning including configuration and services
Isolated infrastructure per environment
On-demand or automated lifecycle management
Support for databases, caches, queues, and background workers
CLI, API, and console access for full control

Enterprise considerations

Security

Preview Environments inherit Upsun’s security model, including network isolation, encrypted data paths, and hardened runtime environments. Testing does not weaken the production security posture.

Access control

Access to Preview Environments is governed by the same role-based permissions as the rest of the platform. Teams can control who can create, view, or modify environments.

Cost and lifecycle management

Environments are ephemeral by design. They can be created automatically when needed and removed when no longer in use, helping teams avoid long-running, unused infrastructure.

How teams use this in practice

Pull request validation

A developer opens a pull request. Upsun creates an environment automatically. Reviewers test the change in a live environment before approving the merge.

Database migrations

A team validates a schema migration against a production-grade dataset in their new environment. Issues are identified early, without risking downtime.

Stakeholder review

Product managers or QA teams review new features in an isolated environment using real data and configuration, reducing back-and-forth and release delays.

Get started

Start using Preview Environments to reduce release risk and speed up delivery.

Start a free trial Request a demo