OYO
Cloud-Native Platform for OYO — 99.98% Uptime
Legacy infrastructure, idle cloud spend, DDoS vulnerability, and manual deployments were compounding simultaneously for one of the world's fastest-growing hospitality brands. GYSP tuned Kubernetes auto-scaling to eliminate idle capacity on GCP GKE, driving a 30% cost reduction while achieving 99.98% platform uptime.
Industry
TravelTech
Key Result
99.98% Platform Uptime
Primary Service
Cloud Engineering
Core Stack
AWS, GCP, Kubernetes
See how your cloud setup compares to the results in this case study.
Run the Cloud FinOps DiagnosticThe Challenge
OYO's legacy infrastructure was holding back one of the world's fastest-growing hospitality brands. Manual deployments were slowing product innovation, legacy systems created downtime risk during peak booking hours, and idle cloud resources were inflating spend without contributing to capacity. The platform's microservices transition lacked the automation and observability it needed. DDoS vulnerability and weak data security controls added further urgency. OYO needed a transformation, not an incremental fix.
Our Solution
GYSP delivered a full cloud-native transformation. We built a multi-region high-availability infrastructure across AWS EKS and GCP GKE, containerised legacy workloads into microservices, and implemented Jenkins CI/CD pipelines for zero-touch deployments. Security was baked in at every layer: GCP Cloud Armor for DDoS protection, KMS for encryption, and IAM for granular access control. DevSecOps practices were integrated directly into the automated pipelines. Kubernetes auto-scaling was tuned specifically to eliminate idle node costs while preserving full headroom for demand spikes — the FinOps lever that drove the 30% cost reduction.
Facing a similar challenge? Get a no-commitment technical brief.
Get free briefKey Deliverables
- Multi-region high-availability infrastructure across AWS EKS and GCP GKE
- Containerisation of legacy workloads into microservices enabling per-service scaling
- Kubernetes auto-scaling tuned to eliminate idle node costs — the primary FinOps lever behind the 30% cost reduction
- Jenkins CI/CD pipelines enabling zero-touch, frequent deployments
- GCP Cloud Armor DDoS protection integrated at the infrastructure level
- KMS encryption and IAM-based granular access control
- DevSecOps practices embedded throughout automated pipelines
Services Delivered
- Cloud Engineering
- DevOps Engineering
- DevSecOps
- Kubernetes
- Cloud FinOps
Tech Stack
This engagement used AWS, GCP, Kubernetes, Docker, Jenkins, and 3 additional tools.
Frequently Asked Questions
How did GYSP achieve 99.98% uptime for OYO's hospitality platform?+
GYSP built multi-region high-availability infrastructure across AWS EKS and GCP GKE, with Kubernetes auto-scaling tuned to handle demand spikes without manual intervention. Blue/Green deployment strategies and zero-touch CI/CD pipelines eliminated risky manual deployment windows. The combination of automated scaling, containerised workloads, and multi-region redundancy created a platform that could absorb failures without user impact.
What is DevSecOps and how was it applied to OYO's platform?+
DevSecOps embeds security practices, scanning, access control, and encryption enforcement, directly into the CI/CD pipeline rather than treating them as a post-deployment step. For OYO, GYSP integrated security scanning into every automated pipeline run, so vulnerabilities were caught at build time rather than discovered in production, reducing both security risk and the overhead of separate security reviews.
How did GYSP protect OYO from DDoS attacks at the infrastructure level?+
GYSP implemented GCP Cloud Armor as OYO's DDoS protection layer, sitting in front of the application infrastructure and filtering malicious traffic before it reached the platform. Cloud Armor provides rate limiting, IP-based blocking, and WAF rules that can be updated dynamically in response to evolving attack patterns without requiring application downtime.
What is the advantage of containerising legacy workloads into microservices?+
Containerising legacy workloads breaks a monolithic application into independently deployable services, each with its own resource allocation and scaling policy. For OYO, this meant a failure in one service no longer risked taking down the entire platform, individual services could be updated or rolled back without full-system deployments, and Kubernetes auto-scaling could optimise resource usage at the service level, reducing idle costs while maintaining surge capacity.
Work with GYSP
Similar TravelTech challenge?
Get a free technical brief: architecture options, cost estimates, and a delivery timeline scoped to your challenge.
- 48-hour turnaround
- Senior engineers only
- No commitment required
Or call: +1 (929) 588-8364
More TravelTech Case Studies
TravelTechExpedia India
Manual deployments, peak-season exposure, and reactive monitoring, at the scale of millions of daily travel bookings. The infrastructure needed to match the ambition.
TravelTechAdventure Japan
PCI-DSS, ISO 27001, and SOC2, across AWS, Azure, and GCP, with a live booking platform that couldn't go down. A compliance-first multi-cloud migration with zero business disruption.
