Skip to content
Latest (currently 2026.11.0) has the newest features, bug fixes, and CVE patches of Solo Enterprise for agentgateway.

For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

Licensing

Enterprise
Page as Markdown

Supply a license key to standalone Solo Enterprise for agentgateway, and understand what happens when that key expires.

Solo Enterprise for agentgateway checks for a valid license key every time the proxy starts. This check is the main operational difference between the enterprise proxy and the open source project, which needs no key at all. A proxy that cannot present a valid key does not start.

The check runs at startup only. A proxy that is already running is never stopped because its license changed, so an expiry never interrupts traffic that is already flowing. It changes what happens the next time that process restarts.

Note

This page covers standalone mode, where the license belongs to the proxy itself. In Kubernetes mode, the control plane holds the license and the proxies it manages take theirs from it. A proxy that an agentgateway control plane manages ignores the settings on this page.

Where the proxy looks for the key

The proxy reads the key from one of two places, and the environment variable wins when both are set.

SourceSet it withUse it when
Environment variableENTERPRISE_AGENTGATEWAY_LICENSE_KEYThe key comes from your own secret store, your CI system, or a Kubernetes Secret.
Configuration fileconfig.license.keyYou want one artifact that describes the whole installation, including the key or the path to it.

The configuration file field takes the key inline or reads it from a file on disk.

# yaml-language-server: $schema=https://docs.solo.io/agentgateway/standalone/latest/reference/configuration/config.json
config:
  license:
    key:
      file: /etc/agentgateway/license/license-key
gateways:
  default:
    port: 4000

Important

Prefer the file form or the environment variable for anything beyond a local trial. An inline key is stored in whatever holds your configuration file, which for the Helm chart is a ConfigMap that any reader of the namespace can print.

# yaml-language-server: $schema=https://docs.solo.io/agentgateway/standalone/latest/reference/configuration/config.json
config:
  license:
    key: eyJh...
gateways:
  default:
    port: 4000
FieldDescription
config.license.keyThe license key as a string.
config.license.key.filePath to a file whose contents are the license key. Surrounding whitespace is trimmed, so a trailing newline is fine.

Set the license

Set the license key for your method of installing the agentgateway binary.

Binary

Set the license as an environment variable for quick testing, or put the license in a file for more secure storage.

Export the key in the shell that starts the proxy.

export ENTERPRISE_AGENTGATEWAY_LICENSE_KEY=<license-key>
agentgateway -f config.yaml

Keep the license key in a secure file to prevent the key from being leaked in your shell history and environment.

  1. Write your license key to a file at a secure location.

    echo -n '<license-key>' > license.key
    chmod 600 license.key
  2. Update your agentgateway configuration to refer to the license key file.

    # yaml-language-server: $schema=https://docs.solo.io/agentgateway/standalone/latest/reference/configuration/config.json
    config:
      license:
        key:
          file: ./license.key
    gateways:
      default:
        port: 4000

Docker

Set the license as an environment variable for quick testing, or put the license in a file for more secure storage.

Set the environment variable for the Docker container.

docker run -d \
  --name agentgateway \
  -e ENTERPRISE_AGENTGATEWAY_LICENSE_KEY=<license-key> \
  -p 4000:4000 \
  us-docker.pkg.dev/solo-public/enterprise-agentgateway/agentgateway-enterprise:2026.11.0

To keep the key out of the container definition, mount a file that holds it and point config.license.key.file at the mount path inside the container.

  1. Write your license key to a file.

    echo -n '<license-key>' > license.key
    chmod 600 license.key
  2. Create a configuration file that reads the key from the path that you mount it at.

    # yaml-language-server: $schema=https://docs.solo.io/agentgateway/standalone/latest/reference/configuration/config.json
    config:
      license:
        key:
          file: /license/license.key
    gateways:
      default:
        port: 4000
  3. Mount both files and start the container. The key is mounted read-only, and the path in the container must match the file value in your configuration.

    docker run -d \
      --name agentgateway \
      --user "$(id -u):$(id -g)" \
      -v "$PWD/config.yaml:/config.yaml" \
      -v "$PWD/license.key:/license/license.key:ro" \
      -p 4000:4000 \
      us-docker.pkg.dev/solo-public/enterprise-agentgateway/agentgateway-enterprise:2026.11.0 \
      -f /config.yaml

Helm

The chart has no dedicated license value. Supply the key through one of the general-purpose hooks that the chart does have.

To keep the key out of the ConfigMap and Deployment, store the license key in a Kubernetes Secret.

  1. Create a Kubernetes Secret with the license key.

    kubectl create secret generic agentgateway-license \
      -n agentgateway-system \
      --from-literal=license-key='<license-key>'
  2. Update your agentgateway configuration values.yaml file to refer to the Secret.

    config:
      config:
        license:
          key:
            file: /etc/agentgateway/license/license-key
    extraVolumes:
      - name: license
        secret:
          secretName: agentgateway-license
    extraVolumeMounts:
      - name: license
        mountPath: /etc/agentgateway/license
        readOnly: true
  3. Install agentgateway with the configuration.

    helm upgrade -i enterprise-agentgateway-standalone \
      oci://us-docker.pkg.dev/solo-public/enterprise-agentgateway/charts/enterprise-agentgateway-standalone \
      --namespace agentgateway-system \
      --create-namespace \
      --version v2026.11.0 \
      --reuse-values \
      -f values.yaml

Set the environment variable for the license key in the Helm installation command. Note that this method stores the value of the license key in plain text in the Kubernetes Deployment.

helm upgrade -i enterprise-agentgateway-standalone \
  oci://us-docker.pkg.dev/solo-public/enterprise-agentgateway/charts/enterprise-agentgateway-standalone \
  --namespace agentgateway-system \
  --create-namespace \
  --version v2026.11.0 \
  --set-json 'extraEnv=[{"name":"ENTERPRISE_AGENTGATEWAY_LICENSE_KEY","value":"'"<license-key>"'"}]' \
  --reuse-values \
  -f values.yaml

Verify the license

To confirm which key a running proxy actually loaded, read /api/runtime rather than the configuration file. A proxy that was started with the environment variable set reports that key, even if the configuration file has a different value.

When agentgateway is running, send a request to the admin address on the /api/runtime path.

curl -s localhost:15000/api/runtime | jq .license
  1. Port-forward the agentgateway admin address.

    kubectl port-forward -n agentgateway-system \
      deploy/enterprise-agentgateway-standalone 15000:15000
  2. Send a request to the admin address on the /api/runtime path.

    curl -s localhost:15000/api/runtime | jq .license

Example output for a licensed proxy:

{
  "state": "running",
  "product": "agentgateway",
  "expiresAt": "2027-08-17T17:45:00Z"
}

If the license is expired, you might see a grace state. During the grace period, the proxy still starts until the reported date. Make sure to update the license to continue service.

{
  "state": "grace",
  "reason": "licenseExpired",
  "graceDeadline": "2026-09-01T17:45:00Z"
}

Next steps