Master’s in End-to-End IoT Platforms Engineering
Online master's programme of 1,900 hours in end-to-end IoT platforms engineering, structured in 12 modules covering IoT solution architecture, connected device design, connectivity, messaging protocols, cloud platforms, edge processing, IoT data, fleet lifecycle management and end-to-end security, with an assigned technical tutor.
Take the controls.
Run a real engineering trade-off from this programme. Move the sliders, watch the model react in real time and beat the challenge.
What you will be able to do
Design end-to-end IoT architectures with cost and scalability criteria.
Develop connected devices with secure firmware.
Select the right connectivity technology for each product.
Implement cloud IoT platforms and edge processing.
Manage the lifecycle of device fleets.
Apply security measures that comply with European regulations.
Develop a complete IoT solution from device to application.
Who it's for
- IoT solutions architects responsible for the full device-to-cloud chain.
- IoT platform engineers working with AWS, Azure or open-source platforms.
- Connected firmware developers who want to understand the cloud side.
- IoT data engineers building telemetry pipelines.
- IoT security engineers preparing products for European cybersecurity requirements.
- Connected product managers who need solid technical judgement.
- Engineering or science graduates aiming to work in consumer electronics.
What you'll work with
- ISO/IEC 30141 (IoT reference architecture)
- ETSI EN 303 645 (cybersecurity for consumer IoT)
- OASIS MQTT 5.0 (MQTT messaging protocol)
- IETF RFC 7252 (Constrained Application Protocol, CoAP)
- OMA LwM2M (lightweight IoT device management)
- Regulation (EU) 2024/2847 (Cyber Resilience Act)
- Regulation (EU) 2016/679 (General Data Protection Regulation, GDPR)
- NIST IR 8259A (IoT device cybersecurity capability core baseline)
- AWS IoT Core
- Azure IoT Hub
- ThingsBoard
- Eclipse Mosquitto
- Apache Kafka
12 modules · 1900 h
1.1Device, connectivity, platform and application layers1.2Functional and non-functional requirements1.3Reference IoT architecture patterns1.4Cloud, edge and hybrid deployment models1.5Total cost of ownership1.6Connected product lifecycle1.7ISO/IEC 30141 reference architecture1.8Documentation with the C4 model1.9Choice of suppliers and dependencies1.10Case study: architecture of a connected consumer product
2.1Selection of microcontroller and wireless SoC2.2Sensors, actuators and interfaces2.3PCB design and radio certification2.4Device power management2.5Real-time embedded operating systems2.6Embedded Linux with Yocto2.7Secure boot and root of trust2.8Factory provisioning2.9Design for manufacturing and testing2.10Practical: prototype with ESP32 and environmental sensors
3.1Wi-Fi, Bluetooth LE and Thread3.2Matter for the connected home3.3LTE-M and NB-IoT cellular networks3.4Public and private LoRaWAN networks3.5Low-throughput satellite connectivity3.6SIM and eSIM management3.7Connectivity selection by cost and consumption3.8Intermittent connectivity and local storage3.9Roaming and operator agreements3.10Lab: power consumption comparison between BLE and Wi-Fi
4.1MQTT 5 and its new features4.2CoAP and resource observation4.3HTTP and WebSockets on devices4.4AMQP for enterprise integration4.5JSON, CBOR and Protocol Buffers formats4.6Topic and schema design4.7Quality of service and guaranteed delivery4.8Payload compression and efficiency4.9Comparison of MQTT brokers4.10Workshop: designing the topic space for a fleet
5.1AWS IoT Core and associated services5.2Azure IoT Hub and DPS5.3ThingsBoard and Eclipse open platforms5.4Device registry and identity5.5Device shadows and twins5.6Rules engines and routing5.7Integration with serverless services5.8Multi-tenancy in IoT platforms5.9Vendor lock-in and portability5.10Practical: connecting a fleet to AWS IoT Core
6.1Gateways and edge nodes6.2Containers on edge devices6.3AWS Greengrass and Azure IoT Edge6.4Model inference at the edge6.5Local filtering and aggregation6.6Disconnected operation and later synchronisation6.7Workload orchestration at the edge6.8Updating edge applications6.9Hardware resources and limitations6.10Lab: TinyML inference on an edge node
7.1Large-scale data ingestion7.2Time-series telemetry storage7.3Data lakes and columnar formats7.4Stream processing7.5Sensor data quality and cleansing7.6Retention and storage costs7.7Descriptive analytics and dashboards7.8Machine learning on IoT data7.9Data access APIs7.10Practical: streaming pipeline with Kafka
8.1Secure onboarding and provisioning8.2Remote parameter configuration8.3Over-the-air firmware updates8.4Fleet health monitoring8.5Remote diagnostics and event logging8.6Decommissioning and end of life8.7LwM2M management protocol8.8Rollback and staged rollouts8.9Fleet reliability indicators8.10Case study: OTA strategy for 50,000 devices
9.1Threat modelling in IoT9.2Identity with X.509 certificates9.3Secure elements and TPM9.4Encryption in transit and at rest9.5Cloud platform security9.6Vulnerability management and SBOM9.7European Cyber Resilience Act9.8Penetration testing of devices9.9Incident response in fleets9.10Workshop: STRIDE threat model of a product
10.1Mobile apps for devices10.2Web dashboards for operators10.3Notifications and alerts10.4Integration with voice assistants10.5BLE provisioning interfaces10.6Accessibility and usability10.7Third-party APIs10.8Product usage analytics10.9Subscription and service models10.10Practical: device onboarding app
11.1Load testing with simulated devices11.2Platform observability11.3High availability and recovery11.4Cloud cost optimisation11.5Infrastructure as code11.6Continuous integration and delivery11.7Service level agreements11.8Compliance and data protection11.924×7 support and operations11.10Case study: simulating one million messages per minute
12.1Definition of the connected product12.2End-to-end architecture12.3Device design and prototype12.4Platform implementation12.5Security and fleet management12.6Scalability testing12.7Cost and feasibility analysis12.8Conclusions on the IoT solution12.9Master's Thesis report12.10Master's Thesis: defence before a panel
How you'll learn
100% online training on the SEIUM campus, with downloadable material, recorded classes and an assigned technical tutor. No fixed timetables: you progress at your own pace within each intake, so the programme fits around your job.
Each module combines theory, guided reading of the original standard and applied exercises. The working software is AWS IoT Core, Azure IoT Hub, ThingsBoard, Eclipse Mosquitto and Apache Kafka, in free, academic or evaluation versions. Testing is studied through real procedures: connecting and managing device fleets on cloud platforms, deploying over-the-air firmware updates, and load testing with simulated devices. Assessment is continuous by module, plus the final Master's Thesis.
Standards covered: ISO/IEC 30141, ETSI EN 303 645, OASIS MQTT 5.0, IETF RFC 7252, OMA LwM2M, Regulation (EU) 2024/2847, Regulation (EU) 2016/679, NIST IR 8259A.
Build it end to end
Your final project follows the real engineering workflow, step by step, reviewed by your tutor.
Where this takes you
Requirements
- A university degree in engineering, science or architecture, or equivalent demonstrable professional experience.
- An internet connection and a computer capable of running the programme's software.
- English sufficient to read technical standards.
Ready to start?
Send your application today. Our admissions team replies within 72 hours with your study plan and funding options.
Frequently asked questions
The programme totals 1,900 hours over 12–14 months. You set your own pace within each intake, and your tutor helps you plan the workload around your job.
You work with AWS IoT Core, Azure IoT Hub, ThingsBoard, Eclipse Mosquitto and Apache Kafka, using free, academic or evaluation versions. Your tutor indicates the free alternative wherever one exists.
A SEIUM Institute diploma, awarded on passing the continuous assessment and the Master's Thesis. It is SEIUM's own qualification, not an official state degree; its recognition depends on the programme completed and the regulations of each country.
Yes. Modules passed in a course or postgraduate diploma in the same area are recognised in the higher programme. Ask about the recognition policy when you enrol.
A university degree in engineering, science or architecture (or equivalent professional experience), a computer able to run the programme's software, and English sufficient to read technical standards.
Start dates are set by SEIUM's faculty for each intake. Our admissions team will confirm the next available date when you apply.
Related programmes
Master’s in 5G Millimetre-Wave Engineering
Online master's programme of 1,900 hours in 5G millimetre-wave engineering: 12 modules covering mmWave propagation, the 5G NR physical layer, beam management, mmWave integrated circuits, antenna-in-package,…
Master’s in Regulated Medical Design Engineering
Online master's programme of 1,900 hours in regulated medical design engineering, structured in 12 modules covering the MDR and FDA framework, ISO 13485 quality management, ISO…
Master’s in Industrial Protocols Engineering
Online master's programme of 1,900 hours in industrial protocols engineering, structured in 12 modules covering Modbus, Profibus and Profinet, EtherNet/IP and CIP, EtherCAT, CAN and CANopen,…
More in Electronics, Embedded Systems & Telecom
All Electronics, Embedded Systems & Telecom programmes → · How to apply · Fees & financing · Scholarships