Embedded Systems & IoT
Software for hardware, from the device on the bench to the dashboard that watches a fleet of them.
Embedded work tends to fail at the seams: between firmware and operating system, device and network, controller and the business system that needs its data.
We work on both sides of those seams. The same team that writes for the device builds the back end it reports to, which is what "from the cloud to the factory floor" means in practice.
What we take on
Embedded Linux
Custom Linux images built with Yocto, and the applications and services that run on the device.
Firmware and real-time systems
RTOS-based software for devices where timing matters.
Industrial automation
PLC logic in Structured Text on Beckhoff TwinCAT, connected to the systems that plan and report.
Sensor networks and IoT
Devices that report over MQTT, and the back end that collects, stores and shows what they send.
How an engagement runs
Scope
A conversation, then a short written plan: what gets done first, what it costs, and what is deliberately left out.
Build
Working results early and often. You see progress in something running, not in status reports.
Ship
Deployment, monitoring and backups are part of the job, not an afterthought.
Hand over
Your code, your accounts, and documentation written for whoever maintains it next.
What we use
Work that backs this up
Device-level C++ in the open-source framework for an AI accelerator.
A fork-safety fix for tt-metal
Contribution to an AI hardware framework
Tenstorrent's tt-metal hung when a forked process opened a device. We traced it to state inherited across fork() and wrote the fix.