F5 NGINX Service Mesh
Service mesh tools
Cloud security software
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
Take the quiz to check if F5 NGINX Service Mesh and its alternatives fit your requirements.
Pay-as-you-go
Free TrialFree version
Small
Medium
Large
- Banking and insurance
- Energy and utilities
- Public sector and nonprofit organizations
What is F5 NGINX Service Mesh
F5 NGINX Service Mesh is a Kubernetes-focused service mesh that uses sidecar proxies to manage east-west traffic between microservices. It targets platform and DevOps teams that need traffic management, mTLS-based service-to-service security, and policy controls for applications running in Kubernetes clusters. The product is built around NGINX Plus as the data-plane proxy and integrates with common Kubernetes workflows (e.g., CRDs and CLI-based operations).
Kubernetes-native installation model
The product is designed for Kubernetes environments and uses Kubernetes resources and tooling for deployment and configuration. This aligns with teams that standardize on cluster-level operations and GitOps-style workflows. It can reduce the need for separate control-plane infrastructure outside the cluster compared with approaches that assume multi-environment control planes.
NGINX-based data plane
It uses NGINX Plus as the sidecar proxy, which can be attractive for organizations already operating NGINX in production. Teams can apply familiar operational practices around NGINX configuration, observability, and performance tuning. This can simplify standardization when NGINX is already part of the application delivery stack.
Built-in mTLS and policies
The mesh supports mutual TLS for service-to-service encryption and identity, helping enforce zero-trust patterns inside the cluster. It also provides traffic policies such as routing rules and access controls at the service level. These capabilities address common service-mesh use cases without requiring application code changes.
Product lifecycle uncertainty
F5 announced end-of-life for NGINX Service Mesh, which affects long-term supportability and roadmap confidence. Organizations adopting it may need a migration plan to another mesh for future upgrades and security patches. This increases operational risk compared with meshes that have an active, ongoing release cadence.
Kubernetes-centric scope
The product primarily targets Kubernetes and is less suited to heterogeneous environments that include VMs or multiple non-Kubernetes runtimes. Teams running mixed estates may need additional tooling for consistent service identity, policy, and traffic management across environments. This can limit its fit for broader enterprise service networking programs.
Smaller ecosystem and integrations
Relative to more widely adopted meshes, it typically has fewer third-party extensions, community examples, and off-the-shelf integrations for advanced traffic management and telemetry pipelines. This can translate into more custom work for integrations with specific observability, policy, or multi-cluster patterns. It may also reduce the availability of experienced operators in the hiring market.
Plan & Pricing
Usage-based (NGINXaaS - pay-as-you-go) Pricing model: Pay-as-you-go (NGINXaaS for Azure / Google Cloud) Components (documented official rates):
- Azure (Standard V3): Fixed deployment = $0.25/hour; NCU = $0.008 per NCU per hour; Data processing = $0.005/GB. (NCUs sold in bundles of 10; minimum 10 NCUs). See Azure NGINXaaS docs for estimator and examples.
- Google Cloud (Enterprise plan tiers): Tier 1: Fixed price = $0.10/hour; NCU = $0.008/hour; Data processing = $0.0096/GB. (Higher regional tiers with higher fixed/NCU/data rates exist.) Example costs:
- Azure example (from official doc): 20 NCU deployment for 2 hours + 1 GB data => fixed 2*$0.25 + 40*$0.008 + 1*$0.005 = $0.87 (example shown in docs).
- Google example (from official doc): 20 NCU processing 100 GB for 1 hour => $0.10 + (20*$0.008) + (100*$0.0096) = $1.22 (example shown in docs). Minimum paid cost (NGINXaaS Standard V3 on Azure): Minimum NCU bundle is 10 NCUs, so minimum hourly cost (excluding data) = $0.25 + (10 * $0.008) = $0.33/hour (official docs show the components and bundling rules).
Tiered / Subscription (NGINX One / NGINX Service Mesh packaging)
| Plan | Price | Key features & notes |
|---|---|---|
| NGINX One (Enterprise subscription) | Custom / Contact F5 | Annual enterprise subscription that bundles NGINX components (NGINX Plus, Ingress Controller, Gateway Fabric, Service Mesh, optional WAF); pricing not published — contact F5. |
| NGINX Service Mesh (Open-source download) | Free | Officially downloadable/open-source (always-free OSS distribution) — available for download from NGINX/F5. |
Notes:
- NGINX Service Mesh is available as an open-source (always-free) product to download.
- Enterprise/managed/cloud paid offerings that include Service Mesh capabilities are sold either as NGINX One annual subscriptions (contact sales for pricing) or as NGINXaaS (cloud pay-as-you-go) with the documented NCU-based pricing model.
Seller details
F5, Inc.
Seattle, Washington, USA
1996
Public
https://www.f5.com/
https://x.com/f5
https://www.linkedin.com/company/f5/
