Connected Device Prototype

From idea to a working connected device you can put in people's hands: ESP32 firmware, the radio, a custom board when a dev kit won't do, and the cloud backend and app behind it. One team, end to end, for prototypes and small batches.

Overview

Most connected-device projects stall at the seam between the hardware and everything behind it: a firmware contractor who has never run a backend, a cloud team that has never debugged a radio. We do both ends — electronics, firmware, cloud and app — so a prototype arrives as a working product rather than two halves that need introducing.

This is for prototypes, pilots and small production runs: a sensor network for a site, a product to put in front of your first customers, a device to prove an idea to investors. For runs in the thousands, we take the design to the point a contract manufacturer can quote it, and work alongside them.

How it goes

Prove it on a dev kit

• ESP32 dev kits and off-the-shelf sensor boards, so the first working version takes days rather than a board spin

• Firmware with secure provisioning and over-the-air updates from the start, because a device you can't update is a recall

Connect it

• Wi-Fi, Bluetooth LE or a sub-GHz radio, chosen for your range, power and environment

• A backend, dashboard or mobile app for the data, built to the same standard as the rest of our cloud work

Make it a product

• A custom board around a pre-certified radio module when the prototype has earned one

• Enclosure, power and battery life tuned for real use

• Small batches assembled through established PCB assembly services

Know what's needed to sell it

• A plain account of the certification your product needs for the markets you're selling in, before you commit to a launch date

Deliverables

• Working devices, firmware source and the update pipeline

• Schematics and board files when a custom board is part of the work

• The backend and app, in your accounts and repositories