The internal developer platform (IDP) market is growing fast. Gartner says 80% of large enterprises will have a platform engineering initiative by 2026. But "IDP" means different things to different vendors.
Some build catalogs. Some build portals. Some orchestrate other tools. Very few actually deploy infrastructure. Let's break down what each tool does — and doesn't do.
Backstage (Spotify)
What it is: An open-source service catalog and developer portal framework.
What it does well: Catalogs services, tracks ownership, provides a unified UI for internal tools via plugins. The plugin ecosystem is large.
What it doesn't do: Deploy infrastructure. Backstage is a catalog — a cockpit without an airplane. You still need Terraform Cloud, ArgoCD, and a platform team to wire it all together.
Time to value: 3-6 months. Backstage requires significant customization. You're essentially building your own IDP on their framework.
Best for: Large enterprises with dedicated platform teams who want a unified portal for many internal tools.
Port.io
What it is: A no-code developer portal with a visual builder.
What it does well: Beautiful UI builder. Self-service actions that trigger external systems. Software catalog with scorecards.
What it doesn't do: Actually run infrastructure. Actions in Port call external APIs — you still need Terraform Cloud, GitHub Actions, or Jenkins to do the work. Port is the frontend to your existing automation.
Pricing: Starts at ~$50k/year. That's for a portal that calls your existing tools.
Best for: Teams that already have mature CI/CD and IaC pipelines and want a better developer-facing UI.
Humanitec
What it is: A platform orchestrator that standardizes how applications get deployed across environments.
What it does well: Dynamic configuration management. Environment-aware deployments. Score (their open-source spec) is interesting.
What it doesn't do: Replace your tools. Humanitec orchestrates Terraform, Kubernetes, and your CI/CD pipeline. You still need all of them. Humanitec adds a layer of abstraction on top.
Best for: Kubernetes-heavy teams that want to standardize deployment configurations across environments.
Terraform Cloud / HCP Terraform
What it is: HashiCorp's managed Terraform execution environment.
What it does well: Runs terraform plan and apply in a managed environment. State management. Sentinel policy engine. Private module registry.
What it doesn't do: Provide a developer-friendly UI. Self-service deployment. Drift management (beyond plan output). Blueprint lifecycle management. Multi-cloud template catalog.
Best for: Teams that are deep in Terraform and want better execution, state management, and policy enforcement.
AskArchie
> Updated September 2026. This post was written in March, and the AskArchie
> section below has been corrected where the product has since moved. Three
> things changed: the starter-template library was retired in favour of sourcing
> from your own repo and the public registry; the Pulumi-Terraform wrapper was
> deleted, so HCL now runs natively; and the category is no longer "IDP" but
> agentic development platform — agents ask, and Archie governs what they get.
> The comparison itself stands.
What it is: A platform that composes, governs and deploys infrastructure end-to-end — driven by an agent rather than a form.
What it does:
- Platform engineers compose governed golden paths with locked fields and compliance rules
- Developers ask in plain language from their own agent — no IaC knowledge required
- Real deployment, natively: your Terraform runs as Terraform, with no wrapper and no conversion
- Components are sourced down a ladder — your catalog, your repo, the public registry, then generated last
- Drift detection with severity classification and bounded auto-remediation
- Versioning with upgrade tracking across the fleet
- Approval workflows gated on provenance and blast radius
- Published paths are proven by a real deploy into your own non-production account, then torn down
- Slack notifications for deploy/destroy/drift events
Key difference: AskArchie is the engine, not the dashboard. Other tools give you a UI that calls your existing automation. AskArchie *is* the automation.
The Comparison
| Capability | Backstage | Port | Humanitec | TF Cloud | AskArchie |
|---|---|---|---|---|---|
| Actually deploys infra | No | No | No | Yes (TF only) | Yes |
| Self-service for devs | Plugin-dependent | Yes | Partial | No | Yes |
| Drift detection | No | No | No | Partial | Yes |
| Blueprint governance | No | No | Partial | Sentinel | Yes |
| Lifecycle management | No | No | No | No | Yes |
| Time to first deploy | Months | Weeks | Weeks | Hours | Minutes |
| IaC input agnostic | N/A | N/A | No | TF only | TF/CFN/Pulumi |
Which One Should You Pick?
If you have a 10-person platform team and want a unified portal for all internal tools: Backstage.
If you have mature automation and want a better developer UI on top: Port.
If you're Kubernetes-native and want standardized environment configs: Humanitec.
If you want Terraform with better execution: Terraform Cloud.
If you want a single platform that deploys, governs, and manages infrastructure end-to-end — with no existing automation required: AskArchie.
The IDP market is full of tools that give developers a portal. AskArchie gives them a platform.