Quick start

The fastest way to understand Operayde is to unbox an appliance and use it. This page walks through the full sequence for a Starter Micro arriving at a 20–50 FTE office; the rack-mount Starter and the dual-GPU Pro follow the same pattern, just with racking instructions appended.

1 · Rack or shelf

The Micro is a silent desktop unit. Sit it on a shelf or under a desk; the only clearance requirement is 50 mm of airflow on the back panel. Rack-mount units use standard 4-post rails; Pro units ship with slide rails in the box.

Power

1× IEC C13, ≤ 220 W (Micro) / ≤ 650 W (Starter) / ≤ 2× 1,100 W redundant (Pro)

Network

1× 1 GbE (Micro) / 2× 10 GbE (Starter and Pro)

Internet

Outbound HTTPS to ops.<region>.operayde.com only

2 · First boot

Connect power and network. The appliance boots from an internal mSATA into a Debian-stable image. At the first boot screen you'll be asked for the enrolment token we sent ahead of shipment — 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, attests to the TPM, 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, from any machine on your LAN:

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-13b",
    "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 network". 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.