Texas, United States
Custom software and independent cybersecurity, supported by managed IT and purpose-built hardware. From the application to the infrastructure behind it.
Showing all layers.
Explore the layers of software, security, and the systems supporting them.
An illustrative view of how our practices connect. It does not depict a client system or a product for sale.
The four custodies
Custom software and independent cybersecurity, supported by managed IT and purpose-built hardware. From the application to the infrastructure behind it.
connects devices to software
A sensor on a machine, the firmware that reads it, and the gateway that gets the reading onto a network in a form something else can use.
Ends at the network boundary. What stores the reading and reasons about it is the software division.
supports the software foundation
The networks, cloud environments, and day-to-day support that keep your software running.
Ends at the general-purpose estate. A purpose-built device on the end of the run belongs to the hardware division.
applications, integrations, and data
Applications, integrations, and data systems built around your business, with the infrastructure and security expertise to support them.
Begins where the network boundary ends. Anything physical in the room is the hardware division.
independent assessment alongside the build
Independent security assessment alongside software delivery: testing weaknesses, reviewing evidence, and helping the team address findings.
Works alongside the software practice, with independent assessors checking the build and re-testing the fixes.
Selected work
Client names are withheld under NDA unless the client has agreed to be named. Everything else is described as it happened.
Autonomous vehicle testing was producing position and rotation relative to wherever the vehicle happened to start, which made every run internally consistent and impossible to compare against any other. Referencing the whole system to magnetic north turned it into data a person could reason about, and it is still collecting.
Read the case studyIt kept testing fine and kept failing in use, so it kept getting replaced. Nothing was ever wrong with the microphone. The fault was where the receiver had been put, and the manufacturer’s own installation instructions had said so from the beginning.
Read the case studyBuilding an isolated hundred-machine training environment is a project. Running one every week, for cohorts and for a multi-institution competition, is a system. We built the second thing.
Read the case studyWorking together
Choose a phase to see what happens in it.
What breaks today, what the status quo is costing, and which division would own the fix.
Paid, fixed-scope, and it ends in a plan you could hand to another firm, plus working code proving the riskiest assumption.
A small senior team puts something real into use: a production system, a pilot running on the floor, or a finding you can reproduce.
The system grows against evidence from production rather than against a plan written before anyone used it.
We keep the system healthy after launch, and your team can take it over whenever you’d rather run it yourselves.
Next step
Forty-five minutes, no charge, no deck. We’ll tell you what we’d do, what it would likely cost, and whether what you already have can be made to work.
