Flomesh Service Mesh vs Network Service Mesh
Flomesh Service Mesh
flomesh.ioNetwork Service Mesh
networkservicemesh.ioSide by side
| Figure | Flomesh Service Mesh | Network Service Mesh |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| macOS | Yes | — |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Service Mesh Platforms | 8.0 (#5) | 8.4 (#3) |
| Purpose | FSM provides traffic management and service governance for microservices running on Kubernetes. | Network Service Mesh is a hybrid and multi-cloud IP service mesh for connecting workloads across clusters and clouds. |
Plans
In their own words
Flomesh Service Mesh
Flomesh Service Mesh (FSM) provides traffic management and service governance for microservices running on Kubernetes. It uses the Flomesh Pipy proxy, which is automatically added as a sidecar to onboarded applications. FSM supports traffic shifting, ingress and egress, and Kubernetes Gateway API capabilities, along with HTTP, TCP, gRPC and MQTT traffic. For service security, it enables mutual TLS and fine-grained access policies. Certificate management can use Tresor, cert-manager or HashiCorp Vault. Documentation marks Prometheus and Grafana integrations as stable and Jaeger distributed tracing as beta; integration guides also cover Dapr and discovery registries such as Consul, Eureka and Nacos. FSM supports x86 and ARM architectures and multi-cluster Kubernetes connectivity through the MCS API, though multicluster is marked alpha. It is open source, free and self-hosted, with Kubernetes and OpenShift listed. Installation requires Kubernetes 1.19 or later; version 1.1 is listed for Kubernetes 1.19 through 1.24.
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.