Is Cilium or Vitess better?

Neither clearly leads. Cilium starts at Free and Vitess at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.

Which is cheaper, Cilium or Vitess?

Cilium starts at Free and Vitess at Free.

Does Cilium or Vitess run on more platforms?

Cilium runs on Kubernetes, Linux. Vitess runs on Linux, macOS, Docker, Kubernetes.

Can I use Cilium for free?

Both have a free tier, so you can try either at no cost before committing.

What is Cilium best used for?

Cilium is most often used for kubernetes networking at a scale where iptables-based cni performance degrades, network policy expressed on workload identity rather than fragile ip rules, seeing which services actually talk to each other, and what policy is dropping. Of those, kubernetes networking at a scale where iptables-based cni performance degrades and network policy expressed on workload identity rather than fragile ip rules are not what Vitess is typically brought in for.

What can Cilium do that Vitess cannot?

Cilium covers eBPF datapath, Identity-based policy, Hubble observability, Sidecar-free mesh. Vitess covers Horizontal Sharding, Connection Pooling, Query Routing, Online Schema Changes.

Cloud · head to head

Cilium vs Vitess

Cilium

Cloud

eBPF-based networking, observability and security for Kubernetes

From: Free
Rated: -

Full review Website

Vitess

Databases

Scalable database clustering system for horizontal scaling of MySQL

From: Free
Rated: -

Full review Website

The short version

Each has a real cost: Cilium requires a recent Linux kernel, which rules out older distributions and some managed environments; Vitess vTGate scatter queries without sharding key incur significant performance penalties
They diverge on capability: Cilium covers eBPF datapath, Vitess covers Horizontal Sharding.
Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Cilium and Vitess actually diverge.

Attributes where Cilium and Vitess differ
Attribute	Cilium	Vitess
Pricing model	Open source, no licence fee	Unknown
Platforms	Kubernetes, Linux	Linux, macOS, Docker, Kubernetes
Category	Cloud	Databases
Founded	Unknown	2010

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Cilium

eBPF datapath
Identity-based policy
Hubble observability
Sidecar-free mesh

Only in Vitess

Horizontal Sharding
Connection Pooling
Query Routing
Online Schema Changes
Shard Management
Replication Management
Automated Failover
MySQL

What people use each for

The jobs each tool is most often brought in to do.

Cilium

Kubernetes networking at a scale where iptables-based CNI performance degradesnot Vitess
Network policy expressed on workload identity rather than fragile IP rulesnot Vitess
Seeing which services actually talk to each other, and what policy is droppingnot Vitess

Vitess

Transaction processingnot Cilium
Data storagenot Cilium
Application backendnot Cilium
Reportingnot Cilium
Data analyticsnot Cilium

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Cilium

Requires a recent Linux kernel, which rules out older distributions and some managed environments
eBPF is genuinely hard to debug when it misbehaves, and the skill is rare on most teams
Broad scope — CNI, policy, mesh, observability — means the learning curve covers several domains at once

Vitess

VTGate scatter queries without sharding key incur significant performance penalties
Foreign key constraints not enforced across shards, requiring application-level integrity handling
Single primary per keyspace limits multi-region write capabilities
Distributed transactions without proper sharding key routing suffer performance degradation

Pricing, plan by plan

Cilium

Free

CiliumFree
- Full functionality
- No usage limits
- Community support

Vitess

Free

No published plan breakdown. See the Vitess review.

Which should you pick?

Choose Cilium if

You need ebpf datapath.
You want to start without paying.
You work on Kubernetes, Linux.
You also want identity-based policy.

Cilium review

Choose Vitess if

You need horizontal sharding.
You want to start without paying.
You work on Linux, macOS, Docker, Kubernetes.
You also want connection pooling.

Vitess review

Questions people ask

Is Cilium or Vitess better?: Neither clearly leads. Cilium starts at Free and Vitess at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cilium or Vitess?: Cilium starts at Free and Vitess at Free.
Does Cilium or Vitess run on more platforms?: Cilium runs on Kubernetes, Linux. Vitess runs on Linux, macOS, Docker, Kubernetes.
Can I use Cilium for free?: Both have a free tier, so you can try either at no cost before committing.
What is Cilium best used for?: Cilium is most often used for kubernetes networking at a scale where iptables-based cni performance degrades, network policy expressed on workload identity rather than fragile ip rules, seeing which services actually talk to each other, and what policy is dropping. Of those, kubernetes networking at a scale where iptables-based cni performance degrades and network policy expressed on workload identity rather than fragile ip rules are not what Vitess is typically brought in for.
What can Cilium do that Vitess cannot?: Cilium covers eBPF datapath, Identity-based policy, Hubble observability, Sidecar-free mesh. Vitess covers Horizontal Sharding, Connection Pooling, Query Routing, Online Schema Changes.

Answered from the vendors’ own pages

Cilium: Is Cilium free?

Yes, open source and CNCF-graduated. Isovalent sells an enterprise distribution and support.

Vitess: Is Vitess free to use?

Yes. Vitess is completely free and open source under the Apache 2.0 license. It is a graduated CNCF project with no licensing costs or pricing tiers.

Source

Cilium: What does eBPF change?

It lets Cilium run packet-processing programs inside the kernel instead of relying on iptables rule chains, which behave poorly as the number of services grows.

Vitess: What databases does Vitess support?

Vitess supports MySQL and MariaDB as backend databases. It acts as a middleware layer that adds sharding and orchestration capabilities on top of these databases.

Source

Cilium: Does Cilium replace a service mesh?

It can cover much of what a mesh does without sidecars, though full mesh feature sets still favour Istio or Linkerd.

Vitess: Does Vitess require Kubernetes to run?

No. Vitess can run on Kubernetes using the Vitess Operator, but it can also be deployed on traditional infrastructure. Kubernetes integration is optional and provides additional automation benefits.

Source

Vitess: How does Vitess handle cross-shard transactions?

Vitess supports distributed transactions across shards, but they require queries to be routed through the sharding key. Transactions without a proper sharding key can result in slower performance.

Source

Vitess: Does Vitess enforce foreign key constraints?

Vitess does not enforce foreign key constraints across shards by default. Referential integrity must be managed at the application layer, though per-database support can be enabled with limitations.

Source

Cilium vs Vitess

Cilium

Vitess

The short version

Where they differ

What each one covers

Only in Cilium

Only in Vitess

What people use each for

Cilium

Vitess

Where each one falls short

Cilium

Vitess

Pricing, plan by plan

Cilium

Vitess

Which should you pick?

Choose Cilium if

Choose Vitess if

Questions people ask

Answered from the vendors’ own pages

Related pages

More on Cilium

More on Vitess

Keep looking

Other head to heads