Linkerd

Ranked #1 of 13 for service mesh tools: Rust micro-proxy mesh for Kubernetes that adds mutual TLS with no configuration.

Commercial relationships can affect which products appear and how prominently. The Linkerd link is marked as every vendor link is, see disclosure.

Visit Linkerd See it in the service mesh tools ranking

01

Linkerd at a glance

HeadquartersNot stated by the vendor
APINo API details for Linkerd in our records
Best forKubernetes-only teams wanting automatic mutual TLS and per-workload metrics with little configuration
DeploymentOpen source code
Pricing modelOpen source code under Apache-2.0; Buoyant Premium and Strategic plans quoted on request
Free planNo
02

What is Linkerd?

Linkerd presents itself as a service mesh for Kubernetes that adds security, observability and reliability to any cluster. The homepage calls it written in Rust, CNCF graduated and open source, and credits Buoyant as the originator. Its design is a self-contained control plane, an incrementally deployable data plane and a small Rust proxy called linkerd2-proxy.

Mutual TLS is applied to on-cluster TCP traffic without configuration, and success rates, latencies and request volumes appear for every meshed workload. The code sits in the linkerd/linkerd2 repository under the Apache-2.0 licence. A commercial distribution, Buoyant Enterprise for Linkerd, is sold in Premium and Strategic plans whose prices are not published. Neither the Linkerd homepage nor the Buoyant privacy page names a country.

03

Linkerd key features

  • Zero-configuration mutual TLS. The homepage says mutual TLS is added to any on-cluster TCP communication with no configuration. A team gets encrypted, authenticated service traffic from installation alone, although the page does not detail certificate lifetimes.
  • Per-workload golden metrics. Success rates, latencies and request volumes are shown for every meshed workload without extra setup. This gives operators a first view of service health before they build any dashboards of their own.
  • Traffic reliability features. Latency-aware load balancing, cross-cluster failover, retries, timeouts and blue-green deploys are listed on the homepage. The pages read do not say which of these belong to the open source code and which to the paid plans.
  • Rust micro-proxy. The data plane uses linkerd2-proxy, written in Rust, with a self-contained control plane. The repository describes the project as an ultralight, security-first mesh, a claim the pages support with architecture rather than benchmarks.
  • Viz extension. Running linkerd viz install adds an on-cluster metrics stack and dashboard. It is optional, so clusters that already run their own monitoring can skip it, and the guide also mentions Jaeger and multicluster extensions.
  • Gateway API based policy. The guide says Gateway API CRDs are needed for authorization policy and dynamic request routing. Policy therefore follows Kubernetes resources, which suits teams already managing configuration through manifests.
  • Enterprise plans for Linkerd. Buoyant lists Premium for multi-cluster communication, CVE remediation SLAs, L7 network security policies and Linux VM workloads. Strategic adds hotpatch releases, SBOMs, optional FIPS validated cryptography and 24x7 SLAs.
04

Who Linkerd suits

  • A platform team encrypting internal traffic. Injecting workloads into the mesh gives mutual TLS between them without touching application code. The team can confirm proxy health afterwards with the linkerd check --proxy command from the guide.
  • A start-up with fewer than 50 employees. Buoyant states that companies of this size can run Buoyant Enterprise for Linkerd in production at any scale. The pricing page does not explain what happens when headcount passes that line.
  • An operations team spanning several clusters. Cross-cluster failover and multi-cluster communication are named features, with the Premium plan covering multi-cluster communication. The team would need a quote, as the pricing page shows no amounts.
05

Getting started with Linkerd

The getting started guide expects a reachable Kubernetes cluster and kubectl. You install the linkerd CLI with an install script, then add the CRDs and control plane by piping linkerd install into kubectl apply, and verify the result with linkerd check. Gateway API CRDs are needed before authorization policy and dynamic request routing work, and the guide notes extra configuration for GKE private clusters and for clusters using Cilium as the CNI.

To try the mesh, the guide injects the Emojivoto sample application with linkerd inject and checks its proxies. The viz extension, installed with linkerd viz install, then provides the dashboard. The pages we read give no time estimate for any of these steps.

06

Our verdict on Linkerd

Under the Apache-2.0 licence and graduated within the CNCF, Linkerd was originated by Buoyant and has a self-contained control plane and the Rust-based linkerd2-proxy. Installation is a CLI plus kubectl apply.

The commercial split is the catch: Buoyant's pricing page shows no prices, and multi-cluster communication, L7 network security policies and CVE remediation SLAs sit in the Premium plan, whose button leads to a contact page.

Linkerd is entry #1 of 13 in the service mesh tools list: Kuma follows directly after it. Places 1 to 3 in every list go to challengers where the category has them, so this is a position on that rule and not a score.

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

07

Strengths and limits of Linkerd

Linkerd: strengths
  • Under the Apache-2.0 licence and graduated within the CNCF, Linkerd was originated by Buoyant and has a self-contained control plane and the Rust-based linkerd2-proxy.
  • Where it fits: Kubernetes-only teams wanting automatic mutual TLS and per-workload metrics with little configuration.
  • Catalogue tag: CNCF graduated.
  • Catalogue tag: Apache-2.0.
  • Rust proxy is among the traits we single out for it.
Where Linkerd does not
  • Buoyant Enterprise for Linkerd shows no prices; its plan buttons lead to a contact page.
  • Not for: Buyers who need a published price list before talking to anyone.
  • Gateway API CRDs are a prerequisite for authorization policy and dynamic request routing.
08

Linkerd pros and cons in practice

Works well
  • Mutual TLS arrives with no configuration for on-cluster TCP traffic.
  • The install path is short: a CLI, a kubectl apply and a linkerd check.
  • The code is Apache-2.0 and the project is CNCF graduated, per the homepage.
  • Small companies under 50 employees may run the enterprise distribution in production.
Gets in the way
  • Buoyant shows no prices, and the plan buttons lead to a contact page.
  • Multi-cluster communication, L7 network security policies and CVE remediation SLAs sit in Premium.
  • Gateway API CRDs must be added before authorization policy and dynamic routing work.
  • The pages read name no country of establishment.
09

Paying for Linkerd

Pricing as recorded: Open source code under Apache-2.0; Buoyant Premium and Strategic plans quoted on request.

The Linkerd code is published under Apache-2.0, and Buoyant's pricing page says Buoyant Enterprise for Linkerd is always free to try with no plan required. It adds that companies with fewer than 50 employees can run it in production at any scale; no trial length is stated. Two paid plans are named, Premium and Strategic, and neither shows a price: the plan buttons lead to a contact page. Premium covers multi-cluster communication, CVE remediation SLAs, L7 network security policies, automatic cross-cluster failover and Linux VM workloads. Strategic adds hotpatch releases, SBOMs, optional FIPS 140-2 and 140-3 validated cryptography and 24x7 SLAs. Buoyant Cloud features and HAZL appear as add-ons to those plans.

Where this comes from: the vendor pages at linkerd.io, checked for Best Service Mesh Tools in 2026 on 15 November 2026.

10

Linkerd in practice

The getting started guide needs a reachable cluster and kubectl, installs the CRDs and control plane with linkerd install, and verifies the result with linkerd check.

GKE private clusters and Cilium as the CNI need extra configuration.

11

Linkerd: data and security

Linkerd runs inside the customer's own cluster, so telemetry from the viz extension stays on-cluster by default. Mutual TLS covers on-cluster TCP communication. The pages we read state no SOC 2 or ISO certification.

FIPS 140-2 and 140-3 validated cryptography is named only as an option in Buoyant's Strategic plan or an add-on to Premium. The Buoyant privacy page names the company but gives no registered office, postal address or country, and the Linkerd homepage names none either.

12

Integrations and ecosystem

Integrations the vendor names (9):

  • Kubernetes
  • kubectl
  • Gateway API
  • Cilium
  • GKE
  • Jaeger
  • Emojivoto sample app
  • linkerd viz
  • Buoyant Cloud

Also in our records:

  • Gateway API CRDs are a prerequisite for authorization policy and dynamic request routing.
13

Fact sheet: Linkerd

ProductLinkerd
Vendor websitelinkerd.io
Price visibilityNot shown, sold by quote
Catalogue tagsCNCF graduated, Rust proxy, Apache-2.0
Alternatives pageNot written yet
Rank there#1 of 13
Head-to-head pagesNone yet
HeadquartersNot stated by the vendor
Primary guideBest Service Mesh Tools in 2026
Gaps in our recordsheadcount, funding and customer count
Source codeOpen source, per our records
14

What to look at instead of Linkerd

These are the nearest neighbours of Linkerd in the same list, picked on shared traits and price model.

  • Kuma (#2 of 13): Envoy-based mesh for Kubernetes and virtual machines, run from one control plane.
  • Istio (#3 of 13): Not for: small teams that cannot spare time to pick install profiles. Community mesh offering Layer 4 tunnels or Envoy sidecars, chosen per feature.
  • Traefik Mesh (#7 of 13): Suits: Kubernetes teams wanting opt-in meshing without injecting a sidecar into every pod.
  • Cilium Service Mesh (#8 of 13): A good match for: Clusters already on Cilium networking that want mesh features from it.
  • HashiCorp Consul (#10 of 13): Service discovery and mesh across on-premises, hybrid and multi-cloud networks. Suits: Operators spanning several environments who need service discovery alongside the mesh.
15

Where else Linkerd is ranked

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

Linkerd: questions

9 answers
Which country is Linkerd from?

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

Where does Linkerd stand among service mesh tools?

In our service mesh tools list Linkerd stands at place 1 of 13.

Who should choose Linkerd?

Kubernetes-only teams wanting automatic mutual TLS and per-workload metrics with little configuration. It does not fit as well for buyers who need a published price list before talking to anyone.

How much does Linkerd cost?

As recorded: Open source code under Apache-2.0; Buoyant Premium and Strategic plans quoted on request. On free access, nothing is free to use, as far as we recorded.

What else should I look at besides Linkerd?

Start with Kuma, Istio, Traefik Mesh, Cilium Service Mesh and HashiCorp Consul. Compare their entries before settling on Linkerd.

Who makes Linkerd?

The homepage names Buoyant as the originator. The project is described as CNCF graduated, and the main repository is under the Apache-2.0 licence.

Can we run it in production at no charge?

Buoyant says companies with fewer than 50 employees can run Buoyant Enterprise for Linkerd in production at any scale. Larger organisations need to ask about Premium or Strategic.

What does Premium add?

The pricing page lists multi-cluster communication, CVE remediation SLAs, L7 network security policies, automatic cross-cluster failover and Linux VM workloads.

Is a dashboard included?

The viz extension installs an on-cluster metrics stack and dashboard on request. Buoyant Cloud, a SaaS dashboard, is listed as an add-on to the Strategic plan.

17

Linkerd: sources

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

18

How we rank

We test for four things rather than for features: setup time, price in practice, exit and audience. On those tests Linkerd lands at place 1 of 13. The editorial process sets out how facts are gathered and how commercial links are handled.