Internal Developer Platform and Developers: What Does the Business Pay For?
summary
Discussion of building and operating an internal developer platform for a large, fast‑growing company, focusing on which platform features and services the business is willing to pay for. Covers costs visibility and tradeoffs when an engineering team provides a mature platform to many product teams, and how to prioritize platform investment to match business value.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 2:12From feudal state to platform chaos
- 9:58Centralization efforts
- 15:34Platform crisis and alignment
- 18:46Building trust with availability tiers
- 21:19User influence and transparency
- 25:19Pricing model and cost transparency
- 33:53Automation and financial integration
- 37:07Platform as business unit
- 39:14Next steps and open sourcing
- 40:23Q&A: Scaling platform
- 41:29Q&A: Investment budgets
- 43:14Q&A: Refusing needs
- 44:42Q&A: External market entry
- 46:08Q&A: Platform origins
- 47:34Q&A: International competition
- 49:00Q&A: Platform development hacks
- 49:20Q&A: Regulating products
- 53:33Closing remarks
related talks
40mInternal platforms in practice
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling
11mBuilding Scalable Developer Platforms
43mEngineering Platforms Evolved
48mTechnical governance of an IDP (Internal Developer Platform) for 7,000 developers
26mBuilding Internal Platforms to Enhance Developer Experience
44mPlatform as a Product: A Deep Dive into the Technical Foundations
25mInternal Platform as a Product