Cost guide
IoT monitoring cost in India (2026): what a real deployment is made of
By Samuel Marndi · Updated
The short answer
The hardware is the small part. An industrial temperature and humidity sensor with Modbus output is ₹2,750–₹6,500, a LoRaWAN gateway ₹15,000–₹75,000 depending on indoor or outdoor — and the same measurement can be bought for ₹500 or ₹35,000, with accuracy class rather than brand explaining the gap.
What decides the real cost is the three things a hardware list does not show: how the devices get power and signal where they physically are, how the data reaches a screen, and who looks at the alert. A deployment that gets the first two right and the third wrong is a dashboard nobody opens, and that is the most common outcome in this field.
The hardware, as actually listed in India
These are seller listings, not quoted project prices, and the spread is real rather than noise — the cheap end is DIY-grade and the expensive end is certified instrumentation. Which one you need depends on what the number is for.
| Item | Indian listed price | When it is the right choice |
|---|---|---|
| DIY-grade temp/humidity sensor (SHT20, Modbus RS485) | ₹471 – ₹495 | Proving a concept, or monitoring where being 2°C out does not matter |
| Industrial temp/humidity probe (RS485 Modbus) | ₹2,750 – ₹4,500 | Most real deployments: cold rooms, server rooms, warehouses |
| Duct-mount industrial sensor | ₹6,500 | HVAC and airflow, where the sensor has to sit in the duct |
| Temp/humidity/CO₂ combo (Modbus/BACnet) | ₹12,500 – ₹17,500 | Occupied spaces and building management integration |
| Certified instrumentation (e.g. Thies class) | ~₹35,000 | Where the reading is evidence: compliance, pharma, calibration chains |
| LoRaWAN gateway, indoor | ₹10,980 – ₹15,000 | One building, sensors within a few hundred metres |
| LoRaWAN gateway, outdoor | ₹35,000 – ₹36,000 | A yard, a campus, or several buildings |
| High-spec outdoor gateway | ~₹75,000 | Long range, harsh environment, redundancy |
Why the same measurement costs ₹500 or ₹35,000
It is not brand premium. Four things separate the ends of that range, and only one of them appears on a datasheet people read.
- Accuracy class and drift. ±0.5°C holding over two years is a different instrument from ±2°C when new. If the reading triggers an action, or has to satisfy an auditor, the cheap one is not cheaper.
- Calibration traceability. A certificate linking the device to a national standard is what makes a reading defensible. Compliance work needs it; monitoring a server room does not.
- Enclosure and rating. An IP65 probe that survives washdown, dust and condensation against a breakout board that survives a bench.
- Expected life and support. Five years with spares available, against a part number that disappears when the supplier moves on — which matters more than the price when device nineteen of twenty fails.
- The rule of thumb: buy DIY-grade to prove the idea, then buy the industrial class for the deployment. Do not deploy the prototype, and do not buy certified instrumentation for a nice-to-have dashboard.
The five parts of a deployment, and which one is underestimated
Every IoT quote has these five. The one that is wrong in most of them is the second, because it is the only one that depends on your building rather than on a catalogue.
| Part | What it covers | What drives the cost |
|---|---|---|
| 1. Sensing | The devices that take the reading | Accuracy class, enclosure rating, and how many points |
| 2. Getting power and signal there | Cabling, conduit, mounting, local power, access | The building. A ceiling void is cheap; a live cold store at height is not |
| 3. Connectivity | LoRaWAN gateway, 4G SIM, or wired to an existing network | Range, obstructions, and whether a SIM per device or one gateway is cheaper |
| 4. Dashboard and alerting | Where the data lands, thresholds, who gets told | Self-hosted against a platform subscription, and how many users |
| 5. Keeping it honest | Calibration, battery replacement, dead-device detection | Device count, and whether the readings have to stay defensible |
The part nobody quotes: who looks at the alert
This is the difference between a monitoring system and an expensive telemetry hobby, and it costs nothing to get right at the design stage. Most failed IoT deployments I have seen did not fail technically. The sensors worked, the data arrived, the dashboard rendered — and nobody was accountable for acting on it, so within a quarter the alerts were muted and within a year nobody could say whether the system was still running.
Decide these five things before buying hardware, and write the answers down.
- What is the threshold, and who set it? A number somebody owns, not a default.
- Who gets told, on which channel, at 2am? Email is not an alerting channel for anything urgent.
- What are they expected to do? A documented response, or the alert is just information.
- How do you know a device has died? A sensor reading nothing looks identical to a sensor reading normal. Dead-device detection is a requirement, not a feature.
- Who re-calibrates, and how often? Drift is silent and it invalidates the record retrospectively.
Connectivity: LoRaWAN, 4G, or your existing network
| LoRaWAN | 4G per device | Wired / existing Wi-Fi | |
|---|---|---|---|
| Upfront | Gateway ₹11,000 – ₹75,000, then cheap per device | No gateway, SIM per device | Lowest, if the network reaches |
| Recurring | Minimal | A SIM bill per device, forever | None |
| Range | Hundreds of metres to kilometres | Wherever there is signal | Wherever your cable or AP reaches |
| Best at | Many devices, one site, low data | A handful of devices, scattered sites | Devices near existing infrastructure |
| Worst at | High data rates, or very few devices | Scale — the SIM bills compound | Anywhere the network does not already go |
| Break-even | Pays back against 4G at roughly 10–15 devices on one site | — | — |
How to buy this without wasting the budget
- Start with one question, not a platform. "Is the cold room ever going above 8°C overnight?" is a project. "Digital transformation of the facility" is a budget with no end.
- Pilot three devices, in the worst location. Not the easiest one. The pilot exists to find out what the building does to your signal, and the easy spot tells you nothing.
- Price the recurring cost over three years before you choose connectivity. A SIM per device looks cheap at four devices and absurd at forty.
- Own the data and the dashboard. Accounts in your name, data exportable. A platform you cannot leave will price accordingly once you depend on it.
- Budget for the second year. Calibration, batteries, and the two devices that will have died. A deployment with no maintenance line is a deployment with an expiry date.
- Agree what success is, numerically, before you start. "We will know within ten minutes if the temperature crosses 8°C, and the duty manager will be the one told" is testable. "Better visibility" is not.
FAQ
Related questions
How much does an IoT monitoring system cost in India?
The hardware is the small part: an industrial temperature and humidity sensor with Modbus output is ₹2,750–₹6,500, a LoRaWAN gateway ₹10,980–₹15,000 indoors or ₹35,000–₹36,000 outdoors, and certified instrumentation up to about ₹35,000 a point. What decides the project cost is installation access, connectivity choice and the dashboard — and those depend on your building, not on a catalogue, which is why a site assessment comes before a quote.
Why do IoT sensors range from ₹500 to ₹35,000 for the same reading?
Accuracy class and drift, calibration traceability, enclosure rating, and expected life with spares available. ±0.5°C holding over two years is a different instrument from ±2°C when new. If the reading triggers an action or has to satisfy an auditor, the cheap one is not cheaper. Buy DIY-grade to prove the idea and industrial class for the deployment — just never deploy the prototype.
Is LoRaWAN cheaper than 4G for IoT?
On one site with many devices, yes — a gateway at ₹11,000–₹75,000 then very little per device, against a SIM bill per device forever. It pays back against 4G at roughly ten to fifteen devices on a single site. For a handful of devices across scattered locations, 4G per device is simpler and cheaper. Price the recurring cost over three years before choosing, because a SIM per device looks cheap at four devices and absurd at forty.
What is usually missing from an IoT quote?
Three things. The installation reality — power, signal and physical access where the devices actually have to go, which is the only line that depends on your building. Dead-device detection, because a sensor reading nothing looks identical to one reading normal. And the second-year costs: calibration, batteries and the devices that will have failed.
Why do IoT projects fail?
Rarely technically. The sensors work, the data arrives, the dashboard renders — and nobody is accountable for acting on the alert, so within a quarter the notifications are muted and within a year nobody can say whether the system is still running. Decide the threshold, who is told at 2am, on which channel, what they are expected to do, and who re-calibrates, before buying any hardware.
Can I monitor temperature or energy without a big project?
Yes, and you should start that way. One question, three devices, in the worst location on the site rather than the easiest. That pilot costs very little, tells you what the building does to your signal, and either proves the value or saves you the rest of the budget. Scaling a working pilot is straightforward; rescuing a platform bought before anyone tested the signal is not.
Who should own the IoT dashboard and data?
You, with accounts in your name and data you can export in a usable form. A platform you cannot leave will price accordingly once you depend on it, and the data is the asset the project was for. Self-hosting is a legitimate option for a single site and often cheaper over three years than a per-device subscription.
Do IoT sensors need calibration?
The ones whose readings matter do, and drift is silent — it invalidates the record retrospectively, which is worse than a device failing outright. Compliance deployments need a calibration schedule and traceable certificates; a server-room dashboard does not. Decide which you are building before buying, because retrofitting traceability means replacing the sensors.