mosn/mosn

The Cloud-Native Network Proxy Platform

View on GitHub ↗Jump to charts ↓Open shareable report →

mosn/mosn has 4.5k+ stars and 750+ forks on GitHub, is written in Go, and was last pushed on Jul 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 51 minutes ago
Added to GitGenius on September 15th, 2026
Created on July 12th, 2018
Open Issues & Pull Requests: 298 (+0)
GitHub issues: Enabled
Number of forks: 788
Total Stargazers: 4,508 (+0)
Total Subscribers: 168 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.6 hours
Mean response time: 69.9 days
90th percentile: 2.0 days
Tracked items: 16

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 473 days
Stale 30+ days: 13
Stale 90+ days: 12

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

MOSN is a cloud-native network proxy platform written in Go that functions as a modular, extensible data plane for service mesh and standalone load balancing scenarios.

MOSN addresses the need for a high-performance, protocol-agnostic proxy that integrates deeply with cloud-native infrastructure. It works by providing a modular architecture that supports multiple protocols through an XProtocol framework, enabling automatic protocol identification and extension. The proxy handles both Layer 4 and Layer 7 traffic, offering capabilities like virtual host-based routing, header and URL-based routing, traffic mirroring, and weighted load balancing. It includes connection pooling, circuit breakers, active health checking, and multiple load balancing policies. For observability, it integrates with Jaeger and Skywalking for tracing, exposes Prometheus-style metrics, and provides configurable access logging. The tool supports hot upgrades and graceful shutdown for production environments.

Teams should adopt MOSN if they need a proxy that works as a sidecar in Istio-based service meshes or as a standalone L4/L7 load balancer, API gateway, or cloud-native ingress controller. It suits organizations already invested in Go ecosystems and those requiring extensibility through go-plugin, process-based, or WebAssembly extensions. The project's support for multiple certificate matching, TLS inspection, and extensible certificate verification makes it suitable for security-conscious deployments. Its ability to handle transparent traffic hijacking and support for gRPC distinguish it in scenarios requiring advanced traffic interception and modern protocol support.

Development activity shows sustained engineering effort with regular updates to the changelog and active contribution guidelines. The project maintains comprehensive documentation and a dedicated website, indicating ongoing investment in usability and community engagement. Partners participate in co-development, suggesting collaborative evolution of the platform's capabilities.