One Net
Talk to an expert

One Net solutions / Software

Fleet software. For shore and on board.

Fleet visibility for shore teams. An onboard portal for captains and crew. Secure file storage for the vessel. Each application has a clear operational role.

Talk to an expert
The abela applicationsOne fleet.
Different perspectives.
Published abela.io fleet overview with illustrative data
For shore teamsabela.io
For captains and crewabela Pulse
For vessel documentsabela Drive
Maritime operating environment

Designed for maritime operations

One fleet. Different information needs.

Shore teams need the fleet picture. Captains need the vessel’s context. Document owners need controlled access to files. One Net’s software portfolio separates these jobs clearly and connects them to the wider ICT environment.

One NetOne Net

Our applications.

abela.io

Fleet-wide visibility for shore teams across connectivity and ICT.

abela Pulse

The onboard captain portal for vessel operations and crew welfare.

abela Drive

Secure vessel-facing file storage with authentication and an audit trail.

Communications

Ship-to-shore email for vessel and office teams.

SecOps

Security monitoring and incident response coordination through Sentrify.

Internet Café

Individual crew accounts, data allowances and usage tracking, managed from shore through abela.io.

The shore-side perspective

Your fleet,
in view.

abela.io brings site information and operational context together for the teams overseeing the fleet.

Explore abela.io
abela.io fleet overview with a site map and summaries

Inside the service

Maritime email, alongside the abela applications.

Ship-to-shore email has its own requirements: limited bandwidth, intermittent links and administration across several vessels. One Net’s published software portfolio includes Dualog Mail and GTMail alongside the abela applications and Zwana onboard services.

Dualog Mail

Dualog Mail provides maritime email with central administration from shore and support for commonly used email clients. One Net’s published offering includes unlimited user accounts per vessel; confirm licensing and the service configuration in your proposal.

  • Manage vessel email accounts through a central fleet approach.
  • Review satellite delivery and the email clients already in use.
  • Agree security controls, account administration and migration responsibilities.
GTMail

GTMail uses store-and-forward delivery and attachment optimisation to support email over satellite links. Shore administration includes audit and quarantine functions, with central management across domains.

  • Review compression and delivery behaviour for the vessel’s links.
  • Set domain, quarantine and per-vessel policies.
  • Plan integration with Zwana and the transition from the current email service.
Crew access, voice and usage analysis

The Zwana software suite adds Internet Café, VoIP, telemetry and Data Analysis. These serve different jobs from the abela applications: allocating crew access, carrying voice calls and understanding the use of the vessel’s network.

  • Internet Café supports individual accounts, credits and data allocations.
  • VoIP covers crew and business calling over the vessel’s data connection.
  • Telemetry and traffic analysis help shore teams review link availability, equipment status and consumption.
Choose applications around the users

abela.io provides the fleet perspective for shore teams. abela Pulse gives captains and crew an onboard view of digital operations, with onboard status and support access. abela Drive provides secure vessel file storage with authenticated access and an activity trail.

  • Confirm which sources and services each application will use.
  • Agree user access, administration and the responsibilities behind an alert.
  • Review the behaviour of each required function on limited or interrupted connections during a walkthrough.
Discuss the service scope

A practical starting point

Start with the person who needs the information.

The abela applications serve different users. Choosing the right application begins with their work, not the product name.

Explore the requirement that fits your team.
The team overseeing the fleetabela.io

Fleet and site information, operational context and the view from shore.

Discuss this requirement
The captain and crewabela Pulse

Onboard system status, available modules and support access.

Discuss this requirement
The people responsible for vessel filesabela Drive

Secure storage, authenticated access and a record of file activity.

Discuss this requirement

Connected services

Connect Software to the wider operation.

The abela applications serve distinct roles around Zwana and One Net’s managed services. Select the team and task first, then review infrastructure, access and configuration together.

From specification to handover

Choose the task. Then demonstrate it.

A useful software review starts with real users and representative information. Follow the task through the application, the connection and the people responsible for the result.

  1. Define the users and records

    Identify the shore team, onboard users, files, mailboxes and information sources involved. Decide which application owns each task and where existing systems will remain in use.

    Bring: user roles, sample tasks and current applications.

  2. Walk through the actual work

    Review the available modules and permissions with representative data. Check the chosen functions on the vessel’s intended connection and make any limitations clear to the users.

    Agree: demonstration tasks and acceptance criteria.

  3. Prepare the service handover

    Assign account administration, document ownership, mailbox management and support contacts. Define how users join, change roles and leave, and what records the organisation needs to retain.

    Keep: access responsibilities and user handover notes.

Before you decide

Make the differences clear.

Review your requirements

Which abela application does our team need?

abela.io serves the shore team overseeing fleet and site information. abela Pulse gives captains and crew an onboard view of available status and modules, with support access. abela Drive provides vessel file storage, authenticated access and an activity record. Choose the task before choosing the product.

What should we check before changing maritime email?

List domains, mailboxes, current clients and administration responsibilities. Review delivery handling, attachment limits, quarantine and any existing archive or retention requirements. Plan the cutover and confirm how users identify a queued message versus a delivered one.

How do crew internet and the onboard portal relate?

Internet Café handles crew accounts, allocations and usage within the configured Zwana environment. Pulse is the onboard portal. An airtime allowance, an application login and access to support serve different purposes; demonstrate the parts selected for your vessel together.

What should happen when the connection is interrupted?

Confirm the behaviour of each selected function during a demonstration. Identify which information remains available, which tasks need a connection and how users recognise an incomplete action. Offline synchronisation or automatic recovery should be confirmed for the specific product and configuration.

Talk to an expert

Find the tools that fit your teams.

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.