Ship Score
Not all failures are equal, and neither is the score
A broken Open Graph card and a dead checkout are not the same incident. The Ship Score weighs them differently, and tells you in one sentence why it dropped.
“I had twelve red alerts. I didn't know which one to open first.”
Green or red is a poor summary as soon as there's more than one thing to watch: it ranks nothing, and after a few false starts nobody looks anymore.
- to start with
- 100
- page that takes money
- −40
- share card
- −15
- expiring SSL
- −10
to start with
page that takes money
share card
expiring SSL
How the score is built
01A hundred points, then we deduct
Every production deploy starts at 100.
02Weighted by what it costs
A page that takes money is worth 40 points, because an hour of outage there is counted in revenue.
03A number, and the sentence that explains it
“60 — the payment page no longer loads the Stripe script.” The score tells you whether to go; the sentence tells you where.
04Shareable, if you decide so
The public deploy card shows the score and how it evolves on a page you can send to a client, without giving them access to your account or to your list of URLs.
What we're often asked
Can I change the weighting?
Not the scale, no: a score that means the same for everyone is a score you can compare from one deploy to the next. The Team plan does let you set a minimum score below which the GitHub Check turns red.
Does a score of 100 mean everything is perfect?
It means everything you asked to be checked passed. PostShip doesn't guess what matters on your site: the score is worth what your list of monitored URLs is worth.
And if the score drops without anything breaking?
It happens: a certificate nearing its expiry deducts points before it becomes an incident. That's intended — the score anticipates, the alert reacts.
Paste your site's URL. PostShip checks it in front of you, no account and no card.