How a governed build runs.
Three stages, stated in advance. Each one ends with something you hold and something you can show the people you answer to. No stage begins without the last one’s receipts. The line, the gate, and the map are explained on the platform page; this page is what you hold at the end of each stage.
The conversation.
You bring the workflow AI should run but can’t be trusted with yet: submission intake and clearance, the Excel rater, the bordereaux, the portal rebuild, the Phase II prototype that needs its ATO package. And the examiner, or the assessor, you answer to when it changes. We scope it together. The fee is fixed before anything starts, and the first deliverable review is on the calendar before we write a line.
The governed first project.
It starts with a read-only survey of your estate, inside your boundary. Your first governed service is scaffolded onto the line and passes the gate green out of the box; what moves onto the line goes onto the map. Agents build inside declared scope; your people review and approve every change; bad changes don’t get reviewed, they get blocked. It ends production-acceptable, live in your environment.
Governed operations.
The line moves to governed operations, in the mode you choose: Operated, where we run the line, or In-house, where your team runs it and we train your operator. Either way you walk at renewal with everything. Deployment lands where your risk sits: your cloud or on-prem, air-gap on request. Your identity stack plugs in; roles and permissions go on the record. And your models become policy: the model port is the contract, Anthropic ships today, other providers and local models drop in where code can’t leave, with every receipt naming the model and prompt that ran.
Your walls. Your models.
Your rules.
Your cloud
Private deployment in your own tenancy: your keys, your regions, your controls. Nothing multi-tenant, nothing shared.
On-prem
Inside your data center, beside the systems it governs. Code and evidence never leave the building.
Air-gap on request
Fully disconnected operation for the environments that demand it. The design is portable and the lane is stood up on request; we label what ships when, out loud.
Which model may do what is a gate, not a habit.
The model port is the contract: Anthropic ships today, other providers and local models drop in behind it. Which model may run where is written as policy and enforced like every other gate: Anthropic behind the port today, local models where data can’t leave as they drop in.
Swap models. Keep the history.
Every receipt names the model and the prompt version that ran, so when a better model ships, you switch, and the record stays whole across the seam. No provider can hold your history hostage.
Models provide the intelligence. The routing, the boundaries, and the proof are yours.
Stated before anything starts.
What do you ask of us?
A named owner who can meet weekly. Access to the workflow and the people who run it today. Your compliance lead in the room when the evidence pack is mapped to the exams you sit.
What does it cost?
A fixed fee for the first build, scoped and priced in the first call and agreed before anything starts. Governed operations afterward are priced separately, in the mode you choose.
How long until it is live in our environment?
Four to eight weeks for the first build, production-acceptable and live inside your boundary, with the evidence pack mapped to the exams you already sit. Builds run one at a time, in sequence.
Will you name us?
Only with your written consent, and never as a condition of the engagement.
What if it doesn’t work?
You keep everything that shipped: the software, the map, the receipts, and the evidence pack documenting exactly what happened. That is the design of the offer, not a concession.
Will you tell us if it isn’t a fit?
Yes, on the first call, and no is a fine answer. We would rather lose the engagement than the reference.
Start at stage one.
One conversation: the workflow, the examiner, the timeline. The fee is fixed before anything starts, and the first review is on your calendar before we write a line.
Inquiries are answered within one business day, by someone who can answer them.
