Quickstart

Ship your first load balancer

Point a hostname at AnyLB and route traffic to two origins — about five minutes end to end.

Last updated: August 18, 2026 · 5 min read

Before you start

You need a domain whose DNS you control and at least one reachable HTTP or HTTPS origin. AnyLB works with public endpoints, private origins, virtual machines, containers and serverless functions alike.

A domain you can add a CNAME record to
One or more reachable origin endpoints
An API token, or access to the AnyLB console

Create the load balancer

Create a pool, add your origins, and attach a health check. The CLI, Terraform and console produce exactly the same configuration — pick whichever fits your workflow.

shell

$ anylb lb create \    --hostname api.example.com \    --strategy latency \    --origin api-sin1.internal \    --origin api-fra1.internal \    --health-check /healthz --interval 2s ✔ Pool created          api-prod (2 origins)✔ Health checks on      3 probe regions✔ Certificate issued    api.example.com✔ Load balancer live    https://api.example.com Next: point a CNAME at edge.anylb.com

Point your domain

Add a CNAME from your hostname to the AnyLB endpoint shown in the console. Edge certificates are issued automatically as soon as the record resolves.

dns

api.example.com.   300   IN   CNAME   edge.anylb.com.

Verify traffic is flowing

Send a request and read the response headers to see which edge region handled it. Then open the log stream and confirm the origin and latency for that same request.