Esta página se muestra en inglés. Una traducción al español está en curso.
SkillsApr 13, 2026·3 min de lectura

Backstage — Open Source Developer Portal by Spotify

Backstage is an open platform for building developer portals. Created by Spotify, it provides a centralized catalog of all services, documentation, CI/CD, infrastructure, and tooling — giving developers a single pane of glass for everything they need.

Listo para agents

Instalación lista para agent

Este activo puede instalarse después de elegir el runtime, revisar el plan y ejecutar el comando correspondiente.

Native · 98/100Política: permitir
Superficie agent
Cualquier agent MCP/CLI
Tipo
Skill
Instalación
Single
Confianza
Confianza: Established
Entrada
step-1.md
Comando de instalación directa
npx -y tokrepo@latest install eb267d16-371c-11f1-9bc6-00163e2b0d79 --target codex

Ejecutar después de confirmar el plan con dry-run.

TL;DR
Backstage centralizes all services, docs, and tooling into one developer portal.
§01

What it is

Backstage is an open platform for building developer portals, created by Spotify and donated to the CNCF. It provides a centralized software catalog of all services, documentation, CI/CD pipelines, infrastructure, and tooling. Developers get a single pane of glass for everything they need: discovering services, reading docs, checking build status, and provisioning infrastructure through templates.

Backstage targets platform engineering teams at organizations with many microservices and teams. It reduces the cognitive overhead of navigating dozens of tools by bringing them all into one interface.

§02

Why it saves time or tokens

In large organizations, developers waste time finding which team owns a service, where the docs live, and how to access CI/CD. Backstage puts all of this in one searchable catalog. Software templates let developers provision new services with best practices baked in, reducing onboarding time from days to minutes. For AI-assisted development, Backstage provides structured context about all services that an AI agent can query.

§03

How to use

  1. Create a Backstage app: npx @backstage/create-app@latest
  2. Configure the software catalog by adding catalog-info.yaml files to your repositories
  3. Deploy Backstage and add plugins for CI/CD, monitoring, and other integrations
§04

Example

# catalog-info.yaml (placed in your repo root)
apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
  name: payment-service
  description: Handles payment processing
  annotations:
    github.com/project-slug: myorg/payment-service
    pagerduty.com/service-id: P123ABC
spec:
  type: service
  lifecycle: production
  owner: team-payments
  system: checkout
  providesApis:
    - payment-api
FeatureDescription
Software CatalogRegistry of all services and owners
TechDocsDocs-as-code rendered in Backstage
TemplatesScaffold new services from templates
SearchFind anything across the organization
Plugins100+ community plugins
§05

Related on TokRepo

§06

Common pitfalls

  • Backstage requires ongoing investment; the catalog only stays accurate if teams maintain their catalog-info.yaml files
  • Plugin compatibility across Backstage versions requires careful dependency management; version upgrades can break plugins
  • Backstage is a platform, not a product; it requires significant customization to match your organization's needs

Preguntas frecuentes

Is Backstage free?+

Yes. Backstage is fully open source under the Apache 2.0 license. Spotify open-sourced it and donated it to the CNCF. Several companies offer commercial Backstage hosting (Roadie, Spotify Portal) with managed infrastructure and premium plugins, but the core platform is free.

What is the software catalog?+

The software catalog is a centralized registry of all software components (services, libraries, websites, APIs) in your organization. Each component has an owner, lifecycle stage, dependencies, and links to docs, CI, and monitoring. It answers the question 'who owns this service and where are its docs?'

How do software templates work?+

Templates let developers scaffold new services from a standardized starting point. A template defines the repository structure, CI/CD configuration, and catalog entry. When a developer creates a service from a template, Backstage generates the repository, registers it in the catalog, and sets up the CI pipeline automatically.

Does Backstage support TechDocs?+

Yes. TechDocs is Backstage's built-in documentation system using a docs-as-code approach. You write Markdown in your repository, and Backstage renders it as a searchable documentation site. TechDocs uses MkDocs under the hood and integrates documentation directly into the service catalog.

How does Backstage scale for large organizations?+

Backstage supports hundreds of teams and thousands of components. The catalog uses a PostgreSQL database for persistence and supports incremental updates. Search is powered by Elasticsearch or Lunr. For large deployments, Backstage runs as a scalable web application behind a load balancer.

Referencias (3)
  • Backstage GitHub— Backstage is an open platform for developer portals by Spotify
  • Backstage Docs— Backstage is a CNCF incubating project
  • CNCF— Software catalog and developer experience

Discusión

Inicia sesión para unirte a la discusión.
Aún no hay comentarios. Sé el primero en compartir tus ideas.

Activos relacionados