Multi-region provisioning
I architected and led a provisioning system on the company cloud that lets enterprises configure and deploy networks programmatically across four regions: US, EU, India and UAE.
Region is not a configuration flag. Each one has its own capacity, its own latency relationship to everything else, and — the part that shapes the design — its own reasons why a customer's data is required to stay inside it. A provisioning API that treats regions as interchangeable is one that has not met a compliance requirement yet.
Real-time backend
Creating and monitoring distributed nodes, with:
- Kafka for background job processing, so provisioning work survives a restart and can be retried without a human deciding whether it already ran.
- WebSockets streaming container logs to a dashboard while they are being written.
Streaming logs live is a small feature with a disproportionate effect: it changes "deployment failed" from a support ticket into something the customer can watch and diagnose. Most of the engineering is in backpressure — a container that is failing tends to be verbose about it, and the dashboard has to stay usable while that happens.
An AI compliance agent, aligned to the DPDP Act
India's Digital Personal Data Protection Act is legislation, not documentation. The agent does retrieval over the actual text, using RAG and LangChain, and supports consent management and auditable data governance.
The interesting constraint is that a compliance answer is worthless without provenance. An agent that says "yes, that is permitted" is a liability; an agent that says "that is permitted, under this clause, and here is the clause" is a tool. So the retrieval layer exists as much to produce citations as to produce answers, and the audit trail is a first-class output rather than logging.
Also
Backend services and APIs for enterprises to deploy and execute transactions inside isolated private networks.
TODO(omkar): confirm what's publicly sayable here — this is enterprise work and I've kept it to what your résumé already states, but you should check it against whatever you signed.