Internal Platform as a Product
summary
Claims a successful internal platform scales from a tiny, opinionated core to full self‑service: start with opinionated defaults and small scope, avoid cramming every tool. Gives concrete pain points — Jenkins plus another ad‑hoc tool caused a CI job to run hours and developers to re-run pipelines manually — and concrete scale metrics: about 250 developers, 1,700 users, 8,000 CI runs and 2,000 pipelines feeding 185 releases to UAT/SIT in one month. Recommends GitLab as a single surface, fast feedback loops, cost visibility, and strong security hygiene.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:31Why internal platform
- 6:52Building principles
- 10:05Developer experience
- 13:18Internal platform challenges
- 17:31Platform investment cost
- 20:37Successful platform results
- 24:08Summary & Q&A
related talks
33mWhy You Should Treat Your Platform as a Product
44mPlatform Engineering 101: Building Internal Developer Platforms
40mInternal platforms in practice
11mBuilding Scalable Developer Platforms
54mDeveloper experience platforms
26mBuilding Internal Platforms to Enhance Developer Experience
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines
26mLessons Learned from 7 years of Running Developer Platforms