Is Backstage for me?
summary
Backstage claims rapid momentum—24,000 stars—and analysis of adopters (20 surveyed, dozens interviewed) finds successful installs rely on custom plugins that embed company workflows and on the scaffolder/templates that cut onboarding and delivery from weeks to hours (Spotify cites day‑one push to production). Catalogs can index services, APIs, models and show ownership, SonarQube/ArgoCD integrate, and code checks surface compliance, but setup, human friction and ongoing maintenance are required; the catalog is useful but optional.
AI-written summary · about
chapters (12)
- 0:00Backstage introduction and growth
- 5:15Why engineering needs better communication
- 9:12Backstage as communication framework
- 13:45Backstage is a framework, not plug-and-play
- 16:09Signals to solve with Backstage
- 19:37Onboarding with software templates
- 21:22Enforcing practices with checks
- 23:29Commitment to adopt Backstage
- 24:55Q&A: Non-developer assets
- 28:06Q&A: Inconsistent onboarding
- 29:59Q&A: Workflow engines
- 30:41Q&A: First adoption step
related talks
06mThe Future is Backstage
29mWhat Does Backstage Really Offer – Looking Beyond Catalog and Templates and Into...
27mIntroduction to Backstage
47mImproving Developer Experience with Backstage
35mImproving Developer Experience with Backstage
49mA Front Row Seat to Backstage Adoption
35mBackstage: Restoring Order To Your Chaos
26mBackstage: Shaping the Future Of Developer Experience