Intranet tunneling and node management platform
Built-in Web console · Single-port access · Single-file deployment
English | 简体中文
NetsGo is an out-of-the-box intranet tunneling and node management platform. It combines the Web console, REST API, client access, and low-level network tunnels into a single-file binary, making deployment simpler, access more unified, and operations easier. You can use it to remotely access services inside private networks, or to centrally manage remote nodes distributed across different locations.
Web console overview
For more documentation and usage guides, visit the official website: https://netsgo.zs.uy.
curl -fsSL https://netsgo.zs.uy/install.sh | shcurl -fsSL https://netsgo.zs.uy/upgrade.sh | sh -s -- -yAfter installation, follow the interactive prompts to initialize a Server or Client. Once the Client is online, you can create and manage tunnels in the Web console.
If you want to start the server quickly, connect private-network machines, and then create tunnels, NetsGo focuses on exactly that:
- One binary is enough: run
./netsgo serverto start the server, and./netsgo clientto connect a remote node. - One port is enough: the Web console, control channel, and data channel share the same entry point, so firewalls and reverse proxies only need one shared access path. TCP/UDP tunnels use additional ports only when needed.
- A console is included by default: after a client connects, manage nodes, inspect status, and configure tunnels directly in the Web console.
This table is a capability checklist, not a ranking. Cells intentionally use short labels:
Built-in: included in the product itselfPlatform: provided by a hosted platformPlugin: commonly implemented through a plugin or panelConfig: mainly handled through config files or commandsExternal: typically requires third-party monitoring, logging, or operations systems
| Item | NetsGo | frp | ngrok | cloudflared | rathole |
|---|---|---|---|---|---|
| Product focus | Self-hosted management platform | Self-hosted tunneling tool | Hosted platform | Cloudflare tunnel | Self-hosted lightweight tunnel |
| Self-hosted server | ✅ | ✅ | ❌ | Platform | ✅ |
| Web UI | Built-in | Built-in/plugin | Platform | Platform | External |
| API / automation | Built-in REST | Supported/plugin | Platform | Platform | Config |
| Client management | Built-in | Config/plugin | Platform | Platform | Config |
| Tunnel CRUD | Web/API | Config/plugin | Platform | Platform | Config |
| Shared Web/API/client entry | ✅ | Multiple entries | Platform | Platform | Config |
| HTTP tunnel | ✅ | ✅ | ✅ | ✅ | TCP-backed |
| TCP tunnel | ✅ | ✅ | ✅ | ✅ | ✅ |
| UDP tunnel | ✅ | ✅ | Plan/scenario-dependent | Scenario-dependent | ✅ |
| Login / key | Admin + Key | Token/OIDC | Account/Token | Account/policy | Token |
| Online status | Built-in | Built-in/plugin | Platform | Platform | Logs/external |
| Traffic statistics | Built-in | Built-in/plugin | Platform | Platform | External |
| Reconnect after disconnect | ✅ | ✅ | ✅ | ✅ | ✅ |
| Rate limiting | Built-in | Built-in | Platform/plan | Platform policy | External |
- NetsGo: for scenarios where you want to manage clients, tunnels, status, and traffic in one self-hosted Web console.
- frp / rathole: for configuration-driven, lightweight deployments where you compose your own operations tooling.
- ngrok / cloudflared: for hosted-platform scenarios where you want to use platform accounts and edge network capabilities directly.
First published on the linux.do forum.