The following diagram illustrates the Launcher architecture between Launcher software, mobile apps, the message broker and backends.
Launcher for Windows is the central piece of software for the Launcher solution. It uses Bluetooth Low Energy (BLE) to announce its presence to Launcher mobile apps.
Once a Launcher mobile app is detected, all communication between them is achieved over RabbitMQ (www.rabbitmq.com), secured by TLS.
Launcher mobile app
The Launcher mobile app (iOS/Android) acts as user identifier and allows users to interact with the Launcher software. The iOS version of the mobile app uses Bluetooth Low Energy to discover nearby devices that are running the Launcher software.
Once the Launcher software is detected, all communication between them is done over RabbitMQ (www.rabbitmq.com), secured by TLS.
Hosting, certifications and licensing
Our backends are hosted on Microsoft Azure. Azure’s data centres are geographically dispersed and comply to ISO/IEC 27001:2005, SOC 1 and SOC 2 and have a CSA STAR certification. The backend manages licensing and updates API REST, and it is only accessed by the Launcher software.
Backend communication with Launcher
Launcher backend is accessed by Launcher software and mobile apps, it is used for verifying that devices discovered through BLE are Launcher instances, and returns all information needed to establish a connection via RabbitMQ.
Encryption and certificates
Communication between our backends and the Launcher software and mobile apps, is encrypted and transmitted over HTTPS with 2048-bit asymmetric encryption and 256-bit symmetric encryption, using certificates from third party credited authorities.