Custom IoT product development, from hardware to cloud.
Connected product design from one lead and a team of specialists: board, firmware, radio link, cloud and web, from first call to delivery. Three designs of our own show the range, each at its stated stage.
Just want monitoring deployed, not a custom build? See Paqett →
The problem
A connected product needs several kinds of engineering at once, and each depends on the others. We cover mechanical, electronics, firmware, radio, cloud and web. Our own designs, at their honest stages: a four-channel LoRaWAN temperature node, taken from schematic to a field trial of one unit; a three-board drone electronics stack, v0 designs in KiCad with no board built yet; and a cellular GPS tag with a complete schematic and layout in progress. Whether a project needs a custom board at all would be part of scoping. Sometimes a ready-made module on a small carrier board is enough, and we would say so. We would be plain about which of these pieces your project needs and which it does not.
What we'd build
Hardware, firmware, radio and cloud from one team
The full chain for a connected product, designed together. The details below come from our own designs, each at the stage described above. Where a project needs a different part, radio or cloud setup, the choice would be made for the product, not for our past builds. Which of these layers your product needs, and which it does not, would be settled first. The same lead would stay on the project from scoping to delivery, with specialists joining for the layers that need them, such as radio planning or cloud set-up.
| Layer | What we'd do | Detail |
|---|---|---|
| Hardware | PCB design from schematic through layout, with the mechanical side scoped with you where the product needs it. | Our designs use STM32WL (temperature node), STM32F405 (flight controller) and nRF9151 (GPS tag) |
| Firmware | Firmware that senses and reports on the schedule your product needs, and looks after itself where nobody can reset it by hand. | Update strategy, behaviour when the link is down and what the device reports about its own health |
| Radio | LoRaWAN, NB-IoT or BLE, chosen for the product and where it will be used. | Coverage surveys, gateway or modem choice and the data volume the product will send |
| Mechanical | Enclosures and fixings, where the product needs them, scoped with you at the start and shaped by where the product will live. | Environment, cleaning, access for batteries and how the product is mounted |
| Cloud and web | A network server, a telemetry database and the web side your own customers would see. | Our temperature node uses ChirpStack as its network server |
How working with us goes
- 01 Scope We agree what has to be built, where it lives and where the data goes.
- 02 Prototype Working hardware and firmware on your bench, tested against real conditions.
- 03 Pilot A small batch on real sites, with fixes folded back into the design.
- 04 Production Design for manufacture, a production run, and support once it is in the field.
Related
Legionella monitoring ·Cold chain monitoring ·Pharmaceutical cold chain ·Drones and aerial robotics ·LoRaWAN sensor design ·Low-power IoT design ·IoT dashboards and data pipelines · All sectors →
Have a connected product that needs building?
Custom hardware, firmware and software, from first sketch to production.
Talk to us about your project alessio.grespi@gmail.comWant it deployed, ready to run?
If you need monitoring rather than a new product, Paqett, our monitoring company, deploys it under your brand. Ask whether it fits.
See Paqett →