This guide is for product owners, operations leads and IT managers who are scoping a connected product or a sensor rollout and must pick a network before the battery budget, the device contract and the platform are fixed. It sits under our IoT development service, which covers the device-to-cloud data path, the back end and the integrations; the radio itself is chosen with your device maker.
In this guide
- Why choose by device profile rather than by technology?
- What does each option do well, and where does it break?
- Which network fits which device profile?
- A five-question screen before you compare spec sheets
- Where AI fits
- What delivery record exists, and what does not
- Alternatives: what else can carry device data?
- What changes in the platform when the network changes?
- When not to choose a low-power network
- Limits of this guide
- Frequently asked questions
- Next step
Why choose by device profile rather than by technology?
Most comparisons list range, data rate and battery life per technology and end with "it depends". A device profile turns "it depends" into a short answer, because each profile rules out most options before any spec sheet is read. A profile is five facts about one kind of device: how it is powered, where it sits and whether it moves, how much it sends and how often, how fast a command must reach it, and who owns and pays for the network it uses.
A single project rarely has one profile. A warehouse can have mains-powered scanners, battery temperature tags on pallets and trucks that leave the site. Each profile gets its own network, and the platform has to accept all of them as one stream of readings with one device registry. That is why the choice belongs in scoping, not in procurement.
What does each option do well, and where does it break?
Wi-Fi gives high throughput on infrastructure most buildings already have, but a radio that stays associated keeps listening. Espressif's Wi-Fi low-power guide explains that keeping the connection means the RF module wakes for beacon intervals, so Wi-Fi suits mains power or a device that can recharge often.
Bluetooth Low Energy (BLE) is designed for very low power and supports point-to-point, broadcast and mesh topologies, according to the Bluetooth SIG technology overview, with data rates from 2 Mb/s down to 125 kb/s depending on the physical layer. It needs a phone or gateway nearby to reach the internet.
LoRaWAN trades data rate for range and battery life. The LoRa Alliance cites up to 15 km in rural areas and battery life of ten years or more, on private, public, community or satellite networks. In Europe, the 868 MHz sub-bands carry a 1% duty cycle, and The Things Network's public community network adds a fair-use limit of 30 seconds of uplink airtime and 10 downlink messages per device per day.
Cellular LTE-M and NB-IoT use operator networks, so coverage comes without your own gateways. Both support power saving mode (PSM) and extended discontinuous reception (eDRX). Onomondo notes that LTE-M supports seamless handover between cells and is ready for voice, while NB-IoT does not hand over seamlessly and has more limited roaming, with lower peak data rates.
Which network fits which device profile?
| Device profile | Default network | Coverage note | Battery note |
|---|---|---|---|
| Fixed device on mains power inside a building (gateway, camera, kiosk, machine controller) | Wi-Fi, or wired Ethernet where cabling exists | Depends on site access points and the IT team's network policy | Not a constraint; power and heat matter more |
| Battery sensor spread across a large site (farm, campus, yard, plant) | LoRaWAN with your own gateways | You control coverage; plan gateway positions and a cellular or wired backhaul | Multi-year battery is realistic for small, infrequent uplinks with Class A devices |
| Battery sensor at scattered fixed sites in public coverage (meters, tanks, cabinets) | NB-IoT, or LTE-M where NB-IoT is not offered | Depends on the operator; test signal at the real install points, including basements | Long battery life depends on PSM and eDRX settings the operator supports |
| Moving asset (vehicle, trailer, container, returnable crate) | LTE-M | Handover between cells and wider roaming; check roaming for every country on the route | Moderate; position fixes and frequent reporting drain more than the radio idle time |
| Wearable or handheld paired with a phone or nearby gateway | BLE | Short range; the phone or gateway carries data onward | Long battery life on small cells is typical for low duty cycles |
| High-data device (video, images, large logs, frequent firmware) | Wi-Fi or LTE Cat 1 and above | Needs a strong signal and a data plan sized for volume | Mains power or a large battery; low-power networks do not fit |
Mixed projects are normal: a common pattern is BLE or LoRaWAN at the edge with a Wi-Fi or cellular gateway carrying the readings to the platform.
A five-question screen before you compare spec sheets
-
Power source
Mains or frequent charging keeps Wi-Fi and full cellular open; a battery that must last years narrows the choice to BLE, LoRaWAN, NB-IoT or LTE-M with power saving.
-
Location and movement
Inside one building, across one site, at scattered fixed points, or on the move? Movement across cells points to LTE-M; one large private site points to LoRaWAN.
-
Payload and frequency
Write the message size and how often it is sent. A few bytes every few minutes fits every option; images, audio or large logs rule out LoRaWAN and NB-IoT.
-
Command latency
Decide how fast a command or configuration change must reach the device. LoRaWAN Class A devices only listen briefly after they send, so a downlink can wait until the next uplink; Class C listens continuously and is usually mains powered.
-
Network ownership
Choose who installs, monitors and pays for the network: your own gateways and backhaul, a community or public LoRaWAN network, a site Wi-Fi run by IT, or operator SIM contracts with roaming terms.
Answer the five questions per device profile, then test the shortlisted network at the real install points before the device order is placed.
Where AI fits
The network choice is an engineering decision; AI does not make it. AI earns its place after readings arrive: anomaly detection that flags a sensor whose pattern changes, gap detection that separates a dead battery from a lost signal, and forecasts of when a device will need a battery swap. AI with IoT is one of Netbase's AI capability areas, and Netbase works with the major commercial and open-source AI tools and models, chosen per project. Engineers still set the thresholds, check each alert against the device log and decide what triggers a site visit.
- In delivered work
Recommendation engine
A recommendation engine delivered for 4over4's online printing store; it is not an IoT system.
- Available capability
Anomaly detection on device readings
Flags unusual readings and silent devices for an engineer to review; not yet tied to a published IoT project.
What delivery record exists, and what does not
Netbase's lead offers are consulting, solutions, custom development and AI-enabled digital transformation, and its delivery practice covers mobile and IoT alongside API-first integration and security by design. Netbase has delivered projects for clients in manufacturing and logistics; these clients are not named, and one is described in an anonymous manufacturing and logistics platform record that states only the kind of platform and Netbase's role.
The closest registered device work is on phones, not sensors: Netbase builds and tests private SMS gateways on real Android devices, with an offline queue, recovery after reboot and network loss, and idempotent sends, as our Android SMS gateway guide explains. The same habits matter on any connected device whose network drops.
No IoT project is published yet. Netbase does not design radio hardware, certify devices or resell connectivity, and it publishes no battery result, coverage figure or device count of its own. Most Netbase projects are delivered on fixed-price contracts; milestone-based, monthly team retainer and KPI-linked models are also offered.
Alternatives: what else can carry device data?
- Wired Ethernet or fieldbus. Choose it for fixed machines on a plant floor where cabling already exists and radio interference is a risk.
- Zigbee, Thread or other mesh radios. Choose them for many low-power devices inside one building when a hub is acceptable; they still need a gateway to the platform.
- Wi-Fi HaLow or private cellular. Consider them for large sites that need more throughput than LoRaWAN with longer range than Wi-Fi, if module and access point supply suits your region.
- Satellite IoT. Choose it for remote assets with no terrestrial coverage, accepting small messages and a higher per-message cost.
- Store and forward. For devices that only need daily reporting, a device can log locally and upload when a phone, vehicle or gateway passes by.
What changes in the platform when the network changes?
The network sets limits the platform must respect. A low-power network means small messages, so the data model uses compact readings and the platform adds context from the device registry. Rare downlinks mean configuration and firmware updates must be planned per network, and some devices on LoRaWAN or NB-IoT need a different update path. Gaps are normal, so the platform should buffer on the device, accept late readings and alert on silence, not only on values. Once readings arrive, the choice between streaming and batch follows the business decision, as our guide on streaming or batch latency sets out, and the integration pattern follows our manufacturing and logistics workflow automation guide.
When not to choose a low-power network
Do not choose LoRaWAN or NB-IoT for devices that need frequent commands, large firmware images or live video. Do not choose Wi-Fi for a multi-year battery device. Do not choose BLE where no phone or gateway will be in range when data must move. And do not sign a device order before testing signal at the real install points, because published coverage maps and lab results do not show basements, steel racking or rural edges.
Limits of this guide
- Figures are vendor and alliance statements accessed on 2026-11-19; real battery life depends on reporting frequency, temperature, signal quality, retries and firmware.
- Regional rules differ: duty cycles, bands and operator support for LTE-M, NB-IoT, PSM and eDRX vary by country and operator.
- This guide covers the network choice only; device messaging protocols and edge processing are separate decisions.
Plan the next step with a Netbase consultant
Frequently asked questions
Both can run battery sensors for years when messages are small and infrequent. LoRaWAN suits a large site where you can place your own gateways and control coverage. NB-IoT suits scattered fixed sites inside an operator's coverage where you do not want to run gateways. Test the signal at the real install points before deciding.
A vehicle tracker should usually use LTE-M. LTE-M supports seamless handover between cells and has wider roaming agreements, while NB-IoT does not hand over seamlessly and fits devices that stay in one place. Check roaming for every country on the route.
Yes, and most real deployments do. Each device profile uses its own network and gateway, and the platform receives all readings through one device registry and one data model, with rules for late and missing readings.
Netbase helps define the device profiles and the platform requirements during discovery, and the radio and module are chosen with your device maker. Netbase does not design radio hardware, certify devices or resell connectivity contracts.
Next step
If you are scoping a connected product or a sensor rollout, write down your device profiles and book a solution review; we will map each profile to a network shortlist and the platform it needs.
Related services and solutions
IoT development with AI analytics that connects devices to the business Netbase provides IoT development for manufacturers, logistics operators and product companies to connect devices and sensor data to the business platforms that act on them, with AI that spots anomalies and forecasts what needs attention. We design the device-to-cloud data path, build the back end, dashboards and integrations, and treat security, data ownership and AI as design decisions.
Learn More
API integration services that keep your systems in agreement and ready for AI Netbase provides API integration services for commerce and operations teams that need e-commerce, ERP, CRM, shipping and payment systems to agree, so data moves once and AI services can act on it, with retries, monitoring and reconciliation on every API and webhook. According to its published client record, Netbase has worked with 500+ businesses across 80 countries since 2012.
Learn More
Enterprise integration hub ready for AI agents: one monitored layer for commerce, ERP and CRM data An enterprise integration hub is a central layer that moves orders, customers, stock and invoices between your commerce, ERP and CRM systems, with monitoring, retries and replay in one place, and scoped APIs that AI agents can call safely. Netbase builds it as a custom layer on the stack you already run, starting from the flows that break most often.
Learn More
Fleet and transport management software: orders, dispatch, tracking, drivers and vehicle costs on one record A fleet and transport management solution from Netbase is one system where planners turn orders into loads and routes, dispatch drivers, follow vehicles live and close each job with proof of delivery and its cost. We design and build it around your fleet, depots and customers, and add AI that suggests routes and flags delays while dispatchers decide.
Learn More
Work with Netbase remotely
Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.project@netbasejsc.com
+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.