// the find
cnoe-io/idpbuilder
Spin up a complete internal developer platform with only Docker required as a dependency.
idpbuilder spins up a full internal developer platform — kind cluster, ArgoCD, Gitea, ingress-nginx, Backstage — from a single binary with only Docker as a prereq. It's aimed at platform engineers who want a local or CI reference IDP without standing up real infrastructure. Think 'kind for your entire platform stack' rather than just a cluster.
The single-binary model is genuinely useful: one `idpbuilder create` and you have a working GitOps loop locally, which is hard to achieve otherwise without hours of glue work. The custom package CRD system lets you bolt on additional tools via ArgoCD ApplicationSets, so it's extensible without forking. Active CI with real e2e tests (not just unit tests) is a good sign for a tool that orchestrates this much infrastructure. Goreleaser + Homebrew tap means distribution is sorted — no 'build from source' tax for new users.
320 stars for a CNCF-adjacent project that's been around long enough to have stable releases suggests limited adoption outside the cnoe.io circle — the IDP space is crowded and this one hasn't broken out. The embedded manifests for ArgoCD, Gitea, and nginx are pinned in the repo under `hack/` and `pkg/controllers/localbuild/resources/`, which means upgrading component versions requires a new idpbuilder release rather than a values override. No support for remote clusters — it's strictly local/kind, so it can't be used to bootstrap a real cluster in the same way. Documentation is thin in the repo itself; most of it lives on cnoe.io, which is a maintenance liability when the site drifts from the code.