Kuma

At #2 of 13 in our service mesh tools ranking, Kuma is summed up in the catalogue as: Envoy-based mesh for Kubernetes and virtual machines, run from one control plane.

Paid placement exists here and is disclosed. Whatever the arrangement, the Kuma link carries the same marker as all others (details).

Visit Kuma See it in the service mesh tools ranking

01

At a glance

HeadquartersNot stated by the vendor
Free planNo free tier on record
APIAn API is mentioned by the vendor
DeploymentOpen source code
Pricing modelOpen source under Apache-2.0; the Kuma pages show no prices or plans
Best forPlatform teams running Kubernetes and virtual machines together under one multi-zone control plane
02

What is Kuma?

Kuma calls itself the universal Envoy service mesh for distributed service connectivity, with Envoy bundled so that users need no Envoy expertise. The homepage counts more than 10 ready-to-use L4 and L7 policies for security, observability, discovery, routing and traffic reliability, and names Kubernetes, OpenShift and Universal virtual machine deployments, including hybrid setups.

One control plane can run several meshes and zones across clouds and clusters. The GitHub repository kumahq/kuma carries the Apache-2.0 licence. Kuma is a CNCF Sandbox project that Kong, Inc. originally created, and the commercial product built from it is Kong Mesh. The pages read show no prices for Kuma itself, no support offer and no company address, so the country is not stated.

03

Kuma key features

  • Bundled Envoy. Envoy ships with Kuma, and the homepage says users do not need to be Envoy experts. Teams get a proven proxy without writing proxy configuration by hand, though advanced tuning is not described.
  • Ready-made policies. More than 10 L4 and L7 policies cover security, observability, discovery, routing and traffic reliability. The homepage gives the count but the pages we read do not list each policy by name.
  • Multi-zone and multi-mesh. One control plane supports multi-zone deployments across clouds and clusters, and several meshes can be managed from it. This suits organisations that separate environments yet want one operating point.
  • Kubernetes, OpenShift and VMs. Supported platforms are Kubernetes, OpenShift and Universal mode for virtual machines, including hybrid environments. Services that have not moved to containers can therefore join the same mesh.
  • Four interfaces. Native CRDs, a GUI, a REST API and a CLI are listed. Teams can manage configuration declaratively or through the console, depending on how they work.
  • Zone egress option. The installation guide adds an optional zone egress through a flag on either install method. It is an opt-in component, so smaller installs can leave it out.
  • Apache-2.0 code under CNCF. The repository is Apache-2.0, and the homepage and community page place Kuma in the CNCF Sandbox. Sandbox is an early stage, so maturity is a point to weigh.
04

Who Kuma suits

  • An organisation mixing VMs and Kubernetes. Universal mode lets virtual machines join the same mesh as Kubernetes workloads. A team mid-migration can apply one set of policies to both during the transition.
  • A company with several regions or clouds. Multi-zone support under a single control plane lets operators view and govern zones together. The guide describes zone mode installation as the starting point.
  • A team wanting Envoy without proxy expertise. Bundled Envoy and ready-made policies reduce what operators must learn. Anyone needing custom proxy behaviour should check the documentation beyond the pages we read.
05

Getting started with Kuma

On Kubernetes, the installation guide installs the control plane in zone mode, either with kumactl install control-plane piped to kubectl apply or with the kuma/kuma Helm chart into the kuma-system namespace. An optional zone egress is enabled with a flag on either method. Application pods must be restarted afterwards so their data plane objects can be generated.

For admin access, the guide port-forwards the kuma-control-plane service on port 5681 and registers the control plane with kumactl using a bearer token from the admin-user-token secret. The pages we read do not cover the Universal installation for virtual machines in the same detail, and give no time estimate.

06

What we make of Kuma

Kuma was created by Kong, Inc. and is now a CNCF Sandbox project that bundles Envoy, so teams need no Envoy expertise. It runs on Kubernetes, OpenShift and virtual machines, and one control plane can manage several meshes and zones.

The pages read name no maintainers, no company address and no support offer; the commercial route is Kong Mesh, which has its own entry in this ranking.

The service mesh tools list places Kuma 2 of 13: the products next to it are Linkerd above and Istio below. Top-three spots are set aside for challengers, and Kuma holds one of them; read it as a position, not a grade.

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

07

Strengths and limits of Kuma

Kuma: strengths
  • Kuma was created by Kong, Inc.
  • Strongest for: Platform teams running Kubernetes and virtual machines together under one multi-zone control plane.
  • Multi-zone, one of the three traits the catalogue lists for Kuma.
  • CNCF Sandbox, one of the three traits the catalogue lists for Kuma.
  • Marked in our records as envoy bundled.
Where Kuma costs you
  • Poor match for: Teams that need a vendor contract and price list from this project.
  • Existing application pods need a restart before their data plane objects are generated.
  • The community page names no individual maintainers and no company address.
08

Kuma pros and cons in practice

Works well
  • Envoy is bundled, so no separate proxy knowledge is assumed.
  • One control plane covers several zones and meshes.
  • Virtual machines and Kubernetes share one mesh through Universal mode.
  • The Apache-2.0 repository is open to inspection.
Gets in the way
  • The pages read name no maintainers and no support offer.
  • CNCF Sandbox is an early project stage.
  • No company address or country appears on the Kuma pages.
  • Kong Mesh has no published prices, only Book Demo and Get Started.
09

Living with Kuma: setup and exit

On Kubernetes the control plane is installed in zone mode, through kumactl install control-plane piped to kubectl apply or through the kuma/kuma Helm chart into the kuma-system namespace.

Admin access means port-forwarding service port 5681 and registering the control plane with a bearer token.

10

Kuma pricing

Pricing as recorded: Open source under Apache-2.0; the Kuma pages show no prices or plans.

The Kuma pages read show no prices and name no plans, so the open source code under Apache-2.0 is the only offer described. Kong Mesh, the commercial product from Kong, is presented on konghq.com without prices; its calls to action are Book Demo and Get Started. The Kong Mesh page lists Kuma among its open source projects and describes Kong Mesh as an enterprise-grade service mesh for development and governance. Which Kong Mesh features exceed Kuma is not spelled out on the pages we read. Teams budgeting for support should therefore expect a conversation with Kong rather than a published rate card, and should treat self-run Kuma as having no vendor support promise.

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

11

Kuma: data and security

Kuma runs in the customer's own Kubernetes, OpenShift or VM environment, so data plane traffic stays within infrastructure the customer controls. The homepage lists security policies among its policy set, but the pages we read name no mutual TLS settings, certifications or compliance standards. The community page names The Kuma Authors as copyright holder and lists no individual maintainers. No company address or country appears on the Kuma pages.

12

Kuma integrations and ecosystem

Integrations the vendor names (9):

  • Kubernetes
  • OpenShift
  • Universal (VMs)
  • Envoy
  • Helm
  • kumactl
  • kubectl
  • Kong Mesh
  • CNCF
13

Kuma in numbers and labels

ProductKuma
Vendor websitekuma.io
Price visibilityModel recorded, no figure
Source codeOpen source, per our records
Primary guideBest Service Mesh Tools in 2026
Head-to-head pagesNo comparison written
HeadquartersNot stated by the vendor
Catalogue tagsCNCF Sandbox, Multi-zone, Envoy bundled
Alternatives pageNot written yet
Rank there#2 of 13
Not in our datacompany size and funding
14

Every guide that lists Kuma

GuidePosition
Best Service Mesh Tools in 2026#2 of 13
15

What to look at instead of Kuma

Shared tags and a similar price model decide who is listed here; where none match, the neighbours in the ranking fill in.

  • Tetrate Service Bridge (#4 of 13): Istio and Envoy based platform spanning containers, virtual machines and serverless. Suits: Enterprises wanting an Istio-based layer with multi-tenancy and NIST-aligned controls.
  • Skupper (#6 of 13): Application-layer interconnect linking services across sites without VPNs or firewall rules. Suits: Teams linking services across separate clusters, sites or edge devices without VPNs.
  • Traefik Mesh (#7 of 13): Sidecar-free SMI mesh routing through per-node proxies, with opt-in membership. Watch out: its documentation is dated 2023, and the vendor site has moved on to other products.
  • Cilium Service Mesh (#8 of 13): eBPF datapath mesh that moves connectivity out of application code. Watch out: two headline mesh features carry a beta label, which limits production use.
16

Kuma: questions

9 answers
Who is Kuma best for?

Platform teams running Kubernetes and virtual machines together under one multi-zone control plane. It does not fit as well for teams that need a vendor contract and price list from this project.

How does Kuma rank for service mesh tools?

Position 2 of 13 is where Kuma sits among service mesh tools.

Is Kuma a European company?

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

What are the main alternatives to Kuma?

The closest products in the same guide are Tetrate Service Bridge, Skupper, Traefik Mesh and Cilium Service Mesh. You will find each one reviewed in the service mesh tools ranking.

Is Kuma free, or what does it charge?

Open source under Apache-2.0; the Kuma pages show no prices or plans is how we record the pricing of Kuma. On free access, a paid plan is required, per our records.

Who created Kuma?

The community page says Kong, Inc. originally created it, and that its open community made it successful. It is now a CNCF Sandbox project.

Does Kuma only work on Kubernetes?

No. The homepage lists Kubernetes, OpenShift and Universal mode for virtual machines, including hybrid environments.

What is Kong Mesh?

Kong Mesh is Kong's commercial service mesh. Its page links Kuma in the open source list and gives no prices.

How is Kuma installed on Kubernetes?

Either with kumactl install control-plane piped to kubectl apply, or with the kuma/kuma Helm chart into the kuma-system namespace.

17

Kuma: sources

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

18

How we rank

Feature lists tell little, so positions rest on setup effort, the true price, portability and fit. Here that gives Kuma the #2 position in a list of 13. Method and commercial relationships are in our editorial process.