1. Market Context
1. Market Context
A service mesh moves service-to-service communication out of application code and into infrastructure. A control plane issues workload identities and policy. A data plane of sidecar proxies, shared node-level proxies, or kernel-level programs encrypts, routes, and observes traffic. Some products offer L7 functions only through optional components.
Most products in this Radar build on a small number of graduated upstream Cloud Native Computing Foundation (CNCF) projects: Istio, Linkerd, and Cilium. What separates the field is where mesh functions run, which security defaults apply out of the box, how far the mesh extends beyond Kubernetes, and who does the work of keeping it current. Buyers are choosing an architecture and an operating model as much as a feature set. Five themes capture where the field separates.
Upstream Projects Set the Terms of Competition
Most commercial products here are distributions or enterprise editions of a foundation-hosted open-source project, and the projects themselves compete alongside them. A managed cloud service and a few independently developed platforms make up the rest. The most widely adopted project anchors much of the field, and the managed cloud service uses its APIs for configuration as well.
Where products share a base, commercial value shifts from mesh features to the release line itself: long-term CVE patching, FIPS builds, tested platform matrices, multicluster tooling, and a vendor accountable for incidents. Lineage also sets the pace a buyer inherits. One distribution holds an upstream base several minor releases behind the current line, while others ship in step with upstream or within one release of it.
What this means for buyers: Decide on the upstream project before the vendor. Once you choose the base, compare distributions on what they add: the support window, patch commitments, FIPS and platform coverage, and how far the release line trails upstream. A distribution that stays on an older upstream release trades new capability for predictability, so make that tradeoff explicit in the contract.
The Data Plane Splits Three Ways
A proxy alongside each workload remains the production norm across most of the field, whether a full Envoy sidecar, a purpose-built Rust microproxy, or proxyless gRPC libraries for some clients. A few products run ambient and sidecar data planes side by side at general availability: node-level proxies carry L4 identity and encryption, waypoint proxies add L7 processing where needed, and namespaces move between modes reversibly.
A few more are sidecarless by design. Most of these handle traffic with eBPF programs in the node kernel and a shared per-node proxy, and one routes traffic through site-level nodes that the vendor manages as a service. Some sidecar products list ambient or eBPF modes at alpha or experimental status, and another has removed its experimental eBPF path.
What this means for buyers: Pick the data plane model first: it decides resource cost, upgrade mechanics, and which products remain options. If ambient is the target, ask whether sidecar and ambient workloads coexist at general availability and whether migration is reversible per namespace. If the mesh runs inside the network layer, confirm which security features are generally available there.
Secure by Default Is Still a Configuration Choice
Every product encrypts service traffic, but defaults differ sharply. Some products install with strict mTLS and refuse plaintext unless an operator declares an exception. Others encrypt meshed traffic automatically but accept plaintext from unmeshed sources until an operator tightens policy. The most widely adopted project and some of its distributions ship permissive inbound defaults, which makes strict enforcement an operator task.
In the kernel-based products, mesh-managed mTLS and SPIFFE mutual authentication remain in beta, and transport encryption comes from WireGuard or IPsec instead. Cryptography is moving quickly. A small group negotiates hybrid post-quantum key exchange by default, and others offer it once configured or in a release candidate. FIPS paths range from validated builds to cipher restrictions on hosts running in FIPS mode.
What this means for buyers: Audit defaults, not datasheets. Ask what a fresh installation enforces before anyone touches it, how the mesh handles plaintext from unmeshed workloads, and whether workload certificates chain to your enterprise CA. Regulated buyers should confirm which validated cryptographic module covers the data plane and whether post-quantum key exchange works in FIPS mode.
The Mesh Reaches Past Kubernetes, Unevenly
Several products enroll VMs, bare-metal hosts, and Amazon ECS tasks as first-class mesh members, with the same discovery, identity, and policy as Kubernetes services. These products also join zones, clusters, and data centers under a global control plane. Others add VMs to the mesh through mesh expansion features while keeping Kubernetes as their primary platform. At the other end, one product runs only on its parent Kubernetes platform, and the kernel-based products stay within Kubernetes clusters.
Multicluster designs vary just as much. Some run independent control planes per cluster that exchange scoped service information, some distribute policy from one management plane to per-cluster instances, some rely on a shared trust anchor, and some copy policy objects to each cluster.
What this means for buyers: Inventory your estate before you build a shortlist. Count the workloads that run outside Kubernetes today and will still be there in three years, and test the mesh against them, not only against pods. For multicluster designs, ask what happens to cross-cluster traffic, identity, and new configuration when one cluster or one control plane fails.
AI Traffic Arrives Mostly Through Companion Products
Agent gateways, AI gateways, and agent routers carry most of the governance of AI agent and model traffic. Vendors sell them as companion products rather than inside the mesh SKU. They add token metering, model-aware routing, and prompt filtering, and in some cases run inside the mesh as a waypoint.
The upstream reference project adds model-aware routing for inference traffic through a Gateway API extension. One specialist platform registers MCP agents as mesh services with workload identities, allow-lists the tools each agent may call, inspects prompts for injection and PII, and sets token budgets per team. Another product includes AI service roles only in a release candidate, not yet in a production release. The capability is real but early, and the packaging is unsettled.
What this means for buyers: Separate the mesh decision from the AI gateway decision unless one product truly delivers both. Ask which AI controls ship in the mesh SKU, which require a companion product and license, and whether agent identity reuses the mesh's workload identity. Treat release-candidate and preview AI features as roadmap items until they reach a production release.
2. Radar Graphic
2. Radar Graphic
Figure 1. GigaOm Radar for Service Mesh. Inner ring denotes Leaders and outer ring denotes Challengers; dot color carries market velocity.
Notable Patterns
The paragraphs below describe how this market populates each quadrant. Section 3, Tech Buying Triad, gives the house definitions of the quadrants.
Foundation Builders. These products treat the mesh as dependable infrastructure for estates that cannot absorb disruption. Products here run sidecar data planes in production and sell continuity: long-lived release lines with LTS windows, validated platform matrices, staged CA rotation, and governance layered over many clusters and runtimes, including VMs and container services outside Kubernetes. Ambient operation is absent or still early, and some products in this quadrant hold a deliberately conservative upstream base. Change arrives as hardening and lifecycle work rather than new architecture.
Agile Optimizers. The largest group improves a workflow buyers already run, release by release. The improvements are operational: lighter per-pod proxies, post-quantum key exchange switched on by default, managed control planes with gradual proxy upgrades, ambient operation delivered inside an existing platform subscription, and mesh features built into the cluster's networking layer. Products here ship often and ask the buyer to keep pace, but none asks for a wholesale rearchitecture to get the next gain.
Disruptive Pioneers. Products here change where mesh functions live. One enforces identity-aware policy in kernel eBPF programs and hands L7 traffic to a shared per-node proxy. Another delivers the mesh as a site-level fabric managed from a SaaS console, and a third extends an accredited zero-trust platform to AI agent and MCP traffic. Each trades some conformance with mesh standards, such as Gateway API routing for east-west traffic or generally available mesh mTLS, for a model the sidecar meshes do not offer.
Enduring Innovators. The smallest group treats ambient operation as the long-horizon target and makes the path there safe. Ambient and sidecar workloads coexist in one mesh at general availability, and services move between modes incrementally and reversibly. Multicluster ambient matures release by release toward a single mesh across clusters and clouds. The value compounds as more of the estate moves onto the new data plane, while vendors continue to support the sidecar model for as long as buyers need it.
3. Tech Buying Triad
3. Tech Buying Triad
The quadrant descriptions and decision framework help buyers read this Radar from an enterprise procurement perspective. The Radar plots solutions on two axes: Operational Focus versus Strategic Focus, and Stability-Centered versus Evolution-Centered. Placement therefore signals both the outcome a product aims to deliver and how it approaches change.
The Tech Buying Triad maps decision responsibility: the CIO owns Brown Money tradeoffs, the CTO owns Green Money tradeoffs, and the CISO owns GRCS tradeoffs. The Triad treats Emerging Technology inputs as consulted advice. In service mesh, all three roles hold a real stake, and misalignment among them is a common reason deployments stall at the pilot stage.
Role | Bucket | What the bucket means | Responsibilities in the procurement |
CIO | Brown Money | Operational and infrastructure value: capabilities tied to operational reliability, cost containment, and table-stakes function. | Resource Efficiency and Data Plane Overhead, Sidecarless / Ambient / eBPF Architecture Support, Sidecar-to-Ambient Migration and Coexistence, Control Plane Scalability, Control Plane Resilience and Blast Radius, Operational Lifecycle and Upgrades, Platform and Distribution Support, Day-2 Tooling and Stack Integration. |
CTO | Green Money | Innovation and growth value: capabilities tied to architectural durability, interoperability, and competitive differentiation. | Multi-Cluster and Hybrid Cloud Management, Non-Kubernetes and Multi-Runtime Support, Multiprotocol Support, Progressive Delivery and Advanced Traffic Control, Resilience and Circuit Protection Depth, Extensibility and Programmability, Gateway API / GAMMA Conformance, Load Balancing and Locality Routing. |
CISO | GRCS | Governance, risk, compliance, and security: the controls required to operate the technology safely and within policy. | mTLS Enforcement Posture, Workload Identity and Federation, Enterprise PKI and CA Integration, L7 Authorization Granularity, FIPS and Regulated-Environment Cryptography, Audit Logging and Compliance Reporting, Supply Chain and Patch Integrity, Policy Rollout Safety. |
All three (consulted) | Emerging Technology | Forward-looking capabilities that signal where the market is moving; not owned by any single role. | Input on AI and Agentic Traffic Governance, eBPF Data Plane Maturity, AI-Assisted Policy and Operations, WebAssembly Extensibility Maturity, Ambient Multicluster Maturity, Post-Quantum Cryptography, and Runtime Security and Observability Convergence, to inform tradeoffs across Brown Money, Green Money, and GRCS. |
Quadrants
Foundation Builders
The buyer is typically a CIO or a platform engineering lead running large, established Kubernetes and VM estates where a control plane outage or a disruptive upgrade is expensive. The purchase is operational confidence: mTLS and workload identity that do not require rearchitecting the data plane every eighteen months, traffic management that behaves consistently across Kubernetes versions, long support windows, and conservative, documented upgrade paths. Change is the risk in this quadrant, so buyers judge vendors here on continuity before anything else.
Agile Optimizers
The buyer here is a platform engineering team or SRE group that treats the mesh as a living system and is comfortable adopting releases on a regular cadence. The intent is still operational: lower resource overhead, simpler day-2 operations, faster multicluster failover, and better telemetry on the workflow already in production. This buyer expects measurable improvement from each release and funds the work from platform budgets rather than a transformation program. Vendors land here when each release removes friction from running the mesh, without asking the buyer to adopt a new architecture to get it.
Enduring Innovators
The buyer is a CTO or platform architect who expects the mesh to become the foundation of a zero-trust architecture or a multicloud application platform. Over several years, the buyer requires a predictable roadmap, sustained investment, and enterprise support commitments around an architecture whose value compounds as more of the estate moves onto it. These buyers accept measured change in exchange for depth: federated control, enterprise PKI and SIEM integration, FIPS-validated builds, and a supported migration path to the target data plane.
Disruptive Pioneers
The buyer profile for this quadrant is a CTO or CISO with strong platform engineering capability who wants architectural advantage now and will accept a faster-moving product surface to get it. The bet is to move mesh functions somewhere new: the node kernel, a managed network fabric, or a zero-trust platform that governs AI agents as well as services. These buyers tolerate gaps in standards conformance and maturity, and they have the expertise to work around them.
Axes
The X-axis: Operational Focus versus Strategic Focus describes the value a product aims to deliver, with Operational placements on the left of the chart and Strategic placements on the right. Buyers choose solutions toward the Operational side to secure and stabilize the services an organization already runs, minimizing operational risk and the effort of running the mesh day to day. Buyers choose solutions toward the Strategic side to change how the organization builds and connects distributed systems, with value that compounds through architectural commitments over several years.
The Y-axis: Stability-Centered versus Evolution-Centered describes change posture, with Stability placements in the upper half of the chart and Evolution placements in the lower half. Stability-centered placements favor long support windows, conservative deprecation, and controlled upgrade cycles. For them, change is the risk to minimize. Evolution-centered placements treat change as the benefit buyers are paying for: frequent releases that extend what the mesh can do, or an architecture that redefines what a mesh is.
Ring System (Leader Versus Challenger)
The Radar's concentric rings communicate overall capability depth and maturity independent of quadrant. This Radar uses two rings: Leader, the inner ring, and Challenger, the outer ring. Six products hold the inner ring, and nine hold the outer ring.
Leader denotes products that combine broad capability across the evaluation lenses, production-grade security and lifecycle engineering, and enough documentation and ecosystem integration to be referenceable at scale.
Challenger denotes solid capability with important areas of growth: useful in many deployments, but likely to need more integration effort, operational validation, or workarounds for specific enterprise requirements. In this field, Challenger placements often reflect a narrower data plane model, support for fewer runtimes, or security features that have not yet reached general availability.
Use ring position as a procurement heuristic. Inner-ring placements reduce integration and validation effort when the buyer's requirements align with the product's strengths. Outer-ring placements call for more architectural validation, clearer commitments during procurement, and often a pilot. Ring position does not change which quadrant a product targets.
Archetype Variants
Different buyer archetypes shift priorities across the Tech Buying Triad's three roles. Compliance-bound buyers in defense, government, and financial services tilt toward GRCS. For them, strict mTLS by default, FIPS-validated cryptography, enterprise CA chaining, audit records tied to workload identity, and patch integrity dominate. The CISO's accountabilities lead the procurement.
Platform-led buyers building multicluster and multicloud estates shift toward Green Money and CTO leadership, weighting multicluster management, non-Kubernetes reach, Gateway API conformance, and extensibility. Cost-pressured buyers elevate Brown Money and the CIO, focusing first on data plane overhead, the sidecarless option, and upgrade mechanics.
Succeeding with any selection requires explicit Triad alignment up front. Agree which bucket has the final say when priorities conflict. Then define the acceptance tests before the mesh carries production traffic: a control plane outage under load, a canary upgrade of the data plane, and a strict-mTLS cutover for a namespace with unmeshed callers.
Decision Matrix — Which Quadrant Fits Your Organization?
Use the per-quadrant profile below to self-identify the quadrant whose buyer most resembles your organization. Read the row that sounds like your team. That quadrant's vendor capsules deserve your closest reading.
Quadrant | You are likely this buyer if… | Start your shortlist with |
Foundation Builders | You are a CIO or platform engineering lead running a large, established Kubernetes and VM estate. You need mTLS, identity, and traffic management that stay predictable across long support windows, with conservative upgrades and governance over many clusters and runtimes. | F5 Aspen Mesh, HashiCorp (IBM), Kong, Tetrate |
Agile Optimizers | You lead a platform engineering or SRE team that adopts releases on a regular cadence. You want each release to cut proxy overhead, simplify day-2 operations, or improve multicluster behavior on the mesh you already run, without a rearchitecture. | Buoyant, Cilium (CNCF), Google Cloud, Kuma (CNCF), Linkerd (CNCF), Red Hat |
Enduring Innovators | You are a CTO or platform architect making a multiyear bet on the mesh as the foundation of zero-trust and multicloud architecture, and you want a supported, reversible path to ambient operation across clusters. | Istio (CNCF), Solo.io |
Disruptive Pioneers | You are a CTO or CISO with deep platform skills who wants mesh functions in a new place, such as the kernel, a managed fabric, or an accredited zero-trust platform that also governs AI agents, and you accept gaps in standards conformance to get there. | F5 Distributed Cloud Mesh, Greymatter.io, Isovalent |
4. Vendor Capsules by Quadrant
4. Vendor Capsules by Quadrant
Vendor Capsules by Quadrant
Enduring Innovators
These vendors suit a CTO or platform architect who is making a multiyear bet on the mesh as the base for zero trust or a multicloud application platform. Buyers trade fast change for depth: a predictable roadmap, steady investment, enterprise-grade security integrations, and a supported route to their target architecture.
Disruptive Pioneers
These vendors suit a CTO or CISO with a strong platform engineering team who wants an architectural advantage now and will accept a faster-moving product to get it. They move mesh functions somewhere new, such as the node kernel, a managed network fabric, or a zero-trust platform that also governs AI agents. Their buyers have the skills to work around gaps in maturity and standards.
Foundation Builders
These vendors treat the mesh as critical infrastructure for CIOs and platform leads running large, established Kubernetes and VM estates, where an outage or a disruptive upgrade is costly. Buyers judge them first on continuity: stable security and traffic management, long support windows, and careful, documented upgrade paths.
Agile Optimizers
These vendors suit platform engineering and SRE teams that run the mesh as a living system and are happy to take regular releases. Each release should make the mesh cheaper, simpler, or more resilient to run, without forcing a move to a new architecture.
5. Velocity
5. Velocity
Market-Level Velocity Story
A vendor's velocity is the pace at which it ships capability that moves the category, judged against the market's direction rather than raw feature count. Most of the field sits at Fast Following, with a minority Outpacing and a small tail at Slow Following.
The Fast Following majority ships steadily and on schedule. Its output includes quarterly or semiannual minor releases, long-term support lines, new identity and CA providers, native sidecars as the default, Gateway API updates, and ambient or post-quantum features that arrive soon after the upstream project ships them. Several are making substantial changes that affect their customers, through deprecated control plane modes, removed features, or mesh security paths in transition from one design to another. What they have not shipped is a generally available capability that reached the market first. For a category built on shared upstream code, that is a natural place for most commercial products to sit.
A vendor earns an Outpacing mark here by arriving first with a generally available capability or by originating a component that the upstream project later integrated. Five capabilities earned those marks. Three are conformance to the Gateway API inference extension, an agent gateway running as an ambient waypoint, and ambient multicluster held at general availability. The other two are hybrid post-quantum key exchange on by default for all meshed traffic, and post-quantum key exchange inside FIPS builds paired with in-proxy inspection of AI and MCP traffic. They come from upstream and commercial products alike, so speed does not depend on which upstream project a product comes from.
The Slow Following tail ships maintenance releases on an aging upstream base. These products build on the most widely adopted upstream project. One ships maintenance-only releases on a base several upstream minor releases old, with no new ambient, Gateway API, post-quantum, or MCP work while the market shipped all four. The other still carries ambient support and Gateway API routing at alpha on an upstream version whose community support has ended.
The mark describes pace, not reliability. It reflects the tradeoff of staying on an older upstream release, which Market Context describes. Expect the mark to stand until the vendor publishes a dated roadmap that changes it.
Read velocity as a sign of how a vendor approaches change, not as a quality ranking. In a market built on shared upstream projects, a Fast Following distribution is often exactly what a platform team wants: upstream capability, hardened and supported, a release or two later. Beyond the base-version questions Market Context raises, ask whether the vendor's release history shows steady, dated increments, and whether ambient operation, post-quantum cryptography, and AI traffic governance are moving toward general availability on a published schedule.
6. Ecosystem
6. Ecosystem
Technical Support Quality and Responsiveness
Support depends on the commercial offering built around the code. Distributions sell it as the product, in tiers that run from around-the-clock coverage on a long-lived release line up to hotpatches, long-term CVE patching, faster response, and published remediation deadlines for critical vulnerabilities. Managed delivery adds an uptime SLA.
The foundation-hosted projects instead patch each release for a fixed period that the community sets, which is a release policy rather than a support relationship. Once you choose the distribution, what remains is contractual: get response targets and remediation deadlines in writing for the exact release line you will run, not for the vendor's newest one.
Professional Services Depth
Vendors deliver implementation help mostly as product features rather than as services engagements. Migration tooling does most of this work. It assesses readiness and generates waypoint and policy configuration for an incremental, reversible move to ambient. It also replaces the CNI node by node with both data planes live and a way back, and it moves workloads from client agents to a lighter data plane without downtime.
Operator-driven upgrades commonly run the control plane first and the data plane second. A few products hand operations to the vendor through a managed control plane or a SaaS console. Tooling covers the mechanics of a migration, not its judgment calls, so ask each vendor who performs the work and price it separately from the subscription.
Partner and Channel Ecosystem Breadth
A mesh that comes inside a container platform subscription, with no separate purchase, sets the procurement path before buyers compare any feature. A mesh that buyers often purchase alongside its vendor's API gateway does much the same. Cloud marketplaces carry several products on node-based or cluster-pack terms, under subscription, pay-as-you-go, or annual contracts. Public-sector buyers can reach a specialist platform through government resellers and contract vehicles.
Integration partnerships cluster around certificate authorities, with external secret stores, cert-manager, and cloud private CAs recurring as issuers, and around progressive delivery tools such as Argo Rollouts and Flagger. Map these relationships to the platform, gateway, and PKI estate you already run, because they decide whether the mesh fits into your existing stack or arrives as a parallel one.
Workforce Skills Availability
Envoy configuration and filter-chain debugging carry from one product to the next, because most of the field builds its data plane on Envoy, whether as a sidecar, a per-node proxy, or a waypoint. The exceptions narrow or redirect that skill. A purpose-built Rust microproxy that accepts no custom filter code asks less of operators. A proprietary node model with a JavaScript engine for request customization requires different skills.
Gateway API and upstream project resources are portable skills, while console-defined objects and vendor-specific languages tie expertise to one vendor. SPIFFE identity, cert-manager, and OpenTelemetry recur widely. Hire for Envoy, Kubernetes networking, and PKI fundamentals, and weight products whose configuration model matches skills you can recruit.
Training and Certification Programs
Documentation, release notes, and community material for a foundation-hosted project apply directly to every distribution built on it, so most enablement comes from upstream. Vendors add operational aids inside the product: diagnostics that pair a detected fault with remediation guidance or a corrective command, analysis of proposed configuration before operators apply it, in-cluster documentation, and policy generated from observed traffic for review. Treat the built-in diagnostics as part of the training program. Confirm which curricula and credentials cover the upstream project and which cover the distribution, and budget hands-on time for the data plane model you choose.
Community Health
Most of the open-source projects beneath service mesh hold graduated CNCF status, with one still at the Sandbox stage. That gives the category a stronger shared open-source base than most infrastructure markets have. Project health still varies.
The largest project ships roughly quarterly minor releases and patches each for a defined window. Another publishes frequent edge releases, while its stable releases have come only from a commercial vendor since February 2024. A third concentrates development in one sponsoring company, and its latest major release removed several features.
When one sponsor funds most of the work, its commercial priorities set the roadmap. Before treating community backing as a support plan, check contributor diversity, the stable-release policy, and who patches the version you run.
7. Architect's Validation
7. Architect's Validation
No organization weights the decision criteria equally, and a few deployment-specific questions decide outcomes in service mesh. Before shortlisting, pressure-test four things in order.
First, the data plane: run your own workload mix under the sidecar, ambient, or node-level model you will operate, and measure proxy cost and upgrade disruption, not only latency. Second, default security posture: install fresh and record what the mesh enforces before any configuration. Third, failure behavior: take the control plane down and observe what keeps working, for how long, and what new workloads can do. Fourth, estate reach: mesh one workload outside Kubernetes and one workload in a second cluster, and confirm that identity and policy follow.
The table below indicates when to promote specific criteria to first-order requirements and when to let them recede.
Prioritize when… | Treat as secondary when… |
Sidecarless / Ambient / eBPF Architecture Support and Resource Efficiency: proxy cost at thousands of pods is a budget line, or dense clusters cannot carry a proxy per workload | Service counts are modest, and per-pod proxy cost is small next to the workloads themselves |
mTLS Enforcement Posture and Policy Rollout Safety: zero-trust mandates require strict mTLS everywhere, and enforcement must be staged without breaking unmeshed callers | The mesh serves a bounded, fully meshed environment where strict mode can be set once |
Enterprise PKI and CA Integration and FIPS Cryptography: workload certificates must chain to an existing enterprise CA, or regulated workloads require validated cryptography | The mesh CA is acceptable as a trust root, and no FIPS obligation applies |
Non-Kubernetes and Multi-Runtime Support: VMs, bare-metal hosts, or container services outside Kubernetes will carry production traffic for years | The estate is Kubernetes-only, and legacy hosts are scheduled for retirement |
Multi-Cluster and Hybrid Cloud Management and Control Plane Resilience: services span clusters, clouds, or data centers, and one cluster's failure must not stop the others | A single cluster or region hosts the workload, and cross-cluster failover is not required |
Gateway API / GAMMA Conformance and Extensibility: portability across distributions matters, or custom request-path logic must run in the proxy | One vendor's configuration model is an accepted long-term commitment, and no custom filters are planned |
AI and Agentic Traffic Governance: AI agents and model servers will call internal services and tools through the mesh | AI traffic is handled entirely by a separate gateway outside the mesh |
Adapting the Radar to Your Organization. Start from your three or four nonnegotiable criteria and re-read the vendor capsules against those alone. Let that reading reorder the field before you consider overall placement. The placements in this report reflect the market's overall direction, not your architecture. A product positioned modestly here may be the right fit for your weighting.
8. Horizon
8. Horizon
Capabilities Likely to Become Table Stakes (12–24 Months)
Several capabilities that separate products today are on track to become standard expectations. A sidecarless option is first. Several products already run ambient and sidecar data planes together at general availability, and a few more are sidecarless by design. Alpha or preview modes appear in other products and in the managed cloud service.
Gateway API routing for east-west traffic is next, with GAMMA routes stable in some products and alpha or absent in others. Buyers will increasingly treat a proprietary routing model as a portability cost. Hybrid post-quantum key exchange for mesh mTLS is moving the same way: it is already on by default in some products, configurable in others, and in release candidates elsewhere. SPIFFE workload identity that spans containers, VMs, and bare metal through SPIRE is common enough that its absence will need explaining.
Control plane outage behavior is converging as well. Proxies that keep serving on last-known-good configuration until workload certificates expire are now the common baseline. Buyers will therefore press vendors for stated certificate grace periods and redundancy guidance rather than accept the behavior on trust. Native Kubernetes sidecars as the default injection mode, and diagnostics that check the live mesh before an operator applies a change, round out the list.
Capabilities Likely to Emerge as Differentiators
Early features in today's products already point to the next round of differentiators, beginning with governance of AI agent and model traffic inside the mesh. Today most of it ships as companion products. The first vendors to bind agent identity, tool authorization, and token budgets to mesh workload identity in a production release will set the reference. Ambient multicluster is second: a single distribution offers it at general availability, while the upstream project carries it at beta and another distribution at Technology Preview.
Policy safety is third. Simulating proposed policy against live cluster data, generating policy from observed flows, and dry-running authorization changes before enforcement each ship in individual products today. Buyers will reward the vendor that turns these into one supported workflow. Finally, regulated cryptography will separate the field as buyers expect FIPS-validated builds and post-quantum key exchange to work together, a combination few products document.
Expected Market Consolidation or Fragmentation
Consolidation here follows lineage rather than size. The project families that Market Context describes hold most of the field, and a few independent platforms and a managed service stand apart. Ownership has already shifted: some commercial mesh vendors now sit inside larger infrastructure companies, and one vendor's managed mesh service reached end of life in November 2025.
Within families, products are narrowing scope rather than merging. Recent releases have removed features, retired gateway types, deprecated control plane modes, and moved AI functions into separately sold products. None of this points to a specific acquisition, but the consequence for due diligence is clear. Buyers should establish which capabilities live in the SKU they are purchasing, which depend on a companion product, how the release line maps to its upstream project, and what the exit path is if the sponsor's priorities change.
9. Value Chain
9. Value Chain
A service mesh sits between the application platform and the security and operations estate. The mesh's job is to make every call between workloads authenticated, encrypted, routed, and observable without changing application code.
Upstream producers and consumers | The service mesh | Downstream estate |
Microservices on Kubernetes; VMs, bare-metal hosts, and container services outside Kubernetes; CI/CD, GitOps, and progressive delivery pipelines; AI agents, MCP servers, and model-serving endpoints | Control plane issuing identity, policy, and routing configuration; data plane of sidecars, node-level proxies, waypoints, or kernel programs; workload identity and certificate issuance; mTLS and L7 authorization; traffic management and resilience; telemetry, flow records, and audit events | Enterprise CAs and secret stores; identity providers; observability, tracing, and SIEM platforms; API, ingress, and AI gateways at the mesh edge; CNI and cluster networking; managed Kubernetes and VM platforms |
The differentiation in this field lives at two seams. The lower seam is the network. Whether the mesh runs as sidecars above the CNI, as ambient node proxies alongside it, or inside the CNI itself decides resource cost, upgrade mechanics, and which encryption and identity features are generally available.
The upper seam is the edge of the mesh, where east-west policy meets API gateways, ingress, and AI gateways. Products that express both seams through Gateway API resources and SPIFFE identity give buyers portable configuration. Products that use console-defined objects or vendor-specific languages trade that portability for an integrated model.
The mesh tends to enter the architecture at predictable moments. These include a zero-trust mandate that requires workload identity and mTLS between services, a move from one cluster to many, a platform refresh, or a cost review of sidecar overhead at scale. Exit is easier than in most infrastructure categories when the product stays close to its upstream project, because the same resources and identities carry over to another distribution. It is harder where routing, policy, and extensions live in proprietary models. Choose the mesh based on how well it handles both seams, and confirm before purchase that policy, identity, and certificates can move to another product without rewriting every service's configuration.
10. Appendix A — Decision Criteria
10. Appendix A — Decision Criteria
This evaluation groups its decision criteria by the accountability lens they serve.
Brown Money
BM1. Resource Efficiency and Data Plane Overhead: How far operators can cut data plane cost, by sending less traffic through L7 proxies or by setting per-workload proxy resource limits.
BM2. Sidecarless / Ambient / eBPF Architecture Support: Whether a generally available data plane serves workloads without a proxy in each pod, or with a lighter per-workload variant.
BM3. Sidecar-to-Ambient Migration and Coexistence: Whether workloads move between data plane models one namespace or workload at a time, with coexistence and a way back.
BM4. Control Plane Scalability: Whether one control plane's capacity is stated in proxies, services, or endpoints, from testing or a named deployment.
BM5. Control Plane Resilience and Blast Radius: What keeps working when the control plane is lost, and how far a single failure reaches.
BM6. Operational Lifecycle and Upgrades: How traffic keeps flowing during upgrades, through version skew support, canary revisions, staged operators, and pre-upgrade checks.
BM7. Platform and Distribution Support: Which Kubernetes releases, managed services, and on-premises distributions the product supports.
BM8. Day-2 Tooling and Stack Integration: Whether a CLI or console diagnoses proxies, certificates, and live traffic, and exports metrics and traces.
Green Money
GM1. Multi-Cluster and Hybrid Cloud Management: Whether cross-cluster services are discovered automatically and secured by mesh identity under the same policy as local calls.
GM2. Non-Kubernetes and Multi-Runtime Support: Whether VMs, bare-metal hosts, and container services outside Kubernetes get identity, policy, and telemetry from the same control plane.
GM3. Multiprotocol Support: Which protocols the mesh understands beyond HTTP, including gRPC, WebSocket, messaging, and database traffic.
GM4. Progressive Delivery and Advanced Traffic Control: Whether weighted and header routing combine with mirroring or fault injection, and canaries promote or roll back on mesh metrics.
GM5. Resilience and Circuit Protection Depth: How the mesh contains a failing service, through circuit-breaker limits, outlier ejection, and active health checks.
GM6. Extensibility and Programmability: Whether customers add request-path behavior through a supported filter API or their own Wasm filters, without forking the proxy.
GM7. Gateway API / GAMMA Conformance: Whether ingress and east-west routing use generally available Gateway API resources, including HTTPRoute attached to a Service.
GM8. Load Balancing and Locality Routing: Whether traffic stays in the caller's zone while healthy, fails over outward automatically, and weights endpoints by latency.
GRCS (Governance, Risk, Compliance & Security)
GRCS1. mTLS Enforcement Posture: Whether mTLS covers all meshed connections by default or is enforced mesh-wide by one policy that blocks plaintext.
GRCS2. Workload Identity and Federation: Whether workloads receive rotated SPIFFE identities, attested through SPIRE where needed, that federate across trust domains.
GRCS3. Enterprise PKI and CA Integration: Whether certificates come live from an enterprise CA such as Vault, cert-manager, SPIRE, or a cloud private CA.
GRCS4. L7 Authorization Granularity: Whether requests are authorized by method, path, headers, and JWT claims against the caller's verified identity, per route.
GRCS5. FIPS and Regulated-Environment Cryptography: Whether regulated buyers have a supported FIPS path, through builds on validated modules or mesh-wide cipher restrictions.
GRCS6. Audit Logging and Compliance Reporting: Whether traffic records carry authorization outcomes and configuration changes leave an actor-attributed audit trail.
GRCS7. Supply Chain and Patch Integrity: Whether each supported version line receives CVE-tracked patches, with SBOMs, provenance, and stated remediation timelines.
GRCS8. Policy Rollout Safety: Whether authorization runs in audit or shadow mode, and strict mTLS phases in per namespace, before enforcement.
Emerging Technology
EM1. AI and Agentic Traffic Governance: How far the mesh governs AI agent and model traffic, from identity-scoped route authorization to tool allow-lists and token budgets.
EM2. eBPF Data Plane Maturity: Whether eBPF programs in the node kernel capture or act on mesh traffic, and how much of the data plane they carry.
EM3. AI-Assisted Policy and Operations: Whether the product analyzes live mesh state and proposed changes, and reports failing checks against the affected resources.
EM4. WebAssembly Extensibility Maturity: Whether a supported Wasm extension resource loads Proxy-Wasm modules into the proxies with versioning and verification.
EM5. Ambient Multicluster Maturity: Whether multicluster operation works with a generally available sidecarless data plane, not only per-workload proxies.
EM6. Post-Quantum Cryptography: Whether mesh mTLS negotiates a hybrid ML-KEM key exchange such as X25519MLKEM768 in a released version.
EM7. Runtime Security and Observability Convergence: Whether telemetry and flow records name source and destination workloads by verified identity.
11. Methodology
11. Methodology
*Vendors marked with an asterisk did not participate in our research process for the Radar report, and their capsules and scoring were compiled via desk research.
For more information about our research process for Radar reports, please visit our Methodology.
12. About Ivan McPhee
12. About Ivan McPhee
Formerly an enterprise architect and management consultant focused on accelerating time-to-value by implementing emerging technologies and cost optimization strategies, Ivan has over 20 years’ experience working with some of the world’s leading Fortune 500 high-tech companies crafting strategy, positioning, messaging, and premium content. His client list includes 3D Systems, Accenture, Aruba, AWS, Bespin Global, Capgemini, CSC, Citrix, DXC Technology, Fujitsu, HP, HPE, Infosys, Innso, Intel, Intelligent Waves, Kalray, Microsoft, Oracle, Palette Software, Red Hat, Region Authority Corp, SafetyCulture, SAP, SentinelOne, SUSE, TE Connectivity, and VMware.
An avid researcher with a wide breadth of international expertise and experience, Ivan works closely with technology startups and enterprises across the world to help transform and position great ideas to drive engagement and increase revenue.
13. About GigaOm
13. About GigaOm
GigaOm provides technical, operational, and business advice for IT’s strategic digital enterprise and business initiatives. Enterprise business leaders, CIOs, and technology organizations partner with GigaOm for practical, actionable, strategic, and visionary advice for modernizing and transforming their business. GigaOm’s advice empowers enterprises to successfully compete in an increasingly complicated business atmosphere that requires a solid understanding of constantly changing customer demands.
GigaOm works directly with enterprises both inside and outside of the IT organization to apply proven research and methodologies designed to avoid pitfalls and roadblocks while balancing risk and innovation. Research methodologies include but are not limited to adoption and benchmarking surveys, use cases, interviews, ROI/TCO, market landscapes, strategic trends, and technical benchmarks. Our analysts possess 20+ years of experience advising a spectrum of clients from early adopters to mainstream enterprises.
GigaOm’s perspective is that of the unbiased enterprise practitioner. Through this perspective, GigaOm connects with engaged and loyal subscribers on a deep and meaningful level.
14. Copyright
14. Copyright
© Knowingly, Inc. 2026 "GigaOm Radar for Service Mesh" is a trademark of Knowingly, Inc. For permission to reproduce this report, please contact sales@gigaom.com.
