In the previous subchapters, we saw golden paths and the Service Catalog: ways to offer ready-to-use infrastructure to developers. But as a company grows, developers face another problem: fragmentation. There are many tools, many services, lots of documentation... scattered everywhere. Where do I find information about my service? How do I create a new one following the rules? Where is the documentation? To unify all this in one place, there is Backstage: a developer portal that has become the industry standard for building Internal Developer Platforms.

In a large company with many services and tools, a developer (especially a new one) feels lost:

All that fragmentation makes developers waste time searching, duplicate work (because they don’t know what already exists), and take a long time to become productive. You need a single place that brings it all together. That’s Backstage.

Backstage is an open source platform (originally created by Spotify) for building a developer portal: a single place where developers find everything they need to work—their services, their documentation, their tools, their golden paths—in a unified and organized way.

Analogy: Backstage is like a single, well-organized company intranet portal, but for developers. Instead of having to remember ten different addresses, search through scattered wikis, and ask colleagues “where is this?”, you go into one portal and from there access everything in an organized way: your projects, documentation, tools, guides to do new things. It’s the developer’s “one-stop shop” that brings order to the chaos of tools.

Backstage offers a catalog of all the company’s services, applications, and components: what exists, who is responsible for each thing, how they are related. This solves the “what’s already there?” and avoids reinventing what another team has already built. At a glance, you see the organization’s software map.

Backstage allows you to offer templates (software templates) that implement the golden paths (subchapter 31.1): “want to create a new service? Use this template and you’ll get one with all the structure, infrastructure (Terraform), pipelines, and best practices already set up.” It’s the way to offer golden paths in an accessible way, from the portal.

Backstage brings together the documentation for all services in one place (often alongside the code itself), so finding it is easy. No more searching through scattered and outdated wikis.

Backstage integrates with the tools the company already uses (CI/CD, monitoring, cloud, the Service Catalog from subchapter 31.2...), showing everything in a unified way. It’s extensible via plugins, so each company adapts it to their tools.

Here’s where the whole chapter comes together. Remember the concepts:

• Platform Engineering (subchapter 31.1): building an internal platform for developers.
• That platform is called the Internal Developer Platform (IDP): the set of tools, golden paths, and services that the platform team offers to developers.
• Backstage is, very often, the visible face (the portal) of that IDP: the place where developers access everything the platform offers.

Backstage doesn’t replace the other pieces; it unifies them into a coherent experience for the developer.

Real-world example: a company with 200 developers and hundreds of services was in chaos: scattered information, people didn’t know what existed or how to create services properly. They implemented Backstage as the developer portal. Now, a new developer enters Backstage and sees: the catalog of all services (and who owns each one), the documentation for each, and templates (golden paths) to create a new service with all the infrastructure and best practices set up in minutes. What used to take a newcomer weeks—to understand the landscape and be able to contribute—now takes days. And duplicate work stops, because everyone can see what already exists. Backstage turned the chaos of tools into an organized and productive experience.

• In large companies, developers get lost among a thousand tools, services, and scattered documentation, wasting time and duplicating work. They need a single place that brings it all together.
• Backstage is an open source platform (created by Spotify) for building a developer portal: a single place with services, documentation, tools, and golden paths, in a unified way. Like the developer’s single intranet portal (the “one-stop shop”).
• It offers: a software catalog (what exists and who maintains it), templates that implement the golden paths (create new things properly, easily), centralized documentation, and integration with existing tools (extensible with plugins).
• It’s usually the visible face (the portal) of the Internal Developer Platform (IDP): the place where developers access the whole platform (golden paths, Service Catalog, modules...). It doesn’t replace those pieces; it unifies them.

In the last subchapter of the chapter (and of Part VII), we’ll wrap up the idea with a key vision: treating Terraform modules as an internal product, with the product mindset that underpins all of Platform Engineering.