Installation

Operayde appliances can be deployed on your own infrastructure or hosted in one of our datacenter regions (EU, KSA, UAE). The first-boot flow takes care of the rest.

Before deployment

We send a short pre-flight checklist. It covers:

• Network connectivity requirements
• Outbound firewall allow-list (only the central plane, central.operayde.com:443)
• DNS record for appliance.<your-domain> pointing at the appliance IP
• An OIDC client created in your IdP (Entra ID, Okta, Google Workspace, or your own dex), or appliance-local auth if you prefer to skip federation
• A named first-user email for the appliance admin

Deployment

1. The appliance environment is provisioned — either on your infrastructure or in an Operayde datacenter.
2. Power on. The appliance boots into a one-time setup wizard on the local console. It captures seven items — tenant, admin email, central-plane URL, the enrolment token, IdP details, proxy (optional), and the inference profile — and takes about five minutes.
3. On completion the appliance's fleet agent exchanges the one-time token with the central plane and receives its appliance identity and fleet-signed client certificate (see Enrolment for exactly what is exchanged and where each key lives). Services start automatically.

First sign-in

Open https://appliance.<your-domain>. You’ll be redirected through your IdP (or the local login if you skipped federation). The named first-user becomes the appliance admin; they can mint API keys and invite the rest of the team.

Verifying the install

From any machine with network access to the appliance:

curl https://appliance.example.com/healthz
# {"status":"ok",...}

curl https://appliance.example.com/v1/models \
  -H "Authorization: Bearer $OPERAYDE_APPLIANCE_KEY"   # an ak_... key
# {"data":[{"id":"...","object":"model",...}, ...]}

If either command fails, see Troubleshooting.