Softwr

Developer Tools · head to head

Backstage vs Cucumber

Backstage logo

Backstage

Developer Tools

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

From
Free
Rated
-
Full reviewWebsite
Cucumber logo

Cucumber

Testing

Behaviour-driven development testing framework that returned to community ownership after nine years under SmartBear

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.; Cucumber gherkin's plain-language layer adds a real maintenance burden, keeping feature files, step definitions and implementation code synchronised across a large suite is a known source of drift and duplicated effort.
  • They diverge on capability: Backstage covers Software catalogue, Cucumber covers Gherkin syntax.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Backstage and Cucumber actually diverge.

Attributes where Backstage and Cucumber differ
AttributeBackstageCucumber
PlatformsWeb, Self-hosted, Linux, Docker, KubernetesLinux, macOS, Windows
CategoryDeveloper ToolsTesting

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 Cucumber

  • Gherkin syntax
  • Step definition binding
  • Multi-language support
  • Living documentation
  • Tagging and scenario outlines
  • Reporting plugins

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

Cucumber

  • A team practising behaviour-driven development that wants shared, readable specifications between product owners and engineersnot Backstage
  • An organisation wanting living documentation that stays synchronised with actual test coverage rather than a separate specification documentnot Backstage
  • A QA team migrating acceptance tests from a proprietary BDD tool to an open source, community-governed alternativenot Backstage
  • A Java, JavaScript or Ruby project needing a mature BDD framework rather than building Gherkin-style parsing from scratchnot 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.

Cucumber

  • Gherkin's plain-language layer adds a real maintenance burden, keeping feature files, step definitions and implementation code synchronised across a large suite is a known source of drift and duplicated effort.
  • Ownership has moved twice in under a decade, from independent to SmartBear-owned to independent community ownership again, which should temper confidence in any specific long-range roadmap claim.
  • Non-technical stakeholders who are meant to read and write Gherkin scenarios often do not engage with them in practice, leaving the readability benefit unrealised while the maintenance cost remains.
  • Step definition reuse across a large feature file set can become tangled, with ambiguous step matching causing hard-to-debug failures as a suite grows.
  • As a community-owned project without a corporate backer's support infrastructure, enterprise buyers wanting a formal support contract have no vendor to buy one from, unlike some competing BDD tools still sold commercially.

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

Cucumber

Free
  • CucumberFree
    • Full functionality across Cucumber-JVM, Cucumber-JS, Cucumber-Ruby and other implementations
    • Community support via GitHub
    • Returned to independent community ownership in December 2024 after nine years connected to SmartBear

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 Cucumber if

  • You need gherkin syntax.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want step definition binding.
Cucumber review

Questions people ask

Is Backstage or Cucumber better?
Neither clearly leads. Backstage starts at Free and Cucumber at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Backstage or Cucumber?
Backstage starts at Free and Cucumber at Free.
Does Backstage or Cucumber run on more platforms?
Backstage runs on Web, Self-hosted, Linux, Docker, Kubernetes. Cucumber runs on Linux, macOS, Windows.
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 Cucumber is typically brought in for.
What can Backstage do that Cucumber cannot?
Backstage covers Software catalogue, Software templates, TechDocs, Plugin architecture. Cucumber covers Gherkin syntax, Step definition binding, Multi-language support, Living documentation.

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.

Cucumber: Is Cucumber owned by SmartBear?

No, not currently. SmartBear acquired Cucumber Ltd in 2019 but the open source project returned to independent community ownership in December 2024.

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.

Cucumber: Is Cucumber free?

Yes, entirely open source with no licence fee across all its language implementations.

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.

Cucumber: Does Cucumber replace Selenium or Appium?

No, Cucumber provides the Gherkin specification layer and step definition binding; the actual browser or mobile automation still needs a driver such as Selenium or Appium underneath.

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 Cucumber

Keep looking

Other head to heads