Is a connected object using LPWAN secure by default?
Not automatically — security depends on the technology and how it’s configured. Sigfox relies on frequency hopping and sequence numbers to protect against replay, without encrypting the payload itself by default; LoRaWAN, by contrast, implements encryption at three levels (device, application, network) — stronger protection, but only if the keys and network parameters are set up correctly, which adds integration work.
What’s the real security difference between Sigfox/0G and LoRaWAN?
Sigfox is effectively "plug & play" — no configuration, but no built-in payload encryption, relying instead on frequency hopping and sequence numbers against replay attacks. LoRaWAN requires setting up encryption keys and network parameters, often needing extra provisioning steps on-site, but in exchange offers three-level encryption. The trade-off is simplicity versus configurable strength.
How do you manage the lifecycle of a fleet of thousands of connected devices?
This is exactly the operational layer that basic dashboards skip: firmware updates, device provisioning, identity and access management, and regulatory compliance need to be handled continuously across the whole fleet, not just at deployment. It’s the reason IoT platforms are described as needing to evolve into "IoT ERPs" — lifecycle governance, not visualization, is the real core of an IoT system.