Overview

Backstage is a self-hosted framework for building a developer portal, rather than a finished portal service. Its catalog brings ownership and metadata for services, websites, libraries and data pipelines into a shared view. The project describes a range from a team managing 10 services to a company managing thousands, making it relevant to organizations seeking a common map of a growing software ecosystem.

The flexibility has an operational counterpart. The standalone installation guide produces a local demo using in-memory SQLite and sample content, and says that setup is not production-ready. It calls for at least 20 GB of disk and 6 GB of memory, with more disk needed as modules and plugins are added. Teams should treat production deployment as a separate implementation task, not a step already solved by the demo.

Key features

The software catalog tracks ownership alongside metadata, which can help engineering teams connect components to the people responsible for them. Software Templates turn code skeletons into generated projects by substituting variables and publishing output to destinations such as GitHub or GitLab. That makes Backstage a fit for teams that want repeatable project creation inside their portal.

TechDocs follows a docs-like-code approach, keeping documentation close to code. Backstage Search can index sources including TechDocs, Confluence and Stack Overflow, while integrations can read or publish data through providers such as GitHub, GitLab, Bitbucket, LDAP and cloud providers. The Kubernetes feature aggregates a service’s deployments through the Kubernetes API, including for cloud and multi-cloud environments.

Existing open-source plugins and locally built plugins let organizations extend the portal, including with self-service workflows and engineering scorecards. That breadth is useful when the portal needs to reflect a particular stack, but it also leaves adoption and maintenance choices with the organization. Community plugins have not all been vetted by the core team, so teams should assess them before adding them.

Pricing

Backstage open-source framework: 0.00 USD per free. The framework is free and self-hosted; no plan limits are stated. There is no paid tier in the pricing model described, so the decision is less about seats or quotas than whether a team can take responsibility for deployment and ongoing customization.

Platforms

Backstage supports API, Linux, macOS, self-hosted and web platforms. Its deployment model is self-hosted, which gives teams control over how the portal fits their environment but makes deployment and operational readiness their responsibility.

Who it's for

Backstage is best suited to organizations whose product and engineering teams need a shared portal and catalog, and have the capacity to configure and operate one. Teams that want control over catalog structure, integrations, templates and plugins can benefit from the framework approach. It is a weaker fit for teams seeking a production-ready, managed portal with little deployment work.

Security also affects fit. Backstage recommends enabling only authentication providers an instance uses and configuring sign-in resolvers carefully. Its threat model describes only rudimentary denial-of-service protection and primarily envisages deployment in a protected environment. Teams that cannot provide that environment should look elsewhere. The project documentation links to community support and contribution resources.

Pros and cons

Pro: The catalog covers multiple kinds of software and ownership metadata, giving organizations a shared inventory rather than a narrow service list.
Pro: Templates, TechDocs, search and integrations support workflows across project creation, documentation and existing tools.
Pro: An open plugin ecosystem allows teams to extend the portal or build capabilities to match their needs.
Con: The standalone demo is explicitly not production-ready, so teams must plan and operate a proper deployment.
Con: The stated memory and disk minimums, plus extra disk as plugins and modules grow, create a real infrastructure commitment.
Con: Rudimentary denial-of-service protection and the protected-environment assumption make security architecture a prerequisite, not an afterthought.
Con: Community plugins are not all core-team vetted, which means organizations need to judge their suitability.

Alternatives

Choose configure8 if a freemium portal with a free plan and unlimited catalog users and items up to a data cap better fits your needs. Northflank offers a free Sandbox with two services, one database and two cron jobs, so consider it when those bounded resources suit the use case. Port is another freemium option; its Free plan caps usage at 15 seats, 10k entities and 400 runs.

Cycloid has a free SaaS plan for up to five users and one workspace, making it an option for teams that prefer that setup. Cortex uses custom, per-seat pricing that scales with organization size. Humanitec is a paid option with a Teams plan at 1979.00 USD per month, billed annually, for five users, two projects and up to five environments per project. OpsLevel is a paid alternative with a Standard plan for up to 50 users and unlimited cataloged components. Qovery is a paid option with a Team plan at 299.00 USD per month, billed yearly, for three users, one managed cluster and 3,000 deployment minutes per month.

Compare other options in Internal Developer Portals, Platform Engineering Software, Application Dependency Mapping Software and Code Generators.

Verdict

Choose Backstage if your engineering organization wants a highly adaptable portal and can own its self-hosted deployment, integrations and security posture. Its catalog and extension model are the main reasons to choose it; teams that need managed operations or stronger built-in denial-of-service protection should look elsewhere.

	Backstage	Illumio Segmentation
Free plan	Yes	No
Free trial	No	No
Paid from	Free	—
Open source	No	No
Platforms	api, Linux, macOS, self-hosted, Web	Linux, Windows
Free plan	Yes	No

Backstage vs Illumio Segmentation

Backstage

Illumio Segmentation