Transforming DevEx with Internal Developer Portals
summary
Teams describe building an Internal Developer Portal (IDP) that reduces friction by automating CI/CD templates, repository creation and compliance checks using architecture as code, SCA scans against Bitbucket/GitHub, and a Backstage-friendly buying strategy. They track zero-to-hero time and workflow usage, report developers hitting production in under 30 days and demos in 3–4 days, and embed security guardrails in templates so self-service accelerates delivery while staying auditable. Start small, nail one workflow, then expand.
AI-written summary · about
chapters (10)
- 0:00Transforming DevEx with portals
- 1:05Panelist roles in DevEx
- 3:36Vision for enterprise portals
- 6:45Adoption and platform integration
- 9:58Measuring DevEx metrics
- 14:16Security vs developer experience
- 21:03Build vs buy portals
- 23:11AI and internal portals
- 33:55Starting platform engineering
- 36:42Closing remarks and Q&A
related talks
24mDevEx on Steroids: 🚀 5 Hacks to SUPERCHARGE Developer Experience
43mIDP as a Product: Where Developer Happiness Meets Platform's Excell...
11mBuilding Scalable Developer Platforms
29mRevolutionize DevEx: Platform Engineering & DevOps
06mBuilding an IDP in 5 Minutes Not 5 Months
15mDevEx at scale through InnerSource
42mPlatform Engineering 101: Building Internal Developer Platforms
39mDoing more with internal developer portals
