IoT & Embedded Product Engineering
From Circuit to Cloud — Hardware, Firmware & Software Engineering.
Every microamp counted. Every packet accounted for.
From custom electronics and PCB design to embedded firmware, cloud platforms and IoT software, BuildIoT Lab delivers practical engineering solutions with clear documentation and maintainable handover.
Connected products need hardware, firmware and software that work together. We design the electronics, develop the embedded systems, build the supporting applications and document the handover.
An electronics design you can explain, build and test.
We turn a connected-product idea into a system architecture and a circuit design: sensor interfaces, power, radios and protection. Low-power design is a speciality: we budget where the charge goes in each state and change the design until the budget holds.
ESP32 family, STM32, Sensor interfaces (I²C, SPI, UART, ADC), Li-ion and LiPo power, Low-quiescent regulators
IoT Hardware R&D & Design in detail
Board files a fabrication house can build from.
Schematic capture, 2- to multilayer layout, stack-up, design-for-manufacture review and component selection. We supply the digital output a board house or assembler needs; we do not run manufacturing or assembly ourselves.
Schematic and layout CAD, Multilayer stack-ups, DFM checks, Gerber and drill output
Devices that recover on their own.
Firmware in C and C++ for ESP32 and STM32, with FreeRTOS where the job needs it. We design for the bad day: a brownout, a dropped link, a sensor that stops answering, an update that fails halfway.
ESP-IDF, STM32Cube HAL and LL, FreeRTOS, C, C++17, BLE, Wi-Fi, MQTT, LoRa
Data that arrives in order and survives a dropped link.
From the device to the screen: web dashboards, mobile apps, backend and APIs, MQTT and cloud services, telemetry pipelines and device management. Reliable delivery is a speciality: buffering on the device while the link is down, ordered ingestion, and alerts people will act on.
MQTT, TLS, Mosquitto, EMQX, InfluxDB, Grafana, Node.js, Docker
IoT Software & Cloud in detail
A clear next engineering step, before you spend on the wrong one.
Feasibility checks, architecture advice, debugging of a design that misbehaves, prototype guidance and remote support for your own team. Everything is done remotely, with the work and the findings written down.
Design reviews, Bench measurement guidance, Remote debugging sessions
Technical Consulting & Remote Engineering in detail
Projects written up as engineering reports: the problem, what we built, the evidence and its limits.
Test report
BIL-TR-001
A water-monitoring node that tracks consumption, learns demand patterns and closes a valve by itself when it sees a leak, without waiting for a server.
| Measure | Result | Method |
|---|---|---|
| Broker round trip | 14 ms | Unverified: method note pending |
| Leak prediction accuracy | 96.7 % | Unverified: method note pending |
Read the report
A connected product is a PCB, firmware and software working as one. These two panels are labelled illustrations; real, approved examples replace them as projects are cleared for publication.
Devices online
12 of 12
Last report
2 min ago
Battery (sample)
3.9 V
Internal R&D demonstrators, separate from client work: wiring, firmware outline, design notes and a parts list. Our calculators are in the Tools section.
An ESP32 that watches a water sensor on the floor, sounds a buzzer and publishes an MQTT alert when water appears under a tank, pump or washing machine.
6 parts, reference design, draft
An MQ-2 gas sensor read by an ESP32 that logs readings, sounds a local alarm and switches an exhaust fan relay when the level rises above a clean-air baseline.
5 parts, reference design, draft
Voltage and current logging for a 12 V battery system up to 20 A, such as a solar battery or a router backup, with alerts before the battery is drained too far.
5 parts, reference design, draft
Five steps, the same every time. You always know what we’re doing next and what you’ll get from it.
You tell us what the device must do, where it will live and what constraints apply. The short form on our contact page is enough to start.
You get: Our questions back by email, or an honest no if it isn't a fit.
We write down what we'll build, how we'll test it, what it costs and the milestones. Work starts only when you've agreed to it in writing.
You get: A written scope with test criteria, milestones and a price proposal.
We build in short increments and send bench notes as we go, so you see progress and problems while they're still cheap to fix.
You get: Access to the code as it grows, and regular bench notes.
We test against the criteria in the scope and record how each number was measured: the device, the conditions, the instrument and the date.
You get: A test report with methods, results, and what failed on the way.
Source, documentation and a walkthrough, so your team can build, flash and maintain the device without us in the room.
You get: A handover pack: source files, build steps, documentation and test results, as scoped.
You should be able to build, test and maintain the work without us in the room.
Every engagement starts with an agreed scope, milestones and acceptance criteria. Depending on the project, deliverables may include editable schematics and PCB files, firmware and application source code, deployment instructions, technical documentation and test results.
We can discuss NDA arrangements before reviewing confidential design files. Access, ownership and handover terms are agreed in writing before work begins.
Named profiles are published with each engineer’s consent. About our engineering approach.
What we learn on the bench, written down so you don't have to learn it the hard way.
A node that reconnects for every report pays for a TLS handshake every time. Often the handshake, not the reading, sets the battery life.
Telemetry, Power
Power cuts, dips, inverter switch-overs and whole neighbourhoods coming back at once. A checklist for devices that live on an unreliable grid.
Firmware, Reliability
The ESP32's ADC is good enough for most sensors, if you respect which pins, which range, calibration and impedance.
Firmware, ESP32, Sensors
Pick the shape that fits. We quote after reading your brief, as a written proposal.
A close look at a design, firmware or software you already have.
Teams with a design or device that misbehaves, or that want a second opinion before they commit.
Examples
A defined piece of work, delivered against written test criteria and milestones.
A new board, a firmware release, a cloud platform, or a complete first version of a connected product.
Examples
A set number of engineering days every month.
Teams with a product in development or in the field that needs steady engineering support.
Examples
The short answers. The full list is on the FAQ page.