{"id":2879,"date":"2026-10-20T18:05:00","date_gmt":"2026-10-20T18:05:00","guid":{"rendered":"https:\/\/www.kneehospitals.com\/blog\/?p=2879"},"modified":"2026-10-20T18:05:00","modified_gmt":"2026-10-20T18:05:00","slug":"platformops-2026-field-check","status":"publish","type":"post","link":"https:\/\/www.kneehospitals.com\/blog\/platformops-2026-field-check\/","title":{"rendered":"PlatformOps in 2026: A State-of-the-Field Check"},"content":{"rendered":"

There is a moment in every knee clinic waiting room when the conversation turns to running. Somebody has taken it up at fifty, everybody has an opinion, and the honest answer is always the same: running is wonderful for most knees when you build up sensibly, and ruinous when you skip the build-up. That is roughly where the software world sits with PlatformOps right now. Nearly everybody has started. The interesting question \u2014 the one worth your afternoon \u2014 is who built up properly and who is limping. So here is a friendly lap of the field as it stands, with the numbers, the tools, and a few cautionary tales.<\/p>\n

PlatformOps Adoption: Almost Everyone, Not Always Well<\/h2>\n

Start with the headline. By 2025, platform research found roughly nine in ten surveyed organisations were running some form of internal developer platform. That is not a fringe practice anymore; it is the default posture of medium and large engineering organisations. Yet the same research programme that counted the adoption \u2014 DORA, the team behind the industry’s best-known delivery surveys \u2014 also found something awkward: a badly run platform can push both throughput and stability downward. Read that twice. The thing everyone is building can make delivery worse when it is managed like a cost centre instead of a product. Adoption, in other words, was never the hard part. Operating well is, which is exactly the gap PlatformOps exists to close.<\/p>\n

The Tooling Grew Up While Nobody Was Watching<\/h2>\n

Look at the ecosystem’s maturity markers over the last few years. Backstage \u2014 Spotify’s open-source portal framework, and the closest thing the field has to a default \u2014 has been incubating within CNCF since March 2022 and now ships on a monthly cadence, with catalog entities and software templates doing the everyday heavy lifting. Crossplane, which lets teams describe cloud infrastructure through the same control-plane logic, reached graduation status in October 2025, a signal that the infrastructure-layer side of the stack has settled. Around them sits a stable supporting cast: Argo and Flux for GitOps-style delivery, Prometheus and OpenTelemetry for measurement, OPA and Kyverno for policy. None of this is exotic anymore. A team assembling a platform in 2026 is bolting together mature parts, which is precisely why the differentiator has moved from what you install to how you run it.<\/p>\n

PlatformOps Reality Check: Vendor Products Die Too<\/h2>\n

Now the uncomfortable exhibit. AWS quietly ended support for Proton, its managed delivery product, on 7 October 2026. Microsoft has Azure Deployment Environments scheduled to switch off on 22 February 2027. These were not hobby projects; they were offerings from two of the largest platform vendors on the planet, and both are now tombstones. The moral is not to buy nothing \u2014 it is to buy at the interface layer while keeping the core yours. The three-layer architecture that has become the field’s reference model separates user-facing surfaces from the orchestration and policy core, and the core from the providers beneath. Interfaces are replaceable. If your whole platform is a vendor’s interface with nothing of yours underneath it, you have rented a platform, not built one, and the rent review can arrive without warning.<\/p>\n

What Good Looks Like as the Field Matures<\/h2>\n

The organisations pulling ahead share habits that are almost boringly consistent:<\/p>\n