Quick start

The fastest way to understand Operayde is to deploy an appliance and use it. This page walks through the full sequence — whether you deploy on your own infrastructure or in one of our datacenters (EU, KSA, UAE).

1 · Provision

Choose your deployment model:

• On-premises — we provision the appliance image for your infrastructure.
• Operayde-hosted — we deploy in one of our datacenter regions (EU, KSA, UAE).

In both cases, your deployment engineer will prepare the environment and provide you with an enrolment token.

2 · First boot

The appliance boots into a hardened Debian image. At the first boot screen you'll be asked for the enrolment token we sent ahead of deployment — paste it in.

# What's happening under the hood, FYI:
operayde-enrol --token $TOKEN \
  --region eu-1 \
  --tenant $TENANT_ID \
  --site "Head Office — Ground Floor"

The appliance generates a keypair and registers with the fleet. Total elapsed time: under five minutes.

3 · Bring the first users on

Once enrolled, the appliance is reachable at https://appliance.<your-domain>. Staff sign in with your existing IdP (the enrolment flow created the OIDC client for you).

4 · Ask it something

A first smoke test:

curl -s -X POST https://appliance.example.com/v1/chat/completions \
  -H "Authorization: Bearer $OPERAYDE_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "operayde/instruct",
    "messages": [{"role": "user", "content": "Who owns the data I just sent you?"}]
  }'

Expect a response like "you do — this appliance is sealed and runs on your infrastructure". The virtual key $OPERAYDE_KEY was minted at enrolment with scope room:admin for your bootstrap user; you can mint finer-grained keys from the operator portal as soon as you're ready.

5 · Next steps

• Mint per-team virtual keys in the portal.
• Publish a first OPA policy — even a trivial one — to learn the workflow in Policies.
• Wire the appliance into your existing tools with the Gateway API reference.