ChatGPT SearchOct 12, 2026
Loading…
Data as of Oct 12, 2026A topic in Internal Developer Platform Software.
Reviewed by Dimitry Apollonsky
Mentioned in · Jul 7 – Oct 12, 2026
ChatGPT SearchOct 12, 2026
If your goal is to build an internal platform engineering team for a large organization, my default recommendation is Backstage as the developer portal, combined with a paved-road platform built on your existing infrastructure and deployment tools.
The key distinction is that an Internal Developer Platform is more than a portal. It is a product that lets application teams provision infrastructure, deploy services, manage dependencies, and meet security and compliance requirements through standardized self-service workflows.
There isn't one universally best framework. The right choice depends on whether you need a developer portal, an end-to-end platform, or a foundation for building your own platform capabilities.
(Best default starting point)
Open source · CNCF incubation project
Backstage provides the developer-facing layer: a software catalog, service ownership, templates for creating new services, documentation, and a plugin ecosystem. It's a strong foundation when you want to integrate existing enterprise tools rather than replace them.
Best for: Large organizations with multiple engineering teams, existing CI/CD systems, and diverse technology stacks.
Commercial orchestration platform
Focuses on the execution layer behind self-service: provisioning infrastructure, resolving environment-specific configuration, managing resources, and coordinating deployments. It can work with a separate portal such as Backstage.
Best for: Enterprises that want to standardize deployment and infrastructure workflows without building all orchestration logic themselves.
Open source · Build-your-own platform
Kratix provides a framework for defining platform services and exposing them through APIs, with automation behind those services. It can integrate with portals such as Backstage.
Best for: Organizations with strong platform engineering skills that need a customizable, API-driven platform rather than a largely predefined product.
| Requirement | Best starting choice |
|---|---|
| One developer portal across many teams and tools | Backstage |
| Automated infrastructure provisioning and environment configuration | Humanitec |
| Maximum flexibility to define your own platform services | Kratix |
| A cohesive platform with both portal and execution capabilities | Backstage + an orchestration layer |
These tools aren't exact substitutes. Backstage is primarily the developer portal; Humanitec and Kratix address platform orchestration and service delivery. That distinction matters when designing an enterprise architecture.
For a large enterprise, I would use a layered architecture rather than making the portal responsible for every platform function.
Developer experience
Service catalog · Self-service workflows · Documentation · Ownership
Platform API and orchestration
Policies · Environment configuration · Resource provisioning · Workflow automation
Golden paths and reusable capabilities
Service templates · Infrastructure modules · Deployment pipelines · Security guardrails
Execution and infrastructure
Cloud · Kubernetes · CI/CD · Identity and secrets · Observability · Databases
Cross-cutting concerns: security, governance, reliability, cost management and developer experience metrics.
This separation allows you to change infrastructure implementations without forcing every developer workflow or portal integration to change. Backstage's plugin architecture and Humanitec's orchestration model both support this general approach.
| Layer | Recommended starting point |
|---|---|
| Developer portal | Backstage |
| Source control | Your existing GitHub, GitLab or equivalent |
| Infrastructure as code | Terraform or OpenTofu, depending on your requirements |
| Workload runtime | where it fits; don't force every workload onto it |
Treat these as candidate building blocks, not a mandate to introduce every tool. Reuse the systems your organization already operates well.
Start with a small team that owns a product, not a team that simply maintains a collection of tools.
Platform product management
Define developer personas, prioritize recurring friction, establish the roadmap, and measure adoption and business outcomes.
Developer experience and portal
Own Backstage, the service catalog, templates, documentation, onboarding, and developer-facing workflows.
Platform infrastructure and automation
Own reusable infrastructure capabilities, environment provisioning, deployment automation, and the platform APIs.
Platform reliability and governance
Establish platform SLOs, access controls, policy automation, upgrade strategies, operational readiness, and cost visibility.
These are responsibilities, not necessarily four separate teams. For an initial team of roughly 6–10 people, people will likely cover multiple areas. At larger scale, split into platform product areas as demand grows.
Days 1–30: Discover and define
Days 31–60: Deliver the minimum viable platform
Days 61–90: Prove adoption and expand
Track a few metrics from the beginning:
A portal with many plugins isn't necessarily a successful IDP. The real test is whether developers can deliver software more safely and with less friction.
Start with Backstage plus a small number of high-value, automated golden paths. Keep the platform API and infrastructure automation separate from the portal. Add Kratix if you want to build a highly customizable, API-driven platform, or evaluate Humanitec if reducing the effort required to implement and maintain orchestration is a priority.
Before committing to the full architecture, I would narrow the decision based on your existing infrastructure.
What does your current enterprise environment look like?
1. Primary infrastructure
AWS
Microsoft Azure
Google Cloud
Multi-cloud / hybrid / on-premises
2. Main application runtime
Kubernetes / containers
VMs and traditional applications
A mixture of containers, VMs and serverless
3. Biggest platform engineering priority
Developer self-service and golden paths
Infrastructure provisioning automation
Security, compliance and governance
Standardizing fragmented engineering tools
4. Approximate developer population
Under 250
250–1,000
More than 1,000
[Build my recommended architecture]
Google AI ModeOct 2, 2026
For a large organization , there is no single out-of-the-box software that solves everything. Instead, enterprise platform engineering relies on a combination of a Developer Portal (the control plane/UI for developers) and an Orchestration/Provisioning Engine (the backend that handles infrastructure and environments).
When building an IDP for a large enterprise, the "best" framework depends on whether you want to build on an open-source standard or buy a commercial control plane to move faster.
What is the industry standard framework for creating an internal developer platform in a large-scale company?
What are the top-rated IDP frameworks suitable for a large organization's platform engineering team?
| Delivery | Existing CI/CD and GitOps tooling |
| Identity and secrets | Enterprise identity provider and approved secrets manager |
| Observability | Existing logging, metrics, tracing and alerting platforms |
| Policy and compliance | Automated policy checks integrated into provisioning and delivery |
To help narrow down the exact framework for your enterprise, tell me:
