unthinkable
Case study · Chalo, India · live public transport tracking app

Chalo's commuters see where their bus is in real time, and new cities get the app in days, not weeks.

Chalo, whose app shows the live location and arrival time of buses and trains in more than 15,000 vehicles across 17 Indian cities, wanted commuters to rely on it every day and to open in new cities quickly.

IndiaPublic transit & mobility (live tracking, ticketing, ride-sharing)

What changed

40%lower IT operations cost (as reported)
50%less time to onboard a new city (as reported)
0downtime during the migration (as reported)
99.9%uptime (as reported)
What stood in the way

What stood in the way.

What stood in the way
  • Thousands of daily commuters depended on live bus locations, so slow responses or downtime were not acceptable.
  • The app ran on GCP as a platform service, which gave little room to scale and little control over cost when traffic surged.
  • Opening in each new city took weeks of setup and configuration.
  • The whole system and its database had to move without losing or exposing any data.
What changed
  • 40%lower IT operations cost (as reported)
  • 50%less time to onboard a new city (as reported)
  • 0downtime during the migration (as reported)
  • 99.9%uptime (as reported)
What we built

What we built.

  • Advice on the cost, strengths and limits of each cloud, which led Chalo to choose AWS.
  • A migration roadmap, planned to complete within one month with minimum downtime.
  • A disaster recovery environment on AWS first, kept in sync with production, then a new AWS production environment synced to it before the switch.
  • Linux application and database servers on Amazon EC2 with EBS volumes fast enough for payment transactions.
  • Auto scaling groups behind a Network Load Balancer, so capacity grows at peak hours and shrinks when traffic is low.
  • Backups on Amazon S3 and logs collected in Amazon CloudWatch, connected to Chalo's event management.
  • CloudOps that standardised deployments across environments, with ongoing support for outages.
  • AWS
  • Amazon EC2
  • Amazon EBS
  • Amazon S3
  • Amazon CloudWatch
  • Network Load Balancer
What it shows

What this work shows about us.

We keep live systems live

Commuters kept tracking their buses throughout the move, because the new environment was built and synced beside the old one before the switch.

Infrastructure that follows the business

Capacity that scales with rush hour and a pay-as-you-go cost let Chalo plan spending around its expansion to new cities.

Want to move a live app from GCP to AWS with no downtime? Tell us what you want to change. Our AI assistant, Ask Unthinkable, helps you define your requirements, then connects you with the right team.

Start your plan ↗
If we built it today

If we built it today, with AI.

This work came before today's AI. If Chalo asked us now, this is what we would add, step by step.

Tracking

An agent would answer a commuter's 'where is my bus' from the live location feed, and suggest the next best route when a bus is far away. The arrival times still come from the tracking system.

A delay

An agent would notice a bus running late against its schedule and tell the commuters waiting for it, with the next option. Operators still decide any change to service.

Booking

An agent would help a commuter buy the right ticket or pass for a trip and explain the fare. The fares and payments stay in the ticketing rules.

Ask Unthinkable

Want this for your business?

Tell us what you run or what you're building. Our AI assistant, Ask Unthinkable, helps you define your requirements, then connects you with a senior AI engineer.

Send us a note instead

Required

Thanks. A senior AI engineer will reply to you.
u
Ask UnthinkableClarity first, then the right team
Your conversation

An AI agent. This prototype uses prepared answers and sends nothing.