Best Practices

CNCF Landscape Explained: How Projects Move from Sandbox to Incubating to Graduated

October 18, 2026 Kubezilla Team 8 min read
Terminal style graphic reading CNCF Landscape Explained: Sandbox to Incubating to Graduated

If you have ever opened the CNCF Landscape, you know the feeling. Hundreds of logos, dozens of categories, and no obvious place to start. Some of those logos are CNCF projects, many are not, and the CNCF projects themselves sit at very different levels of maturity. Knowing how to read the landscape, and what “Sandbox”, “Incubating” and “Graduated” actually mean, helps you pick tools with your eyes open.

This guide explains what the landscape is, how the CNCF maturity levels work, what the Technical Oversight Committee (TOC) checks before a project moves up, and how to use those signals when you choose software for your own platform. If you are new to the foundation itself, start with our complete CNCF guide first.

What the CNCF Landscape is, and what it is not

The CNCF Interactive Landscape is a map of the cloud native ecosystem. It actually holds three views: the cloud native landscape, a serverless landscape and a member landscape. Each one can be downloaded as a PNG or PDF. Logos shown in grey are not open source.

The most common mistake is to treat every logo as a CNCF project. It is not. The landscape is an index of the ecosystem, and it includes commercial products, open source tools hosted elsewhere, and CNCF projects side by side. The cncf/landscape repository spells out the inclusion rules:

  • Cloud native projects with at least 300 GitHub stars that clearly fit an existing category are generally included.
  • Each project goes in the single category where it fits best, and a company’s product usually appears in only one box.
  • Commercial versions of open source software are generally left out, with one exception: all Certified Kubernetes implementations are shown.
  • Closed source products need a link to a clear product description.

All of this data lives in a single file, landscape.yml, and new entries arrive through pull requests. The site itself is generated by landscape2, a command line tool that builds static, interactive landscape websites from YAML data. So a logo on the map tells you a tool exists and roughly what it does. It does not tell you that CNCF hosts it. For that, you need the maturity level.

The four maturity levels

CNCF hosts projects at three active levels plus one end state. The definitions below follow the CNCF Project Lifecycle and Process page and the CNCF projects page.

  • Sandbox: the entry point. Experimental or innovative projects early in their development. Some may see limited production use, but they are not yet widely tested in production.
  • Incubating: projects that are gaining adoption and working on stability. Change slows down, breaking changes become rarer and APIs become versioned and stable. CNCF describes them as used successfully in production by a small number of users, with a healthy pool of contributors.
  • Graduated: the most mature projects, considered stable, widely adopted and production ready, with adopters who have shown that in real deployments.
  • Archived: projects that are inactive, have low activity or are no longer recommended. The TOC no longer supports them.

CNCF maps these levels to the “Crossing the Chasm” adoption model: Sandbox for innovators, Incubating for early adopters, and Graduated for the early majority. In other words, the level is a hint about what kind of organization should be comfortable adopting a project today.

For scale: in October 2026, the landscape data file lists 39 graduated projects, 38 incubating projects and more than 150 sandbox projects. Graduated names include Kubernetes, Prometheus, Envoy, etcd, containerd, Cilium, Argo, Flux, Kyverno, OpenTelemetry and Kubeflow. These numbers change over time, so check the landscape for the current list.

How a project gets into Sandbox

A project applies to Sandbox by filling in an issue form in the cncf/sandbox repository. The TOC reviews applications roughly every two months, and applications that fail basic checks can be closed without a review. Those pre-checks are a good summary of what CNCF expects even at the earliest stage:

  • License: Apache 2.0 or another allowlisted license, compliant before acceptance. BSL and GPL family licenses are not acceptable.
  • MAINTAINERS file: a real table of names, GitHub or GitLab IDs and organizations. “TBD” does not count.
  • Organization diversity: at least three maintainers from two or more employers.
  • Reusable project: CNCF accepts projects, not reference architectures that only wire existing tools together.

Acceptance needs a TOC vote and a signed contribution agreement. Until both happen, a project cannot describe itself as donated to CNCF. Outcomes include approved, declined, postponed and “need info”, and projects are often encouraged to apply again later.

Moving up: the incubation and graduation process

Moving from Sandbox to Incubating, or from Incubating to Graduated, follows the same path. The project opens an incubation or graduation issue in the cncf/toc repository, using the official templates. From there, the steps look like this:

  1. The project writes its application with evidence links and lines up five to seven adopters willing to be interviewed.
  2. The TOC checks the application for completeness. Incomplete ones are closed and marked “Not Ready”.
  3. A TOC member is assigned as sponsor, and a kickoff meeting reviews repositories, release process, metrics and governance.
  4. The sponsor writes a due diligence document and runs adopter interviews where needed.
  5. The TOC gets about one week for internal review, followed by a two week public comment period.
  6. Voting opens on GitHub, and the move needs a two thirds supermajority of the TOC.

CNCF is clear that there is no guaranteed timeline. Once a sponsor is assigned, projects should plan for at least three months, and the lifecycle FAQ says the whole process can take five to fifteen months. There is also a freeze around KubeCon + CloudNativeCon Europe and North America: in the four weeks before each event there are no new sponsorships, public comments, votes or announcements.

What the TOC checks at each step

The incubation and graduation templates share the same structure, but the bar rises. Both levels require a General Technical Review, a Governance Review, a security self assessment, a clear way to report vulnerabilities, enforced access controls such as two factor authentication, the OpenSSF Best Practices passing badge, a public roadmap, and a public adopter list with at least three independent adopters.

Graduation adds stricter requirements on top of that:

  • Maintainers from at least two organizations, plus a mechanism that balances organizations in governance decisions, such as org balanced voting or caps on steering committee seats.
  • A documented maintainer lifecycle (onboarding, offboarding, emeritus) with evidence that it is used.
  • A contributor ladder that produces maintainers from more than one organization.
  • A third party security review, with moderate and low findings tracked.
  • A RELEASES.md or equivalent covering support length, branch strategy and artifacts, plus a history of regular releases.
  • Adopters verified by the TOC at production level. For incubation, development and test use is the expected level.

This is why “graduated” carries weight. It is not only a popularity badge. It says the project has a governance model that survives one company leaving, a security process that has been looked at by outsiders, and real production users who have talked to the TOC.

When projects are archived

Not every project keeps growing. A review can start from health signals such as activity, security responsiveness and adoption, or from a request by anyone in the community. After discussion on a public issue, the TOC opens a two week public comment period and then a two week vote, and archiving needs a two thirds majority.

An archived project loses CNCF support and marketing and can no longer use its Sandbox, Incubating or Graduated label, although CNCF keeps hosting its trademarks and domains. The code can keep evolving, and the project can return through the normal lifecycle. Brigade, Keptn, rkt and OpenTracing are examples on the archived projects page.

Hands-on: reading a project’s level from the landscape data

Prerequisites: a web browser, or any text editor if you clone the cncf/landscape repository. Every entry in landscape.yml is an item. CNCF hosted projects carry a project field. Here is the Kubernetes entry as it appears in the file today:

- item:
  name: Kubernetes
  description: Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications
  homepage_url: https://kubernetes.io/
  project: graduated
  repo_url: https://github.com/kubernetes/kubernetes
  logo: kubernetes.svg

The project value is one of sandbox, incubating, graduated or archived. If an entry has no project field at all, it is listed on the landscape but is not a CNCF project.

Using maturity levels when you choose tools

The levels are a signal, not a verdict. A few practical rules help:

  • For core platform pieces you expect to run for years, such as networking, policy or observability, a graduated project like Kyverno lowers your risk.
  • Incubating projects are often a safe choice for production if you check adopters, release history and how active the maintainers are.
  • Sandbox projects are great for experiments and for contributing early, but plan for API changes and have an exit path.
  • Always check the archived list before adopting something you found in an old blog post or tutorial.
  • Read the due diligence document in the TOC repository. It is one of the most honest public reviews of a project you will find.

Key takeaways

  • The CNCF Landscape is an index of the whole ecosystem. A logo on it does not mean CNCF hosts the project.
  • CNCF projects move through Sandbox, Incubating and Graduated, and can be Archived when they become inactive.
  • Moving up needs a TOC sponsor, due diligence, adopter interviews, public comment and a two thirds TOC vote.
  • Graduation adds third party security review, multi organization governance and TOC verified production adopters.
  • Use the level as one input, together with adopters, release history and your own testing.

Sources

CNCF Project Lifecycle and Process, CNCF archiving process, CNCF projects, CNCF project metrics, CNCF Sandbox projects, CNCF archived projects, CNCF Interactive Landscape, cncf/landscape on GitHub, cncf/landscape2, cncf/sandbox, cncf/toc, incubation application template and graduation application template.

One thought on “CNCF Landscape Explained: How Projects Move from Sandbox to Incubating to Graduated”

Leave a comment