The method doesn’t change. Immerse, spot, execute. What changes is where the system lands: a web platform, a phone in the field, a machine on the bench, or hardware that never touches the internet. Everything below ships through the same forward-deployed engagement, with the same gates. The tooling behind the gates is going public as licence reviews clear.
Most of what we ship lands here: web platforms with AI in the load-bearing path. That phrase has a test. Take the model out, and the workflow should stop. Every build is multi-tenant, with isolation enforced at the database. We measure the result against the real workflow it replaces.
The default engagement is a 2-hour immersion that scopes the build, then the build. Who runs it after launch is your call.
Field teams don’t work at desks, so the platform goes with them: a React Native or native app that tolerates losing signal and runs on the same governed backend as everything else we ship.
The 2-hour immersion decides whether mobile is the right place to spend the build; the rest of the engagement runs the same way.
Heavy files and local hardware keep some work on the desktop, a long way from any browser tab. For that work we ship applications on Windows, macOS, and Linux. The range runs from a tray utility that removes a daily annoyance up to a full working environment.
Scoped in the same immersion and shipped through the same engagement. Your team runs it, or we do.
For some clients, onshore isn’t enough. The rule is that data never leaves the premises, which also rules out any model that phones home. So inference runs locally on hardware you control, and nothing in the data plane sits outside infrastructure you own. We build the system and hand you the keys. Whether we stay on to run it is a separate decision, and it is yours.
It starts like every engagement: two hours in the room with the workflow and the constraint. We build sovereign only when sovereignty turns out to be the binding one.
Where this stands
We have not delivered a sovereign build into production yet, and we would rather write that down than imply a history we do not have. What exists is the reference architecture below, components that are each proven in their own right, and the posture we hold on our own platform: the isolation harness green on every commit, residency and retention in writing, the subprocessor register down to the last entry. The first sovereign build will be a design-partner engagement, priced and scoped as one.
7 tables checked · ran