Sorry, your browser is not supported
Please update your browser to a later version or use a supported browser like Chrome or Firefox.
Why build an Internal Developer Platform?
Accelerate Developers
Code
Code where you
always code
Merge
Git-push as usual
Run
Run on your Internal Developer Platform
Relieve pressure on ops
Why teams build Internal Developer Platforms
Tame your scripts
Teams with organically grown setups often end up in scripting hell. Hundreds of scripts and YAML in all languages.
Former Head of Platform at Zalando
Scale your ops
Unstructured scripts make setups hard to maintain. It also makes it impossible to reach end-to-end developer self-serving.
Make developers self-serving
An Internal Developer Platform frees developers from worrying about the underlying setup. There’s a sense of freedom in having a structure which enforces standards in configs meaning they are able to focus their energies on more creative tasks.
When should you consider an Internal Developer Platform?
It’s a good time to start looking at Internal Developer Platforms when you adopt microservices, go multi-cloud, or realize your ops team is under pressure.
Is an Internal Developer Platform worth the investment?
Further readings
Tame your zoo of scripts
Maintaining scripts is like taming a zoo. But there is a path through the wilderness.
The Rise of Internal Developer Platforms
Enable people to focus on what’s critical to their role.
GitHub's Internal Developer Platform
GitHub's CTO Jason Warner on why and how they built it.