CatalogStacksModulesSaaSMobileLabs → Become a partner
Home›Catalog›🧰 Dev portal›Backstage
Screenshot of Backstage

// official site: backstage.io ↗

DEV PORTAL · PRO TIER

Backstagepro

Backstage is the open developer portal platform originally built at Spotify, now CNCF incubating. Service catalog, tech docs (TechDocs), software templates (Backstage Templates), plugin ecosystem with 100+ plugins. Centralizes "what services exist, who owns them, how to deploy" for engineering orgs.

🧰 Dev portal Min 2048 MB RAM Port 7000 (http) Tier pro
// What it is

A closer look.

Backstage is the open developer portal platform originally built at Spotify, now CNCF incubating. Service catalog, tech docs (TechDocs), software templates (Backstage Templates), plugin ecosystem with 100+ plugins. Centralizes "what services exist, who owns them, how to deploy" for engineering orgs.

The "internal developer platform" reference implementation — adopted by Spotify, Netflix, Expedia, Wealthsimple.

// Use cases

What it's for.

Concrete scenarios where teams pick Backstage over the SaaS alternative.

◆

Service catalog

single source of truth for "what services run where"

◈

Tech docs (TechDocs)

Markdown-in-Git → rendered docs portal

◇

Software templates

golden-path "new service" generators

▣

API + dependency tracking

visualize service mesh + API consumers

▦

Plugin ecosystem

add views for CI, K8s, AWS, costs, etc.

// Who it's for

Built for these teams.

If your team profile matches one of these, Backstage is a strong fit out of the box.

Profile A

Mid-to-large engineering orgs

with 10+ services + multiple teams

Profile B

Platform engineering teams

building internal developer platforms

Profile C

Companies migrating from "tribal knowledge" to documented service catalog

Profile D

DevEx teams

standardizing developer workflows

Profile E

Multi-team companies

needing service ownership clarity

// Differentiators

Why teams pick Backstage.

When evaluating self-hosted options for this category, here are the dimensions on which Backstage consistently lands above the alternatives.

  • ✓Apache 2.0 — fully open
  • ✓CNCF Incubating — vendor-neutral governance
  • ✓Massive plugin ecosystem — 100+ official + community plugins
  • ✓Battle-tested at scale — Spotify, Netflix, BMW, NS
  • ✓Active development — frequent releases
  • ✓Customizable — full code-level customization
// Integrations

Connects to.

The stack you'll plug Backstage into — services, protocols, and adjacent apps in the BluixApps catalog.

◇
Plugins (100+)
Kubernetes, AWS, GitHub Actions, GitLab CI, Jenkins, Argo CD, Datadog, PagerDuty, more
◈
Identity
OAuth (Google, GitHub, Microsoft, custom OIDC), SAML
◆
Service discovery
Kubernetes, AWS, GitHub orgs, GitLab groups
▣
TechDocs
Markdown in Git rendered as searchable docs
▦
Templates
Scaffold new services from golden paths
▩
Database
Postgres primary
▼
Search
built-in or Elasticsearch backend
// Adoption & deployment

Notable users & community

  • 29k+ GitHub stars
  • Spotify (origin), Netflix, BMW, Wealthsimple, Roadie, Expedia, NS, American Airlines
  • CNCF Incubating project
  • BackstageCon annual conference
  • Backed by Spotify + commercial community (Roadie, Spotify Backstage Hub)

What we ship

  • Docker image: roadiehq/community-backstage-image:latest (community quickstart)
  • Postgres backend with auto-generated password
  • Persistent Postgres volume
  • Port 7000 exposed (mapped from container 7007)
  • Guest auth enabled by default (for evaluation)
  • Production customization documented (custom build required)
  • Backup hook covers Postgres
// Tips & operations

Run it properly.

Operational guidance from running this in production — what to lock down, what surprises people.

// PERFORMANCE
Production Backstage = custom build
Spotify's reference, then customize plugins for your org
// SECURITY
This image is for evaluation
Roadie community Backstage with sample data
// OPERATIONS
Postgres required
no SQLite option
// RELIABILITY
Authentication setup is mandatory
guest auth is for dev only
// DEPLOYMENT
Plugin selection
start minimal, add as needed
// SCALING
Resource sizing
Node.js heavy; 2-4 GB RAM minimum for production
2048
// min ram (MB)
8
// min disk (GB)
7000
// access port
http
// protocol
pro
// bluixapps tier

Project resources

Official sitebackstage.io ↗
↑