Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Backstage

backstage.io

  • Free plan
  • macOS
  • Linux
  • Web
  • API
  • Self-hosted
8.0 Club score Visit backstage.io

What Backstage is

Backstage is a free, open-source framework for building and deploying self-hosted developer portals. Its software catalog records ownership and metadata for services, websites, libraries, and data pipelines, for teams managing a handful of services or catalogs of thousands. Software Templates can fill code skeletons with variables and publish generated projects to places such as GitHub or GitLab. TechDocs keeps documentation close to code in a docs-like-code workflow. Integrations can read or publish data through providers including GitHub, GitLab, Bitbucket, LDAP, and cloud providers. Teams can add existing open-source plugins or create their own, while Backstage Search can index TechDocs, Confluence, and Stack Overflow. Its Kubernetes feature aggregates deployments for a service using the Kubernetes API. The standalone installation guide creates a local app with demo content and an in-memory SQLite database, but says this setup is not production-ready. That guide lists minimum requirements of 20 GB disk space and 6 GB memory. The threat model describes only rudimentary denial-of-service protection and recommends a protected environment.

Who it suits

Backstage suits organizations whose product and engineering teams need a shared developer portal and software catalog. It is intended for self-hosted deployment, with the threat model recommending a protected environment.

Good to know, and what to watch

  • Catalog records ownership and metadata across software assets
  • Templates publish generated projects to GitHub or GitLab
  • TechDocs keeps documentation close to code
  • Search can index TechDocs, Confluence, and Stack Overflow
  • Organizations can add or build plugins
  • Standalone demo setup is not production-ready
  • Minimum standalone requirements include 20 GB disk and 6 GB memory
  • Denial-of-service protection is described as rudimentary
  • Community plugins have not all been vetted by the core team

Backstage open-source framework

Free

Free plan

Getting started

  1. Open https://backstage.io/
  2. Follow the standalone installation guide
  3. Provide at least 20 GB of disk space and 6 GB of memory
  4. Run the locally hosted app with its in-memory SQLite database and demo content
  5. Extend the portal with integrations or plugins as needed

Limits to check

The standalone installation creates an in-memory SQLite demo application that is explicitly not production-ready. Disk needs increase as modules and plugins are added, and the threat model describes only rudimentary denial-of-service protection.

The verdict

Backstage provides a flexible foundation for a shared developer portal, catalog, and documentation workflow. Plan for self-hosting and review the security guidance and plugin status before deployment.

Questions people ask

Is Backstage free?

Yes. Backstage is offered as a free, open-source framework, with a listed plan price of free.

Which platforms does Backstage support?

Listed platforms are API, Linux, macOS, self-hosted, and web.

Can Backstage connect to external services?

Its integrations can read or publish data through GitHub, GitLab, Bitbucket, LDAP, and cloud providers.

Is Backstage self-hosted?

Yes. Its deployment model is self-hosted.

What does the standalone installation include?

It creates a locally running app with demo content and an in-memory SQLite database. The guide says this configuration is not production-ready.

Can organizations customize Backstage?

Yes. Organizations can install open-source plugins or build their own; the community plugin directory notes that not every plugin has been vetted by the core team.

What the maker publishes

Catalog scale
Backstage says its catalog can help a team manage 10 services and make it possible for a company to manage thousands. source
Deployment
The standalone installation guide creates a locally running app with an in-memory SQLite database and demo content, and says this setup is not production-ready. source
Integrations
Integrations let Backstage read or publish data using providers such as GitHub, GitLab, Bitbucket, LDAP, and cloud providers. source
Intended users
Backstage is aimed at organizations whose product and engineering teams need a shared developer portal and software ecosystem catalog. source
Kubernetes
The Kubernetes feature aggregates a service’s deployments and uses the Kubernetes API to support cloud and multi-cloud environments. source
Plugin ecosystem
A Backstage portal can be customized with existing open-source plugins or plugins built by the adopter. source
Plugins
Organizations can extend Backstage with open-source plugins or build their own; the plugin directory warns that community plugins have not all been vetted by the core team. source
Product
Backstage is an open-source framework for building developer portals. source
Purpose
Backstage is an open-source framework for creating and deploying developer portals, originally created at Spotify. source
Requirements
The standalone app guide lists minimum requirements of 20 GB disk space and 6 GB memory, with additional disk space needed as modules and plugins are added. source
Search
Backstage Search is an extensible platform that can index sources such as TechDocs, Confluence, and Stack Overflow. source
Security
Backstage's threat model recommends enabling only the authentication providers an instance uses and configuring sign-in resolvers carefully. source
Security
The official threat model outlines security considerations for operators, developers, and security researchers, and points to the project’s security policy for vulnerability reporting. source
Security limit
The threat model says Backstage provides only rudimentary protection against denial-of-service attacks and is primarily designed for deployment in a protected environment. source
Software catalog
The catalog tracks software ownership and metadata, including services, websites, libraries, and data pipelines. source
Support
The project documentation links to a community support chatroom and contribution resources. source
Support
The project lists Discord, FAQs, and community resources for support and discussion. source
TechDocs
TechDocs uses a docs-like-code approach that keeps documentation close to the code. source
TechDocs
TechDocs provides documentation as code, letting engineers write Markdown alongside their code. source
Templates
Software Templates can load code skeletons, substitute variables, and publish generated projects to locations such as GitHub or GitLab. source
Templates
Software templates let engineers create components with organizational standards built in. source

Checked against the maker's pages on 30 Sept 2026.