CNCF graduated projects: sandbox, incubating and graduated

You'll see "CNCF graduated projects" in job adverts, conference talks and vendor slides, usually as shorthand for "safe to run in production". At KubeCon + CloudNativeCon North America on 10 November 2026, CNCF announced that NATS had graduated, and that CloudNativePG and Open Cluster Management had moved up to incubating. So now is a good time to look at what those labels mean.
This post explains the three maturity levels (sandbox, incubating and graduated), how a project moves between them, and what the labels do and don't tell you. If you're studying for the KCNA, it also fits the "Cloud Native Community and Collaboration" competency in the curriculum.
Key points
- CNCF projects sit at one of three maturity levels: sandbox, incubating or graduated. Inactive projects are archived.
- A project can join as sandbox or apply straight for incubation. Moving up takes a 2/3 supermajority vote of CNCF's Technical Oversight Committee (TOC).
- Graduated means "stable, widely adopted, and production ready" in CNCF's own words. It is a signal about the project, not a guarantee for your use case.
- On 20 November 2026, the CNCF projects page lists 41 graduated and 38 incubating projects. CNCF's 10 November announcement put the whole portfolio at 231 projects.
Sandbox, incubating and CNCF graduated projects
CNCF describes each level in one line on its projects page.
Sandbox. "Experimental projects not yet widely tested in production on the bleeding edge of technology." It's the entry point for new ideas. APIs can change, and breaking changes are expected. Newer sandbox projects announced this year include OpenShell and Agent Substrate, both aimed at running AI agents.
Incubating. "Projects used successfully in production by a small number users with a healthy pool of contributors." The project's lifecycle docs say these show a slower rate of change and more stable, versioned APIs. This is also where the TOC starts looking hard at real adoption.
Graduated. "Projects considered stable, widely adopted, and production ready, attracting thousands of contributors." CNCF's 10 November announcement lists Kubeflow, Cloud Native Buildpacks, Karmada, KubeVirt, NATS and OpenTelemetry among those that graduated over the past year.
There's a fourth state too. Archived projects are "inactive or low activity projects" that CNCF no longer supports or recommends. Archiving isn't a judgement on the code. Often the problem the project solved has moved on, or its maintainers have.
How a project moves up
The process is public and documented in the TOC's repository on GitHub. In short:
- Apply. Sandbox applications go through an issue form, and the TOC reviews them in batches about every two months. A project can skip sandbox and apply directly for incubation.
- Find a sponsor. For incubation or graduation, a TOC member sponsors the application and holds a kickoff with the maintainers.
- Due diligence. The sponsor drafts a due diligence document as a pull request. The project supplies a self-assessed technical review and governance review.
- Adopter interviews. The project names 5 to 7 adopters willing to be interviewed. A published CNCF case study or reference architecture can stand in for an interview, at the sponsor's discretion.
- Comment periods. About a week of internal TOC comment, then two weeks of public comment.
- Vote. The TOC votes on the pull request, and it passes with a 2/3 supermajority. Community members can react to show support, but only TOC votes count.
It isn't quick. The lifecycle docs tell projects to plan on at least three months after a sponsor steps forward, and the FAQ estimates 5 to 15 months overall. The TOC also doesn't take new sponsorships, open public comment or open votes within four weeks of a KubeCon + CloudNativeCon Europe or North America, so timing around the events matters.
A joint security review with TAG Security is "highly recommended" for incubating projects heading towards graduation. Treat the detailed graduation criteria as living documents: they sit in the TOC's application templates on GitHub, and they change between versions.
What the label tells you, and what it doesn't
The level is a good first filter. A graduated project has shown the TOC real production adopters, an open governance model and a contributor base that doesn't hang on one company. That matters when you're choosing what to build a platform on.
Reality check: it doesn't tell you the project is right for your problem. A sandbox project can be the best tool for a narrow job, and a graduated one can be overkill. Maturity also says nothing about how well your team knows the tool, which is often the bigger risk. Read the adopters list, check the release cadence, and look at how quickly security issues get fixed.
Pro tip: when a project you use moves up a level, read its due diligence pull request. It's one of the most honest write-ups you'll find of a project's strengths and gaps, because its job is to test the project's claims.
Why this matters for your certification
The KCNA curriculum has a Cloud Native Architecture domain, weighted at 12%, that includes "Cloud Native Ecosystem and Principles" and "Cloud Native Community and Collaboration". Knowing how CNCF projects are governed and what the maturity levels mean is part of that picture. Don't expect to memorise lists of projects; understand the model instead.
It helps beyond the exam too. Several CNCF certifications are built around a single project: Prometheus (PCA), Argo (CAPA), Istio (ICA), Cilium (CCA), Backstage (CBA), OpenTelemetry (OTCA) and Kyverno (KCA). If you're picking your next exam, check the project's maturity level first: it's a fair hint at how settled the tool is. You can see which of these certifications people hold together on the CertDirectory insights page.
If KCNA is your next step, the KCNA discount page lists the current offers.
FAQ
What is a CNCF graduated project? A project the CNCF Technical Oversight Committee has voted to the top maturity level, after due diligence and adopter interviews. CNCF describes these as "stable, widely adopted, and production ready".
What is the difference between CNCF sandbox and incubating? Sandbox is the experimental entry level, with no production track record needed. Incubating projects have shown successful production use by a small number of users and a healthy group of contributors, and have passed TOC due diligence.
How many CNCF graduated projects are there? The CNCF projects page listed 41 graduated and 38 incubating projects on 20 November 2026. The number changes after each TOC vote, so check the page for the current count.
Can a CNCF project skip the sandbox? Yes. CNCF's lifecycle docs say a project can apply as a sandbox project or directly for incubation.
Is a CNCF sandbox project safe to use in production? Some organisations do, case by case. CNCF calls sandbox projects experimental, so expect breaking changes and test carefully before you depend on one.
Pick one graduated project you use every day, read its due diligence document, and see how much of the cloud native world makes more sense afterwards.