Load Balancer — free. Yes, completely
Distribute traffic between servers, ride out load peaks and update backends with no downtime. On AWS a balancer costs ~$220/year, on Gcore — from €180/year. With us — $0: you pay only for the instances the traffic is distributed across.
Why you need a balancer
Fault tolerance, load peaks and zero-downtime updates — out of the box
Fault tolerance
One server went down — traffic automatically goes to the rest. Health checks regularly probe backends and remove dead ones from rotation, without your involvement.
Load peaks
A sale, an ad campaign, a stream under stress: add instances to the pool — the balancer distributes the load. Removed them after the peak — the bill went down.
Zero-downtime updates
Take servers out of rotation one by one, update them, put them back. Users notice nothing.
A single entry point
One IP/domain outward — any number of backends inside the private network (VPC). Backends with no public IPs at all — a smaller attack surface.
How it works
Three steps — and traffic is distributed across your servers
Create a balancer
In the panel: choose a location and a public IP ($3/mo — the only paid component).
Add backends
Instances from the pool, ports, health check rules.
Point the domain
The domain to the balancer's IP — and it's done.
private network, no public IPs
- Instance1
- Instance2
- Instance3
- InstanceN
Technical capabilities
- Protocols: HTTP, HTTPS, TCP
- Automatic backend health checks
- Management via the panel and API
Comparison with alternatives
A "free load balancer" is rare. Here's why it's not a trap
| Comparison with alternatives | OneCloudPlanet | AWS ALB | Gcore | DigitalOcean | Your own HAProxy on a VPS |
|---|---|---|---|---|---|
| Price/mo | $0 | ~$18 + traffic | from €15 | $12 | instance price + your time |
| Setup | panel/API, minutes | complex | panel | panel | manual, configs |
| Maintenance | us | AWS | Gcore | DO | you |
Your own HAProxy gives more flexibility — and that's fine too: run it on our instance. But for 95% of scenarios a managed balancer at $0 is the simpler answer. Competitor prices are approximate and may change.
Frequently asked questions
Fault tolerance at a price of… zero
Create a balancer, add a second instance — and your service will survive a server failure. You pay only for instances.
Latest publications
Everything you need to create a stable, secure and scalable environment
Cloud on-call handover checklist for reliable 24/7 support: prevent context gaps and speed up issue resolution
A practical cloud on-call handover checklist to keep support continuity, avoid missed alerts, and resolve incidents faster across shifts.
Cloud change freeze and rollback plan for safer production releases: reduce outage risk during critical updates
A practical change freeze and rollback framework to protect production stability, keep customer services available, and recover fast if an update fails.
Cloud maintenance window planning playbook for stable service updates: reduce disruption and keep customers productive
A practical cloud maintenance window playbook to plan updates safely, reduce disruption risk, and keep customer operations predictable.
Cloud instance disaster recovery testing playbook: prove restore readiness before real outages
A practical cloud disaster recovery testing playbook to validate restore readiness, reduce recovery risk, and keep customer services available during critical disruptions.
Cloud incident response runbook for faster service recovery: reduce downtime and protect customer experience
A practical cloud incident response runbook to reduce downtime, speed up service recovery, and keep customer operations stable during disruptions.
Cloud instance capacity planning calendar for predictable growth: keep services fast during peak demand
A practical monthly capacity planning calendar for cloud instance workloads to keep response times stable during peak demand and control infrastructure spending.
Cloud instance rightsizing and cost control playbook: keep performance stable while reducing monthly spend
A practical cloud instance rightsizing playbook to reduce monthly infrastructure spend while maintaining stable service performance.
OpenStack + Kubernetes multi-region failover checklist for stable client services
Practical multi-region failover checklist for OpenStack and Kubernetes to keep client-facing services stable during outages.
OpenStack + Kubernetes multi-region failover checklist for stable client services
Practical multi-region failover checklist for OpenStack and Kubernetes to keep client-facing services stable during outages.
Cloud instance monitoring and alerting baseline: prevent silent failures before they impact customers
A practical monitoring and alerting baseline for cloud instances to detect failures earlier, reduce downtime, and protect customer experience.