Load Balancers — hosted in Nairobi
Coming soonLoad Balancers
One IP in front, healthy servers behind.
Distribute HTTP, HTTPS, TCP and UDP traffic across your servers with smart health checks, SSL termination and automatic failover — at a flat monthly price with no per-request charges.
- HTTP, HTTPS, TCP & UDP
- SSL termination with auto-renewal
- Three locally-hosted regions — Nairobi, Dar es Salaam & Lagos
- Data residency for Kenya's Data Protection Act — your data stays in-country
- 99.99% uptime SLA
Launching soon · Local billing in KES, TZS & NGN
Pricing
One flat price, no per-request fees
Pick a size for your traffic. Data transfer between the load balancer and same-region backends is unlimited and included. In your currency, no forex.
Small
Hosted in Nairobi, Dar es Salaam & Lagos
- 10,000 concurrent connections
- 250 Mbps throughput
- Up to 20 backends
- Basic health checks
- Unlimited same-region transfer
Medium
Hosted in Nairobi, Dar es Salaam & Lagos
- 50,000 concurrent connections
- 1 Gbps throughput
- Up to 50 backends
- Advanced health checks
- Unlimited same-region transfer
Large
Hosted in Nairobi, Dar es Salaam & Lagos
- 100,000 concurrent connections
- 2.5 Gbps throughput
- Up to 100 backends
- Health checks with SSL verification
- Unlimited same-region transfer
Enterprise
Hosted in Nairobi, Dar es Salaam & Lagos
- 250,000+ concurrent connections
- 5+ Gbps throughput
- Unlimited backends
- Custom-script health checks
- Unlimited same-region transfer
Flat monthly pricing with no hidden fees and no per-request charges. Upgrade or downgrade tiers anytime with zero downtime. Prices exclude VAT; local currency figures are indicative and settled at checkout.
The platform
Everything between your users and your servers
Termination, health checks, persistence, and protection — handled at the edge of your stack so your backends just serve.
Automatic failover
Failing backends drop out of the pool instantly and traffic reroutes to healthy servers — no manual intervention.
Smart health checks
Probe backends over HTTP, HTTPS, TCP, or ICMP with custom intervals, timeouts, and recovery thresholds.
SSL/TLS termination
TLS 1.2 and 1.3 with SNI for multiple certificates, automatic renewal, and encryption offloaded from your backends.
Four balancing algorithms
Round Robin, Least Connections, Source IP Hash, and Weighted Round Robin — match the algorithm to the workload.
Session persistence
Cookie-based or source-IP sticky sessions keep stateful clients pinned to the same backend.
DDoS protection built in
Rate limiting and connection throttling at the balancer, before traffic ever reaches your servers.
IPv4 & IPv6
Full dual-stack support on every load balancer, at every tier.
Real-time monitoring
Live traffic, connection counts, backend health, and access logs with request-level detail.
API & Terraform
Create and manage balancers from a REST API or the Terraform provider — wired into your CI/CD.
Regions
Nairobi is home. The other two are there when you need them.
ke-1a is in Nairobi, and for a Kenyan business that is most of the argument. Your customers arrive on Safaricom, on Faiba, on Zuku, on Poa — 2.65 million fixed subscriptions and 84.1 million active SIMs, nearly all of them inside the country. Lineserve peers at KIXP, the neutral exchange TESPOK runs across four Nairobi facilities, so traffic between your instance and another of its 136 networks is handed over a few kilometres away. A round trip that starts and finishes inside the metro is typically around 2 ms.
That matters because of where Kenya's bandwidth comes ashore. Every international subsea cable lands at Mombasa — SEACOM, EASSy, TEAMS, PEACE, DARE1 and LION2 — and the capacity is hauled roughly 480 km inland before it reaches a Nairobi rack. Anything leaving the country still makes that trip. Domestic traffic takes the other route entirely, exchanged in Nairobi between networks in the same city, and choosing ke-1a decides which of those two journeys your checkout depends on.
Dar es Salaam and Lagos sit on the same account, the same API and the same shilling invoice. Open tz-1a when you start selling into Tanzania and want the data held there under Tanzanian law, or ng-1a when Lagos becomes a market rather than a pin on a map. They are also where a copy goes when you want one outside Kenya — a standby database, a backup bucket — which makes disaster recovery a configuration change instead of a second supplier.
Kenya
Nairobi
~2 ms
typical, within metro · Data stays in Kenya
Tanzania
Dar es Salaam
~6 ms
typical, within metro · Data stays in Tanzania
Nigeria
Lagos
~4 ms
typical, within metro · Data stays in Nigeria
Use cases
Built for what you're building
Web applications
Spread HTTP and HTTPS traffic across your web servers for high volume with zero downtime.
APIs & microservices
A single entry point routing requests across API instances and containerized services.
Database read scaling
Balance read queries across replicas while writes go straight to the primary.
Gaming & streaming
Low-latency TCP and UDP balancing for player connections and high-bandwidth media.
How it works
In front of your traffic in three steps
Create a load balancer
Pick a region and a size tier — live in under 60 seconds from the console or API.
Add backends & health checks
Point it at your servers, choose an algorithm, and set the health check that fits.
Point your DNS at it
One record change and traffic flows through — failover and monitoring are already on.
Uptime SLA
99.9%
- DDoS filtering is included, not an upsell
- Service credits applied automatically when we miss the SLA
- Measured monthly, per region, on network and power availability
Support
A Nairobi number, and East Africa Time all year
Kenya has its own line: +254 119 039 063. Alongside it are [email protected] and the ticket system, and Lineserve Limited keeps an office on Utalii Lane, View Park Towers, in the Nairobi CBD. A supplier with a street address in your own city is a different kind of counterparty from a web form and a billing address in another hemisphere.
Kenya runs on East Africa Time, UTC+3, and has never observed daylight saving. That reads like trivia until you are the one holding the phone. Business hours here mean the same thing in January and in July; nothing slides by an hour twice a year because another country changed its clocks. When your checkout starts throwing 502s at 09:20 on a Tuesday, it is 09:20 for whoever picks up — an ordinary working morning in the same city, rather than the small hours of somebody's Monday night, eight time zones west.
The other half of local support is vocabulary, not hours. The person you reach knows what a Safaricom callback is, what KIXP has to do with the trace you are staring at, and why your finance team wants a KRA PIN on the invoice. None of that has to be explained before the actual problem can be. Buy from somewhere that has never sold into Kenya and the first twenty minutes of every serious ticket go on describing the country.
Kenya
+254 119 039 063
Sales
Why Lineserve
Managed beats maintaining your own proxy
Running NGINX or HAProxy on a VPS means one more machine to patch, monitor, certify, and fail over — and it's usually the single point of failure in front of everything else.
FAQ
Questions, answered
It sits in front of your servers on a single IP and distributes incoming traffic across them. If a backend fails, traffic reroutes to healthy servers automatically — better availability, better performance, no single point of failure.
A flat monthly rate per size tier — Small, Medium, Large, or Enterprise. Data transfer between the load balancer and backends in the same region is unlimited and included. No per-request charges, no hidden fees.
Yes. Backends can be Lineserve Cloud Servers, VPS, dedicated servers, Kubernetes nodes — or servers hosted anywhere else, as long as the load balancer can reach them over the network.
Upload certificates to the load balancer and it terminates SSL/TLS for you, offloading encryption from your backends. TLS 1.2 and 1.3 are supported, with SNI for serving multiple certificates from one load balancer and automatic renewal.
The load balancer probes each backend over HTTP, HTTPS, TCP, or ICMP on an interval you set. Servers that fail their threshold are removed from the pool automatically and re-added once they recover.
Sticky sessions route a returning client to the same backend — essential for apps that keep session state locally. Choose cookie-based or source-IP persistence per load balancer.
Round Robin for evenly matched servers, Least Connections for long-lived connections, Source IP Hash to pin clients to a server, and Weighted Round Robin to send more traffic to bigger machines.
Yes. Upgrade or downgrade anytime with zero downtime — your configuration, certificates, and backend pools carry over unchanged.
Yes. Your data is hosted in Kenya and stays in-country, giving you data residency for Kenya's Data Protection Act. It isn't moved out of Kenya without your instruction.
In our Nairobi data centre (ke-1a). Your content is stored and served from Nairobi, close to your users.
Pay in your local currency using M-Pesa and other mobile money, bank transfer, or card. No foreign card or forex conversion is required.
You're billed in KES. Prices can be viewed in USD, KES, TZS, or NGN, but as a Kenya customer you pay in KES with no forex conversion.
Put a load balancer in front of it — soon
Load Balancers are launching soon. Talk to us to reserve early access and pricing in your local currency, with no card to start.
Launching soon · 99.99% uptime SLA · Local billing in KES, TZS & NGN