The Handoff Is the Problem

The weak point in an Adriatic yacht network usually shows up just after the easy part. You leave Cavtat with full bars, flat water, and a Starlink dish that looks healthy. An hour later, southbound into the Bay of Kotor, the owner is trying to join a call from the upper deck and the crew phones are behaving differently from they did that morning. Nothing looks broken. That is the problem.

In Croatia and Montenegro, bad connectivity is rarely one dramatic failure. It is usually a stack of small ones: a roaming rule changes at the border, a marina cell sector fills up, a phone grabs the wrong network, an old SIM falls back badly, or the yacht's own Wi-Fi dies first on the aft deck where people actually sit. The right question is not whether the yacht has Starlink. The right question is which traffic gets which path, and what keeps working when the path changes.

Croatia's June 2026 Digital Decade update put basic 5G coverage at 97.8 percent, above the EU average [1]. Montenegro is pushing capacity from the other direction: Crnogorski Telekom said in March 2026 that its next 5G phase adds 3.6 GHz capacity in urban and suburban zones while using 700 MHz to extend coverage farther out [2]. Those are good numbers. They do not turn a yacht into a house. A moving metal structure still needs a better plan than a shoreside condo.

The border changes policy before it changes signal

The Croatian side and the Montenegrin side do not behave the same way for crew phones. The European Commission's current roaming FAQ is explicit: Roam Like at Home covers the EU and EEA, while countries outside the EU/EEA are not included by default. Montenegro's inclusion is still under negotiation, and there is no set deadline for completion [3]. In practice, that means a southbound Adriatic passage is still a roaming-policy event even when the signal bars look fine.

The same FAQ matters for another reason. The Commission notes that non-terrestrial satellite networks on boats are outside the usual Roam Like at Home price protections and are usually expensive [3]. If crew handsets are allowed to attach to the wrong service at the wrong moment, the billing problem comes from configuration, not geography.

Croatia has also closed the door on lazy fallback planning. A1 Hrvatska says its 3G network stopped operating nationwide on July 6, 2026, and older SIMs that do not support 4G or 5G lose features such as VoLTE [4]. Any yacht still carrying a legacy failover handset, an old crew tablet, or a forgotten cellular router from a few seasons ago should assume Croatia will expose it.

Starlink is fast, but it is still a plan, not magic

Starlink fixes a very specific problem: distance from terrestrial infrastructure. It does not fix roaming policy, weak onboard Wi-Fi, or careless data budgeting. The current Starlink Roam page for Croatia says in-motion use is supported in select areas, boating is supported in territorial and inland waterways, and Roam plans advertise up to 300+ Mbps across 160+ countries and territories [5]. That is a strong cruising tool. It is not a reason to stop engineering.

For a yacht that actually works a full season, the more useful page is Starlink Maritime. Starlink's current business offering sells Global Priority in 50GB, 500GB, 1TB, and 2TB tiers, and after the priority allotment is used the service continues at up to 1 Mbps down and 0.5 Mbps up on the water. The Performance Kit is also clearly the right hardware class for this use: AC or DC power, permanent-install language, 10-year saltwater survivability, and wind tolerance up to 270+ kph [6]. That is enough context to make one thing clear: the Performance Kit exists for a reason, and quota planning still matters.

A recent SuperYachtNews piece made the same point from the bridge: do not treat Starlink as the only link on board [8]. That is not nostalgia for older satellite systems. It is just disciplined operations.

How Cave Group Builds the Stack

Start with three paths, not one

On an Adriatic yacht, Cave Group treats WAN connectivity in layers. Starlink Maritime is the fast offshore path. A coastal 5G stack, usually orchestrated through a Peplink multi-WAN router such as a MAX BR2 Pro 5G or SDX Pro with properly mounted external antennas, is the opportunistic high-value path when the shoreline is helping. The third path is a survival lane: enough for management access, messaging, customs paperwork, and critical notifications when the first two paths are compromised.

That third lane does not need to be glamorous. On a support vessel, a chase boat, or as a tertiary dockside path, UniFi 5G Backup is interesting because Ubiquiti designed it as a PoE-fed add-on that can be placed where signal is best, run either SIM or eSIM, and follow explicit failover rules. The current release also prices it at $99, which makes it easy to justify as insurance instead of a science project [7]. On a larger yacht, we still want Peplink doing the serious WAN orchestration. The point is architecture, not brand tribalism: every path needs a job.

Then the traffic gets classified. Bridge and vessel operations first. Remote support next. Crew communications after that. Guest streaming and cloud photo sync last. If a yacht burns through a Starlink priority allotment on software updates before dinner, that is not a bandwidth problem. It is a policy problem.

Keep Crestron local

On yachts, Cave Group keeps control and lighting in the same Crestron ecosystem. A Crestron CP4-R or DIN-AP4-R should keep lighting scenes, AV control, and core automation local even if every outside path goes down. Crestron DM NVX should keep video distribution on the LAN. If the yacht carries a Kaleidescape library, that traffic should stay local too.

That separation matters more than most owners realize. When a network is built correctly, a roaming change between Croatia and Montenegro does not affect a salon touchscreen, a guest-cabin TV, or a nighttime lighting scene. Internet-dependent services can degrade. The yacht itself should not.

This is one of the easiest ways to tell whether a marine system was designed by people who actually think about passage conditions. If control, lighting, and AV are quietly dependent on a WAN path, the fault will show up at exactly the wrong moment.

Design Wi-Fi for deck use, not showroom use

Most onboard complaints are not about the WAN. They are about the last twenty feet. The aft deck, flybridge seating, beach club, and the cabin just aft of the mast are where a network earns its keep. That means AP placement above people, not behind joinery. It means clean PoE switching, thoughtful channel planning, and separate SSIDs and VLANs for guest, crew, management, and vessel systems.

On metal boats, 6 GHz is useful where the path is short and clean. It is not the first band to trust through structure, wet bodies, and stainless hardware. That is why a speed test in the saloon tells you almost nothing about how the sun deck will behave at anchor. A good yacht Wi-Fi design is boring in the best way: the guest does not think about it, because the access point was put where the body load, glass, and metal could not ruin the link.

What to Lock Before the Season

Carrier policy before departure

The roaming rules should be documented before the yacht leaves the dock, not discovered over lunch. For an Adriatic program that crosses between Croatia and Montenegro, that means:

Confirm which crew SIMs and data pools are valid in Montenegro, and what happens after the cap is hit [3].
Disable unintended attachment to non-terrestrial mobile networks on phones that do not need maritime satellite roaming [3].
Replace any older SIM or handset that still depends on 3G-era behavior before Croatian cruising begins [4].

One avoidable pattern shows up every season: the owner's devices are planned, the bridge is planned, and the crew phones are left to chance. Then the yacht crosses a border, the lowest-priority devices start making the worst network choices, and support calls begin from the deck.

Traffic policy and data budgeting

This is where most good hardware gets wasted. Starlink Maritime is fast enough to hide bad behavior until it is not. The fix is simple and unglamorous:

Reserve Starlink priority data for work traffic, urgent guest use, and remote support when coastal 5G is weak [6].
Shunt photo backups, OS updates, and bulk crew entertainment to shore-side 5G or scheduled maintenance windows.
Test failover with real traffic classes, not a single ping and a satisfied shrug.

The Starlink plan details themselves tell you why this matters. Once the priority allotment is gone, the fallback speed on the maritime page is serviceable for essential communications, not luxury guest behavior [6]. A yacht that budgets data by policy feels calm. A yacht that budgets by hope always ends up paying twice.

Remote support and failover drills

The last part is procedural. It should still be written down.

Label every WAN path, SIM, eSIM, and antenna location.
Keep an out-of-band management path for the network core.
Record the local addressing and port map for the Crestron processor, DM NVX endpoints, switching, and remote power control.
Force a failover test before guests arrive, then repeat it after any major carrier or firmware change.

The newer UniFi failover tooling is useful here because the hardware can be placed where signal is cleanest and the backup policy can be made explicit instead of assumed [7]. But the bigger point is old-fashioned: no yacht should discover its failover logic during a passage.

The Standard That Matters

A good Adriatic yacht network is not the one that posts the biggest dockside speed test. It is the one that survives the handoff. Southbound, the owner's call holds. The crew can file what they need to file. The kids can stream on the aft deck. Crestron lighting still behaves like it did that morning. And when something fails, the system tells you which link failed and what traffic moved.

That is the standard Cave Group designs to in Croatia and Montenegro: Starlink Maritime for distance, 5G for opportunistic coastal performance, Peplink for WAN policy, UniFi for the onboard IP fabric, and Crestron kept local so the yacht never feels dependent on a cell sector or a satellite queue.

Croatia and Montenegro Yacht Connectivity: How Starlink and 5G Actually Behave in the Adriatic