A superyacht's tender needs its own connectivity package, not a hopeful connection back to the mothership's Wi-Fi. A compact marine router paired with a maritime-rated cellular antenna keeps the tender online as it moves away from the vessel, a GPS receiver built into that antenna reports the tender's position back to the bridge, and a separate network identity keeps tender devices from mixing with guest, crew, or control traffic on the main vessel. Getting this right during a refit or new build means treating the tender garage as its own commissioning checkpoint, not an afterthought bolted on after the main AV and network systems pass their tests.
What does a tender actually need for connectivity?
An open-helm tender away from the mothership needs its own WAN path, because once it's more than a short hop from the yacht, a point-to-point Wi-Fi bridge back to the main vessel network loses range and the tender has to fall back to cellular. Peplink's Maritime antenna series is built around this problem: the Maritime 10 is a single-cellular, 9.3 dBi antenna good for long-range reception on a smaller boat, while the Maritime 20G and 40G add two or four cellular channels respectively plus a built-in GPS receiver, and are IP68 rated to handle spray and sun on an open helm (Peplink Maritime Antenna Series). Peplink recommends pairing these antennas with its BR1 or MAX Transit routers for smaller vessels, reserving the larger MBX HD4 or EPX for applications that need more throughput — which for most tenders means the smaller, router-independent option is the right starting point rather than over-specifying hardware a 20-to-30-foot boat doesn't need (Peplink Maritime Antenna Series).
A question worth raising with whoever designs the tender's package: does the boat actually need four cellular channels, or does a single- or dual-channel antenna cover the coastal and in-port use case the tender will see most days?
How does the tender hand off from the mothership's Wi-Fi to cellular?
While the tender sits in the garage or idles near the yacht, it can ride the mothership's own network rather than burn cellular data for routine use. UniFi's device and building bridging technology links remote network points wirelessly using an automatic "deploy and point" setup, extending the main vessel's network out to a nearby endpoint without trenching cable or manual reconfiguration (All-New UniFi Bridging). As the tender moves beyond that bridge's effective range, the tender's own router needs to fail over to cellular on its own WAN link rather than simply dropping offline. Ask your integrator how that handoff is tested — specifically, whether the tender's router treats the mothership bridge and cellular as two WAN sources it can switch between, and what happens to an active call or file transfer during the switch.
This is a different problem from the multi-WAN failover logic on the yacht itself, which blends Starlink, cellular, and sometimes a secondary satellite link using Peplink's SpeedFusion technology. SpeedFusion's Hot Failover feature is built to move active sessions to a healthy link before the failing one fully drops, rather than waiting for a connection to go down first (SpeedFusion Bonding & Failover Technology). Whether that same hot-failover behavior is available or practical on a smaller tender-grade router is a design question to settle before relying on it — Cave Group's related guide to Peplink multi-WAN failover algorithms on yachts covers how Priority, Overflow, and Persistence modes behave on the main vessel network, which is useful background for comparing against what a tender router can realistically do.
How does the tender's position reach the bridge?
The Maritime 20G and 40G antennas include an active, high-performance GPS receiver specifically described as suited to location tracking (Peplink Maritime Antenna Series). That GPS feed is what gives the bridge a live position for a tender that's away from the yacht — whether running guests ashore or on a fishing run. Before specifying hardware, confirm with your integrator how that GPS data actually surfaces: does it feed a chartplotter, a Peplink InControl dashboard, or a custom screen at the helm, and who on the crew is expected to monitor it. The antenna supplies the location data; how that data is displayed and who acts on it is a separate decision that belongs in the commissioning plan.
How should tender devices stay separated from the main network?
A tender that bridges back to the yacht's network, even briefly in the garage, is still another device touching the vessel's infrastructure. The same segmentation discipline that applies to crew and guest Wi-Fi on the main vessel — keeping different user groups and traffic types on separate network segments — applies to a tender's connection as well. Cave Group's guide to crew Wi-Fi segmentation on a yacht network walks through how guest, crew, AV/control, and bridge traffic are kept apart when they share one Starlink/Peplink WAN; a tender's router and any devices aboard it (crew tablets, handheld radios with Wi-Fi, chartplotters) should be assigned to their own segment under the same logic rather than simply joining whichever SSID is closest.
What should get tested when the tender garage is commissioned?
During a refit or new build, the tender garage deserves its own punch list, separate from the main vessel's AV and network commissioning. At minimum that should confirm: the tender router connects to the mothership bridge while in the garage and at dock-side range; the router fails to cellular as the tender moves away, and recovers the bridge connection on return; the GPS feed reaches whatever display the bridge or captain actually uses; and the tender's network segment stays isolated from guest and bridge VLANs under normal operation. Cave Group designs and services Crestron control, networking, and connectivity for superyachts and custom vessels, including the WAN and segmentation planning a tender package depends on — see the marine services page for the full scope of what's covered on a refit or new build.
Frequently asked questions
Does a tender need its own cellular router, or can it just use the yacht's Wi-Fi?
A tender needs its own cellular router and antenna for when it's away from the mothership, because a Wi-Fi bridge back to the yacht only works at limited range; Peplink's maritime antennas are built with GPS and multi-channel cellular specifically for this kind of standalone small-vessel connectivity.
What's the difference between the Maritime 10, 20G, and 40G antennas?
The Maritime 10 is a single-cellular, long-range antenna without GPS; the Maritime 20G adds a second cellular channel plus a built-in GPS receiver; and the Maritime 40G adds four cellular channels with GPS for heavier-throughput applications, according to Peplink's product documentation.
How does a tender's GPS position get to the bridge?
The GPS receiver built into the Peplink Maritime 20G or 40G antenna reports position data that can feed a tracking display; exactly which screen or dashboard shows it on your vessel is a design decision to confirm with your integrator during commissioning.
Should tender devices share the same network as guests or crew on the yacht?
No — tender devices should sit on their own segmented network, following the same isolation principle used for crew, guest, and bridge traffic on the main vessel network, so a tender connection can't cross into other systems.
Is SpeedFusion hot failover relevant to a tender's router?
SpeedFusion's Hot Failover is designed to move active sessions to a healthy link before a failing one drops, but whether a tender-grade router supports the same behavior as the main vessel's Peplink setup is worth confirming with your integrator before you rely on it at sea.