Booking and itinerary platforms
Search, hold, book and change, with the state of every booking kept in one place.
Booking platforms that stay up when the sale opens, with the supplier integrations and records that package travel rules put on the organiser. We have shipped a platform for 30,000 concurrent users in a month.
Under the UK package travel rules the organiser answers for the travel services in the package even when a supplier performs them. That makes supplier data, booking state and payments a compliance record as well as a sales funnel.
a platform for 30,000+ concurrent users, delivered in one month on microservices and AWS Kinesis
We have no published travel case. We say so on the first call and show the closest work.
Search, hold, book and change, with the state of every booking kept in one place.
Flights, hotels and transfers feeding the same booking, with failures handled.
Deposits, balance and refund flows that show what is owed and why.
Microservices and event streaming for sale days and campaign spikes.
Itineraries and changes in the hand, readable offline.
Bookings, cancellations and money held, so the protection figure is known.
These come from government guidance on the Package Travel and Linked Travel Arrangements Regulations 2018.

Different sector, same load: a platform connecting thousands of users that had to support 30,000+ concurrent users with one month for the first phase. We delivered on microservices and AWS Kinesis, with .NET and Angular.
Where liability and protection depend on the booking record.
Many suppliers, one customer, and a sale that opens at a set hour.
Distribution to many channels with availability that changes by the minute.
Product teams that need a senior build team for a launch.
Related reading: on-demand app software, aviation software and ecommerce software.
Not yet published. We say so on the first call and show the closest work, which is a high-concurrency platform delivered in a month.
Usually, through the supplier API. Tell us which ones and we will say what we have to confirm.
No. That advice comes from your lawyers and the CAA. We build the records and controls they specify.
You do, from the first commit. Repositories and cloud accounts stay in your name.
Thirty minutes with the engineers on expected traffic, your suppliers and what the booking record has to prove.