We write the code we talk about
Technical advice is easy to fake with a nice deck. Outside client work, the Stable State team designs, ships and maintains open-source security tools of our own: evidence that the people assessing your technology still build it.
CableProbeUSB cable security analyser for Linux
LAN FenceMonitoring for unauthorised devices on a network
VLANVerifyEvidence that network segmentation actually holds
What we've built
CableProbe
An open-source USB cable security analyser for Linux. Detects unexpected USB, HID, network, BLE and Wi-Fi behaviour in untrusted cables and devices, because a cable can be a computer in disguise.
LAN Fence
Continuous, observation-only monitoring for unauthorised devices on a network (rogue access points, hidden hardware and supply-chain implants), running on a Raspberry Pi.
Why we do this
Most technical advisory firms stop writing code the day they start consulting. We think that's a mistake. Reading someone else's codebase, judging its risks, and knowing what "good" actually looks like gets harder every year you're not building something yourself.
So the team stays hands-on. We build tools that solve problems we find genuinely interesting (cable security, network integrity, compliance evidence), release them publicly under an open licence, and maintain them the way we'd expect a client's own codebase to be maintained: documented, tested, and honest about their own limitations.
It's a small, deliberate discipline. Staying hands-on keeps our judgement sharp, and shipping real, working software in public is a more honest signal of technical capability than any case study could be.
Judge the code, not just the pitch.
Have a look through the repos. Then, if you want the same rigour applied to your own technology, start with ClearView.