LoRaWAN público vs privado — lo cual encaja.
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 diferencia arquitectónica
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.
Cobertura — el factor 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.
Economía de costes — ¿qué gana?
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.
Seguridad y control
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 de proveedores y plataformas
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.
El híbrido es cada vez más común
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.
Preguntas frecuentes
¿Cuál es más barato — LoRaWAN público o privado?
Depende del número de dispositivos y la geografía del sitio. El público gana con pocos dispositivos en la cobertura de los operadores.
Ganas privadas por encima de ~500–2.000 dispositivos por sitio, o para despliegues fuera de la cobertura del operador. Modelamos ambos en la primera etapa.
¿Puede un dispositivo moverse entre redes públicas y privadas?
Sí, en principio — la Alianza LoRa ha estandarizado el roaming. En la práctica, el roaming público-privado aún no es plug and play y requiere una gestión cuidadosa de claves.
La mayoría de los despliegues híbridos segmentan los dispositivos por red en lugar de roamingarlos dinámicamente.
¿Qué tan fiable es Helium para uso empresarial?
El modelo operado por pares de Helium tiene una cobertura y calidad desiguales. Ha mejorado desde la migración a Solana, pero aún no es un operador empresarial estable en la mayoría de las regiones. La tratamos como una red complementaria, no como una principal.
¿Requieren las redes privadas LoRaWAN un mantenimiento continuo?
Sí — actualizaciones de firmware de gateway, parcheo de servidores de red, gestión de claves, monitorización. Normalmente unos pocos días de ingeniería al año para un despliegue estable.
Los acuerdos de servicios gestionados con TTI o Actility se encargan de esto para empresas que no desean la propiedad interna.
¿Dónde encaja el IoT CELULAR (LTE-M / NB- IoT) en esta comparación?
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.
Última actualización: