Containers · in-mumbai-1 · in-noida-1

Load Balancing Made Simple, Fast & Predictable

Reliable load balancing with flat monthly pricing, SSL offload, health checks, sticky sessions, and static IPs, without complicated usage-based charges.

Control plane ₹0Workers from ₹999/moUpgrades one-clickAutoscale min/max nodesCNI + CSI integrated

Capabilities

Powerful Infrastructure. Built for Your Business

What is the purpose of a load balancer?

A load balancer distributes incoming network traffic across multiple servers to prevent overload, improve performance, increase availability, and ensure reliable application delivery.

What are the four types of load balancers?

The four common types are Layer 4 Load Balancer, Layer 7 Load Balancer, hardware load balancer, and software load balancer. Each type handles traffic differently based on network requirements.

What is a Layer 7 load balancer?

A Layer 7 load balancer operates at the application layer of the OSI model. It can route HTTP/HTTPS traffic based on factors such as URLs, headers, cookies, and application content.

Is a load balancer a VM?

A load balancer can be deployed as a virtual machine (VM), physical appliance, cloud service, or software-based solution. The deployment depends on the infrastructure and traffic requirements.

What are four types of firewalls?

Four common firewall types are Packet-Filtering Firewall, Stateful Inspection Firewall, Proxy Firewall, and Next-Generation Firewall (NGFW). Each provides different levels of traffic filtering and network security.

Static VIP + live metrics

One IPv4 that never changes under DDoS-filtered transit, with per-rule connection and traffic graphs in the console.

Under the hood

HAProxy on redundant virtual routers

Rules configure HAProxy on CloudStack virtual routers — Dedicated HA runs an active-passive pair with sub-second VIP failover. Stickiness maps to LbCookie, AppCookie and SourceBased policies; autoscaling uses CloudStack autoscale VM groups.

TCP and HTTP(S) modes, WebSocket-friendly timeouts
Certificate upload with full-chain validation, per-SNI routing
Backend pools managed by API, console or Terraform
Failover pair in Dedicated HA — maintenance without a maintenance window
VIP and backends both live in India

Frequently asked questions

TCP or HTTP mode — which do I want?+

HTTP(S) mode for web apps: you get SNI routing, cookie stickiness and header-aware checks. TCP mode for databases, MQTT, game servers or anything that isn't HTTP. Both are available on every plan; SSL offload needs Pro or above.

Can I bring my own certificate?+

Yes — upload certificate, chain and private key, and attach per rule. Pro and Dedicated support multiple certificates on one VIP via SNI. Automated renewal via API fits neatly into a certbot deploy hook.

How fast do failed backends leave rotation?+

Health checks run at your configured interval (default 5 s) with a failure threshold (default 2) — so a dead node stops receiving traffic in roughly 10 seconds and rejoins automatically once probes pass.

Does it autoscale my servers?+

Yes, via autoscale groups: define a template, min/max count and a CPU threshold. The platform provisions or destroys instances and keeps the LB pool in sync — no external scripts.

What happens when I outgrow a plan?+

Upgrade in place — the VIP stays, connections drain gracefully. If you're pushing past Dedicated HA's 200k concurrent, talk to us about a custom pair.

Pairs well with

Complete the stack

Cloud ServersThe D-series backends this balancer fronts→VPCKeep LB-to-backend traffic on a private tier→Managed Kubernetestype=LoadBalancer Services wired automatically→