Rollbacks
Zeabur keeps a record of every deployment, allowing you to roll back to any previous successful version if a new deployment introduces issues.
How Rollbacks Work
Each time you deploy a service, Zeabur creates a snapshot of that deployment (the built image). These snapshots are retained so you can revert to a known-good state at any time.
When you trigger a rollback:
- Zeabur creates a new deployment using the snapshot from the selected previous version.
- The new deployment goes through the standard health check process.
- Once the health check passes, traffic is routed to the rolled-back version.
- The failed deployment remains in your deployment history for reference.
Because rollbacks follow the same deployment flow, they benefit from zero-downtime behavior — the old (broken) deployment continues serving traffic until the rolled-back version is confirmed healthy.
Rolling Back from the Dashboard
To roll back a service:
- Open your service in the Zeabur dashboard.
- Go to the Deployments tab.
- Find the deployment you want to revert to in the deployment history.
- Click Rollback on that deployment.
- Zeabur will create a new deployment based on the selected snapshot.
Rollback creates a new deployment entry in your history. It does not erase or modify any previous deployments.
Rollback Methods by Service Type
Git-Deployed Services
For services deployed from a Git repository, you have two options:
- Dashboard rollback — Use the method described above to revert to a previous build snapshot.
- Git revert — Push a revert commit to your repository. Zeabur will detect the new commit and trigger a fresh build, effectively rolling back your code through your normal CI/CD flow.
Docker Image Services
For services deployed from a Docker image, you can roll back by specifying a previous image tag in your service settings. Update the image tag to the desired version, and Zeabur will redeploy using that image.
Prebuilt Services (Templates)
For services deployed from a Zeabur template, rollbacks follow the same dashboard workflow. Select the desired deployment from the history and click Rollback.
What Rollbacks Do Not Restore
Rollbacks restore the application code and build artifacts to a previous state. They do not affect:
- Environment variables — Any changes to environment variables since the original deployment remain in place.
- Volumes — Data stored in persistent volumes is not reverted.
- Database contents — If your deployment included database migrations, rolling back the application does not reverse those migrations. You may need to manually address schema changes.
If your deployment involved database migrations or other stateful changes, plan your rollback carefully. Consider restoring a database backup alongside the application rollback if needed.