Your platform team finally has budget for an internal developer platform. The question on the procurement form is simple — which IDP vendor do you buy from in 2026, what does it cost, and who should you skip? The honest answer changed this year: the category quietly shrank. Roadie, the main commercial Backstage host, has closed its developer-portal plans to new subscribers. Atlassian is steering Compass customers toward DX. That leaves four serious answers for a new buyer: Port (catalog-first SaaS), Humanitec (orchestrator), OpsLevel (governance-first portal), or self-hosting Backstage (the Apache-2.0 framework). Every price and claim below was verified from vendor pages on 2026-09-22 — re-verify before you sign anything. We have no financial relationship with any vendor listed; links are direct and untracked.

TL;DR — the 30-second verdict

Your situation Pick Why
Nobody knows what services exist or who owns them; you want to start this week without procurement Port Free tier with 15 seats and 10K entities, no time limit; paid starts at $30/seat/mo
Environment provisioning takes days and four Jira tickets Humanitec The only one of the three SaaS options that actually provisions environments — accept the price
Audit readiness, production-readiness checks, and scorecards are the deliverable OpsLevel Opinionated governance that works on day one — but pricing is quote-only
You have platform engineers on staff and want zero license cost and total control Backstage $0 license, CNCF Incubation — but budget 1–2 FTEs, not a subscription

The 2026 market reality: the shortlist shrank

Two years ago, "IDP vendors" was a crowded comparison table — Port, Humanitec, OpsLevel, Backstage, Roadie, Cortex, Atlassian Compass, and a long tail. In 2026 the buyer-relevant field contracted, and the survivors all repositioned around AI agents. Verified signals from vendor pages on 2026-09-22:

Signal What we verified What it means for you
Roadie closed portal sales Both developer-portal plans (Teams $24/dev/mo, Growth custom) are marked "Existing subscribers only" on roadie.io/pricing; the company now sells "Context" — structured context for AI agents The main managed-Backstage option is off the table for new buyers — self-host or pick a SaaS portal
Compass is transitioning Atlassian's own banner: "Compass scorecards and catalog functionality will transition into DX" (atlassian.com/software/compass) Do not start a new Compass deployment in 2026; migration questions belong to your Atlassian account manager
Port repositioned Port now markets itself as an "Agentic SDLC Platform" — Context Lake, AI agents, governance for agent workflows (port.io) The catalog vendor you evaluated in 2024 is selling a different product now — evaluate what shipped, not the demo
Humanitec bundles an exit hatch Humanitec maintains Score, the open-source workload spec, alongside its commercial Orchestrator Your developer-facing workload definition has a portable, Apache-2.0 format even if the orchestrator does not
OpsLevel leaned into AI agents too OpsLevel's "Context Layer (MCP)" pitch: "Give your AI agents the curated answer" (opslevel.com) Governance catalogs are being reframed as the context source for agents — same product, new buyer pitch
Backstage keeps shipping v1.55.1 published 2026-09-21; Apache-2.0, CNCF Incubation, ~34.4K stars (GitHub releases) The framework is alive and maintained — the cost is people, not license

One more signal worth naming: community traction. None of the commercial IDP vendors sustains front-page discussion on Hacker News — recent loud IDP-adjacent threads are OSS toolkits like Koreo and OpenChoreo, not vendors. This category sells through sales calls and pilots, not through community wisdom. Every vendor below will get you a demo; almost none will publish a price without a call. Demand a proof-of-concept in your environment, with your data, before any commitment.

What you are actually buying: three shapes of product

"IDP" is a marketing bucket. For a buyer, there are three distinct products hiding inside it, and picking the wrong shape is the expensive mistake — not the vendor brand. We cover the state-model mechanics in depth in Port vs. Humanitec vs. OpsLevel: the state-model analysis; the buyer's summary:

  • Catalog-first portals (Port, OpsLevel): metadata, visibility, scorecards, and self-service actions layered over the systems you already run. Your CI/CD and Terraform keep doing the real work; the portal reads and triggers. Lowest risk, fastest to value, weakest environment-provisioning story.
  • Orchestrators (Humanitec): the tool computes and applies your environments — it is the authoritative source of truth for what runs where. It solves the provisioning-ticket problem directly, and creates the deepest lock-in when it does.
  • Frameworks (Backstage): you build the product on an OSS core. Infinite flexibility, zero license fees, and a permanent engineering bill — our teardown of that trade-off is in The Backstage Trap.

The comparison matrix

Vector Port Humanitec Backstage OpsLevel
Product shape Catalog + self-service + agentic workflows (SaaS) Platform Orchestrator + Portal (SaaS or self-hosted) Framework — you build the portal (OSS) Governance catalog + scorecards (SaaS)
License Proprietary SaaS Proprietary (Orchestrator/Portal); Score spec is Apache-2.0 Apache-2.0, CNCF Incubation Proprietary SaaS
Pricing model Per seat, billed annually, tiered by entities/runs Per tier by users/projects; Enterprise and self-hosted custom $0 license Custom quote based on developer count
Verified entry price $0 (15 seats) → $30/seat/mo $1,979/mo (5 users, annual billing) $0 (plus your engineers) Quote-only (Standard: up to 50 users)
Free way in Yes — Free plan, no time limit Free trial (no credit card) + MVP program Yes — it is the product Product tours; pilot on request
Lock-in risk Medium — blueprints/schemas are yours but SaaS-shaped High — orchestration logic lives in the tool Low vendor risk, high people risk Low — read-mostly governance rules export easily
Who maintains it Port (SOC 2, ISO 27001) Humanitec (SOC 2 Type II) You (with CNCF ecosystem) OpsLevel
Sweet spot Visibility + self-service without platform-team headcount Environment orchestration at companies allergic to ticket ops Orgs with a funded platform team and strong opinions Governance, audits, and production readiness programs

Verified pricing, tier by tier

All prices below were captured from the vendors' own pricing pages on 2026-09-22. Prices change — treat these as the negotiation baseline, not a quote.

Port — the only published price sheet in the category

Plan Price (verified 2026-09-22) Seats Capacity and limits Support / SLA
Free $0, no time limit 15 10K entities, 400 automation runs, community support Community (Slack, docs)
Basic $30/seat/mo, billed annually — sold as a 50-seat package 50 50K entities, 400 runs; unlimited AI-agent usage with your own LLM Commercial; 6h critical; 99.8% SLA
Standard $40/seat/mo, billed annually 200 250K entities, 1.6K runs, 5 workspaces, SSO, dynamic permissions Commercial; 6h critical; 99.8% SLA
Enterprise Custom — platform fee plus per-seat Unlimited 1M+ entities, 8K+ runs, 20 workspaces, SCIM, Private Link, IP allowlist Dedicated; 4h critical; 99.9% SLA

Humanitec — flat tiers, priced per organization size

Plan Price (USD, verified 2026-09-22) Users / projects What you get
Teams $1,979/mo annual billing; $2,199/mo monthly 5 users; 1 project, up to 5 environments Orchestrator core; email support; public office hours; free trial, no credit card
Pro $4,950/mo annual billing; $4,999/mo monthly 50 users; up to 10 projects, unlimited environments RBAC, sandbox organization, standard support, monthly office hours with a platform architect
Enterprise Custom Unlimited SAML, audit logs, premium support, dedicated platform architect
Self-hosted Custom Unlimited For regulated industries and private-cloud deployments; installation support and onboarding

Humanitec also runs an MVP Program: a platform architect sets up the Orchestrator with your stack and deploys your first app end-to-end in two weeks, with the fee credited toward the license if you continue. If you go this route, put that credit clause in writing before the engagement starts.

OpsLevel — quote-only, two plans

Plan Users Included Pricing
Standard Up to 50 Unlimited cataloged components, AI-powered catalog engine, rubrics, turnkey integrations, custom checks, self-service actions, Slack/MS Teams Custom quote, based on developer count
Enterprise Unlimited Custom integrations, customizable UI, dedicated Customer Success Manager and Support Architect, beta access Custom quote

Backstage — $0 license, people-priced

Apache-2.0, a CNCF Incubation project started at Spotify, with v1.55.1 published 2026-09-21. There is no license line item; the real cost is 1–2 full-time platform engineers to own upgrades, plugins, and the catalog ingestion pipeline. If your team cannot staff that, the free option becomes the expensive one — the failure modes are documented in The Backstage Trap, and the current release cadence is covered in our Backstage 1.55.0 analysis.

What it costs at real team sizes

List-price arithmetic, annualized — computed, not estimated, from the tiers above:

Team size Port Humanitec OpsLevel Backstage
50 engineers Basic, 50-seat package: $18,000/yr Pro, 50 users included: $59,400/yr ($4,950 × 12) Standard (fits 50): quote $0 license + 1–2 FTEs
200 engineers Standard: $96,000/yr ($40 × 200 × 12) Enterprise: quote Enterprise: quote $0 license + platform team

The pricing models behave very differently as you scale. Port's per-seat model means a 50-engineer org pays roughly $360/engineer/year at the Basic tier. Humanitec's tier model charges for included capacity, not headcount: at the Teams tier (5 users) you pay an effective $395.80 per user per month; at Pro (50 users included) it drops to $99 per user per month. Humanitec rewards scale and punishes small teams — a 5-person platform pilot pays Porsche money for a five-seater. Port lets a 12-person team run free indefinitely and graduate to Basic when procurement catches up. OpsLevel and Humanitec Enterprise live behind a sales call — which is itself a signal about the deal size they expect.

How to choose, in one diagram

flowchart TB
    START["IDP budget approved: pick your lane"]
    START --> A["Catalog pain: nobody knows what exists"]
    START --> B["Provisioning pain: environments take days"]
    START --> C["Control: platform engineers on staff"]
    A --> D{"Governance and audits the deliverable?"}
    D -->|"yes"| E["OpsLevel"]
    D -->|"no"| F["Port: Free tier, then Basic"]
    B --> G["Humanitec: negotiate the MVP program"]
    C --> H["Backstage: budget 1-2 FTEs, not a license"]