Internal Developer Platform
The assembled surface teams actually touch, and what belongs behind it.
4 to work through
-
intermediate
Review this. A 12-engineer startup with 6 services has built an internal developer platform - a React portal, a YAML DSL that generates Terraform, a bespoke secrets service backed by cloud KMS, a service catalogue and a maturity scorecard with 23 checks. Two of the twelve engineers work on it full time. Deploys take 14 minutes and the DSL covers about 60% of what teams need, with the rest hand-written Terraform merged by those two engineers. What would you remove, what would you change, and what would you leave alone?
3 min answer -
intermediate
Your service catalogue says every service has an owner. Investigating an incident, you find the named owner left the company eight months ago. How do you prevent this class of problem?
2 min answer -
advanced
An organisation is building an internal developer platform. What should be in scope, and what is the most common scoping error?
2 min answer -
advanced
Leadership asks whether to build an internal developer platform or buy one. Twelve teams, forty services, growing. How do you frame the decision?
2 min answer
4 terms in this topic
Backstage-Style Service Catalogue
A queryable inventory of every service, its owner, its dependencies, its documentation and its operational state.
conceptInternal Developer Platform
The curated set of self-service capabilities that lets product teams build, deploy and operate software without filing tickets against infrastructure.
conceptService Catalogue Entry
The record that makes a service a first-class object in the platform — owner, dependencies, docs, runbooks and health in one place with a single identity.
case-studySpotify Backstage: The Catalogue as a Product
Spotify built a developer portal that unified service discovery, documentation, templates and tooling behind one interface, and open-sourced it.
Neighbouring topics
Platform Engineering
General material on internal platforms as products with users, adoption and lifecycles.
Paved Road & Golden Path
A supported default route that is easier than the alternatives rather than mandatory.
Self-Service Provisioning
Teams getting infrastructure without a ticket, and the guardrails that make that safe.
Service Templates
Scaffolding new services with observability, CI and security already wired in.
Platform APIs
Treating the platform's own interfaces as contracts with consumers and compatibility rules.
Platform Tenancy
Isolating teams sharing a cluster, account or pipeline fleet, and where isolation must be hard.
Cluster Architecture
How many clusters, split by what, and the blast radius each split buys.
Service Mesh Operations
What a mesh genuinely solves, its failure modes, and the cost of running one.
Container Image Strategy
Base images, layer hygiene, rebuild cadence, and patching a fleet of images.
Developer Environments
Local, remote and ephemeral environments, and the fidelity each can honestly claim.
Inner Loop & Outer Loop
Where an engineer's time actually goes, and which loop a platform investment shortens.
Abstraction Level Choice
How much to hide, and the leak that turns a helpful abstraction into a trap.
Platform SLOs
Committing to reliability for internal consumers who cannot choose another provider.
Platform Adoption
Migrating existing teams onto a platform without a mandate, and reading the adoption curve.
Platform Funding
Central cost, showback, chargeback, and justifying a team that ships no customer feature.
Platform API Deprecation
Removing something dozens of internal teams depend on, on a timeline that holds.
Guardrails vs Gates
Preventing a class of mistake automatically versus stopping to ask a human.
Platform Telemetry
Instrumenting the platform itself: usage, friction, and where teams leave the paved road.
Platform Team Topologies
Stream-aligned, enabling, complicated-subsystem and platform teams, and their interactions.