Navigara vs DX (Atlassian): baseline data or developer surveys

DX asks your engineers how the work feels, combines the answers with tool data, and turns the result into an index. Navigara reads the repository, scores what was merged, and compares the current quarter with the same team’s pre-AI year. Both are legitimate instruments. They read from different places, so they fail in different places. DX depends on survey participation. Navigara depends on the commit history already sitting in Git.

What DX measures

The headline number is the Developer Experience Index. DX describes DXI as “a composite score of 14 key drivers of engineering efficiency” that “combines data from tools and employee feedback.” The formula itself is not published.

Feedback catches what telemetry misses. Flaky local environments, a review culture that leaves people waiting, the slow tax of a build nobody has owned for a year. None of that shows up cleanly in a merge record, and all of it costs throughput.

The survey dependency is the tradeoff. An index built partly on feedback moves when participation moves, and it moves with the mood of the quarter. Two quarters of DXI compare cleanly when the same people answered under similar conditions.

On AI cost, DX goes further than most of the category. Its AI cost management report breaks down spend by “team, group, contributor, attribute, or AI tool,” counts input, output, cache-write, and cache-read tokens, and reports an estimated cost per merged PR.

DX also publishes one of the clearest lines in the category on individual use: “Never tie throughput metrics to individual performance.” The same product reports token spend at contributor level. Both are DX’s own words and features. The distance between them is where a buyer’s own governance policy has to do the work.

Ownership changes the buying decision. Atlassian agreed to acquire DX on 18 September 2025 for $1 billion in cash and restricted stock, and completed the deal on 10 November 2025. DX’s announcement committed to “continued investment in third-party integrations, so organizations can unlock the full value of DX regardless of whether they use Atlassian products.” A procurement review should read DX as an Atlassian product.

What Navigara measures

Navigara reads the repository and scores each merged change.

Engineering Throughput Value (ETV) sorts each merged commit into one of five categories (features, maintenance, tests, docs, and fixes) and sums them with equal weights. Three lines that fix a production bug and three lines that bump a dependency land in different categories and score as different work.

The comparison point is the team’s own history. Connect your repositories, and Navigara “reads back through years of commits,” so the current quarter aligns with the pre-AI year from the same codebase. Nobody fills in a form.

The Measure tier includes per-developer and per-team breakdowns. Navigara’s docs say individual scores “should not be read as a complete performance picture when supporting roles are present,” and point to the team aggregate as the place a supporting engineer’s contribution shows up.

On AI cost, the Pro tier reports “AI ROI: capacity added vs. spend.”

Side by side

Where the two overlap

Both report at team level. Both get bought by an engineering leader who has been asked a question from outside engineering. Both now report AI costs, and they pair them with different evidence: DX with adoption and developer feedback; Navigara with the change in scored throughput since the pre-AI year.

Which one fits your org

DX fits an org that wants to find and fix friction in how engineers work, has enough trust to elicit candid survey responses, and is comfortable within the Atlassian ecosystem. If the question is “what is slowing my engineers down,” feedback is the right sensor, because engineers feel friction before any dashboard shows it.

Navigara fits an org of roughly 20 to 100 engineers that adopted AI tooling in the last three years and needs a defensible number on whether throughput has moved. The repository history is the only required input, so the answer does not wait on a survey round.

If the question you keep getting asked is the second one, connect a repository and Navigara reads back to your pre-AI year.

Both are sane configurations above roughly 300 engineers. Feedback says where the friction is. A scored baseline says whether the last two years of tooling spend changed what ships.

What neither one sees

Navigara scores “only merged commits on connected repositories.” Its docs list what that leaves out: code review, incident response, mentorship, and planning, the work that never lands as a commit. DX’s feedback reaches some of that work and carries the mirror-image limit. A team can feel unblocked and productive during a quarter in which it shipped very little.

That judgment stays with the engineering leader, which is roughly where it belongs.

Talk to us if you want the baseline comparison run against your own history.