How it works
Unbox. Plug in. Ask.
The job is the document they refused to paste. The path is short on purpose.
Unbox
The unit arrives imaged. Disk encryption is on. An open-weight model is already on the box. You do not assemble a stack over a weekend.
Plug in
Ethernet to your network. Power on. People reach one app on the intranet. No public cloud login. No SSH required to ask a question.
Ask
Drop a PDF. Ask about the memo, the model, or the pricing sheet. Prompts, files, and outputs stay on the machine you own.
Privacy / egress
Outbound is off unless you turn it on.
The point of a local box is that a lab never sees the corpus. Egress starts off. Updates are optional. If IT wants a hole, that is a written choice — not a default.
We will not tell you this is “air-gapped by certification.” We will tell you the intended posture: work stays on the LAN; the box does not call a lab to answer a question.
Proof
A status page you can show IT.
Trust is not a paragraph on a marketing site. The box has a local status page so a technical partner can see model state, disk encryption, and whether outbound is on — without taking a sales call as evidence.
What it shows
Loaded model, disk lock, egress on/off, and whether update checks are enabled. Plain language. Screenshot-friendly.
What it is not
Not a public uptime badge. Not a SOC 2 report. Not a claim that nothing can ever leak if someone walks the box out the door.
Who looks at it
The person who will get the call if an associate pastes a client file. Counsel, IT, or the partner who owns the risk.