Managed Kubernetes — hosted in Nairobi
Coming soonManaged Kubernetes
Production Kubernetes without the control plane toil.
We run the API server, scheduler, and etcd — and handle upgrades, backups, and failover. You get a kubeconfig, autoscaling worker pools, and clusters that are live in minutes.
- Fully managed control plane
- Clusters live in minutes
- Three locally-hosted regions — Nairobi, Dar es Salaam & Lagos
- Data residency for Kenya's Data Protection Act — your data stays in-country
- 99.95% SLA on Fault Tolerant
Launching soon · Local billing in KES, TZS & NGN
Pricing
A cluster fee, plus what your nodes use
Pick a control plane — Basic or Fault Tolerant — then pay only for the vCPU, RAM, storage, and load balancers your worker nodes actually consume. In your currency, no forex.
Basic
Single master node for development, testing, and non-critical workloads.
Hosted in Nairobi, Dar es Salaam & Lagos
- 1 master node
- 99.5% control-plane SLA
- Kubernetes 1.28–1.31
- Autoscaling worker pools
- Prometheus & Grafana included
Fault Tolerant
3 master nodes with automatic failover — recommended for production.
Hosted in Nairobi, Dar es Salaam & Lagos
- 3 master nodes, automatic failover
- 99.95% control-plane SLA
- Kubernetes 1.28–1.31
- Autoscaling worker pools
- Prometheus & Grafana included
Worker node resources
Billed monthly, per unit consumed, on top of the cluster fee.
| Resource | Unit | Price /mo |
|---|---|---|
| vCPU | per vCPU | KES 666 |
| RAM | per GB | KES 306 |
| Local disk | per GB | KES 19 |
| Network HDD | per GB | KES 15 |
| Universal SSD | per GB | KES 23 |
| Fast SSD | per GB | KES 34 |
| Public IP | per IP | KES 150 |
| Load balancer — Basic | per LB | KES 1,638 |
| Load balancer — Basic, redundant | per LB | KES 3,277 |
| Load balancer — Advanced, redundant | per LB | KES 6,553 |
Your monthly total is the cluster fee plus the resources your worker nodes consume. Snapshots, file storage, and traffic beyond the included allowance bill at the same per-GB console rates. Prices exclude VAT; local currency figures are indicative and settled at checkout.
The platform
Everything a production cluster needs
Networking, storage, monitoring, and access control come wired in — so day two looks like day one.
Managed control plane
API server, scheduler, controller manager, and etcd — run, upgraded, and backed up by us.
Autoscaling worker pools
The cluster autoscaler adds and removes nodes with demand, down to zero when idle.
Auto-healing nodes
Unhealthy nodes are detected and replaced automatically, with no manual intervention.
Persistent volumes
A CSI driver provisions HDD, Universal SSD, or Fast SSD volumes straight from your PVCs.
Private clusters
Run control plane and workers with no public IPs, reached over VPN or a bastion host.
Load balancer integration
Services of type LoadBalancer provision cloud load balancers automatically.
Prometheus & Grafana
Built-in monitoring and dashboards on every cluster, with alerting included.
Helm & NGINX ingress
Deploy from any Helm repository, with a built-in NGINX ingress controller for traffic.
Multiple K8s versions
Choose Kubernetes 1.28–1.31 and upgrade through the console with zero downtime.
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
Microservices
Run service meshes with built-in discovery, load balancing, and rolling deploys.
CI/CD pipelines
Host Jenkins, GitLab runners, or Argo CD close to your team, scaling with each build.
Batch & ML workloads
Queue batch jobs and training runs on autoscaling pools that shrink when idle.
Dev environments
Give every team an isolated namespace — one cluster, clean boundaries, less sprawl.
How it works
From zero to cluster in four steps
Pick region, version & cluster type
Choose your region, a Kubernetes version, and Basic or Fault Tolerant control plane.
Add worker pools
Size pools in vCPU, RAM, and storage, and set autoscaler bounds per pool.
Deploy with your tools
Download the kubeconfig, then kubectl apply or helm install like any cluster.
Let it run
The autoscaler tracks demand and auto-healing replaces bad nodes — day and night.
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 here beats self-managed anywhere
Running your own control plane on VMs means patching, etcd backups, and 2 a.m. failovers. Running on a distant hyperscaler means forex bills and latency. This is the third option.
FAQ
Questions, answered
A service where we run the Kubernetes control plane for you — API server, scheduler, controller manager, and etcd — and handle upgrades, backups, and availability. You deploy and manage your applications; we keep the cluster healthy.
Basic clusters run a single master node and suit development, testing, and non-critical workloads, with a 99.5% control-plane SLA. Fault Tolerant clusters run 3 master nodes with automatic failover on a 99.95% SLA — recommended for production.
You pay the monthly cluster management fee (Basic or Fault Tolerant) plus the worker-node resources you actually consume — vCPU, RAM, storage, and load balancers. Scale worker pools up or down anytime; you only pay for what you use.
Versions 1.28 through 1.31, with new versions added shortly after upstream release. You upgrade your cluster through the console with zero downtime.
Yes. Enable the cluster autoscaler, set minimum and maximum node counts, and it adds or removes worker nodes automatically as your workload demands.
Yes. Create a cluster where the control plane and worker nodes have no public IP addresses, and reach it through a VPN or bastion host for maximum security.
Our CSI driver provisions volumes automatically when you create PersistentVolumeClaims. Choose HDD, Universal SSD, or Fast SSD storage classes to match your performance needs.
Yes. Every cluster ships with built-in Prometheus monitoring and Grafana dashboards. Container logs can flow to our logging service or your own backend.
Yes. Standard tools like kubectl, Helm, and Velero work directly, and our team assists with migration planning at no extra charge.
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.
Ship on Kubernetes, skip the control plane
Managed Kubernetes is launching soon. Talk to us to reserve early access and pricing in your local currency, with no card to start.
Launching soon · 99.95% control-plane SLA on Fault Tolerant · Local billing in KES, TZS & NGN