Frequently asked questions

Cruise lines and maritime operators running certification-heavy workforces across multiple vessels.

Multi-ship, multi-location, certification-heavy operations are the default rather than something you configure.

Yes. CruiseControl supports offline-capable workflows onboard, syncing records, training, and compliance data with shore once connectivity is available.

Shore teams access CruiseControl through the web application, while shipboard users work through vessel deployments that stay in sync with the central environment.

Yes. It is multi-tenant by design, so each cruise line runs on isolated data over one shared core, with multi-ship, multi-location operations and offline-capable shipboard use as the default rather than edge cases.

Smart triggers cross-reference data across the platform.

The platform supports role-based training, SCORM/xAPI content, assessments, certifications, and mandatory drills, with full tracking and reporting.

A single platform admin can manage up to 5,000 crew members, because the system does the coordinating through automated workflows rather than manual effort.

Yes. Multi-ship, multi-location, certification-heavy operations are the default.

It maintains audit-ready records, certification and expiry tracking, role-based access controls, and traceable operational history across the fleet.

CruiseControl is multi-tenant by design: each cruise line operates on its own branded subdomain with isolated data, while sharing one continuously improving core platform.

Each suits a different job.

Through SCIM directory provisioning, so accounts are created and retired automatically from your identity provider.

No. Employee records stay aligned with your HRIS as the system of record instead of being maintained twice, and assignment and time data flows to payroll rather than being re-keyed each cycle.

Customers receive ongoing support, adoption tracking, and continuous-improvement guidance aligned to their operational model.

Someone who knows how rotations are really planned, someone who owns the compliance regime, and someone who can speak for the systems we connect to.

No. Every module runs on one shared platform under a single subscription, so starting with a few and adding more later is a configuration decision rather than a new procurement.

The recurring coordination, alerts, onboarding steps, and follow-ups, run automatically through smart triggers once configured.

Yes. Book a walkthrough and we will map CruiseControl to the exact problems your team is facing, using your scenarios instead of these examples.

Continuously, rather than in annual releases.

No. Improvements arrive continuously with ongoing monitoring rather than as disruptive migrations, so the platform keeps changing without turning every upgrade into a project.

No. Every module runs on one shared platform under a single subscription, so recruiting, training, documents, compliance, and communication are all included, not stitched together from separate contracts.

No. The calculator gives an illustrative projection from your inputs and public 2026 market benchmarks.

Yes. At larger fleet sizes you get custom volume pricing, white-label deployment, an onboarding and development credit, and enterprise controls like SSO/SCIM, an SLA, and a dedicated success manager.

Every rollout includes structured onboarding; enterprise plans include a development credit toward integration and migration.