Skip to main content
Run the gateway on a single host with Docker Compose. Save the compose file as compose.yml, put a .env beside it, then run:
The gateway listens on port 8080. Check that it is healthy:
Pick the mode that matches your deployment. Connected is the default once LICENSE_KEY is set. Get LICENSE_KEY (and, in connected mode, EDGEE_SIGNATURE_KEY) from the Edgee Console under Org settings → On-Premise → Reveal deployment secrets.
The gateway fetches its configuration from Edgee on startup and keeps it in sync, and reports telemetry to your own OTLP collector.
compose.yml
.env
In connected mode the gateway also exports usage metering to Edgee at https://onprem-logs.edgee.ai/v1/logs, authenticated with your LICENSE_KEY, so usage shows up in the team dashboard. Override the destination with USAGE_OTLP_ENDPOINT (and USAGE_OTLP_HEADERS) to send it to your own collector instead — the license-key auth is still sent by default to that custom collector too; set USAGE_OTLP_USE_LICENSE_AUTH: "false" in environment to opt out.
Keep LICENSE_KEY and EDGEE_SIGNATURE_KEY out of version control. Store them in the .env file (add it to .gitignore) or inject them from your secret manager.
For production, pin the image to a released tag (for example ghcr.io/edgee-ai/gateway:1.9.0) instead of latest, so upgrades are deliberate.