Services
Four disciplines under one roof.
Reverse Engineering
When the documentation does not exist, the work starts at the wire. StoutWorks specializes in systems that were never meant to be understood from the outside, whether that means a proprietary protocol, a closed file format, a vendor-locked device, or a binary whose source is long gone.
Deliverables are working code and real documentation, not a report that restates the problem.
Typical work
- Protocol capture and analysis: USB, Bluetooth LE, serial, network
- Binary analysis and firmware unpacking
- Proprietary file format decoding and data recovery
- Interoperability layers for closed systems
Reverse engineering work stays inside the interoperability boundaries of DMCA section 1201(f).
Drivers & Firmware
Hardware does not stop being useful because the vendor stopped caring. StoutWorks writes Linux kernel modules and userspace drivers for peripherals that shipped without them, and does the firmware analysis to support hardware whose manufacturer has moved on.
Typical work
- Linux kernel modules and userspace drivers
- Support for unsupported peripherals: sensors, audio interfaces, input devices
- Firmware analysis, patching, and recovery
- Upstream-quality contributions under GPL or LGPL where appropriate
Legacy Modernization
Every company has one: the system nobody dares touch because it still runs the business. StoutWorks stabilizes it, documents it, and moves it forward in increments that never put operations at risk. No rip-and-replace fantasy quotes.
Typical work
- Assessments and risk maps of aging systems
- Data extraction from closed or obsolete formats
- Incremental replacement plans that keep the business running
- Documentation for systems that never had any
AI-Powered Software
StoutWorks builds software the way this decade allows. Serious AI tooling works under human direction, with the judgment to know what to keep. AI extends what the practice can take on, and judgment decides what ships.
Typical work
- Custom internal tools and dashboards
- Integrations between systems that were never meant to talk
- MCP servers and AI-agent infrastructure
- Automation of workflows that eat staff hours
How engagements work
Three steps, no theater.
Describe the problem
Email whatever you have. Model numbers, error messages, folklore. Incomplete is expected.
Get a straight assessment
Feasible or not, what it would take, and what it is not worth doing. If it is not a fit, you hear that first.
Written scope, then work
Fixed scope where the problem is known. Honest hourly where discovery is genuinely open-ended.