IoT Solutions
Connected-device software end to end: firmware integration, gateways, MQTT telemetry, OTA updates, fleet dashboards and alerting, secured throughout.
- MQTT and standard formats, so no single vendor owns your fleet
- Open protocols
- Devices and gateways buffer readings when the link drops
- Offline-first
- Staged firmware rollouts with automatic rollback
- Signed OTA
- Broker, data and dashboards in an account you own
- Your cloud
One reading, from the sensor to the screen
Software for fleets of connected devices, from the firmware's first publish to the dashboard an operator acts on.
Device
Firmware integration on microcontrollers and embedded Linux: sensor drivers, an MQTT client, local buffering and a device identity.
Gateway
Bridges Modbus, BLE, LoRaWAN or serial devices to MQTT, and stores readings while the uplink is down.
Broker
A clustered MQTT broker with per-device credentials, topic access rules and TLS on every connection.
Pipeline
Validates and stores telemetry in a time-series database, with rules that turn readings into events.
Applications
Fleet dashboards, alerting and the APIs your own systems call.
Every layer of a connected product
Firmware integration
Connectivity, telemetry and remote configuration added to your devices in C, C++ or Rust, working with your firmware team or hardware vendor.
Gateways and protocols
Edge gateways that speak Modbus, BLE, LoRaWAN or serial to the field and MQTT to the cloud, and keep data when the link drops.
Telemetry pipelines
MQTT ingestion, schema validation, time-series storage and stream rules that raise an event when a reading crosses a line.
Device management and OTA
Provisioning, a device registry, remote configuration and signed over-the-air updates rolled out in stages with rollback.
Dashboards and alerting
Live fleet views, per-device history, and alerts routed to email, SMS, push or your on-call tool, with escalation.
Security, device to cloud
Per-device credentials or X.509 certificates, TLS everywhere, least-privilege topic rules and an audit trail of every command sent.
A namespace your fleet can grow into
Topics and payload schemas are designed before the first device ships, because every device, rule and dashboard depends on them, and a renamed topic in the field means a firmware update.
- Hierarchical topics: organisation, site, device, then message type
- Versioned JSON or CBOR payloads with a published schema
- Per-device credentials that may publish only to their own branch
- Commands and acknowledgements on separate, audited topics
- acme/
- plant-2/
- press-04/
- telemetryreadings, QoS 1
- statusretained
- cmd/rebootcommand
- cmd/ackdevice reply
{
"v": 2,
"device": "press-04",
"ts": "2026-10-24T09:41:07Z",
"readings": {
"temp_c": 61.2,
"vibration_g": 0.42
},
"fw": "2.4.1"
}
Updates that roll out in rings
Provisioning, a device registry, remote configuration and signed over-the-air updates rolled out in stages with rollback.
Provisioning, the device registry and remote configuration sit in the same console, so the people who run the fleet can see what every unit is running and change it safely.
Built on our own products
Connected-device work is not new to us. These are our own products, built on the same pieces.
- Apexly productLaravel MQTTOur open-source MQTT client for Laravel: publish and subscribe between a Laravel back end, devices and brokers.
- Apexly productSmart Health EcosystemOur health platform streams vitals over MQTT, WebSockets and Redis Pub/Sub, with edge computing on STM32 wearables running Rust firmware.
Pilot on real devices, then scale
Discovery
Devices, connectivity, data volumes and who acts on which reading, written down before anything is built.
Pilot
A handful of real devices publishing end to end, from firmware to a working dashboard.
Scale-out
Provisioning, OTA and the pipeline hardened and load-tested for the full fleet.
Operate
Monitoring, alert tuning and runbooks handed over, with optional ongoing support.
Open protocols and tooling
- MQTT
- EMQX
- Mosquitto
- Rust
- Laravel
- TimescaleDB
- Grafana
- Docker
Frequently asked
Do you build the hardware?
Why MQTT?
What happens when a device loses its connection?
How are firmware updates kept safe?
Can it run in our own cloud?
Connect your first devices
Tell us what the devices measure, how they connect and who needs to act on the data. We will sketch the path from firmware to dashboard and what a pilot would prove.