Compare
Arrio vs DX
DX and Arrio both put numbers on software development, and they measure different things for different people. DX measures the developer experience, and asks developers directly. Arrio measures what the investment produced, and asks the code. Here is how they compare.
DX
Developer experience, measured from the inside.
A developer experience and intelligence platform for engineering leaders and platform teams. Its Developer Experience Index combines system data with developer self-reporting across 14 drivers of engineering efficiency, and its AI framework tracks utilisation, impact and cost. Built to remove friction for developers.
Arrio
Independent measurement, from the outside.
An independent read of what the software investment produces, for the people who fund it. It reads the work itself from the codebases, grounds it in cost, and reports to the CEO, CFO and CIO in business terms, including whether the AI investment is paying off. Built to govern the spend.
Side by side
Where they differ
| DX | Arrio | |
|---|---|---|
| Who it is built for | Engineering leaders and platform teams working on developer productivity and experience. | The budget owner. CEOs, CFOs and CIOs who fund software and answer for the return. |
| What it measures | Developer experience and efficiency: friction, sentiment, time saved, and a composite index across 14 drivers. | What the investment produces: output and value across teams and vendors, set against cost. |
| Where the data comes from | System data combined with perceptual and behavioural insight reported by developers themselves. DX states plainly that it captures self-reported input, rather than only analysing activity in tools. | The work itself, read from the codebases, plus cost. No surveys, no self-reporting, no time-tracking. |
| What the number means | How development feels and flows for the people doing it, which is the right input for improving their working conditions. | What the organisation produced for what it spent, which is the right input for governing the investment. |
| Relationship to the teams measured | A platform the engineering organisation adopts and runs for itself, with its own developers as respondents. | An independent outside read. Does not sell the tools it measures, does not host your code, no incentive to inflate. |
| Commercial model | Enterprise SaaS subscription. | Not published. Speak to us about pricing and services. |
Comparison by design and audience, based on each company’s publicly stated purpose. Not a feature-by-feature ranking.
Would you like to know more about our pricing and services? Speak to our founders.
It is not either / or
Ask developers how the work feels. Ask the code what the work produced.
Developer experience is worth measuring and worth improving, and self-reported data is the honest way to capture how work feels. It is the wrong instrument for a different question: what the organisation got for the money. Self-reporting cannot answer that, because the people reporting are the people being funded. Many organisations will want both, one to improve the work and one to govern the spend. Understand the wider picture in measuring software development.
What is the difference between Arrio and DX?
DX measures the developer experience: how development feels and flows for the engineers doing it, combining system data with what developers report about their own work. Arrio measures what the software investment produced, read from the codebases and set against cost, and reports it to the people who fund it. One improves the conditions of the work. The other accounts for the value of the work.
Is self-reported data a problem?
Not at all for the question DX is answering. If you want to know where developers hit friction, the most reliable source is the developers. It becomes the wrong instrument only when the question changes to what the investment returned, because then the people supplying the data are the people whose budget is under review. That is not a criticism of anyone’s honesty; it is why independent measurement exists as a separate discipline.
DX also measures AI impact. How is that different?
DX measures AI utilisation, time saved and developer sentiment, which tells you how the tools are landing with the team. Arrio measures the AI-built share of the work against what that work delivered, which tells leadership whether the AI spend is producing value. DX’s own published research makes the case for the second question existing: it found 26.9% of production code AI-authored while productivity gains plateaued at around 10% (DX, 2026).
Can we use both?
Yes, and there is no conflict. DX helps you make development better for the people doing it. Arrio tells the budget owner what that development produced. They draw on different data and answer to different people.
Sources
- DX, 2026 Publicly stated product positioning: the Developer Experience Index is a composite of 14 drivers, and DX describes itself as capturing perceptual and behavioural insight self-reported by developers rather than only analysing tool activity. Its 2026 survey of 121,000 developers across 450+ companies reports 26.9% of production code AI-authored against a productivity plateau of about 10%.
- Company positioning, 2026 Comparison is by design and audience, based on each company’s publicly stated purpose. Not a feature-by-feature ranking.
Measure how the work feels. Then measure what it produced.