Your fleet has a documentation blind spot.
We close it.

Cited answers. Verified citations. Transparent confidence. Onboard every vessel, offline.

A safety-critical reasoning system for maritime. Crew get a complete procedure, a source tier, and a confidence score on every answer. Everything runs onboard. No internet required.

Full Fathom AI — Crew Assistant
What is the procedure for entering an enclosed space?
High confidence

Before entering an enclosed space, the following steps must be completed in order:

  1. 1.Complete a formal risk assessment using Form OFS-RA-003
  2. 2.Obtain an Enclosed Space Entry Permit from the Master
  3. 3.Ventilate the space mechanically for a minimum of 24 hours
  4. 4.Test atmosphere — O₂ 20.0–21.0%, H₂S below 5 ppm, CO below 25 ppm, LEL below 1%
  5. 5.Station a trained standby person at the entrance
  6. 6.Establish and test two-way communication before entry
  7. 7.Position rescue equipment at the entrance
  8. 8.All entrants must wear personal gas detector and rescue harness
1
Safety Management Manual — §7.3, p.114
SMS
2
Engine Room Procedures — §7.1, p.46
Vessel
3
SOLAS Chapter IX — Management for the Safe Operation
Regulation
Citations verified · 8 / 8 claims grounded in retrieved context

The problem with maritime documentation

$35,000

per day in PSC detention costs

40%

of PSC findings relate to crew knowledge

#1 finding

after incidents: procedure not followed

97%

of generic AI tools hallucinate a citation under pressure. Ours don't — every citation is verified against the retrieved source before it reaches the crew.

“The procedure existed, but was not followed.”

The maritime industry's most common finding after serious incidents

Four steps to operational safety intelligence

01

Upload

Upload your SMS manuals, procedures, and regulatory references. We parse, chunk, and build an AI knowledge index — preserving tables, numbered procedures, and cross-references.

02

Deploy

Download a 5GB bundle to each vessel. Runs on any mini-PC. Zero internet required. Crew access it through a browser on any device connected to the vessel network.

03

Trust

Every answer shows its source tier (SMS, vessel, regulation, reference), a High / Medium / Low confidence badge, and whether each citation is verified against what was actually retrieved. Crew see at a glance whether to act or verify.

04

Learn

See what your crews are asking. Find documentation gaps. Identify procedure hotspots and confusion signals. Fix them before the next audit.

Same question. Three very different answers.

A crew member asks for the man-overboard procedure — a mandatory, safety-critical answer. Here is what each category of system actually returns.

Generic chatbot

Question

What do I do in a man overboard situation?

Answer

In a man-overboard situation, stop the vessel, throw a flotation device, and alert the coast guard.

No source cited
Three generic steps
Could be hallucinated
Generic enterprise RAG

Question

What do I do in a man overboard situation?

Answer

Follow your vessel's MOB procedure and notify the Master immediately. Assemble at muster stations per the Muster List.

Source: Safety Manual

Document-level citation only
Summary — steps missing
No verification of claims
Full Fathom AIHigh confidence

Question

What do I do in a man overboard situation?

Answer

  1. 1Mark position (Williamson turn)[1]
  2. 2Throw lifebuoy with light / smoke[1]
  3. 3Post lookouts[1]
  4. 4Sound general alarm[1]
  5. 5MAYDAY / PAN-PAN on VHF 16[1]
  6. 6Launch rescue boat[1]
  7. 7Notify Coast Guard and nearby vessels[1]
  8. 8Continue search until located or suspended[1]
  9. 9Headcount and muster[1]
SMSSafety Management Manual — §7.2, p.11
VesselBridge Emergency Procedures — §2.4, p.8
9 steps — full safety procedure
Every claim cited and verified
SMS outranks generic regulation

Real output from a real vessel's Safety Management System, running fully offline on a ship.

Under the hood

A reasoning stack, not a search box

Most “AI search” products bolt a language model onto a vector database and call it done. We do five more things that matter for safety-critical retrieval.

Hybrid retrieval

BM25 keyword search + BGE-M3 dense vectors + bge-reranker-v2-m3 cross-encoder. Two-stage ranking means a query for “generator 2 oil pressure” finds the exact spec table even when the crew uses different words than the manual.

Authority hierarchy

Your SMS outranks generic regulation by design. Vessel-specific procedures beat fleet-type, which beat regulation, which beats reference. Every source carries its tier pill so crew see where the answer is coming from.

Self-correction

When the first retrieval pass is weak, the system rewrites the query into maritime vocabulary and tries again — Corrective RAG. The UI tells the crew when this happened, so they know we had to work hard to find the answer.

Parent–child expansion

When a retrieved chunk is one step of a longer procedure, the parent section is pulled in automatically. A 9-step man-overboard procedure never gets truncated because we only matched step 3 of it.

ICLR 2025

Sufficient-context autorater

A second model call checks whether the retrieved context is enough to answer before the response is shown. Based on Google ICLR 2025 research, applied to maritime. Insufficient context triggers a transparent refusal instead of a confident guess.

Every one of these is shipping in production today on the fleet runtime — not a roadmap item.

Measured, not promised

By the numbers

Real results from the stress-test suite we run on every build. No benchmarks on curated data — these are adversarial maritime questions the system has to get right the first time.

3,717

chunks in a typical bundle

Across 4 authority tiers: SMS, vessel, regulations, reference.

89%

pass rate on stress-test corpus

35-case maritime Q&A covering multi-hop, cross-document, refusal, adversarial.

0

unverified citations

On 33 of 35 stress-test answers. The 2 flagged cases showed a warning to the crew, not a confident answer.

<25 s

average answer latency

On complex multi-hop questions. Running fully offline on ship-class hardware.

Category comparison

Why Full Fathom vs. general AI assistants

The maritime safety stakes are different. The requirements on the AI have to be different too.

 Generic chatbotEnterprise RAGFull Fathom AI
Cites sources
No
Document-level
Chunk-level with page numbers
Verifies citations
Yes — flags unverified
Shows confidence
High / Medium / Low with reasoning
Shows source tier
Vessel / SMS / Regulation / Reference
Safety-critical completeness
Summarises
Summarises
Full mandatory procedure enforced
Refuses when uncertain
Sometimes
Always, with transparent rationale
Runs offline
No
Varies
Fully offline by design
Ingests your procedures
No
Yes
Yes
Maritime-aware ranking
No
No
Yes — SMS outranks regulation
Onboard

For Crew Onboard

Crew Q&A interface

  • Simple interface — no training required
  • Ask questions in plain English
  • Every answer cites the source document, section, and page
  • Works fully offline on the vessel network
  • Accessible from any browser — desktop, tablet, or phone
Ashore

For Fleet Managers

Fleet analytics dashboard

  • Query intelligence — see what crews are asking across your fleet
  • Documentation gaps — questions the system cannot answer reveal missing procedures
  • Procedure hotspots — which manual sections are referenced most, and which are never touched
  • Confusion signals — similar questions in different phrasing across vessels means unclear procedures
  • Filterable by vessel, vessel type, and time period

Built for safety-critical operations

Fully Offline

All inference happens onboard. No cloud processing of queries.

No Crew PII

Query logs contain no personal data. Zero crew identification.

Verified Citations

Every citation is checked against what was actually retrieved. Invented or mismatched citations are flagged with a warning — not shown as facts.

Confidence Transparency

Every answer shows High, Medium, or Low confidence with a tooltip explaining why. Crew know when to trust and when to verify.

Authority Hierarchy

Your SMS procedures outrank generic regulation by design. Vessel > SMS > Fleet > Regulation > Reference, with every source tagged.

Safety-Complete Procedures

Man overboard, fire, enclosed space: we return every mandatory step, not a summary. Completeness enforced by design, not hoped for.

ISM Aligned

Supports ISM Code compliance evidence across Sections 6, 7, and 12.

Tamper-Evident Bundles

SHA-256 checksums on every bundle. The runtime refuses to load a file that has been altered in transit.

Your Data, Isolated

Full multi-tenant data separation. No cross-tenant access.

Hardware requirements

Runs on hardware most vessels already have. No GPU required.

 MinimumRecommended
CPUx86_64, 4 coresx86_64, 8 cores
RAM16 GB32 GB
Storage100 GB SSD256 GB SSD
GPUNot requiredNot required
NetworkVessel LANVessel LAN

Simple per-vessel pricing

No setup fees. No per-query charges. Free 2-month pilot available.

Starter

$149/vessel/month
  • Up to 50 documents per vessel
  • Single vessel
  • Standard document processing
  • On-vessel AI runtime
  • Cited answers with source references
  • Email support
Start Free Pilot
Most popular

Professional

$249/vessel/month
  • Unlimited documents
  • Multi-vessel fleet
  • Fleet analytics dashboard
  • Priority document processing
  • Quality report per bundle
  • Cited answers with source references
  • Priority support
Start Free Pilot

Enterprise

Custom
  • Everything in Professional
  • Custom integrations
  • Dedicated account manager
  • API access
  • Custom model tuning
  • SLA guarantees
Contact Us

Save 20% with annual billing

“Documentation exists to keep people safe.Full Fathom AI makes sure it actually does.”

Request a Demo