Platform engineering is not a one-size-fits-all approach. It has evolved as a response to increasing complexities in software development and deployment and is a methodology for scaling DevOps. DevOps was originally a grass roots movement that grew within the community from 2009 onwards and aimed to reduce friction between developers and operators with the "you build it, you run it" philosophy.
However, as organizations scaled, this model placed an overwhelming burden on development teams.
Platform engineering emerged to address this challenge by establishing platform teams that provide self-service capabilities, tools, and services to application teams. These internal platforms empower developers to build and deliver value more efficiently by reducing cognitive load and operational toil.
Beginning a Platform Engineering Initiative
For leaders considering where to begin with platform engineering, a good starting point is identifying the biggest pain points within an organization. One suggestion is analyzing internal ticketing systems to pinpoint areas of recurring toil and delay. For example, if development teams frequently experience delays due to lengthy provisioning of development environments, a platform team could introduce "development environments-as-a-service" to enable rapid self-service deployments.
Another useful framework for guiding a platform engineering approach is the Platform Engineering Maturity Model, published by the CNCF and contributed to by industry experts within the platform engineering community. This model provides a structured guide to evaluating and advancing platform engineering practices in a way that maximizes organizational impact.
The Value of Internal Developer Platform (IDP) Reference Architectures
Reference architectures can be valuable in demystifying platform engineering terminology and tooling. One of the most straightforward references is the Gartner Diagram of Platform Engineering, which clarifies the role of internal platforms. Additionally, Daniel Bryant’s work on Platform Orchestrators: The Missing Middle of Internal Developer Platforms offers valuable distinctions between Internal Developer Platforms (IDP) and Internal Developer Portals (also IDP).
Platform Engineering Success Stories
One compelling case study of successful platform engineering is from NatWest Bank, which was presented at the Open Source Finance Forum in London in 2024. Chris Plank shared how NatWest aimed to simplify development processes through a self-service internal platform. Key elements of their success included:
Self-service and on-demand – creating a platform that provides on-demand access to the tools and services developers, saving time
Democratization of platform capabilities – allowing multiple teams to contribute and manage services and tools, as well as aspects such as security and compliance
Reduction of cognitive load – implementing “golden paths” to guide developers through best practices.
Measuring Platform Engineering Success
The impact of platform engineering should be assessed using relevant frameworks tailored to an organization’s goals. Commonly referenced models include:
DORA Metrics (Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Time to Restore Service)
SPACE Framework (Satisfaction, Performance, Activity, Communication, and Efficiency)
CORE 4 Framework (introduced more recently as a refined set of engineering effectiveness measures)
However, it is crucial to avoid Goodhart’s Law, which states: "When a measure becomes a target, it ceases to be a good measure." Metrics should be selected based on their ability to drive meaningful improvements rather than as arbitrary targets.
The Future of Platform Engineering: Hype vs. Reality
Platform engineering, much like DevOps before it, is at risk of being misunderstood or misapplied. While many organizations successfully implement platform engineering to achieve significant operational efficiencies, others merely rebrand existing infrastructure or operations teams without making substantive improvements. For the true promise of platform engineering to be realised, the key focus should be on the platform-as-a-product mindset, making sure the platform is delivering the outcomes for the business and that it is an enabler, not a bottleneck.
Essential Open-Source Tools for Building Platforms
A variety of open-source tools are available to support platform engineering efforts. Some of the most impactful include:
Kratix – A flexible framework that enables organizations to build an internal platform with self-service capabilities, composable workflows, and robust fleet management for Day 2 operations.
Backstage – A popular developer portal that centralizes platform documentation and service catalogs.
Crossplane – Provides infrastructure automation with a Kubernetes-native approach.
ArgoCD – A declarative, GitOps-based continuous delivery tool.
When asked how Kratix is different from other platform products, I highlight its Promise abstraction that acts as a “bridge” between technologies. The Promise standardises how a jumble of platform pieces (containers, databases, CI/CD tooling, IAC tooling etc) are composed together in an easily interoperable way. This standardisation offers a simpler developer experience for handling the tech sprawl that many organizations face.
Additionally, its democratized approach allows teams to own their tools and services and contribute these directly into the platform for other teams to consume. Areas such as security and compliance can also be owned by specialist teams and contributed as aspects into the platform. We call this the “multiplayer mode” which balances cognitive load more evenly across an organisation and forges a platform as a force multiplier, reducing friction and silos across teams.
Final Thoughts
Leaders embarking on a platform engineering journey should start by asking: “What is the goal of our platform engineering effort?” The 2024 DORA Report highlighted that while internal platforms can improve software delivery, they do not inherently solve all reliability issues. If an organization suffers from pre-existing reliability problems, implementing platform engineering will not be a silver bullet.
Platform engineering holds immense promise, but its success depends on thoughtful implementation and alignment with business goals. By focusing on user needs, leveraging the right frameworks and tools, and adopting a platform-as-a-product mindset, organizations can create powerful internal platforms that drive efficiency, reduce cognitive load, and accelerate software delivery.
Comments