Software that touches the physical world
Controlling real devices, reverse-engineering legacy protocols, and shipping native apps — with safety gates on anything that actuates.
Silent Sentinel — a live operator console for a real camera fleet
A WinUI 3 desktop console running today against a real 9-camera fleet, talking a proprietary protocol that was never documented for third parties — every write gated behind an explicit arm-and-confirm step.
- Protocol coverage
- 2,048-operation catalogue, reverse-engineered from vendor documentation
- Fleet under control
- 9 cameras, live, multi-firmware autodetect
- Write safety
- Arm checkbox + typed confirmation required before any command that changes device state
- Default posture
- Read-only — writes are the exception, never the default
- Secrets at rest
- DPAPI-encrypted local vault, no plaintext credentials on disk
Multi-feed geometry aligned into one continuous view.
Mertens exposure fusion for high-contrast and low-light scenes.
Coordinator + scene classifier ranking candidates across a live feed.
Video stitching, HDR and tracking are built and exercised against the live feed — not yet the long-running production path the console itself runs day to day.
A device, a protocol, or a fleet that needs a safe control surface — half an hour tells you what's possible.
Start a conversationBeyond one console
Sonos, Samsung, Ring, Hive, Tuya and Alexa unified into one control plane and one voice surface — over a hundred devices, proven on a real installation MAST runs day to day.
One backend contract, native clients on both sides — a Windows desktop app and an iOS/Mac app built from the same protocol, deployed through a remote build pipeline with no local Xcode.
From protocol to a safe, working console
- 01Protocol audit
Reverse-engineer or read the vendor spec, catalogue every operation.
- 02Safety-gated build
Read-only by default; writes need an explicit arm-and-confirm step.
- 03Live integration
Ship against the real fleet or devices, not a simulator.
- 04Maintain
Firmware drifts — the console keeps working when the vendor changes it.
What stops the software from actuating something by accident?
Every write path defaults to read-only. Changing device state needs an explicit arm step plus a typed confirmation — there's no one-click path to an unintended action.
Do you need the vendor's documentation to integrate a device?
No — the camera console's protocol was reverse-engineered from a vendor PDF with no public API. Where documentation exists, it's faster; where it doesn't, that's the job.
Can the same system run on Windows and mobile?
Yes — one backend contract, native clients built for each platform, including an iOS/Mac build pipeline that runs from a Windows machine over a remote build step.
Half an hour to see what an exacting fit looks like for your business.
Start a conversation