Facets and Backstage

Is Facets a Backstage alternative?

Not a like-for-like one. Backstage is a developer portal and software catalog, the UI layer. Facets is the SDLC orchestrator that provisions and manages environments underneath. Teams usually run them together: Backstage on top for catalog and discovery, Facets doing the provisioning. They solve different problems.

Book a demo See pricing

Trusted by Aster, Capillary, Purplle, MPL and other high-growth teams.

Portal and platform are different layers

Backstage gets compared to almost everything in platform engineering, but it is a developer portal: a software catalog, a plugin framework, software templates, and docs. The industry distinction is well established. The portal is the UI and discovery layer. The platform, with an orchestrator at its heart, provisions infrastructure and owns the environment lifecycle. You typically need both, and they sit at different layers of the same stack.

How Facets and Backstage relate

Capability	Backstage	Facets

Primary job	Catalog, discovery, docs (portal/UI layer)	Provision and manage environment lifecycle
Provisions infrastructure	Triggers external actions; does not provision itself	Generates and runs Terraform directly
Catalog & plugin ecosystem	Large, mature plugin marketplace + TechDocs	Not a catalog or portal
Operating model	Framework you assemble (or Spotify Portal SaaS)	Managed orchestration platform
Developer self-service	Self-service navigation and initiation	Self-service provisioning with lifecycle ownership

Capability comparison of Backstage and Facets

Where Backstage is clearly stronger

Backstage owns the developer-portal category: a deep plugin ecosystem, a mature software catalog, TechDocs, and (via Spotify Portal, GA in 2025) a managed option that removes most of the self-host burden. If you want a customizable catalog and developer home page, Backstage is the standard, and Facets is not a substitute for it.

Where Facets fits alongside it

Backstage can describe a service, but standing up the database, the cluster, and the environment behind it still needs a provisioning engine. Facets is that engine: typed, swappable modules, generated Terraform, drift-free self-serve environments. Teams that put that model underneath cut DevOps toil by 80% and ship 8-25x faster, whether or not Backstage sits on top.

Where Facets fits

Backstage and Facets are not substitutes; they are adjacent layers. Backstage is the portal and catalog your developers browse; Facets is the orchestrator that provisions and runs the environments behind it. If you are evaluating Backstage to get self-service infrastructure, the catalog is only half the story, you still need an orchestrator underneath. That is where Facets fits.

Frequently asked questions

Not really, and that is the point. Backstage is a developer portal and software catalog framework; Facets is an SDLC orchestrator that provisions and manages environments. Replacing one with the other leaves a gap: Backstage without an orchestrator still needs a provisioning engine, and Facets is not a catalog or portal.

Yes, that is the common pattern. Backstage provides the catalog, discovery, docs, and plugin ecosystem on top; Facets provisions and runs the infrastructure underneath. A Backstage scaffolder action can trigger Facets as the provisioning backend.

Not itself. Backstage's scaffolder triggers external actions (for example a GitHub workflow that runs Terraform); the provisioning engine, state, and lifecycle live outside Backstage. Facets owns that provisioning and environment lifecycle directly.

See Facets on your stack.

Book a demo