Curiosity is the most powerful thing you own

A beautiful narrative written over an elegant publishing platform. The story begins here...

Platform Engineering. Securing and running production systems across banking, gaming and e-commerce since 2011 — secure CI/CD, Kubernetes, MLOps, Observability. I write up the failures in detail: what broke, what the graphs showed, and what actually fixed it.

Home Labber — Notes from the Trenches

The Journey Begins here…

Selected work

Systems kept alive, and the ones that broke first. Every figure below is from the resume or from a post on this site.

  • Reliability

    99.9999% uptime across datacentre, AWS and Azure

    Sysadmin team at India's largest fashion e-commerce platform — on-call rotation, revenue-impact metrics and PCI audit.

    Six nines · hybrid infrastructure

  • Incident

    A Kubernetes node that served its own NFS mount

    Memory pressure starved the NFS daemon the node itself depended on — a self-referencing deadlock that looked like a network fault.

    1,172 zombie processes · load average 10× cores

  • Cost

    Cut cloud spend by finding what nobody was using

    Billing analysis over AWS and Azure ETL, built in Python and Flask, surfacing overprovisioned and idle services.

    25% reduction

  • Compliance

    Securing ISO 27001 certification

    VAPT remediation and multi-AZ disaster recovery driven by Ansible. The certification unlocked further client contracts.

    ISO 27001 · audited

  • Platform

    Secure CI/CD architecture for a national bank

    OSA, SAST, DAST and a container trust registry, with policy as code catching issues before release rather than after.

    Banking · current role

  • Cost

    Catching an AI agent ignoring its own rules

    Instrumented the tool loop, found the gap where enforcement was never reached, and closed it with a pre-tool hook.

    406M wasted tokens recovered

docker

Zero: The Image That Was Already Clean

Chainguard Hummingbird scans at zero findings in both layers. It was asked to be fixed anyway, so it was re-verified from its digest instead: 0 OS, 0 app, still booting in 8s, still non-root. The interesting part is why rebuilding a clean image would have been the wrong move.

rhel

115 to 56: Remediating an Image That Cannot Patch Itself

UBI Micro scored 115 findings, 3 CRITICAL in Tomcat, and ships no rpm, dnf or microdnf — nothing inside it can upgrade anything. Building the fix outside and copying it in cleared 59 and introduced none, for +4.8% size. Three build bugs along the way, the last silently duplicating a 62 MB JAR.

rhel

895 to 575: Remediating Red Hat UBI 9 Full

The only image in the comparison with a package manager was also the worst offender at 895 findings. Its security channel turned out to be completely empty. A full dnf upgrade cleared 320 of them — and quietly introduced 20 new ones.

llm

The 5.11 Tokens/Second Server

How an 18.5 GB MoE LLM was made usable on a 4 GB gaming laptop: measured 1.53 to 5.11 tokens/sec, then wrapped in rootless systemd supervision with restart backoff, log rotation and boot persistence. Real numbers, real config.