# The CNCF landscape has 230+ tools. Choosing from it is where platform teams get stuck.

DevFeed: [The CNCF landscape has 230+ tools. Choosing from it is where platform teams get stuck.](<https://devfeed.tech/articles/the-cncf-landscape-has-230-tools-choosing-from-it-is-where-platform-teams-get-stuck-17502.md>)

Original publisher: [Read original article](<https://www.giantswarm.io/blog/why-cncf-abundance-is-a-problem>)

Author: The Team @ Giant Swarm

Published: 2026-08-03T14:41:21Z

Content type: opinion

Language: en

Sources: [Giant Swarm Blog](<https://devfeed.tech/sources/giant-swarm-blog.md>)

Topics: [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>)

Tags: [cncf](<https://devfeed.tech/tags/cncf.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [platform](<https://devfeed.tech/tags/platform.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [tools](<https://devfeed.tech/tags/tools.md>)

## AI overview

The article argues that the CNCF landscape's 230-plus projects create evaluation paralysis for platform teams. It says the landscape shows what exists but not which combinations work for a team's production environment, cloud provider, and size, making selection and integration a significant source of delay.

## Source excerpt

The CNCF landscape has 230+ projects. Here's why that's where evaluation paralysis starts, and what it costs. (Giant Swarm)