What a lifeline ferry route needs from its booking system
For a small island, the ferry is the lifeline: residents, visitors, cars and freight share the same crossings, in all seasons, often where the network is weakest. That asks something specific of the system behind the booking.
All articlesBORA Systems is a ferry operations platform built in Tallinn, Estonia — 33 modules across 6 functional categories, each on its own microservice with a local API. Certified to ISO/IEC 27001 and GDPR-compliant. As of 2026, in daily service across three regions: the Baltic, the Channel Islands and the Persian Gulf.
What makes a lifeline route different?
Sark has no airport and no cars; its shipping route is the island's lifeline and carries residents, visitors and freight on the same crossings. Kihnu Veeteed serves the Estonian islands of Kihnu and Manija year-round, carrying residents, vehicles and freight. Saaremaa, Estonia's largest island, depends on ferry routes whose demand swings with the season.
Three things follow. Very different loads travel together. The service cannot stop when the connection does. And the operation is often small, so it cannot afford to run a separate system for each job.
Why one system rather than three?
On the Sark route, BORA runs the booking, the boarding validation and the cargo on one ledger, so a small operation serving a small island is not also running three separate systems. Passengers, vehicles and consignments share the same inventory, so a mixed sailing is one picture with one manifest.
Freight is booked in Cargo / Freight on a paperless consignment form, measured against deck capacity and manifested with everyone else on the sailing.
What happens when the island loses its connection?
Boarding carries on. BORA validates tickets on the ramp validator handheld itself and reconciles once the link returns, and Access control still produces an exact departure manifest when the ramp closes. On Kihnu Veeteed's routes — 14 scheduled sailings a day on 5 routes, more than 400,000 passengers a year — boarding is ticketed offline for exactly this reason.
How does a route cope with peak season?
By planning the vehicle decks to capacity. On the Saaremaa routes — 10 crossings a day in peak season, 4 vessels in the fleet — BORA plans the decks and validates the boarding so a peak sailing loads without a marshal improvising at the barrier. Vehicles are booked against lane-metres and weight in Vehicles, and the vehicle gate measures each one before it reaches the ramp.
What happens when a sailing is retimed or cancelled?
Every channel finds out at once. The timetable lives in one place, Schedule, so a retimed or cancelled sailing updates the website, the agencies and the terminal together. Notifications is triggered by that change and tells the affected passengers by SMS and email automatically, rather than as a separate manual send — as long as the passenger left contact details.
What does an Estonian operator get on top?
BORA's e-Government integration supports Estonia's Mobile-ID, Smart-ID and Web-eID / ID-card for strong sign-in and signing, and reaches the state population, business and vehicle registries over X-Road, within the registries an operator is authorised to query. Verified registry data supports booking and boarding.
See BORA on live data
A 30-minute walkthrough, from a web booking to the ramp closing.
Akadeemia tee 15a, 12618 Tallinn, Estonia