Deployment History

The Deployment History page gives you a complete record of all past preview environments, with the ability to redeploy them with a single click.

How It Works

When an environment is destroyed (manually or by TTL expiration), its metadata and Docker image are archived automatically. This means you can:

Deployment history is available for all plans (Individual and Business).

Navigate to Dashboard > History to see a table of all archived deployments. Each record shows:

Column	Description
Environment	The original URL of the preview
Label	Optional label assigned during deployment
Region	Deployment region (US, EU, APAC, LATAM)
Type	Project type (node, python, go, etc.)
TTL	The TTL duration that was set
Created	When the environment was first deployed
Archived	When the environment was destroyed or expired

Region filter: Filter the list by deployment region using the dropdown
Pagination: History is paginated with 10 records per page. Use the Previous/Next buttons to navigate

Click the redeploy button (circular arrow icon) next to any history record to create a new environment from the archived Docker image.

When redeploying:

The original subdomain and URL are reused if available
If the subdomain is already taken (409 conflict), a new random subdomain is assigned
The new environment gets a fresh TTL based on your current plan defaults
You are redirected to the Environments page to see the new deployment

Click the delete button (trash icon) to permanently remove a history record. You will be asked to confirm before deletion.

The archiving happens automatically and is best-effort:

When an environment is destroyed or expires, the API sends the metadata to the Dashboard

The Docker image is preserved in the regional Zot registry for future redeployment

If the Dashboard is temporarily unreachable, the environment is cleaned up normally (including image deletion)

Redeployed environments that are subsequently destroyed do not create duplicate history entries.