Hardware & Firmware Development
- PCB design & schematic capture
- ESP32 & Nordic BLE on FreeRTOS/Zephyr
- Power-optimized drivers & secure OTA
Timeline: ~4–6 weeks · Outcome: production-ready hardware + firmware
Services
Productized engineering offerings, each scoped as a concrete deliverable, not open-ended hours. A full hardware program — concept through production — is built from several such phases and typically runs 3–6 months; the windows below are for the individual phase.
§01 — OFFERINGS
Cloud Integration & Connectivity
- Firebase / cloud IoT, MQTT pipelines
- Telemetry + cloud→device commands
- Live dashboard & API
Timeline: ~2–3 weeks · Outcome: live device↔cloud pipeline
Computer Vision & Edge Intelligence
- Camera calibration & measurement algorithms
- Edge feature pipelines
- Detection, tracking, anomaly scoring
Timeline: ~2+ weeks · Outcome: actionable, on-device intelligence
§02 — QUESTIONS
Is Enddrave one person or a team?
Enddrave is founder-led — you work directly with the engineer designing your firmware, not an account manager relaying updates from someone else's desk. The studio also runs an engineering internship / TNP program, which adds execution capacity for larger scopes.
Do you sign NDAs?
Yes, as standard practice before any technical discussion. Enddrave's current wheel-alignment vision system engagement runs under NDA, and the same applies to new client work.
What does "fixed-scope" actually mean?
Each offering above is scoped as a defined deliverable and timeline before work starts — not open-ended hours billed as they accrue. A change in scope gets a separate estimate, not a silent overrun.
Can one engagement cover mechanical, firmware, and cloud together?
Yes — that's the default setup, not an add-on. Mechanical, electronics, firmware, and cloud sit under one roof, so you're not coordinating three separate vendors and hoping the handoffs hold.
What happens after the product ships?
Support continues after launch — fixes, firmware updates, and answering the operational questions that come up once a device is actually running in the field, not just at handoff.