Self-host Agentgateway with Levelrail

Proxy built for agent traffic that routes MCP, A2A and LLM requests. The install form carries config.yaml as an editable file, so it starts with a listener that answers on port 3000.

  • Authoragentgateway
  • LicenceApache-2.0
  • Memory128 MiB
  • Services1

How to self-host Agentgateway

  1. Pull the images

    One image is pulled on your server.

    Show images
    • ghcr.io/agentgateway/agentgateway:v1.7.0
  2. Create the app

    One service starts in a single Compose app, on port 3000.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Open the address to see the starter response, then edit the config file setting to add your MCP servers, LLM backends and policies.

Agentgateway requirements

Memory
About 128 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
3000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Agentgateway. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Agentgateway docs page.

Deploy Agentgateway your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Agentgateway from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain agentgateway=app.example.com.

levelrail-cli templates install agentgateway --name my-agentgateway

Deploy Agentgateway with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/agentgateway/install \
  -d '{
    "name": "my-agentgateway"
  }'

Agentgateway configuration

Agentgateway services

ServiceImagePortsVolumes
agentgateway ghcr.io/agentgateway/agentgateway:v1.7.0 3000 none

Agentgateway environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
3000
Volumes
none

Agentgateway FAQ

How much memory does Agentgateway need?

The catalog lists about 128 MiB of memory for Agentgateway.

Does Agentgateway run on arm64?

For Agentgateway, arm64 support is not confirmed; amd64 is unknown.

What licence is Agentgateway under?

Agentgateway is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does Agentgateway need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Agentgateway use?

Agentgateway listens on port 3000 inside the stack.

Can I deploy Agentgateway on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Agentgateway, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image ghcr.io/agentgateway/agentgateway:v1.7.0 is what you deploy there.

levelrail-cli templates install agentgateway --name my-agentgateway