Panel: Insights from Internal Developer Portal Rollouts in Large Enterprises
summary
Large enterprises report concrete claims, tools, and outcomes: Backstage-based IDPs centralize discovery, reduce duplicate tooling (Roku found many redundant log viewers), and require a funded product team with SLAs and global coverage. Specifics include 45,000 developers at one bank, a staffed platform of ~40–50 people at another, and an operational win where a pilot contract system ships in 7 months, avoiding hundreds of millions in fines. Practical advice: start with one team, favor plugins over overloaded scaffolder templates, certify golden templates, and invest in observability and AI.
AI-written summary · about
chapters (8)
- 0:00Introductions and context
- 2:07Motivations for IDP adoption
- 9:54Build vs. buy decision
- 17:36Strategy for portal expansion
- 21:53Investment and maintenance
- 27:36Plugins and workflows
- 31:53Future plans and team sizing
- 38:18Scaffolder templates and impact
related talks
06mPlatform Engineering with a Product Management Mindset: 10x Your De...
37mPanel - How to Develop a Successful Digital Product Within a Large Corporation
26mLessons Learned from 7 years of Running Developer Platforms
01h 01mEnterprise Adoption of DevOps
24mFrom 165 Days To 30 Minutes: Breaking Enterprise Silos With…
22mThe challenges of Platform teams
45mPanel Discussion: Ways to unlock engineering effectiveness
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines