Skip to main content
Once the gateway container is running it registers itself with the control plane and appears in the dashboard. Activation means confirming it’s online and pointing the dashboard at its local URL so you can use the playground, logs, and traces.

​
Step 1 — Watch it appear

Back in the dashboard, open Gateways (/dashboard/gateways). Within about a minute of starting the container, a new row appears with a status badge:
StatusMeaning
PendingRegistered but no heartbeat yet. Usually resolves in <60s.
OnlineHeartbeat received. Ready to serve requests.
OfflineNo heartbeat in the last interval. Check the container.
RevokedCredentials revoked from the dashboard; the gateway is blocked from reconnecting.
Gateways list
Each row shows the version the gateway reports, its last-seen timestamp, and the LAN/WAN IPs it detected. Click the row to open the detail page.

​
Step 2 — Give it a name

On the detail page, click the pencil next to the display name and give the gateway something meaningful (prod-us-east-1, staging-laptop, etc.). This is purely cosmetic but helps when you have more than one.
Rename gateway

​
Step 3 — Connect the dashboard

Click Connect. A dialog asks for the URL the dashboard should use to reach the gateway directly. The LAN IP the gateway reported is pre-filled; edit it if you expose the gateway on a different host or port.
  • Local LAN: http://192.168.1.42:8080
  • Reverse-proxied: https://gateway.internal.example.com
Connect to gateway
The dashboard authenticates to the gateway with a per-session JWT derived from your Supabase token. Nothing else to configure.
If the URL later changes (you moved the container, added TLS, etc.) the dashboard detects the stale URL on the next 401 or network error, clears it, and prompts you to reconnect. You don’t need to “unregister and re-register.”

​
Step 4 — Confirm the connection

The detail page now shows live data from the gateway: version, uptime, loaded config digest, and a small activity graph. If you see these, activation is complete.

​
Troubleshooting

Check docker logs guardway-gateway. Most common causes: outbound egress to api.guardway.ai:443 blocked, system clock skew > 5 minutes, or registration token already consumed.
The dashboard has to reach the gateway’s local URL, not the cloud. If your laptop cannot ping the gateway host on port 8080, expose it or run the dashboard from a machine that can.
Delete the pending row in the dashboard and click Register New Gateway again. Tokens live for 1 hour.

​
Next step

Connect a provider

A gateway without providers cannot serve inference. Add one now.