Learning in public. On purpose.

Every founder team has a moment where they realise the problem they thought they were solving is not the real one. Ours came in a warehouse in Pune, standing next to an operations head who had six figures of monthly pallet shrinkage and no way to prove when it was happening. He had guards. He had cameras. He had an insurance policy. What he did not have was a coherent record. And without that, none of the rest of it worked.

Rakshak was not born as a drone company. It was born as an attempt to give that operations head — and thousands like him across Indian industrial sites — one honest answer to a simple question: what actually happened last night?

We are not a company you buy from and never hear from again. For every one of our first customers, at least one founder is reachable, personally, on the deployment. That is not a marketing decision. It is how we learn. Security is a relationship built site by site; we do not intend to outsource that back to a reseller until we are certain we have earned the right to.

Foreign platforms carry foreign assumptions — about weather, about labour, about regulation, about who your customers actually are and how they make decisions. India is not a translation of an American security market. It is its own thing. We are building for it directly.

Some of what we publish on this site is modeled — an outcome projected from site engineering assumptions rather than a completed pilot. Where that is true, we say so, in the same typographic weight as the number itself. As pilots complete and clients let us name them, we will replace the models with the record.

— The founding team, Rakshak Systems. Bengaluru.