Rollback
The previous deploy comes back in four seconds
Knowing a page is broken is half the job. The other half is fixing it before you've understood why: the previous deploy worked, you just have to go back to it.
“I knew it was broken, but I was on the train.”
An alert at 11:40 pm is useless if the only possible answer is to open a laptop, find the host's console, find the right deploy and click in the right place.
- to put the old one back online
- 4 s
- rebuilds: the build already exists
- 0
- click, from the alert or the app
- 1
- if you've decided so, per project
- auto
to put the old one back online
rebuilds: the build already exists
click, from the alert or the app
if you've decided so, per project
How it works
01PostShip knows your deploys
Every Vercel deploy is seen, checked and remembered with its verdict.
02One click from the alert
The message — on your phone, Slack, Discord or Telegram — carries the button.
03Or on its own, if you want
Per project, you can decide that PostShip rolls back without asking when a production deploy breaks a page that passed right before.
04Checked after, like before
A rollback is a deploy like any other: it's checked right away, and the recovery alert goes out once everything is green again.
What we're often asked
What if the old deploy depends on a database that changed?
Rollback restores the previous code, not the data. That's why it's checked afterwards: if the old deploy doesn't pass either, you know right away, and automatic mode doesn't insist.
Does it work with Netlify and Cloudflare?
One-click rollback is available on Vercel. On Netlify and Cloudflare Pages, PostShip takes you to the right deploy in their console, with the verdict telling you which one to pick.
Can automatic mode run away?
It only goes back to a deploy that passed, once per incident, and never twice in a row on the same project without a fresh deploy in between. You can turn it off at any time.
Paste your site's URL. PostShip checks it in front of you, no account and no card.