Softwr
Istio logo

Istio

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

As of 13 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.

Overview

What Istio does

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 it falls short

Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about 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.

Pricing

What Istio costs

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

Features

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

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 plan11 researched notes
  • Runs production-like development environments on your own Kubernetes cluster

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

    Free plan13 researched notes
  • Event gateway that receives, queues, retries and replays inbound webhooks

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

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

    Free, then $20/mo12 researched notes
  • Runs Terraform plan and apply from pull request comments, self-hosted and free

    Open source12 researched notes
  • Kubernetes development and testing automation with shared caching, now owned by Incredibuild

    Open source12 researched notes
  • Durable execution engine in Rust with a free tier and low-latency workflows

    Free, then $300/mo12 researched notes
  • Specification and tooling that turns source code into OCI images without Dockerfiles

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

    Pricing on request12 researched notes
  • The API platform for building and using APIs

    Free plan12 researched notes
  • High-performance build system for JavaScript and TypeScript monorepos

    Free plan9 researched notes
  • Highly configurable text editor built to enable efficient text editing

    Free plan10 researched notes
  • A declarative, GitOps continuous delivery tool for Kubernetes

    Free plan4 researched notes
  • A cross-platform IDE for C and C++

    Free plan11 researched notes
  • Self-hosted platform for provisioning governed cloud development environments

    Free plan8 researched notes
  • Production-grade container orchestration

    Free plan10 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

PHPRunner and ASPRunner.NET: low-code builders that turn databases into web apps

one-time

Desktop AI coding assistant that runs on DeepSeek models

freemium

Internal developer portal that scores service ownership and maturity rather than just cataloguing services

quote

Programmable CI/CD engine that runs your pipeline as containers on any runner

Per month per team for Dagger Cloud

Feature flag service priced per flag and environment with unlimited seats and unlimited monthly active users

Per month by feature flag and environment count

Analytics governance: define a tracking plan, generate typed code from it, and catch drift before release

Per editor seat per month

Event gateway that receives, queues, retries and replays inbound webhooks

Per month by delivered event count

Kubernetes development and testing automation with shared caching, now owned by Incredibuild

Open source, no licence fee

Compare Istio with alternatives