How I got here
Twenty-four years ago I started where most people in technology start — figuring out how systems work and how to make them work better. What followed was a career spanning some of India's most recognised technology companies: Wipro, HCL, Capgemini, and others. I led infrastructure programmes, managed large enterprise accounts, and ran service delivery at scale across financial services, healthcare and cloud infrastructure. The work taught me one thing above all: the bigger and more complex a system, the more it depends on assumptions that nobody has questioned.
At some point one of those assumptions became hard to ignore. Much of the defensive architecture I worked with assumed that what it protected stayed still long enough to protect — the attack surface a fixed object, the attacker the dynamic element. I started wondering what would happen if you flipped that: what if the observable surface kept changing? Not by patching it, not by monitoring it — by rotating its network-visible identity on a schedule (60 seconds by default), with an independent verifier checking each change from outside.
That question became Adaptive Cryptographic Surface Engineering — ACSE. Two years of design and engineering later — with formal analysis of parts of the protocol in ProVerif and an adversarial assessment of the code — the Indian Patent Office published the application (IN202641070690, Journal No. 25/2026, 19 June 2026); it is pending examination. I am now in the earliest stage of what comes next: taking the invention from a patent and a working codebase into the world. That is the work of a founder.
Indian patent application IN202641070690 — Adaptive Cryptographic Surface Engineering. Published 19 June 2026, Journal No. 25/2026, by the Indian Patent Office; pending examination.
Core beliefs
Principles built from 24 years of making things work — and watching what happens when they aren't followed.
The most elegant solutions are often the simplest ones that solve the core problem effectively.
More is lost by indecision than by wrong decisions. Progress through iteration beats waiting for perfection.
Build with growth in mind, but don't over-engineer. The right architecture enables future scale.
What I'm working on
A third-party penetration test, a vulnerability scan against a running build, an empanelled security audit and a third-party cryptographic review are planned and not yet completed. A public adversarial challenge is planned after the internal red-team work. No dates are set.
Lab regression gates run against real agents and network stacks, readying the product for its first pilot.
Turning the IP, the evidence and the working codebase into a company — the work this stage is really about.
Where I've worked
Enterprise technology at scale — infrastructure leadership, service delivery and client management across some of India's most recognised technology organisations.
Beyond the work
The kind of mind someone has shows in what they do when they're not working.
An avid player — not for tournaments, but for what the game teaches about sitting patiently with a complex position and finding the right move rather than the fast one.
Travelled almost the entire country by road — two wheels and four. Crossing India at ground level, through every kind of terrain and town, puts everything else into perspective.
Personal thinking goes to iamarul.in — a space separate from the technical work where longer ideas get worked through in prose.
Theology, philosophy, history, astronomy, cosmology. The questions about consciousness, the scale of things, and where human beings fit in all of it have never stopped being interesting.
Shpongle and Indian classical in roughly equal measure — psychedelic, layered and ancient at the same time.
If you're thinking about investment, partnership or a pilot deployment — or simply want to understand what ACSE-PME is and why it matters — that conversation is welcome. Get in touch, see the innovation, or read the research. Connect on LinkedIn.