Hi, I'm Ajin
A space for discussing both new and old ideas in the Cloud and SRE domain — written by a practitioner who has spent over 15 years building, scaling, and breaking things in production.
I started my career as a Linux server administrator — hands on with bare metal, late-night kernel panics, and the deep satisfaction of keeping things running. That foundation led me to founding a web-hosting company, where I learned that running infrastructure for others is a different challenge entirely.
From there I moved into the fin-tech space, co-founding a company where distributed systems, reliability, and security stopped being academic concepts and became daily operational realities. Today, I work as a cloud architect and am actively exploring the Site Reliability Engineering practice — bridging the gap between development velocity and operational excellence.
More recently, I've been deep in AI infrastructure — deploying and operating large-scale ML workloads on cloud platforms, working with GPU clusters, model serving pipelines, vector databases, and the observability challenges that come with running non-deterministic systems in production. It's a fascinating layer of the stack where SRE principles meet entirely new failure modes.
This blog is my public notebook. Writing forces clarity, and sharing invites better thinking. Everything here is something I've either built, broken, or had to explain to someone at 2am during an incident.
- Early Career Linux Server Administrator Started at the metal — configuring servers, managing networks, learning that reliability is earned, not assumed.
- Founder Web Hosting Company Founded and operated a web hosting business, running production infrastructure for clients across multiple stacks.
- Co-Founder Fin-Tech Company Built distributed systems in a regulated industry — where availability and security are non-negotiable.
- Present Cloud Architect & SRE Explorer Designing cloud-native systems on AWS and Azure, deepening SRE practice, and writing about all of it here.
Free Consultation
I'm happy to help with problems I find genuinely interesting. No fees — just good conversations about hard problems. Time commitment capped at a few hours per engagement.
Open Source: If you're working on an open-source project and need an extra hand, reach out. I'm willing to commit 10–15 hours a week to the right project — whether that's infrastructure, automation, documentation, or code review.