MANAGED L4 BALANCING ON OUR OWN EU CLOUD
Load Balancers
High Availability, the Boring Way.
A stable public IP, health checks and a backend pool you can reshape at any time. Created in minutes, billed hourly from your credit balance.From €7.30/month. Built on OpenStack Octavia, Kubernetes-integrated.
ONE STABLE IP IN FRONT OF EVERYTHING
Built for Uptime
Health checks, member management and Kubernetes integration, without running HAProxy yourself.
Real L4 Balancing
TCP load balancing across your cloud servers with a dedicated public IP, built on OpenStack Octavia, the same engine large private clouds run.
Health Checks Built In
The balancer probes your backends and routes traffic only to healthy ones. A dying server drops out automatically; a recovered one rejoins.
Members In, Members Out
Add or remove backend servers from the pool at any time, scale out behind a stable IP without touching DNS.
Stable Public Entrypoint
The balancer's IP is yours for its lifetime. Replace every backend behind it; the address your users hit never changes.
Kubernetes Integration
Service type LoadBalancer in our Managed Kubernetes provisions one of these automatically, no manual wiring.
API-First
Create the balancer, listener, pool and members from the console or the public REST API, scriptable end to end with scoped tokens.
TWO WAYS TO GET ONE
Console or YAML
Console → Cloud → Load Balancers → Create
1. Name it, pick the listener port (e.g. 443)
2. Add backend members (your cloud servers)
3. Set the health-check port
→ public IP attached automaticallyANSWERS TO YOUR MOST COMMON QUESTIONS
Frequently Asked Questions
How are load balancers billed?
Hourly from your credit balance at €0.01/hour, about €7.30/month, capped like every cloud resource. The exact live rate is always shown in the console before you create one, and there are no traffic-based surprise charges.
What does it balance?
TCP (layer 4) traffic, web servers, APIs, game servers, databases with read replicas. You define a listener port, a backend pool and a health check; the balancer does the rest.
How do health checks work?
You set the check port and interval; backends failing the probe are taken out of rotation automatically and re-added when they pass again.
Can it balance servers in other clouds?
It targets RareCloud cloud servers in the same region (private network). For mixed setups, put it in front of your RareCloud tier and keep cross-provider routing at DNS level.
How many can I create?
As many as your project quota allows, quotas are per-customer and raised on request via a support ticket.
Does it work with Kubernetes?
Yes, exposing a Service of type LoadBalancer in our Managed Kubernetes provisions one automatically, wired to your nodes.
Ready to get started?
One Stable IP in Front of Everything
Health-checked, hourly-billed, ready in minutes.