openchoreo: A complete, open-source developer platform for Kubernetes
What problem it solves
Kubernetes provides powerful primitives, but they are too low-level for most developers, forcing platform teams to build higher-level abstractions and integrate delivery, security, and observability tools. The resulting bespoke platform can be fragile, expensive to maintain, and difficult to evolve while balancing developers' need for self-service with platform engineers' need for control.
Key features
Multi-plane architecture — The platform separates experience, control, data, observability, and optional CI concerns into distinct planes. Each plane handles a specific concern and operates independently.
Source: README
Developer and platform abstractions — Developers work with components, endpoints, dependencies, and other high-level concepts. The control plane translates that intent into Kubernetes resources while reflecting runtime state back to users.
Source: README
Integrated delivery and operations — The platform includes a Backstage-powered developer portal, CI, GitOps, observability, RBAC, and analytics. Its optional CI plane uses cloud native Buildpacks and Argo Workflows by default.
Source: README
Declarative Platform API — The Platform API consists of Kubernetes CRDs for defining platform structure and behavior declaratively. Programmable abstractions let platform teams establish golden paths, encapsulate practices, and enforce organizational standards.
Source: README
Access through multiple interfaces — Developers, platform engineers, and SREs can interact through the portal, CLI, GitOps, or AI agents. The experience plane provides a common interface for these different working modes.
Source: README
Who it may suit
This may suit platform engineers building an internal developer platform for Kubernetes and developers who need a self-service way to deploy and operate applications. It may also suit SREs and teams interested in defining governed platform workflows through Kubernetes-native abstractions.
Topics to discuss
Which Platform API abstractions should be prioritized for the next set of platform experiences?
How can developers and platform engineers share ownership of configurable golden paths?
Which workloads and deployment sources should receive more hands-on sample coverage?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/openchoreo/openchoreo#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…