Distribute traffic to healthy targets
Put a managed load balancer in front of your application in minutes. It distributes TCP (L4) and HTTP/HTTPS (L7) traffic across multiple targets, automatically takes unhealthy targets out and handles TLS termination. Manage it from the panel, the REST API, Terraform or MCP (AI).
IPv4 + IPv6 · 20 TB traffic · health checks includedFixed monthly — 20 TB traffic and dual-stack IP included
The load balancer comes with a fixed monthly fee; 20 TB of traffic plus IPv4 + IPv6 are included. There is no extra charge for the traffic processed.
Everything you need to manage traffic
TCP or HTTP checks; you set the path, expected status code, interval and the healthy/unhealthy thresholds (rise/fall).
Upload your own certificate (leaf + intermediate chain); the private key is stored encrypted and HTTPS traffic is decrypted at the load balancer.
Every listener is live on both IPv4 and IPv6; no extra charge for IPv6.
Round-robin, least-connections or source-IP; keep the same client on the same target with sticky sessions.
Active connections, requests/s, traffic and each target's UP/DOWN status stream live in the panel.
End-to-end automation over the REST API, the official Terraform provider and MCP with AI.
Frequently asked questions about Load Balancer
You upload your own certificate (leaf + intermediate chain) and private key as PEM; the key is stored encrypted and not shown back in the panel. The load balancer handles TLS termination on the HTTPS listener. If you like, it automatically redirects HTTP to HTTPS.
No. Every plan includes 20 TB of traffic and there is no extra charge for the traffic processed; only the fixed monthly plan fee applies.
L4 (TCP) carries raw connections — ideal for databases, queues and custom protocols. L7 (HTTP/HTTPS) works at the application layer; it provides TLS termination, HTTPS redirection and session stickiness.
No. Health checks inspect the targets at the interval you set; after consecutive failures (the fall threshold) the target is removed from the pool and automatically brought back once healthy again (the rise threshold).
You can add listeners, targets and certificates and watch metrics from the panel; you can do the same over the REST API, the official Terraform provider, or MCP with AI assistants like Claude.
In L7 (HTTP/HTTPS) mode, WebSocket connections and HTTP/2 (ALPN) on the HTTPS listener are carried to the targets. For raw TCP workloads you use L4 mode.
Yes. Every listener runs dual-stack; IPv4 and IPv6 are live together and there is no extra charge for IPv6.