I like working on the parts of software most people never look at: protocols, network behaviour, and the checks that run before something ships. Most of what I build starts with a question I couldn't answer by reading about it.

Based in Kerala. Tabs over spaces.

Halonyx is an end-to-end encrypted messenger. I wanted to understand the Signal Protocol properly, so I implemented X3DH and the Double Ratchet myself instead of pulling in a library. It has since grown group chats with no server-side group state, a client-side scanner that catches leaked API keys and card numbers before a message is encrypted, and a written threat model I try to keep honest. I also wrote up the protocol work in two papers.

PulseCast came from a simple thought: congestion behaves more like weather than like a number. It is a Rust simulator where overload at one node spreads across the topology, with a forecast engine that tries to say where the pressure is heading before it arrives, and a few routing strategies that try to get out of the way. The frontend is React and D3, so you can watch it happen.

AXIS audits websites against WCAG 2.2. The engine is published as a package for .NET, JavaScript and Rust, so it can sit inside a CI pipeline instead of being something you run once before launch.

Applied cryptography, async networking in Rust, and tooling that makes other people's work easier to trust. I'm also getting deep into Spark and Databricks, because data infrastructure is the other half of backend work I want to understand.

I write up what I learn while building these on DEV and Medium. Most of it is the reasoning behind a design decision, not a tutorial.

Find me on LinkedIn.