For cruise operators
A pitch for the people in your organization who decide what runs on your vessels: the CEO, the CIO, the CTO, the VP of IT, the VP of Hotel Operations.
This page is written for you specifically. The other pages cover the architecture, the open-source posture, and the developer story. This page is about TCO, time-to-deploy, retrofit-first posture, regulatory positioning, and what "open source" actually means for a cruise operator.
The honest case for switching
The SPMS market has three serious players. Two are 30-year-old Windows monoliths. The third is modern but narrow. None of them ship native AI voice. None of them have integrated content safety for the kid-on-board reality. None of them are open source. Two of three still rely on batch ship-to-shore sync.
Your operating costs reflect this. The monoliths are 9-figure TCO at fleet scale because every AI feature is a custom quote, every PBX integration is a project, every regulatory addition is a release cycle, and every terminal you buy is locked to a vendor.
Nautilus changes the contract:
- Open source. No license fees on the platform. Pay for support and managed services if you want them. Pay for nothing if you'd rather operate it yourselves.
- AI as fabric. New AI capabilities show up as agents on the bus, not as quoted custom projects.
- Voice-first. ConnectOne carries the call; CallCraft AI joins as an agent. Voice ordering, AI Notes, AI-guided muster, omnichannel federation — one platform, no integration jungle.
- Retrofit-first. Your existing PBX, IPTV head-end, and signage system don't have to be replaced on day one. Tier-C specs let them coexist while you migrate at your own pace.
- Commodity hardware. No MICROS terminals. No Oracle DB. No proprietary scanners. Replace a vendor and the software doesn't notice.
TCO comparison (directional)
A directional view — your numbers will differ. NT Connect runs detailed TCO models per fleet under NDA.
| Cost category | Oracle SPMS | MXP | Otalio | Nautilus (NT Connect managed) | Nautilus (self-hosted) |
|---|---|---|---|---|---|
| Platform license | High (per-vessel + per-pax + module fees) | Medium-high | Medium | None (AGPL) | None (AGPL) |
| Hardware lock-in | High (MICROS, Oracle DB infra) | Medium | Low | None | None |
| AI features | Quoted custom (high) | Add-on modules (medium-high) | Limited / external | Included as agents on the bus | Included as agents on the bus |
| PBX | Limited integration | Limited integration | Limited integration | ConnectOne included | Self-hosted ConnectOne |
| Content safety | Not native | Limited | Not native | Heimdall managed | Self-hosted Heimdall |
| Per-vessel deployment | Long, vendor-led | Vendor-led | Vendor-led | NT Connect-led, playbook-driven | Tenant-led, with NT Connect support optional |
| Multi-tenant for fleet brands | Retrofitted | Retrofitted | Limited | Native — region-pinned, brand-isolated | Native |
| Vendor lock-in exit cost | Very high | Medium | Low-medium | Zero — full source, AGPL | Zero — full source, AGPL |
The leverage is in three places: no platform license fee, AI capabilities as part of the platform rather than quoted projects, and commodity hardware throughout.
Request a TCO model under NDA →
Time-to-deploy on a new vessel
The Phase-1 vessel is the slow one. Subsequent vessels are playbook-driven and faster.
| Stage | Phase-1 vessel | Phase-N vessel |
|---|---|---|
| Onboard cluster commissioning | Full engineering | Playbook + checklists |
| Network commissioning | Full survey | Standardized profile |
| Hardware procurement | Vendor qualification | Off-shelf SKUs |
| Integration with operator's CRS / PBX / IPTV | Adapter authoring (Tier-C) | Re-use of authored adapters |
| Regulatory acceptance | Per-jurisdiction walk-through | Re-use of authored compliance package |
| Crew training | First-vessel cohort | Train-the-trainer |
| Go-live dry-run | Full simulated cruise | Standardized acceptance test |
Phase-1 vessel: months 4–9 in NT Connect's standard delivery model (corresponding to spec-doc Phase 2 — Operations Core). Phase-N vessel: weeks, not months, once the operator's adapters and compliance package are in place.
Retrofit-first posture
You're not ripping out your existing investments on day one. The Tier-C interface model is built precisely for retrofit.
- Legacy PBX stays. Avaya, Mitel, Cisco, Alcatel, Asterisk, FreeSWITCH — all integrate via the published ship-PBX spec (Draft v0.1 live today). Your existing PBX shows up on the Nautilus bus for call events, PA/GA, E911, recordings, and commands. Replace when you decide, not when the platform forces you.
- Existing IPTV head-end can run alongside Nautilus's iTV stack while you migrate.
- Existing signage can be progressively migrated to extended signsync.
- Existing CRS stays in place; the Domain 2 adapter integrates against it.
- Existing payment processor plugs into the Domain 3 vendor-agnostic adapter.
Migration is a track, not an event.
Fleet rollout playbook
A typical fleet rollout follows this shape:
- Phase 1 vessel (months 4–9) — full engineering attention, regulatory acceptance, crew cohort training. Operations Core domains live (folio, POS, gangway, muster, ConnectOne cabin telephony).
- Phase 2 vessel (months 9–12) — playbook-driven, operator-led with NT Connect oversight. Phase 3 domains added (dining, excursions, spa, full mobile, kiosks, iTV, signage).
- Phase 3+ vessels — accelerated rollout. Each vessel inherits the operator's adapters and compliance package.
- AI differentiation activation (months 10–15) — Quanta Concierge, CallCraft voice ordering, Heimdall content safety, predictive spend live across the fleet.
- Crew & supply (months 13–18) — Domain 10 / 11 / 12 live; multi-tenant if the operator runs multiple brands.
- Fleet at full scale (months 16–24) — 5,000+ pax tuning, CRS/GDS integrations, regulatory automation.
Data residency, GDPR, and regulatory
Privacy is the global default, regardless of tenant jurisdiction. GDPR-grade controls are baseline; tenants in other jurisdictions inherit them rather than getting weaker protections.
- Per-tenant region pinning. Operational data stays in-region.
- DSR APIs as first-class endpoints in Domain 1: access, rectify, erase, port, restrict, object.
- Per-category retention configured per jurisdiction.
- Crypto-erasure for non-deletable stores (audit logs, append-only ledgers).
- DPIA per tenant authored at onboarding.
- No secondary use of operational data without explicit renewed consent.
- Heimdall topology — per-region SafeSpace + consolidation-region analytics with metadata-only cross-border flow.
For maritime regulatory:
- SOLAS, MARPOL, STCW dashboards in Domain 12.
- ENOAD submissions from Domain 5.
- EU-LISA-compatible access-control interface.
- NCMEC + IWF + BKA + eSafety + INHOPE wiring for Heimdall's CSAM detection path.
- E911 with Kari's Law + dynamic routing in ConnectOne.
- Maritime legal pack authored per cruise itinerary.
NT Connect's compliance assistance service handles the per-tenant DPIA, jurisdictional retention configuration, and audit liaison.
What you should expect from NT Connect
- A named technical account manager at Gold tier and above.
- Quarterly architecture review at Gold tier and above.
- Onboard incident response at Platinum tier for safety-critical paths (muster, gangway, ConnectOne PA/GA, E911).
- A public roadmap that you can comment on as a tenant.
- A CLA-signed pathway for your own engineers to contribute upstream if you want.
- A commercial license available if AGPL doesn't fit your distribution posture.
Talk to NT Connect → Request a TCO model under NDA → Read the spec →