DevOps & Cloud · Delivery metrics
ShipRate
Your delivery numbers, without a platform.
The four DORA metrics from your GitHub or GitLab data in one command, with lead time split into coding, review and deploy waits, and every failed change traced to the deploy that caused it.
$ ship-rate report ship-data.json
62 deploys and 133 changes over 11.9 weeks
Deployment frequency 5.23 a week high
Lead time for changes 2.0 days high
coding 22.8 h, waiting for review 16.1 h, in review 1.7 h, waiting to deploy 5.5 h
Large pull requests take 2.5x as long to ship as small ones
The problem
Boards, investors and auditors ask how fast and how safely you ship. Most teams guess, or roll out a paid engineering-metrics platform to find out. Neither tells you where changes actually wait.
What it does
Deployment frequency, lead time for changes, change failure rate and recovery time, with elite, high, medium or low bands
Lead time split into coding, waiting for review, in review and waiting to deploy, so the bottleneck is obvious
Every failure named: the deploy, and whether it failed, was reverted, was hotfixed or was followed by an incident
Deploys from GitHub Deployments, releases, your deploy workflow or GitLab environments; incidents from labelled issues
Pull request size against lead time, and this month compared with last month
Client-ready HTML report with weekly charts, and a weekly GitHub Action
Team-level only: nothing is measured per person
How it works
- Point it at a repository and choose where deploys come from
- Get the four metrics, the lead-time breakdown and the failed deploys
- Fix the biggest wait and measure again next month
Works with
Runs in your CI
# Weekly delivery report
ship-rate fetch $REPO --deploys workflow:deploy.yml --days 90
ship-rate report ship-data.json --format md --out delivery.md --html delivery.html
Your data
- Read-only GitHub or GitLab API calls with your own login.
- Runs on your laptop or in your CI; nothing is uploaded.
- No per-person metrics.
Who it's for
Questions
How does it know a deploy failed?
The deploy itself failed, a revert or hotfix followed it within a day, or an incident issue was opened soon after. Each failure is listed with its reason, so you can check it.
We don't use GitHub Deployments.
Use your releases, or the runs of your deploy workflow on the main branch.
Related
Often used with ShipRate
BlastRadar
Change impact analysisKnow what a change will touch. Before a release, see every service a change can affect and the line of code that links it. After the release, confirm those services are still healthy.
Free to start · quote on requestView product → DevOps & CloudSLOStudio
SLOs and error budgetsReliability you can measure. Define each SLO in a few lines and get correct burn-rate alerts, an error budget everyone understands, and a release gate, on the monitoring you already run.
Free to start · quote on requestView product → DevOps & CloudTestScope
Test impact selectionRun the tests that matter. Every pull request runs the tests its change can affect, each with a stated reason, and the full suite whenever a change is too broad to trust.
Free to start · quote on requestView product →See ShipRate on your own data
A 30-minute call. We run the product on your export, repository or document and walk you through the results.