Security · CIO · CISO
Private-deployment architecture
Overnight Engine is not a SaaS workspace that trains on your queue. It is a computer that sits inside your perimeter, does one stable operations workflow overnight, and learns only from the people who already own that workflow.
What never leaves
Your floor
A dedicated Overnight Engine computer on a VLAN you name. Physical access is required for hardware reset. Disks are encrypted at rest with AES-256.
Your systems
The engine calls Concur, Coupa, Epic, Guidewire, nCino, Veeva, or the mailbox from your network. Credentials live in the local enclave. We never hold the tokens.
Your learning
Corrections, approvals, and weight updates stay on the encrypted drive. They are not used to train another customer’s model.
Our telemetry
Off-box traffic is hardware health: temperature, uptime, error rates. Not receipts, charts, claims, or credit files.
How a model is allowed to change
A morning accept or reject is captured with the evidence and the reason. That event is a candidate example. It is not a live policy edit. Overnight the engine proposes hypotheses, tests them against your labeled history, and discards the ones that fail. The winner is released for the next queue. The prior model stays loaded as rollback. Live disagreement rate is watched. If it moves the wrong way, you revert.
Deployment stages
- 01
Site survey
Power, network, identity (SSO), and the first workflow’s systems of record. Founders on site.
- 02
Hardware
The machine is racked or desk-deployed. You keep it. A support visit requires your escort.
- 03
Read-only connect
One workflow, one entity. The engine can see the queue. It cannot write.
- 04
Shadow
It prepares work in parallel with the current process. You compare. Nothing changes operations.
- 05
Supervised
The morning queue is live. People accept, reject, and correct. Writes are limited to the actions in that workflow’s boundary list.
- 06
Promote or roll back
A new model ships only if it beats labeled history. The previous model remains the rollback. You can also unplug the writes.
Audit, access, and support
Every prepared action, human decision, and model promotion has an actor, a timestamp, and the evidence that was on screen. Role-based access follows your SSO. We do not have a standing remote shell into the queue. A support session is scheduled, escorted, and limited to hardware health unless you explicitly open a workflow for debugging.
This page is the shareable brief. A site survey produces the network diagram for your environment. Call the founders — there is not a sales overlay between you and the machine.