Softwr

Developer Tools · head to head

Backstage vs Cilium

Backstage logo

Backstage

Developer Tools

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

From
Free
Rated
-
Full reviewWebsite
Cilium logo

Cilium

Cloud

eBPF-based networking, observability and security for Kubernetes

From
Free
Rated
-
Full reviewWebsite

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.; Cilium requires a recent Linux kernel, which rules out older distributions and some managed environments
  • They diverge on capability: Backstage covers Software catalogue, Cilium covers eBPF datapath.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Backstage and Cilium actually diverge.

Attributes where Backstage and Cilium differ
AttributeBackstageCilium
PlatformsWeb, Self-hosted, Linux, Docker, KubernetesKubernetes, Linux
CategoryDeveloper ToolsCloud

Identical on both: starting price (Free), pricing model (Open source, no licence fee), 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 Cilium

  • eBPF datapath
  • Identity-based policy
  • Hubble observability
  • Sidecar-free mesh

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

Cilium

  • Kubernetes networking at a scale where iptables-based CNI performance degradesnot Backstage
  • Network policy expressed on workload identity rather than fragile IP rulesnot Backstage
  • Seeing which services actually talk to each other, and what policy is droppingnot 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.

Cilium

  • Requires a recent Linux kernel, which rules out older distributions and some managed environments
  • eBPF is genuinely hard to debug when it misbehaves, and the skill is rare on most teams
  • Broad scope — CNI, policy, mesh, observability — means the learning curve covers several domains at once

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

Cilium

Free
  • CiliumFree
    • Full functionality
    • No usage limits
    • 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.
Backstage review

Choose Cilium if

  • You need ebpf datapath.
  • You want to start without paying.
  • You work on Kubernetes, Linux.
  • You also want identity-based policy.
Cilium review

Questions people ask

Is Backstage or Cilium better?
Neither clearly leads. Backstage starts at Free and Cilium at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Backstage or Cilium?
Backstage starts at Free and Cilium at Free.
Does Backstage or Cilium run on more platforms?
Backstage runs on Web, Self-hosted, Linux, Docker, Kubernetes. Cilium runs on Kubernetes, Linux.
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 Cilium is typically brought in for.
What can Backstage do that Cilium cannot?
Backstage covers Software catalogue, Software templates, TechDocs, Plugin architecture. Cilium covers eBPF datapath, Identity-based policy, Hubble observability, Sidecar-free mesh.

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.

Cilium: Is Cilium free?

Yes, open source and CNCF-graduated. Isovalent sells an enterprise distribution and support.

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.

Cilium: What does eBPF change?

It lets Cilium run packet-processing programs inside the kernel instead of relying on iptables rule chains, which behave poorly as the number of services grows.

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.

Cilium: Does Cilium replace a service mesh?

It can cover much of what a mesh does without sidecars, though full mesh feature sets still favour Istio or Linkerd.

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

More on Backstage

More on Cilium

Keep looking

Other head to heads