GetDX (DX) is a highly respected developer intelligence tool, and has recently become part of the Atlassian platform. Its research-backed approach combines DORA, SPACE, DevEx, surveys, benchmarks, and engineering workflow data to help leaders understand how software teams work.
That depth is useful, but it also defines the boundary. Once AI measurement moves beyond engineering, GetDX stops short. Engineers often do work outside the boundaries of engineering. And Finance, HR, operations, and executive teams need to know where AI is being used, what it costs, whether people are using it well, and what the business is getting back, across the full organization. For these use cases, Larridin is the best alternative.
This guide compares GetDX with four alternatives: Larridin, Jellyfish, Faros AI, and Worklytics.
|
Larridin — Enterprise AI Measurement Beyond Engineering |
|
|
Larridin is the strongest GetDX alternative for comprehensive AI measurement across the organization. GetDX helps leaders understand developer experience, engineering productivity, and AI-assisted software work. Larridin provides an enterprise-wide view: who’s using AI, what it costs, how well people and agents are using it, and what value the business gets back. |
|
|
✅ Best For CIOs, CFOs, CHROs, and AI transformation leaders who need enterprise-wide AI ROI across teams, tools, agents, workflows, and outcomes. |
⚠️ Key Limitation Larridin is broader than GetDX, but it’s not a replacement for GetDX’s specialized developer experience surveys, research-backed engineering benchmarks, or DevEx methodology. |
|
Jellyfish — Engineering Intelligence + R&D Investment Analytics |
|
|
Jellyfish is a strong GetDX alternative when engineering leaders need R&D investment visibility and capacity planning more than developer experience depth. It helps CTOs and VPs of Engineering to understand engineering allocation, software delivery trends, team capacity, and AI coding tool adoption. |
|
|
✅ Best For CTOs and engineering leaders who need SDLC analytics, R&D investment visibility, capacity planning, and AI coding tool adoption data. |
⚠️ Key Limitation Jellyfish is focused on engineering more broadly. It doesn’t have the developer experience depth, academic methodology, or integration with the Atlassian environment offered by GetDX. |
|
Faros AI — Engineering Productivity with Strong Compliance Credentials |
|
|
Faros AI is a strong GetDX alternative when compliance-ready software delivery intelligence is the priority. It focuses on DORA metrics, SDLC analytics, AI adoption tracking, and engineering productivity for teams that need strong security and governance credentials. |
|
|
✅ Best For Engineering teams in regulated industries where compliance certifications (SOC 2, ISO 27001, GDPR) are a hard requirement. |
⚠️ Key Limitation Faros AI is built for engineering productivity and software delivery intelligence. Its methodology is less research-grounded than GetDX, and it doesn’t include developer satisfaction surveys. |
|
Worklytics — People Analytics + AI Adoption Benchmarks |
|
|
Worklytics is a GetDX alternative or complement when the workforce question extends beyond engineering, but is not as strong for the engineering team. It helps HR and people analytics teams understand AI adoption across teams, roles, and peer benchmarks. |
|
|
✅ Best For HR and people analytics teams that need workforce analytics, AI adoption benchmarks, and peer comparison data. |
⚠️ Key Limitation Worklytics is built for people analytics and adoption benchmarks, not developer experience measurement, DORA/SPACE-style engineering analytics, or AI code metrics. |
|
Feature |
Larridin |
GetDX (DX) |
|---|---|---|
|
Enterprise-wide coverage |
✅ Yes — all departments |
❌ Engineering only |
|
Developer experience surveys |
⚠️ Not-developer specific |
✅ Yes — specialized |
|
DORA / SPACE framework support |
⚠️ Via integrations |
✅ Yes — core |
|
AI code metrics |
✅ Yes |
✅ Yes — deep |
|
Token spend tracking |
✅ Yes |
⚠️ Partial |
|
Non-engineering workflow tracking |
✅ Browser and desktop coverage |
❌ No |
|
Industry benchmarks |
❌ Not currently |
✅ Yes |
|
AI proficiency measurement |
✅ Yes |
⚠️ Limited |
|
Shadow AI discovery |
✅ Yes |
❌ No |
|
CFO / CHRO reporting |
✅ Yes |
⚠️ CTO focused |
|
In Our Tests... In our enterprise AI audits, engineering teams often had strong developer productivity and AI coding data. The gap showed up when AI measurement moved outside the dev org, where leaders still needed visibility into usage, spend, proficiency, governance, and business outcomes. That is where Larridin pulls ahead. GetDX can help engineering leaders understand developer experience and AI-assisted software work. Larridin helps developers with work they do outside the engineering tools environment and follows AI across all departments, tools, users, agents, workflows, spend, proficiency, and outcomes. |
GetDX stands out for research-backed developer intelligence. It combines DORA, SPACE, DevEx, developer surveys, benchmarks, workflow analysis, and engineering system data to help teams understand developer experience and productivity.
GetDX is scoped to engineering. It stops short of measuring AI usage, spend, proficiency, governance, and business impact across non-engineering-specific work and across departments such as sales, marketing, HR, finance, and operations.
Yes; both pull data from Git, Jira, and CI/CD to give engineering leaders visibility into delivery and productivity, but they're optimized for different buyers.
Use Jellyfish when finance/executive stakeholders and cost reporting drive the buying decision. Use GetDX when developer sentiment and DevEx benchmarking matter most. Neither currently does fine-grained, line-level attribution of AI-generated code to productivity/quality outcomes; that's a known gap in both.
Faros AI and GetDX overlap in engineering analytics, DORA metrics, and software delivery intelligence. Faros AI is stronger when compliance credentials are a major buying requirement. GetDX is stronger for Atlassian environment integration and for developer experience measurement, surveys, benchmarks, and research-backed productivity analysis.
Larridin is the best fit when leaders need enterprise-wide AI ROI tracking across technical and non-technical teams. Jellyfish and Faros AI are stronger for engineering analytics, while Worklytics is stronger for broad workforce adoption benchmarks.
GetDX is part of the Atlassian environment, and it’s a strong choice when engineering leaders need developer experience measurement, AI code analytics, and research-backed productivity insights.
Choose Larridin, either alongside or instead of GetDX, when the bigger problem is enterprise AI accountability: what AI costs, who is using it, how well they are using it, and what the business is getting back across every department.
