Cilium Service Mesh

Cilium Service Mesh holds place 8 of 13 in our service mesh tools ranking. The catalogue describes it as: eBPF datapath mesh that moves connectivity out of application code.

On this site vendors can buy visibility, and we say so. Outbound links, including the one to Cilium Service Mesh, are marked identically. Read more.

Visit Cilium Service Mesh See it in the service mesh tools ranking

01

Key facts about Cilium Service Mesh

HeadquartersNot stated by the vendor
Best forClusters already on Cilium networking that want mesh features from it
DeploymentOpen source code
Pricing modelOpen source under Apache-2.0; no prices or plan names in the documentation read
Free planNone recorded
APIAn API is mentioned by the vendor
02

What is Cilium Service Mesh?

Cilium Service Mesh is the mesh layer of the Cilium project, which its repository describes as eBPF-based networking, security and observability. The documentation explains that connectivity, security and observability move out of application code: an in-kernel eBPF datapath handles much of the work, and a proxy such as Envoy is used for application protocols like HTTP, gRPC and DNS.

Ingress, Gateway API and GAMMA support sit next to the mesh features, and the docs include demos for running Istio in ambient or sidecar mode on top of Cilium. The open source project is published under Apache-2.0, with BPF code templates dual-licensed under GPL-2.0 and BSD-2-Clause. Cisco announced in December 2023 its plan to acquire Isovalent, the company it described as having led Cilium development. No country of establishment is named on the pages we read.

03

Cilium Service Mesh key features

  • eBPF datapath. The documentation names eBPF as the in-kernel datapath, so a share of traffic handling happens in the Linux kernel instead of in a proxy container attached to every application pod.
  • Envoy for application protocols. For HTTP, gRPC and DNS the docs describe a proxy such as Envoy, which means layer 7 behaviour is still handled by a user-space component when a policy needs it.
  • Mutual authentication. Listed as a beta feature, with an identity model that references SPIFFE. Teams planning encrypted, authenticated service calls should read the beta label before committing production traffic.
  • L7-aware traffic management. Load balancing, circuit breaking, traffic shifting and proxy load balancing for Kubernetes Services are covered, and the docs also mark this group as beta.
  • Ingress and Gateway API. Kubernetes Ingress and Gateway API are both documented, and a migration guide explains how to move from Ingress resources to Gateway API objects.
  • GAMMA support. The documentation covers GAMMA, the Gateway API approach to configuring east-west mesh traffic, so routing rules for traffic between services can use the same API family as ingress.
  • Istio integration demos. Separate pages with demos show Cilium running with Istio in ambient mode and in sidecar mode, useful for teams that want Istio policy objects on a Cilium network.
04

Who Cilium Service Mesh suits

  • Clusters already running Cilium as the network plugin. A platform team that has chosen Cilium for networking can read the mesh features as an extension of the same installation rather than adding a second control plane.
  • Teams reviewing sidecar-free approaches. Engineers who dislike a proxy container in every pod can compare the eBPF datapath with sidecar designs, keeping in mind that some protocol handling still uses a proxy.
  • Gateway API adopters. Groups moving from Ingress to Gateway API get a documented migration guide and GAMMA coverage in the same documentation set.
05

Getting started with Cilium Service Mesh

The default installation guide starts with the Cilium CLI, which downloads a release, checks it against a sha256 checksum file and installs it to /usr/local/bin. You then run cilium install with a version number. Before that, Kubernetes must be configured to use a CNI, and the Linux kernel must be version 5.10 or later.

The installer picks a default configuration per platform, either Direct Routing or encapsulation, with Kubernetes PodCIDR, AWS ENI or cluster pool IPAM. Afterwards, cilium status --wait and cilium connectivity test validate the result, and pods that were already running unmanaged are restarted so they receive Cilium networking. Example cluster commands exist for GKE, AKS, EKS, kind, minikube, k3s and other platforms.

06

Where Cilium Service Mesh wins and where it does not

Where Cilium Service Mesh earns its place
  • Cilium Service Mesh uses an eBPF datapath in the kernel plus a proxy such as Envoy for protocols like HTTP, gRPC and DNS.
  • Marked in our records as beta features.
  • Marked in our records as eBPF.
  • Strongest for: Clusters already on Cilium networking that want mesh features from it.
  • Gateway API is among the traits we single out for it.
Where Cilium Service Mesh costs you
  • Two headline mesh features carry a beta label, which limits production use.
  • Linux kernel 5.10 or later is required, and already-running pods need a restart.
  • Less suited to: Environments stuck on Linux kernels older than version 5.10.
07

Verdict: Cilium Service Mesh

Cilium Service Mesh uses an eBPF datapath in the kernel plus a proxy such as Envoy for protocols like HTTP, gRPC and DNS.

The documentation marks mutual authentication and L7 traffic management as beta, and installation needs Linux kernel 5.10 or later on a cluster configured with a CNI. Cisco announced in December 2023 a plan to acquire Isovalent, which led Cilium development; no country is named.

In our service mesh tools ranking Cilium Service Mesh stands at #8 of 13: Traefik Mesh sits directly above it and Kong Mesh directly below. From place 4 the established names follow in their ranked order; we publish no numeric score.

The vendor states no country of establishment, so Cilium Service Mesh is left out of the regional count for this list.

08

Cilium Service Mesh pros and cons in practice

Works well
  • The eBPF datapath moves part of the work into the kernel instead of per-pod proxies.
  • The installation guide ships with a built-in connectivity test to validate the result.
  • Documentation covers Ingress, Gateway API and GAMMA in one place, with a migration guide.
  • Example cluster commands exist for a long list of Kubernetes platforms, including k3s, RKE and Alibaba ACK.
Gets in the way
  • Mutual authentication and L7-aware traffic management carry a beta label in the documentation.
  • Linux kernel 5.10 or later is required, which rules out older node images.
  • Pods that were already running need a restart before they get Cilium networking.
  • The pages we read show no prices and name no country of establishment, so contract questions go to the vendor.
09

Living with Cilium Service Mesh: setup and exit

The documentation covers Kubernetes Ingress, Gateway API and GAMMA support, with demos for running beside Istio in ambient or sidecar mode.

Installation uses the Cilium CLI, which checks a sha256 file, then cilium install; cilium connectivity test validates it.

Unmanaged pods already running must be restarted to receive Cilium networking.

Example cluster commands span GKE, AKS, EKS, OpenShift, k3s and Alibaba ACK.

10

Cilium Service Mesh pricing

Pricing as recorded: Open source under Apache-2.0; no prices or plan names in the documentation read.

The documentation and repository pages we read show no prices for Cilium Service Mesh and name no trial for it. The open source project is distributed under Apache-2.0, with BPF code templates dual-licensed under GPL-2.0 and BSD-2-Clause, so the software itself can be installed from the project's releases. Cisco's December 2023 announcement said it planned to keep offering Isovalent Enterprise, an enterprise distribution of Cilium and Tetragon, but the pages we read give no plan names, amounts or support terms for that distribution. A buyer who wants commercial support therefore has to ask the vendor directly, and should budget engineering time for the kernel and CNI prerequisites that the installation guide lists.

Checked against cilium.io for Best Service Mesh Tools in 2026, review date 15 November 2026.

11

Cilium Service Mesh: data and security

The mutual authentication feature references SPIFFE for identity management and is marked beta in the documentation. The pages we read do not list certifications, data residency options or a data processing agreement.

Because Cilium is software that you install in your own cluster, traffic stays wherever you run it. Source code is public in the cilium/cilium repository, which allows inspection of the Apache-2.0 licensed code. The Cisco announcement and the documentation name no country of establishment for Cilium or Isovalent.

12

Fact sheet: Cilium Service Mesh

ProductCilium Service Mesh
Vendor websitecilium.io
Primary guideBest Service Mesh Tools in 2026
HeadquartersNot stated by the vendor
Alternatives pageNot written yet
Price visibilityModel recorded, no figure
Not in our dataheadcount, funding and customer count
Rank there#8 of 13
Head-to-head pagesNone yet
Catalogue tagseBPF, Gateway API, Beta features
Source codeOpen source, per our records
13

What Cilium Service Mesh connects to

Integrations the vendor names (9):

  • Kubernetes
  • Envoy
  • Istio ambient mode
  • Istio sidecar mode
  • Gateway API
  • GKE
  • AKS
  • EKS
  • OpenShift

Also in our records:

  • The documentation covers Kubernetes Ingress, Gateway API and GAMMA support, with demos for running beside Istio in ambient or sidecar mode.
  • Ecosystem tags in our records: Gateway API.
14

Alternatives to Cilium Service Mesh

3 products in this guide come closest to Cilium Service Mesh on tags, pricing and region.

  • Linkerd (#1 of 13): Rust micro-proxy mesh for Kubernetes that adds mutual TLS with no configuration. Suits: Kubernetes-only teams wanting automatic mutual TLS and per-workload metrics with little configuration.
  • Skupper (#6 of 13): Application-layer interconnect linking services across sites without VPNs or firewall rules. Watch out: the site describes no managed service, price list or named owner.
  • Traefik Mesh (#7 of 13): Not for: buyers who need a mesh with visible 2026 documentation. Sidecar-free SMI mesh routing through per-node proxies, with opt-in membership.
15

Where else Cilium Service Mesh is ranked

GuidePosition
Best Service Mesh Tools in 2026#8 of 13
16

Cilium Service Mesh: questions

9 answers
Is Cilium Service Mesh a European company?

The vendor pages we reviewed state no country of establishment for Cilium Service Mesh, so we do not give one.

Is Cilium Service Mesh one of the top service mesh tools?

Position 8 of 13 is where Cilium Service Mesh sits among service mesh tools.

Which tools compete with Cilium Service Mesh?

The nearest neighbours in our ranking are Linkerd, Skupper and Traefik Mesh. You will find each one reviewed in the service mesh tools ranking.

Is Cilium Service Mesh the right fit for me?

Clusters already on Cilium networking that want mesh features from it. Less suited to: environments stuck on Linux kernels older than version 5.10.

Is Cilium Service Mesh free, or what does it charge?

Our catalogue records Cilium Service Mesh’s pricing as: Open source under Apache-2.0; no prices or plan names in the documentation read. On free access, we found no free tier.

Which kernel version does the installation need?

The default installation guide states that the Linux kernel must be version 5.10 or later and that Kubernetes must already be configured to use a CNI.

Are all mesh features generally available?

No. The documentation marks mutual authentication and L7-aware traffic management as beta, so check the current label before relying on them in production.

Can Cilium be used together with Istio?

The documentation includes integration pages with demos for Istio in ambient mode and in sidecar mode.

Who owns Cilium?

The pages we read describe an open source project and a Cisco announcement from December 2023 about acquiring Isovalent, which it said had led Cilium development. No country is named.

17

Cilium Service Mesh: sources

Read from the vendor’s own pages on 14 November 2026.

18

How we rank

The same four questions are asked of every service mesh tools product: time to value, real cost, the way out and the intended buyer. Here that gives Cilium Service Mesh the #8 position in a list of 13. Details: how we rank software.