Nautilus

For system integrators

If you're integrating Nautilus into a cruise operator's environment — building CRS adapters, retrofitting legacy PBXes, wiring up GRMS, migrating IPTV head-ends, or authoring adapters for a vendor whose system we haven't touched yet — this page is for you.

The integration model is Tier C — Documented interfaces. You implement against published specs. You don't need to use any NT Connect closed-source code. Conformance harnesses verify that your integration meets the contract.

How integration works in Nautilus

The integration surface is not a SDK to install. It's a set of published interface specifications with reference stubs and conformance harnesses.

  • Spec text is CC BY 4.0.
  • Reference stubs and conformance test harnesses are Apache 2.0.
  • You implement against the spec; the conformance harness verifies the implementation meets the contract.
  • No NT Connect proprietary code is required to ship a compliant integration.

The model is deliberately the same way Signal published its protocol: open primitives, audited crypto, conformance harnesses, no SDK lock-in.

Tier-C specs

Spec Status What it covers
ship-PBX integration Live (Draft v0.1) Legacy on-vessel PBX (Avaya / Mitel / Cisco / Alcatel / Asterisk / FreeSWITCH / etc.) ↔ Nautilus bus for call events, PA/GA, E911, recordings, and commands. Retrofit-first.
Heimdall content-safety API Coming next REST contract for /analyze, /moderate, /moderate/conversation, /moderate/image, /moderate/video. Audience tier enum. Verdict schema. NCMEC-hook pattern.
CallCraft agent contract Coming Extends the Quanta agent contract (AGENT_MESSAGES / AGENT_RESPONSES) with voice/video-session semantics so third-party AI agents can participate in calls and rooms.
ConnectOne E911 / PA-GA / muster signaling Coming Concrete subject contract and priority semantics for Nautilus muster and safety flows when ConnectOne (not a legacy PBX) is the telephony platform.
Quanta keys-service protocol Coming Key-bundle format and verification, so third parties can implement a Quanta-compatible keys-service.
iTV / cabin GRMS adapter contract Coming Lighting, HVAC, drapes, safe, minibar, door-lock abstraction behind a pluggable adapter.
Fleet-wide federation Coming Ship-to-ship and ship-to-shore subject routing for multi-vessel tenants.

Each spec follows a standard structure:

  1. Purpose & audience.
  2. Integration model — the 30-second picture.
  3. Authentication & authorization (transport, JWT claim schema, capability model).
  4. Subject / endpoint contracts.
  5. Payload schemas.
  6. SLAs and delivery semantics.
  7. Priority / emergency handling (where applicable).
  8. Tenant isolation.
  9. Retention & data handling.
  10. Conformance testing.
  11. Security considerations.
  12. Known unknowns / TBD.
  13. Relationship to Nautilus requirements (FR / NFR / F-Dxx / OQ references).
  14. Licensing.

Browse all Tier-C specs →

The retrofit-first integration story

Most integrators arrive at Nautilus when an operator has decided to migrate. The operator already has:

  • An existing PBX (Avaya / Cisco / Mitel / Alcatel / Asterisk / FreeSWITCH).
  • An existing CRS (often Versonix Seaware, sometimes Infor Cruise, sometimes a custom system).
  • An existing IPTV head-end with content licenses tied to it.
  • An existing signage system (often vendor-locked).
  • An existing payment processor (Stripe, Adyen, or a regional provider).
  • Existing GRMS (KNX / BACnet / DALI in cabin) wired into a vendor's controller.

You don't replace any of this on day one. Tier-C interfaces let the existing systems coexist with Nautilus while migration happens at the operator's pace. NT Connect builds the bridges; you, as an integrator, can build them too against the same specs.

Conformance harnesses

Each Tier-C spec ships with a conformance test harness (Apache 2.0). Run it against your integration to verify:

  • Subject contracts are honored.
  • Payload schemas validate.
  • SLAs are met under representative load.
  • Tenant isolation holds.
  • Priority / emergency handling fires correctly.

The harness output is the basis for integrator certification (see below). Re-running the harness against a future spec revision is the basis for conformance attestation at version bumps.

Get the conformance harnesses →

Integrator certification program

NT Connect runs an integrator certification program to give operators confidence that a third-party integration meets the contract.

  • Per-spec certification — your integration is certified against a specific Tier-C spec at a specific version.
  • Portable across tenants — once certified, your integration is recognized at any Nautilus tenant.
  • Re-certification at spec version bumps.
  • Listed in the Nautilus integrator directory with appropriate detail (vendor, certified specs, scope).

Certification covers:

  1. Conformance harness pass.
  2. Architecture review with NT Connect.
  3. Security review of the integration's auth + tenant isolation.
  4. Operational review of the integration's monitoring, logging, and incident response.

Apply for certification →

Partnership and commercial terms

NT Connect runs a partnership program for integrators who deliver Nautilus deployments at scale.

  • Co-marketing. Joint case studies, conference presence, listing in the integrator directory.
  • Joint go-to-market. NT Connect refers operators to certified integrators for in-region delivery.
  • Commission terms for integrator-led tenant introductions.
  • Early access to draft Tier-C specs ahead of public release.
  • Spec advisory seat — input into the spec evolution process.

Talk to integrator partnerships →

Where to start

  1. Read docs/integrations/README.md for the integration model overview.
  2. Read the ship-PBX spec (the first published, currently Draft v0.1) to see the spec structure in practice.
  3. Pull the conformance harness for whichever spec you're implementing against.
  4. Open a discussion on the public issue tracker for clarifying questions or proposed spec changes.
  5. Join the integrator partner program when you're ready for certification.

Browse Tier-C specs → Get the conformance harnesses → Apply for certification → Talk to integrator partnerships →