Ovago + 30-brand booking platform
A consumer OTA that is also the public face of a shared engine: Hop2, ScholarTrip, Wowfare, GTT, Healthcarefares and more are configurations, not 30 codebases.
Problem
Travel brands wanted distinct storefronts without forking search, GDS, checkout and cabinet. Peak search traffic must not break paid reservations.
Stack
PHP, Yii2, MySQL, Redis, GDS (Sabre, Amadeus/NDC, Galileo, Worldspan), Stripe, Cover Genius, AWS S3, multi-tenant OTA.
Architecture
- One Yii2 hybrid booking core powering 30+ white-label OTAs
- Flight search and checkout wired to GDS plus an internal Search API
- Payments and ancillaries: Stripe, cards, pay-later, travel insurance upsells
- Traveler cabinet, hotels, help/about and locales without engine forks
- Backoffice PNR/ticketing, CRM (Twilio/live chat) and Redis/queues under load
Result
Sister brands ship as configurations. Integrono's role was platform engineering on the shared core: the pattern buyers need when they ask for a travel or multi-tenant product, not a one-off brochure site.
Bezpłatna rozmowa odkrywcza
Bałagan w stacku albo zawieszona integracja - Integrono zaplanuje najmądrzejszy pierwszy ruch.
Dostajesz senior-ocenę pułapek budżetowych, zależności i tego, czy kupować, sklejać czy budować - zanim zacznie się płatna praca. CEO zostaje w pętli.