LoRaWAN vs NB-IoT vs Sigfox: Choosing the Right LPWAN Technology

The LPWAN Landscape

Low Power Wide Area Networks solve a specific problem: connecting thousands of sensors that send small amounts of data over long distances while running on batteries for years. WiFi drains batteries in hours. Cellular costs too much per device. Bluetooth doesn't reach far enough. LPWAN fills the gap.

Three technologies dominate this space: LoRaWAN, NB-IoT, and Sigfox. Each makes fundamentally different architectural decisions that affect everything from deployment cost to long-term flexibility.

LoRaWAN: Private Networks on Unlicensed Spectrum

LoRaWAN operates on unlicensed sub-GHz ISM bands (868 MHz in Europe, 915 MHz in North America). This is the defining characteristic that separates it from the other two options.

Range and Penetration: LoRaWAN achieves 3-15 km in rural environments and 1-5 km in dense urban areas. The sub-GHz frequency provides excellent building penetration—reaching basements, parking garages, and plant rooms that higher-frequency protocols cannot. A single gateway covers 3,000-5,000 square meters indoors, penetrating concrete, steel beams, and multiple floors.

Battery Life: Devices in Class A mode (the most common) achieve 5-10 years on a single battery. Sensors spend most of their time in deep sleep, waking briefly to transmit small packets. Typical payloads range from 51 to 241 bytes—perfect for temperature readings, meter pulses, GPS coordinates, and sensor status.

Network Ownership: You can deploy your own LoRaWAN network. Buy gateways, install a network server like ChirpStack, and you own the entire infrastructure. No monthly SIM fees, no carrier contracts, no dependency on a third party's business decisions. Data stays on your servers.

Ecosystem: The LoRa Alliance has over 500 members. More than 200 certified device manufacturers produce sensors for every imaginable use case. The open standard means you're never locked to a single vendor for hardware, software, or network infrastructure.

Security: Two layers of AES-128 encryption are built into the protocol. The Network Session Key ensures device authenticity at the network level, while the Application Session Key encrypts payload data end-to-end—meaning even the network operator cannot read your sensor data.

Capacity: A single gateway can handle thousands of devices, depending on transmission intervals and spreading factors. The adaptive data rate (ADR) algorithm automatically optimizes each device's transmission parameters for the best balance of range and airtime.

NB-IoT: Cellular Infrastructure, Carrier Dependency

NB-IoT (Narrowband IoT) operates on licensed cellular spectrum, deployed by mobile network operators as an overlay on existing LTE infrastructure.

Range and Penetration: Similar indoor penetration to LoRaWAN thanks to sub-GHz operation in some bands. Coverage depends entirely on your carrier's NB-IoT deployment—which varies dramatically by region. Rural coverage is often nonexistent because carriers prioritize urban areas where the business case is stronger.

Battery Life: Comparable to LoRaWAN in theory (5-10 years), but real-world results vary. The cellular protocol stack is more complex, and devices must maintain carrier registration, which consumes more energy than LoRaWAN's simpler Class A wake-transmit-sleep cycle.

Network Ownership: You don't own the network. Period. You pay per-device SIM fees to a carrier. If the carrier raises prices, changes terms, or discontinues NB-IoT service in your region, your deployment is at their mercy. Several carriers have already deprioritized NB-IoT in favor of other technologies.

Ecosystem: Growing but smaller than LoRaWAN. Device options are more limited, and each device requires a SIM card and carrier provisioning. Module costs are higher than LoRa equivalents.

When NB-IoT Makes Sense: Mobile deployments where devices move between cities or countries (though roaming adds cost and complexity). Situations where carrier-grade QoS guarantees are required by regulation. Locations where deploying your own gateway infrastructure is impossible.

Sigfox: Simple but Limited

Sigfox operates its own global network on unlicensed ISM bands, selling connectivity as a service.

Range: Excellent in areas with Sigfox coverage—up to 50 km in rural line-of-sight. But coverage is binary: either Sigfox has deployed infrastructure in your area or it hasn't. You cannot extend coverage yourself.

Battery Life: Outstanding. The ultra-simple protocol (no handshake, no acknowledgment by default) means minimal energy consumption.

Critical Limitations: Maximum 140 uplink messages per day with 12-byte payloads. Downlink is extremely limited (4 messages per day, 8 bytes each). This makes Sigfox unsuitable for any application requiring frequent data transmission, firmware updates, or real-time control. You cannot send commands to devices in any practical sense.

Network Ownership: You cannot deploy your own Sigfox network. You're entirely dependent on Sigfox's infrastructure and business viability. The company has faced financial difficulties, changed ownership, and modified pricing—all of which directly impact every deployment built on their network.

Head-to-Head Comparison

*Subject to regional duty cycle regulations (e.g., 1% duty cycle in EU868)

Decision Framework

Choose LoRaWAN when:

• You need to own and control your network infrastructure
• Data sovereignty matters (healthcare, industrial, government)
• You're deploying in a specific area where you can install gateways
• You need bidirectional communication (commands to devices, firmware updates)
• Long-term cost predictability is important (no recurring SIM fees)
• You want vendor independence and a large device ecosystem
• Indoor penetration is critical (basements, plant rooms, parking garages)

Choose NB-IoT when:

• Devices are mobile across wide geographic areas
• Carrier-grade service level agreements are legally required
• You cannot install any gateway infrastructure
• Higher data throughput per message is needed
• The carrier has strong NB-IoT coverage in your deployment area

Choose Sigfox when:

• You need very simple, very infrequent sensor readings (a few per day)
• Sigfox has coverage in your area
• Bidirectional communication is not needed
• Ultra-low per-device cost is the primary decision factor

The Total Cost Reality

Gateway and device hardware is only part of the equation. Over a 5-year deployment:

LoRaWAN: Gateway investment (~€300-600 each) plus devices (~€20-100 each). No recurring per-device fees if self-hosted. The network server runs on a basic Linux server. Total infrastructure cost is front-loaded and predictable.

NB-IoT: Lower upfront hardware cost per device, but each device incurs monthly SIM fees (€0.50-5/month depending on carrier and volume). Over 5 years, 1,000 devices at €2/month = €120,000 in connectivity fees alone—before counting the devices themselves.

Sigfox: Low device cost, annual per-device subscription (€1-7/year). But the 140-message daily limit and 12-byte payload severely restrict what you can build. Many projects outgrow Sigfox's capabilities within the first year.

Why Most Enterprise Deployments Choose LoRaWAN

The combination of network ownership, zero recurring fees, AES-128 encryption, a massive device ecosystem, and full bidirectional communication makes LoRaWAN the default choice for organizations that take IoT seriously. You're not renting someone else's infrastructure—you're building your own.

The unlicensed spectrum means no carrier negotiations, no roaming complications, no surprise price increases. The open standard means you can switch gateway vendors, device vendors, and network server software without rebuilding your deployment.

For organizations deploying hundreds or thousands of sensors in defined areas—buildings, campuses, farms, factories, cities—LoRaWAN delivers the lowest total cost of ownership with the highest degree of control.

What We Provide

We help organizations evaluate LPWAN options based on their specific requirements, then design and deploy the optimal solution. For LoRaWAN deployments: gateway placement, network server configuration, device provisioning, data pipeline setup, and Grafana visualization—delivered with full source code and documentation. No vendor lock-in, no recurring platform fees.

Related Articles

Industrial Retrofitting with LoRaWAN: Connecting Legacy Equipment

Open Source LoRaWAN Multiplexer and Protocol Converter

Open Source LoRaWAN Traffic Analyzer