Defragmenting the Ecosystem
The core problem CNOE addresses has a name: ecosystem fragmentation. Every company building an IDP is solving the same set of problems — developer portal, GitOps deployment, infrastructure provisioning, identity management — but each company is solving them independently, often making incompatible choices. The collective engineering effort wasted on re-solving the same integration problems is enormous.
CNOE's mission is to defragment this space by establishing a shared baseline. Two properties define its approach:
- Opinionated: CNOE explicitly recommends specific tools for specific layers. It does not say "use any GitOps tool." It says "use ArgoCD." This specificity is the point — it allows the community to build deep, validated integration patterns rather than shallow, generic ones.
- Open: Every recommended tool is a CNCF-graduated or incubating open-source project. There are no proprietary vendor lock-in requirements. You can run the entire stack without paying a single vendor license fee.
This combination is deliberate. Being opinionated without being open would create a new form of lock-in. Being open without being opinionated would recreate the original problem.
The "Glue" Strategy
Here is a truth that experienced platform engineers know: installing ArgoCD takes 10 minutes. Configuring ArgoCD to authenticate against Keycloak, register its applications in Backstage, and enforce OPA policies on every sync — that takes weeks of undocumented trial and error.
CNOE focuses on the glue: the configuration patterns, Helm values, Kubernetes manifests, and architecture decisions that connect the tools into a coherent system. It provides "recipes" — validated, reproducible configurations — so that teams are not starting from a blank page every time.
This shifts the conversation from "What tool should I pick?" to "How do I implement this standard stack for my organization's specific constraints?"
Interviewers at platform-focused companies often ask: "How do you approach tool selection for a new IDP?" A weak answer lists tools. A strong answer describes a framework: start with a validated reference architecture (like CNOE), understand the integration patterns between layers, then customize based on organizational constraints (existing vendor relationships, team expertise, compliance requirements). This demonstrates systems thinking rather than tool familiarity.