features

Rollback

Roll back to a previous deployment version instantly.

Rollback#

Deployed a bug? Roll back to a previous version instantly. Runix keeps your previous deployment versions, so you can restore a known-good state without rebuilding.

How rollback works#

Runix keeps previous Docker images for each deployment
Rolling back swaps the current container with the previous version
No rebuild required — it is instant
Environment variables use their current values (not the values from the previous deploy)

Rollback from the dashboard#

Open your deployment

Go to your deployment page in the dashboard.

View deployment history

Click the "History" tab to see all previous versions.

Click rollback

Click the "Rollback" button next to the version you want to restore. The rollback happens immediately.

Rollback from the CLI#

You can also trigger a rollback from the command line.

CLI rollback

bash

# View deployment history
runix history my-api

# Rollback to the previous version
runix rollback my-api

Rollback via the API#

API rollback

bash

curl -X POST https://api.runix.dev/deployments/a1b2c3d4-.../rollback \
  -H "Authorization: Bearer $TOKEN"

Rollback restores the previous container image but does NOT revert environment variable changes. If you changed env vars between deploys, the rolled-back version will use the current env vars.

Limitations#

Database schemas are not rolled back — only the application container
Rollback is only available for web services and workers, not databases
The number of versions kept depends on your plan

Blueprints

Overview