Deployments
Ship Score, GitHub Check and rollback
A score out of 100 for every deploy, the verdict on the GitHub commit, and a way back to the last healthy deploy.
Checking a deploy isn't enough: you have to be able to decide quickly. Merge it, keep it in production, or roll back?
The Ship Score
Every deploy gets a score out of 100, with its breakdown: what was checked, what cost points, and what no check covers yet. A page replaced by “coming soon” or by a 5xx error is detected and flagged. Below your score floor, the release is treated as blocked.
On the commit, before merging
The GitHub Check shows PostShip's verdict right on the commit. A pull request is checked on its preview URL, and a Ship Score that is too low can block the merge. The Check is connected from Deployments → Settings, including on an account where the PostShip App is already installed. The Overview counts the week's checked previews, and how many are red — a count, not an alert.
Rollback
A Vercel deploy that broke a check carries “Roll back to the previous deploy”: PostShip points production back to the last deploy it checked as good. A per-project option does it without asking when a payment page breaks on release.