Ross ROSS = Recommend OSS · open-source software intelligence for agents

kumahq/kuma

🐻 The multi-zone service mesh for containers, Kubernetes and VMs. Built with Envoy. CNCF Sandbox Project. observed · 2026-08-28

github.com/kumahq/kuma · homepage · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

94/100

  • Activity 99
  • Release rhythm 85
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 0.0
  • age_days: 2730
  • days_rel: 23
  • days_push: 7
  • n_releases_24m: 117

Full methodology

Adoption not part of the score

3995 stars · 368 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Kuma is a CNCF Sandbox, Envoy-based service mesh that provides L4-L7 connectivity, discovery, security (mTLS), observability, and traffic control across Kubernetes and VM workloads. It supports single- and multi-zone deployments across clouds with automatic policy propagation and multi-mesh multi-tenancy.

Use cases

  • secure microservices with mutual TLS across clusters
  • run a service mesh spanning both Kubernetes and VMs
  • manage traffic routing, retries, and circuit breaking between services
  • observe service traffic with metrics, logs, and distributed tracing
  • connect services across multiple zones, clusters, and clouds
  • apply zero-trust security policies to east-west traffic
  • expose services through built-in or delegated gateways

When to choose

  • you need a multi-zone or multi-cluster service mesh across Kubernetes and VMs
  • you want Envoy-powered mesh features without requiring Envoy expertise
  • you need multi-tenancy with multiple isolated meshes
  • you want a CNCF-neutral project with broad policy support (mTLS, rate limiting, observability)

When to avoid

  • you run a single small Kubernetes cluster where native Kubernetes networking suffices
  • you are already standardized on another service mesh like Istio or Linkerd
  • you cannot operate sidecar proxies or a control plane
  • you need a lightweight mesh for very simple, low-traffic deployments

Facets

application · maturity stable

networking security monitoring api-gateway service-discovery cryptography rate-limiting microservices cloud-computing networking security infrastructure-as-code self-hosted cloud go service-mesh envoy sidecar-proxy mtls zero-trust multi-zone control-plane cncf traffic-management observability containers devops kubernetes docker linux

9 sources

Member repositories

RepositoryRoleHealth v2
kumahq/kumamain94

For agents

markdown · JSON · MCP: product_card(name="kumahq/kuma")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem