Nautilus

Phasing & roadmap

Nautilus is delivered in 6 phases over 24 months. Phase 1 lays the foundation that every later phase depends on — we don't skip ahead.

This page is honest about what's available when. Phase 4 features are not shipping today. Where a feature is mentioned elsewhere on this site, the phase it lands in is called out.

We use phase-relative months (e.g., "Phase 4 — months 10–15") rather than calendar dates. Calendar dates rot; phase-relative months don't.

Phase 1 — Foundation (months 1–6)

The baseline every later phase depends on.

  • NATS JetStream cluster, shore + first vessel.
  • Quanta agent contract live on the bus.
  • Zitadel IAM (OIDC / OAuth2).
  • RKE2 shore cluster + K3s on the first vessel.
  • Kong Gateway, identical config shore and onboard.
  • CI/CD: ArgoCD + GitHub Actions, Helm charts per domain.
  • CloudNativePG operator + per-service Postgres.
  • Cilium CNI with WireGuard transparent encryption + Hubble.
  • Domain 1 — Identity & Guest Profile.
  • Domain 2 — Reservation & Check-in.
  • Mobile app skeleton.

Exit criteria: A guest can be created in Domain 1, reserved in Domain 2, and have a board card issued — end-to-end, with the events flowing on the bus and replicating shore-to-vessel.

Phase 2 — Operations Core (months 4–9)

First full-vessel go-live.

  • Domain 3 — Onboard Accounts & Billing (real-time folio, multi-currency, Stripe reference adapter).
  • Domain 4 — Point of Sale (browser PWA, offline queue, KDS, EMV).
  • Domain 5 — Gangway & Access Control (Android tablets, offline mode, SOLAS/ENOAD).
  • Domain 6 — Safety & Muster (mobile mustering, fully offline).
  • ConnectOne cabin telephony.

Exit criteria: A vessel can run a full cruise on Nautilus end-to-end — reservation through end-of-cruise settlement, including muster.

Phase 3 — Revenue Services (months 7–12)

The full guest experience.

  • Domain 7 — Dining & Restaurant.
  • Domain 8 — Shore Excursions & Activities.
  • Domain 9 — Spa & Wellness.
  • Full mobile app (white-label per tenant).
  • Self-service kiosks.
  • Cabin iTV — first-class platform: live TV + VOD + cruise info + booking + folio + crew quick-call + video-call endpoint + cabin GRMS.
  • Fleet-wide digital signage (extended signsync).

Exit criteria: A guest can book dining, spa, and excursions from any of mobile / iTV / kiosk; signage reflects live state across the ship.

Phase 4 — AI Differentiation (months 10–15)

The features that make Nautilus categorically different.

  • Quanta AI Concierge live across mobile, iTV, kiosk, voice.
  • CallCraft voice ordering — guest dials cabin extension, AI takes the order, posts to POS.
  • Heimdall sentiment + content safety — 12-plugin SafeSpace across in-app chat, video calls, photo sharing, signage zones, iTV. CSAM detection path live with NCMEC reporting wired.
  • Predictive spend alerts for revenue ops.
  • AI tour and dining recommendations.
  • AI Notes summaries on every call.
  • AI-guided emergency announcements over the ConnectOne PA/GA tier.

Exit criteria: AI-as-fabric is observably real — agents see operational events, take actions back into domains, and the differentiators on the home page are demonstrable on a reference vessel.

Phase 5 — Enterprise & Fleet (months 13–18)

Crew operations and multi-tenant.

  • Domain 10 — Crew, HR & Payroll.
  • Domain 11 — Materials & Supply Chain.
  • Domain 12 — Fleet Management & HQ Intelligence.
  • Multi-tenant — region-pinned, brand-isolated, full DSR support per tenant.
  • Per-tenant DPIA tooling.
  • Heimdall topology evolution: per-region SafeSpace + single-region analytics with metadata-only cross-border flow.

Exit criteria: Two unrelated cruise operators run on the same Nautilus shore cluster with full data isolation and per-region pinning, each with their own brand surfaces.

Phase 6 — Scale & Optimization (months 16–24)

Fleet rollout. 5,000+ pax tuning. CRS/GDS integration. Regulatory automation.

  • Fleet-wide rollout across multiple vessels per tenant.
  • 5,000+ pax tuning (single-vessel scale ceiling).
  • CRS / GDS integrations beyond Versonix Seaware (Infor Cruise, custom).
  • Regulatory automation — auto-submission of SOLAS / MARPOL / ENOAD reports where the regulator supports it.
  • Telehealth at fleet scale.
  • Tier-C interface specs published in priority order: Heimdall API, CallCraft agent contract, ConnectOne signaling, Quanta keys-service protocol, iTV/GRMS adapter, fleet-wide federation.

Exit criteria: Tenant has multiple vessels live, cross-vessel guest journeys (back-to-back cruises, fleet-wide loyalty) work seamlessly, and the regulatory dashboard requires manual review only on exception.

What's not on the roadmap

  • No "Phase 7." This is a 24-month delivery plan, not a forever-roadmap.
  • No blockchain. Nautilus has nothing to do with it.
  • No proprietary hardware lock-in. Phase 6 doesn't add a "Nautilus terminal" — POS terminals stay commodity.
  • No closed AI black-box. Heimdall stays open with audited primitives.

What governs the roadmap

The source of truth for done is the requirements & features specification (docs/requirements-and-features.md, currently v0.16). When a phase decision is taken that diverges from the spec, the spec is updated — never the other way around.

Open questions tracked formally as OQs in §13 of the spec. Resolutions are dated and propagated.

See the tech stack → See domain detail → Contact us about a deployment →