FOR DEFENCE AND MARITIME SECURITY TEAMS
Secure maritime autonomy for your mission
Maritime security teams need useful observations, protected communications and clear control of what a vessel may do. NAUTILUS is a software platform in development for those requirements, with local processing, SHACE-based post-quantum security requirements and independent command checks aboard.
IN DEVELOPMENT · PILOT CONVERSATIONS OPEN
ON THIS PAGE→
Page sections appear in preview
01 / NAUTILUS
Build a capability your technical teams can interrogate
Your technical team needs to assess the complete installation: the link, device credentials, onboard software, sensors and route into the machinery.
NAUTILUS assigns a specific job to each module. Observation records identify the model and sensor used. Navigation data includes its age and uncertainty. Commands carry an authenticated source and expiry. The result distinguishes what was requested from what the vessel actually did.
Security, integration and operational staff can therefore examine the same chain of records when assessing the capability.
02 / NAUTILUS
Protect supervision across untrusted infrastructure
WAVE defines the authenticated application connection over approved routes, with SHACE as the external secure packet tunnel. A reviewed post-quantum profile is required before operational remote commands can be admitted.
Endpoint identity, permitted routes, key lifecycle and captured-device response belong in the evaluation from the outset. The current SHACE evidence is a lab proof of concept; operational assurance must be established for the selected topology and hardware.
03 / NAUTILUS
Process maritime observations locally
HORIZON places vessel detection aboard and produces observation records with the model, time and calibration used. The link can carry those records when continuous video streaming is unsuitable or unavailable.
Military or naval subtype recognition depends on a separately evaluated model. A visual class remains an observation about appearance, and identity correlation requires additional evidence. Uncertainty remains visible to the operator and downstream policy.
04 / NAUTILUS
Keep mission permission explicit
The signed mission package defines the authorised objective, area, limits, required inputs and contingencies. COURSE proposes action within that scope. WATCH checks control ownership and interlocks, and BRIDGE remains the sole equipment-translation boundary.
Remote supervisors, local planners and external systems all submit requests through defined boundaries. Integration with an existing mission or combat-management system requires its own authenticated adapter and scope; it does not create implicit actuation authority.
05 / NAUTILUS
Plan for degraded connectivity and lost equipment
A locally staged mission is intended to continue only while its onboard authority, data, navigation and reserve conditions remain satisfied. Outages must preserve a coherent mission state and audit trail for later reconciliation.
The security design also includes unique device identities, bounded offline trust, shore-side quarantine and controlled re-enrolment after suspected compromise. Those controls must be evaluated against a realistic loss-or-capture scenario.
06 / NAUTILUS
A focused evaluation route
A first pilot can focus on protected observation and supervision, using a simulator to exercise control and faults. Extension to physical autonomy requires the vessel safety case, tested hardware and operating approval for the mission.
NAUTILUS is in development. Operational assurance, defence accreditation and any security approval must be established for the named deployment and intended use.