Travel · Marketplace · Europe

Making releases safe for a European transfer-booking platform

A booking platform for airport and city transfers depended on a geo-search service nobody could safely change. We containerised it, built a deploy pipeline with automatic checks and one-step rollback, added end-to-end tests for the booking flows, and cut its paid map-API usage.

place records served
~15M
fewer paid map-API calls (measured)
~47%
end-to-end flows tested on every change
12
rollback in production
1 step

The challenge

The company runs a marketplace where travellers compare and book taxi and private-driver transfers across Europe, in several languages, with card payments secured by 3-D Secure and a dashboard for transport providers. Every search depends on a geo service that turns what a traveller types into a precise pickup point.

That geo service was business-critical and fragile. It served a gazetteer of around fifteen million places, but it had no reproducible build, deploys were manual, and a bad release could break search for every customer. At the same time, each lookup that fell through to a paid map API added to a growing monthly bill, and there was no automated way to check that bookings and payments still worked after a change.

What we did

Results

Stack

Docker · GitHub Actions · GitHub Container Registry · Node.js · PostgreSQL 17 · Valkey · Playwright · Sentry · Jira · BigQuery

In their words

The infrastructure LL Cloud built handles millions of requests daily with remarkable reliability. Their team operates as a true extension of ours — responsive, proactive and technically excellent.

— CEO, European transfer-booking platform

Services

Tell us what you need