Every fast-growing engineering team eventually hits the same wall. A developer needs a new staging environment to test a critical feature, so they file a ticket with the infrastructure team. The platform engineering team, already overwhelmed with maintenance tasks, queues it. Two weeks later, the environment finally exists, but the developer has already lost momentum, and the product release has been delayed.
As Kenyan and African tech startups scale and enterprise IT departments modernize, this friction becomes a major bottleneck. The solution gaining rapid traction globally is the Internal Developer Platform (IDP). By leveraging powerful open-source tools like Spotify's Backstage, ArgoCD, and Crossplane, engineering organizations can build a self-service infrastructure that empowers developers while maintaining strict operational guardrails.
Understanding the Modern Platform Stack
To build an effective IDP, organizations must move away from manual ticketing systems and ad-hoc scripting. Instead, they need a cohesive platform that abstracts infrastructure complexity. A robust open-source IDP stack typically relies on three core pillars: a developer portal, a continuous delivery engine, and a cloud infrastructure provider.
At the frontend of this platform sits Backstage, an open-source framework originally developed by Spotify. Backstage serves as a centralized developer portal. It provides a single catalog for all software assets, microservices, and documentation, alongside software templates that allow developers to spin up new projects with pre-configured CI/CD pipelines and monitoring in a single click.
Under the hood, infrastructure provisioning and application deployment must be automated and declarative. This is where Crossplane and ArgoCD enter the picture. Crossplane is a Kubernetes add-on that extends clusters to provision and manage external cloud resources—like databases, storage buckets, and networking—using standard Kubernetes custom resources. ArgoCD then handles GitOps-based continuous delivery, ensuring that the actual state of the infrastructure and applications always matches the desired state defined in Git repositories.
Connecting Backstage, ArgoCD, and Crossplane
Building a seamless IDP requires integrating these three tools into a unified workflow. The process begins when a developer requests a new service through the Backstage UI.
First, Backstage utilizes its Software Templates feature to scaffold a new repository. This repository contains both the application code and the declarative infrastructure manifests required to run it. Instead of writing custom Terraform code or accessing cloud consoles directly, the developer simply fills out a form in Backstage specifying their requirements, such as database size or region.
Second, Crossplane interprets the infrastructure manifests generated by Backstage. Because Crossplane runs inside a Kubernetes cluster, it continuously monitors these manifests and calls the APIs of cloud providers (like AWS, Azure, Google Cloud, or local African cloud providers) to provision the requested resources. This eliminates the need for developers to manage cloud credentials directly, significantly improving security.
Finally, ArgoCD monitors the Git repository containing the application code and deployment configurations. As soon as the infrastructure is ready, ArgoCD automatically deploys the application container to the target environment. If any configuration drift occurs—for instance, if someone manually alters a setting in the cloud console—ArgoCD and Crossplane work together to automatically reconcile the system back to the approved Git-defined state.
Why IDPs Matter for African Tech Ecosystems
For engineering leaders in Kenya, Nigeria, South Africa, and across the continent, adopting platform engineering practices is no longer a luxury reserved for Silicon Valley giants. The African tech ecosystem faces unique talent dynamics; experienced senior DevOps and site reliability engineers (SREs) are highly sought after and often difficult to retain.
By building an IDP, organizations can maximize the impact of their existing senior infrastructure talent. Instead of spending their days manually provisioning databases and troubleshooting deployment pipelines for individual developers, SREs can focus on building and refining the platform itself. This "platform product management" approach allows a small infrastructure team to support hundreds of software developers efficiently.
Furthermore, as local businesses migrate to hybrid cloud environments—balancing local data residency requirements with international cloud services—an IDP built on Crossplane provides cloud-agnostic abstractions. Developers do not need to learn the specific APIs of different cloud vendors; they simply interact with the standardized internal platform, accelerating time-to-market for digital products and financial services.