The most important technology on an autonomous ship may not be on the ship at all.

It may be the communications network that keeps the vessel connected to shore. The remote operations centre that can intervene when automation reaches its limits. The port systems capable of exchanging machine-readable information with the vessel. The cybersecurity architecture protecting navigation and control systems. The legal framework that decides who is responsible when a decision is made partly by software, partly by a remote operator and partly by a master who may not be physically present on the bridge.

This is why Africa should be careful not to treat autonomous shipping as a distant spectacle involving futuristic vessels in Europe or Asia.

In May 2026, the International Maritime Organization adopted the first global International Code of Safety for Maritime Autonomous Surface Ships — the MASS Code. The non-mandatory Code took effect on 1 July 2026 and establishes a goal-based safety framework for remotely controlled and autonomous commercial ships. IMO’s roadmap then moves toward a future mandatory MASS Code, with adoption targeted by 1 July 2030 and entry into force on 1 January 2032.

The regulatory clock has therefore started.

The question for Africa is not whether every port will suddenly begin receiving crewless cargo ships in 2027. That is unlikely.

The more important question is whether African maritime systems are beginning to develop the shore-side capabilities that autonomy will eventually require.

Because a ship can become autonomous faster than a port, a regulator, a communications network or a legal system can become ready for it.

Autonomous does not mean human-free

The popular image of autonomous shipping is a vessel crossing the ocean with no crew, no bridge team and an artificial-intelligence system making every decision.

That is only one possible form of autonomy.

IMO defines a Maritime Autonomous Surface Ship, or MASS, as a ship that can, to varying degrees, operate independently of human interaction. A vessel may still have crew onboard while using automated decision-support systems. It may be remotely controlled from shore with seafarers still onboard. It may be remotely operated with no crew onboard. Or it may eventually perform certain functions autonomously.

The new MASS Code is therefore not built around a single vision of the “robot ship”. It uses a functional approach. Shipowners and designers are expected to identify which functions are performed conventionally onboard, which are remotely operated and which are autonomous.

That distinction matters because the human does not simply disappear.

The human may move.

Some roles that traditionally sit on the bridge or in the engine room may increasingly be supported or performed from a remote operations centre. Decision-making may be shared across onboard personnel, shore-based operators and software systems. A conventional watchkeeping structure may evolve into a distributed operational system in which responsibility crosses the physical boundary of the vessel.

That creates an entirely new infrastructure problem.

The ship may be autonomous. The ecosystem cannot be disconnected.

A conventional ship can lose a data connection to shore and continue operating because the people, knowledge and control functions required for navigation are onboard.

A remotely operated ship is different.

If a safety-critical function depends on a shore-based operator, then connectivity is no longer merely a convenience. It becomes part of the operational architecture.

This is reflected directly in the MASS Code. The framework addresses connectivity, remote operations, software principles, alert management, navigation, human factors, security, machinery, search and rescue and other functions needed to achieve safety equivalent to a conventional ship.

For African maritime authorities, that should change the way autonomy is discussed.

The readiness question is not simply:

Can an autonomous ship navigate to an African port?

It is:

Can the surrounding maritime ecosystem maintain safe, secure and legally accountable operations when critical ship functions are distributed between vessel, software and shore?

What does an autonomous-shipping ecosystem actually require?

Africa does not need to build one giant autonomous-shipping platform. It needs a set of interoperable capabilities.

A useful way to think about the architecture is:

Autonomous vessel → resilient connectivity → remote operations → digital port systems → vessel traffic services → cyber defence → regulatory oversight → emergency response.

If one layer fails, autonomy becomes harder to scale safely.

1. Resilient maritime connectivity

Remote operation depends on reliable communication between ship and shore.

This does not mean every autonomous vessel requires uninterrupted broadband for every function. Good autonomous-system design should allow the vessel to remain safe when connectivity degrades or fails. But remote supervision, telemetry, software updates, situational awareness and human intervention all depend on communications systems with appropriate reliability, redundancy and latency.

A realistic architecture could combine satellite links, coastal cellular networks, private port networks and other maritime communication systems depending on the operational area.

For Africa, the issue is not simply coverage.

It is assured coverage.

A commercial internet connection that is acceptable for email is not automatically suitable for a safety-critical remote operation. Operators need to understand latency, failover, interference, bandwidth availability, cyber exposure and service continuity along a vessel’s actual route.

That suggests a future role for governments, telecommunications providers, satellite operators, ports and maritime administrations: mapping where autonomous and remotely operated vessel corridors can be supported safely, and where communications resilience remains insufficient.

2. Remote Operations Centres could become a new maritime industry

If some ship functions move ashore, then one of the most important facilities in future shipping may look less like a bridge and more like a control centre.

A Remote Operations Centre could allow qualified personnel to supervise one or more vessels, monitor systems, receive alerts, communicate with ports and intervene when predefined conditions require human judgement.

But a remote operations centre should not be confused with a room full of screens.

Its design raises difficult questions.

How many vessels can one operator safely supervise?

What qualifications should remote operators hold?

How is fatigue managed when the operator is ashore rather than on watch at sea?

What happens if the centre loses power or communications?

Should a backup centre exist in another location?

How should bridge-resource-management principles be translated into shore-based teams?

Which decisions remain the legal responsibility of the master?

The MASS Code keeps the human element at the centre of the safety framework, even as technology changes where human functions are performed.

This creates a strategic opportunity for Africa.

Instead of seeing remote operation only as a technology imported with foreign-built vessels, African maritime economies could develop their own remote-operations expertise, simulation centres, training programmes, communications services and human-machine-interface capabilities.

That is not only a regulatory task. It is a potential new service industry.

3. Ports must become machine-readable environments

An autonomous ship does not arrive at a port in isolation.

It needs information.

Berth availability. Pilotage requirements. Tug arrangements. Traffic restrictions. weather and hydrographic information. Port-clearance requirements. Security notices. Cargo instructions. Navigation warnings. Terminal readiness.

Today, much of maritime coordination still relies on human communication across phone calls, emails, radio messages, PDFs and separate digital systems.

Autonomy increases the value of structured, standardised and machine-readable information.

A port that can exchange trusted digital data with ships, agents, terminals and public authorities is much better positioned for future autonomous operations than a port whose critical processes remain fragmented across manual systems.

Africa is already moving in this direction.

Since 1 January 2024, IMO Member States have been required to use Maritime Single Windows for the electronic exchange of information associated with ships’ arrival, stay and departure. In April 2026, IMO, the Africa Transport Policy Program and the World Bank convened representatives from 12 African countries in Tanzania to accelerate Maritime Single Window and Port Community System implementation and improve the way port and shipping data is structured and exchanged.

IMO’s “Future-Ready Shipping in Africa” programme is also supporting Sub-Saharan African countries with digital-readiness assessments, data-driven maritime oversight, Maritime Single Window roadmaps and upgraded training in digital technologies.

These systems were not created primarily for autonomous vessels.

But they are part of the same foundation.

A port cannot realistically become autonomy-ready if it is still struggling to become digitally interoperable.

4. Vessel Traffic Services may become part of the human-autonomy interface

Vessel Traffic Services already help monitor and coordinate maritime traffic in busy or sensitive waters.

Autonomous shipping could make their role more complex.

How does a VTS operator communicate with a vessel whose navigation decisions are being made partly by an autonomous system?

Who receives the instruction?

A remote operator?

A master onboard?

A machine interface?

What information should an autonomous vessel expose to traffic authorities about its current mode of operation, system health or level of human supervision?

Ports and coastal States may eventually need protocols that allow VTS centres to understand not only where a vessel is, but how it is being controlled.

That creates a broader design challenge: autonomous shipping will require maritime authorities to interact with machines without losing clear human accountability.

5. Cybersecurity becomes a navigation issue

The more control functions move into software and communications networks, the less meaningful it becomes to separate “cybersecurity” from “ship safety”.

If a cyber incident can affect propulsion, navigation, sensor data, remote control or port-clearance systems, then cyber resilience becomes part of physical maritime safety.

This is especially important because autonomous shipping increases the number of interfaces that may require protection:

ship-to-shore communications;
remote-operation workstations;
navigation and sensor systems;
software-update mechanisms;
cloud and data infrastructure;
port and terminal interfaces;
identity and access-control systems; and
third-party technology suppliers.

IMO’s broader digitalisation work is already moving in this direction. In March 2026, the Facilitation Committee approved a global Strategy on Maritime Digitalization and advanced mandatory cybersecurity measures for Maritime Single Windows, recognising that increasingly connected port systems create operational, safety and security risks.

The implication is straightforward.

Africa should not digitise maritime infrastructure first and add security later.

Autonomy makes “secure by design” a prerequisite.

6. The legal problem is not simply “who is the captain?”

Autonomous shipping creates legal questions that go much deeper than terminology.

Consider a remotely operated vessel entering port.

An onboard system identifies a collision risk. An autonomous navigation function recommends one manoeuvre. A remote operator overrides it. A communications delay means the command arrives late. The ship then takes an emergency action automatically.

If damage occurs, responsibility cannot be determined merely by asking which person touched the controls last.

Investigators may need to understand:

the vessel’s approved operating mode;
the responsibilities assigned to the master and remote operator;
system design and limitations;
software behaviour;
communications performance;
the quality of sensor information;
human intervention; and
the operator’s safety-management procedures.

IMO’s autonomous-shipping work has therefore had to consider the meaning and responsibilities of masters, crews, remote operators and other persons involved in ship operation.

African maritime law will eventually need to absorb these concepts into national legislation, casualty investigation, certification, port-state control, insurance and liability practice.

Waiting until the first serious incident involving an autonomous vessel would be the worst time to start.

7. Search and rescue becomes more complicated when there may be nobody onboard

A crewless vessel creates an unusual emergency profile.

If the vessel itself is in distress, responders may need to deal with machinery, fire, flooding or loss of control without an onboard crew able to provide situational awareness.

If another vessel or person is in distress nearby, questions also arise about the autonomous vessel’s ability to render assistance.

The MASS Code addresses search and rescue because autonomy changes both sides of the rescue equation.

For African coastal States, this means future readiness cannot stop at port gates. Maritime rescue coordination centres, coast guards, navies and emergency-response agencies need to understand how they would communicate with, board, tow, recover or secure an autonomous vessel during an incident.

8. Seafarer skills will change before seafarers disappear

Autonomy is often discussed as a threat to seafaring jobs.

The reality will probably be more uneven.

Some tasks may be automated. Some onboard roles may shrink on certain vessel types. Other roles may move ashore. New roles will emerge around remote supervision, systems engineering, cyber operations, sensor maintenance, data analysis, software assurance and autonomous-system certification.

The near-term African challenge is therefore not to predict a world with no seafarers.

It is to prevent a skills gap.

A maritime academy that trains only for conventional bridge and engine-room operations could find that graduates are technically competent but unprepared for systems increasingly shaped by automation and remote supervision.

A future-ready curriculum may need to combine conventional seamanship with:

human-machine interaction;
remote watchkeeping;
automation management;
cybersecurity awareness;
data interpretation;
software and sensor fault recognition; and
decision-making under degraded connectivity.

This direction is already visible in IMO’s Future-Ready Shipping in Africa initiative, which includes upgraded maritime education and training for digital technologies alongside decarbonisation and alternative-fuel skills.

Africa should not copy the autonomous-shipping model of another region

There is a temptation in emerging technology to assume that the future will arrive from somewhere else fully formed.

A European autonomous coastal vessel operates in a highly digitised port network, under a specific communications environment, with particular labour costs, traffic conditions, hydrographic coverage, legal structures and rescue capabilities.

Those assumptions may not transfer directly to West Africa, East Africa or the Gulf of Guinea.

African autonomy will need to be designed around African operating realities.

That may mean the most commercially sensible early applications are not large crewless oceangoing container ships.

They could be controlled environments where the operational domain is narrower and easier to manage: harbour craft, survey vessels, environmental-monitoring platforms, security and inspection craft, offshore-support applications, ferries on defined routes, inland-waterway operations or specialised logistics between fixed locations.

The principle should be to begin where autonomy solves a real operational problem, not where it produces the most futuristic demonstration.

The right question for government: where should autonomy be allowed to learn?

Because the MASS Code is initially non-mandatory, the period ahead is partly about experience-building.

African maritime administrations should consider using that period deliberately.

Rather than waiting for autonomous vessels to arrive commercially, governments could establish controlled test environments or regulatory sandboxes for defined maritime use cases.

A credible pilot could bring together:

the maritime administration;
port authority;
navy or coast guard;
classification society;
telecommunications provider;
local technology company;
maritime university;
insurer;
vessel operator; and
an independent safety assessor.

The purpose should not be to prove that a vessel can move without a crew.

That has already been demonstrated elsewhere.

The purpose should be to learn whether the whole operating system works safely under local conditions.

A practical African autonomous-shipping readiness framework

Before a country describes itself as ready for autonomous shipping, it should be able to answer seven questions.

Readiness Layer	Critical Question
Connectivity	Can safety-critical ship-to-shore communications remain resilient across the intended operating area?
Remote Operations	Are there approved facilities, trained operators, redundancy and clear human responsibility?
Digital Ports	Can ports exchange standardised, secure and machine-readable information with vessels and authorities?
Cybersecurity	Are ship, shore and port interfaces protected as operational infrastructure rather than ordinary IT?
Regulation	Do national laws recognise autonomous and remotely operated functions, responsibilities and evidence?
Emergency Response	Can authorities intervene safely when a vessel has little or no crew onboard?
Skills	Are seafarers, regulators, VTS operators, engineers and investigators trained for human-machine operations?

If the answer to several of these questions is no, the solution is not to reject autonomous shipping.

It is to identify the infrastructure gap early enough to close it intelligently.

There is an industrial opportunity hidden inside the regulation

The most interesting question for AD Marina is not simply whether Africa will adopt autonomous ships.

It is whether African companies will build any of the technologies and services around them.

The autonomous-shipping ecosystem will require:

remote-operation software;
marine communications integration;
port-system APIs;
sensor and edge-computing systems;
cybersecurity services;
simulation and training platforms;
digital-twin technology;
vessel-performance analytics;
fault-detection systems;
autonomous-system assurance;
shore-control centre design; and
legal, insurance and certification expertise.

If African maritime economies wait until autonomous shipping is mature before developing these capabilities, most of that technology stack will arrive as imported infrastructure.

If they start during the experience-building period, there is room to develop local expertise around the parts of autonomy that depend heavily on operating context.

That is where “Solutions from Africa, for Africa to the world” becomes more than a slogan.

The future ship will expose the quality of the shore

The autonomous vessel attracts attention because it is visible.

The shore-side systems behind it are less dramatic.

But the future of autonomous shipping will depend on them.

A vessel may contain advanced AI, redundant sensors and sophisticated control software, yet still be constrained by a port that cannot exchange data efficiently, a communications corridor without adequate resilience, a regulator without an approval framework, a VTS centre without appropriate interfaces or an emergency system that does not know how to respond when no crew is onboard.

This is the central lesson for Africa.

Autonomous shipping is not primarily a race to remove people from ships. It is a race to redesign the maritime system around a new relationship between people, machines and shore.

IMO has now provided the first global framework for that transition. The non-mandatory MASS Code gives States and industry a period to learn before the expected move toward mandatory rules in the next decade.

Africa should use that period.

Not by declaring that every port must become autonomous.

Not by purchasing technology for prestige.

And not by assuming that a model designed for Rotterdam, Singapore or a Scandinavian coastal route can simply be installed in Lagos, Tema, Mombasa or Durban.

The smarter approach is to build the capabilities that remain valuable whether autonomy arrives quickly or slowly: secure digital ports, resilient connectivity, strong maritime cybersecurity, interoperable data systems, better technical training, modern vessel-traffic management and regulators capable of understanding software-defined ships.

Those investments improve conventional shipping today.

And they prepare Africa for autonomous shipping tomorrow.

At AD Marina, we believe the future of maritime technology should be approached from the system outward: understand the vessel, the port, the regulator, the network and the human operator as one connected environment. The question is no longer whether autonomous ships can sail. It is whether the maritime systems around them are ready to think, communicate and respond at the same speed.

Frequently Asked Questions

What is a Maritime Autonomous Surface Ship?

IMO describes a MASS as a ship that, to varying degrees, can operate independently of human interaction. Autonomous or remote technologies may replace or support functions traditionally performed by crew onboard. Automation alone does not automatically make a ship a MASS.

Is the IMO MASS Code mandatory?

No. The MASS Code adopted in May 2026 is non-mandatory and took effect on 1 July 2026. It is intended to support experience-building while IMO develops the future mandatory framework.

When could mandatory autonomous-ship rules enter into force?

IMO’s current roadmap targets adoption of a mandatory MASS Code by 1 July 2030, with entry into force on 1 January 2032.

Does autonomous shipping mean ships will have no crew?

Not necessarily. Different ship functions can be conventional, remotely operated or autonomous. Some MASS may still carry crew, while others may be remotely controlled or eventually operate with little or no onboard personnel.

What should African maritime authorities prioritise now?

High-value priorities include resilient maritime connectivity, interoperable port systems, cybersecurity, remote-operation and VTS capability, legal readiness, emergency-response planning and maritime training for automation and human-machine operations.