GetDX vs. DevStats
A demo-only DevEx research platform with surveys and performance review tooling from the co-author of the DevEx framework, or a focused diagnostic instrument built on SPACE with public per-dev pricing that auto-configures itself in under two minutes.
DevEx research platform with surveys vs. focused diagnostic intelligence with auto-configuration
GetDX, built by Abi Noda (co-author of the DevEx framework with Nicole Forsgren and Margaret-Anne Storey), pairs developer surveys (DevEx 360), performance review tooling (PerfDB), and a data cloud for custom enterprise dashboards. Powerful if you have a research function and a six-month rollout budget. DevStats is the opposite operating model: 24 reports across SPACE, an AI agent that auto-detects how the team works on connect, and public per-dev pricing — no surveys, no implementation services.
Are you funding a research program, or buying a diagnostic instrument?
GetDX's flagship is DevEx 360 — a survey-driven measurement framework that requires a research-led rollout, custom dashboards built by their team, and a contract you negotiate behind a demo. Powerful if you have the research function to interpret the qualitative data. DevStats's bet is the opposite: analytics-first signals from your existing source systems, with public per-dev pricing and self-serve onboarding. Same DORA research underneath, opposite go-to-market posture. One more thing to weigh: DevStats is bootstrapped and profitable, so the roadmap follows the customer. GetDX is venture-funded (Series A from a16z), so the roadmap follows the round.
Where DevStats genuinely wins
Four honest edges. No vanity metrics, no fabricated tool counts.
24 reports across 6 categories — not three modules you compose with services
DevStats ships 24 reports across Flow, Planning & Sprints, Investment & Allocation, Quality & Reliability, Visibility & Insights, and AI Impact — one clear signal per question. GetDX is structured as three modules you assemble — DevEx 360 surveys, PerfDB performance reviews, and Data Cloud raw exports — plus implementation services to wire them together for your org.
- 24 reports curated for the engineering leader, not three modules to assemble
- Player Dashboard, AI Impact, and Investment Profile in one product
- Squad-first views by default — no custom-dashboard project required
An MCP server and an in-product AI Chat — query your data in natural language
DevStats ships a first-party MCP server so Claude, Cursor, or Copilot can drill into your PRs, issues, and reports through natural-language queries. The in-product AI Chat answers the same questions without leaving DevStats. GetDX tracks AI tooling adoption (GitHub Copilot, etc.) at the survey and metric level, but ships no MCP server, no in-product AI assistant, and no natural-language query interface across your engineering data.
- First-party MCP server — GetDX has none
- In-product AI Chat with squad-scoped context
- AI Impact reports across Copilot, Cursor, Claude Code, Amazon Q, Cody, and Windsurf
Public per-dev pricing vs. demo-only enterprise contracts
DevStats lists every tier on the pricing page: $15 Starter, $27 Pro, custom Enterprise (VPC, no per-seat billing). For a 40-developer team, DevStats Pro runs about $13,000 a year. GetDX does not publish pricing. Every prospect goes through a demo, a discovery call, and a multi-week sales process to find out the number — typically a six-figure annual contract sized for the kind of mid-to-large enterprise GetDX targets.
- Public per-dev pricing — no demo required to see a number
- 14-day self-serve trial, no credit card required
- Bootstrapped and profitable — vendor optimising for renewals, not the next round
An AI agent configures your team on setup — no taxonomy workshop, no demo loop
DevStats connects in under two minutes with no code changes. An AI agent then inspects your Git and issue-tracker history to auto-detect how your team actually works — squads, services, sprint cadence, branch conventions — so you skip the configuration phase entirely. Historical backfill runs in the background within normal API rate limits. GetDX is a multi-week implementation: DevEx 360 surveys are designed and rolled out across the org, PerfDB workflows are configured, and Data Cloud dashboards are built by GetDX's services team to fit your data shape — typically a six-week to multi-month engagement with a Customer Success counterpart.
- AI agent auto-detects squads, services, sprint cadence, and branch conventions
- Self-serve trial with no sales call required to see your numbers
- No surveys to design, no custom dashboards to commission
Who each platform fits
The short version: pick the one whose ideal customer looks most like you.
- Large enterprises with 500+ developers and a research function to interpret qualitative DevEx survey data
- Engineering organizations that have already standardised on the DevEx framework (Feedback Loops, Cognitive Load, Flow State) as their measurement language
- Companies that need a dedicated performance review tooling layer (PerfDB) alongside engineering metrics
- Buyers comfortable with multi-week services-led implementation and a Customer Success engagement to roll the platform out
- Teams that want raw data exports to Snowflake or BigQuery and a custom dashboard project, not 24 pre-built reports
- Procurement teams that prefer demo-led negotiations over published per-dev pricing
- Growth-stage SaaS with 15+ developers (sweet spot 30 to 50) that want enterprise-grade insights without a multi-week implementation
- VP Engineering and CTO buyers who need to make engineering legible to the CEO and board this quarter, not next year
- Engineering managers running squads day-to-day who want one clear signal per question, not three modules and a survey program
- Teams committed to SPACE and processes-not-people as a measurement philosophy
- Buyers who prefer published per-dev pricing on the website over demo-led custom contracts
- Companies that want a first-party MCP server and in-product AI Chat — GetDX has neither
- Leaders who want DORA Elite/High/Medium/Low auto-rated against the Accelerate research, not raw benchmarks
- Buyers who want a sustainable, profitable vendor behind their engineering intelligence stack, not a venture-funded exit trajectory
Full feature comparison of GetDX and DevStats
Side by side across what most engineering leaders actually use day-to-day. Pricing rows are at the top because they are usually the deciding factor, and rows where DevStats has a clear edge are highlighted.
| Feature | DevStats | GetDX |
|---|---|---|
| Pricing | ||
| Starting price (per contributor, billed annually) | $15/mo (Starter) | Demo required · custom contract |
| Mid-tier price (per contributor, billed annually) | $27/mo (Pro) | Demo required · custom contract |
| Enterprise price (per contributor, billed annually) | Custom (VPC, no per-seat) | Demo required · custom contract |
| Public pricing page | ||
| Free tier (no card required) | 14-day trial | |
| Self-serve onboarding (no sales call) | ||
| Time to first insight | Under 2 minutes | Multi-week implementation |
| Business model | Bootstrapped and profitable | Series A (a16z, 2024) |
| Report breadth | ||
| Reports shipped in the product | 24 reports across 6 categories | DevEx 360 + PerfDB + Data Cloud (3 modules) |
| Squad-scoped contribution view (Player Dashboard) | Partial | |
| Investment Profile / work-type allocation | Custom dashboards via Data Cloud | |
| DORA & delivery metrics | ||
| All four DORA metrics | ||
| DORA thresholds from research (Accelerate) | Benchmarks + trends, not auto-rated | |
| Elite / High / Medium / Low performer rating | ||
| PR Cycle Time with 5-stage breakdown (Coding, Pickup, Review, Merge, Deploy) | ||
| Throughput | ||
| Planning accuracy / sprint tracking | Partial | |
| Aging PRs and WIP overload alerts | Partial | |
| Code review & developer experience | ||
| Review turnaround time | ||
| Reviewer load balancing | Partial | |
| Flags oversized PRs and high-risk code | Partial | |
| SPACE framework foundation | ||
| DevEx framework (Feedback Loops, Cognitive Load, Flow State) | Partial | |
| Developer surveys (DevEx 360) | ||
| Performance review tooling (PerfDB) | ||
| No individual stack ranking by design | ||
| AI & AI-native analytics | ||
| First-party MCP server | ||
| In-product AI Chat | ||
| AI Impact reports (AI-assisted PR %, velocity, quality, review time) | Pro and Enterprise | AI tooling adoption via surveys + metrics |
| GitHub Copilot | ||
| Cursor | Partial | |
| Claude Code | Partial | |
| Windsurf | ||
| Setup & time to value | ||
| Setup time (connect & configure) | Under 2 minutes, no code changes | Multi-week services-led rollout |
| AI agent auto-detects squads, services, sprint cadence, and branch conventions | ||
| Customer Success implementation engagement required | ||
| Historical data pulled on connect | 1 year (Starter) · 3 years (Pro) | Configurable in contract |
| First full reports after historical backfill | Hours (API-bound) | Weeks (services-led) |
| Investment & allocation | ||
| Four-bucket work categorization (New Things, Improving, KTLO, Productivity) | Partial | |
| Software cost capitalization reporting | Not a core focus | Custom dashboards via Data Cloud |
| Effort dashboard / people allocation | Custom dashboards | |
| Custom metrics | Enterprise tier | Data Cloud (Snowflake/BigQuery export) |
| Integrations | ||
| Git (GitHub, GitLab, Bitbucket, Azure DevOps) | GitHub, GitLab, Bitbucket | |
| Issue tracker (Jira, Linear, Asana, ClickUp, Azure DevOps) | Jira, Linear | |
| Incident management (PagerDuty, OpsGenie, Datadog, incident.io) | Partial | |
| First-class Slack integration | ||
| Microsoft Teams integration | Partial | |
| Raw data export to Snowflake / BigQuery | ||
| Support & compliance | ||
| Dedicated Slack channel for support | Pro plan | All paid plans |
| Customer Success Manager | All plans | All paid plans |
| SOC 2 Type II | ||
| SAML SSO | Enterprise | Enterprise |
| Self-hosted / VPC deployment | Enterprise (VPC, no per-seat billing) | SaaS only |
| Geography & language | ||
| Primary market | US · Brazil · growth-stage SaaS | US · large enterprise (500+ devs) |
| Portuguese-language support | ||
DevStats is built for
Six profiles where DevStats goes from useful to obvious.
Growth-stage SaaS that wants enterprise insight without a six-figure custom contract
Series A through Series C SaaS with more than 15 developers (sweet spot 30 to 50) that has outgrown gut-feel management but cannot justify a $25K to $100K enterprise platform. DevStats Pro is roughly $13,000 a year for 40 developers, listed publicly on the pricing page. GetDX does not publish pricing — every prospect goes through a demo and a multi-week sales motion before seeing a number, and contracts are sized for the kind of large enterprise that has the research budget to absorb implementation services on top of seats.
Engineering managers who do not want to run a research-led implementation
GetDX is a multi-week to multi-month rollout: DevEx 360 surveys are designed and rolled out across the org, PerfDB performance review workflows are configured, and Data Cloud dashboards are built by GetDX's services team to fit your data shape. DevStats takes the opposite approach: connect a repo and issue tracker in under two minutes, an AI agent auto-detects how the team works from Git and issue history, and you skip the configuration phase entirely.
Teams that want a first-party MCP server and in-product AI Chat
DevStats ships both: a first-party MCP server so Claude, Cursor, or Copilot can drill into your PRs, issues, and reports through natural-language queries, and an in-product AI Chat that answers the same questions without leaving DevStats. GetDX has neither — its AI surface is limited to tracking adoption of tools like GitHub Copilot through surveys and dashboard panels.
Teams that want analytics-only signal, not a survey program
GetDX's flagship is DevEx 360, a developer survey program that requires careful design, an org-wide rollout, and a quarterly cadence to be useful. DevStats deliberately ships zero surveys — every signal is derived from your existing Git, issue tracker, CI, and incident systems. Same DORA and SPACE research underneath, no response-rate dependency, no quarterly survey fatigue.
Leaders who want instant context on the numbers
DevStats applies the DORA/SPACE research thresholds from Accelerate automatically, so every dashboard opens with an Elite/High/Medium/Low read. The board conversation starts from shared research, not from raw benchmark trendlines you have to interpret yourself.
Regulated orgs that need data in their own cloud
DevStats Enterprise can be deployed into your own VPC with no per-seat billing — a flat agreement that fits security reviews and lets you keep Git, issue, and PR data inside your perimeter. Pair it with SOC 2 Type II, ISO 27001, GDPR, and SAML SSO and procurement stops blocking the rollout.
Common questions about comparing GetDX and DevStats
GetDX does not publish pricing. Every prospect goes through a demo and a multi-week sales motion to land a custom annual contract, and contracts are sized for large enterprises with research budgets and Customer Success engagements. DevStats publishes per-dev pricing on its website: $15 Starter, $27 Pro, custom Enterprise (VPC, no per-seat billing). For a 40-developer team, DevStats Pro is about $13,000 a year, fully transparent before any sales conversation.
Yes. DevStats connects in under two minutes with no code changes; an AI agent then auto-detects your squads, services, sprint cadence, and branch conventions from Git and issue-tracker history. GetDX is an implementation engagement: DevEx 360 surveys are designed and rolled out, PerfDB performance review workflows are configured, and Data Cloud dashboards are built by GetDX's services team — typically a six-week to multi-month rollout with a Customer Success counterpart.
No. DevStats AI Impact reports track AI-assisted PRs, velocity impact, quality scores, and review time across GitHub Copilot, Cursor, Claude Code, Amazon Q, Cody, and Windsurf on Pro and Enterprise — flat pricing, no metering. DevStats also ships a first-party MCP server and an in-product AI Chat for natural-language queries. GetDX measures AI tooling adoption (Copilot, etc.) through surveys and dashboard panels, but offers no MCP server and no in-product AI assistant.
No. DevStats deliberately does not run developer surveys. The bet is that signals derived from your existing source systems (PR cycle time, throughput, planning accuracy, aging issues, AI-assisted PR percentage) are easier to act on than survey scores that depend on response rates, reviewer fatigue, and a quarterly cadence. If qualitative survey data is a hard requirement, GetDX is a better fit. If you want analytics-only, no-survey signal from the data you already have, DevStats is.
GetDX has a dedicated module for performance reviews — PerfDB — built around individual contributions and review cycles. DevStats deliberately does not. The DevStats philosophy, anchored to SPACE, is processes-not-people: squad-first views, no individual stack ranking, no review tooling. If you want platform-level performance review automation, GetDX is the better fit. If you want your engineering metrics platform to stay out of perf-review territory, DevStats is.
GetDX is built for that profile — most named customers are 500-10,000+ developers (Etsy, Pfizer, Block, BlackRock, eBay, Vercel) with a research function and a Customer Success engagement budget. DevStats's sweet spot is growth-stage SaaS (15-50 developers) and the smallest enterprises that do not need a six-month implementation to see value. If you have a research team and a multi-week rollout budget, GetDX. If you want plug-and-play insight inside two minutes, DevStats.
Yes — but the comparison is asymmetric. DevStats offers a 14-day self-serve trial, so you can connect a repo and issue tracker on day one and see your numbers in two minutes. GetDX requires a demo, a discovery call, and a contract before any data flows. The most realistic comparison is: run a DevStats trial in parallel with a GetDX demo, and decide whether the survey + services depth justifies the price and timeline difference.
DevStats vs. the others
GetDX is the most direct alternative on the survey/research-platform side, but it is not the only platform engineering leaders weigh against DevStats. The other comparisons buyers usually run are below.