Predictable pricing based on your engineering output.
Never pay per seat.

You could build the charts. Lead time, throughput and PR size take a few weeks of engineering, plus upkeep every time GitHub's API changes. What you can't build is the comparison: peer benchmarks need delivery data from many organizations, and an in-house tool only ever sees yours. Every team that joins FlowMetrics makes everyone's peer groups sharper. Stalled-PR nudges that calibrate themselves to your own history, and a value stream that separates work from waiting, come included. Pro costs $49 a month, less than a few hours of the engineering time a homegrown version would take.

Paid plans come with a 50% Overage Allowance that you can trigger twice a year for free. It's built specifically for major shipping pushes. If you pass the overage limit, we pause ingestion and automatically queue your remaining PRs for the next billing period.

Developer tools shouldn't punish you for growing your team or encourage people to share accounts. The value of FlowMetrics is in the data, not in the number of people looking at it. Pricing by PR volume ties your cost directly to your engineering output — a number you actually control.

Yes — all merged PRs count toward your monthly volume limit, including hotfixes and reverts. However, FlowMetrics automatically detects remediation PRs (those with "hotfix" or "revert" in the title or branch name) and excludes them from your lead time and review metrics by default, so they don't distort your baseline. They still count toward throughput, because a revert is still a merged PR.