Pubblico vs privato LoRaWAN — che si adatta.
LoRaWAN deployments split into public networks (carrier-run, subscription-based, where coverage exists) and private networks (you run your own gateways and network server, full control).
The right choice is highly use-case-dependent, and most mature enterprises end up with a mix. This is the operator-level comparison that helps procurement decide.
La differenza architetturale
Public LoRaWAN: you connect devices to a carrier's network (Orange / Bouygues / Objenious in France, KPN in Netherlands, Swisscom in Switzerland, Senet and Everynet in North America, Helium globally on a peer-operated model).
You pay per-device subscription; the carrier operates gateways and network server.
Private LoRaWAN: you operate your own gateways and network server (ChirpStack open source, The Things Industries, Actility ThingPark Enterprise) on your site. Devices connect only to your network. Capex up-front, no subscription, full control.
Copertura — il fattore decisivo
Public LoRaWAN coverage is excellent across most of Europe (carrier-run networks cover major countries comprehensively), patchy in North America (Senet, Everynet, Helium fill in but coverage is uneven), and limited in much of Asia, Latin America and Africa.
For deployments concentrated within carrier coverage, public is the fastest path to scale. For deployments spread across patchy or uncovered regions, private (or hybrid) is the only practical option.
Economia dei costi — quale vince?
Public: per-device subscription, typically 1–5 Euros per device per year for low-payload sensors, more for trackers. No upfront infrastructure capex.
Private: gateway capex (1,000–3,000 Euros each, you need 1–5 per site depending on size), network-server capex or licence (ChirpStack free, TTI / Actility commercial), operations overhead.
Breakeven happens around 500–2,000 devices per site, depending on density and gateway choice. Above that, private is usually cheaper TCO.
Sicurezza e controllo
Both use AES-128 encryption end-to-end. The security difference is operational. Public: traffic transits the carrier's network server; key management is shared. Private: you control the entire path, including device provisioning, network keys and routing.
For defence, critical infrastructure, regulated industries (pharma, financial-services field equipment, oil & gas) and sensitive corporate use cases, private is usually required for governance reasons even when public coverage exists.
Panorama dei fornitori e delle piattaforme
Public carriers: Orange Business / Objenious, Bouygues Telecom, KPN, Swisscom, Telekom Austria, Senet, Everynet, Helium (peer-operated).
Private network servers: ChirpStack (open source, dominant for self-managed), The Things Stack (TTI commercial + community), Actility ThingPark Enterprise (carrier-grade for large private deployments), AWS IoT Core (with LoRaWAN integration), Azure IoT Central.
Gateways: Kerlink, Multitech, Tektelic, Cisco, MikroTik — most work with both public and private. Devices: thousands of LoRaWAN-conformant sensors and trackers.
L'ibrido è sempre più comune
Many enterprises run both. Public LoRaWAN for assets that move across regions (returnable containers, livestock, mobile equipment) where carrier coverage exists. Private LoRaWAN for sensitive in-site applications (factory sensors, hospital staff, military / defence equipment).
Hybrid stacks use roaming standards to hand devices between networks. We design the network architecture in stage 1 — see /insights/lorawan-explained for the deeper technology treatment.
Domande frequenti
Quale è più economico — LoRaWAN pubblico o privato?
Dipende dal numero di dispositivi e dalla geografia del sito. Il pubblico vince con pochi numeri di dispositivi nella copertura degli operatori.
I privati vincono oltre ~500–2.000 dispositivi per sito, oppure per implementazioni fuori dalla copertura degli operatori. Modelliamo entrambi nella fase 1.
Un dispositivo può muoversi tra reti pubbliche e private?
Sì, in linea di principio — l'Alleanza LoRa ha standardizzato il roaming. In pratica, il roaming pubblico-privato non è ancora plug-and-play e richiede una gestione attenta delle chiavi.
La maggior parte delle implementazioni ibride segmenta i dispositivi per rete invece di roaming-li dinamicamente.
Quanto è affidabile Helium per l'uso enterprise?
Il modello peer-operated di Helium ha una copertura e una qualità disomogenee. È migliorato dalla migrazione a Solana, ma non è ancora un operatore enterprise stabile nella maggior parte delle regioni. Lo trattiamo come una rete supplementare, non primaria.
Le reti private LoRaWAN richiedono manutenzione continua?
Sì — aggiornamenti firmware gateway, patching del server di rete, gestione delle chiavi, monitoraggio. Tipicamente qualche giorno di ingegneria all'anno per una distribuzione stabile.
Gli accordi di servizi gestiti con TTI o Actility si occupano di questo per le imprese che non desiderano la proprietà interna.
Dove si collocano i cellulari IoT (LTE-M / NB-IoT) in questo confronto?
Cellular IoT is the other LPWAN option. NB-IoT and LTE-M are carrier-managed, globally available where cellular exists, and integrate naturally with mobile devices.
LoRaWAN wins on cost-per-device at scale and on private-network capability; cellular wins on global mobility and standardised interoperability. Most enterprises run both for different use cases.
Ultimo aggiornamento: