Infrastructure on demand from Backstage, and a catalog that builds itself
StackGen gives developers governed self-service infrastructure from Backstage templates. Agents build and maintain your software catalog from the code, and your platform team approves every change.
Trusted by platform teams building the future
.svg)
Infrastructure from Backstage in minutes, with policy built in
Developers pick a golden path and answer only what they know. StackGen fills in the rest, checks policy and commits to Git.
A Backstage catalog that builds itself from your code
Agents read every repository, generate the system model and suggest an owner. Your platform team approves each entry as a pull request.
Backstage, running in production
Two platform teams show how StackGen works inside Backstage.
One uses it to keep the software catalog accurate without hand-written YAML. The other uses it to start new services from approved blueprints, with the infrastructure code written and ready for review.
(A Global Technology Company)
Aiden reads repositories inside the network and drafts catalog-info.yaml only when a service clears a confidence check. Developers review a pull request instead of writing the file.
Golden paths, governed by default (LATAM Bank)
A Backstage form starts a new service from an approved blueprint. StackGen writes the OpenTofu from the platform team’s own modules and opens the pull request.
The portal is live. Two things still hold it back.
Built for platform teams that run Backstage at scale
From install to first golden path
Getting started
01
Install the StackGen Backstage plugin
From the public npm registry, with no GitHub token in the install path.
02
Turn your top requests into golden paths
Start with the three to five infrastructure requests your platform team sees most.
03
Connect identity and policy
Sync groups from your identity provider and load your security rules.
04
Point hydration at one source control system
Measure catalog completeness first, then widen system by system.
