cncf/landscape

🌄 The Cloud Native Interactive Landscape filters and sorts hundreds of projects and products, and shows details including GitHub stars, funding, first and...

View on GitHub ↗Jump to charts ↓Open shareable report →

Summary Information

Updated 38 minutes ago
Added to GitGenius on September 6th, 2026
Created on November 4th, 2016
Open Issues & Pull Requests: 88 (+0)
GitHub issues: Enabled
Number of forks: 2,193
Total Stargazers: 9,989 (+0)
Total Subscribers: 403 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.4 hours
Mean response time: 63.3 days
90th percentile: 202.4 days
Tracked items: 42

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 77% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 7% of issues opened in the past year have been closed. Three people close 80% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 22
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 491 days
Stale 30+ days: 21
Stale 90+ days: 18

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 2
Events in 7 days: 2

Top labels

  • bug (1)
  • enhancement (1)

Most active issues this week

Detailed Description

The landscape addresses the challenge of navigating the fragmented cloud native ecosystem by organizing projects into logical categories and providing a centralized reference point. It pulls data from multiple sources including GitHub and Crunchbase to surface key project metrics and company information, helping developers understand the landscape of available tools and understand which projects represent well-established paths for cloud native deployment.

Organizations considering whether to contribute to the landscape should know that inclusion requires meeting specific criteria: cloud native projects need at least a certain threshold of GitHub stars and must fit clearly into an existing category. The tool accepts only one primary listing per company product to avoid duplication, though exceptions exist for large vendors and all Certified Kubernetes implementations. Entries must include SVG-format logos with the project or company name in English, and closed source products require clear public documentation. The landscape is regenerated daily, so merged contributions become visible within a day.

The project maintains a data-driven approach focused on community contribution through pull requests to the landscape.yml file, with new entries added in alphabetical order and reviewed against documented guidelines. The actual rendering engine lives in a separate repository, keeping data management distinct from the visualization layer. The tool integrates with Technical Advisory Groups to track project ownership within the CNCF ecosystem, allowing projects to declare their organizational home.