What is NanoPing
NanoPing keeps real-time traffic flowing over unreliable connections. It bonds every network connection a device has, whether Ethernet, cellular, Wi-Fi or Starlink, and protects the traffic with forward error correction, retransmissions and a strict latency budget. If it shows up as a network interface, NanoPing can use it.
NanoPing is a single self-contained binary with no runtime dependencies, so it runs the same on bare metal, in virtual machines and in containers. It works with standard IP, UDP and TCP traffic, so your applications do not need to change.
Key concepts
| Concept | What it is |
|---|---|
| Node | A device running NanoPing. Any node's dashboard shows and manages every node on its hub, so a node can also run without one of its own. |
| Hub | Lets nodes find and reach each other. All nodes on the same hub show up in each other's dashboards and can be managed from any of them. See Hubs. |
| Pipeline | The instructions a node runs: a diagram of components that read, protect, route and deliver traffic. See Creating a pipeline. |
| Network | A virtual network across nodes on a hub. NanoPing generates and deploys the pipelines for every node in it. See Networks. |
| KPI | A live dashboard tile built from a pipeline's metrics. See KPIs. |
Features
- Bonding of any number of connections, with bandwidth-aware load distribution
- Adaptive forward erasure correction and retransmissions within a latency budget
- A jitter buffer inside the transport
- Encryption and authentication components, with AES-256-GCM with SHA-384 for high-security deployments and ChaCha20-Poly1305 for fast encryption on any hardware
- Network emulation, such as simulated loss and delay, for testing before you deploy
- Detailed metrics: latency, jitter, packet loss and bandwidth
- Networks that set up tunnels between nodes for you
- Live metrics and KPIs
- An HTTP REST and gRPC API
Ready to try it? Continue with the Quick start or the complete walkthrough.
System requirements
Supported systems
| System | Processor | Minimum version |
|---|---|---|
| Linux | x86-64 or ARM64 | Kernel 3.6.0 |
| macOS | Apple Silicon (ARM64) | macOS 14 |
Hardware
NanoPing needs at least 2 CPU cores, 4 GB of RAM and 2 GB of free disk space. A Raspberry Pi 5 is enough: see Performance for what it can carry. Updates need room on top: each keeps the version it replaces as a backup, about 100 MB plus a copy of the app data, until you delete it, and leaves 1000 MB free on the disk. See Free space.
It works with any network interface the system has, such as Ethernet, Wi-Fi, a cellular modem or Starlink.
Browsers
The dashboard supports:
| Browser | Minimum version |
|---|---|
| Chrome | 111 |
| Edge | 111 |
| Firefox | 128 |
| Safari | 128 |
| Opera | 100 |