Checks and releases
Know whether it can ship.
Tests, signing checks and image boots on your own machines, CI results, uptime and TLS, read into one verdict per commit. Browser checks watch your pages from our cloud.
The release gate
One answer about one commit: Shippable, Not yet or Unproven, always with its reason. It reads what CI, your runners and your uptime checks proved. It reports; it doesn't stop a deploy.
- You decide what Shippable requires, per project.
- vitals gate exits 0 only when the verdict is Shippable.
- An alert when a project goes from Shippable to Not yet.
vitals gate pocket-walrus
- pocket-walrus · Not yet · Failed · 2 of 262
- ✗ Tests pass · Failed · 2 of 262
Checks on your own machine
A check is one thing that can pass or fail: a test command, a Docker smoke, a signing verification. The desktop app or the vitals CLI runs them where your code already is.
- By default your code, full logs and secrets stay on your machine.
- Nothing runs until you approve it, check by check.
- On a schedule, on each commit, or started from the web.
vitals link .
vitals checks approve
vitals run
Also in ShipVitals
Browser checks, in our cloud
A real browser opens one of your pages on a schedule and says whether what must be true was: it loaded in time, a text is on it, and nothing went wrong in its console or its own requests.
- No runner and no CI to set up.
- A check is data, never code: nothing you write runs in the browser.
Guide walks
A model walks your how-to guides step by step in a real browser, as a careful reader would, and reports what doesn't match: on your machine with your own OpenRouter key, or in our cloud against your staging site.
- Findings aren't coverage: a walk proves nothing about the rest.
- A finding opens as a GitHub issue, or copies as a prompt for your agent.
Results from your CI
Your CI uploads its test results, and each project's Health shows what passed, what failed and what flaked on main.
Runners
A runner is a machine paired to a workspace: your laptop with the app, or a headless box with vitals. One approval in the browser pairs it, and you choose who may start runs on it.
What leaves your machine
Results go to ShipVitals; most of the evidence stays where it was made. One table says what goes and what stays, and each project can change it.