Cloud infrastructure and DevOps in Mumbai
Many Mumbai businesses run infrastructure that was clicked together in a console over several years. A fintech's payment services, a publisher's release-day traffic and a brand's sale-day checkout sit on servers nobody could rebuild from memory, with shared keys, logs scattered across machines and a deploy process one person understands. The gaps show when traffic arrives all at once, on a match day, a film release or the first hour of a sale.
We put your infrastructure into Terraform so it can be read, reviewed and rebuilt, usually in AWS's Mumbai region or the region of the cloud you already use. Logs are collected in one place and kept for as long as you decide, access is granted through roles rather than shared keys, and deploys run through a pipeline that leaves a record. Scaling is tested before the big day rather than during it. Alerts page a person only when a person is needed, and the bill usually comes down too.
Mumbai is India's financial capital. Both major stock exchanges are here, and so are many of the country's banks, NBFCs, brokers, wealth managers, insurers and fintechs. For these companies software is judged first on whether the money is right. A loan ledger that drifts from the bank statement, a payout released twice because a partner timed out, a portfolio screen showing yesterday's price: each one lands on an operations desk the next morning. What they need built is rarely a new product from nothing. It is a lending or payments backend that reconciles, a platform where each role sees exactly what it should, and approvals that need two people before money moves. Engineers who have built those systems are in demand across the city, so the work often waits for a hire.
The city's second industry is attention. The Hindi film industry, most of the country's television networks and many of its large publishers are based here, and their software problems are specific: traffic that arrives all at once on a release or a match day, rights and metadata that decide what can be shown where, and archives that are valuable only if someone can search them. A slow page on a publisher's site is lost revenue, because the readers came from search and will go straight back to it.
The third is consumer business in every size. Mumbai has D2C brands selling beauty, fashion and food through their own stores and every marketplace at once, and it is home to large family-owned groups and conglomerates whose older divisions still run on spreadsheets and exports from their accounting software. In the bigger groups the buyer is usually a digital team with a mandate, a budget and a procurement process, and the work has to survive that process as well as production.
We are in Bengaluru and share your time zone, so the working day is the same on both sides and a question asked in the morning is answered the same morning. You talk directly to the engineer who writes the code. The work happens in your repository and a shared chat channel, where every decision is written down, and the runbooks and architecture notes are written as we go rather than at the end.
We are the right fit when a Mumbai team has a defined piece of work and wants a senior engineer on it within days: a ledger that has to reconcile, a migration with an end date, or extra capacity while you hire. Start with a fixed-price two-week piece, or bring us in white-label for your agency's clients under your name.
Four ways this arrives.
Resources were created in the console over several years and nobody can say which ones matter. We inventory the account, bring what is live into Terraform, remove what is not, and hand you a repository that describes the whole estate.
It is usually idle capacity, oversized instances, forgotten environments and data transfer nobody priced. We find where the money goes, cut the obvious waste where you already are, and only then ask whether a cheaper provider such as Hetzner suits your steady workloads.
One person knows the steps and every release waits for them. We build a pipeline that tests, builds and deploys on merge, with rollback to the previous image, so shipping on a Friday afternoon is a decision rather than a gamble.
The channel fires all day, so everyone has muted it, so real outages are reported by customers. We alert on what users actually feel, route each alert to a named owner, and delete every alert nobody would act on at 3am.
A K3s cluster on Hetzner that we provisioned and are on call for, deployed through Flux, where only a push to master can produce an image production will run.
Read the write-up →Asked by Mumbai teams.
How do you work with teams in Mumbai?+
We are in Bengaluru and share your time zone, so calls, reviews and releases fit inside your normal working day. We work in your tools, Slack, GitHub and Linear or whatever your team already uses, and every decision is written down in the repository or the channel. You talk directly to the engineer writing the code, from the first 30-minute call through to handover, with runbooks and architecture notes written as we go.
Do you build for Mumbai lenders, brokers and fintechs?+
Yes. We build the parts where the money has to be right: loan and payment ledgers that reconcile against the bank's records every day, retries that cannot turn a timeout into a double payout, maker-checker approvals where a second person signs off before money moves, and a full history of every change of state. We work inside the system you already run, in Node, Python and Next.js, and ship in increments.
How does your rate compare to hiring in Mumbai?+
PayScale puts a mid-career software engineer in Mumbai at about ₹15 lakh a year. Our published rate is $35 an hour, with a $5,000 minimum. That buys a senior engineer who writes the code, works in your Slack, GitHub and Linear, and starts within days, with no recruiting round, notice period or employment overhead. Start with a fixed-price two-week piece at $2,800 and judge us on the output before committing to more.
Can you work white-label for our Mumbai agency?+
Yes. Mumbai's digital and media agencies bring us in when a client needs a backend, a mobile app or a data pipeline alongside the design and campaign work. We work under your name, in your client's repositories and your channels, and sign an NDA before specifics. The code belongs to the client from the first commit. You keep the relationship, we write the code and the runbooks, and your team presents the work.
Should we run our own Kubernetes cluster?+
Usually not. Self-hosting starts to pay when your managed bill is mostly things you do not use, your workloads are steady rather than spiky, and someone is willing to own the control plane. We run our own on Hetzner, so we know what that job involves. If nobody on your side wants it, managed is cheaper in total even when the invoice is larger.
Do we need Kubernetes at all?+
Often not. Plenty of products are better served by a managed container service, a platform like Railway, or two virtual machines and a good deploy script. Kubernetes earns its place when you run several services, have steady traffic and have people to look after it. We will recommend the least infrastructure that does the job, and say so when that is less than you expected.
Which clouds do you work with?+
AWS most often, then Google Cloud, Azure and Hetzner. We work in whichever one you are already on, because moving clouds is rarely the cheapest fix for a cost or reliability problem. If we think a move is worth it, we will show you the case using your own bill before anyone migrates anything.
Can you cut our cloud bill without a migration?+
Usually, yes. Most of a bill that has grown unchecked is idle capacity, oversized instances, environments left running and data transfer nobody priced, and all of that is fixed where you already are. We will not promise a percentage before we have read the bill. After the first week we can tell you what is realistic and what it takes to get there.
Who is on call?+
Whoever the engagement says, in writing. While we run your infrastructure it can be us, with hours and response times agreed up front. If you are taking it in-house, the handover includes the runbooks, the alert routing and a rota your team can actually staff. We do not leave behind a pager that only we know how to answer.