The IT superintendent you don't have to hire.
On most vessels, IT is everybody's job and nobody's job. We take it off your crew and off your shore team, and run it properly.
Right now, your vessel IT depends on whoever is least annoyed by it.
A crew PC dies. The onboard server has not been backed up since the last superintendent left. Nobody knows the admin password. The ETO is doing it because he is good with computers, which is not the same as being an IT engineer, and it is not his job.
Then class starts asking for a cyber asset inventory, and suddenly it is everybody's problem at once.
We fix this the boring way. We take an inventory, standardise it, monitor it, and support it. So it stops being a fire, and starts being a service.
Managed Vessel IT
All the IT on board, run by us as a service. So you do not need a vessel IT department, and your crew can get back to running the ship.
Your IT department, without the hires
We take responsibility for everything IT on board. No vessel IT staff to recruit, no chief engineer doing double duty. One agreement, one number to call.
Remote support, built for sea
Most problems are solved from shore, over the satellite link, without waiting for a port call. Crew get help from an engineer who knows the vessel.
One annual IT inspection on board
An engineer attends each vessel every year: hardware health, cabling, spares, inventory refresh, and the small faults that never make it into a ticket.
Also in the service
Proactive monitoring. We usually see the problem before the crew does.
Patching and updates on schedule. Applied in planned windows, never mid-operation.
Backups, managed. With restores actually tested, not assumed.
Crew changes handled. Accounts and access set up and revoked as people join and leave the vessel.
Compliance evidence kept current. The asset inventory and patch records ISM and class surveys ask for, maintained as a by-product.
A fixed fee per vessel. Predictable cost, no surprise invoices. Compare it with a salary and see which one wins.
Everything on board that is not the ship.
What we do not touch
Type-approved navigation and safety equipment: ECDIS, radar, GMDSS, AMS. That is the maker's domain and the maker's certification. We work alongside it, we help you keep it segregated from everything else, and we do not put our hands inside it.
- Onboard servers and infrastructure. The machines your fleet software, crew systems and document stores actually run on.
- Endpoints. Bridge admin PCs, engine control room, office, crew mess, cabin terminals.
- Backup and recovery. Tested restores, not just backups that nobody has ever tried to read back.
- Onboard applications. Planned maintenance, reporting, document management, POS and crew welfare systems.
- Peripherals that ruin your week. Printers, scanners, POS terminals, CCTV, digital signage.
- Identity and access. Who can log in to what, and what happens when they leave the vessel.
- Patching and lifecycle. Updates applied on a schedule, hardware replaced before it fails.
IACS UR E26 and E27, without the panic.
Cyber resilience is no longer advice. For vessels contracted from 1 July 2024, E26 and E27 are class requirements, and the evidence has to exist, not just the intention.
Most operators are not failing on cyber because they are careless. They are failing because nobody has ever written down what is actually connected to the vessel network.
We start there.
Compliance is not a certificate you frame. Fleets change, equipment gets added, contractors plug things in. We hold it as a retainer, keep the evidence current, and prepare you for survey.
- Asset inventory. Every connected device on board, documented, owned, and kept current.
- Network segmentation. Operational technology separated from crew, business and guest traffic, with the evidence to prove it.
- Access control and hardening. Accounts, passwords, remote access paths, all under control.
- Patch and update management. A documented process, not an intention.
- Incident response plan. What the crew actually does at 03:00, written in language they will follow.
- Class evidence pack. The documentation your surveyor asks for, prepared before they ask.
Remote first. On board when it matters.
Singapore and Denmark get next-business-day attendance. Everywhere else, we give you an honest mobilisation time up front, and solve most of it remotely in the meantime.
Remote support
Most problems solved from shore, which is the only support that arrives in time for a vessel mid-voyage.
Monitoring
We see the disk filling, the backup failing and the certificate expiring before your crew does.
Port attendance
We meet the vessel where it calls.
Riding technicians
When the work needs sea time, our engineers sail with you and finish the job underway.
Newbuild and retrofit
IT specified, installed and commissioned properly at the yard, instead of patched together in year three.
Crew handover
We train the people who will live with the system.
We have been the person who gets the call.
Twenty-two years of maritime and industrial IT: vessel networks, onboard systems, legacy equipment that should have been replaced a decade ago, and the specific experience of trying to fix something critical from a thousand miles away.
We also build our own maritime software, which means we understand what the vessel IT stack has to carry, and why it fails when it fails. We are comfortable with the awkward legacy: industrial controllers, unsupported operating systems, equipment older than the crew.
And we are vendor-honest. We tell you when the answer is to replace something, including something we sold you.
Find out what is actually on your vessel network.
We will run a review of one vessel and tell you what we find: what is connected, what is exposed, what is unsupported, and what class will ask about. No obligation.
Questions we get asked
Do you replace our shore IT team?
No. Most of our clients have one. We take the vessels, which is the part shore IT teams find hardest and enjoy least.
Can you support a vessel with a bad satellite connection?
Yes. We design for it. Our monitoring and support tooling is built to work over constrained links, and we cache what needs caching on board.
What about our existing IT provider?
We are happy to work alongside them, or take over. If they are doing a good job, we will tell you that too.
We have very old systems on board. Is that a problem?
It is normal, and it is our specialism. Windows NT, unsupported industrial controllers, machines nobody dares to reboot. We know how to isolate and manage them safely rather than pretending they can simply be replaced tomorrow.
Are you a class society or an auditor?
No. We prepare you for survey and produce the evidence. Class does the surveying.