Nextify Load Balancer
HTTPS with automatic certificates, HTTP/2, WebSockets, TCP and UDP, in front of your instances on a private network.
A managed load balancer with its own public IPv4 address. It terminates HTTPS with certificates it gets and renews by itself, routes each request by host, path, header, cookie or source address, and spreads traffic across the instances on your private network, taking a server out of rotation when its health check fails. Plain TCP and UDP are forwarded in the Linux kernel. Every setting is one versioned configuration you can change in the portal or through the API, and roll back in one click.
HTTPS with automatic certificates
Point a domain at the load balancer and it gets a Let's Encrypt certificate and renews it before it expires, or upload your own. TLS 1.3 and 1.2, HTTP/2 and WebSockets.
TCP and UDP
Databases, mail, MQTT, game servers, DNS, VoIP. Plain TCP and UDP are forwarded in the Linux kernel, with no user-space proxy in the path.
Routing rules
Ordered rules on host, path, method, header, query, cookie, source address or SNI: send to a pool, redirect, answer, deny, rewrite paths and headers.
Health checks you can see
HTTP, TCP or send-and-expect checks. A failing server leaves rotation and returns when it recovers; each server's state and last check result are in the portal and the API.
Sticky sessions
Keep a client on one server with a cookie or by source address. Balance round robin, by least connections, or by a hash of the source, URI or a header.
Built-in L7 protection
Per-IP request and connection rate limits, a cap on open connections per IP, maximum body size, allow and deny lists, and temporary bans that stop repeat offenders in front of the load balancer.
Private network backends
The load balancer joins your private network and reaches instances on it, or on other networks of your VPC through its routes, so backends need no public IP.
Intrusion prevention
An optional tier on bigger nodes (2 vCPU, 1.5 GiB): threat-intel feeds such as Spamhaus DROP, bans that escalate for repeat offenders, one blacklist for every load balancer of your account, and Protocol Studio rules that ban clients breaking your protocol's format. Every intrusion prevention setting exports to one file you can import elsewhere.
Protocol Studio included
Describe your own binary protocol as a pattern, then check health by its reply's fields, set weights from them, route TCP and UDP connections on them, and trace live traffic with breakpoints. Part of every load balancer at no extra cost.
Versioned config, one-click rollback
The whole configuration is one JSON document, edited in the portal or through the API. Every change is a new version, checked first and applied without dropping connections; restore any earlier one in one click.
Protocols
Nodes
A load balancer runs on one or more nodes in one region, in front of instances in the same region. The nodes share its public IPv4 address and the connections: each new connection goes to one of them and stays there. Add or remove nodes at any time; the address stays the same, and if a node stops, the others keep serving.
Included with every load balancerNo extra cost: open it from any load balancer in the portal
Protocol Studio: load balancing that understands your protocol
Describe your binary protocol once, as a pattern. Health checks then read the reply field by field, servers get weights from what they report, rules route on fields, live metrics count them, and you can watch and pause live traffic, one connection at a time. Every packet is decoded in the kernel at native speed. Game servers, IoT devices, custom RPC: bring your own protocol.
The standard health checks (HTTP, TCP, TCP and UDP send/expect) stay as they are; Protocol Studio adds to them.
Pricing
$9/moper node
$0.0123/hr billed by the hour, never more than the monthly price
$18/mo per node with intrusion prevention
2 vCPU and 1.5 GiB per node, threat-intel feeds, ban escalation, an account-wide blacklist and protocol IPS rules. Switch an existing load balancer either way; it keeps its IP and settings.
- Includes the load balancer's public IPv4 address and its certificates.
- Billed from create to delete, like an instance. Outbound transfer counts toward your account's transfer allowance.
- Each node is billed on its own: add nodes for more capacity, remove them when you no longer need it.
For comparison, one load balancer node per month: DigitalOcean $12.00, Linode $10.00, Vultr $10.00 (list prices, October 2026).
Ready when you are
Sign in to the portal and create one in a single screen.