A Front Row Seat to Backstage Adoption
summary
Backstage adoption stories report concrete wins: teams use the catalog, scaffolder and plugins to automate onboarding, governance and docs, migrating from fragmented portals and custom CLIs to a single platform; one org reduced service creation from two days to five minutes, another centralizes metadata across 20,000 entities and a core team supports over 6,000 developers. Deployments use GitHub, Kubernetes/EKS and Postgres (often moved to managed RDS), plugin ownership plus inner‑sourcing scales contribution, and measurable KPIs (time saved, deploy frequency, catalog accuracy) drive further rollout.
AI-written summary · about
chapters (14)
- 0:00Backstage adoption intro
- 1:43Panelist roles
- 3:28Why Backstage matters
- 11:21Starting Backstage adoption
- 18:25Phasing Backstage roadmap
- 25:05Prerequisites for Backstage
- 31:27Measuring Backstage success
- 34:56Advice for new adopters
- 37:46Future Backstage features
- 40:16Catalog growth value
- 42:23Collaborating with portals
- 45:32Backstage database choices
- 46:37Testing scaffolding templates
- 48:42Closing remarks Q&A
related talks
32mIs Backstage for me?
31mBackstage Adoption Deep Dive - Navigating the Pitfalls
06mScaling Enterprise Platform Engineering with Backstage
22mUnlocking Backstage’s Potential: Driving Adoption and Maturity With Your Develope...
35mImproving Developer Experience with Open Source 1
27mLessons from a Year with Backstage: What Worked, What Didn’t...
36m4 Common Pitfalls when Adopting Backstage
35mImproving Developer Experience with Backstage