Who this is for
Engineers and operations managers planning an IoT rollout across South African sites — factories, farms, water networks, mines, fleets — who need to choose a connectivity strategy before committing to hardware, and don't want to discover the coverage gap after installation.
Why this is harder in South Africa
Two local realities dominate the decision. First, coverage is uneven: cell networks are strong in metros and along corridors, then thin out fast on a farm or at a remote pump station. Second, load shedding means any link that depends on grid-powered infrastructure — including the cell tower itself — can go dark, so resilience and local buffering matter as much as raw throughput.
The four contenders, compared
| Network | Best for | Range / coverage | Power | Data per device | Watch-out |
|---|---|---|---|---|---|
| 4G / LTE | Few devices, anywhere with cell signal; gateways; video/rich data | National carrier coverage | Higher — mains or solar | High | SIM/data cost per device; tower depends on grid |
| LoRaWAN | Many low-data sensors over a site you control | Several km from your own gateway | Very low — years on a battery | Low | You run the gateway; not for rich data |
| NB-IoT | Low-data sensors where carrier has deployed it | Carrier-dependent, patchy | Low | Low–medium | Coverage varies sharply by area |
| Sigfox | Very simple, very low-data, low-cost devices | Operator network footprint | Very low | Very low (tiny payloads) | Single-operator lock-in; minimal data |
Why 4G is so often the practical answer
For many real projects — a dozen sensors at a plant, a few water points, an edge gateway pushing dashboards — 4G simply removes a problem: you don't build or maintain any network infrastructure, and it works the moment there's signal. The trade-off is per-device data cost and power draw, which is why 4G suits a smaller number of richer devices or a gateway that aggregates many cheap sensors behind it. In a country where the priority is usually "get it working reliably without a site-wide network project," that pragmatism wins a lot of the time.
When LoRaWAN is clearly better
The moment you have many low-data sensors spread across an area you control — a farm, a mine, a municipal reservoir network — LoRaWAN's economics dominate. One gateway covers kilometres, devices run for years on a battery, and there's no per-device SIM cost. The catch is that you own and power the gateway, and the link isn't for rich data. For soil moisture, tank levels, flow pulses and the like, that's exactly the right shape.
The hybrid that usually wins: LoRaWAN (or wired) for the many cheap sensors on-site, aggregated to an edge gateway, with 4G as the backhaul to the cloud — and local buffering so a tower or grid outage doesn't lose your data. You rarely pick one network; you layer them.
The decision, in five questions
- Coverage: Is there reliable cell signal at every device location? If not, you need your own gateway (LoRaWAN) or a different site plan.
- Device count: A handful → cellular per device. Dozens-to-hundreds → LoRaWAN behind a gateway.
- Data per device: Rich (video, high-rate) → 4G. Small periodic readings → LPWAN.
- Power: Mains/solar available → cellular is fine. Battery-for-years required → LoRaWAN/NB-IoT/Sigfox.
- Resilience: Whatever you choose, buffer at the edge so load shedding and tower outages don't lose data.
This is precisely the assessment we run at the start of every addaNet project — connectivity chosen per site, not per brochure — and why our platform supports all four. It's especially decisive for remote farms, water networks and mines.
Frequently asked questions
Is LoRaWAN or 4G better for a farm with poor signal?
If you have many sensors across the property, LoRaWAN almost always wins: one gateway at the homestead covers several kilometres, and devices last years on a battery. Use 4G as the backhaul from that gateway to the cloud. If you only have a couple of devices near a building with signal, 4G alone may be simpler.
Does NB-IoT work everywhere in South Africa?
No — NB-IoT coverage is carrier-dependent and uneven. It's excellent where your operator has deployed it, but you must confirm coverage at each device location before standardising on it. Don't assume metro coverage extends to your site.
What happens to my IoT data during load shedding?
It depends on your architecture. Edge devices and gateways that buffer locally keep logging and sync when power and connectivity return. Cloud-only setups with no buffering lose data during the outage — which is why we design for edge buffering on every South African deployment.
Is Sigfox a safe long-term choice?
It's cheap and simple for very low-data devices, but you're tied to a single operator's network footprint and very small payloads. For long-term, multi-site programmes we usually prefer LoRaWAN (you own the gateway) or cellular for flexibility.
Can one platform handle multiple networks at once?
Yes. addaNet is network-agnostic — LoRaWAN, NB-IoT, 4G, Sigfox or wired can all feed the same dashboards. That lets you choose the best link per site without fragmenting your data.