If you've asked three system integrators how many cameras your building needs and gotten three different numbers, you've met the problem: CCTV projects are still specified by experience, not measurement. IndoAI's four free tools at indo.ai/tools — Camera Coverage & Layout, AI Camera Space Planner, Lens & Sightline Selector, and Low-Light/Aesthetic Check — replace that guesswork with pixel-density math, one calculation for each decision a project actually needs made.
- CCTV projects are usually priced on habit, not math — coverage, lens, lighting, bandwidth and storage are rarely calculated as one connected system.
- IndoAI's four free tools at indo.ai/tools are part of a wider nine-tool suite, documented in peer-reviewed research, organised into Design, Size and Verify phases.
- Two well-placed, higher-resolution cameras can beat four cheap ones on both image quality and total cost — the worked ₹ example below shows the math.
- The tools are free and require no login, but they model design inputs, not a substitute for a site survey or a licensed integrator's final sign-off.
The CCTV Industry's Missing Ingredient: A Methodical, Whole-Project Calculation
Most CCTV layouts in India are still specified the way they were fifteen years ago: an integrator walks the site, eyeballs the room, and picks a camera count that "feels right" for the budget. Demand isn't the problem — India's video surveillance market was valued at roughly USD 4.40 billion in 2025 and is forecast to reach USD 7.12 billion by 2030, a 10.10% CAGR, with hardware alone accounting for over 63% of spend in 2024.[1] The problem is that growth in spend hasn't been matched by growth in method.
"The whole-project math is what's missing, not just the camera count. Coverage, lens selection, lighting suitability, bandwidth and storage almost never get modelled together on the same job — each is estimated separately, by different people, at different stages, and nobody reconciles them until something breaks on-site." — Independent security systems consultant, on why CCTV projects run over budget
A Bill of Quantities (BOQ) — the itemised list of hardware, cabling and labour that makes up a quote — is only as trustworthy as the logic behind every line on it. That's the specific gap IndoAI's four tools were built to close, and it's a gap the industry has largely tolerated rather than solved: SIs, architects, IT teams and finance all work off separate, unreconciled numbers until the installation is already underway.
What Is PPM (Pixels Per Meter), and Why Does It Change Everything?
PPM is the pixel-density logic behind the international DORI framework (Detection, Observation, Recognition, Identification) defined in IEC 62676-4, the application-guideline standard for video surveillance system design. The commonly cited thresholds are roughly 25 px/m for basic detection and 250 px/m for identification-grade footage — the level needed to reliably match a face or a licence plate.[2] A 2025 revision of the standard has since recommended even higher densities for modern digital sensors, reflecting how much compression and noise degrade real-world footage compared to lab conditions.[3]
Two cameras can look identical on a spec sheet and deliver completely different legal usefulness, depending on distance and lens. "How many cameras do I need" is the wrong first question; "what PPM do I need at this specific distance" is the right one — and it's the question IndoAI's tools are built around.
Four Free Tools, One Design Language
Rather than one all-purpose calculator, IndoAI splits the design problem into four focused tools, each solving one specific decision a project actually needs made — all free, all at indo.ai/tools, none requiring a login.
Camera Coverage & Layout
Turns "I think two cameras should cover this room" into a diagram you can hand to a client.
Camera_coverage_calculator.htmlAI Camera Space Planner
Replaces the "one camera per X sq ft" guess with a quantity model driven by area and target PPM.
AI_camera_quantity_estimator.htmlLens & Sightline Selector
Matches focal length to distance and target PPM — wrong focal length is the most invisible design mistake.
Lens_focal_length_selector.htmlLow-Light / Aesthetic Check
Prevents the "it worked in the demo, not at 9pm" complaint and the housing an architect never signed off on.
Low_Light_Suitability_Estimator.htmlThe Research Behind the Tools: A Nine-Tool, Three-Phase Pipeline
The four tools above are the ones most relevant to System Integrators and Architects, but they're part of a wider nine-tool suite at indo.ai/tools. IndoAI's engineering team — Dr. Vivek Gujar, Advait Gujar, and Ashwani Kumar Rathore — documented the full architecture in a peer-reviewed case study, "Vision Language Models as the Reasoning Layer of an AI-CCTV Planning Toolkit," which frames the suite as a coupled pipeline across three phases rather than nine standalone calculators.[5]
| Phase | Tools | What It Fixes |
|---|---|---|
| Design | Camera Coverage & Layout, AI Camera Space Planner, Lens & Sightline Selector | Camera count, placement and lens against the physical layout |
| Size | Storage Calculator, Bandwidth Calculator | Disk capacity and network load implied by the Design-phase output |
| Verify | PPM Checker, Face Recognition Feasibility, ANPR Feasibility, Low-Light/Aesthetic Check | Stress-tests the design against physical constraints before hardware is purchased |
The paper's core argument is that these nine tools are "not nine separate estimators but a whole interlinked pipeline" — a change in one input (say, adding an ANPR requirement to a zone that was previously PPE-only) propagates automatically through pixel-density, bitrate, storage, edge-compute and licensing, rather than requiring the buyer to work out each consequence by hand.[5]
The AI Stack as a Structured List
It's worth noticing that even the underlying software architecture doesn't resist being explained any other way than as a categorised list — capture, process, act — the same three-step logic that runs through every layer of this toolkit.
The Capture Layer
Records the physical footage.
The Intelligence Layer
The "brain" running the algorithms.
The Outcomes Layer
Delivers actionable evidence.
This is also why the four planning tools above can't be evaluated in isolation from each other: get the Capture Layer wrong — too few cameras, the wrong lens — and the Intelligence Layer has nothing usable to reason over, no matter how good the Edge Box is. The listicle format isn't just an editorial device here; it mirrors how the stack itself is built to be reasoned about, one layer feeding the next.
The Target Market Pyramid: Four Buyers, One Calculation Engine
These four tools activate four distinct roles in the surveillance supply chain, each solving a different problem with the same underlying pixel-density logic.
| Tier | Buyer | Core Anxiety | Primary Tool(s) |
|---|---|---|---|
| 1 | System Integrators | Losing the bid or losing the client | Camera Coverage & Layout, AI Camera Space Planner |
| 2 | Architects & BMS Consultants | Ugly, clashing retrofits | Lens & Sightline Selector, Low-Light/Aesthetic Check |
| 3 | IT Managers | Bandwidth chokeholds & DPDP exposure | Network/storage load estimates from the above outputs |
| 4 | CXOs & Owners | Cost, liability, ROI | Consolidated design output from all four tools |
Tier 1 — System Integrators: From Guesswork to a Defensible BOQ
The challenge: System Integrators (SIs) sit at the base of the pyramid because every tier above depends on their number being right. Their dilemma is structural: quote too many cameras and lose the bid on price; quote too few and absorb the cost of a failed audit and a furious client months later.
The IndoAI leverage: The AI Camera Space Planner replaces the "one camera per 200 sq ft" habit with a quantity estimate driven by actual room area and target PPM, and the Camera Coverage & Layout tool turns that count into a visual footprint the client — or a rival integrator — can independently check.
Tools: AI Camera Space Planner + Camera Coverage & Layout"Every SI has lost a bid to someone who under-quoted, and lost a client to someone who over-delivered at a lower price. The only way out is a number you can defend with math, not confidence." — Regional security systems integrator, Pune, on the economics of camera BOQs
Tier 2 — Architects & BMS Consultants: Designing Security In, Not Bolting It On
The challenge: Security has traditionally been an afterthought in architectural drawings — added once the conduit layout, false ceiling and finishing schedule are already locked. The visible result: exposed cabling, cameras bracketed onto whichever column was nearest, and a building that looks "smart" on the brochure but improvised in the ceiling voids.
The IndoAI leverage: The Lens & Sightline Selector lets an architect or BMS consultant work out, at the drafting stage, exactly what focal length and mounting distance a given sightline needs — before a conduit is drawn. The Low-Light/Aesthetic Check adds the constraint architects care about most and integrators often ignore: will this housing look right on a heritage facade or a glass lobby, and will it still work after dark.
Tools: Lens & Sightline Selector + Low-Light/Aesthetic CheckWhere the design meets the hardware: EdgeBox™
Once camera count, placement and lens are settled, the next question is where the AI inference actually runs. IndoAI's EdgeBox™ appliances process video locally at the edge instead of streaming every frame to a cloud GPU — which is exactly why the pixel-density and bandwidth numbers coming out of these tools matter so much. A design that's accurate on paper and inefficient on the network isn't actually finished.
Explore the planning tools →Tier 3 — IT Managers: Bandwidth, Storage and DPDP Risk
The challenge: IT Managers inherit the video estate after design is finished, and they carry three specific anxieties: will the local network choke under peak camera-to-NVR (Network Video Recorder) load, will the internet bill balloon once remote viewing is switched on, and is the retention policy defensible under India's data protection law.
The compliance backdrop: The Digital Personal Data Protection Act, 2023 (DPDP Act) treats footage that can identify a person as personal data. The DPDP Rules, 2025 were notified on 13 November 2025, starting a phased rollout — the Data Protection Board became operational immediately, the Consent Manager framework activates in November 2026, and full substantive compliance obligations (notice requirements, security safeguards, retention limits) come into force by 13 May 2027.[4] Industry analysis separately estimates DPDP compliance work adds roughly 8–12% to average project budgets.[1]
Input: camera count & resolution from Tier 1–2 toolsBehind IndoAI's Storage Calculator sits a straightforward relationship the research paper documents explicitly: Cameras × Codec Bitrate × Retention Days = Required Terabytes. The bitrate half of that equation isn't fixed — it depends on what the AI is being asked to do, not just the resolution on the box:[5]
| Stream Profile | Frame Rate | Codec | Target Bitrate |
|---|---|---|---|
| 1080p, general-purpose | 10–15 fps | H.265 | ~1024 Kbps |
| 4MP, AI-analytics grade | 10–15 fps | H.265 / H.265+ | 1440–2048 Kbps |
| 4MP, vehicle/ANPR tracking | 25–30 fps | H.265 / H.265+ | Upper end of 1440–2048 Kbps band |
In practice this means a camera doing forensic-grade ANPR at a gate needs roughly double the storage and bandwidth budget of the same-resolution camera doing general-purpose monitoring — a difference that's invisible if storage is quoted off resolution alone, and exactly the kind of interaction the coupled tool suite is built to catch.[5] The camera count and resolution decided upstream also directly determine two network loads that are easy to conflate but behave very differently:
| LAN Bandwidth (Camera → NVR) | Internet Upload Bandwidth (Remote Viewing) | |
|---|---|---|
| What it carries | Full-resolution mainstream video, all cameras, continuously | Lower-resolution substream, only while someone is watching remotely |
| Typical load | Larger — often the real bottleneck | Smaller — frequently over-budgeted |
| What breaks if under-sized | Dropped frames, switch congestion, recording gaps | Laggy or frozen remote viewing only |
| Common IT mistake | Ignored until switches choke at peak hours | Over-provisioned "just in case," inflating ISP cost |
"Nobody budgets for bandwidth until the switches start dropping frames during peak hours. Separating LAN load from internet upload load sounds obvious once you see it modelled — but almost no one asks for that distinction upfront." — IT infrastructure lead, mid-size manufacturing enterprise, on network planning for video surveillance
Tier 4 — CXOs & Owners: ROI and Risk, in Plain Language
The challenge: At board level, nobody asks about focal length. The questions are blunt: what does this cost, will it actually reduce loss and liability, and are we compliant. Technical proposals that don't answer these in plain language stall in approval queues for months — which is exactly where the pyramid's top tier gets stuck without the layers below it doing their job first.
The IndoAI leverage: Because the output from all four tools is grounded in verified math, it translates cleanly into a business argument — including the reframing below, which is often the moment a CXO stops treating the proposal as a cost centre and starts treating it as a risk-mitigation investment.
How the commercial model works: Running alongside the technical tools is what IndoAI's research paper calls the Appization layer — a licensing model that lets one camera or Edge Box run several AI "agents" concurrently (PPE detection, ANPR, fire/smoke detection, and so on). The CXO-facing output weighs a Growth subscription tier (illustratively priced around ₹1,499 per camera per month, lower upfront cost) against an Enterprise on-premise tier (higher upfront hardware cost, no recurring per-camera fee), alongside an ROI estimate built from expected reductions in compliance violations and incident-response time.[5]
Output: consolidated design summary from all four toolsThe Worked Example: Fewer, Better Cameras vs. More, Cheaper Ones
This is the single reframing that most often moves a CXO from "cost centre" to "risk mitigation investment": a smaller number of well-placed, higher-resolution cameras frequently beats a larger number of cheap, wide-angle ones — on both image quality and total cost, once rework is accounted for.
| Option A: 4 Wide-Angle Cameras (4mm lens) | Option B: 2 High-Res Cameras (6mm lens, 4MP) | |
|---|---|---|
| Camera count | 4 | 2 |
| Hardware cost / camera | ₹8,000 | ₹22,000 |
| Cabling & install / camera | ₹3,000 | ₹4,000 |
| Design subtotal | ₹44,000 | ₹52,000 |
| PPM achieved at walkway edge | ~60–70 px/m (Recognition grade) | ~260 px/m (Identification grade) |
| Rework after failed audit (1 extra camera + labour) | ₹15,000 | ₹0 |
| Total effective cost | ₹59,000 | ₹52,000 |
Option B costs ₹7,000 less once rework is included, and it clears the Identification threshold uniformly across the walkway instead of only in patches — the difference between footage that holds up in a loss-prevention review and footage that doesn't.
What These Tools Can't Do
Being direct about this matters more than the sales pitch: IndoAI's four tools model geometry, pixel density and lighting mathematically, but none of them can see your actual site. They don't account for physical obstructions (pillars, racking, signage), real-time local vendor pricing, or structural constraints in a heritage or leased building — the ₹ figures above are illustrative, not a quote. The DPDP compliance picture is also still moving: with full substantive obligations only phasing in through May 2027, these tools can help you design a defensible retention window, but they aren't a substitute for a legal compliance review.[4] Treat every output as a rigorous starting baseline for a site survey and a licensed integrator's sign-off, not as a final, installable design.
Why the Pyramid Works: One Design Language, Four Audiences
The strategic point isn't that IndoAI built four separate tools — it's that all four tiers draw from the same pixel-density and calculation logic. That shared baseline is what collapses the friction that normally exists between design, procurement, IT and finance: what the architect designs, the SI can price, the IT manager can safely host, and the CXO can confidently fund.
| Tier | Primary Buyer | Core Anxiety | What Changes |
|---|---|---|---|
| 1 | System Integrators | Losing bids or losing clients | Guesswork replaced by defensible, PPM-verified counts |
| 2 | Architects & BMS Consultants | Ugly, clashing retrofits | Security designed into the blueprint, not bolted on |
| 3 | IT Managers | Bandwidth chokeholds & DPDP risk | LAN vs. internet load modelled before a wire is run |
| 4 | CXOs & Owners | Cost, liability, ROI | Technical design reframed as a business case |
| — | Whole supply chain | Design vs. procurement vs. IT disputes | One number, agreed upon before installation begins |
What's Next: Describing a Site in Plain Language Instead of Filling Forms
The same research team is also studying a Vision Language Model (VLM) — an AI model that can reason over both images and text together — as a natural-language front end for this exact tool suite. The idea, described in the paper, is that a user could type something like "I need to secure a 500-metre dark perimeter fence line and identify licence plates at the gate," and have the model infer the structured inputs — target PPM, frame rate, retention window — that the calculators currently need entered by hand.[5] It's still R&D, not a shipped feature, but it points at where whole-project CCTV planning is headed next.
Run your own numbers before your next surveillance design
Four free, open-access CCTV and AI planning tools — coverage, camera count, lens selection, and low-light/aesthetic fit — no guesswork, no login wall.
Try the Tools at indo.ai/tools →Frequently Asked Questions
PPM measures how many pixels of a camera's image cover one metre of a scene at a given distance. It determines whether footage is merely detection-grade ("someone was there") or identification-grade ("that specific person"). Designing around a target PPM rather than a generic camera count turns a subjective layout into a verifiable engineering spec.
Yes. Camera Coverage & Layout, AI Camera Space Planner, Lens & Sightline Selector, and Low-Light/Aesthetic Check are all open access at indo.ai/tools, with no login wall for a baseline design.
It estimates the total camera count a space needs based on room area, room type, and a target pixel-density (PPM) grade, replacing flat rules of thumb like "one camera per 200 sq ft" with a number tied to the actual geometry of the space.
A high-resolution camera with the wrong focal length still fails to deliver identification-grade footage at the range you need — resolution and lens together determine the actual pixel density on your subject. The Lens & Sightline Selector matches focal length to distance and target PPM specifically to avoid this mismatch.
It checks whether a chosen camera and lens will still perform after dark, and flags whether the housing is discreet enough for aesthetically sensitive spaces like lobbies or retail frontages — two factors a pure geometry-based coverage tool doesn't account for.
Camera-to-NVR traffic runs at full resolution on the local network and is usually the larger load; remote viewing over the internet typically uses a lower-resolution substream. Treating these as one number leads IT teams to either overpay for internet bandwidth they don't need or under-provision the local switching capacity they do need.
Under the DPDP Act, 2023, footage that can identify a person is personal data, which brings notice, retention and security obligations into scope. The DPDP Rules, 2025 (notified 13 November 2025) phase in full substantive obligations by 13 May 2027, so retention-window planning done today should anticipate the stricter phase rather than only today's requirements.[4]
Coverage quality depends on pixel density at the point of interest, not raw camera count. Two well-placed, higher-resolution cameras can deliver identification-grade footage across an area that four wide-angle, lower-resolution cameras would only cover at detection-grade — often at a lower combined cost once rework is included, as shown in the worked example above.
No. The tools produce a mathematically verified baseline design from the dimensions and PPM targets you enter, but they can't see physical obstructions, real-time lighting conditions, or mounting constraints at your actual site. Treat the output as a starting point for a site survey and a licensed integrator's sign-off.
The Camera Coverage & Layout and Lens & Sightline tools give you the coordinates, angles and mounting-height data needed to position cameras accurately in a drawing, but the current tools don't export a native CAD file — architects typically transpose the calculated positions manually or via a coordinate export.
Both. New-build projects get the most value because placement can be designed before conduits are drawn, but retrofit projects benefit just as much from PPM-verified camera counts, correct lens selection, and bandwidth modelling before hardware is purchased.
Yes — each site is modelled individually against its own room dimensions and PPM targets, and the outputs from all four tools can be aggregated into a single multi-site BOQ, lens schedule, and network-load summary for procurement and IT planning.
There's no single right answer — retention should reflect your sector's audit requirements and a documented, defensible DPDP data-minimisation position rather than "store everything indefinitely." Many commercial deployments model 30–90 day windows as a starting point, then adjust for sector-specific compliance needs.
References & Further Reading
- Mordor Intelligence, "India Video Surveillance Market Size & Share Analysis," market sizing and DPDP compliance cost-impact estimate. mordorintelligence.com
- Axis Communications, "Pixel Density Based on IEC 62676-4:2014" white paper — DORI framework and px/m thresholds. whitepapers.axis.com
- asmag.com, "IEC 62676-4 Newly Released, Including Application Guidelines" (Oct 2025) — updated 2025 pixel-density recommendations. asmag.com
- Press Information Bureau, Government of India, "Digital Personal Data Protection (DPDP) Rules, 2025" notification and phased implementation timeline. pib.gov.in; primary Act text via meity.gov.in
- Gujar, V., Gujar, A., & Rathore, A. K. (2026). "Vision Language Models as the Reasoning Layer of an AI-CCTV Planning Toolkit: A Case Study of the IndoAI's Calculator Suite." Accepted for publication — source for the nine-tool Design/Size/Verify architecture, the storage/bitrate formulas, the Appization licensing model, and the VLM front-end research referenced in this article.
₹ figures in the worked cost example are illustrative estimates for FY2026, not vendor quotes. Run project-specific numbers via indo.ai/tools.