OwnLLM Docs
Desktop app

Pairing

Pair Atlas with your OwnLLM tenant from the first-run wizard.

The first time you launch Atlas, the pairing wizard opens automatically. After successful pairing, the wizard never reappears unless you unpair the machine.

Get a pairing key

In your OwnLLM admin space:

  1. Go to Admin → Agents.
  2. Click Generate pairing key.
  3. Copy the key (ownllm_pair_<32-hex>). It expires in 7 days and is single-use.

Paste it into Atlas

In the wizard:

  1. Paste the key into the input. Atlas validates the format client-side before submitting.
  2. Click Connect. The wizard:
    • Hashes the host machine ID.
    • Posts the key + machine ID + host specs (VRAM, RAM, CPU cores, GPU type, OS) to POST /api/v1/agents/pair.
    • Receives the agent token + Cloudflare Tunnel credentials + the list of recipes the admin pre-selected at signup.
    • Writes the secrets to the OS keychain (Keychain on macOS, Credential Manager on Windows, Secret Service on Linux).
  3. Atlas registers itself as a service so it restarts on boot, then starts Ollama and cloudflared as supervised subprocesses.
  4. The wizard closes and the dashboard takes over.

What you'll see during pairing

The wizard shows a four-step progress indicator:

[●] Validate key            ✓
[●] Provision tunnel        ✓
[●] Install runtimes        downloading ollama 0.6.4 …
[ ] Pull recommended models   queued

The Install runtimes step downloads Ollama and cloudflared if they aren't already present (~150–200 MB total). On a fresh install this takes 30–60 seconds on a fast connection.

The Pull recommended models step is optional and can be skipped — you can install models later from the Models page.

Errors

MessageMeaning
Invalid pairing keyFormat check failed (length, prefix).
Pairing key expiredOlder than 7 days — generate a new one.
Pairing key already usedSingle-use; generate a new one.
Network errorAtlas can't reach ownllm.app. Check egress / TLS.
Machine already pairedA previous Atlas (or CLI) install paired this host. Run Unpair first.

If the wizard hangs on Provision tunnel, the most common cause is egress filtering: cloudflared needs outbound TCP 7844 (or HTTPS 443 fallback). On a corporate network, ask IT to open one of those.

Unpairing

Settings → Account → Unpair this machine disconnects the host:

  • Stops the daemon and cloudflared.
  • Calls POST /api/v1/agents/unpair so the site marks the agent offline immediately.
  • Wipes the keychain entries.

The Cloudflare Tunnel is deleted on the OwnLLM side; the next pairing provisions a fresh one.

Re-pairing

A machine can be paired to one tenant at a time. To switch tenants, unpair first, then run the pairing wizard again with a key from the new tenant.

Headless

Atlas is GUI-only. To pair a headless host, install the CLI and run ownllm pair <key> instead.

On this page