Chris Aniszczyk — CTO of the CNCF — used the KubeCon Europe 2026 Press Conference to unveil the Q1 2026 CNCF Technology Radar, focused entirely on Platform Engineering. The headline number: 28% of organizations now have a dedicated platform engineering team responsible for internal platforms.
That number might seem modest, but it represents a tipping point. Platform engineering has moved from conference buzzword to funded organizational capability.
The 28% Threshold
Having 28% of organizations with dedicated platform teams means:
- Headcount is being allocated — These are not side projects. Companies are hiring platform engineers as a distinct role.
- Budget exists — Dedicated teams mean dedicated budgets for tooling, infrastructure, and developer experience.
- Measurement is happening — Teams are tracking developer productivity, deployment frequency, and platform adoption metrics.
For the 72% without dedicated teams, the question is not whether to invest in platform engineering — it is how far behind you are falling.
Platform Engineering Tools Maturing for AI
Aniszczyk highlighted that platform engineering tools are maturing specifically to support AI-driven infrastructure. This is the convergence that has been building for two years:
- Internal Developer Platforms (IDPs) need to support GPU workload provisioning
- Golden paths must include AI/ML pipeline templates
- Self-service portals need inference endpoint deployment workflows
- Cost dashboards must attribute GPU spend per team and project
The Technology Radar evaluates tools across four adoption levels: Adopt, Trial, Assess, and Hold. While the full report details are available separately, the press conference highlighted several key trends.
Backstage Documentary Premiere
In a unique move, the CNCF announced the premiere of the Backstage Documentary at KubeCon:
- Date: March 25, 2026 at 18:15
- Location: Forum
Backstage, Spotify’s open-source developer portal, has become the de facto standard for internal developer portals. A documentary signals that the project has enough history, adoption stories, and impact to warrant long-form storytelling.
For platform teams evaluating developer portals, Backstage’s trajectory from Spotify internal tool to CNCF graduated project to documentary subject tells you everything about its staying power.
Gateway API Moves to Production
The Technology Radar confirms the transition to Gateway API for production use. This is significant because Gateway API replaces the aging Ingress resource with a more expressive, role-oriented model:
- Infrastructure providers define GatewayClass resources
- Platform teams manage Gateway resources
- Developers create HTTPRoute resources
This separation of concerns maps perfectly to the platform engineering model. Gateway API gives platform teams control over infrastructure while letting developers define their own routing rules within safe boundaries.
For AI workloads specifically, Gateway API is critical for:
- Inference endpoint routing — Route traffic to different model versions based on headers or weights
- A/B testing — Split traffic between model variants for evaluation
- Rate limiting — Enforce per-tenant token limits at the gateway level
- Authentication — Centralize API key validation before requests reach inference pods
Kubernetes 1.36 Preview
Aniszczyk also previewed Kubernetes 1.36, expected in April 2026. While the full feature list was not disclosed, the mention during the platform engineering segment suggests features aligned with platform team needs — likely including DRA improvements, scheduling enhancements, and further Gateway API integrations.
Clearing Tech Debt for AI Innovation
A recurring theme in Aniszczyk’s presentation was that organizations must clear tech debt before they can innovate with AI. Platform engineering is the mechanism for this:
- Standardize on Gateway API instead of maintaining custom Ingress controllers
- Adopt Kyverno policies instead of manual compliance checks
- Implement golden paths instead of tribal knowledge
- Build self-service instead of ticket-based provisioning
The organizations deploying AI successfully are the ones that did this foundational work first.
What to Do With This Information
- Read the full Technology Radar report — It provides specific tool recommendations at each adoption level.
- Evaluate your platform maturity — If you do not have a dedicated platform team, start building the case with the 28% benchmark.
- Plan the Gateway API migration — If you are still on Ingress, the Technology Radar confirms it is time to move.
- Watch the Backstage documentary — Understanding the origin story helps you evaluate whether Backstage fits your organization.
Platform engineering is not a trend. It is the operational model that enables everything else — including AI at scale.
