A surveillance camera is a different category of product from most of the electronics India imports and assembles. It doesn't just sit in a home or office — it continuously generates video of the people, spaces and activity around it, and increasingly, it processes that video with on-device intelligence before sending anything anywhere. That makes the question of where it was designed, and by whom, materially different from the same question about a kettle or a router.
The data-sovereignty argument, stated plainly
Most of India's installed base of surveillance cameras today runs on foreign-designed silicon and closed firmware, procured through supply chains that few Indian buyers — including government ones — can meaningfully audit. For a device that watches and records continuously, that's a different risk profile than for most other imported electronics: it's not just a product-quality question, it's a question of who could theoretically access, influence or disable a safety-relevant piece of infrastructure, and how that would ever be detected.
This is the practical reasoning behind data-residency requirements, local-component mandates, and a push for domestically designed (not just domestically assembled) surveillance technology that we're seeing move from policy conversation into actual procurement requirements.
Why "Make in India" has to mean design, not just assembly
There's an important distinction that often gets lost: a camera can be physically assembled in India while still being designed entirely elsewhere, built around a reference design, firmware and component choices that an Indian team had no hand in and cannot meaningfully modify or audit. That satisfies a manufacturing-location requirement without addressing the underlying concern at all.
Designing in India — meaning the hardware architecture, the embedded firmware, the image processing and the on-device analytics are actually developed by a team here — is what makes the technology auditable, modifiable and genuinely sovereign. It's also, practically, a prerequisite for navigating India's own security certification regime (STQC) smoothly, since that process examines exactly the firmware and security decisions that only the actual design team can speak to with authority.
The market is already moving this direction
India's video-surveillance market is on a steep growth trajectory — industry estimates put annual growth at roughly 20%, with the market expected to more than double by 2030 (sources: Mordor Intelligence, IMARC). That growth is being driven by smart-city and urban-safety programmes, the expansion of housing, office and small-business installations, a shift from older analogue cameras to smart, connected ones, and — increasingly — government security testing requirements and a deliberate move away from Chinese-origin equipment.
Put together, those forces mean that "designed in India" is moving from a preference some buyers express to a specification some buyers will require outright, particularly in the government and critical-infrastructure segments. Companies that can only offer imported, closed designs will find a shrinking share of that market open to them.
What this means in practice
For OEMs and product brands evaluating where to source their next camera design, the practical question worth asking isn't "can this be manufactured in India" — most contract manufacturers can say yes to that. It's "was this actually designed by engineers here, with a component strategy and firmware architecture that holds up to Indian security testing and genuine technical scrutiny." That's a smaller list of teams, and it's the gap SAMS is built to fill: an Indian engineering team with the imaging, hardware, firmware and AI depth to design a camera product end to end, not assemble one.