Security
What we will and will not claim.
Data stays with you. Not with the labs. Remote is Hatch OS over your VPN. We will not dress that up as a certification we don’t have.
What is true today
- Your files stay yours. Prompts and outputs stay on premises.
- Work does not go to OpenAI, Anthropic, Bedrock, or a data company to answer a question.
- Outbound starts denied. Signed updates can be disabled.
- Disk encryption is on before the cluster ships.
- A local status / connections page shows model, disk, and whether traffic is leaving.
- Backup is the encrypted disk you own — not a Hatch cloud. You can unplug the cluster.
- Remote means people reach the same Hatch OS over your VPN. The cluster still does not call a lab to answer.
Lines we will not cross
- HIPAA compliant, HIPAA ready, or BAA language.
- SOC 2, ISO 27001, or “examiner-ready.”
- Zero risk. Zero egress as a certified fact. Zero attack surface.
- A named VPN product, or a finished remote brand we do not have.
- Beats Claude, GPT, or any named frontier model.
- Named customers, case studies, or revenue we do not have.
- Medical or legal advice. We sell a clean room — cluster plus Hatch OS.
Remote access
Same private system. Honest limits.
The building is yours. You travel. You use phones. You should not have to paste privileged work into a lab because you left the office machine.
Intended
Secure access to the same Hatch OS — models, documents, seats — from the office, a trip, or a phone. Files stay with you. They are not uploaded to a frontier lab or a Hatch cloud because someone is remote.
Not invented
We will not name a VPN vendor or ship a slogan about an unbreakable tunnel. How you get in from outside the office is confirmed when we image a unit, typically through the VPN you already trust. Pre-launch.
Still true of the cluster
Default-deny outbound stays the appliance posture. Remote is inbound access to your system. It is not “we send your files out so you can work from a hotel.”
Threat model, simply
This solves the paste problem. Not every problem.
It is for
An associate who would otherwise send a client memo to a lab. A deal team that will not give the IC deck to a data company. An operator who will not put the pricing sheet in someone else’s cloud. Including when you are not at the office desk.
It is not for
Someone who walks the cluster out of the room. A compromised laptop — in the office or on the road. A firm that needs a signed audit letter this quarter. Those are different products and different paperwork.
Physical reality
If someone has the hardware, they have the hardware. Encryption helps. Policies help. A phone on a public network is still a phone on a public network. We will not pretend a marketing site is your incident plan.
Medical
Later. Paperwork first.
We may serve clinical operators later. Until then this site makes no HIPAA claim, no treatment claim, and no “hospital-ready” claim. If that is your need, say so on the inquiry — we will be honest about timing.
Inquire