Endpoint pooling
When two endpoints have the same URL (and binding), they form a pool and share its traffic: each request goes to one of them at
random. Start every agent with --pooling-enabled:
$ devgate http 8080 --url https://api.example.internal --pooling-enabled Run the same command on a second machine — or a second process — and both serve the URL. Stop one and the rest carry on, which makes restarts and deploys invisible to visitors.
Without pooling
By default a URL takes one agent: a second start on it fails with “already online”, so you never end up load balancing by accident. Pooling has to be allowed by every endpoint in the pool, the first one included.
Billing
Each pooled endpoint is its own endpoint: two agents on one URL count as two online endpoints and accrue their active hours separately, wherever they run.