Skip to content

Load balancer

One address in front, as many servers as you need behind.

Traffic spread across your servers, with health checks that take a sick one out of rotation before your customers find it. From $25.90 a month, in Amsterdam, Atlanta, Mumbai, Jakarta, Dallas, Frankfurt, Sao Paulo, Washington, Osaka, Los Angeles, London, Chennai, Madrid, Melbourne, Miami, Milan, Tokyo, New York, Chicago, Paris, Seattle, Silicon Valley, Singapore, Stockholm, Sydney, Toronto.

Order a load balancerAdd servers behind it

Price

What it costs, and what that includes.

Three tiers, flat monthly. The difference between them is throughput and connection capacity — most sites never leave the first one.

  • LB-STANDARD

    Standard load balancer — one public address in front of as many servers as you like

    $25.90 / mo

  • LB-PREMIUM

    Premium load balancer — one public address in front of as many servers as you like

    $378.90 / mo

  • LB-ENTERPRISE

    Enterprise load balancer — one public address in front of as many servers as you like

    $756.90 / mo

Runs in: Amsterdam, Atlanta, Mumbai, Jakarta, Dallas, Frankfurt, Sao Paulo, Washington, Osaka, Los Angeles, London, Chennai, Madrid, Melbourne, Miami, Milan, Tokyo, New York, Chicago, Paris, Seattle, Silicon Valley, Singapore, Stockholm, Sydney, Toronto.

How you get it: set up by hand today, within business hours — someone reads the order before anything is built, and you get the details by email. We are writing the automation; until it is done and tested, this is the honest timing.

What you get

The parts that are ours.

Health checks that act

A backend that stops answering is taken out of rotation and put back when it recovers. That is the whole point: a deploy gone wrong on one server becomes a slower page rather than an outage.

TLS terminated for you

Certificates live on the balancer, so your servers can speak plain HTTP behind it and you renew in one place instead of on every machine.

A fixed address

The public IP belongs to the balancer, not to any one server. Servers behind it can be rebuilt, resized or replaced without touching DNS — which is what makes zero-downtime deploys possible at all.

Honesty

When you should not buy this.

One server with a good uptime record does not need this — a load balancer in front of a single machine adds a monthly bill and a second thing that can break, without removing the single point of failure. Buy it when you have two or more servers to spread across, or when you are about to. If you only want TLS and caching in front of one site, a CDN is cheaper.

Questions

The ones worth asking first.

Does it make my site highly available?
Only if there is more than one server behind it, in a shape where losing either one still serves requests. A balancer in front of one machine, or in front of two machines that share one database, moves the single point of failure rather than removing it. Tell us what you run and we will say plainly whether this helps.
Can it terminate TLS with my own certificate?
Yes — bring your own certificate and key, or a Let's Encrypt one. Renewal is handled in one place instead of on each server.
How many servers can sit behind it?
More than you are likely to have. The tiers differ by throughput and concurrent connections, not by backend count, so pick the tier from traffic rather than from how many machines you own.
How fast do I get it?
It is set up by hand today — within business hours, and someone reads the order before it exists. That is the honest state of it while the automation is being written.