rarecloud
L4 LOAD BALANCING IN EUROPEHOURLY BILLING

Load Balancer

One stable address in front of your servers.

Spread traffic across your Cloud VMs and send it only to the servers that answer. Create one from the console, from your scripts, or let your AI agent do it for you.€9/month with its public IPv4 · billed by the hour · health checks on by default · engineers on support 24/7

Get StartedCreate a Load Balancer
One price per load balancer
€9a month

Billed by the hour, about €0.0123 an hour, and never more than €9 in a month.

  • A public IPv4 that stays the same for the balancer's lifetime
  • TCP health checks on every server
  • No charge per connection or per GB

Prices exclude VAT. The console shows the price before you create one.

What people use it for

  • Websites and APIs

    HTTPS on port 443, spread across several web servers behind one address.

  • Updates without downtime

    Take one server out, update it, put it back, while the others keep serving.

  • Database read replicas

    Spread read queries across replicas on one TCP port, such as 5432 or 3306.

  • Kubernetes ingress

    A Service of type LoadBalancer in front of your ingress controller.

Set It Up Your Way

Point your DNS at the balancer's address once. Behind it, add servers when traffic grows and take them out for maintenance, without touching DNS. The console, the API, the CLI, Terraform and the MCP server all create the same balancer at the same price.

Your DNS points here, once
203.0.113.10 : 443
Load balancer
TCP, round robin · checks each server every 5 seconds
web-01
Answering
web-02
Answering
web-03
No answer
After three failed checks a server stops getting traffic. When it passes three checks in a row, it is back in rotation.
resource "rarecloud_load_balancer" "web" {
  name              = "web-lb"
  port              = 443
  health_check      = true
  member_server_ids = [
    rarecloud_server.a.id,
    rarecloud_server.b.id,
  ]
}

output "lb_ip" {
  value = rarecloud_load_balancer.web.ipv4
}

Read the API referenceUse the Terraform providerInstall the CLI

Included With Every Balancer

A public IPv4, health checks and room to change the servers behind it, in the same region as your Cloud VMs.

One Stable Public IPv4
Each balancer gets its own public IPv4 that stays the same for its lifetime. Replace every server behind it and the address your users reach does not change.
Health Checks
Each server gets a TCP check on its port every 5 seconds. After three failed checks it stops getting traffic, and it rejoins after it passes three checks in a row.
TCP on Any Port
Balance any TCP service on a port from 1 to 65535: websites, APIs, mail or database replicas. TLS passes through, so your certificates stay on your servers.
Round Robin
New connections are spread in turn across every server that passes its health check.
Servers In and Out
Add a server to take more traffic, or remove one for maintenance, from the console, the API or the CLI. A server you add later can listen on its own port.
Cloud VMs Behind It
Members are Cloud VMs in your account, in the same region as the balancer. Pick them when you create it, or add them later.
Kubernetes Services
In Managed Kubernetes, a Service of type LoadBalancer creates one of these for you, and the cluster keeps its servers up to date.
API, CLI, Terraform, MCP
Create a balancer with its port and servers in one API call, CLI command or Terraform resource, or ask your AI agent, which asks you before it spends.

Works with Cloud VM and Managed Kubernetes

The Rest of the Cloud

Same account, same console, same monthly invoice. Each piece has a published price, shown before you create it.

Cloud VM

Hourly cloud servers

The servers behind your balancer, ready in less than a minute, with a public IPv4 and traffic included.

From €3.99/mo

See Cloud VM

Kubernetes

Managed clusters

Run containers with the control plane included. Services of type LoadBalancer get a balancer like this one.

Workers from €7.99/mo

See Kubernetes

Block Storage

Volumes

Disks that live apart from any server. Attach them, detach them and move them with their data.

€0.05 per GB a month

See Block Storage

Object Storage

S3-compatible

Buckets for backups, media and static files, used with the S3 tools you already know.

€10/mo with 1 TB

See Object Storage

Billed by the Hour

A load balancer is metered from the moment you create it until you delete it, at €9 a month with its public IPv4 included, and a month never costs more than €9. Use one for a two-day launch and you pay for two days. It goes on the same monthly invoice as your servers, and the credit on your account pays each invoice automatically. Pay by card, PayPal, Alipay, crypto or bank transfer, in EUR or USD.

How cloud billing works

Region
Our European cloud region, in Bucharest, inside the EU. More regions in Europe and the US are planned.
Support
24/7. Engineers answer the tickets.
Invoices
From Rare Mood Agency SRL (RareCloud), with EU VAT, in EUR or USD.

Questions Before You Create One

How is a load balancer billed?
€9 a month, with its public IPv4 included. It is metered by the hour, about €0.0123 an hour, from the moment you create it until you delete it, and its charge for a month stops at €9. It is invoiced monthly with your servers, and the console shows the price before you create one. There is no charge per connection or per GB on the balancer.
How long does it take to create one?
A few minutes. The balancer appears in your account at once, then its listener, servers and public IP are set up in the background, and it shows as active when it is ready. If a request seems to fail, check your load balancers before you create another one. Scripts can send an Idempotency-Key header, so a retried request returns the same balancer instead of building a second one, and the CLI's --wait option waits until it is active.
What can it balance?
TCP traffic on one port per balancer, from 1 to 65535: web servers, APIs, mail, database replicas. New connections are spread round robin across the servers that pass their health check. To balance two ports, create two balancers.
Can one balancer serve both HTTP and HTTPS?
Each balancer has one listener, on the port you choose, so it serves one port. For a website, put it on 443 and point your domain at its address: HTTPS reaches your servers, which keep the certificates. A second balancer for port 80 would get its own address, so it cannot answer for the same domain. To keep browsers on HTTPS, send an HSTS header from your servers, and add your domain to the HSTS preload list so browsers never try plain HTTP.
Do my servers see the visitor's IP address?
No. The balancer passes TCP connections through and opens its own connection to your server, so your server sees the balancer as the client. It does not add a PROXY protocol header or an X-Forwarded-For header. Plan logs, rate limits and geo-IP rules with that in mind.
Does it support IPv6 or UDP?
It balances TCP over IPv4. Each balancer gets one public IPv4 address, and any TCP service on one port works behind it. IPv6 and UDP are not available on balancers today.
How do the health checks work?
Each server is checked over TCP on its port every 5 seconds, with a 3 second timeout. After three failed checks in a row it stops getting new traffic, and it comes back once it passes again. Checks are on by default. You can create a balancer without them, and there is no interval or HTTP path to configure today.
Where do my TLS certificates live?
On your servers. The balancer passes TCP through without decrypting it, so HTTPS stays encrypted all the way to your servers, and you issue and renew certificates there as you do today. For routing by host name or path, run a reverse proxy or an ingress controller on the servers behind it.
Which servers can I put behind it?
Cloud VMs in your account, in the same region. You need at least one to create a balancer, and you can add or remove servers at any time from the console, the API or the CLI. A server you add later can listen on a different port. Kubernetes worker nodes are managed by their cluster: use a Service of type LoadBalancer for those.
Does the public IP ever change?
No. The balancer keeps its public IPv4 for as long as it exists, however often you change the servers behind it, so you point DNS at it once. The address is released when you delete the balancer. In Terraform, changing the port or the member list replaces the balancer and gives it a new address, so manage members from the console, the API or the CLI if the address must stay.
How does it work with Kubernetes?
In RareCloud Managed Kubernetes, a Service of type LoadBalancer creates a load balancer in your account, and the cluster keeps its members in step with your nodes. It is billed like any other load balancer. To serve several apps from one address, put an ingress controller behind a single Service.
What do I need to create one?
An account with at least one Cloud VM. New accounts prepay: your balance covers the first month of what you run. Once your account has paid twice and is a few weeks old, new resources go on the monthly invoice.

One Stable Address for Your Servers

€9 a month with its public IP, billed by the hour.

Create a Load Balancer