Backstage IDP
The problem
New services meant a ticket queue: someone on the platform team hand-provisioning a repo, CI pipeline, cloud resources, and catalog entry before an engineer could write a line of application code. Onboarding a new service — or a new hire — took days, and the platform team became the bottleneck for every team that wanted to ship something new.
What I built
A Backstage-based internal developer platform with golden-path software templates: scaffolding a new service, its pipeline, and its infrastructure all come from the same self-service template, backed by the Software Catalog so every service is discoverable and owned. The paved road is the fast road, so teams follow it by default instead of hand-rolling their own setup.
Result
Developers provision new services themselves in minutes instead of filing a ticket, and the platform team’s support load for “how do I get a new service set up” has dropped correspondingly.