Commercial vessel connectivity
Give onboard business and monitoring systems a predictable public IP identity across supported internet connections.
WireGress provides managed connectivity with a dedicated static public IPv4 for selected outbound traffic. Connect shore-side applications and vendor platforms through one consistent identity, with custom inbound access available by arrangement.
Commercial vessels may use satellite offshore, cellular near shore, and port internet while alongside. Those connections can assign different public IP addresses or place onboard systems behind carrier-grade NAT.
Changing addresses complicate access to shore-side platforms that require IP allowlisting. CGNAT can also prevent direct inbound access to approved onboard maintenance services.
WireGress gives selected vessel traffic a dedicated public IPv4 through a managed WireGuard gateway. When the onboard tunnel reconnects over another supported uplink, traffic routed through the same WireGress service continues to use that address. The vessel's router manages uplink selection and failover; applications may need to reconnect after a change.
Use existing fleet or vendor-managed connectivity where it already meets your needs. WireGress is a fit when you need a consistent public IP independent of the vessel's current internet provider.
Connect onboard reporting, inventory, and business applications to approved shore-side services that require an allowlisted public IP.
Route the required business traffic through WireGress according to your onboard network policy.
Send equipment health summaries, measurements, and alerts to shore-side monitoring platforms using a consistent source address.
Applications should buffer data and retry transmissions where intermittent connectivity is expected.
Arrange custom inbound access to an approved maintenance gateway or diagnostic host so authorized vendors can investigate supported equipment remotely.
Keep vendor access limited to the required systems and maintenance scope.
Support configured remote administration of business servers and network services. Where required, discuss access to an approved recorder or video management system.
Separate business, crew, and operational networks. Video performance depends on available uplink capacity.
Outbound — included
Selected traffic uses a dedicated public IPv4 that partners and service providers can allowlist, independent of the vessel's current uplink address.
Custom inbound — by arrangement
Inbound access is scoped and configured per deployment for approved sources, ports, and destination services. It is separate from the included outbound public IP.
A dedicated WireGress gateway is provisioned with a static public IPv4 for the agreed deployment.
Your team or marine IT partner configures a WireGuard peer on a compatible onboard router or host. WireGress supplies the service configuration, not client software.
Send the required applications or networks through WireGress. Your onboard router manages which internet uplink carries the tunnel.
Register the WireGress public IPv4 with approved shore-side applications, vendors, and partner services.
Contact us to discuss a custom path to approved onboard maintenance or business services.
Important: A known public IP is one part of an access policy. Continue using application authentication, encryption, network segmentation, and controlled vendor access.
A practical fit for vessel reporting, periodic data transfers, and administrative access that can tolerate a WireGress gateway interruption.
Review the Core Plan →Better suited to deployments that need the same outbound public IP to remain available through a WireGress gateway or facility failure.
HA operates on the WireGress side. It does not manage the vessel's satellite-to-cellular switching or guarantee uninterrupted application sessions.
Review the HA Plan →Important: WireGress does not replace navigation, distress, or other required maritime communications systems.
Yes, when the onboard router or host can establish the required outbound WireGuard tunnel. The stable public identity comes from WireGress rather than the vessel's local carrier.
Yes, for selected traffic routed through the same WireGress service after the tunnel reconnects over the active uplink. Your onboard equipment manages the change. Existing sessions may be interrupted.
That depends on your fleet's access and isolation requirements. Separate addresses can help partners distinguish vessels, while a shared outbound identity may suit some integrations. Confirm the address and routing design before deployment.
Inbound access is a custom configuration arranged per deployment. It can provide a path to approved onboard services, with agreed source restrictions, ports, and destinations.
No. Your provider supplies internet access, and your team or marine IT partner supplies a compatible router, host, or standard WireGuard implementation. WireGress provides the managed gateway service and connection configuration.
No. HA protects against WireGress-side gateway and facility failures. Vessel-side outages require a separate resilience design, including suitable uplinks, power, and onboard failover equipment.
Operated by APYL Inc.
ARIN Member since 2010 • AS53628 • 30+ years infrastructure experience • 24/7 operations • Operating production infrastructure for businesses worldwide
Tell us about your vessels, their uplinks, and the applications or maintenance services that need connectivity. We'll confirm whether WireGress fits your fleet and what public IP and inbound configuration would be required.