Push size, RAM, latency, accuracy — or any number your build prints — from CI, a nightly job or your laptop. Driftmetrics keeps the history, slices it by product, component and version, and fails the pull request when a budget breaks.
Flat price per org — never per seat. We never see your source or your binary.
A chat thread where someone pastes the numbers after each release.
A 917-line script that prints the size table.
A README table someone updates by hand every release.
A spreadsheet of size × accuracy × latency per model.
A GitHub issue that has been the size dashboard for six years.
Every team that cares about these numbers has already built a worse version of this. It works — until keeping it current is someone’s job, and nothing stops the pull request that quietly blows the budget.
Anything your build already prints — size, RAM, latency, accuracy, cost per build. One binary, one command.
$ driftmetrics push \
--version v2.4 \
--metric binary_size=2.14MB✓ pushed · comparing to v2.3A budget per metric becomes a status check: the merge is blocked when a number goes the wrong way — not a notification after it shipped. A straight comparison, so no statistics and no bare-metal runners.
Every metric you push in one dashboard, faceted across a monorepo — per product, per component, per target, per branch. Not one tool per metric type, and not a Grafana panel someone builds first.
| metric | v2.4 | Δ |
|---|---|---|
| binary_size | 2.14 MB | +10.9% |
| peak_ram | 419 KB | +1.7% |
| latency_ms | 41.6 ms | −1.2% |
| accuracy | 91.3% | +0.1% |
Driftmetrics ingests numbers — a metric name, a value, a few tags. Your build produces them and your CI keeps everything else. There is no artifact upload to review, nothing to parse on our side, and nothing for compliance to sign off on.
Every release gets a shareable report — so anyone on the team can see exactly what changed between versions, generated automatically.
Alpha pricing — the first five teams keep three months free.
I take on a few projects at a time, free, and set them up myself: send me the repo and I’ll open the pull request that pushes your numbers from CI and gates the budget you pick — you review it like any other PR. I pick them by hand, so tell me what you’d want to catch.
A handful at a time — I reply either way, within a day.
I’m onboarding 5 teams personally — free for 3 months — to gate the numbers they care about before they merge.
Work emails only, please — it helps me line up the right early conversations.
Prefer email? Write to me directly →