Backstage, Port and Cortex: Three Paths to the IDP
Actualizado: 2026-05-03
The term Internal Developer Platform (IDP) gained traction throughout 2023. The idea is sound: reduce developer cognitive load by giving them a unified portal to discover services, provision environments, run common workflows, and see their systems’ state. Three options dominate the conversation: Backstage[1] (Spotify, open source), Port[2] (commercial, low-code), and Cortex[3] (commercial, scorecards). This article is an honest comparison with criteria to choose.
What Problem an IDP Solves
Developers in mid-to-large organisations spend time on tasks that shouldn’t consume it:
- Discovering: “what service does X? where is the code? who maintains it?”
- Provisioning: “how do I request a DB? how do I spin up staging?”
- Repetitive workflows: “how do I rollback? how do I scale this?”
- Basic observability: “is my service OK? are there errors?”
An IDP centralises this in a portal that is the door to the internal ecosystem. The alternative is fragmentation: stale wikis, Slack channels, tribal knowledge.
Backstage: The Open-Source Standard
Backstage was born at Spotify and open-sourced in 2020. Today it’s a CNCF project with a large community.
Strengths: Pure open source (Apache 2.0); extensible via plugins; YAML-in-Git catalog; TechDocs for docs-as-code; large contributing community.
Weaknesses: High adoption curve (months to production); continuous maintenance (React app you operate); customisation requires code; discovery takes work.
Backstage is for companies with a dedicated platform team — minimum three people — and multi-year commitment.
Port: Low-Code and Faster
Port (Israeli, founded 2022) takes a radically different approach. Commercial SaaS with visual configuration.
Strengths: Setup in hours not months; dynamic catalog (automatic ingestion from AWS, GitHub, Kubernetes, Terraform state, JIRA); visual blueprints and self-service actions; integrated scorecards; more polished UI.
Weaknesses: SaaS (data outside your network); commercial pricing; less extensibility; vendor lock-in on migration.
Port is for companies wanting a productive IDP quickly, without investing in an internal platform team.
Cortex: Scorecards Focus
Cortex (founded 2019) positions strongly in service catalog + engineering standards.
Strengths: Sophisticated scorecards (Bronze, Silver, Gold levels); automatic catalog from GitHub, Jira, Datadog; reliability workflows; powerful queries; engineering excellence focus.
Weaknesses: High price; less self-service than Port; dense UI; less open ecosystem.
Cortex is for companies wanting to raise technical level measurably, especially after serious incidents.
Comparison Table
| Aspect | Backstage | Port | Cortex |
|---|---|---|---|
| Model | OSS | SaaS | SaaS |
| Time-to-value | 3-6 months | weeks | 1-2 months |
| Extensibility | React code | Low-code | Configurable |
| Self-service | With work | Native | Less |
| Scorecards | Plugin | Native | Core |
| Cost | Infra + team | SaaS license | SaaS license |
| Lock-in | Low | High | High |
Decision by Team Size
Startup or team under 30 engineers: A sophisticated IDP is overkill. If you need something, start with Port on the free or basic tier.
Mid-market (30-150 engineers): Port is the sweet spot: productive quickly, no dedicated platform team needed. Cortex if focus is raising measurable technical level.
Enterprise (150+ engineers): Backstage starts justifying itself through extensibility and customisation. Needs a dedicated team of 3-10 people to operate and evolve it. Port or Cortex if you prefer commercial management and lower operational burden.
The Common Error: Portal Fetish
Many teams install Backstage and are surprised developers don’t use it. Typical cause: the portal has only a static catalog — no real self-service, no executable workflows, no actions.
A useful IDP offers four things: catalog with rich information (not just name but dependencies, SLIs, on-call owner); executable self-service actions; integrated automation (not “click here, then copy-paste elsewhere”); in-context observability. Without these, it’s just a wiki dressed up as a modern portal.
Crawl, Walk, Run
Pragmatic approach to building an IDP from scratch: Phase 1 (service catalog), Phase 2 (docs as code), Phase 3 (basic self-service actions), Phase 4 (scorecards and measurable engineering standards), Phase 5 (complex orchestrated workflows). Trying everything at once is the recipe to abandon it within three months.
Lighter Alternatives
If the decision is not a full IDP: README + GitHub Topics as minimal viable catalog; OpsLevel for maturity-focused scoring; structured wiki in Notion/Confluence for teams under 50; Slack + bots for basic self-service. Not everything must be a giant React portal with a dedicated team.
Conclusion
IDPs are useful for teams that have grown past the point where “ask on Slack” works. The choice between Backstage, Port, and Cortex depends on resources, culture, and ambition: Backstage for who can invest in platform and wants full control; Port for speed and pragmatism; Cortex for measurable technical discipline. Value is in content and executable workflows, not in the interface — installing a pretty portal without real content is the most expensive mistake a platform team can make.
