Skip to main content

What this is for

The gateway is configured entirely through environment variables. The Register Gateway dialog on Deploy generates the minimum set you need (registration token, gateway name, optional LAN IP). This page is the full reference for every other variable the container accepts — production hardening, control-plane overrides, Supabase JWT validation, database/Redis, and observability. All variables are read once on startup. To change a value, edit .env (or your config-management equivalent) and restart the container.

Required: cloud registration

Every gateway you register from the dashboard runs in cloud mode and exchanges a one-time token for long-lived credentials. After the first successful registration the token is ignored — credentials are loaded from disk on every subsequent boot. See Deploy → Step 4.

Production hardening

Recommended in production. The defaults are placeholder values that work for local development only — the gateway refuses to boot in any non-development environment if ENCRYPTION_KEY is left at its default or shorter than 32 characters.

Cloud overrides

The defaults already point at Guardway Cloud. Change these only for staging, an internal control plane, custom credential storage, or interval tuning.
Request bodies, prompts, and completions never leave the gateway host. Only aggregate event metadata (counts, latencies, costs) and administrative audit events are pushed to the control plane.

Supabase JWT validation

Set these when the gateway should accept dashboard Supabase JWTs directly (Phase 3.1 — used by direct-connect flows). Both must be set together. When GUARDWAY_SUPABASE_JWKS_URL is empty the gateway only validates locally-issued JWTs.

Server

CORS

All three accept comma-separated lists.

Database

The gateway ships with sensible defaults for the bundled Compose Postgres. Override only when pointing at an external database.

Redis

Rate limiting (gateway-local)

These set the local request and token caps the gateway enforces. Org-wide caps are configured from Settings → Traffic and override these at runtime.

Cache

These are gateway-local cache defaults. Org-wide cache settings configured from Settings → Traffic override these at runtime.

Semantic cache (preview)

Observability

Admin UI

The gateway ships with a minimal local admin UI. Most users govern the gateway from the dashboard and leave this off.

API key prefix

  • Deploy — minimum env vars from the Register Gateway dialog.
  • Activate — what success looks like once the gateway boots.
  • Settings → Traffic — org-wide rate-limit and cache settings that override the gateway-local defaults above.