Fixed-scope engagement
ESP32 Production-Readiness Audit
A working prototype is roughly 60% of a shippable product. The remaining 40% — the unglamorous engineering that decides whether devices survive years in the field — is exactly what a prototype hides and an audit surfaces, while it's still cheap to fix.
What we review
| Area | What we check | Field failure it prevents |
|---|---|---|
| PCB & DFM | Footprints, clearances, annular ring, panelization, antenna keep-out | Fab rejection, respins, poor RF range |
| Firmware hardening | Watchdogs, brownout handling, NVS durability, error recovery | Field hangs, flash corruption, lock-ups |
| Security | Secure Boot v2, flash encryption, eFuse provisioning plan | Cloned firmware, credential and IP theft |
| OTA updates | Signed images, rollback, anti-rollback counters | A bad update bricking the deployed fleet |
| Connectivity | Reconnect logic, local buffering, protocol robustness | Data loss during network dropouts |
| Power | Deep-sleep current, regulator choice, power budget | Batteries that die years early |
What you get
- A prioritized findings report — critical / high / medium, each tied to the field failure it prevents.
- Concrete, specific fixes — the exact change to make, not generic best-practice advice.
- A walkthrough call with the senior engineer who did the review, so your team can act immediately.
How it works
- You share your schematic, firmware, and production targets (NDA on request).
- We review against the same production checklists we use on our own builds.
- You receive the report and walkthrough — typically within about a week.
The checklists behind the audit
Frequently asked questions
What do you need from us to run the audit?
Your schematic and/or firmware source (or binaries), a short description of the product and its deployment environment, and your production targets. The more you share, the deeper the review — we sign an NDA on request before anything is sent.
How long does the audit take?
A typical ESP32 hardware-and-firmware audit is delivered within about a week, including the written report and a walkthrough call. Larger or multi-board systems take a little longer; we confirm the timeline when we scope it.
Do you sign an NDA?
Yes. We routinely sign mutual NDAs before reviewing schematics, firmware, or product details. Your IP stays yours; the audit is a review, not a transfer of any rights.
What if the audit finds we need a bigger engagement?
The report stands on its own — you can take the findings to any team. If you'd like us to implement the fixes (hardening, OTA, a board respin, or the firmware build), the audit fee is credited toward that engagement so you never pay twice.