{"slug":"best-developer-portals-for-self-service-infrastructure-provisioning","title":"Best developer portals for self-service infrastructure provisioning","question":"What are the best developer portals for self-service infrastructure provisioning in 2026?","verdict":"As of 2026-07-18, ChatGPT, Claude, Gemini collectively rank Port first for developer portals for self-service infrastructure provisioning. Source: https://modelsagree.com/best/best-developer-portals-for-self-service-infrastructure-provisioning (modelsagree.com, CC BY 4.0).","category":"Platform Engineering","url":"https://modelsagree.com/best/best-developer-portals-for-self-service-infrastructure-provisioning","updated":"2026-07-18","models":["ChatGPT","Claude","Gemini"],"consensus":"All 3 models rank Port the top pick","disagreement":null,"combined":[{"rank":1,"product":"Port","domain":"port.io","score":15,"appearances":3,"modelRanks":{"ChatGPT":1,"Claude":1,"Gemini":1},"reason":"Best overall portal layer for exposing existing Terraform, GitHub Actions, CI/CD, and custom automation through polished forms, RBAC, approvals, audit trails, TTL policies, and catalog-aware workflows; especially strong when infrastructure tooling already exists."},{"rank":2,"product":"Backstage","domain":"backstage.io","score":11,"appearances":3,"modelRanks":{"ChatGPT":3,"Claude":2,"Gemini":2},"reason":"The de facto open-source standard (CNCF, Spotify-born) with the largest plugin ecosystem; software templates give real self-service scaffolding and provisioning, and the catalog model is now the lingua franca the commercial portals themselves emulate. Unmatched extensibility for orgs with dedicated platform engineers. Near-tie with Port — Backstage wins on ownership and ecosystem, loses on time-to-value."},{"rank":3,"product":"Roadie","domain":"roadie.io","score":5,"appearances":2,"modelRanks":{"Claude":3,"Gemini":4},"reason":"Managed Backstage that removes the #2 pick's biggest cost — hosting, upgrades, and plugin maintenance — while keeping ecosystem compatibility; its scaffolder and Terraform/API integrations deliver genuine self-service provisioning without a portal team."},{"rank":4,"product":"Humanitec","domain":"humanitec.com","score":4,"appearances":1,"modelRanks":{"ChatGPT":2},"reason":"Strongest near-tie for organizations wanting actual infrastructure orchestration beneath the portal: it dynamically selects approved Terraform/OpenTofu modules, provisions dependencies, enforces environment rules, and supports lifecycle operations across clouds and runtimes."},{"rank":5,"product":"Massdriver","domain":null,"score":3,"appearances":1,"modelRanks":{"Gemini":3},"reason":"Unifies the portal UI and the execution layer by providing a visual, diagram-based infrastructure provisioning experience. Developers deploy production-ready cloud architectures using pre-approved cloud bundles (Terraform, OpenTofu, or Helm) with built-in observability, IAM policies, and cost tracking. Assumes you want to avoid separate tools for catalog UI and deployment engine."},{"rank":6,"product":"Cortex","domain":"cortex.io","score":2,"appearances":1,"modelRanks":{"Claude":4},"reason":"Strongest maturity/scorecard engine of the commercial portals, with credible self-service actions and scaffolding bolted to it; best fit when the driver is production standards and service ownership at mid-to-large scale, with provisioning as part of the package."},{"rank":7,"product":"Qovery","domain":"qovery.com","score":2,"appearances":1,"modelRanks":{"ChatGPT":4},"reason":"Delivers unusually fast, approachable self-service environments and application infrastructure on Kubernetes and major clouds, with templates, governance, previews, deployment workflows, and Terraform integration already assembled."},{"rank":8,"product":"Atlassian Compass","domain":"atlassian.com","score":1,"appearances":1,"modelRanks":{"Claude":5},"reason":"Cheapest credible on-ramp for the huge population already on Jira/Bitbucket — component catalog, scorecards, and templates with zero-friction Atlassian integration and aggressive pricing; earns the slot on distribution-adjusted value, not depth."},{"rank":9,"product":"Cycloid","domain":null,"score":1,"appearances":1,"modelRanks":{"ChatGPT":5},"reason":"A strong Terraform-centric choice combining reusable infrastructure stacks, forms-based self-service, RBAC, policy controls, cost visibility, and lifecycle management; near-tied with Qovery when infrastructure rather than application delivery is the center of gravity."},{"rank":10,"product":"Harness IDP","domain":"harness.io","score":1,"appearances":1,"modelRanks":{"Gemini":5},"reason":"Built on Spotify Backstage but fully integrated with Harness's commercial CI/CD pipelines, GitOps, and Infrastructure-as-Code Management (IaCM) orchestrator. It allows teams to easily map self-service templates to enterprise-grade provisioning workflows with built-in OPA governance and secret management. Assumes you are already adopting the Harness execution ecosystem."}],"perModel":{"ChatGPT":[{"rank":1,"product":"Port","reason":"Best overall portal layer for exposing existing Terraform, GitHub Actions, CI/CD, and custom automation through polished forms, RBAC, approvals, audit trails, TTL policies, and catalog-aware workflows; especially strong when infrastructure tooling already exists.","fix":"It orchestrates your automation rather than replacing it, so the platform team must still build and operate the provisioning backends."},{"rank":2,"product":"Humanitec","reason":"Strongest near-tie for organizations wanting actual infrastructure orchestration beneath the portal: it dynamically selects approved Terraform/OpenTofu modules, provisions dependencies, enforces environment rules, and supports lifecycle operations across clouds and runtimes.","fix":"Its opinionated orchestration model and enterprise-oriented commercial footprint are excessive for small teams or simple Terraform estates."},{"rank":3,"product":"Backstage","reason":"Best open-source foundation for teams that need complete ownership and customization; Software Templates, custom actions, its large plugin ecosystem, and the catalog can present almost any provisioning workflow through one extensible developer portal.","fix":"It is a framework, not a turnkey provisioning product, and operating it well commonly requires a dedicated Backstage engineering capability."},{"rank":4,"product":"Qovery","reason":"Delivers unusually fast, approachable self-service environments and application infrastructure on Kubernetes and major clouds, with templates, governance, previews, deployment workflows, and Terraform integration already assembled.","fix":"It fits application-platform and Kubernetes-centric provisioning better than arbitrary enterprise infrastructure or highly bespoke workflows."},{"rank":5,"product":"Cycloid","reason":"A strong Terraform-centric choice combining reusable infrastructure stacks, forms-based self-service, RBAC, policy controls, cost visibility, and lifecycle management; near-tied with Qovery when infrastructure rather than application delivery is the center of gravity.","fix":"Its portal and ecosystem are less broadly extensible than Port or Backstage, making it less compelling as a company-wide developer hub."}],"Claude":[{"rank":1,"product":"Port","reason":"Fastest path from zero to working self-service provisioning for a typical platform team — its data model (blueprints/entities), no-fork customization, and first-class self-service actions that trigger GitHub Actions/Jenkins/Terraform mean golden paths ship in days, not quarters; strongest scorecards-plus-actions combo among the SaaS portals. Assumption: the typical practitioner is a small platform team without headcount to maintain portal code.","fix":"Commercial SaaS with per-seat-style pricing and a proprietary data model — teams wanting full ownership of portal code or air-gapped deployments will chafe."},{"rank":2,"product":"Backstage","reason":"The de facto open-source standard (CNCF, Spotify-born) with the largest plugin ecosystem; software templates give real self-service scaffolding and provisioning, and the catalog model is now the lingua franca the commercial portals themselves emulate. Unmatched extensibility for orgs with dedicated platform engineers. Near-tie with Port — Backstage wins on ownership and ecosystem, loses on time-to-value.","fix":"It's a framework, not a product — expect a React/TypeScript codebase to own, ongoing upgrade toil, and typically 1-3 dedicated engineers; small teams routinely stall or abandon rollouts."},{"rank":3,"product":"Roadie","reason":"Managed Backstage that removes the #2 pick's biggest cost — hosting, upgrades, and plugin maintenance — while keeping ecosystem compatibility; its scaffolder and Terraform/API integrations deliver genuine self-service provisioning without a portal team.","fix":"You inherit Backstage's data model and UX constraints without full freedom to hack the source; heavily customized in-house plugins can still be awkward, and it's SaaS-only."},{"rank":4,"product":"Cortex","reason":"Strongest maturity/scorecard engine of the commercial portals, with credible self-service actions and scaffolding bolted to it; best fit when the driver is production standards and service ownership at mid-to-large scale, with provisioning as part of the package.","fix":"Provisioning/self-service is secondary to its scorecard DNA — teams whose primary need is rich infrastructure actions get more depth from Port or Backstage templates; enterprise pricing."},{"rank":5,"product":"Atlassian Compass","reason":"Cheapest credible on-ramp for the huge population already on Jira/Bitbucket — component catalog, scorecards, and templates with zero-friction Atlassian integration and aggressive pricing; earns the slot on distribution-adjusted value, not depth.","fix":"The shallowest self-service provisioning of the five and weak outside the Atlassian ecosystem; ambitious platform teams outgrow it."}],"Gemini":[{"rank":1,"product":"Port","reason":"Offers an extremely flexible, no-code blueprint engine to model any infrastructure schema. Its self-service actions are first-class citizens, providing structured UI forms and lifecycle tracking (run states, logs) with direct integration to execute across GitOps, CI/CD, and third-party APIs. Assumes you want a clean separation of the portal UI from the execution engine.","fix":"It does not execute infrastructure provisioning itself, serving strictly as a frontend control plane; platform teams must still build and maintain the backend orchestration, APIs, and pipelines that execute the actions triggered by Port."},{"rank":2,"product":"Backstage","reason":"The dominant open-source framework with a massive plugin ecosystem. The Software Templates (Scaffolder) engine is highly extensible, allowing teams to build complex, multi-step wizards for resource provisioning, repository creation, and API integration. Assumes your organization has the resources to treat the portal as a product itself.","fix":"High total cost of ownership and operational overhead; since it is a code-first React and Node.js framework rather than a turnkey solution, it requires dedicated engineering headcount to maintain, build, and deploy."},{"rank":3,"product":"Massdriver","reason":"Unifies the portal UI and the execution layer by providing a visual, diagram-based infrastructure provisioning experience. Developers deploy production-ready cloud architectures using pre-approved cloud bundles (Terraform, OpenTofu, or Helm) with built-in observability, IAM policies, and cost tracking. Assumes you want to avoid separate tools for catalog UI and deployment engine.","fix":"Highly opinionated deployment paradigm that is not suited for organizations that already have mature, complex, custom CI/CD pipelines and platform orchestration tools they do not want to replace or refactor."},{"rank":4,"product":"Roadie","reason":"Delivers the power of Backstage's Software Templates and Service Catalog while eliminating the operational maintenance burden. As a managed SaaS, Roadie handles version upgrades, hosting, and plugin maintenance. Assumes you want the open-source Backstage model but cannot justify dedicating engineers to maintain the framework codebase.","fix":"Restricted customizability compared to self-hosted Backstage, as you cannot run arbitrary custom Node.js backend plugins and are limited to the integrations and customization options supported on Roadie's platform."},{"rank":5,"product":"Harness IDP","reason":"Built on Spotify Backstage but fully integrated with Harness's commercial CI/CD pipelines, GitOps, and Infrastructure-as-Code Management (IaCM) orchestrator. It allows teams to easily map self-service templates to enterprise-grade provisioning workflows with built-in OPA governance and secret management. Assumes you are already adopting the Harness execution ecosystem.","fix":"Strong vendor lock-in; to get real value out of its infrastructure provisioning capabilities, organizations must use Harness's underlying pipeline and execution modules, making it unsuitable for teams committed to alternative CI/CD tooling."}]},"missedByModel":{"ChatGPT":[{"product":"Roadie","reason":"excellent managed Backstage experience, but infrastructure provisioning still depends heavily on templates, plugins, and external automation you supply"},{"product":"Cortex","reason":"excellent catalog, scorecards, and developer workflows, but less purpose-built for deep infrastructure provisioning than the top five"}],"Claude":[{"product":"OpsLevel","reason":"solid catalog and actions but overlaps Cortex/Port while trailing both on ecosystem momentum and provisioning depth"}],"Gemini":[{"product":"Cortex","reason":"highly optimized for service catalogs, scorecards, and maturity metrics, but its self-service action capability is less flexible and mature for complex infrastructure provisioning workflows compared to Port or Backstage templates"},{"product":"OpsLevel","reason":"offers great service catalog features and maturity tracking, but its infrastructure provisioning integrations and custom template features are less robust than the top 5 options"}]}}