Honest GMTS answer to the August Roam changes: one Starlink plan is not the whole connectivity strategy. We bond Starlink to cellular on Peplink — Hot Failover, SpeedFusion where the brief needs it — and we provision One NZ / roaming SIM estates we actually manage through GMTS Connect.
Outcome first: the vessel still has a path when the satellite plan hits a geography or timer wall. One sentence on the bond: multiple WANs, one router policy set, alerts in InControl when the active leg switches.
We cite Starlink TOS for limits and Peplink docs for failover behaviour. We do not name carriers we are not provisioning on your job.