unthinkable
Case study · A global SaaS transit-tech company (unnamed in the source) · 20+ countries, 500+ cities

Riders on the company's shuttles and on-demand transport in 500+ cities rely on services that stay up.

The company, which runs on-demand transport, shuttles, student transport and logistics for cities, universities and companies in 20+ countries, wanted every service to stay available and every team to know who owns what.

What changed

99.9%SLA and uptime (as reported)
360°monitoring and log management (as reported)
35%lower cloud costs (as reported)
What stood in the way

What stood in the way.

What stood in the way
  • DevOps was decentralised across 100+ AWS accounts, with no control over access and no clear ownership of operations.
  • Infrastructure was over-provisioned, with no central monitoring, no high availability setup and no private network.
What changed
  • 99.9%SLA and uptime (as reported)
  • 360°monitoring and log management (as reported)
  • 35%lower cloud costs (as reported)
What we built

What we built.

  • Controlled access with AWS IAM and single sign-on, role by role, for servers, monitoring and developer tools.
  • Private networks with Amazon VPC and AWS Transit Gateway, with endpoints, domains and SSL certificates managed.
  • Provisioning on serverless and Kubernetes, with microservices on AWS Lambda set up through CloudFormation stacks.
  • Dashboards that show performance at every level, with central log analytics.
  • AWS IAM
  • Amazon VPC
  • AWS Transit Gateway
  • AWS Lambda
  • AWS CloudFormation
  • Kubernetes
What it shows

What this work shows about us.

One way of running many systems

Hundreds of transport solutions across 100+ accounts now share the same access, network, provisioning and monitoring rules.

Pay for what runs

Provisioning by code ended over-provisioning, which cut cloud costs by 35% (as reported).

Want standard, automated DevOps across your AWS accounts? 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 the global transit-tech (TaaS) company asked us now, this is what we would add, step by step.

Watching the service

An agent would watch the dashboards and logs across accounts, notice a service slowing down and page the owner with the likely cause. The on-call engineer decides the fix.

Keeping costs right

An agent would list idle or oversized resources each week with their owners and the saving, for each team to accept or reject. Teams decide every change.

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.