State of the Art of Platform Engineering • Abby Bangser & Charles Humble • GOTO 2026
Summary
The "State of the Art of Platform Engineering" discussion with Abby Bangser and Charles Humble highlights the discipline's evolution towards self-service internal developer platforms. While understanding the value of centralization for cost savings and compliance is widespread, many organizations struggle with execution, often rehashing centralized operations. An emerging architectural pattern involves internal marketplaces to scale platform building, as observed at KubeCon 2025 and 2026. Key aspects include treating the platform as a product with a clear scope, avoiding "platform facades" created by portals and CI/CD pipelines that lack true self-service and longevity, and recognizing signs of platform decay. The conversation emphasizes making a business case for maintenance by tracking cost and opportunity impacts. Critically, AI is transforming platform engineering by making AI agents first-class consumers, driving the need for API-first, deterministic capabilities and robust guardrails to enable confident AI adoption. The future of platform engineering hinges on achieving compliance and coherency at the scale of AI consumption.
Key takeaway
For AI Architects and Platform Engineers evolving internal developer platforms, prioritize delivering API-first, deterministic capabilities with robust guardrails. This is crucial for enabling trusted, scalable AI agent consumption and ensuring compliance, shifting the platform's core value. Justify platform investments by tracking cost savings and opportunity costs, rather than solely developer experience, to secure necessary funding. Failure to provide these foundational elements will constrain AI adoption and accelerate platform decay.
Key insights
Platform engineering must provide self-service, API-first, deterministic capabilities to enable scalable, compliant AI agent consumption.
Principles
- Centralization with self-service unblocks value streams and ensures compliance.
- Treat a platform as a product with clear scope, including feature deprecation.
- Platform capabilities should be implementation agnostic and fleet managed.
Method
Begin with high collaboration to understand user needs, then facilitate across multiple consumers, progressing to automated on-demand APIs.
In practice
- Identify platform decay by observing development teams "cutting corners" or avoiding friction.
- Design platform APIs to serve both human and AI agent consumers effectively.
Topics
- Platform Engineering
- Internal Developer Platforms
- AI Agents
- API-First Design
- Platform as a Product
- Technical Debt
Best for: AI Engineer, MLOps Engineer, AI Architect
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by GOTO Conferences.