Shipwize Product Roadmap: What's Coming in Q3–Q4 2026

Our Approach to Roadmap Communication

We share roadmap updates publicly for two reasons: accountability and conversation.

Accountability means we commit to what we're building and you can hold us to it. Conversation means that if you're evaluating Shipwize and a specific feature is critical for your fleet, you should tell us — it may already be on the roadmap, and your use case helps us prioritise.

This is the Q3–Q4 2026 roadmap, as of a review cycle in July 2026.

Q3 2026 (July–September)

Structured Incident AI Summary

When an incident is resolved, the platform already generates a full communication log. In Q3, we're adding an AI-assisted summary layer: a structured incident report draft generated from the communication record.

The draft includes: incident description (from the first notification), response chain (who acknowledged, when), resolution note, and a recommended follow-up action based on incident category.

The AI draft is editable before saving. It doesn't replace human judgment — it eliminates the blank page problem for incident reporting.

Why it matters: Incident report writing takes time. On a vessel with 10–15 incident reports per week, reducing the drafting time by 50% is 2–3 hours of officer time saved.

API v2 — Fleet Management Integration

Our current fleet management integration is a webhook-based push system. API v2 adds a full REST API with: incident record query, crew status query, communication channel management, and roster sync.

This enables deeper integration with fleet management platforms (NAVTOR, DNV, SpecTec) without requiring custom webhook configuration.

Wearable Notification Support

Android watches running Wear OS and Apple Watch (via WatchKit push extension) will receive Shipwize emergency notifications with one-tap acknowledgement. For engine room and outdoor deck contexts, wrist notification is more reliable than phone-based notification.

Q4 2026 (October–December)

Offline AI — On-Vessel LLM

For vessels that want AI assistance without routing data to cloud language models, we're piloting a quantized LLM (LLaMA 3 8B) running on the vessel server. This enables:

• Natural language incident search ("show me all medical incidents from last month from Deck 12")
• Draft notification text from structured alarm data
• Automated categorisation of incoming incident reports

The model runs on the vessel server CPU. No GPU required, no satellite data transmission of communication content.

Video Call Recording

SIP and WebRTC calls can be recorded (with participant consent notification, GDPR-compliant) and linked to incident records. For telemedicine consultations, this provides a complete medical record of the consultation.

Expanded Alarm System Bridges

Current alarm system integrations: Consilium, Autronica, Jastram.

Q4 additions: Emerson (Ovation), Kongsberg maritime, ABB Onboard DC.

If your alarm system isn't listed, contact us — we build integration bridges for fleet-scale deployments.

Multi-Vessel Management Console

Shore-side fleet operators currently access vessel incident records through individual vessel connections. Q4 introduces an aggregated fleet dashboard: all vessels, all active incidents, real-time communication status, and fleet-wide response time analytics.

How to Influence the Roadmap

The roadmap is shaped by fleet operator input. If you're a current customer or evaluating us:

• Tag a feature request in the support portal with [ROADMAP]
• Join the quarterly customer advisory call (announced in the operator newsletter)
• Email our product team directly — we read and respond to every feature request

The roadmap items above came partly from customer input. The features that matter most to you are the features that get built fastest.