Predictable pricing based on your engineering output.
Never pay per seat.
|
Starter $0 |
Most popular
Pro $49/mo |
Business $99/mo |
Enterprise Custom |
|
|---|---|---|---|---|
| Target | Open Source / Public Repos | 1–2 Engineering Squads | Multiple Teams / Department | Large-scale Operations |
| Monthly PR Limit | 500 merged PRs | 500 merged PRs | 2,500 merged PRs | Custom Volume |
| Private Repositories | remove | check_circle | check_circle | check_circle |
| Historical Backfill | 90 days | 90 days | 90 days | Custom |
| Velocity, Quality, Flow metrics | check_circle | check_circle | check_circle | check_circle |
| Release Spike Override | remove | 2× per year | 2× per year | Custom |
| Billing method | - | Credit card | Credit card | Invoice available |
| Get started free | Start free trial | Get started | Contact us |
Common questions
Pro and Business plans include a Release Spike Override — twice per year, you can exceed your monthly PR limit by up to 50% at no extra charge. It's there for big release pushes or end-of-quarter sprints. After the override is used, additional merged PRs in that month are queued and processed in the following 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 velocity metrics by default, so they don't distort your baseline lead time or throughput numbers.
Stop guessing. Start measuring.
Connect your GitHub account and have answers by tomorrow morning.
Generate Your Dashboard →Reads pull request metadata only. We cannot read your source code.