For most of the last decade, the interesting work in connected devices happened in the cloud. The device sent its data up; the cloud thought about it; a decision came back down. Latency, bandwidth, and connectivity all tilted in favour of centralised processing.
That balance has shifted. Small, capable models now run on cheap silicon, in the field, with no round-trip. A camera can decide what it is looking at; a meter can classify what it is reading; a sensor can detect an anomaly without ever calling home. The architectural posture of IoT and embedded systems is being rewritten in real time.
This article is about what edge intelligence has unlocked, what new failure modes have arrived with it, and how a senior team approaches IoT engagements in this new shape.
Edge intelligence is no longer exotic
Models that mattered to industrial use cases now fit on devices that cost tens of dollars.
Two trajectories crossed in the last two years. Models got smaller and faster at the same task, and edge hardware got cheaper for the same compute envelope. The result is that capabilities that required a server eighteen months ago (vision classification, anomaly detection, simple language understanding) now fit on devices that cost less than the sensor next to them.
This unlocks a different system shape. Industrial monitoring can decide locally what is worth sending. Retail cameras can do counts and dwell-time analytics without sending video upstream. Logistics sensors can flag a problem inside a container before the container reaches a depot. The cloud is still in the loop, but it is no longer the only place decisions happen.
The economics also change. Bandwidth becomes cheaper because devices transmit decisions, not raw streams. Latency drops because decisions do not wait on a round-trip. And privacy improves, because the data that never leaves the device cannot leak from a centralised store.
Firmware, connectivity, and fleet operations
IoT engineering at SDEN still covers the work the discipline has always covered. Firmware development for the device itself, in C, C++, Rust, or a higher-level framework where the constraints allow. Connectivity: choosing the right radio (cellular, LoRaWAN, Wi-Fi, BLE) and the right protocol (MQTT, CoAP) for the use case. Secure provisioning: making sure each device has a verifiable identity from the moment it is manufactured. Edge-to-cloud pipelines: getting decisions, events, and telemetry to the cloud safely and cheaply. And fleet operations: software updates, observability, and incident response across thousands of devices in the field.
What is new is the AI layer that sits inside the firmware, between the sensor and the radio. The discipline absorbed it, but the operational realities (model updates, model drift, model evaluation in the field) are new responsibilities for an embedded team.
When the device decides, the device has to be observable
A device that classifies its own sensor data is a device whose classification can be wrong. The operational layer has to give the team the ability to know that, without sending every input upstream, because that defeats the point of edge computing.
The pattern that works is statistical: each device samples a small fraction of its decisions, with the inputs and the model output, and uploads the sample for evaluation. The team monitors the sampled accuracy over time, the distribution of decisions, and the gap between what the device says and what the centralised system would have said. When the metrics drift, the team retrains, redeploys, and tracks the change like any other production change.
This is a new operational discipline for most embedded teams. It is the one that decides whether the AI features in the firmware are a stable capability or a slow-moving liability.
Three defaults across every device engagement
These are the practices we hold to across firmware, fleet operations, and edge-to-cloud pipelines.
Secure provisioning from manufacture
Every device leaves the factory with a unique, verifiable identity. Devices that cannot be provisioned this way are not deployed; the security debt is too expensive to retrofit at scale.
Updateable, observably so
Firmware is updateable over the air, including the AI models at the edge. The update telemetry is observable: we know which devices are on which version at any moment.
Field-evaluated, not lab-trusted
Every edge model has a sampled evaluation loop in the field. We do not assume the lab numbers hold once the device is deployed; we measure.
A fleet that does the right thing, then tells you about it
A mature IoT deployment is felt as a quiet operations dashboard.
A working fleet is one where decisions happen at the device, anomalies surface at the centre, and the operations team trusts what they see. New devices come online cleanly. Updates roll out without surprises. Battery, signal, and accuracy stay within expected envelopes; when they do not, the dashboard says so before the customer does.
The technical artefact is a stack from firmware to cloud that one team can reason about. The cultural artefact is an operations team that does not flinch when the fleet grows by another order of magnitude.
When SDEN finishes an IoT engagement, the deliverable is the firmware, the OTA pipeline, the fleet observability, and the runbook for the next deployment. The handoff is the point.