JetSetGo vs FerryHawk — A Side-by-Side for Vehicle Ferry Operators

This comparison is for vehicle ferry operators evaluating their booking platform options — operators running RoRo or RoPax vessels with vehicle decks, mixed passenger and freight capacity, and the day-to-day complexity of loading vehicles by lane metre, tonnage, height, and class.

FerryHawk is a vehicle-ferry-vertical platform built by a ferry-operating family. "Built by ferry operators, for ferry operators" is their positioning, and the platform is focused tightly on the vehicle ferry segment.

JetSetGo is built by transport operators tackling real-life messiness — vehicle inventory and passengers and packaged accommodation and walk-up sales and OTA channels and yield management, all on one platform. Ferry is one of several product types JetSetGo handles natively — with a vehicle deck model and operational tooling built for serious ferry operations. If your operation is ferry-only and you want a single-purpose tool, FerryHawk's narrow scope is the proposition. For multi-modal operators — those who run a ferry as one leg in a larger operation alongside tours, accommodation, or transfers — JetSetGo is the only one of the two designed for that work.

Both platforms cover the basics of vehicle ferry booking — passengers, vehicles, schedules, transactions. The differences sit in vehicle deck modelling depth, pricing-engine breadth, channel rules, multi-product packaging, and the operational tooling around walk-up sales and audit reporting.

At a glance

Where each fits best

FerryHawk is a strong fit when

You run a vehicle ferry operation, want a single-purpose tool focused tightly on the ferry, and don't plan to package the ferry alongside other product types. The team behind FerryHawk are ferry operators themselves, and the platform is built around the vehicle ferry and the direct-booking model. Their customer base includes government-contracted operators and family-owned ferry businesses across multiple regions.

JetSetGo is a strong fit when

• The operation runs more than just a ferry, or you want one platform managing the whole operation — ferry plus accommodation, ferry plus day tours, ferry plus packaged experiences sold as one bookable thing.
• Packaged product across product types — ferry leg plus destination tour plus overnight stay plus return ferry sold as one transaction, with cross-leg availability and one confirmation.
• Multi-dimensional inventory with operator-defined classifications across the dimensions — lane metres, tonnage, height, hazmat, EV-charging, towed trailers — rather than a fixed set of vehicle types.
• Complex pricing, yield, and revenue management goals — per-channel tiers, peak/off-peak versioning, dynamic surcharges, sector-based fares across multi-stop routes, consumption-based vehicle pricing on the same operation.
• Walk-up at the wharf alongside advance bookings online and OTA traffic, all drawing from one shared inventory pool.
• Channel rules for OTA capacity and freight allocation that aren't part of a direct-booking-only model.
• Council-contract or government-contract audit requirements that need probity-grade reporting.
• Ferry-only today but trending toward multi-product or multi-modal.

Both platforms cover the basics of vehicle ferry booking. The decision turns on scope (just the ferry, or the whole operation) and on depth — vehicle deck modelling, pricing-engine breadth, channel rules, walk-up tooling, audit reporting. For multi-modal ferry operators, there is no real contest — JetSetGo is the only one of the two designed to bundle the ferry into a wider package.

Vehicle deck modelling

Vehicle deck depth is what an operator should compare hardest between any two ferry platforms — it is where capacity is won or lost.

FerryHawk's vehicle deck handling is built around AI-assisted vehicle placement, weight-based pricing, deck capacity monitoring, and smart lane assignment — the standard set of vehicle-ferry features.

JetSetGo models the vehicle deck as a serious inventory problem rather than a flat space count. The model is hierarchical — a vessel breaks into decks, decks into areas, areas into bookable units — with each level enforcing its own constraints automatically. Lane metres are the typical unit of capacity. Tonnage runs as a separate dimension on weight-rated decks (a truck consumes both lane metres and tonnage; a car consumes lane metres only). Height limits enforce per-deck (no 4-metre van on the under-cover deck regardless of lane-metre availability). Hazmat class is a per-deck acceptance rule with declaration capture at booking. EV-spaces track independently from regular car spaces for routes with charging-equipped berths or insurance restrictions. Vehicle-class restrictions ("motorbikes never on the open-truck deck") are enforced structurally. The configuration is operator-driven — operators who run weight-rated decks turn tonnage on, operators with no overhead constraints leave height off, the dimensions that don't apply to your operation simply aren't part of your model.

The vehicle catalogue covers make, model, year, and body type, so a customer gets accurate dimensions automatically rather than guessing. Trucks, buses, and custom builds outside the catalogue go into a per-operator list. Attachments — bullbars, roof racks, kayaks — extend the parent vehicle's dimensions.

Towed vehicles and trailers are worth comparing carefully. JetSetGo treats a car towing a caravan as two linked entities — the platform knows they belong together, they sail on one ticket but each is recorded for reporting and each consumes its own lane metres. A B-double truck with two trailers is three linked entities. The rules that apply to combinations (limited manoeuvrability into tight loading lanes, length-plus-trailer caps, separate hazmat declarations for the towed unit) are enforced by the platform.

Multi-product packaging

This is where the scope difference between the two platforms shows most clearly. FerryHawk is built around the vehicle ferry. Operators who run ferry plus tours typically book each product separately. Tours can be added as a module, but the bundling sits across separate bookings rather than as a single package with cross-product dependency rules.

JetSetGo's package builder bundles different product types into one booking. A ferry crossing plus a tour at the destination plus an overnight stay plus return transport sells as one transaction. The package has an anchor leg (the customer selects the ferry first) and choices for the rest (which tour, which accommodation tier), with dependency rules across the legs. If any leg is unavailable, the package is unavailable. The customer gets one confirmation, one invoice. The platform knows the legs belong together (booked together, refunded together) and tracks them separately for reporting and for rules specific to the combination.

If your operation is ferry-only and you don't sell bundled experiences across product types, this difference matters less. For operators running a ferry alongside other product types, JetSetGo is the only one of the two designed for multi-modal package selling — FerryHawk's scope ends at the ferry.

Channel control and revenue management

FerryHawk's customer base leans toward operators who sell mostly direct. Their feature set reflects that — the OTA story is lighter compared to the direct-booking depth, which suits the segment they serve.

JetSetGo connects to whatever OTAs the operator's customers use and adds an operator-first channel-rule layer on top. Combined with the configurable pricing engine, this is a revenue-management layer. Operators set rules like:

• OTAs get a maximum of 40% of passenger capacity on this sailing.
• Reserve 10% of the vehicle deck for direct bookings; release 24 hours out if unsold.
• Hold a freight allocation across every sailing for trade-account customers.
• Premium-tier inventory stays direct-only; OTAs sell the standard tier.

The intent is not to displace OTAs — operators keep them as marketing channels while the rules shift the revenue mix toward direct over time. If your operation is mostly direct, this matters less. If a meaningful share comes through OTAs and you want to shape that mix without dropping the channels, JetSetGo's channel-rule layer combined with the pricing engine is worth showing in a demo.

Walk-up at the wharf

Most vehicle ferry operations take some walk-up traffic — even highly-booked services have last-minute drivers showing up at the wharf hoping for a spot.

JetSetGo runs walk-up and advance booking from one shared vehicle deck inventory pool. The kiosk at the wharf, the website on the customer's phone, the agent portal in the office, and the mobile POS on the deck supervisor's tablet all draw from one inventory record. A walk-up vehicle sold at the kiosk shows on the deck supervisor's tablet the moment the card clears. A no-show triggers re-allocation. A vehicle that arrives as a different class than booked updates the lane-metre count immediately.

Kiosk POS uses Stripe Terminal for card payments. Concession recognition runs at the till — a verified resident or pensioner card pulls up the right tariff in real time. QR scanning at the gangway cryptographically validates each ticket. The customer database builds itself with every transaction. Weather and tide cancellation comms go out automatically. Ticketed non-scheduled product — multi-trip tickets, season tickets, residents' commuter passes — is handled natively with validation tracking per use.

These capabilities work whether or not advance booking is enabled. A wholly walk-up vehicle ferry still gets full lane-metre tracking, QR tickets, live manifest, customer database, weather comms, and audit reporting. FerryHawk offers QR boarding passes and operates at the wharf at its customer sites — the depth of walk-up tooling, particularly around manifest sync, offline mode, ticketed pass product, and audit trail at the wharf, is worth comparing against your specific operation.

Audit reporting

Council-contract and government-contract vehicle ferry operators need audit-grade reporting that holds up to outside review.

JetSetGo logs every ticket, payment, modification, refund, concession-card lookup, and boarding scan with timestamp, vessel, skipper attribution, and payment-trail attribution. The audit trail satisfies operators where probity-grade reporting is a contract condition. Council operators use it as their primary reporting tool to the contract manager.

FerryHawk provides transaction reporting standard to ferry platforms and is deployed at operators with government contracts. Whether the depth satisfies your specific contract depends on the contract; ask both platforms to walk the audit fields against the contract's requirements.

Pricing engine

Both platforms run dynamic pricing — seasonality, demand, vehicle-weight inputs are well-trodden territory. The question is breadth.

JetSetGo's pricing is set per service, per route, per season, per channel, and per fare or vehicle type — flat, consumption-based, attribute-based, or any combination:

• Flat — fixed rate per fare or vehicle type.
• Consumption-based — priced by what's actually used. A car by lane metres on a long route. A truck by lane metres and tonnage together. A cabin by berth count. Freight by tonnage.
• Per-sector — multi-leg journeys priced per route sector boarded.
• Per-night — accommodated multi-day services priced per night.
• Per-package — bundled experiences priced as a package, with revenue allocated to each component for reporting.
• Versioned price lists with peak, off-peak, and shoulder tiers switching automatically by date.
• Visual rules engine — early-bird discounts, weekend surcharges above a capacity threshold, resident concessions on a verified card, hazmat surcharges, trade-account pricing for repeat freight customers, channel-specific tiers, dynamic surge above capacity thresholds.

A single operation can run flat pricing on the passenger fare, consumption pricing on the vehicle deck, per-night pricing on a multi-day package, and dynamic peak/off-peak tiers across all of it — in one booking flow, with one price the customer sees. This is a revenue-management engine, not a price-card configurator.

FerryHawk's pricing engine — seasonality, demand, vehicle weight — covers the ferry-route fundamentals. If your pricing is primarily vehicle-weight-and-seasonality driven on a single route, both platforms handle it. If your pricing crosses pricing types — flat for some entities, consumption-based for others, per-night for cabins, peak tiers across all of it, packaged-product pricing layered on top — that's the breadth JetSetGo's engine is built for.

Migration considerations

If you're on FerryHawk today and it's serving your operation well, switching has a cost — change-management, data migration, retraining at the kiosk, customer-database re-import.

The reasons operators look at switching tend to fall in a few categories: they've added a product type that doesn't sit alongside the ferry cleanly (accommodation, day tours, transfer buses); they want one platform managing the whole operation; they want channel rules for OTA capacity; they want a package builder for multi-product bundling; they want pricing-engine breadth beyond vehicle-weight-and-seasonality.

If your operation is ferry-only and FerryHawk fits the daily work, the case for switching is weaker. If your operation is genuinely multi-product, or trending that way, the case for one platform across all of it is worth evaluating. JetSetGo includes onboarding, the configuration is operator-driven, and most operators are live within weeks. Your data is yours to export at any time, in full, no lockout.

Frequently asked

FerryHawk is built by ferry operators. JetSetGo says the same. What's the difference? Both platforms are built by people with operating-side experience. The difference is scope. FerryHawk's operators are ferry operators specifically. JetSetGo's operators have run ferries, tours, buses, and accommodation across multiple business models. If your operation is ferry-only, FerryHawk's narrowness is a feature. If multi-product, JetSetGo's breadth is a feature.

We run a ferry plus a separate accommodation booking. Why would I bring them onto one platform? Operators with both products today often run them as separate systems and stitch the customer experience together with manual workflow. A single platform with package bundling lets the ferry crossing plus the accommodation night sell as one booking with shared inventory awareness. Whether that matters depends on how much of your booking volume is people doing both.

Does JetSetGo handle hazmat and dangerous goods? Yes. Hazmat class is modelled at the vehicle level and acceptance rules are configured per deck — restrict specific classes to specific decks, exclude classes entirely, apply surcharges. The booking flow asks the right declaration question and deck allocation respects the class restriction structurally. Both platforms handle this; differences in configuration depth are best assessed in a demo.

Can drivers walk up at the wharf without booking? Yes. Kiosk POS is a core capability. An operator can run a wholly walk-up vehicle ferry with no advance booking and still get full lane-metre tracking, QR tickets, live manifest, customer database, weather comms, and audit reporting. If advance booking is enabled, the kiosk and the website share inventory automatically.

Does JetSetGo fit small ferry operations as well as larger ones? Yes. The configuration adapts to scale. A short-route community ferry can run pure walk-up with kiosk POS, QR scanning, and customer database — the same platform a multi-vessel passenger ferry uses for full peak-season channel management. Operators turn on the capabilities they need and leave the rest off.

Does my data come with me if I switch? Yes. Customer database, booking history, and product catalogue come with you on switch-in. Exportable at any time, in full, no lockout.

See if it fits

A 30-minute call. We show you the platform with your routes, your fleet, your numbers. No slideshow, no pressure — just whether JetSetGo fits your operation.

Book a demo →

See also: vehicle ferry software (deeper detail on lane metres, tonnage, hazmat, and trailers), ferry booking system (passenger and vehicle ferries on one platform), multi-modal booking platform (transport plus tour plus accommodation as one operation), tour operator software (the sister pillar for the touring side of your business).