Choose your access technologies
Combine Starlink, VSAT, OneWeb, LTE/5G and L-band in a multi-link WAN. WatchGuard SD-WAN supports dynamic path selection and configured failover, with routing and priorities set around the traffic.
Onboard infrastructure
Zwana Nexus
The network. The servers.
The software your vessel runs.
Route satellite and mobile links, host business applications and manage crew internet from one onboard platform.
What Zwana does
One platform for the systems on board.
Bring network access, computing and storage together. One Net configures the platform around your vessel’s applications and supports it from shore.
Run applications on board
Host business applications in virtual machines on board. The published range includes Dell PowerEdge XR5610 server configurations, with RAID, NAS, UPS and redundant-power options sized for the deployment.
Separate and protect the network
Use VLAN segmentation, quality-of-service policies and per-VLAN WAN selection to separate crew, business and operational traffic. WatchGuard UTM provides the gateway controls; EDR and SOC services are available through Sentrify.
Keep the environment managed
Connect the platform to infrastructure monitoring, patch policies, backup and maintenance through abela IT.
Zwana services
Services that run
on the platform.
Beyond the infrastructure itself, Zwana hosts the onboard services shore teams and crew depend on. Availability and configuration are agreed for each deployment.
Telemetry
Bring hardware, software and connectivity observations together to understand the vessel’s ICT environment.
- Connectivity availability tracked per link
- Hardware, network-device and firewall observations
- Traffic data connected to Data Analysis
Internet Café
Give crew individual internet accounts with visible allocations and flexible credit arrangements.
- E-wallet with pre-pay and post-pay credits
- One-off or recurring complimentary data allowances
- Per-user usage records and shore administration via abela.io
Data Analysis
Look beyond total vessel consumption to see where capacity is being used.
- Consumption by subnet
- Individual crew usage
- IP-level traffic visibility for policy and allocation reviews
VoIP
Run a virtual voice server within Zwana for onboard and ship-to-shore calling.
- Prepaid crew Chat-Card calling
- SIP integration for business calls
- Quality-of-service rules to prioritise voice traffic
Configure the foundation
The hardware, network
and software in one plan.
Zwana Nexus brings the onboard infrastructure and its services together. Begin with the workloads and equipment you already have, then define the computing, network controls, storage and management needed for the vessel.
Fusion / access aggregation
Bring Starlink, VSAT, OneWeb, LTE / 5G and L-band into a managed WAN. WatchGuard SD-WAN provides dynamic path selection and failover policies across configured links. Define the role of each carrier, the traffic priorities and the fallback arrangements together.
Server / edge computing
The published platform includes Dell PowerEdge XR5610 edge-server configurations and virtual-machine hosting for onboard business applications. RAID storage, NAS, backup, UPS and redundant power options are reviewed against capacity and recovery needs. The final hardware specification belongs in the vessel’s configuration.
Network / traffic policy
Quality-of-service rules, VLAN segmentation and bandwidth control separate traffic groups and manage how they use the available WAN. Business applications, crew access and voice can have different priorities and preferred paths. Provisioning includes site management, capacity checks and template-based activation.
Protection / network boundary
One Net lists WatchGuard UTM in every configuration: stateful firewall, intrusion prevention (IPS), application control and web filtering. Endpoint detection and specialist security monitoring are additional managed-service choices through Sentrify. Their scope is agreed alongside the network configuration.
Management / the shore team
abela IT provides the management relationship around the infrastructure: asset monitoring, patch policy, virtual-machine care and remote maintenance. abela.io supplies fleet visibility from shore, while abela Pulse supports captains and crew on board. Each service has its own users and responsibilities.
The Zwana software suite
Give every onboard service
a clear role.
Software runs alongside the physical platform to manage access, understand consumption and support the people using the connection. The selected model and service agreement determine the modules available on each vessel.
Internet Café / crew access
Individual crew accounts keep data allocations and usage records separate. An e-wallet supports pre-pay and post-pay credit arrangements, with one-off or recurring complimentary allowances. Shore teams manage the service through abela.io. Review quotas, account lifecycle, billing arrangements and the links available for crew traffic.
Data Analysis / traffic intelligence
Review consumption by subnet, user and IP address. These different views help the team understand which part of the network is using capacity and how that compares with the intended policy. Use the findings to discuss allocations, application priorities and cost control rather than treating all vessel traffic as one total.
Telemetry / equipment and links
Continuous hardware and network monitoring provides a record of connectivity availability and equipment health. Configured security sources can contribute endpoint status and firewall events. Network traffic information also feeds Data Analysis, connecting system observations with the way the connection is used.
VoIP / crew and business calling
A virtual voice server runs within the Zwana environment. Crew calling can use prepaid Chat-Card arrangements, while business calling connects ship and shore through SIP integration. Quality-of-service policies prioritise voice traffic. Review numbers, endpoints, credit arrangements and call behaviour on the available links.
Compare Zwana models
One platform.
Three starting points.
Every published model includes the four Zwana software modules and abela Pulse. Edge Lite adds Sentrify / SecOps; Edge Max also includes abela IT and abela.io.
Choose the service mix first, then size the hardware around your applications, storage and recovery needs. The model comparison describes service inclusions, rather than CPU, memory or storage specifications.
Discuss your configuration| Service | Edge Mini | Edge Lite | Edge Max |
|---|---|---|---|
| Crew Internet Café | Included | Included | Included |
| Telemetry | Included | Included | Included |
| Data Analysis | Included | Included | Included |
| VoIP · crew & business | Included | Included | Included |
| abela Pulse | Included | Included | Included |
| Sentrify / SecOps | — | Included | Included |
| abela IT | — | — | Included |
| abela.io | — | — | Included |
| abela Drive | Optional | Optional | Optional |
| Plan your vessel | Build my Zwana | Build my Zwana | Build my Zwana |
Confirm hardware, licences, service scope and portal access in the final configuration. abela.io appears in the live model table under Edge Max; shore administration described for other modules should be clarified for your selected package.
Connected services
The platform is the foundation.
The services make it work.
Configured around the vessel
Start with the systems
you need to run.
Choose the platform around the operation. One Net reviews the infrastructure and the managed services together. Resilience, spare capacity and recovery arrangements are design choices to specify for the selected model.
Size the workloads
List each application, its vendor, operating system, licences, computing and storage needs. Include expected growth and dependencies on other onboard systems. Select an Edge configuration against that workload list.
Plan the physical installation
Review rack space, power, cooling, cabling and terminal connections. Record the equipment to retain and the access or port window needed for installation.
Prepare the migration
Agree the order in which workloads move, the maintenance window and a rollback point. Confirm application-vendor involvement and the effect on users before changing the existing environment.
Demonstrate recovery
Define which data and virtual machines need protection, where backups are held and who restores them. Agree a restore test and recovery objectives; a backup schedule alone does not establish how quickly a service can return.
Hand over the operating record
Keep the configuration, network diagram, access roles, licences and acceptance results together. Identify who owns platform maintenance, application support and security changes.
Talk to an expert
Design the foundation for your fleet.
Review your current installation, the services you need and the configuration that brings them together.