Y Marine OS
Platform Architecture

The Yacht Master Record
is the Source of Truth

Every domain in Y Marine OS connects to one canonical Yacht entity. Operational data is never duplicated across systems — it is unified into a single master record with permissioned views for every role.

Yacht Master Record
Single Operational Source of Truth
Technical
Maintenance
Journeys
Fuel
Crew
Charter
Guests
APA
Compliance
Documents
Listings
Xperio3D
Intelligence

External systems — including Xperio3D — connect through the Extension Gateway. They never replace the Yacht Master Record. They project and extend it.

How Domains Connect

1. Canonical Entity

One Yacht Record

Every yacht has one canonical record with specifications, identity, and configuration. All other domains reference this record by ID — never by name.

2. Domain Modules

Connected, Not Duplicated

Technical, maintenance, charter, crew, and intelligence modules each store their own data but always link back to the canonical yacht. No silos. No drift.

3. Permissioned Views

Role-Based Projections

The same master record is projected differently to owners, captains, engineers, charter managers, and resellers. Each sees only what their role and entitlements permit.

Want to see the architecture in action?

See how Y Marine OS brings every system — technical, charter, crew, and intelligence — into one source of truth.

We use cookies for essential functionality and optional analytics.