Travel · OTA · Multi-tenant

Ovago OTA + 30-brand booking platform

Ovago is the public face of a serious travel stack (Kivork / Travel Insides). I worked the Yii2 hybrid booking engine that many brands share - search, checkout, payments, insurance and cabinet - so sister OTAs are configurations, not 30 codebases.

Role PHP / Yii2 engineer · OTA platform & GDS

Engagement Consumer OTA plus shared engine for 30+ white-labels

Platform type Web

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.

Stack

PHP Yii2 MySQL Redis GDS Sabre Amadeus NDC Stripe Cover Genius multi-tenant OTA

Free discovery call

Bring a messy stack or stalled integration - Integrono will map the smartest first move.

You get a senior take on budget traps, dependencies and whether to buy, glue or build - before paid work starts. The CEO stays in the loop.

Book the free intro · Telegram WhatsApp

Problem

Stack

Architecture

Result

Stack

Related sites

Bring a messy stack or stalled integration - Integrono will map the smartest first move.