openchoreo/openchoreo
OpenChoreo is an internal developer platform for Kubernetes
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
5 releases in the last 90 days, the latest 7 days ago, with 64 contributors on GitHub.
Use Cases & Benefits
- Provides a complete open-source internal developer platform for Kubernetes with abstractions, CI/CD, GitOps, observability, and a Backstage-powered portal.
- Delivers a production-ready, multi-plane architecture that separates developer intent from platform control, enabling scalable and maintainable Kubernetes platform engineering.
- Use for enabling developers to self-service deploy and operate Kubernetes workloads without managing low-level resources directly.
- Use for platform engineers to declaratively configure organizational boundaries, deployment pipelines, and security policies using Kubernetes-native APIs.
- Use for integrating AI agents and automated workflows to enhance developer productivity and platform observability in cloud-native environments.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
Apache 2.0
Permissive: commercial use, modification and redistribution are allowed with attribution; includes an explicit patent grant from contributors.
Community files
- README: present
- Contributing guide: present
- Code of conduct: present
Watch-outs
No watch-outs from GStars' checks.
General guidance from repository metadata, not legal advice. How we score
From the README
OpenChoreo is a developer platform for Kubernetes that lets developers and AI agents build, deploy, and operate apps, resources, and agentic workloads. It provides development and platform abstractions, a Backstage-powered developer portal, CI/CD, GitOps, and observability.
Kubernetes gives you powerful primitives like Namespaces, Deployments, CronJobs, Services, and NetworkPolicies, but they're too low-level for most developers. Platform engineers end up building the actual platform from scratch: defining higher-level abstractions, wiring together tools for delivery, security and observability, and maintaining all of it as an in-house product.
That means stitching together a developer portal, CI pipelines, GitOps workflows, an observability stack, and access controls and then owning the glue between them indefinitely. The result is a fragile, bespoke system that's expensive to maintain and hard to evolve.
Developers and platform engineers need different things from the same platform. Developers want a simple, self-service experience. Platform engineers want control over what's running underneath. Most DIY platforms end up optimizing for one side at the expense of the other.
Compared with peers in AI Agents
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 1, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| vercel-labs/agent-desktop | 17.0K | +13.3K | 33 | today |
| thedotmack/claude-mem | 113.6K | +8.8K | 35 | today |
| stablyai/orca | 116.8K | +6.6K | 40 | today |
| milind-soni/OpenMausBot | 13.5K | +6.0K | 45 | today |
| HKUDS/DeepTutor | 55.5K | +5.5K | 65 | 5 days ago |
| openchoreo/openchoreo | 1.8K | — | 65 | 7 days ago |
| Category median | 55.5K | +6.6K | 40 | — |
Discover Repositories
Search across tracked repositories by name or description