Flux reads your GitHub, Linear, and deploy data. Then it tells you which stage your pull requests are sitting in, and how long they have been there.
Example integrations in this demo
Each number traces back to a specific event in your repository: a commit, a review, a merge, a deploy.
01 / Pulse metrics
Deploy frequency, lead time for changes, change failure rate, and time to restore — all four derived from your deploy and incident webhooks.
Deploys per week · last 12 weeks · sample org
02 / Cycle time
Median hours per stage · 23.6h total · sample org
Coding, review, QA, deploy. Flux records the median hours a change spends in each one. The longest stage is where next week goes, and on most teams it is not the one people name.
03 / Team health
Reviews completed per person, counted weekly, alongside focus-time fragmentation and after-hours commit share.
Reviews completed, last 7 days · sample org
Every figure below is sample data, generated for this demo. A connected workspace shows the same view against your own repositories.
Deploys per week · 13 weeks
Starter is free and does not expire. Paid tiers add repositories, history, and views that span the whole team.
One developer, one repository.
Cycle time and review load across the team.
SSO, audit logs, and a signed SLA.
Point Flux at one repo and it backfills 90 days of history in a few minutes. No card, and nothing to install on your machine.