01
Sales
One booking flow across a passenger website, a dedicated agency interface, and onboard sales.
- Home
- Modules
Modules, by function
BORA is built as separate services rather than one application. Each module runs on its own service with a local API, so a ferry transportation service adopts what it needs and connects the rest to systems it already runs.
BORA Systems is a ferry operations platform of roughly 33 modules across 6 functional categories — booking, capacity, revenue, customer, reporting and platform. Each module runs on its own microservice and exposes a local API over REST and GraphQL, so an operator adopts the modules it needs and connects the rest to systems it already runs.
Built in Tallinn, Estonia and in daily service as of 2026 across the Baltic, the Channel Islands and the Persian Gulf, BORA is certified to ISO/IEC 27001 and GDPR-compliant, and its Access control module is built to the ISPS Code. Deployment is the operator's choice: cloud or on-premise.
Sales & service channels
Online Booking
passenger website
Consignment Form
cargo booking (paperless)
Back-Office & Agency
staff / agents
Cash Desk (Till)
point of sale
Check-in
boarding / scanning
Admin Tool
configuration & reports
API Gateway
BORA application modules
Reservations & Bookings
Schedule
Routes & Sailings
Inventory & Capacity
Pricing & Fares
Payments
Cargo / Freight
Customers & Agents
Check-in
Documents
Notifications
Reporting
Admin & Configuration
Add-ons
Data & integrations
Database
bookings, cargo, customers, config
Data Warehouse
reporting & analytics
Payment Gateway
online & card / till
Accounting
Xero (or alternative)
Cloud hosting
UK / EEA region
What's shown here
These are the 33 modules BORA can deploy today, grouped into six functional groups. A further set of modules is either built for a specific operator or still in development, and isn't listed here.
Booking
How a ticket gets sold, across every channel it can be sold through.
02
Schedule
Timetables and sailings by route and season — the source every booking is sold against.
03
Reservation
The central booking engine — create, change, cancel, refund and invoice, from any channel.
04
GDS
Distribution into maps, travel apps and third-party booking platforms — one connection covers every channel.
05
Routes & Sailings
Routes, legs and individual sailings, with the rules that govern each crossing.
06
Product catalog
Products — routes, legs, sailing packages and the channels each is sold through.
07
Check-in
The boarding flow at the ramp and gate — the passenger side of validation.
Capacity
What the fleet can carry — vessels, decks, weight and boarding limits, described once and used everywhere.
08
Inventory
Ships, passenger and car decks, weight capacity and boarding limits, described once per vessel.
09
Vessels
Vessel master data — decks, cabins, berths and configurations, described once.
10
Vehicles
Car-deck capacity — lane-metres, weight and slots, so a full deck is genuinely full.
11
Cargo / Freight
Consignments and freight units, with paperless consignment forms, priced and manifested like any other load.
12
Additional services
Extras sold with a crossing — cabins, meals, lounge, pets — each with its own capacity.
13
Catalog
Shared reference data — attributes, languages, nationalities and age categories.
Revenue
What things cost, and how the money settles once they are sold.
14
Dynamic pricing
Rates for deck spaces, cabins and services by route, date, season and vehicle class.
15
Car-deck pricing
Vehicle fares by class, length and route, against the lane-metres a vehicle consumes.
16
Payment gateway
Online banking, cash, Apple Pay, Google Pay and agency tickets, settled into one ledger.
17
Ledger
Double-entry accounting — an immutable journal, with customer and credit accounts.
18
Loyalty
The loyalty programme and credit contracts, applied automatically at the point of sale.
19
Cash desks
Tills and cashier shifts at the terminal, settling into the same ledger as every sale.
Customer
The passenger and agency records, and everything sent to them.
20
Customers & Agents
Passenger and agency records — the relationships and terms behind every booking.
21
Documents
Tickets, confirmations, manifests and emails generated from every sale.
22
Notifications
Messengers, SMS and emails to passengers and agents across the journey.
23
Passenger website
The modern, multi-brand ticket storefront where passengers book directly.
24
Agency portal
The dedicated interface travel agencies book through, with their own terms and credit.
Reporting
What actually happened, drawn from live operations rather than exported and merged by hand.
25
C-level dashboard
Manager selected KPI's for company financials, used capacity and B2B sales.
26
Reporting
Passenger volumes, vehicle counts and revenue by route and season, from live operations.
27
Audit log
An immutable record of actions across the platform — who did what, when.
Platform
The parts every other module leans on — access, security and the shared spine of the system.
28
Back-office & Configuration
The operator's own controls — how the whole system is set up and tuned.
29
Access control
Boarding validation and onboard security, built to the ISPS code and fully offline-capable.
30
e-Government integration
National ID-card sign-in and signing. A secure link to state registries — population, business and vehicle.
31
Login & roles
Authentication, users, roles and permissions, checked by every module and business process.
32
Scheduler
Background and periodic jobs per operator — reminders, reconciliations, exports.
33
Add-ons
Optional modules that extend the core for a specific operator's needs.
Categories at a glance
Six functional groups, 33 modules available to deploy today.
| Category | What it covers | Modules |
|---|---|---|
| Booking | Selling and distributing sailings across every channel | Sales, Schedule, Reservation, GDS, Routes & Sailings, Product catalog, Check-in |
| Capacity | What the fleet can carry — vessels, decks, weight and boarding limits | Inventory, Vessels, Vehicles, Cargo / Freight, Additional services, Catalog |
| Revenue | What things cost, and how the money settles once they are sold | Dynamic pricing, Car-deck pricing, Payment gateway, Ledger, Loyalty, Cash desks |
| Customer | The passenger and agency relationship, and everything sent to them | Customers & Agents, Documents, Notifications, Passenger website, Agency portal |
| Reporting | What actually happened — volumes, revenue and an audit trail from live operations | C-level dashboard, Reporting, Audit log |
| Platform | Access, identity, integrations and the shared spine every module leans on | Back-office & Configuration, Access control, e-Government integration, Login & roles, Scheduler, Add-ons |
Frequently asked questions
How many modules does BORA have?
Roughly 33 modules across 6 functional categories. An operator adopts the modules it needs and connects the rest to systems it already runs.
How does BORA Systems connect to other software?
Every module exposes a local API over REST and GraphQL, so an operator's website, CRM, ERP or revenue tools can read and write the same data the interface uses.
Can BORA be deployed on-premise?
Yes. Deployment is the operator's choice — cloud or on-premise — and where a line runs on-premise, no passenger data leaves its own infrastructure.
How many modules can we actually deploy?
35 today, grouped into six functional groups (Booking, Capacity, Revenue, Customer, Reporting, Platform). A further set of modules is built for specific operators or still in development, and isn't listed here.