In today’s complex enterprise landscape, internal developer platforms have become essential for boosting developer productivity and standardizing cloud operations. But as organizations scale, platform responsibility often becomes decentralized. Independent Platform Teams emerge, each building their own platform to meet local needs — leading to a fragmented ecosystem of Platform Kingdoms.
The Platform Kingdoms, much like interest-driven principalities of the Middle Ages, operate with varying degrees of autonomy and local control. Each has its own priorities, tools, and ways of working — and not all are eager to align. In fact, efforts toward “unification” are often met with skepticism, driven by concerns over losing influence or independence. Yet, to unlock the full potential of platform engineering at scale, these kingdoms must be intentionally and respectfully united under a shared vision.
This is where the concept of the Platform Empire comes in — not as a rigid centralization, but as a federated union of Platform Kingdoms. A Platform Empire enables collaboration, shared standards, and interoperability, while respecting the unique contexts of each team. It’s about creating a cohesive whole from distributed strengths.
The Inevitable Rise of Multiple Platforms
The journey typically begins simply enough: an organization decides to build an internal developer platform to standardize cloud operations and improve developer productivity. However, as the organization grows and evolves, multiple platforms emerge — often through different paths, such as new business units joining via acquisitions or independent digital innovation teams building their own solutions without broader alignment.
One common scenario occurs through mergers and acquisitions. Consider a real-world example: UniCredit’s acquisition of the digital bank Aion and its cloud platform provider Vodeno, which brought Azure-based infrastructure into an AWS-centered environment. The acquisition’s Azure platform represented years of investment and optimization — simply migrating everything to AWS would be both costly and risky. Instead, the organization needed to find a way to manage both platforms effectively.
But M&As aren’t the only driver of platform multiplication. Different business units often have distinct requirements that lead them to adopt different cloud providers or platform approaches. A data science team might require specific GPU capabilities and AI/ML services best provided by Google Cloud Platform, while the customer-facing applications team might benefit more from AWS’s extensive global infrastructure.
Understanding the Platform Kingdom Model
The Platform Kingdom model provides a framework for understanding and managing these multiple platforms effectively. At its core, this model recognizes that different platforms within an organization function like semi-autonomous kingdoms — each with its own governance, priorities, and technical directions, yet aligned under shared principles and goals.
However, as the number and complexity of these kingdoms grow, organizations must move beyond coexistence toward meaningful collaboration. This is where the Platform Empire comes into play — a unifying structure that respects the autonomy of individual Platform Kingdoms while enabling shared standards, interoperability, and strategic alignment across the entire enterprise!
The model is built on three key principles:
- Hierarchical Platform Stacking
- Shared Responsibility Models
- A matching Landing Zone Architecture
Let’s explore each of these in detail.
Hierarchical Platform Stacking
Platform stacking represents the layered approach to platform services. At the foundation, we have the basic cloud infrastructure platforms – the hyperscalers like AWS, Azure, and GCP. Above this foundation, organizations build their cloud foundation platform, which provides enterprise-wide services like identity management, security controls, and compliance frameworks.
Further up the stack, we find domain-specific platforms. These might include data science platforms, internal developer platforms for web applications, or specialized platforms for IoT devices. Each layer builds upon the capabilities of the layers below while adding its own specialized features and constraints.
Shared Responsibility Models
The success of a Platform Empire depends heavily on clearly defined responsibilities between platform providers and consumers. Each platform in the kingdom must have its own shared responsibility model that clearly delineates:
- What the platform provides "out of the box"
- What customizations are allowed
- What responsibilities remain with the platform consumers
- How platform updates and changes are managed
- Security and compliance responsibilities
Landing Zone Architecture
Landing zones serve as the technical implementation of platform governance. They provide a structured way to implement security, compliance, and operational requirements across different platforms while maintaining flexibility for specific use cases.
Think of landing zones as the zoning laws of your Platform Kingdom. Just as a city might have different zones for residential, commercial, and industrial use, your cloud infrastructure can have different landing zones optimized for various workload types, security requirements, or business units.
Governing the Platform Empire
Effective governance in a multi-platform environment requires balancing autonomy with control. Platform Kingdoms need enough freedom to innovate and optimize for their specific use cases, while the organization needs to maintain overall control and visibility.
The key to achieving this balance lies in implementing what we call "federation principles":
Central Visibility with Distributed Control
While individual platform teams maintain control over their specific platforms, the organization needs central visibility across all platforms. This includes monitoring, security oversight, and cost management. Tools and processes should be put in place to aggregate information from all platforms into central dashboards and reporting systems.
Standardized Interfaces, Customized Implementations
While each platform may have its own internal implementation details, the interfaces they expose to users should follow organizational standards. This includes consistent terminology, documentation formats, and service request processes. Think of it as ensuring all citizens of your Kingdoms speak a common language, even if they have different local customs.
Cross-Platform Collaboration
Encourage and facilitate collaboration between platform teams. Regular "Platform Council" meetings where platform teams share challenges, solutions, and best practices can help maintain alignment while fostering innovation.
Measuring Success in the Platform Empire
Success in a multi-platform environment can’t be measured by traditional infrastructure metrics alone.
Developer Productivity Metrics
The DORA metrics provide an excellent framework for measuring the impact of your platform strategy:
- Deployment Frequency: How often new code is successfully deployed to production — a key indicator of how quickly teams can deliver value.
- Lead Time for Changes: The time it takes from committing code to having it running in production — measuring the speed of the delivery pipeline.
- Mean Time to Recovery (MTTR): The average time it takes to restore service after a failure — reflecting the team’s ability to respond and recover quickly.
- Change Failure Rate: The percentage of changes that result in a failure in production — highlighting the stability and reliability of the release process.
Platform Adoption and Usage
Track how developers are using each platform and identify patterns that might indicate areas for improvement or consolidation. This includes monitoring:
- Number of active users per platform
- Types of workloads being deployed
- Service request patterns
- Support ticket categories and volumes
Cost Efficiency
While each platform might have its own cost structure, track overall efficiency metrics such as:
- Cost per deployment
- Resource utilization rates
- License usage and optimization
- Support costs per platform
Building Your Platform Empire
If you’re navigating the challenge of managing multiple platforms, imagine building a Platform Empire that’s more than just a collection of kingdoms — it’s a thriving federation guided by shared purpose, clear boundaries, and coordinated strength.
Picture a central map room — a real-time overview of all your Platform Kingdoms, showing who’s doing what and where. Each kingdom operates under a charter — a clearly defined model of rights, duties, and shared responsibilities. The empire is protected by guardrails — policy-driven landing zones that ensure safety without stifling innovation.
At the heart of the empire is a council chamber — a space for regular dialogue, alignment, and collaboration among platform teams. And overseeing it all is a watchtower, where unified metrics and observability tools give you insight into the health and progress of the entire realm.
The goal isn’t to centralize power, but to federate capabilities — empowering platform teams to serve their domains while contributing to a greater whole.
Looking Ahead
The trend toward multiple specialized platforms within organizations is likely to continue as cloud services become more diverse and specialized. The key to success lies not in fighting this trend, but in embracing it with a structured approach that maintains order while allowing for innovation and specialization.
The Platform Empire model provides a framework for managing this complexity — whether your organization resembles a loosely connected federations or a tightly integrated structure depends largely on how much autonomy exists across your teams and units.
Success in platform engineering isn’t about building the perfect platform – it’s about building the right set of platforms for your organization’s needs and managing them effectively as a cohesive whole. By thinking of your platforms as an Empire rather than a single entity, you can better manage the complexity while delivering value to your developers and organization.