openchoreo/openchoreo
OpenChoreo is an internal developer platform for Kubernetes observed · 2026-08-28
Health v2 · maintenance only
87/100
- Activity 99
- Release rhythm 99
- Longevity 39
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: 7.5
- age_days: 551
- days_rel: 11
- days_push: 8
- n_releases_24m: 37
Adoption not part of the score
1404 stars · 229 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
OpenChoreo is an open-source internal developer platform (IDP) for Kubernetes that bundles platform abstractions, a Backstage-powered developer portal, CI/CD, GitOps, and observability into one cohesive system. It uses a modular multi-plane architecture (control, data, workflow, observability) and exposes CLI, API, UI, and MCP surfaces so both developers and AI agents can build, deploy, and operate workloads.
Use cases
- build an internal developer platform on kubernetes
- give developers self-service deployments without kubernetes complexity
- set up gitops-based ci/cd for kubernetes apps
- add a backstage developer portal with golden paths
- unified logs metrics and traces for kubernetes workloads
- let ai agents operate kubernetes safely via mcp
- automate root cause analysis and cost optimization with sre and finops agents
- standardize environments and component types across teams
When to choose
- you are a platform engineering team standing up an IDP on Kubernetes without building everything from scratch
- you want an opinionated, integrated bundle of portal, CI/CD, GitOps, and observability rather than stitching tools yourself
- you want AI agents to assist delivery and operations within platform guardrails
- you need multi-cluster, multi-environment deployment with tenant isolation
When to avoid
- you run workloads outside Kubernetes or on a single small cluster with simple needs
- you already have a mature bespoke platform and only need one narrow piece like CI or observability
- you need a fully managed IDP-as-a-service rather than self-hosted software
- your team cannot adopt opinionated abstractions and golden paths
Facets
application · maturity active
deployment ci-cd monitoring developer-tools mcp workflow-automation configuration-management developer-tools self-hosted cloud-computing microservices go self-hosted cli internal-developer-platform platform-engineering gitops backstage cncf-sandbox observability developer-portal golden-paths multi-plane-architecture finops devops containers ai-agents kubernetes docker web-server
10 sources
- readme: https://github.com/openchoreo/openchoreo · fetched 2026-08-28 · 9b8613471223
- homepage: https://openchoreo.dev · fetched 2026-08-29 · 80d6e0f19c9f
- site_page: https://openchoreo.dev/docs · fetched 2026-08-29 · fbe652f867b9
- site_page: https://openchoreo.dev/docs/next · fetched 2026-08-29 · f8593cea6f40
- site_page: https://openchoreo.dev/docs/v1.1.x · fetched 2026-08-29 · 1673d7f5458a
- site_page: https://openchoreo.dev/docs/v1.0.x · fetched 2026-08-29 · 1d0b75e974ee
- site_page: https://openchoreo.dev/docs/v0.17.x · fetched 2026-08-29 · 705030f0818f
- site_page: https://openchoreo.dev/docs/v0.16.x · fetched 2026-08-29 · c77f75885d8b
- site_page: https://openchoreo.dev/docs/overview/architecture · fetched 2026-08-29 · a13f99086398
- site_page: https://openchoreo.dev/docs/platform-engineer-guide/gitops/overview · fetched 2026-08-29 · 6407e4f646dd
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| openchoreo/openchoreo | main | 87 |
For agents
markdown · JSON · MCP: product_card(name="openchoreo/openchoreo")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem