Backstage pricing in 2026: a $0 licence, and what self-hosting really costs
The Apache-2.0 licence is genuinely free. What costs money is the platform engineers who run it: on our planning model, 2 to 4 in year one is $468k to $936k of loaded salary at $234k each. Here is the arithmetic, with every input stated.
Backstage is the open-source developer-portal framework Spotify created, now a CNCF incubating project, and it has no licence fee at all: it is Apache-2.0 licensed, so the software costs $0, with no per-seat or per-entity charge. The real cost is operational. On our planning model, self-hosting it takes two to four platform engineers in year one, which at our senior loaded rate is $468k to $936k of loaded salary. If you want Spotify to run it for you, the first-party managed product, Spotify Portal for Backstage (generally available since October 2025), is sold as a custom annual subscription with no public list price. Third-party hosted Backstage is now effectively quote-only too: Roadie publishes a per-developer rate for one tier that is marked for existing subscribers only, and Frontside and Liatrio publish no rates at all (checked 27 Sep 2026; details on /backstage-hosted-cost). There is no per-seat "Backstage pricing" page because the software itself is free; what you are really pricing is who operates it.
What "Backstage cost" actually means
Backstage was created at Spotify and open-sourced in 2020. It was accepted into the CNCF on 8 September 2020 and moved to Incubating on 15 March 2022. Today it is the de facto reference implementation of an Internal Developer Platform front-end: a unified portal for the service catalogue, software templates, documentation, tech radar, and a long tail of plugins.
Because the licence is free, the search query Backstage cost is almost always asking the wrong thing. The right question is: what does it cost to run Backstage well enough that your product engineers will actually use it on a Tuesday afternoon? That is mostly a headcount number, with a small cloud-hosting line and a small but real upgrade-tax line on top. This page models the headcount line only, and says so.
The headcount line, broken down
Our planning estimate is that Backstage at year one needs the equivalent of two to four platform engineers working largely full-time. After the initial scaffolding, the first few plugins, and the integration with your authentication and source-control systems, we plan on one to two full-time-equivalents of ongoing effort, with the rest of the platform team contributing intermittently. These counts are our estimate; no public source publishes a Backstage staffing figure.
At our senior platform-engineer loaded rate of $234k per year (see /salary for how it is built), that is a year-one personnel line of $468k to $936k for two to four engineers, and a steady-state line of $234k to $468k for one to two. Most of the visible platform cost for a 100-developer organisation is the platform team itself, and the Backstage portion follows the same pattern.
What puts you at two engineers or at four
The low end fits an organisation that already has a mature platform team running other tooling and is adding Backstage as a unified front-end. Backstage becomes one engineer's primary focus and a fraction of others' time, and most plugin work is wrapping existing internal APIs rather than building from scratch.
The high end fits an organisation standing Backstage up from zero: no existing service-catalogue source of truth, scaffolder templates written from scratch, a fragmented cloud footprint to integrate with, and an adoption push to run (office hours, internal docs, scorecard pilots). That needs more engineers full-time, plus a fraction of a manager, plus the first batch of plugin development.
Cloud and infrastructure
Backstage itself is a Node application that scales horizontally with modest resource requirements. A typical production deployment is a small Kubernetes deployment, a small Postgres database, an object store for documentation artefacts, and an authentication integration. The hosting cost of the Backstage app itself is small next to the headcount line; we do not put a number on it because it depends entirely on your cloud and your existing shared infrastructure.
The catch is that Backstage is rarely the only thing you are running. If Backstage is fronting workflows that themselves spin up cloud resources (the scaffolder provisioning a new repository, a Helm chart, a database, an environment), the second-order cloud cost runs through whatever budget owns those resources. That is usually accounted for elsewhere, but a clean platform-cost picture should flag it.
The plugin economy
Backstage ships with a useful default plugin set (catalogue, scaffolder, TechDocs, search, Kubernetes) and a long tail of community plugins of variable quality. Most organisations of any size end up authoring custom plugins: typically a deeper integration with their identity provider, a plugin wrapping an internal API (deployments, environments, on-call rotations), and one or two integrations with third-party SaaS that the stock plugins do not cover.
In engineer-time at our senior loaded rate ($234k a year, so $4.5k an engineer-week and $20k an engineer-month): a simple read-only catalogue plugin runs about two to three engineer-weeks, or $9k to $14k. A scaffolder template (a working golden path) is four to six engineer-weeks, or $18k to $27k. A deep integration plugin with auth, error handling and tests is closer to two to three engineer-months, or $39k to $59k. The effort counts are our planning estimates. This time sits inside the platform team's headcount line above, not on top of it.
The upgrade tax
Per the Backstage versioning policy, the main release line ships monthly, on the Tuesday before the third Wednesday of each month, and the next line ships weekly on Tuesdays. Most upgrades are mechanical. Breaking-change cycles arrive periodically and touch every plugin you maintain, more so if you maintain many first-party plugins. Our planning estimate is one to two engineer-weeks per breaking-change cycle, and about 15 to 20 percent of one platform engineer's time devoted long-term to keeping Backstage core current.
The expensive failure mode is falling a long way behind upstream. The path back to current then costs more than staying current would have. The discipline that prevents this is committing to a regular upgrade cadence that follows the monthly main line and treating upgrade time as non-negotiable roadmap time, not as something to slip when product pressure rises.
Build versus hosted Backstage
Hosted Backstage offerings (Roadie, Frontside, Liatrio, others) remove the operating cost of running Backstage itself: install, upgrades, hosting infrastructure, identity-provider integration, and the on-call burden. They do not remove plugin authoring, content debt, or adoption work. For an organisation with a small platform team or limited Kubernetes operations experience, hosted Backstage often wins on cost in the early years. Most vendors publish no price, so the comparison starts with a quote; see /backstage-hosted-cost for the one published rate and how to weigh it against the engineer-time above.
With a larger platform team that authors significant numbers of plugins, the operating cost of self-hosted Backstage can fall below a hosted subscription. Where that crossover sits depends on your quote and your team.
How Backstage compares to commercial IDPs
Commercial Internal Developer Platforms (Port, Cortex, OpsLevel, Compass, Humanitec) usually need less engineer-time than self-hosted Backstage at year one because you skip the platform-engineer staffing needed for installation and plugin authoring. Later, when a self-hosted Backstage deployment is mature and the operating work is spread across a larger platform team, the cost per developer served can be lower than commercial IDP licences, especially at large organisations.
For dedicated cost framings of each commercial option see /port-cost, /cortex-cost, /opslevel-cost, /compass-cost, and /humanitec-cost. For the broader question see /build-vs-buy.
Honest caveats
A handful of things that get glossed over in Backstage adoption writing and that tend to bite teams in year two:
- Service-catalogue data is only valuable if it is fresh. Without a discipline of automating entity sync from source-of-truth systems, the catalogue drifts and engineers stop trusting it.
- TechDocs adoption needs writers, not just a publishing pipeline. The platform team rarely owns the writing; if no-one does, the docs section sits empty.
- The scaffolder templates need a maintenance owner. Templates rot faster than service code because they accumulate references to whichever frameworks were modern when the template was written.
- The plugin contribution model needs to be defined. If only the platform team can write plugins, plugin authoring becomes a bottleneck; if anyone can, the plugin quality varies wildly.
Bottom line
The Backstage licence is $0. On our planning model, self-hosting it is two to four platform engineers in year one ($468k to $936k of loaded salary at $234k each) and one to two engineers steady state ($234k to $468k a year). Hosting the app itself is a small line next to that. The upgrade tax is small but non-zero and best treated as scheduled roadmap time.
If those figures feel high and the alternative looks like one of the commercial IDPs, see the per-vendor pages (linked above) and run the numbers in /calculator. If they feel low, the most likely missing line is plugin development, which compounds across years and is easy to under-budget.
Licence, CNCF status and release cadence checked 25 October 2026 against the sources linked. Engineer counts and costs are our planning model at the senior loaded rate on /salary, not published figures. Sources: Backstage project site, github.com/backstage/backstage (Apache-2.0 licence), CNCF project page, Backstage versioning policy.