Aboard.
Guest experience platform for small-ship cruising.
The problem.
Cruise lines run on a fragmented stack — printed daily agendas, separate guest portals, separate crew operational tools. None of them share a data model. Guests get a clunky experience; crew get duplicate workflows.
Why we built it.
Because the cruise industry has spent a decade buying parts that don’t fit together. We built one platform with two surfaces: a concierge-grade guest app and a role-scoped crew portal, both writing to the same underlying data. Shape it with the cruise rhythm — port days, sea days, embarkation, all-aboard.
Who uses it.
Cruise line management. Guests and crew aboard. Live demo available.
What makes it different.
One data model, two surfaces
Guest app and crew portal write to the same entities.
Built for cruise rhythm
Not generic hospitality software. Shaped by port days, sea days, embarkation, all-aboard.
Role-scoped crew operations
Dining edits menus, excursions edits capacity, every action audit-logged.