What is available
and what is staged.

Observed in the current application

• Administrator sign-in, sign-out and vessel name/MMSI search.
• Vessel listings, vessel details, alert listing and the existing map/dashboard.
• Existing report/export endpoints, with uneven workflow and content validation.
• The narrow Dark Vessels frontend correction, with received-gap wording that avoids asserting deliberate shutdown.

Visible controls are not proof of complete end-to-end validation. Review source timestamps and error states for the specific task you are performing.

Tested in isolation; not yet deployed

• Company-private investigation cases and frozen evidence captures.
• AIS gap explanations with source context and explicit limitations.
• Insurance Evidence Review, incident timelines and evidence-linked findings.
• Case replay and the new HTML/JSON report exports.
• Company trial eligibility and sandbox subscription access controls.

The screenshots and sample report in these docs demonstrate this staged workflow using synthetic data. They are not real client investigations or proof of a live commercial deployment.

Not established or not included by default

• Guaranteed satellite coverage or independently verified current SAR detections.
• Independent authentication of corroborating documents or attachment storage in the review.
• Certified insurance audits, automated fraud/coverage decisions or guaranteed legal admissibility.
• Verified feed redistribution rights, unlimited data or a contractual performance/SLA promise.
• General self-service company onboarding or active commercial charging.

Arrange an informed evaluation

Ask to review the workflow in its stated environment, confirm the data scope, and agree the criteria that matter to your team. For insurance use, assess the report with a qualified practitioner and identify the independent evidence still needed.