A shoreside AV/IT contractor supporting a yacht between seasons works through three separate cloud platforms, not one: Crestron XiO Cloud for the control and AV devices, UniFi Site Manager for the network and cameras, and Peplink InControl 2 (with InTouch) for the WAN. Each tool sees only its own layer of the vessel's technology stack, each access grant should be scoped and logged separately, and none of them can replace a technician standing in front of a failed piece of hardware. Understanding what each platform actually does — and does not — do is the first governance question a captain or ETO should settle before handing out credentials.
What can a shoreside tech actually do through XiO Cloud?
Crestron's XiO Cloud is a device-management platform, not a programming tool. It runs on Microsoft Azure IoT Hub and lets an enterprise or dealer view live device status, push firmware updates, change settings across multiple units at once, and review cloud audit logs — all from a browser, with no extra hardware required on the vessel (XiO Cloud Overview). For a captain, that means a shoreside technician can confirm whether a touch panel or processor is online, push a firmware update to the lighting keypads before the owner arrives, and pull an audit log showing who changed what and when — all without a yard visit.
XiO Cloud can also integrate into an owner's or management company's existing single sign-on identity provider, which is a reasonable way to centralize who can log in at all rather than managing a separate password per vendor (XiO Cloud Provisioning and Management Service Manual). That audit-log feature is worth asking your contractor to demonstrate specifically: a usable remote-access governance model depends on being able to answer "who touched the lighting processor last month" without guessing.
What does UniFi Site Manager let a technician see on the network?
UniFi's cloud gateways separate network zones — LAN, WAN, guest, and IoT — through a zone-based firewall, and guest Wi-Fi runs isolated from other traffic by default to meet segmentation expectations (UniFi Cloud Gateways). For a vessel, that default guest isolation is the starting point for keeping a visiting technician's remote session away from bridge systems, crew communications, and whatever else shares the onboard network — but it still has to be confirmed zone by zone during commissioning, not assumed.
The UniFi Site Manager portal (unifi.ui.com) gives multi-factor-authenticated remote management, automatic cloud backups, and traffic-flow logs useful for after-the-fact review of what a remote session actually did on the network. Ask your contractor to walk through exactly which zone their remote account lands in, and whether that account can see camera feeds, guest traffic, or only the network infrastructure itself.
How does Peplink InControl grant WAN access without opening the firewall?
Peplink InControl 2 is the cloud dashboard for the Peplink router handling Starlink Maritime and cellular failover; it lets an administrator push firmware and configuration changes, monitor WAN quality, and reach the web admin interface of any device behind the router without a site visit (Cloud Based Network Management Solution InControl 2). InControl's role-based accounts — dashboard viewer, group viewer, group administrator, organization viewer, organization administrator — are the mechanism for scoping exactly what a given login can see or change, and that role should be set deliberately rather than defaulted to administrator for every contractor who ever touches the system.
Peplink's InTouch extension goes further, giving one login remote access to any IP device behind the router — cameras, servers, remote desktops — without requiring a public IP, inbound firewall ports, or a VPN (Peplink InTouch Remote Device Access with One Login). That is a meaningfully different security posture than opening a traditional VPN tunnel into the vessel's network, since no inbound path is exposed to the internet at all. A captain evaluating a support contract should ask whether the contractor uses InTouch specifically for this reason, rather than requesting a conventional port-forwarded VPN.
What can't these tools fix remotely?
None of the three platforms can replace a crimp, a cable run, a failed antenna, or a processor that needs a hands-on power cycle at the rack. XiO Cloud can tell a technician that a device has dropped offline; it cannot reseat a connector. InControl can push a configuration change to a router; it cannot replace damaged coax or a corroded connector on an exposed antenna mount. These cloud tools shorten the list of problems that need a technician physically aboard — they do not eliminate that list, and a realistic support agreement should say so plainly rather than implying every fault is remotely fixable.
What belongs in the remote-access section of a crew handover package?
An incoming captain or ETO should receive, in writing: which platforms are in use (XiO Cloud, UniFi Site Manager, InControl/InTouch), which accounts exist on each and at what role/permission level, how long each outside contractor's access is valid for, and where the audit logs live for each platform. Because XiO Cloud keeps cloud audit logs and InControl logs network events, a handover package that simply names "remote support" without naming the accounts and their scope leaves the next captain unable to answer a basic security question: who can currently reach this vessel's systems from shore. This governance layer sits alongside, not instead of, the broader crew/guest network segmentation that a vessel's SMS should already document.
Cave Group designs around Crestron for vessel control and lighting and specifies UniFi and Peplink for networking and WAN failover on new builds and refits, with every system enrolled in the relevant cloud dashboard at commissioning so remote support is scoped from day one rather than bolted on later. For owners and captains weighing a refit or a new-build technology package, the marine integration page outlines how control, networking, and connectivity are specified together, and the support page covers the ongoing Cave Watch service model layered on top of these platforms.
Frequently asked questions
Can a shoreside technician reprogram the Crestron system without being aboard?
XiO Cloud supports remote firmware updates, settings changes, and device monitoring, but it is a provisioning and management platform, not a programming environment — deeper logic changes to the control system typically still require a programmer to load updated code, which may or may not be pushable remotely depending on how the system was commissioned. Confirm with your integrator exactly which category of change their remote account can make.
Does guest Wi-Fi being isolated mean a remote technician's session is automatically separated from guest devices too?
Not automatically — UniFi's zone-based firewall isolates guest Wi-Fi from other networks by default, but a remote-support account still needs to be placed in a specific zone during setup (UniFi Cloud Gateways). Ask your contractor to confirm which zone their access lands in rather than assuming it.
Does Peplink InTouch require opening a VPN or firewall port into the vessel's network?
No. InTouch is built on an active InControl 2 license and SpeedFusion Connect usage and explicitly does not require a public IP, inbound firewall access, or VPN infrastructure to reach devices behind the router (Peplink InTouch Remote Device Access with One Login).
What should be revoked first when a support contract ends?
At minimum, the contractor's logins on XiO Cloud, UniFi Site Manager, and Peplink InControl should all be removed or downgraded, and the single sign-on provider (if XiO Cloud is tied into one) should also be checked for lingering access. A clean handover package should list every account by platform so nothing is missed.
Can these cloud platforms fix a hardware failure on board?
No. They can identify that a device is offline or misbehaving and push software-level fixes like firmware updates and configuration changes, but physical problems — damaged cabling, a failed antenna, a processor that needs a hands-on reset — still require a technician on the vessel.