Rollbacks
Made a mistake? Rollback to any previous deployment instantly. Every successful deployment is saved, giving you a safety net for production changes.
How Rollbacks Work
When you rollback:
- The previous deployment's files are made active
- CDN is updated to serve the old version
- Changes propagate globally in seconds
- The rolled-back version becomes the current live version
Instant Recovery
Rollbacks are instant - no rebuild required. Your site recovers in seconds, not minutes.
Performing a Rollback
1
Open Deployment History
Go to the Deployments section in your project.
2
Select a Version
Find the deployment you want to revert to.
3
Click Rollback
Click the Rollback button next to that deployment.
4
Confirm
Confirm the rollback when prompted.
When to Rollback
- Broken functionality - Something stopped working
- Visual regressions - UI looks wrong
- Performance issues - Site became slow
- Integration failures - External services not working
- Urgent revert - Need to quickly undo changes
What Gets Rolled Back
- Included: All application code, styles, and static assets
- Not included: Database data, environment variables, domain settings
Environment Variables
Rollbacks don't affect environment variables. If you changed a secret or API key, you'll need to update it separately.
Version Retention
How long versions are kept:
- Free plan - Last 5 deployments
- Pro plan - Last 30 deployments
- Team/Enterprise - Last 90 deployments
Rolling Forward
After a rollback, you can always deploy again to move forward:
- Fix the issue in your code
- Deploy the fixed version
- Your fix becomes the new live version
Next Steps
- Status Tracking - Monitor deployments
- Environments - Test before production