Don’t let your traffic pile up on a single server. portvMind Load Balancer, with load balancing at L4 and L7, automatically distributes your requests across healthy instances; when a server stops responding, your users notice nothing.
A load balancer is a layer that distributes incoming traffic to the pool of servers behind it according to rules you set. The user connects to a single address; the load balancer decides which server the request goes to.
It provides two core functions. The first is scaling: you handle traffic that a single server cannot by splitting it across many servers. The second is availability: the load balancer regularly probes the servers behind it and stops sending traffic to one that doesn’t respond. When a server goes down, your users don’t notice.
portvMind Load Balancer works at both L4 and L7. At L4 you distribute TCP and UDP connections by port. At L7 you can route to different server pools by looking at the content of the HTTP request — by path, header or domain name. This lets you publish multiple services from a single entry point in microservice architectures.
Instances that don’t respond are automatically removed from the traffic pool and returned when they recover.
Simple balancing at the TCP/UDP level or HTTP path- and header-based routing.
Manage your certificate on the load balancer and free your backend servers from that load.
Route the same user’s requests to the same instance when needed.
The availability and updates of the load balancer itself are our responsibility.
Track the active connection count and backend health from the console.
| Feature | Detail |
|---|---|
| Layer | L4 (TCP/UDP) and L7 (HTTP/HTTPS) |
| Health checks | HTTP, TCP and custom check definitions |
| SSL/TLS | Certificate upload and termination |
| Session persistence | Cookie- and source IP-based |
| Integrations | Floating IP · Kubernetes service exposure |
| Metering | Per minute — for the time it runs and the traffic it processes |
Distribution algorithms and configuration options are covered in the documentation.
For detailed technical specifications and release notes, see Documentation
Enter your load balancer configuration and see the total cost instantly.
Metering: Per minute — based on the time it runs and the traffic it processes
Your resources are metered for as long as they are running — you never pay for time you don’t use. In the console you can define a monthly or period-specific budget and get alerts when your spending reaches the 50%, 80% and 100% thresholds. Turn on overrun forecasting to see in advance whether your current consumption rate will take you over budget by the end of the period.
Alerts arrive by e-mail; with webhook support they can also be sent to Slack, Microsoft Teams or your own application.
Budget alerts send notifications; they do not stop resources automatically. You decide which resource to scale down.
The full pricing modelThere is no practical limit on the number of instances you can add to the pool; capacity scales with your needs.
You can upload your certificate to the load balancer configuration and terminate HTTPS there.
Requests are sent to the backend instances at the intervals you set. If the number of failed responses you define is reached, the server is removed from the pool; when it recovers it is returned automatically.
Yes. You can use the load balancer integration when exposing your services on Kubernetes.