Firmware & embedded software
Low-level code that runs on the device itself — sensor drivers, control loops, power management, and the on-board logic that has to be right before anything else can be.
Service · IoT & Device Development
Where hardware meets software.
Where hardware meets software.
Built to live in the real world.
We bridge the physical and digital — firmware, connectivity, device-cloud, and companion apps that turn a device into a connected product. One senior team owns the whole stack, from the chip to the dashboard.
Device to cloud · one senior team.
—— What we build
The whole stack, device to dashboard.
A connected product is firmware, radios, a cloud, and an app moving as one. We design and build every layer so they fit together — no seams where a vendor handoff used to be.
Connectivity — BLE, Wi-Fi & cellular
Getting data on and off the device reliably: Bluetooth pairing that feels instant, Wi-Fi provisioning that survives real home networks, and cellular for devices that roam.
Device-cloud & telemetry
The ingest pipeline, the data model, and the real-time control plane — streaming telemetry up, pushing commands and config down, and storing it so the rest of the product can use it.
Companion apps & fleet management
The mobile and web experiences people actually touch — setup, control, and insights — plus the back-office dashboards to monitor, update, and operate a fleet of devices at scale.
—— Where IoT projects break
The gaps that sink connected products.
Most connected-product trouble isn't the chip. It's the seams — where firmware, the network, updates, and the fleet were each owned by someone else.
Firmware and cloud drift apart
Separate teams ship on separate clocks, and the device and the backend stop speaking the same language mid-project.
Connectivity that fails in the field
It works on the bench, then meets a real home network or a dead cell zone — and the link the whole product relies on drops.
Risky over-the-air updates
Without staged rollouts, signed builds, and a rollback path, one bad update can brick a device you can't reach in person.
Fleets that don't scale
A cloud built for one device buckles at a thousand — provisioning, monitoring, and updates that needed designing in from day one.
—— Services
Every layer of a connected product.
Bring us in for one layer or the whole stack — each is a deliverable on its own, and one senior team owns how they fit together.
Firmware & Embedded
On-device code — drivers, control loops, and power management running on the metal.
Connectivity (BLE / Wi-Fi / Cellular)
The transport that fits the product — instant pairing, robust provisioning, roaming cellular.
Device-Cloud & Telemetry
Ingest, data model, and control plane — telemetry up, commands and config down.
Companion Apps
The mobile and web experiences people touch — setup, control, and live device insights.
OTA Updates
Staged rollouts, signed firmware, and a safe rollback path — ship fixes without a truck roll.
Fleet Management
Provision, monitor, and operate thousands of units from one back office as you grow.
—— How it works
Prototype to production fleet.
Connected hardware is unforgiving once it's in the field. We prove the idea on a bench, integrate the full loop, harden it for the real world, then scale it across a fleet.
1
Phase 01
Prototype
Stand up a working device on the bench — the sensor reads, the radio talks, the data lands. Prove the core loop before committing to the build.
2
Phase 02
Integrate
Wire the full path — device ↔ cloud ↔ app — so telemetry flows up, control flows down, and the companion experience reflects what the hardware is actually doing.
3
Phase 03
Harden
Make it survive the real world: reliability under flaky connectivity, over-the-air updates, and security across the device, the transport, and the cloud.
4
Phase 04
Deploy & scale
Ship to production and grow from one device to a fleet — provisioning, monitoring, and the operational tooling to run thousands of units with confidence.
—— The build, week by week
A device-to-cloud build, plotted out.
A typical engagement, week by week. Phases overlap — cloud and app work start while the firmware is still settling on the bench.
PROTOTYPE
INTEGRATE
HARDEN
DEPLOY
WEEK 1Apr 06
WEEK 2Apr 13
WEEK 3Apr 20
WEEK 4Apr 27
WEEK 5May 04
WEEK 6May 11
WEEK 7May 18
WEEK 8May 25
WEEK 9Jun 01
WEEK 10Jun 08
WEEK 11Jun 15
WEEK 12Jun 22
—— Selected work
Connected products that shipped and scaled.
A few of the products we’ve shaped — including Eyebot, a self-serve AI vision kiosk that delivers an eye screening in about ninety seconds on connected hardware.
—— Common questions
What device teams ask first.
Whether we touch hardware, which protocols we use, how OTA updates work, scaling a fleet, and how we secure connected devices.
Do you do hardware too, or just software?
We're a software and AI studio. We own everything from the firmware on the device up through connectivity, the device-cloud, and the companion app — and we partner closely with your hardware team or electronics vendor. On products like Eyebot and Hydrow, the software and the device were inseparable.
Which connectivity protocols do you work with?
The common ones for connected products: Bluetooth Low Energy for pairing and short-range, Wi-Fi for in-home and venue devices, and cellular for devices that roam or have no local network. We pick the transport that fits the product and its power, range, and cost constraints — not the other way around.
How do over-the-air (OTA) updates work?
We build OTA in from the start, because a device you can't update is a liability the moment it ships. That means staged rollouts, signed firmware, and a safe rollback path if an update misbehaves — so you can fix bugs and ship features without a truck roll.
Can you handle a fleet at scale?
Yes — fleet management is part of the stack, not an afterthought. Provisioning new devices, monitoring health and connectivity, pushing config and updates, and operating thousands of units from a single back office. We design the device-cloud so growth from one unit to a fleet doesn't require a rewrite.
How do you secure connected devices?
Security spans three layers: the device, the transport, and the cloud. That means per-device identity and authentication, encrypted communication, signed firmware so only trusted code runs, and least-privilege access on the backend. For products like Eyebot in healthcare, that discipline isn't optional.
—— Field notes
What we’re writing about.
Field notes from the studio — what we’re learning about AI products, agent UX, and the messy reality of shipping software in 2026.
