Backstage Is Not Free: The Real TCO of Building vs Buying an Internal Developer Platform Backstage has a $0 license fee. It also requires 2-3 senior platform engineers to maintain it full-time. At a loaded salary of $150,000 per engineer, that is $300,000 to $450,000 per year before you write a single line of custom plugin code. This is the IDP cost blindspot. Engineering leaders compare "free open source" against a vendor quote and conclude the build is cheaper. They are comparing a license fee against a total cost of ownership. Those are not the same number, and the gap grows every year. The Hidden Invoice in Your Open-Source IDP When Spotify open-sourced Backstage in 2020, they released code that took 200 engineers two years to build internally. They did not release the institutional knowledge required to operate it. That knowledge lives in your platform team, and it costs money every month. A Backstage deployment at a 200-person engineering org has four cost centers that rarely appear in the initial business case. The infrastructure cost is real but small: a managed Kubernetes cluster for Backstage, a PostgreSQL instance, and observability tooling runs $12,000 to $24,000 per year. The engineering cost dwarfs it. Plugins are where the maintenance burden hides. Backstage has 300+ community plugins, but fewer than 40% receive updates within six months of a new Backstage release. Every custom plugin your team writes becomes a maintenance liability on the next upgrade cycle. Building Costs More Than You Budgeted For We tracked three years of build costs for a 200-developer organization deploying Backstage from scratch. The numbers below use $150,000 loaded cost per engineer. Cost Component Year 1 Year 2 Year 3 Platform engineering (2.5 FTE) $375,000 $375,000 $375,000 Infrastructure $18,000 $20,000 $22,000 Custom plugin development $90,000 $45,000 $45,000 Upgrade cycles (2 major/yr) $15,000 $30,000 $30,000 Adoption programs and docs $45,000 $20,000 $15,000 Total $543,000 $490,000 $487,000 Year 1 is the most expensive because you are building. Years 2 and 3 are still expensive because you are maintaining. The three-year TCO is $1,520,000. The upgrade cost compounds specifically because each major Backstage release requires auditing every custom plugin for compatibility. We measured 2 to 5 days of engineering time per custom plugin per release cycle. An org with 10 custom plugins spends 20 to 50 engineer-days per year just on upgrade testing, before any new features ship. Adoption lag adds hidden cost that is easy to miss. Internal builds typically reach 60% developer adoption in 18 to 24 months. A platform that half the org ignores has a cost-per-active-user that is double what the spreadsheet shows. This is why developer portal adoption metrics matter from day one. Buying Costs Less Than You Fear Commercial IDP vendors have spent the last four years productizing exactly what Backstage makes you build yourself: catalog UI, software templates, tech docs rendering, and integrations with the 20 tools every engineering org uses. The pricing is more predictable than most engineering leaders expect. Platform 100 Developers 300 Developers 500 Developers Notes Port $15,000/yr $30,000/yr $48,000/yr Per-seat model Cortex $20,000/yr $40,000/yr $60,000/yr Per-seat model Backstage (managed) $18,000/yr $36,000/yr $55,000/yr Roadie, Spotify managed Backstage (self-hosted) $543,000 Y1 $543,000 Y1 $543,000 Y1 Engineering cost dominates For a 200-developer org, Port or Cortex runs $24,000 to $35,000 per year. That is 6% of what a full Backstage build costs in Year 1. Even at Year 3, when build costs stabilize, commercial pricing is 5 to 7% of the build TCO. The tradeoff is customization depth. Commercial platforms give you 80% of what Backstage can do, out of the box, in 30 days. The remaining 20% is where some orgs legitimately need the build path. Negotiation works here. Most commercial IDP vendors will reduce list price 20 to 30% for multi-year contracts. The $48,000 quote for 500 developers often becomes $34,000 with a two-year commitment. The Crossover Point: A Decision Framework for Engineering Leaders The build vs buy decision has a clean decision tree once you know three numbers: developer count, required customization depth, and existing platform engineering headcount. Buy wins at under 50 developers in almost every case. The per-developer economics do not support a dedicated platform engineering team at that scale, and commercial tools onboard in weeks. Platform engineering for early-stage teams covers this threshold in detail. Build wins when three conditions hold simultaneously: your org is above 500 developers, you have specific workflow automation requirements that commercial tools cannot handle, and you already have a 3-person platform team. That combination makes Backstage worth the maintenance cost. For the 50 to 500 band, which covers most engineering orgs, the default answer is buy unless you can articulate what specific functionality your org needs that no commercial tool provides. "We want more control" is not that articulation. It is a feeling that costs $400,000 per year to honor. Running Your Own TCO Calculation The TCO Model for IDP Investment (we call it the 3-3-3 Framework: 3 years, 3 cost centers, 3 org sizes) takes 20 minutes to run with your actual numbers. Input 100-Developer Org 500-Developer Org Platform engineers required (FTE) 1.5 3.0 Loaded engineer cost $150,000 $150,000 Annual engineering cost $225,000 $450,000 Infrastructure cost $15,000 $25,000 Plugin and upgrade cost $40,000 $80,000 Annual build TCO $280,000 $555,000 Commercial alternative $18,000-25,000 $48,000-60,000 Build premium 11-15x 9-11x The build premium rarely drops below 5x even at enterprise scale, because engineering cost scales with org complexity, not just headcount. The one scenario where build TCO approaches commercial pricing: an org above 1,000 developers that already employs a dedicated platform engineering team of 5 or more engineers. At that scale, the marginal cost of Backstage maintenance becomes small relative to the team that was already funded. But that team was funded to solve platform problems, not to maintain an IDP. That opportunity cost belongs in the model too. Cloud cost allocation across platform teams applies the same TCO framework to infrastructure decisions. The math works the same way: hidden engineering costs make self-managed systems more expensive than they appear at license time. Before your next IDP budget conversation, run the 3-3-3 calculation with your actual loaded engineer cost. The number that comes out is usually the conversation-ender.