Google Cloud Service Mesh vs Network Service Mesh
Google Cloud Service Mesh
cloud.google.comNetwork Service Mesh
networkservicemesh.ioSide by side
| Figure | Google Cloud Service Mesh | Network Service Mesh |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Web | Yes | — |
| Linux | — | Yes |
| API | — | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 1 |
| Spec score · Service Mesh Platforms | 6.8 (#13) | 8.4 (#3) |
Plans
Google Cloud Service Mesh
- Cloud Service Mesh standalone usageFree
In their own words
Google Cloud Service Mesh
Google Cloud Service Mesh is a web-accessed service mesh with a hybrid deployment model. Its listed capabilities include mutual TLS, traffic policies, and multi-cluster support, with proxy architecture listed as both. Supported platforms include GKE on Google Cloud and Google Distributed Cloud software-only for VMware. The standalone usage plan is listed at free and charges each client $0.0006945 per hour. That plan includes a managed control plane, telemetry dashboards, and a managed certificate authority with no per-certificate charge. The broader pricing information identifies the service as paid, says there is no free plan, and gives a pricing note of From $0.50/mo. These are separate listing details from the standalone usage plan. Teams assessing the service can focus on its stated traffic-policy controls, mutual TLS, multi-cluster coverage, hybrid deployment, and managed components. Web is the listed platform for access.
Network Service Mesh
Network Service Mesh connects workloads across clusters and clouds through a hybrid, multi-cloud IP service mesh. Each workload can connect independently to zero or more Network Services, regardless of where it runs. The project says it works with an existing CNI without requiring changes to Kubernetes or workloads. Services can provide connectivity, security, and observability at Layer 3 and above, carrying IP or Ethernet payloads.
Clients may be Kubernetes pods, virtual machines, or physical servers. They authenticate independently, currently using SPIFFE IDs, and need authorization to attach. Clients request and close virtual wires over gRPC and can monitor connection status through a streaming call. Endpoint selection offers composition, selective composition, topology awareness, and scale from zero. A service may also provide domain-scoped DNS for connected pods. The architecture describes integration with Istio, Linkerd, Consul, and Kuma. Network Service Mesh is a CNCF sandbox project and is free and open source. Its run guide lists Docker, Go, a Kubernetes cluster, and kubectl as prerequisites; most examples require at least two worker nodes.