Muti Metroo
Your private metro system for network traffic - connect distributed infrastructure with encrypted relay chains.
Muti Metroo creates encrypted tunnels through multiple relay points, letting you reach resources behind firewalls without VPN infrastructure. Deploy a single binary, connect your agents, and route traffic through any network topology.
Why Muti Metroo?
| Challenge | Solution |
|---|---|
| Firewalls block your traffic | HTTP/2 and WebSocket transports blend with normal HTTPS |
| Complex network paths | Multi-hop routing selects optimal paths through the mesh |
| Hard to deploy | Single binary, no root, no kernel modules |
| Per-app proxy config is tedious | TUN interface routes all traffic transparently |
| Transit nodes see your data | End-to-end encryption - transit cannot decrypt |
Key Features
| Feature | Description |
|---|---|
| Multi-Hop Routing | Traffic flows through chains, trees, or full mesh - routes propagate automatically |
| E2E Encryption | X25519 + ChaCha20-Poly1305 - transit nodes cannot read your traffic |
| Firewall Traversal | QUIC, HTTP/2, and WebSocket transports for restrictive networks |
| SOCKS5 Proxy | TCP and UDP support with optional authentication |
| TUN Interface | Transparent routing with Mutiauk - no per-app configuration |
| Web Management | Visual mesh monitoring and control with Metroo Manager |
| Dashboard API | JSON endpoints for topology, node details, and mesh connectivity testing |
Use Cases
Reach Internal Resources
Access servers behind NAT or firewalls through multi-hop relay chains. No VPN infrastructure needed.
Connect Multiple Sites
Link office locations through a mesh. Each site accesses resources at other sites seamlessly.
Resilient Connectivity
Deploy redundant paths with automatic failover. Agents reconnect with exponential backoff if connections drop.
How It Works
- Deploy agents on available hosts and configure peer connections
- Routes propagate through flood-based advertising once peers connect
- Connect via SOCKS5 on any ingress agent
- Traffic flows through the mesh to the exit with the matching route
- Exit agents open real connections to destinations
Next Steps
| Goal | Start Here |
|---|---|
| Try it now | Getting Started - 2-minute Docker demo |
| Understand the architecture | Core Concepts |
| Compare alternatives | Comparisons |
| Deploy to production | Deployment Guide |
| Troubleshoot issues | Troubleshooting |