About this post. Written by Rocket Routers about technology we are actively developing. We use AI assistance (Claude, by Anthropic) to help draft and research content — we review everything before it goes live. Rocket Mesh is in active development. Nothing described here is available to buy yet — we will announce when it is.
Start simple. What is bandwidth bonding?
Your phone has one SIM. It connects to one cell tower. Your internet speed is whatever that one connection gives you — usually somewhere between 20 Mbps and 150 Mbps depending on signal, congestion, and which carrier you're on.
Bandwidth bonding means combining multiple separate internet connections so that your devices can use all of them simultaneously — as if they were one fast pipe. Not failover (where you switch to a backup if the primary fails), but genuine parallel use of every connection at the same time.
If you have three connections each doing 50 Mbps and you bond them, a single device on your network can pull 150 Mbps. A video stream uses connection one, a file download uses connection two, a video call uses connection three. All at once. Automatically.
The key difference from failover: Failover means "use connection A, switch to B if A fails." Bonding means "use A, B, and C simultaneously — all the time." Both are valuable. Rocket Mesh does both.
How Rocket Mesh works
Each Rocket Router in a mesh has its own cellular uplink — one or two SIM cards depending on the model. In a standalone setup, each router uses only its own SIMs. In a Rocket Mesh configuration, every router's connections are pooled together into one logical network using WireGuard encrypted tunnels between the units.
The technology underneath is built on OpenMPTCProuter — an open-source bandwidth bonding system that runs on top of OpenWrt, which is the same firmware base our routers already run. It was designed exactly for this: combining multiple WAN connections across multiple devices into a single bonded pipe.
WireGuard handles the encrypted mesh between routers. OpenMPTCProuter handles the traffic distribution across connections. Our custom Rocket firmware configures both automatically on first boot — no manual setup required.
What it looks like in practice
Say you deploy four Rocket Routers in a building — a venue, a large office, a building site, or a hotel. Each router has at least one SIM card. Here is what happens as you add each one:
A customer anywhere in that building gets the full bonded bandwidth. They do not need to know which router their traffic is going through. They just get fast internet.
Why different carriers matter
Putting all your SIMs on the same carrier is the obvious thing to do. It is also a mistake.
If Three UK has a mast outage in your area, every Three SIM goes down simultaneously. If you have SIMs spread across Three, EE, Vodafone, and O2 — on four completely separate towers — one carrier going down means you lose 25% of your bandwidth, not 100%. The other three connections carry on and mwan3 instantly redistributes the traffic. Your customers notice nothing.
This is what telcos mean by carrier-grade redundancy. They achieve it with expensive dedicated hardware and managed contracts. Rocket Mesh achieves the same outcome with open-source firmware on commodity hardware.
Real world resilience: A building site 30 miles from the nearest fibre exchange. No landline is possible. Rocket Mesh with four routers across four carriers means a mast outage, a carrier maintenance window, or a SIM going bad affects only one quarter of available bandwidth — and recovers automatically when the issue clears. No engineer visit. No phone call to a helpdesk.
Who is this for?
| Use case | Routers | SIMs | Why it matters |
|---|---|---|---|
| Building site | 2–4 | 2–6 | No fibre available. Temporary power. Needs to work reliably for months. Scale bandwidth as crew size grows. |
| Event venue | 3–6 | 4–8 | Hundreds of simultaneous users. Single cell connection congests instantly. Bonded mesh shares load across carriers and towers. |
| Rural business / farm | 2–3 | 2–4 | Fibre not available or years away. Needs reliable connectivity for EPOS, cameras, staff. Cannot afford downtime. |
| Pop-up retail / hospitality | 1–2 | 2–3 | Different location every week. No time to arrange broadband. Plug in, SIMs work, done. |
| Enterprise backup WAN | 2 | 2–4 | Primary fibre fails. Rocket Mesh takes over automatically. IT team does not get called at 2am. |
| Cool homes | 2 | 2 | Because why not have bonded cellular internet at home. You earned it. |
What is in the firmware
Rocket Mesh runs on our custom OpenWrt-based firmware — the same base as the Rocket Plus and Rocket Pro, extended with the Firmware D mesh layer. On first boot, each router detects how many modems are present and configures itself automatically. When mesh mode is active, WireGuard tunnels form between units and OpenMPTCProuter begins distributing traffic.
No manual WireGuard key exchange is needed. No config files to edit. The mesh discovers the other units, exchanges keys automatically, and begins bonding within minutes of being powered on and connected.
The LuCI web interface — the router's built-in control panel — shows the status of every connection in the mesh, the bandwidth contribution of each SIM, and allows you to set carrier priority if needed. If one connection is on a limited data SIM, you can weight it lower so it only takes traffic when others are saturated.
What commercial equivalents cost
Multi-WAN cellular bonding is not a new idea. Peplink, Cradlepoint, and Digi International all sell hardware that does similar things. Their managed enterprise solutions typically cost between £2,000 and £5,000 per month on service contracts, plus hardware costs in the thousands. The monthly cost alone pays for several Rocket Mesh deployments.
We are not claiming our firmware is as polished as Peplink's enterprise dashboard. It is not — yet. What we are saying is that the underlying technology is identical, it runs on open-source software that anyone can inspect and verify, and the hardware cost is a fraction of the commercial equivalents.
Transparency: Rocket Mesh is in active development. We are building and testing it on our own hardware. We will not release it until it works reliably. If you have a specific deployment in mind, get in touch — we may be able to work with you on an early deployment.
The technology underneath — for the technical reader
WireGuard — the mesh backbone. Every router generates a public/private keypair. Public keys are exchanged between units automatically during mesh setup. All inter-router traffic is encrypted with ChaCha20-Poly1305 — the same cipher used in TLS 1.3 and Signal. WireGuard's codebase is around 4,000 lines — small enough for a single person to fully audit. It is built into the Linux kernel from version 5.6 onwards.
OpenMPTCProuter — the bonding layer. Uses MPTCP (Multipath TCP) — a kernel-level extension to TCP that allows a single connection to use multiple network paths simultaneously. When a device downloads a file, MPTCP splits the TCP stream across all available WAN connections. The receiving end reassembles the stream in order. The application sees one connection; the network uses all of them.
mwan3 — the failover and load-balancing policy engine. Already present in our Firmware A and B builds. In Rocket Mesh it operates at a higher level — managing traffic distribution not just across SIMs on one router, but across the entire mesh. Failure of a connection triggers automatic rebalancing within seconds.
BATMAN-adv — Better Approach To Mobile Adhoc Networking. Handles mesh routing — deciding which path traffic should take through the network of routers. Originally developed for city-scale mesh deployments, it handles topology changes (a router going offline, a new one being added) without any manual reconfiguration.
When will it be available?
We are targeting a Rocket Mesh beta for late 2026. We will not put a more specific date on it because firmware this complex needs to be right before it ships. When it is ready, it will be announced here on the blog first.
If you are planning a deployment that could use this — a building site, a venue, a large rural property — get in touch now. We would rather hear about your use case while we are building it than after we have shipped something that does not quite fit.