Gateway
As a gateway, devgate sits in front of your APIs and services: it terminates TLS, runs your Traffic Policy, balances traffic across the machines that serve it and logs every request — and your services need no public IP or open port. The dashboard walks through it under Get started → Gateway.
Put a service behind the gateway
Run the agent next to the service, on your dev domain:
$ devgate http 80 --url https://your-dev-domain.devgate-free.run
Start the same command on more machines with --pooling-enabled and the URL's traffic is
load balanced between them; stop one and the rest carry on.
Keep services private
Start services on internal endpoints
(--url https://api.internal) — unreachable from the internet — and put a
cloud endpoint on your public domain in front of them. The cloud endpoint lives at the
edge, stays online with no agent running, and routes each request to an internal endpoint with
forward-internal.
Secure and shape traffic
Policy runs at the edge, before a request reaches any machine: allow only some IPs
(restrict-ips), rate limit callers
(rate-limit), require a password
(basic-auth), verify webhooks, rewrite URLs and set headers. Pass it
with --traffic-policy-file, or edit it on the endpoint's page in the dashboard.