Appliance
Installation
Physical install, network requirements, and the first-boot enrolment.
Last updated 18 Apr 2026
Installation is deliberately simple — we ship the hardware pre-configured for your site and the first-boot flow takes care of the rest.
Before the appliance arrives
We send a short pre-flight checklist a week before shipment. It covers:
- Power and network drops
- Outbound firewall allow-list (only
ops.<region>.operayde.com:443) - DNS record for
appliance.<your-domain>pointing at the LAN IP - An OIDC client created in your IdP, or our shared IdP offer if you don’t have one
- A named first-user email for the bootstrap virtual key
Physical install
- Unpack, inspect for shipping damage, and connect power + network. Units carry a tamper-evident seal over the rear panel; if it’s broken on arrival, stop and call us.
- Power on. The unit runs a POST and boots into the enrolment screen
(console or web at
http://<appliance-ip>:8080). - Paste the enrolment token. The unit registers itself with the fleet, generates a keypair under TPM seal, and obtains its fleet-signed certificate.
First sign-in
Open https://appliance.<your-domain>. You’ll be redirected through your
IdP. The named first-user becomes the appliance admin; they can mint more
virtual keys and invite the rest of the team.
Verifying the install
From any LAN machine:
curl -k https://appliance.example.com/healthz
# {"status":"ok","service":"workspace","ts":"2026-04-18T11:22:33Z"}curl -k https://appliance.example.com/v1/models \
-H "Authorization: Bearer $OPERAYDE_KEY"
# {"data":[{"id":"operayde/instruct-13b",...}, ...]}If either command fails, see Troubleshooting.