How it works
Plug in and go.
Unbox. Plug in. Ask. Data stays with you. Same Hatch OS from a phone — over your VPN.
Unbox
An encrypted cluster, already imaged for you. Hatch OS ready. House model path loaded. You do not assemble a stack.
Plug in
Ethernet to your network. Power on. You sign in first, then invite seats. No public cloud login. No SSH to ask a question.
Ask
Drop a PDF, or put files in the watched folder. Ask. Retrieval and answers stay on premises. Remote is your VPN — not a lab.
Arrive imaged
The cluster ships ready, customized to the fit we confirmed: seats, documents, knowledge base. Encryption is on. Models are local.
Join your network
Plug into the LAN. People reach Hatch OS. Work stays on your network — not a lab account.
You sign in, then invite
The first account is yours. You invite seats. Hatch OS is the login — ChatGPT-like, on your box.
Add documents
Upload in Hatch OS, or drop files into a watched folder. The house model can use the memo that should stay in the room.
Ask without sending it out
Chat on the cluster. The pass test: a non-technical person drops a PDF and asks. No SSH.
Check the status / connections page
See model state, disk encryption, and whether outbound is on. Proof for IT and counsel — not a sales paragraph.
Proof
Default-deny outbound.
The cluster does not call a frontier lab or a data company to answer. Egress starts off. Signed updates are optional and can be disabled. If IT wants a hole, that is a written choice — not a silent default.
We will not call this a certified air gap. We will say the intended posture: work stays on premises; the status page is how you see it. Remote access is people reaching this Hatch OS over your VPN — it does not mean the cluster uploads files to a lab.
Remote
Same OS over your VPN.
The building is yours, not one desk. Traveling, you should use the same private AI — without pasting the memo into a lab because you left the floor.
What we mean
Secure access to Hatch OS on your cluster. Same models. Same documents. Same seats. Travel, phone, anywhere you already work.
What we do not mean
We do not host your files in a Hatch cloud. We do not send them to a frontier lab. We will not invent a VPN product name or claim a zero-attack-surface remote product.
What is confirmed later
How you get in from outside the office is confirmed when we image a unit — typically through the VPN you already trust. Pre-launch. We will be specific before you commit.
Backup and proof
You own the disk. You can show the page.
Backup
There is no Hatch cloud copy. Backup is the encrypted disk you own, or a copy you make of it. Unplug the cluster and the work stays with you.
What the status page shows
Hatch OS ready, disk lock, outbound on/off, update checks on/off. Plain language. Screenshot-friendly for IT.
What it is not
Not a public uptime badge. Not a SOC 2 report. Not a claim that nothing can leak if someone walks the hardware out of the room.