Cruise booking engine and reservation software: 8 options for 2026

TL;DR

A cruise booking engine in 2026 is three purchases, not one: the reservation core that holds cabins and fares, the trade channels that put those fares in front of travel advisors, and the API between them. We compared 8 off-the-shelf options on named cruise users, published API surface, booking depth and control. Versonix Seaware ranks first: four cruise companies were announced on it in 2026, and its OpenTravel-based API is the only one of the eight documented in public, by a cruise line that runs it.

• IBS Software's iTravelCruise is the other core with a major group signed: Royal Caribbean Group, still years from launch in June 2025.
• Traveltek is where Sabre pointed agents when it sunset Sabre Cruise on October 31, 2023.
• 63% of recent cruisers booked through a travel advisor, per CLIA's 2026 report.
• None of the eight publishes a price.

Cruise booking runs on one core and many channels

Demand is not the constraint. CLIA's 2025 Global Market Report, updated April 27, 2026, counts 37.3 million ocean cruise passengers in 2025, up 7.7% on 2024. The constraint is where they book. Per Travel Market Report, CLIA's 2026 State of the Cruise Industry report found that 63% of people who cruised in the last 12 months used a travel advisor, a share that has stayed between 60% and 66% since 2022.

So a cruise line sells the same cabin in two places at once: its own website and app, and the tools advisors already work in. Both read one inventory. Windstar Cruises, whose ships carry 150 to 350 guests, shows how fast the second list grows:

1. February 2024: UK agents on Traveltek got Windstar's GBP pricing, itineraries and ship content, without booking, per TravelMole.
2. July 23, 2024: Revelex became Windstar's first booking engine partner.
3. November 20, 2024: consumers could book on windstarcruises.com; before that, online booking was for advisors, per Seatrade Cruise News.
4. April 17, 2025: Odysseus Solutions added Windstar for its trade partners.

Four channels in 14 months, each one an integration against the same reservation core. Channels also close. Sabre sunset its Sabre Cruise tool on October 31, 2023 and recommended Traveltek's AgentConnect engine, per a Tres Technologies notice. Cruise Planners, a longstanding Sabre customer with more than 2,500 franchise owners, announced Traveltek on November 1, 2023, per Travolution.

Off-the-shelf cruise booking software therefore comes in three kinds. The reservation core a line runs. The trade platforms its fares flow into. And booking engines assembled from travel components for one operator. The eight options below cover all three.

Four cruise companies chose the same reservation core in 2026

The reservation core holds cabin inventory, fares, holds, payments and agency accounts. In 2026 one product kept winning it. Versonix announced Seaware for Mitsui Ocean Cruises on February 10. StarDream Cruises went live in May. Atlas Ocean Voyages followed on August 12, ahead of its 2028 sailing yacht. On October 22, Versonix expanded its deal with NCLH: Regent Seven Seas Cruises and Oceania Cruises will adopt Seaware, and Norwegian Cruise Line will upgrade to its latest generation.

The other big signing moves slowly. Royal Caribbean Group chose IBS Software's iTravelCruise in November 2023 to replace legacy technology. In June 2025, Vicki Freed, Senior Vice President Sales & Trade Relations, told Cruise Weekly it was still a number of years away from launching, with Silversea first.

Cores also change hands. Celestyal was the first cruise line on IBS's iTravel reservation platform in 2016 and partnered with Versonix for Seaware in 2021. UnCruise Adventures implemented iTravelCruise Enterprise Reservation in September 2023 and selected Seaware in August 2024.

Read that as an engineering brief. The core is a decision you revisit. Your booking site, your apps and your partner integrations should outlive it.

How we evaluated

Five criteria, applied to every option and visible in each card:

1. Named cruise users: a cruise line that runs the product or is bookable through it, named by the vendor or in trade press.
2. API surface: whether the message format is published, which standard it follows, and whether a reference is readable before you sign.
3. Booking depth: cabin holds, multi-cabin and group bookings, packages, payments and changes after booking.
4. Channel reach: the line's own site, travel advisors, GDS users and partners.
5. Control: what you license, what you configure and what stays yours.

Options are ranked by how much of a cruise line's booking stack each covers with named cruise evidence. The candidate set starts from the three pages that currently answer this query: GP Solutions' cruise booking page, Revelex's cruise page and Maukaa's cruise booking platform page. Maukaa is not ranked: we found no source independent of Maukaa for the cruise clients and four live integrations its page claims. We added the cores and trade platforms that trade press names as cruise reservation or distribution systems, and left out Widgety, whose Cruise API supplies content, not bookings.

Facts come from vendor pages, partner documentation and trade press opened on November 6, 2026. Mercury Development sells no off-the-shelf engine, so the custom path follows the cards instead of a ranked card. Any group in our own data with fewer than three data points is not published. The shipboard PMS and the rest of the stack are in our guide to the best cruise ship software.

The 8 options at a glance

1. Versonix Seaware

Seaware is the core with the most named cruise users in this guide, and the only option here whose booking API reference we could read before signing anything. Beyond the four 2026 deals, Lindblad Expeditions signed in 2018 partly for Seaware's OTA API to reach more channels. When Azamara signed in 2022, Seatrade Cruise News reported that Seaware had powered reservations for more than 20m passengers and 100 ships around the world each year, as one hub for OTA, GDS, B2B, B2C and contact center channels.

The API is public because a customer published it. HX, the line formerly called Hurtigruten Expeditions, runs a partner guide to the Seaware OTA API, last updated May 2026. Messages are OpenTravel XML, sent in a SOAP envelope or as plain XML to REST endpoints, with an Auth0 bearer token. The catalog runs from sailing, cabin, fare, dining and shore excursion availability to holds, booking, payment and cancellation pricing. Each partner runs in Plain OTA or Versonix OTA mode, set per partner; the second adds Versonix extensions, such as cabin unhold and premium dining, ahead of OpenTravel releases. Bookings run stateless, sessionful or stateful, and the guide recommends stateful mode for holding cabins in multi-step bookings.

Best for: a line replacing its reservation core, or a new brand that needs fares, inventory and agency channels from the first sailing. Facts: founded 1986 and based in San Jose, CA, per G2. Watch-out: you license the core and move on Versonix's release cycle, as NCL's upgrade shows, and the NCLH announcement gives no timeline. The readable reference comes from HX, not from Versonix.

2. IBS Software iTravelCruise

iTravelCruise is a cloud retail platform built around the cruise reservation. When Royal Caribbean Group signed in November 2023, Seatrade described an omni-channel platform that bundles flights, hotels and transfers and carries offers, credits and loyalty rewards in a guest wallet. Resorts World Cruises chose iTravel Cruise for its June 2022 launch, and UnCruise Adventures implemented its Enterprise Reservation system in 2023.

Best for: a cruise group that wants packaging, dynamic pricing and a guest wallet on one vendor's SaaS. Facts: founded 1997, with 4,000 professionals and 16 offices when Apax funds agreed to invest about $450m for a significant minority stake in May 2023. Watch-out: the largest signing was still years from launch in June 2025, two of its named cruise users later announced Seaware, and we found no public API reference for the platform.

3. Traveltek

Traveltek names more cruise lines on its API page than any other option here. Its Cruise API page describes REST with JSON, documentation listing JSON and XML, hold or confirmed bookings, several cabins in one transaction, card details passed to cruise lines for processing, and Postman collections. Its FAQ counts over 27 cruise suppliers and over 30,000 itineraries; its products page says over 30 suppliers. The same API page notes that cruise lines typically update their APIs about every six months, which is the maintenance you inherit if you integrate each line yourself.

Lines choose it as a channel. Disney Cruise Line named Traveltek its global technology and distribution partner in July 2023, bookable through the Cruise API and the iSell agent engine. In February 2026 Traveltek made Scenic and Emerald Cruises bookable through the same API.

Best for: a line that wants its fares in UK and North American agency tools through one connection. Facts: established 2002, headquartered in Glasgow, 90 team members, per its About page. Watch-out: it sells to agents and operators, so it adds a channel rather than a core, and its own pages disagree on the supplier count.

4. Revelex

Revelex is a Florida-based trade engine with a white label option. Per Windstar's July 2024 release, Revelex aggregates cruise inventory across 40+ major lines, and its Power Agent 5 engine gives advisors a global cruise API, web and private fares, markups and discounts through a yield management tool, and changes after booking. Its cruise page adds a white label booking engine, interactive deck plans, shore excursion and onboard dining reservations, and headless APIs for cruise search, pricing and booking with role-based access control.

Best for: a line that wants to be bookable in agency booking tools, or a seller that wants a white label cruise engine. Facts: founded 1999, per G2; headquartered in Boca Raton, FL, with an office in Southampton, UK, and used by more than 100,000 travel professionals and 10,000+ agencies, per its FAQ. Watch-out: neither its cruise page nor its API page names a data format, and the cruise page names no client.

5. Rescompany cruisePAL

cruisePAL is the reservation core for small fleets: a web-based, cloud-ready central reservation system. Its maker, Rescompany Systems, was acquired in 2021 by the Schulte Group, which also owns MariApps, and MariApps says cruisePAL was launched jointly with Rescompany and OnboarD Software. Expedition start-up Positive Polar chose it in May 2024 for bookings, changes, payments, sales invoices, commission production and agency account reconciliation. Victory Cruise Lines implemented it the same year.

Best for: an expedition, river or small-ship operator that needs reservations and agency accounting without local installs. Facts: Rescompany's CEO said in 2021 it had served the cruise market for nearly 20 years; MariApps lists 150+ clients and 300+ vessels connected across its products. Watch-out: none of the pages we read names a booking API or a consumer booking engine, so ask how your website and trade partners connect before you sign.

6. Amadeus Cruise Portal

Amadeus Cruise Portal is the GDS route to agents. Its product page offers live access to 30+ bookable and 100+ searchable cruise lines, booking data synced with the lines so prices and payment status stay current, side-by-side comparisons, interactive deck plans and four languages. At its UK and Ireland launch in March 2021 it carried more than 20 lines, river lines included, plugged into Amadeus Selling Platform Connect, came in white label versions for agencies building their own apps, and drew on a partnership with Odysseus Solutions.

Best for: a line that wants reach among agents who already work inside Amadeus. Facts: Amadeus IT Group, founded 1987 and based in Madrid, per Wikipedia. Watch-out: the page names no cruise line and no price, and it serves travel sellers, so it gives you no booking engine for your own site.

7. Odysseus Solutions

Odysseus runs a cruise booking engine for trade and consumer sellers. Crystal joined it in October 2024 and Windstar in April 2025, which its CEO, Monish Luthra, called its first foray into sailing yachts. Its G2 profile describes a hosted engine that sellers customize with their own headers, footers and style sheets, up to a full private label.

Best for: a line that wants to appear in private-label booking sites run by agencies. Facts: founded 2005 and based in Miami, per G2; a partner behind Amadeus Cruise Portal's 2021 launch. Watch-out: no line count, no public API reference, and the G2 page lists an air booking engine rather than the cruise product.

8. GP Solutions

GP Solutions assembles booking engines from travel components and adapts them per operator. Its Cruise Booking Software page, last modified October 16, 2026, lists real-time availability, allotment tracking, rule-based cabin assignment, group, multi-itinerary and shared-cabin bookings, scheduling of onboard facilities and combined payment types, sold through websites, OTAs, partners and kiosks. The maritime proof is Tallink, a Baltic cruise and ferry operator: a single-page booking flow, add-ons, self-service changes and a loyalty program inside the booking system, over 50,000 man-hours on Java, Objective-C, AngularJS and React.

Best for: a ferry or small cruise operator that wants a configurable engine and a team to adapt it. Facts: founded 2002, headquartered in Unterschleissheim, Germany, Clutch 4.9 on 24 reviews, $50,000+ minimum; Amadeus Certified Partner and Sabre Developer Partner, per its About page. Watch-out: the cruise page names no cruise line and no API format, and the Tallink result it reports, a 1.4% sales increase, is not attributed to the project alone.

Which option fits your cruise line

Start with the layer you are buying. A core is a multi-year commitment; a trade channel is a contract you can add or drop.

When a custom booking layer beats the products

Custom wins at the joints no product owns. Three cases cover most of it.

1. The core changes under you. Celestyal and UnCruise each signed for a second core within a few years, and NCL is moving to a new Seaware generation. A booking site written against one vendor's messages gets rewritten when the messages change.
2. Every channel is one more integration. Windstar added four in 14 months, all selling the same cabins.
3. The booking crosses into other companies' systems. A spa treatment or a dining table is sold by a partner, priced by two companies and served on a ship.

That is the work Mercury Development has done. For OneSpaWorld, which describes itself as the operator of health and wellness centers onboard cruise ships and which Mercury's portfolio index lists as a client, Mercury built the onboard spa platform: ReactJS web applications on ship servers with no external internet, run on Android tablets in kiosk mode, covering treatment booking and a checkout that prices with discounts from both OneSpaWorld and the cruise lines. Middleware connects it to OneSpaWorld's ship-side backend, its shore data exchange and each cruise line's API, from one codebase rather than a branch per line, with RabbitMQ and Shovel carrying messages between ship and shore. It has been in production since 2018 on over 160 ships operated by multiple cruise lines. Around it, Mercury built a pre-booking site so Windstar guests book treatments online instead of through OneSpaWorld's call center, and a calendar widget that cruise lines embed on their own websites.

For cruise line clients Mercury cannot name under NDA, it has built React Native food and beverage apps, dining host tools for reservations and check-in, and backend components that aggregate data and functions from dozens of legacy microservices behind new middleware for passenger apps. That middleware is the pattern this guide recommends: one API the apps talk to, whatever sits behind it. The same failures repeat across these programs. A login token issued on shore stops working on the ship's network. An API works in production and not in the test environment. Some behavior shows up only on a real vessel.

Custom has a price: discovery, an interface per system, a test plan on a real ship and maintenance after launch. If a product above covers your case, buy it. If not, Mercury Development has built software since 1999, with 500+ engineers, more than 1,500 completed projects and more than 40 million users of its applications. It builds to WCAG 2 AA and ADA requirements, and all work is work-for-hire, so the customer owns the code and all underlying IP. The OneSpaWorld program has no public case page, so the reference comes through a call. For a development partner rather than a product, see our ranking of cruise line software development companies.

What we counted on ranking pages and API documentation

Two counts, both on November 6, 2026.

First, the three pages that answer this query: GP Solutions, Revelex and Maukaa.

• 0 of 3 name an API data format or the OpenTravel standard.
• 0 of 3 mention cabin holds, offline use or the ship's connection.
• 0 of 3 mention accessibility. 1 of 3 mentions PCI DSS.
• 1 of 3 names a cruise line client in its text.
• The one that links its API documentation serves it from a bare IP address over plain HTTP.
• They carry 3, 0 and 8 FAQ questions.

Second, the eight options, on the pages cited in their cards.

• 6 of 8 have a cruise line named as a user or as bookable through them. GP Solutions names Tallink, a cruise and ferry operator; Amadeus's page names none.
• 2 of 8 state the format of their API: Seaware, through HX's guide, and Traveltek.
• 1 of 8 has an API reference we could read without an account: Seaware's, published by HX.
• 2 of 8 document cabin holds: Seaware and Traveltek.
• 0 of 8 publish a price.

Read the second and third lines together. The API you will integrate against is documented for partners under contract, and the one public reference exists because a cruise line chose to publish it. Ask for the reference, the test environment and the release notes before you ask for a demo.

Put your own API in front of the reservation core

Opinion, with the mechanism. Buy the core and the trade channels, then put one API of your own between the core and everything you build. The vendor's messages become an implementation detail.

1. Model holds, not only bookings. In stateless mode each Seaware call stands alone and inventory is held only by an explicit cabin hold, so a multi-step checkout that skips it can lose the cabin between steps. Expose a hold with an expiry the front end can show.
2. Pin the dialect. Plain OTA and Versonix OTA differ by extensions, set per partner. Version your API so a dialect change is a deploy behind it, not a rewrite of your apps.
3. Test every release. Traveltek says cruise lines update their APIs about every six months, and HX lists staging and development endpoints next to production. Run contract tests against staging each time.
4. Keep credentials on the server. The Seaware API takes an Auth0 bearer token; it belongs in your backend, never in a browser or an app bundle. Give apps their own session and test it after the guest's phone joins the ship's network.
5. Keep card entry in the payment provider's frame. On January 30, 2025, the PCI Security Standards Council removed requirements 6.4.3 and 11.6.1 from SAQ A and added a criterion: the merchant must confirm its site is not susceptible to attacks from scripts that could affect its e-commerce systems. Tracking tags on a booking page make that harder to confirm.
6. Build accessibility in. Since 28 June 2025, Directive (EU) 2019/882 has applied to e-commerce services and to the websites, apps and electronic ticketing of waterborne passenger transport, which covers cruises that embark in an EU port under Regulation (EU) No 1177/2010.

A team that has built this answers with a design. A team that has not answers with a demo.

Written by Alexey Rodionov, Lead Front-end Developer at Mercury Development since 2020. Alexey is a Google Developer Expert in Web Technologies and a Chromium contributor whose code ships in Chrome DevTools, Google's Bubblewrap and Microsoft PWABuilder. The architecture records and API documentation review behind this article's technical comparisons come from the front-end practice he leads.

Choosing a core or a trade channel? Start with an integration map

Many booking projects pick a product before anyone maps which system owns the fare, the hold and the guest record. Send us your reservation core, the channels you sell through and the apps and partners that book against it. We will show what to license, what to connect and where an API of your own pays off.