Why is the Lobaro Platform mandatory for NB-IoT Sensors & Gateways?

This common question often arises from integrators who run their own type of IoT platform tailored to a particular use-case. In contrast to this our platform is primary considered for device management of Lobaro and 3rd party sensors and gateways. It's meant as secure abstraction layer to the actual hardware and gives the following benefits to the integrator or end-user:

• Client and server certificate based secured data transfers using DTLS between hardware and Lobaro while maintaining battery lifetime friendly UDP data transfers over NB-IoT
• Functionality for remote configuration updates using simple standardized APIs (HTTPS PUSH, REST, MQTT, SFTP)
• Functionality to trigger remote firmware updates if new features become available or a security update must be deployed
• Providing a simple frontend for data retrieval independent of any upstream external system 
• Merging different sensor technologies (e.g. Wireless-MBUS, LoRaWAN, NB-IoT) to create a uniform interface for connecting external systems and platforms.
• Fast time to market for integrators and platform operators, as they can focus on the use case and data without having to deal with hardware-dependent implementation details of secure data transfers with unknown hardware.
• Small memory footprint can in most cases run in parallel to your own system on your server