Softwr

Developer Tools · head to head

Istio vs Preact

Istio logo

Istio

Developer Tools

A Kubernetes service mesh that adds mutual TLS, traffic control and telemetry between services without changing application code.

From
Free
Free plan
Yes
Visit IstioFull review
Preact logo

Preact

Web Development

3kB alternative to React with the same modern API

From
Free
Free plan
Yes
Visit PreactFull review

The short version

  • Both are free.
  • Only Istio lists automatic mutual TLS; only Preact lists 3kB runtime.
  • Where Preact falls short: compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Istio and Preact actually diverge.

Attributes where Istio and Preact differ
AttributeIstioPreact
Pricing modelOpen-sourceOpen source, no licence fee
CategoryDeveloper ToolsWeb Development

Identical on both: starting price (Free), free tier (Yes), platforms (Web).

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 Istio

  • Automatic mutual TLS
  • Traffic splitting
  • Resilience policies
  • Authorization policies
  • Uniform telemetry
  • Ambient mode
  • Gateway API support
  • Multi-cluster mesh

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.

Istio

  • Proving to an auditor that all internal service traffic is encrypted and authenticated, as a platform property rather than a per-team promisenot Preact
  • Progressive delivery, where releases shift traffic by percentage or header and roll back without a redeploynot Preact
  • A polyglot estate where implementing retries, timeouts and tracing in every language's client library has already failednot Preact
  • Connecting several Kubernetes clusters into one addressable service namespace with shared workload identitynot Preact

Preact

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

Where each one falls short

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

Istio

  • Sidecar mode adds an Envoy container to every pod, which costs CPU and memory per workload and adds a hop of latency in each direction, and it introduces a startup ordering problem where an application container can begin making calls before its proxy is ready
  • Upgrades are projects rather than patches: you run revisioned control planes, canary the new revision and restart every workload to pick up new sidecars, and Istio supports only a narrow band of recent minor versions, so this recurs roughly quarterly for as long as you run it
  • The API surface is large, spanning VirtualService, DestinationRule, Gateway, PeerAuthentication, AuthorizationPolicy, Sidecar and the Kubernetes Gateway API, and a mistake usually appears as a 503 with an Envoy response flag rather than a rejected configuration, so debugging requires Envoy knowledge, not just Istio knowledge
  • Ambient mode removes the sidecar but is a different architecture with its own components and does not cover every feature the sidecar path does, so adopting it is a migration and a re-test of your policies rather than a configuration switch
  • It is Kubernetes-first; adding virtual machine workloads to the mesh is supported but much less well-trodden, so a mixed estate of Kubernetes and VMs ends up maintaining two networking and identity models
  • Below a few dozen services, most of what teams actually want (encrypted internal traffic, retries, weighted rollouts) is available from a cloud load balancer or from Linkerd with a fraction of the components, and at that scale Istio commonly becomes the single largest source of production 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

Istio

Free
  • Open SourceFree
    • self-hosted installation
    • service mesh capabilities
    • cloud native computing foundation project

Preact

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

Which should you pick?

Choose Istio if

  • You need automatic mutual tls.
  • You want to start without paying.
  • You also want traffic splitting.
Istio 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 Istio or Preact better?
Neither clearly leads. Istio 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, Istio or Preact?
Istio starts at Free and Preact at Free.
Does Istio or Preact run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use Istio for free?
Both have a free tier, so you can try either at no cost before committing.
What is Istio best used for?
Istio is most often used for proving to an auditor that all internal service traffic is encrypted and authenticated, as a platform property rather than a per-team promise, progressive delivery, where releases shift traffic by percentage or header and roll back without a redeploy, a polyglot estate where implementing retries, timeouts and tracing in every language's client library has already failed, connecting several kubernetes clusters into one addressable service namespace with shared workload identity. Of those, proving to an auditor that all internal service traffic is encrypted and authenticated, as a platform property rather than a per-team promise and progressive delivery, where releases shift traffic by percentage or header and roll back without a redeploy are not what Preact is typically brought in for.
What can Istio do that Preact cannot?
Istio covers Automatic mutual TLS, Traffic splitting, Resilience policies, Authorization policies. Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering.

Answered from the vendors’ own pages

Istio: Do we need a service mesh at all?

Only if you have enough services, or a compliance requirement, that implementing mTLS, retries and tracing per language has become unmanageable. Below roughly a few dozen services, an ingress controller plus good client libraries usually delivers more reliability for less operational cost.

Preact: Is Preact free?

Yes, open source under the MIT licence.

Istio: Sidecar mode or ambient mode?

Ambient removes the per-pod proxy and its startup ordering problems and costs less at high pod counts, but it is a newer architecture and does not cover every sidecar feature. New deployments should evaluate ambient first; existing sidecar meshes should treat the move as a migration project.

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.

Istio: How does it compare with Linkerd?

Linkerd is deliberately smaller, uses its own Rust proxy rather than Envoy, and is quicker to operate; Istio has a far larger feature surface, multi-cluster and VM support, and broader vendor backing. Note that Linkerd's stable distribution builds are commercially licensed by Buoyant, whereas Istio's releases are freely available.

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.

Istio: Who supports it commercially?

Solo.io and Tetrate sell supported distributions and control planes, and Google offers Cloud Service Mesh as a managed option. The upstream project itself is CNCF-governed with community support.

Istio: Does it work outside Kubernetes?

Partly. Virtual machine workloads can be added to a mesh, but the tooling, documentation and community experience are heavily Kubernetes-centred, so a VM-majority estate is fighting the grain of the project.

Share

Related pages

More on Istio

More on Preact

Keep looking

Other head to heads