Deployment Previews

We’re introducing Deployment Previews, which are ephemeral, fully isolated deployments that let you spin up temporary environments tied to your existing deployment configurations.

Whether you’re validating a feature branch or sharing a working demo, previews give you a real, production-like environment without long-term infrastructure overhead.

Check out our Deployment Preview Guide to get started right away.

What you can do

• Add a preview to any existing deployment configuration
• Assign a unique subdomain for each preview
• Access that subdomain inside the running container via an environment variable
• Trigger a deployment run for a specific preview
• Delete a preview when it’s no longer needed
• Automatically clean up infrastructure when a preview is deleted
• Create and run previews from both the CLI and the UI

How it works

Previews inherit the base configuration of your deployment but run as isolated, ephemeral instances.

Each preview:

• Gets its own subdomain (e.g. feature-x-subdomain.yourapprul.com)
• Receives that subdomain as an environment variable inside the container
• Provisions its own infrastructure
• Can be independently deployed, re-deployed, or removed

When a preview is deleted, all associated infrastructure is automatically cleaned up by the Hyphen Agent, no manual teardown required.

What this means for you

• 🌿 Safe testing without touching staging or production
• 🔁 Branch-based workflows with real infrastructure
• ⚡ Faster iteration cycles
• 🧹 No lingering preview environments
• 💰 No paying for infrastructure you forgot to delete

Things to know

• Previews are tied to an existing deployment configuration.
• At least one app in the deployment must have a hostname and DNS zone configured to create a preview deployment
• Each preview must use a unique subdomain within that configuration.
• Infrastructure is fully torn down upon deletion.
• Previews can be created, deployed, and deleted from both the Hyphen UI and CLI.