IDP (internal developer platform)
An internal developer platform (IDP) is the set of self-service tools, templates and automation that a platform engineering team builds for the rest of the company. Developers use it to create services, get environments, deploy and see their telemetry without filing a ticket. It is run as a product, with developers as its customers.
How it works
A typical IDP stitches existing tools behind one interface:
A service template that creates a repo, CI pipeline and deployment config in one step.
Infrastructure as code modules for databases, queues and buckets, with sensible defaults.
GitOps delivery, so a merge deploys the change.
Dashboards and alerts wired in from day one.
The win is waiting time. On one One2N engagement, a simple Kafka topic request took 3 to 5 days through tickets. Self-service turns that into a reviewed pull request.
Why it matters in production
Without a platform, every team rebuilds the same pipelines and each one drifts. An IDP gives you one supported way to run services, so security fixes and upgrades land everywhere at once. It fails when it is mandated but painful, so adoption is the real metric.
See also
On the One2N blog
Platform engineering strategy: scaling from 5 to 500 engineers
GitOps for Kafka in the real world: how we governed 78 clusters without breaking production
Further reading
