Quickstart

This runs the standalone image: Relay and its own Postgres in one container, with the catalog seeded on first boot.

Start the relay

docker run -p 8080:8080 -p 8081:8081 \
  -v relay-data:/var/lib/postgresql/data \
  wyolet/relay:standalone

The volume keeps your data, the generated credentials and the master key across container restarts. The image is built for linux/amd64.

Admin UI and control API on :8081, OpenAI- and Anthropic-compatible inference API on :8080.

To run the lean image with separate Postgres and Valkey containers instead, use the Compose stack.

On first boot the container prints a generated password for the user admin, and an admin token, to its log:

docker logs <container>

Open localhost:8081, sign in as admin with that password, and follow the setup wizard to add a provider’s API key and create a relay key.

The relay key is shown once, when it is created. Copy it then; only its hash is stored.

Make a request

curl http://localhost:8080/openai/v1/chat/completions \
  -H "Authorization: Bearer <your-relay-key>" \
  -H "Content-Type: application/json" \
  -d '{"model":"gpt-4o","messages":[{"role":"user","content":"hello"}]}'

curl http://localhost:8080/anthropic/v1/messages \
  -H "Authorization: Bearer <your-relay-key>" \
  -H "Content-Type: application/json" \
  -d '{"model":"claude-sonnet-4-6","max_tokens":256,"messages":[{"role":"user","content":"hello"}]}'

Use a model from a provider you added a key for. To see what your relay key can reach:

curl http://localhost:8080/v1/models -H "Authorization: Bearer <your-relay-key>"

Hit a snag?

Status codes and error codes, login problems, keys that stop working.

Next steps

Docker

Persisting data, pinning the master key, the Compose stack and the lean image.

Kubernetes

The Helm chart, migrations, scaling and monitoring.

Clients

Point the OpenAI and Anthropic SDKs at Relay.

Inference API

Endpoints, wire shapes, streaming and errors.

Get Started

Build with Relay

How It Works

Deploy and Operate

Observability

Security and Access

Reference

Hit a snag?

Next steps

Docker

Kubernetes

Clients

Inference API

Hit a snag?

​Next steps

Docker

Kubernetes

Clients

Inference API

Next steps