Cloudplatformsthatshipatnoon,notat11pmonFriday.
I'm Narendra. For five years I've been building the infrastructure under fintechs, healthtechs, and AI platforms. Resilient cloud foundations, Kubernetes that upgrades on a Tuesday, pipelines under ten minutes, and the boring discipline that decides whether incidents are 20 minutes or two hours.
The work that keeps platforms running quietly.
Ten focused services across cloud, platforms, Kubernetes, CI/CD, IaC, SRE, security, databases, migrations, and fractional leadership. I pick what fits, not what I last used.
What you actually buy.
Engagements framed by the result, not the toolchain. Cost under control. Cutovers without weekends. Audits that take three days, not three weeks.
Recent engagements.
Boring is a feature.
I pick well-understood building blocks and configure them deliberately. Tools earn their keep or they leave.
From the people who hired me.
“Honestly thought we'd need to hire two senior people. Narendra came in for three months, fixed the deploy pipeline, sorted out the alerts that were destroying our on-call, and left us with docs we actually read. Calm, no drama.”
“He doesn't try to sound smart. He just asks the right questions, takes a couple of days to look around, then comes back with a plan that makes sense. Cut our cloud bill by something like 30% in the first month and the savings stuck.”
“Wanted someone who could just take the Kubernetes side off my plate. Found Narendra through a friend. Two months later I've stopped getting paged at night and my team actually trusts the upgrade process. That alone was worth it.”
“Bit nervous hiring a freelancer for something this critical. Shouldn't have been. He's straight, tells you when something is a bad idea, and the work is solid. Would hire again without thinking twice.”
Have a hairy DevOps problem?
Tell me what you're trying to ship, fix, or untangle. I'll be honest about whether I'm the right person and how I'd approach it.