Component cost framework

Developer portal cost in 2026: from $0 to $400k+ depending on approach

The developer-portal cost question is really a build-approach question. Five distinct approaches, dramatically different cost shapes, the same goal of giving developers a unified surface to find services, ship code, and check status.

No portal

$0-$20k / yr

Spreadsheet or wiki page. Viable under 50 services with discipline; not viable at scale.

Hosted / commercial

$30k-$300k / yr

Hosted Backstage, Port, Cortex, OpsLevel, Compass. The most common at 50-500 engineers.

Self-host / build

$200k-$1.2M+ / yr

Self-hosted Backstage or in-house framework. Higher per-year but lower per-dev at scale.

The five distinct approaches

The developer portal is the layer of the Internal Developer Platform where engineers find services, owners, runbooks, scorecards, documentation, scaffolding actions, deployment status, and the rest of the platform's surface area. It is the most visible part of the IDP and the part most engineers actually interact with daily.

There are five distinct approaches to delivering one, with dramatically different cost shapes:

No portal. A spreadsheet or wiki page maintained manually. Viable under 50 services.
Hosted Backstage. Managed Backstage from Roadie, Frontside, Liatrio, or others. $30k to $300k a year subscription.
Commercial IDP. Port, Cortex, OpsLevel, Compass, Humanitec (in part). $20k to $250k a year subscription.
Self-hosted Backstage. Open-source Backstage operated by your platform team. $0 licence, $200k to $1.2M a year all-in.
In-house framework. Custom-built portal not based on Backstage. $400k to $1.5M+ a year all-in.

The right approach is not the cheapest one in absolute terms; it is the one whose cost shape and capability profile fits your organisation's size, platform-team capacity, and strategic posture.

No portal: when it works

"No portal" is a real option below 50 services. The configuration that makes it work:

A maintained spreadsheet or wiki page listing every service with its owner, GitHub link, runbook link, primary on-call schedule.
A discipline of quarterly review where the platform team and service owners refresh the data together.
A bookmarks bar with the major internal tools (CI/CD UI, observability UI, secrets-manager UI, cloud-provider console).
CI/CD that emits deployment events to a shared Slack channel so engineers have ambient awareness of what is shipping.
An expectation that engineers can ask "who owns this" in Slack and get an answer within an hour during business hours.

Below 50 services, this works fine. The cost is essentially the platform engineer's time on the quarterly review, typically 4 to 8 hours per quarter per platform engineer. Annual cost: $20k to $40k of platform-engineer time, or effectively zero if amortised across other platform-engineering responsibilities.

Above 50 services, the cost of not having a portal starts to climb fast. Engineers spending several hours a week on "who owns this", "where is the runbook", "is this service deployed to prod" questions adds up to material productivity loss. At 80 services, the case for a real portal is usually clear; at 150, it is unambiguous.

Hosted Backstage and commercial IDP

The most common configuration for 50 to 500-engineer organisations is hosted Backstage (Roadie, Frontside, Liatrio) or a commercial IDP (Port, Cortex, OpsLevel, Compass). Cost shape:

Subscription: $20k to $300k a year depending on tier and entity count.
Platform-engineer time for integration setup, custom plugins or actions, and adoption work: 0.3 to 0.7 FTE typically.
Cloud infrastructure: negligible (the vendor hosts).

Year-one total for a 100-engineer organisation: about $120k to $250k. Steady-state (year 3+) total: about $80k to $200k. The platform-engineer time line is mostly fixed across vendor choices; the subscription is the variable.

For per-vendor cost framings see /backstage-hosted-cost, /port-cost, /cortex-cost, /opslevel-cost, /compass-cost, /humanitec-cost.

Self-hosted Backstage

Self-hosted Backstage is the right choice for organisations with mature platform teams (8+ engineers) and a strategic preference for open-source substrate. Cost shape:

Licence: $0 (Apache-2.0).
Platform-engineer time for operations, plugin authoring, and upgrades: 1 to 2 FTE typically.
Cloud infrastructure: $15k to $80k a year for the Backstage app, database, search index.

Year-one total: about $200k to $1.2M. Year 3+ steady-state: about $250k to $500k. The headcount line dominates. The per-developer-served cost crosses below the hosted alternative at about 300 product engineers because the operations cost amortises across more engineers; below 300 engineers, hosted is usually cheaper.

For full self-hosted Backstage cost framework see /backstage-cost.

In-house framework

Building a custom developer portal not based on Backstage is the most expensive option and is rarely the right call. The build path means re-implementing the catalogue, scaffolder, documentation surface, integration framework, plugin model, and authentication that Backstage already provides for free. Realistic year-one cost:

Two to four platform engineers working largely full-time on the build for the first year.
Ongoing two to four platform engineers of operation and feature work long-term.
Cloud infrastructure of $30k to $100k a year.

Year-one total: $500k to $1.5M+. Year 3+ steady-state: $500k to $1.0M+. The headcount line absolutely dominates.

When is this worth it? Almost never below 300 product engineers. Above 300, the build can amortise across enough users to be reasonable; the platform team usually has the staffing to maintain it; and the strategic differentiation can be real. The honest set of organisations where in-house framework is the right call is small: very large engineering organisations with strong strategic interest in owning the developer-portal substrate, organisations with unusual architectural patterns that no off-the-shelf product supports well, and organisations whose internal-tooling track is genuinely a competitive advantage.

Cost comparison at 100 engineers

For a 100-engineer organisation, year-one total cost by approach:

No portal: $20k to $40k. Not really viable above 80 services.
Hosted Backstage: $120k to $200k.
Commercial IDP: $110k to $250k.
Self-hosted Backstage: $300k to $600k.
In-house framework: $600k to $1.2M+.

At 100 engineers, hosted and commercial dominate on cost. Self-hosted is justifiable for organisations that already run mature platform teams and want open-source substrate. In-house framework is hard to justify at this scale.

Cost comparison at 500 engineers

At 500 engineers, the picture shifts:

Hosted Backstage: $150k to $400k (subscription scales with entities and seats).
Commercial IDP: $150k to $500k (subscription scales similarly).
Self-hosted Backstage: $300k to $700k (operations cost amortises across more engineers, per-developer-served cost lower than hosted).
In-house framework: $500k to $1.2M (build amortises across more users).

At 500 engineers, self-hosted Backstage starts to look competitive on absolute cost. The per-developer-served cost favours self-hosted at this scale. The decision becomes strategic (open substrate vs proprietary) and capacity-based (do you have 8+ platform engineers to absorb the operations cost?) more than cost-driven.

The decision matrix

A quick decision framework for choosing between approaches:

Under 50 services: no portal works.
50 to 500 product engineers, small platform team (under 8): hosted Backstage or commercial IDP at standard tier.
Already heavy on Atlassian: Compass for cost efficiency.
Flexible entity model is priority: Port.
Scorecards are priority: Cortex.
Team Topologies alignment is priority: OpsLevel.
300+ engineers, mature platform team of 8+: self-hosted Backstage for cost efficiency and substrate ownership.
1000+ engineers, very strong platform team, strategic interest in owning the substrate: in-house framework becomes defensible.

Cost bands triangulated from vendor public marketing, the Backstage project, CNCF Platforms Working Group material, and Gartner peer-community signal. Verified 2026-05-11.

Frequently asked questions

How much does a developer portal cost?

It depends entirely on the build approach. Self-hosted Backstage: $200k to $1.2M a year all-in, mostly headcount. Hosted Backstage: $30k to $300k a year subscription plus the same platform-team integration work. Commercial IDP (Port, Cortex, OpsLevel, Compass): $20k to $250k a year subscription plus integration. In-house framework (no Backstage, no commercial): $400k to $1.5M a year fully loaded. 'No portal at all' is genuinely a valid option below 50 services and costs effectively zero. The headline cost range $0 to $400k+ reflects this spread.

When is the in-house framework path worth it?

Almost never below 300 product engineers. The in-house framework path means building a custom developer portal from scratch (not adopting Backstage), which means re-implementing the catalogue, scaffolder, documentation, integration framework, and plugin model that Backstage already provides for free. Above 300 product engineers, the build can amortise across enough internal users to be reasonable; the platform team usually has the staffing to maintain it; and the strategic differentiation can be real. Below that scale, in-house framework is one of the most expensive ways to deliver a developer portal and is rarely the right call.

What does "no portal at all" actually look like?

A spreadsheet or a wiki page that lists all services with owners and runbook links, updated by the platform team and the service owners on a quarterly review. A bookmarks bar with the most-used internal tools. CI/CD that emits deployment events to Slack so engineers know what is shipping. No catalogue UI, no scorecards, no automated entity-sync. This works fine up to about 50 services because the discovery problem the portal solves is genuinely manageable at that scale. Above 50 services, the cost of not having a portal (engineers spending hours per week on 'who owns this' questions) starts to exceed the cost of building or buying one.

How do I decide between Backstage and a commercial IDP for the portal?

Five-way decision matrix. (1) If platform team is small (under 5 engineers) and managed services are preferred: hosted Backstage or commercial IDP at standard tier. (2) If you want flexibility on the entity model: Port. (3) If scorecards are the strategic priority: Cortex. (4) If catalogue plus rubric with Team Topologies alignment: OpsLevel. (5) If you are already heavily on Atlassian: Compass. (6) If you have a mature platform team of 8+ engineers and want open-source substrate: self-hosted Backstage. Subscription cost is a smaller decision factor than fit at this point in the IDP market.

What is the typical year-1 deployment cost for a developer portal at 100 engineers?

For a 100-engineer organisation choosing hosted Backstage at standard tier: $40k to $90k subscription plus $80k to $150k of platform-engineer time on integration, custom plugins, and adoption work. Total year-one: $120k to $240k. For a commercial IDP at similar tier: $30k to $100k subscription plus $80k to $150k of platform-engineer time. Total: $110k to $250k. For self-hosted Backstage from scratch: $0 subscription plus $300k to $600k of platform-engineer time across two to three engineers. Total year-one: $300k to $600k. For 'no portal' upgraded with a spreadsheet and discipline: $20k to $40k of platform-engineer time on the manual maintenance. The buy options are dramatically cheaper at year one for a 100-engineer organisation.

What does developer portal cost look like at steady state (year 3+)?

Hosted Backstage or commercial IDP: subscription stays roughly the same as year one, platform-engineer time drops to about 0.3 to 0.5 FTE for plugin maintenance, integration upkeep, and continued adoption work. Total: $80k to $200k a year. Self-hosted Backstage: $0 subscription, 1 to 2 FTE of ongoing operational and plugin work, $30k to $80k of cloud infrastructure. Total: $250k to $500k a year. In-house framework: 2 to 4 FTE of ongoing work plus cloud. Total: $500k to $1.0M+ a year. The cost crossover where self-hosted starts to beat hosted on per-developer-served cost typically happens around 300 product engineers.

Service catalogue cost

Adjacent component.

Golden paths cost

Adjacent component.

Self-hosted Backstage

The framework all this feeds into.

Run your numbers

Plug in your specific inputs.