Flomesh Service Mesh vs Linkerd
Flomesh Service Mesh
flomesh.ioLinkerd
linkerd.ioSide by side
| Figure | Flomesh Service Mesh | Linkerd |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| macOS | Yes | — |
| Linux | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Service Mesh Platforms | 8.0 (#5) | 7.6 (#10) |
| Observability | The documentation lists Prometheus and Grafana integrations as stable and distributed tracing with Jaeger as beta. | Linkerd records request volume, success rates, and latency distributions for HTTP, HTTP/2, and gRPC traffic, plus TCP-level metrics. |
| Proxy | FSM uses the Flomesh Pipy proxy and automatically injects it as a sidecar into onboarded applications. | Linkerd’s ultralight Linkerd2-proxy is written in Rust and designed specifically for the service mesh sidecar use case. |
| Security | FSM enables mutual TLS for service-to-service communication and fine-grained service access policies. | Linkerd automatically enables mutual TLS for communication between meshed applications and supports authorization policies between services. |
| Traffic management | FSM supports traffic shifting, ingress and egress, and Kubernetes Gateway API capabilities. | Linkerd supports load balancing, retries, timeouts, dynamic request routing, traffic splitting, and rate limiting. |
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.
Linkerd
Linkerd is a service mesh for Kubernetes that adds runtime debugging, observability, reliability and security without requiring changes to application code. It installs into a Kubernetes cluster and injects sidecar proxies into workload pods. The mesh handles HTTP, HTTP/2, gRPC and arbitrary TCP traffic, including TLS connections and WebSockets. It automatically enables mutual TLS between meshed applications and supports authorization policies between services. Metrics include request volume, success rates and latency distributions for HTTP, HTTP/2 and gRPC, plus TCP-level metrics. Traffic controls include load balancing, retries, timeouts, dynamic routing, traffic splitting and rate limiting. Linkerd can use Prometheus and Grafana and supports distributed tracing. Its Linkerd Viz Prometheus instance retains metrics for a short fixed interval, currently six hours, so it is intended to supplement an existing metrics store. Installation requires a modern Kubernetes cluster and a working kubectl command. The open-source project is licensed under Apache 2.0; Buoyant offers commercial support, training and architecture reviews. The listed plan is free.