Amtarc Logo
0%
Home/Intelligence Reports

The State of Platform Engineering 2025

Annual analysis of 42 enterprise environments — which IDP patterns drive elite DORA metrics, and which don't.

layers
12 Pages · Q1 2025
Free · Open Access
Platform Engineering · Q1 2025

The benchmark every engineering leader needed.

This report analyzes anonymized data from 42 enterprise engagements to understand which internal developer platform patterns actually correlate with elite software delivery performance.

12x
higher deploy frequency in top-performing orgs
3x
Backstage adoption growth in 12 months
64%
reduction in MTTR with GitOps adoption
Read the Report arrow_downward
Executive Summary

The Divergence is Accelerating

Platform engineering is no longer an emerging practice — it is the primary differentiator between elite and median software delivery organizations. The 2025 benchmark, drawn from 42 internal platform deployments analyzed during research, reveals a widening performance gap that is directly attributable to internal developer platform maturity.

Elite performers — the top 20% by DORA metrics — are deploying 12 times more frequently than their low-performing counterparts, recovering from failures 96 times faster, and experiencing change failure rates five times lower. The common thread: all of them have invested in a self-service internal developer platform with opinionated golden paths.

Equally striking is what doesn't work. Organizations that built bespoke tooling without developer experience as a first principle consistently showed worse metrics than those using no platform at all. The problem is not whether to build a platform — it is how.

Key Findings

What the Data Shows

rocket_launch
12x
Deploy Frequency Gap

Elite vs. low performers in deploy frequency. The gap is widening as platforms mature.

healing
96x
Recovery Time Gap

Mean time to recovery: elite orgs recover in minutes; low performers take days. GitOps is the primary driver.

trending_up
3x
Backstage Adoption

Backstage adoption tripled in 12 months. It is now the de facto standard for engineering portals.

check_circle
64%
MTTR Reduction

Organizations adopting GitOps (ArgoCD/Flux) reduced mean time to recovery by 64% vs. script-based deployments.

Section 1

The Golden Path Paradox

"Golden paths" — opinionated, pre-built routes to production for standard service archetypes — are the single highest-leverage investment observed. Organizations with 3 or more mature golden paths deploy 6.2 times more frequently than those without them, and report significantly higher developer satisfaction scores.

The paradox: 67% of organizations attempting to build golden paths abandon them within 6 months. The failure mode is consistent — they begin with the platform team's perspective rather than the developer's. Golden paths that don't abstract complexity away from the developer's daily workflow are more cognitive burden, not less.

Section 2

The GitOps Inflection Point

GitOps adoption has crossed the majority threshold in this study — 54% of organizations report production GitOps deployments, up from 31% in 2023. ArgoCD commands a 71% market share among GitOps adopters.

The performance delta is unambiguous. GitOps adopters show a median MTTR of 8 minutes vs. 52 minutes for script-based deployments; a change failure rate of 4.2% vs. 11.7%; and report that developers spend 40% less time on deployment-related activities — freeing engineering capacity for product development.

Section 3

Platform Team Anti-Patterns

Several common patterns consistently correlated with worse outcomes. These are the mistakes organizations make after deciding to invest in platform engineering but before understanding what good looks like.

warning

Building a portal before solving the workflow

Backstage is a surface, not a solution. Organizations that deploy Backstage without first defining their golden paths and automation create a catalog of complexity, not simplicity.

warning

Treating the platform as an internal product with no users

Platform teams that don't measure developer satisfaction and adoption rates build platforms for themselves. The best platforms are built by teams that treat developers as their customers — with NPS surveys, office hours, and feedback loops.

warning

Enforcing governance without enabling compliance

Policy-as-code tools like OPA can either enable developers (by automating compliance checks in CI) or block them (by requiring manual tickets). The difference is design intent.

Recommendations

Actions for Engineering Leaders

01

Instrument DORA metrics before building anything

You need a baseline. Without it, you cannot measure the impact of platform investments. Deploy a DORA dashboard in your first 30 days.

02

Define your service archetypes first

Map every service type your organization runs (API, worker, batch job, frontend). Your golden paths should cover 80% of new services. Start with the most common.

03

Adopt Backstage as your portal surface for teams > 50 engineers

The ecosystem has matured. Backstage's plugin catalog means you are not building from scratch. Assign a dedicated platform DX engineer to maintain it.

04

Migrate to GitOps before adding features

If you are not using GitOps, the ROI on that investment is higher than any feature you could add to your platform. ArgoCD with GitOps significantly reduces MTTR and cognitive load.

05

Measure developer satisfaction quarterly

Adopt the SPACE framework. Survey your developers quarterly. Platform teams that measure and act on developer satisfaction improve DORA metrics 2.4x faster than those that don't.

Methodology

Data Collection

This report is based on anonymized telemetry and audit data from 42 enterprise platform engagements conducted in 2024. These organizations span technology maturity levels, and provided direct observable visibility into their DORA metrics before and after IDP adoption. Elite performance was defined as top-quartile on all four DORA metrics simultaneously.

42
Engagements Analyzed
5
Core Industries
Q4 2024
Observation Window