bond

Several Internet connections as one. Unmodified WireGuard on a transport that splits its packets across every uplink in reach — venue WiFi, a wired line, people's phones — and puts them back in order at an aggregator you host. When an uplink dies, the connection holds.

Where the splitting happens

Inside is real, unmodified wireguard-go, with Bond plugged in underneath as its transport: it splits WireGuard's datagrams across every path and puts them back in order at the far end. Because that happens below the tunnel, everything that runs over IP keeps working — TCP, UDP, ICMP, SRT, RTMP, WebRTC, games, even other VPNs.

Three roles

• Aggregator — on any VPS with a public address. Where your traffic rejoins the Internet.
• Hub — the machine you want better Internet on. It opens a path through every uplink it can reach and sends each packet down whichever one will get it there soonest.
• Relay — lends its uplink to hubs nearby. A phone in Share mode forwards a hub's already-encrypted packets over cellular.

Where UDP is blocked outright, a WebSocket path carries the traffic instead.

Standing it up

A Homebrew tap, plus release archives for Linux on x86, ARM64 and 32-bit ARM — a Raspberry Pi makes a fine hub. One deploy script cross-compiles the aggregator, installs a systemd service and prints a join code and a QR; there is Terraform for AWS, Google Cloud and Azure, and a Docker image that runs unprivileged.

What it is for

The case where the connection has to hold: a live stream out of a venue with bad connectivity, carried by its flaky WiFi, a wired line and three people's phones at once. Self-hosted end to end — the aggregator is yours.