Softwr

Cloud · head to head

Linkerd vs Preact

Linkerd logo

Linkerd

Cloud

Lightweight service mesh for Kubernetes

From
Free
Rated
-
Full reviewWebsite
Preact logo

Preact

Web Development

3kB alternative to React with the same modern API

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Linkerd deliberately fewer features than Istio, so complex routing and multi-cluster policy can hit its limits; Preact compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
  • They diverge on capability: Linkerd covers Automatic mutual TLS, Preact covers 3kB runtime.
  • Prices and features above were last checked on 29 August 2026.

Where they differ

Only the attributes on which Linkerd and Preact actually diverge.

Attributes where Linkerd and Preact differ
AttributeLinkerdPreact
PlatformsKubernetes, LinuxWeb
CategoryCloudWeb Development

Identical on both: starting price (Free), pricing model (Open source, no licence fee), 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 Linkerd

  • Automatic mutual TLS
  • Golden metrics
  • Rust micro-proxy
  • Traffic policy

Only in Preact

  • 3kB runtime
  • preact/compat
  • Same modern API
  • Fast rendering

What people use each for

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

Linkerd

  • Adding mutual TLS between services to satisfy a compliance requirementnot Preact
  • Getting per-service latency and success rates without instrumenting applicationsnot Preact
  • Progressive delivery with traffic splitting during rolloutsnot Preact

Preact

  • Embedded widgets that load inside someone else’s page and must stay smallnot Linkerd
  • Marketing and content sites where JavaScript payload affects Core Web Vitalsnot Linkerd
  • Applications targeting low-bandwidth or low-powered devicesnot Linkerd

Where each one falls short

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

Linkerd

  • Deliberately fewer features than Istio, so complex routing and multi-cluster policy can hit its limits
  • Kubernetes only, with no story for workloads outside a cluster
  • A sidecar per pod is still real memory and latency overhead, however small, and a mesh is another layer to debug during incidents

Preact

  • Compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
  • Behavioural differences from React exist in edge cases, particularly around event handling
  • A much smaller community, so unusual problems have fewer existing answers than React

Pricing, plan by plan

Linkerd

Free
  • LinkerdFree
    • Full functionality
    • No usage limits
    • Community support

Preact

Free
  • PreactFree
    • Full library
    • Commercial use permitted
    • No usage limits

Which should you pick?

Choose Linkerd if

  • You need automatic mutual tls.
  • You want to start without paying.
  • You work on Kubernetes, Linux.
  • You also want golden metrics.
Linkerd review

Choose Preact if

  • You need 3kb runtime.
  • You want to start without paying.
  • You also want preact/compat.
Preact review

Questions people ask

Is Linkerd or Preact better?
Neither clearly leads. Linkerd starts at Free and Preact at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Linkerd or Preact?
Linkerd starts at Free and Preact at Free.
Does Linkerd or Preact run on more platforms?
Linkerd runs on Kubernetes, Linux. Preact runs on Web.
Can I use Linkerd for free?
Both have a free tier, so you can try either at no cost before committing.
What is Linkerd best used for?
Linkerd is most often used for adding mutual tls between services to satisfy a compliance requirement, getting per-service latency and success rates without instrumenting applications, progressive delivery with traffic splitting during rollouts. Of those, adding mutual tls between services to satisfy a compliance requirement and getting per-service latency and success rates without instrumenting applications are not what Preact is typically brought in for.
What can Linkerd do that Preact cannot?
Linkerd covers Automatic mutual TLS, Golden metrics, Rust micro-proxy, Traffic policy. Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering.

Answered from the vendors’ own pages

Linkerd: Is Linkerd free?

The open-source project is free. Buoyant, its maintainer, sells enterprise distributions and support separately.

Preact: Is Preact free?

Yes, open source under the MIT licence.

Linkerd: Linkerd or Istio?

Linkerd trades features for simplicity, with a smaller proxy and far less configuration. Istio is more capable and correspondingly more work to run.

Preact: Can I use React libraries with Preact?

Most, through the preact/compat layer. Compatibility is good but not complete, so libraries relying on React internals can break.

Linkerd: Do I need a service mesh at all?

Only if you need mutual TLS, uniform retries or per-service traffic metrics across many services. For a handful of services it is usually more machinery than the problem justifies.

Preact: Why choose Preact over React?

Bundle size, almost always. If payload is not a binding constraint, React’s ecosystem is usually the better trade.

Share

Related pages

More on Linkerd

More on Preact

Keep looking

Other head to heads