Our adventure in building an internal developer platform
summary
A consultancy builds a CI/CD pipeline as a service that generates provider pipelines from a tiny config file, adds versioning and parallel isolated tests, and ships an adoption dashboard tracking deployment frequency and lead time to change. The team measures success with DORA metrics and Net Promoter–style satisfaction scores, stages work in assess → MVP → seed & scale → evolve phases, and reports fewer tool choices, faster onboarding, and reduced cognitive load once hundreds of services adopt the platform.
AI-written summary · about
chapters (10)
- 0:00Internal developer platforms
- 4:24Tool choice and complexity
- 9:27Four phases of building
- 17:56Assessing needs and metrics
- 18:18Minimal viable platform
- 23:56Pipeline as a service
- 24:18Scaling adoption
- 29:58Evolving the platform
- 34:12Key takeaways
- 37:48Q&A
related talks
29mIaC Next Steps in Platform Engineering
11mBuilding Scalable Developer Platforms
44mPlatform Engineering 101: Building Internal Developer Platforms
37mAchieving High Performance with an Internal Developer Platform
30mOur Continuous Delivery Journey
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling
45mDevOps Is All About Building Internal Developer Platform (IDP)
15mEngineering Culture First: The Journey to Building Sphera, monday.com's IDP