Introduction
Most LPWAN comparison posts do the same thing: list specs, draw a table, declare a winner. That works if you are buying a USB cable. It does not work when you are deploying 500 sensors across a cement factory in Pune or rolling out smart water meters across a mid-size Indian city.
This post is different. We will compare LoRaWAN, NB-IoT, and Sigfox on the dimensions that actually matter in Indian industrial and smart-city deployments range in harsh terrain, battery life in high-temperature environments, cost per node over five years, and network ownership. And where generic posts stop at theory, we will fill those gaps with specific numbers from real Uniconverge deployments.
Uniconverge Technologies builds and deploys end-to-end LPWAN infrastructure: LoRaWAN end-devices, industrial gateways, and the cloud layer that ties it all together. We work across LoRaWAN, NB-IoT, and hybrid setups, and we have a point of view on when each one earns its place.
What Is LPWAN?
LPWAN stands for Low-Power Wide-Area Network. The category exists because standard wireless options do not fit most industrial IoT use cases.
Wi-Fi has too short a range. Cellular (4G/5G) burns battery and costs too much per node when you are running thousands of sensors. Bluetooth barely leaves the room.
LPWAN trades raw speed for three things: long range (5 to 40+ km depending on technology and terrain), multi-year battery life, and low cost per node. For applications where a sensor sends a small packet every few minutes a temperature reading, a vibration anomaly flag, a meter value that trade-off is the right one.
The verticals where LPWAN has proven practical:
- Smart metering (electricity, water, gas)
- Industrial predictive maintenance (vibration, temperature, pressure)
- Asset and tool tracking across large facilities
- Smart city infrastructure (bins, parking, street lighting, air quality)
- Remote utility monitoring (pipelines, water treatment, substations)
- Agriculture (soil moisture, micro-climate, irrigation control)
LoRaWAN, NB-IoT, and Sigfox: Quick Orientation
LoRaWAN uses an unlicensed radio spectrum (865-867 MHz in India) and an open protocol stack maintained by the LoRa Alliance. Organizations can deploy their own private gateways and own the entire network, or connect to a public network operator. It is the only one of the three that gives you genuine infrastructure ownership.
NB-IoT (Narrowband IoT) is a 3GPP standard that runs on licensed cellular spectrum, managed by mobile operators. In India, Reliance Jio and Airtel both offer NB-IoT. You buy SIM cards, pay per device, and let the carrier handle coverage. The trade-off for that convenience is operator dependency.
Sigfox is a single-vendor, subscription-only network. You cannot deploy your own infrastructure. Global coverage is uneven, and in India it is limited to specific zones. For most Indian industrial or municipal deployments, Sigfox is a distant third option.
Comparison Criteria
Before the tables, here are the dimensions we use when evaluating LPWAN for a new deployment:
- Range and indoor/outdoor coverage
- Data rate, payload size, and latency
- Power consumption and battery life
- Network ownership (private, public, hybrid)
- Total cost: modules, gateways, SIM/subscription fees, and OPEX over five years
- Security model and ecosystem maturity
Range, Coverage, and Penetration
| Technology | Typical Urban Range | Typical Rural Range | Deep Indoor |
| LoRaWAN | 2-5 km | 5-15 km | Good (SF12) |
| NB-IoT | ~1-3 km (cell-limited) | Operator coverage-dependent | Excellent |
| Sigfox | 3-10 km | Up to 40 km (ideal) | Moderate |
The numbers above are reasonable starting points. Real-world performance in India often looks different.
LoRaWAN range in dense industrial areas think a steel plant in Jharkhand or a refinery on the Gujarat coast tends to drop to 1-3 km due to metal structures, heavy machinery, and RF interference. The fix is gateway placement: add more gateways, position them strategically, and use Spreading Factor 12 for hard-to-reach nodes. Uniconverge’s UG-series industrial gateways (IP67-rated, 8-channel, DIN-rail or pole-mount) are built for exactly this environment. A typical factory deployment uses four to six gateways to cover a 500,000 sq ft facility with redundant coverage.
NB-IoT coverage depends entirely on which operator you are using and whether they have deployed the technology in your area. In Indian metros and large tier-2 cities, coverage is generally solid. Remote sites a mining operation in Rajasthan, a water treatment plant in a peri-urban area may have no NB-IoT coverage at all. LoRaWAN private infrastructure does not have this limitation.
Sigfox coverage in India is thin. For any serious industrial or municipal deployment, it is not a realistic option today.
Data Rate, Payload, and Latency
| Technology | Max Data Rate | Max Payload | Typical Latency | Best Fit |
| LoRaWAN | 0.3-50 kbps | ~250 bytes | 1-5 seconds | Low-frequency sensor data |
| NB-IoT | 20-250 kbps | ~1600 bytes | 1-10 seconds | Larger payloads, firmware OTA |
| Sigfox | 100 bps | 12 bytes uplink | Several seconds | Ultra-simple, infrequent alerts |
For most industrial IoT use cases, LoRaWAN’s payload limit is not a constraint. A vibration sensor sending a 64-byte packet every five minutes RMS acceleration values, temperature, timestamp, device ID fits comfortably in a single LoRaWAN frame. A water meter sending daily consumption data? Same.
NB-IoT’s larger payload capacity becomes useful when you need to push firmware over the air, stream short audio or video clips, or aggregate data from multiple sub-sensors before sending. If your application involves burst data, NB-IoT is the better fit.
Sigfox’s 12-byte uplink limit is severely restrictive. It works for simple binary alerts (pump on/off, door open/closed) but breaks down the moment you need richer data.
Power Consumption and Battery Life
This is where LoRaWAN tends to win for battery-powered deployments.
| Technology | Typical Battery Life (AA, low-frequency use) | Sleep Current | Active Tx Current |
| LoRaWAN | 10-15 years | ~1-2 µA | ~40 mA peak |
| NB-IoT | 5-10 years | ~3-5 µA | ~200-300 mA peak |
| Sigfox | 10-15 years | ~1 µA | ~35 mA peak |
These numbers assume sensors transmitting small packets at 10-15 minute intervals and spending most of their time in deep sleep. In real deployments, battery life depends on transmission frequency, payload size, distance to gateway (which affects retries), and ambient temperature.
Uniconverge’s LoRaWAN end-devices for factory environments are designed around a 14-15 year battery life target on a standard 3.6V lithium-thionyl-chloride cell. The devices use adaptive data rate (ADR) to reduce transmission power when the gateway is nearby, and stay in EM4 deep sleep between samples. In a comparable NB-IoT setup same sensor, same transmission frequency measured battery life came to 6-7 years, driven by NB-IoT’s higher peak current during radio acquisition.
For deployments where power is available (plugged-in gateways, panel-mounted controllers), this difference does not matter. For remote or field-deployed sensors where battery replacement is expensive or impractical, it is the deciding factor.
Network Architecture and Ownership
This is the dimension most comparison posts gloss over, and it matters enormously in Indian industrial deployments.
LoRaWAN gives you three options:
- Private network: you own the gateways, run your own network server (like ChirpStack), manage devices yourself. No subscription fees, full data sovereignty.
- Public network: you connect to a third-party network operator (TTN, Everynet, etc.) and pay per device.
- Hybrid: private gateways inside the facility, public network as backup outside.
For factories, refineries, and large campuses, private LoRaWAN is almost always the right architecture. Data stays inside your infrastructure, there are no per-device monthly fees, and you control the SLAs.
NB-IoT is operator-managed by definition. You are buying connectivity from Jio or Airtel, with all the dependencies that implies: their coverage, their pricing, their network policies. If you are deploying city-wide smart meters where cellular coverage is reliable and infrastructure ownership is not a priority, NB-IoT makes sense. If you are running a private factory network where data sensitivity or coverage reliability matters, it is a harder sell.
Uniconverge hybrid deployments which have become increasingly common use LoRaWAN inside facilities for dense sensor coverage and NB-IoT for widely distributed assets in the field (remote pump stations, distribution transformers, outdoor kiosks). The two networks feed into a unified cloud dashboard, giving operators a single view regardless of the underlying radio technology.
Cost Comparison
These are relative ranges, not fixed prices hardware costs vary by vendor and volume, and NB-IoT subscription rates differ by operator and tier.
| Cost Element | LoRaWAN | NB-IoT | Sigfox |
| End-device module | ₹400-800 | ₹600-1200 | ₹800-1500 |
| Gateway (per unit) | ₹25,000-80,000 | None needed | None needed |
| Network OPEX (per device/year) | ₹0 (private) | ₹200-600 | ₹500-1000 |
| 5-year TCO (500 nodes, private) | Moderate (upfront) | Higher (recurring) | High + limited coverage |
The LoRaWAN gateway cost looks like a disadvantage at first. For small deployments under 100 nodes, it can be. For 500+ nodes over five years, private LoRaWAN infrastructure typically shows 40%+ lower total cost compared to NB-IoT subscriptions at scale because gateway hardware is a one-time investment, while NB-IoT SIM costs compound annually.
Uniconverge’s UC-Sensor Suite packaged bundles of vibration, temperature, or current sensors with pre-configured LoRaWAN firmware reduces integration time and brings per-node cost down through volume pricing. A typical 300-node factory deployment using UC sensors and UG-series gateways pays back the infrastructure cost in under 18 months through reduced maintenance labor and downtime.
Security, Reliability, and Ecosystem
NB-IoT inherits cellular-grade security: SIM-based authentication, network-level encryption, and carrier-managed key management. For organizations that want security handled at the operator layer with minimal configuration, this is an advantage.
LoRaWAN uses AES-128 encryption with two layers (network and application). Security is solid when properly configured, but it requires the deploying organization to manage keys and device provisioning. Misconfigured LoRaWAN deployments default keys, no join-server hardening are a real vulnerability. Uniconverge ships devices with per-device unique keys and runs a hardened join server with device identity management.
Beyond encryption, Uniconverge’s industrial gateways include:
- Edge-level packet filtering (whitelist-only device EUIs)
- Encrypted backhaul (VPN to cloud platform)
- Physical protection: IP67 enclosures, -40°C to +70°C operating range, surge protection for lightning-prone rural sites
Sigfox uses lightweight proprietary encryption. It works for low-sensitivity applications but lacks the flexibility and auditability of LoRaWAN or NB-IoT.
Uniconverge Deployments: Where Theory Meets Practice
1. Industrial Predictive Maintenance
A large automotive component manufacturer running three-shift production deployed 520 LoRaWAN vibration sensors on motors, pumps, and compressors across two factory buildings. Six UG-series gateways cover the entire facility with redundant paths.
The sensors send 64-byte packets every 5 minutes containing RMS acceleration (three axes), peak velocity, bearing temperature, and an anomaly flag set by edge firmware. Data feeds into a cloud dashboard with threshold alerts and trend visualization.
Result: bearing failures flagged an average of 6-9 days before physical failure, cutting unplanned downtime by approximately 25% in the first year. Battery life on CR123A cells has tracked to 12+ years at current transmission frequency.
2. Factory Asset Tracking
A tooling manufacturer struggled with lost fixtures, jigs, and calibrated tools across a large production facility and an adjacent storage yard. They deployed 180 LoRa-enabled tags across the assets and mounted four gateways to cover both areas.
Each tag transmits a location beacon every 15 minutes, accurate to the gateway sector (~50m zones). Wi-Fi RTLS was evaluated but required 30+ access points at three times the infrastructure cost. BLE tags gave insufficient range for the yard area.
3. Smart City Infrastructure
A municipal pilot in a mid-size city deployed 800 LoRaWAN-connected smart waste bins and 120 smart street-light controllers across a 12 km² zone. Fill-level ultrasonic sensors in bins transmit every 4 hours. Streetlight controllers respond to on/off commands within 2 seconds.
Twelve LoRaWAN gateways (pole-mounted, IP67) cover the zone with 99.6% uplink success rate over six months of operation. The infrastructure runs on a private LoRaWAN server, with no recurring per-device subscription costs.
4. Remote Utility Monitoring
A water utility managing rural distribution across scattered pump stations and storage tanks needed remote monitoring without cellular coverage in several zones. They deployed a hybrid setup: NB-IoT for sites inside cellular coverage (64 sites), LoRaWAN with dedicated small gateways for remote sites (28 sites).
Both networks feed into a unified SCADA-layer dashboard. Battery life on the LoRaWAN nodes at remote sites is projected at 10 years at the current 30-minute transmission interval.
5. Battery Life Comparison: LoRaWAN vs NB-IoT in the Field
A process automation customer ran a side-by-side pilot: identical temperature and vibration sensors, identical transmission schedule (every 10 minutes), one batch on LoRaWAN and one on NB-IoT. After 18 months of monitoring and extrapolation:
- LoRaWAN nodes: projected 13-15 year battery life
- NB-IoT nodes: projected 6-7 year battery life
The NB-IoT nodes required more frequent radio scans due to occasional weak carrier signal at some sensor locations inside a building with metal roofing. That search-and-attach cycle is the single biggest battery drain in NB-IoT. In the same location, LoRaWAN gateways were ceiling-mounted, so path loss was minimal and retransmission rates were under 3%.
How to Choose: A Decision Framework
This is not a flowchart. It is a set of honest questions.
Choose LoRaWAN if:
- You want infrastructure you own and control
- Battery life is critical (10+ years, no replacement budget)
- You are deploying inside a facility or campus where you can mount gateways
- You need to keep data inside your own network
- OPEX over five years matters more than upfront hardware cost
Choose NB-IoT if:
- You are deploying widely distributed outdoor assets in areas with solid cellular coverage
- Your payload requirements are above 250 bytes, or you need OTA firmware updates
- You want zero gateway infrastructure on your end
- Carrier SLAs are acceptable for your reliability requirements
Consider Sigfox only if:
- Your use case involves simple binary alerts, ultra-low data, and very low transmission frequency
- You are specifically operating in a region with solid Sigfox coverage
- Cost per node is the overriding constraint
Quick checklist before starting a PoC:
- What is the coverage area (indoor, outdoor, mixed)?
- How many nodes? What is the 5-year budget?
- What payload size and transmission frequency does your application need?
- Do you need private network ownership or is carrier-managed acceptable?
- What are the battery replacement economics at scale?
- Is cellular coverage reliable at every deployment site?
Why Partner with Uniconverge Technologies?
Most LPWAN deployments that struggle do not fail because of technology choice. They fail because the sensors, gateways, network server, and cloud layer were sourced from four different vendors who never validated their integration together.
Uniconverge builds the full stack: end-devices (vibration, temperature, current, level, pressure), industrial gateways (UG-series, tested to IP67 and IK10), network server layer (private or hybrid), and cloud dashboards with alerting and analytics. Every component is pre-validated end-to-end before it ships to a customer site.
We also run PoC projects before full deployment typically 30-90 days, 20-50 nodes, at a target site. The PoC answers the coverage, battery, and integration questions before you commit to a full rollout.
If you are evaluating LPWAN for a factory, utility, or city infrastructure project, we are available for a technical consultation. No sales pitch just a conversation about what your application actually needs.
Summary Table
| Dimension | LoRaWAN | NB-IoT | Sigfox |
| Frequency band | Unlicensed (865 MHz IN) | Licensed cellular | Unlicensed (865 MHz IN) |
| Typical range (urban) | 2-5 km | Carrier-dependent | 3-10 km |
| Max payload | ~250 bytes | ~1600 bytes | 12 bytes |
| Battery life (low freq) | 10-15 years | 5-10 years | 10-15 years |
| Network ownership | Private/public/hybrid | Carrier only | Public only |
| India coverage | Self-deployable anywhere | Urban and major towns | Limited |
| 5-yr TCO at scale | Low (private) | Moderate-High | High |
| Best for | Industrial IoT, smart city | Distributed outdoor, OTA | Simple alerts only |
Uniconverge Technologies designs and deploys LPWAN infrastructure for industrial, utility, and smart city customers across India. Products include the UG-series LoRaWAN industrial gateways, UC-Sensor Suite, and a managed IoT cloud platform.
