Multi-orbit access
Combine VSAT, Starlink and OneWeb with L-band backup.
One Net solutions / Connectivity
Connect the vessel to the wider operation.
Satellite, cellular and managed routing bring vessels, shore teams and remote sites into one network design.
Talk to a network specialistVessel connectivitySeveral paths.
One network plan.
Compare the access options One network plan.
Designed for maritime operations
The route changes. The network needs a plan.
Deep-sea routes, coastal coverage and critical applications place different demands on connectivity. One Net designs the role of each access link, then manages traffic priorities around the people and systems using it.
What One Net brings
Access, routing and control.
Cellular reach
Use LTE and 5G alongside satellite where coverage permits.
Intelligent routing
SD-WAN selects available paths and supports automatic failover.
Traffic control
Prioritise business applications and manage crew bandwidth.
Choose the role of each connection
Different access.
One network design.
Each access technology suits a different part of the operation. One Net designs the combination around your routes and applications, then SD-WAN manages the available paths between them.
Explore an option to see where it fits.StarlinkLEO satellite
An access option for vessel applications and crew connectivity where the maritime service is available.
What to review
Route coverage, terminal requirements, traffic allowances and its role alongside existing links.
OneWebLEO satellite
An additional satellite access option for maritime and remote enterprise operations.
What to review
Operating area, available maritime plans and the service commitments offered.
FleetXpressKa-band VSAT + L-band
A combination of VSAT access and an L-band backup path.
What to review
Bandwidth profile, failover configuration and the responsibilities set out in the service agreement.
Ku-VSATKu-band VSAT
Satellite capacity selected around established trade routes and application requirements.
What to review
Route coverage, committed or best-effort capacity, and installed hardware.
FleetBroadbandL-band
Essential voice and data communications within the vessel’s wider connectivity plan.
What to review
The terminal and service required for the intended communications, including any applicable safety obligations.
IridiumL-band
Voice and data connectivity for remote routes and backup arrangements.
What to review
Route coverage, required voice and data services, and compatibility with the vessel’s equipment.
MRS LTE / 5GCellular
Coastal and port operations where mobile networks can carry vessel traffic.
What to review
Time spent near shore, operator coverage, roaming terms and traffic-routing policy.
Coverage, capacity, hardware and service terms are confirmed against your routes and requirements in the proposal.
Inside the service
Control how the connection is used.
Access capacity is only part of the service. The network also needs a policy for which traffic uses each link, how crew and business systems are separated, and what happens when an available path changes.
SD-WAN routing and failover
SD-WAN selects between configured links using the routing policies set for the vessel. Traffic shaping and quality-of-service rules give the team control over competing applications and the use of available bandwidth.
- Define the preferred paths for business applications, crew access and voice.
- Set the conditions for switching links and returning to the preferred path.
- Test failover against the applications in use; application continuity depends on the connection and configuration.
Network separation and crew welfare
Zwana Nexus provides a gateway and aggregation point for access links. VLAN segmentation separates traffic groups, while crew internet policies control allocations without giving crew devices unrestricted access to business or operational systems.
- Agree network boundaries for business, crew, IoT and operational equipment.
- Use individual accounts, quotas and bandwidth controls for crew internet.
- Give business traffic and voice an appropriate priority within the available capacity.
Cellular service and cost control
Managed LTE / 5G combines hardware, SIMs and roaming arrangements for coastal and port operations. Multi-IMSI options and hybrid routing can complement satellite access when the required mobile network is available.
- Review the countries, ports and coastal routes in the operating plan.
- Confirm roaming eligibility, allowances and spending controls.
- Choose when the vessel may use cellular capacity and when traffic returns to satellite.
Monitoring, support and rollout
Shore monitoring and troubleshooting support the connection after installation. A useful service plan identifies the terminals, links and routing policies in scope, with direct escalation arrangements when a fault needs further investigation.
- Start with a site survey, installed equipment and the vessel’s schedule.
- Document capacity checks, activation and handover responsibilities.
- Confirm service hours, incident handling and commitments in the applicable agreement.
A practical starting point
Specify the network around the work it carries.
Coverage matters. So do the applications, traffic policies and fallback arrangements behind the connection.
Explore the requirement that fits your team.Add Starlink or another access linkSatellite + SD-WAN
Review route coverage, existing terminals, capacity and the role of each connection.
Discuss this requirementSeparate business and crew trafficTraffic policies + managed access
Define application priorities, crew bandwidth and the network boundaries between them.
Discuss this requirementBring several vessels into one approachFleet network design
Agree the access technologies and operating policies around the fleet’s different routes.
Discuss this requirementConnected services
Connect Connectivity to the wider operation.
Connectivity supplies the access. Zwana brings routing, compute and network controls together at the edge. Managed IT and cybersecurity keep the connected environment maintained and protected.
From specification to handover
Test the work. Not just the connection.
A terminal can be online while a call, remote session or onboard application still struggles. A useful acceptance plan follows the traffic from the user’s device to its destination.
Map the whole path
Start with trade routes, terminals and airtime plans. Include onboard cabling, switches, Wi-Fi, network segments and the applications using them. Identify equipment to retain and any installation constraints.
Bring: route list, network diagram and current contracts.
Prove the traffic policy
Choose representative business, support and crew tasks. Review throughput, delay and packet loss where relevant, then test priorities and the change to a backup link in an agreed maintenance window.
Agree: test tasks, acceptable results and fallback behaviour.
Make the handover usable
Record the installed configuration, access roles, usage limits and escalation route. Confirm how changes to routes, applications or data allowances will be reviewed after installation.
Keep: configuration record, acceptance results and support contacts.
Does another satellite link solve poor onboard Wi-Fi?
The access link and the local network are different parts of the connection. Wi-Fi coverage, cabling, device capacity or local congestion can remain a bottleneck after an airtime upgrade. Include the affected locations and devices in the network review.
What is the difference between failover and bonding?
Failover moves traffic to another available path when the selected link fails. Bonding combines links for a particular connection. SD-WAN policy and failover should not be read as a promise of bonded bandwidth or uninterrupted sessions; confirm the required behaviour in the design.
How should we compare airtime proposals?
Compare the route and territory coverage, permitted maritime use, data allowance, priority policy, overage charges and contract term. Separate terminal and installation costs from recurring airtime, routing and support. Ask what happens when an allowance is exhausted or a service is unavailable.
Can we keep our existing terminals and provider?
Begin with an inventory of the equipment and contracts already in place. Compatibility, access permissions and responsibilities between providers need checking before a retained link becomes part of the managed design.
Talk to an expert
Let’s work through your connectivity requirements.
Share the environment, what is already in place and what needs to change. One Net will help define the technical scope and the working relationship.