Developer Tools · head to head
Backstage vs Cortex
Backstage
Developer Tools
Open source internal developer portal framework created and open sourced by Spotify
- From
- Free
- Rated
- -
Cortex
Developer Tools
Internal developer portal that scores service ownership and maturity rather than just cataloguing services
- From
- On request
- Rated
- -
The short version
- Only Backstage has a free tier, so it costs nothing to try first.
- Each has a real cost: Backstage backstage is a framework rather than a product: there is no supported turnkey install, so getting to a usable portal means a TypeScript and React project your team owns, hosts and upgrades forever.; Cortex pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.
- They diverge on capability: Backstage covers Software catalogue, Cortex covers Service catalogue.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Backstage and Cortex actually diverge.
Identical on both: user rating (Not yet rated), category (Developer Tools).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Backstage
- Software catalogue
- Software templates
- TechDocs
- Plugin architecture
- Kubernetes plugin
- Search
- Entity ownership model
- Auth provider integrations
Only in Cortex
- Service catalogue
- Scorecards
- Initiatives
- Self-service templates
- Query language
- Eng intelligence
- Integrations layer
- On-call and ownership mapping
What people use each for
The jobs each tool is most often brought in to do.
Backstage
- An engineering organisation past roughly a hundred services where nobody can reliably answer who owns a given service at two in the morningnot Cortex
- A platform team enforcing golden paths, so a new service is scaffolded with logging, CI and security defaults already wired innot Cortex
- A company consolidating scattered READMEs and Confluence pages into docs that live beside the code and cannot silently rot unnoticednot Cortex
- A regulated business that needs an auditable register of every running service, its owner and its data classificationnot Cortex
Cortex
- A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot Backstage
- An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Backstage
- Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Backstage
- Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Backstage
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Backstage
- Backstage is a framework rather than a product: there is no supported turnkey install, so getting to a usable portal means a TypeScript and React project your team owns, hosts and upgrades forever.
- Upstream releases move quickly and plugin APIs have broken across major versions, so a customised deployment accumulates upgrade debt and teams routinely fall months behind on versions they cannot cheaply catch up on.
- The catalogue is only as good as the YAML descriptors engineers remember to write; without enforcement the register drifts out of date, and a developer portal nobody trusts is abandoned faster than one that never existed.
- Community plugin quality varies sharply, with many unmaintained or pinned to old core versions, so the plugin that made the business case may be the one blocking your next upgrade.
- Spotify Portal, the packaged commercial route, publishes no price at all and is quoted as a custom annual subscription, so the only cost you can actually forecast up front is the self-hosted one, which is the option with the largest hidden staffing bill.
Cortex
- Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.
- The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything.
- Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue.
- It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves.
- Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract.
Pricing, plan by plan
Backstage
Free- Backstage (open source)Free
- Apache 2.0 licence
- Software catalogue, templates, TechDocs and search
- Full plugin ecosystem
- Spotify Portal for Backstage$undefined/year
- Packaged commercial distribution from Spotify
- Spotify premium plugins including Soundcheck and Insights
- Simplified setup and managed upgrade path
Cortex
On request- Cortex$undefined/year
- Service catalogue and ownership mapping
- Scorecards and initiatives
- Self-service templates
Which should you pick?
Choose Backstage if
- You need software catalogue.
- You want to start without paying.
- You work on Web, Self-hosted, Linux, Docker, Kubernetes.
- You also want software templates.
Choose Cortex if
- You need service catalogue.
- You work on Web, API.
- You also want scorecards.
Questions people ask
- Is Backstage or Cortex better?
- Neither clearly leads. Backstage starts at Free and Cortex at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Backstage or Cortex?
- Backstage has a free tier; the other does not. Paid plans start at Free for Backstage and On request for Cortex.
- Does Backstage or Cortex run on more platforms?
- Backstage runs on Web, Self-hosted, Linux, Docker, Kubernetes. Cortex runs on Web, API.
- Can I use Backstage for free?
- Yes. Backstage has a free tier, so you can try it without paying. Cortex starts at On request.
- What is Backstage best used for?
- Backstage is most often used for an engineering organisation past roughly a hundred services where nobody can reliably answer who owns a given service at two in the morning, a platform team enforcing golden paths, so a new service is scaffolded with logging, ci and security defaults already wired in, a company consolidating scattered readmes and confluence pages into docs that live beside the code and cannot silently rot unnoticed, a regulated business that needs an auditable register of every running service, its owner and its data classification. Of those, an engineering organisation past roughly a hundred services where nobody can reliably answer who owns a given service at two in the morning and a platform team enforcing golden paths, so a new service is scaffolded with logging, ci and security defaults already wired in are not what Cortex is typically brought in for.
- What can Backstage do that Cortex cannot?
- Backstage covers Software catalogue, Software templates, TechDocs, Plugin architecture. Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates.
Answered from the vendors’ own pages
Backstage: Is Backstage free?
The project is Apache 2.0 with no licence fee. The real cost is engineering time; teams commonly dedicate one to two engineers permanently to running it.
Cortex: How is Cortex different from Backstage?
Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.
Backstage: Do I need to write code to use it?
Yes. Configuring and extending a Backstage application is a TypeScript and React project. This is the single most common misjudgement buyers make.
Cortex: Is pricing published?
No. Cortex requires a sales conversation and prepares a custom proposal.
Backstage: What is Spotify Portal for Backstage?
A commercial distribution from Spotify with premium plugins and support, generally available since October 2025 and sold as a quoted annual subscription with no published price.
Cortex: Can it self-host?
It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.
Backstage: Who owns the project?
Spotify created and open sourced it; it is now a CNCF project, so the upstream roadmap is not solely Spotify controlled.
Cortex: What is the main adoption risk?
Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.
Related pages
Other head to heads
- Backstage vs Harness
- Backstage vs OpsLevel
- Backstage vs Tilt
- Backstage vs Ansible
- Backstage vs Frappe
- Backstage vs Refact
- Backstage vs Soketi
- Backstage vs Visual Studio Code
- Backstage vs Penpot
- Backstage vs GNU Emacs
- Backstage vs Bazel
- Backstage vs Argo CD
- Backstage vs Atlantis
- Backstage vs Blacksmith
- Backstage vs Coder
- Backstage vs Garden
- Backstage vs GitLab CI/CD
- Backstage vs Earthly
- Backstage vs Spacelift
- Backstage vs Depot
- Backstage vs Nix
- Backstage vs SonarQube
- Backstage vs Keycloak
- Backstage vs Ona (formerly Gitpod)
- Backstage vs Vite
- Backstage vs Namespace
- Backstage vs Nixpacks
- Backstage vs Octopus Deploy
- Backstage vs Okteto
- Cortex vs Harness
- Cortex vs OpsLevel
- Cortex vs Tilt
- Cortex vs Ansible
- Cortex vs Frappe
- Cortex vs Refact
- Cortex vs Soketi
- Cortex vs Visual Studio Code
- Cortex vs Penpot
- Cortex vs GNU Emacs
- Cortex vs Bazel
- Cortex vs Argo CD
- Cortex vs Atlantis
- Cortex vs Blacksmith
- Cortex vs Coder
- Cortex vs Garden
- Cortex vs GitLab CI/CD
- Cortex vs Earthly
- Cortex vs Spacelift
- Cortex vs Depot
- Cortex vs Nix
- Cortex vs SonarQube
- Cortex vs Keycloak
- Cortex vs Ona (formerly Gitpod)
- Cortex vs Vite
- Cortex vs Namespace
- Cortex vs Nixpacks
- Cortex vs Octopus Deploy
- Cortex vs Okteto