Editorial take
Why it stands out
Cilium should be positioned as a Kubernetes networking platform decision, not just as another mesh or policy tool.
Tool profile
eBPF-based Kubernetes networking, security, observability, and service mesh infrastructure with strong platform gravity in modern cloud-native stacks.
Kubernetes networking
Cilium belongs in the database because it is no longer just a CNI choice. The official documentation positions Cilium as eBPF-based networking, security, and observability for Kubernetes, and the broader project surfaces make it clear that service mesh capabilities and Hubble observability are part of the story as well. That makes Cilium one of the most strategically important infrastructure tools in modern Kubernetes networking, especially for teams that want security and visibility closer to the kernel rather than bolted on at a higher layer.
It also deserves inclusion because its economics are increasingly important even when the upstream project itself is free. Cilium is open source and does not expose a direct software price, but the official docs clearly reference enterprise-ready supported distributions on the Cilium website. That means teams often compare Cilium in two modes: upstream OSS for direct control, or supported enterprise packaging through vendors. For the directory, it should be framed as a foundational platform decision rather than just a niche networking add-on.
Quick fit
Editorial take
Cilium should be positioned as a Kubernetes networking platform decision, not just as another mesh or policy tool.
What it does well
Primary use cases
Fit notes
Pricing snapshot
Cilium is open source and free to use directly. The checked official documentation references enterprise-ready and supported Cilium distributions rather than publishing a native self-serve pricing table for the upstream project.