Softwr

Developer Tools · head to head

Backstage vs Ory Kratos

Backstage logo

Backstage

Developer Tools

Open source internal developer portal framework created and open sourced by Spotify

From
Free
Rated
-
Ory Kratos logo

Ory Kratos

Cybersecurity

Headless identity and user management API

From
Free
Rated
-

The short version

  • 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.; Ory Kratos headless means you build every screen, which is significant work compared with a hosted login page
  • They diverge on capability: Backstage covers Software catalogue, Ory Kratos covers Headless API.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Backstage and Ory Kratos actually diverge.

Attributes where Backstage and Ory Kratos differ
AttributeBackstageOry Kratos
Pricing modelOpen source, no licence feeOpen-source self-hosted, with a paid managed network
PlatformsWeb, Self-hosted, Linux, Docker, KubernetesLinux, Docker, Kubernetes, Self-hosted
CategoryDeveloper ToolsCybersecurity

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

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 Ory Kratos

  • Headless API
  • Self-service flows
  • Multi-factor authentication
  • Pluggable identity schemas

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 Ory Kratos
  • A platform team enforcing golden paths, so a new service is scaffolded with logging, CI and security defaults already wired innot Ory Kratos
  • A company consolidating scattered READMEs and Confluence pages into docs that live beside the code and cannot silently rot unnoticednot Ory Kratos
  • A regulated business that needs an auditable register of every running service, its owner and its data classificationnot Ory Kratos

Ory Kratos

  • Products needing complete control over the look and flow of authenticationnot Backstage
  • Applications that must not hand user identity data to a third partynot Backstage
  • Teams building identity as infrastructure across several servicesnot 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.

Ory Kratos

  • Headless means you build every screen, which is significant work compared with a hosted login page
  • More moving parts than a monolithic IAM: Kratos handles identity, and OAuth2 needs Ory Hydra alongside
  • Documentation assumes real familiarity with identity concepts and is not a gentle introduction
  • Self-hosting identity carries the security and availability burden that hosted providers absorb

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

Ory Kratos

Free
  • Self-hostedFree
    • Full identity server
    • All flows
    • Community support

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 Ory Kratos if

  • You need headless api.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Self-hosted.
  • You also want self-service flows.

Questions people ask

Is Backstage or Ory Kratos better?
Neither clearly leads. Backstage starts at Free and Ory Kratos at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Backstage or Ory Kratos?
Backstage starts at Free and Ory Kratos at Free.
Does Backstage or Ory Kratos run on more platforms?
Backstage runs on Web, Self-hosted, Linux, Docker, Kubernetes. Ory Kratos runs on Linux, Docker, Kubernetes, Self-hosted.
Can I use Backstage for free?
Both have a free tier, so you can try either at no cost before committing.
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 Ory Kratos is typically brought in for.
What can Backstage do that Ory Kratos cannot?
Backstage covers Software catalogue, Software templates, TechDocs, Plugin architecture. Ory Kratos covers Headless API, Self-service flows, Multi-factor authentication, Pluggable identity schemas.

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.

Ory Kratos: Is Ory Kratos free?

Yes, open source and free to self-host. Ory Network is a paid managed service.

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.

Ory Kratos: What does headless mean here?

Kratos provides identity flows as APIs and no user interface. You build the login, registration and recovery screens yourself.

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.

Ory Kratos: Does Kratos do OAuth2?

No. Kratos handles user identity; OAuth2 and OpenID Connect provider functionality is Ory Hydra, a separate component.

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.

Share

Related pages

Other head to heads