Softwr
Istio logo

Istio

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

As of 20 November 2026, Istio is free to use. Istio puts an Envoy proxy in front of every workload so that encryption, retries, traffic splitting and per-request metrics are configured centrally rather than written into each service. Softwr lists it under Developer Tools. Istio is launched in 2016.

Overview

What is Istio?

Istio is a service mesh for Kubernetes, originally created by Google, IBM and Lyft, and now a graduated project of the Cloud Native Computing Foundation, licensed under Apache 2.0. It uses Envoy as its data plane and a control plane component, istiod, that issues workload identities, distributes certificates and translates its custom resources into Envoy configuration. In the classic sidecar mode an Envoy container is injected into every pod; ambient mode, which reached general availability in Istio 1.24, replaces that with a per-node ztunnel for L4 and optional waypoint proxies for L7. It supports both its own API and the Kubernetes Gateway API. What distinguishes it is that it moves cross-cutting network behaviour out of application code and into infrastructure that a platform team owns. Mutual TLS with automatic certificate rotation, retries with budgets, timeouts, circuit breaking, canary traffic splitting by weight or header, and identical golden metrics and distributed traces for every service arrive without a library in any language. In a polyglot estate that is the commercial argument in full: without a mesh, each of those behaviours has to be implemented and kept current in every language your teams use, and it never is. With one, the security team can assert that all service-to-service traffic is encrypted and authenticated as a property of the platform. The organisations for which this works have a dedicated platform team, dozens or hundreds of services, and a compliance or reliability requirement that justifies the machinery. The trade-off is that the mesh becomes infrastructure you now operate. Upgrades require revisioned control planes and restarting every workload, misconfiguration surfaces as an opaque 503 rather than a validation failure, and below a certain scale a cloud load balancer or Linkerd delivers most of the benefit with far fewer moving parts, which is why the mesh so often becomes the largest single source of incidents in a small estate.

What people use it 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

The honest half

Where does Istio fall short?

Each is concrete and checkable: the half of a review a vendor will not write.

  • 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.

Cross-shopped

What are the alternatives to Istio?

The closest alternatives to Istio are Linkerd, Consul and Cilium. Each is a tool buyers genuinely weigh against it, with the reason why.

  • Istio vs Linkerd

    Linkerd: Lighter Kubernetes service mesh with a Rust data plane, chosen by teams that want mTLS and observability with less configuration.

  • Istio vs Consul

    Consul: HashiCorp service mesh and service discovery that also works across VMs and multiple platforms, not only Kubernetes.

  • Istio vs Cilium

    Cilium: eBPF-based networking that can provide a sidecar-free service mesh, an option for avoiding per-pod proxy overhead.

  • Istio vs Envoy

    Envoy: The proxy underneath Istio, usable directly when you want edge or gateway routing without a full mesh control plane.

Pricing

How much does Istio cost?

Istio is free to use. Taken from the vendor's own pricing page; prices move, so check before you buy.

Open Source

Free

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

Capabilities

What can Istio do?

Istio lists 8 features, including automatic mutual TLS, traffic splitting and resilience policies.

  • Automatic mutual TLS

    Encrypts and authenticates service-to-service traffic with issued workload identities and rotating certificates, without code changes

  • Traffic splitting

    Shifts a percentage of requests, or requests matching a header, to a new version for canary and blue-green releases

  • Resilience policies

    Per-route timeouts, retries with budgets, circuit breakers and outlier detection applied centrally

  • Authorization policies

    Allow and deny rules on service-to-service calls based on workload identity, namespace, method and path

  • Uniform telemetry

    Consistent request metrics, distributed tracing spans and access logs for every workload regardless of language

  • Ambient mode

    A sidecar-free architecture using a per-node ztunnel for L4 and waypoint proxies only where L7 features are needed

  • Gateway API support

    Implements the Kubernetes Gateway API alongside its own Gateway and VirtualService resources

  • Multi-cluster mesh

    Joins several Kubernetes clusters into one mesh with shared identity and cross-cluster service discovery

Answered, with sources

Questions people ask

Each answer names the page it came from, so you can check it rather than take our word for it.

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.

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.

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.

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.

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.

Behind it

Who makes Istio?

Checked against

Sources

The pages the facts above were read from. Prices and limits change, so the vendor's own page is the final word.

Share

Keep looking

Where to go from Istio

Best Developer Tools software for

Compare Istio with

Other Developer Tools software

  • A high-performance L7 proxy written in C++ that is configured by an API rather than a config file, and is usually deployed under a control plane.

    Free plan14 researched notes
  • Runs production-like development environments on your own Kubernetes cluster

    Free plan15 researched notes
  • Infrastructure-as-code orchestration for Terraform, OpenTofu, Pulumi and Kubernetes

    Free, then $399/mo14 researched notes
  • Event gateway that receives, queues, retries and replays inbound webhooks

    Free, then $39/mo15 researched notes
  • Internal developer portal that scores service ownership and production readiness

    Pricing on request14 researched notes
  • Cloud development environments repositioned as a control plane for software engineering agents

    Free, then $20/mo13 researched notes
  • Kubernetes development and testing automation with shared caching, now owned by Incredibuild

    Open source14 researched notes
  • Runs Terraform plan and apply from pull request comments, self-hosted and free

    Open source13 researched notes
  • Specification and tooling that turns source code into OCI images without Dockerfiles

    Open source14 researched notes
  • Internal developer portal that scores service ownership and maturity rather than just cataloguing services

    Pricing on request14 researched notes
  • Durable execution engine in Rust with a free tier and low-latency workflows

    Free, then $300/mo15 researched notes
  • Engineering guardrails for the AI era

    Free plan13 researched notes
  • Complete toolchain for embedded software development

    Pricing on request10 researched notes
  • Microcontroller Development Kit for Arm-based devices

    Free plan11 researched notes
  • The dev platform for the next 100 billion commits

    Free, then $100/mo13 researched notes
  • Continuous delivery and runbook automation for releases

    Free plan11 researched notes
  • Fast, disk space efficient package manager

    Free plan14 researched notes
  • Production-grade container orchestration

    Free plan12 researched notes

Softwr does not host reviews and shows no star rating for Istio, because a rating we did not collect is not ours to publish. What is here is the pricing and platform detail from the vendor’s own pages, limitations we could state concretely, and alternatives a reviewer confirmed people weigh against it. Tell us if any of it is wrong.

More on Istio

Best Developer Tools software alternatives

Cloud hosted development environments configured by dev container files

usage-based

TypeScript toolkit from Vercel for building AI applications and agents

open-source

Metalinter that runs and manages linters, formatters and security scanners

freemium

Free graphical Git client from Atlassian for Windows and macOS

free

Open source build automation tool for Java, Kotlin and Android projects

open-source

Git GUI client and developer tool suite with a free Community plan and paid team plans

freemium

Self-hosted, open source Git service with issues, CI/CD and package hosting

open-source

Minimal container base images from Google that hold only an app and its runtime

open-source

Compare Istio with alternatives