Tracking the flow of value, from idea to impact.
Every software organization is trying to answer one question, and at the current state of practice, none can: is the value we generate equivalent to, or greater than, the cost of our staff and platform? RIVER exists because the modern practice of release has finally made that question measurable.
DORA measures the commit-to-deploy segment rigorously; RIVER extends measurement and discipline across release, adoption, and impact.
A question every organization asks and none can answer.
CEOs ask it. Boards ask it. CFOs ask it. Engineering leaders are asked to defend their scope and headcount against it. Product leaders are asked to defend their roadmap against it. The question is central to how modern software businesses are operated, funded, and held accountable.
The reason the question is hard is structural. Today's measurement practice is fractured: product, engineering, and operations each measure themselves in their own vocabulary, and no shared per-release artifact carries what the work was for from one end of the value chain to the other. A release that reaches one percent of users and gets reversed registers, in most measurement systems, the same as a release that reaches all users and transforms a business metric.
Deploy and release, once separated.
The problem is not new in principle; it is newly tractable. Over the past decade a set of practices has propagated through the industry: feature flags, progressive delivery, canary releases, cohort targeting, guarded automation, reversible experimentation. These practices have made the release-and-after segment of the value chain separately observable. That which can be separately observed can be separately measured. That which can be separately measured can be separately operated on.
RIVER is possible now because the operational separation of deploy from release has become mature enough to carry a shared vocabulary. It was not possible ten years ago. It is necessary now because the gap between what the four delivery metrics measure and what the business asks has become wide enough that it cannot be bridged informally. And the gap is no longer widening at human speed.
The faster the factory, the more load-bearing the delta.
AI is compressing the segment of the value chain that was already best measured. DORA's own research across 2024 and 2025 documents the shape of that compression: as AI adoption rises, nearly every upstream process measure improves while delivery performance, and stability in particular, degrades. The same research observes that AI does not drain the value from software work; it expedites its realization, compressing the time between starting valuable work and finishing it, and freeing capacity. What fills the freed capacity is left open. Capacity aimed at volume produces more deployed, unreleased, unmeasured output, faster. Capacity aimed at impact requires a declared target to aim at, and nothing in the delivery toolchain supplies one.
The arrival of agents sharpens the problem from one of speed to one of context. An enormous amount of organizational knowledge passes through humans implicitly: the guardrails, the routing, the value-context that human workers carry without being asked to articulate it. When an agent takes over a piece of work, what gets lost is precisely the unwritten answer to what the work is for.
RIVER's answer is structural. The release delta makes the value-context explicit: hypothesis, success signal, target cohort, and horizon, declared before exposure. A human team and an agent operating against the same declared delta are bound by the same context, because the context is no longer implicit. Acceleration does not weaken the case for declaration; it is the case. The faster the factory runs, the more load-bearing each declared delta becomes.
What DORA measures, and where the difference now lives.
DORA is the most successful measurement framework in the modern history of software engineering, and RIVER is built to encompass its four metrics, not displace them. DORA measures the commit-to-deploy segment through four metrics, the standard against which any new measurement framework in this space must calibrate itself.
Treating DORA fairly also means describing where its research has gone, because the common shorthand, that DORA stops at deploy, is no longer accurate. DORA's research has moved steadily downstream: its 2024 report engages the attribution problem directly, and its 2025 report adopts the flow of work from idea to customer as a unit of analysis. What survives that expansion is a distinction of posture. DORA reaches downstream as research and diagnosis; it observes outcomes after the fact and correlates them with capabilities. It does not bind a declared artifact to each release before exposure and evaluate the release against it after. That is not a deficiency of DORA; it is the difference between an instrument and an operating discipline, and it is the axis on which RIVER is positioned.
RIVER adopts the DORA metrics as-is for the segment they cover. There is no RIVER metric that replaces a DORA metric; for the commit-to-deploy segment, DORA is RIVER's measurement. What RIVER adds is a per-release operating artifact, and measurement scoped to that artifact, for the segments past deploy.