IoT & Smart Systems.

Edge when latency must be under 100ms, bandwidth is expensive or unreliable, or privacy demands data not leave the device. Cloud-only when devices have stable connectivity and centralized analytics is the goal. Most production deployments end up hybrid: edge for filtering, anomaly detection and control loops; cloud for aggregation, long-term storage and model retraining. We design the split based on payload size, decision latency and connectivity reality.

MQTT for most fleets because it's battery-friendly, supports pub/sub topology, and brokers like HiveMQ, EMQX and AWS IoT Core handle scale well. CoAP for severely constrained devices or LPWAN networks where every byte counts. HTTP only when devices are infrequent reporters and integration with existing REST APIs outweighs protocol overhead. We pair the choice with TLS, mutual auth and device-identity rotation - protocol selection without security is a non-starter.

LoRaWAN via private gateways works well for agriculture, utilities and asset tracking across rural Ghana, Kenya and Nigeria. NB-IoT and LTE-M coverage is growing - MTN and Safaricom have credible footprints in major corridors. Satellite IoT (Swarm, Sateliot) becomes viable for genuinely remote deployments. We design network choice based on data rate, latency, coverage maps and total cost of ownership over a 5-year horizon, not just upfront device cost.

We use AWS IoT Device Management, Azure IoT Hub Device Provisioning Service, or Mender for OTA firmware updates, with staged rollouts, A/B groups and automated rollback on failure. Each device has a unique identity (X.509 cert or hardware-backed key), shadow state for offline reconciliation, and telemetry feeding a fleet health dashboard. At 10,000+ devices, manual operations break - we plan for fleet operations from day one.

Hardware-rooted identity where the silicon supports it (ATECC608, TPM), signed firmware with secure boot, encrypted communication via TLS with mutual auth, no shared secrets across the fleet, and automated certificate rotation. We follow IoT Security Foundation guidelines and ETSI EN 303 645. IoT devices are easy targets - cameras and routers shipped with default passwords have fed every major botnet, and we won't be part of that pattern.

We design the firmware (typically C or Rust on STM32, ESP32, nRF52), partner with PCB and enclosure manufacturers for industrial design, build the device-management backend, and ship the operator dashboards. For pure consumer-electronics ID and manufacturing-line setup we partner with specialists. Our sweet spot is industrial and B2B IoT - water meters, fleet telematics, agricultural sensors, utility monitoring.

If existing operators already have line-of-sight to assets and a clipboard is good enough, a mobile app for the operator is cheaper and faster. If devices need to be deployed and forgotten for 10 years in harsh conditions, the upfront engineering and certification costs may not pencil out. We push back when 'IoT' is the answer to a question that didn't need silicon - sometimes the right answer is a barcode and a phone.