FOR BOAT BUILDERS AND MARITIME SYSTEMS INTEGRATORS

Add autonomy to the vessel you build

Keep your vessel design, equipment choices and customer relationships at the centre of the build. NAUTILUS is an autonomy platform in development for builders who want secure communications, onboard vision and controlled access to machinery through documented software interfaces.

IN DEVELOPMENT · PILOT CONVERSATIONS OPEN

Autonomy Software for Boat Builders | NAUTILUS01 / INTEGRATION ARCHITECTUREPLATFORMcore logic and orchestration servicesBRIDGE ADAPTERinterface adaptation to vessel systemsEQUIPMENTonboard subsystem endpointsARCHITECTURE IN DEVELOPMENT

NAUTILUS / FILM

See how BRIDGE connects your build.

BRIDGE · Vessel equipment integration
Watch on YouTube →Playback uses YouTube.
ON THIS PAGE→

Page sections appear in preview

01 / NAUTILUS

Put engineering effort into the capabilities that distinguish your vessel

Connecting sensors, navigation, supervision and machinery creates work that every vessel programme has to address. Identities must be verified, sensor data kept current and control requests checked. NAUTILUS provides a common architecture for those responsibilities, with adapters for the equipment specific to your build.

Your team can concentrate its adapter work on the machinery it knows, while evaluating how the core handles communications, observations and control permission.

The commercial comparison covers the complete build and support requirement. A pilot should establish whether the approach delivers value for your vessel; cost or schedule savings need that baseline.

02 / NAUTILUS

Keep the vessel implementation under your control

The proposed ownership terms let customers buy their vessel-side hardware, retain operational data and maintain the adapters they develop. AIC licenses the core software and agreed integration kit.

AIC retains and licenses the NAUTILUS core. Authorised builders integrate through documented, versioned contracts and the agreed SDK and conformance material. Ownership, licence scope, compatibility support and long-term maintenance are explicit parts of the commercial agreement.

03 / NAUTILUS

Start with a declared capability profile

Identify the ECU family, steering and propulsion arrangement, feedback sources, sensors, power and communications routes. The BRIDGE manifest then defines what the installed vessel actually supports, including units, ranges, timing, faults and the commissioned safe response.

A read-only integration can establish sensing, machinery health and navigation provenance before action-capable interfaces are introduced. This gives the team an early evidence base without assuming that a physical connector establishes protocol support.

04 / NAUTILUS

Add the functions your vessel needs

HORIZON supplies camera observations. RECKON provides qualified navigation state. COURSE assesses a signed mission. WATCH independently admits or withdraws control. BRIDGE translates the admitted intent into the commissioned equipment interface, and WAVE supports protected supervision and evidence delivery.

That chain allows a pilot to define which functions it is proving, with command permission and hardware access separated from perception and planning.

05 / NAUTILUS

Agree responsibilities before the vessel reaches the water

NAUTILUS’s intended scope covers the edge runtime, shared contracts, software authority boundary, adapter interface and evidence mechanisms. The builder and operator retain whole-vessel integration, electrical protection, equipment suitability, physical emergency provisions and operating approval.

The integration plan should identify the responsible party for each component and acceptance item. A complete installation needs power, thermal, ingress, connector and EMC evidence for the assembled system, alongside software and security checks.

06 / NAUTILUS

Build the commercial comparison around the full lifecycle

Evaluate the core licence, integration engineering, hardware, component licences, trials, support and future change. Ask how adapters can be maintained, which versions remain supported and what evidence is available for investigation and audit.

The goal is a cost model that a buyer can assess against its own alternative, with ownership and ongoing obligations visible.

07 / NAUTILUS

Bring us a vessel and a first use case

Bring AIC the vessel type, mission, machinery and sensor interfaces. We can identify where NAUTILUS fits, which adapters are needed and what has to be tested before the vessel trial.

Supported hardware, adapters and operating modes are agreed against the tested configuration. Licence and ownership terms are part of the proposal.