LINESERVE

Managed Kubernetes — hosted in Dar es Salaam

Coming soon

Managed 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.

Clusters fromTZS 55,720/month + resources
  • Fully managed control plane
  • Clusters live in minutes
  • Three locally-hosted regions — Nairobi, Dar es Salaam & Lagos
  • Data residency for Tanzania's Personal 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.

TZS 55,720/mo + resources

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
Recommended

Fault Tolerant

3 master nodes with automatic failover — recommended for production.

TZS 232,680/mo + resources

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.

ResourceUnitPrice /mo
vCPUper vCPUTZS 13,320
RAMper GBTZS 6,120
Local diskper GBTZS 380
Network HDDper GBTZS 300
Universal SSDper GBTZS 460
Fast SSDper GBTZS 680
Public IPper IPTZS 3,000
Load balancer — Basicper LBTZS 32,760
Load balancer — Basic, redundantper LBTZS 65,540
Load balancer — Advanced, redundantper LBTZS 131,060

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

tz-1a is home. Nairobi and Lagos are on the same account.

Deploy in Dar es Salaam and your data stays in Tanzania, in the same city as most of the people using it. ke-1a in Nairobi and ng-1a in Lagos are one API call away on the same console and the same shilling bill, so a standby or an offsite copy is a line in a config file rather than a supplier to onboard. Typical in-metro round trips are around 6 ms in Dar es Salaam, ~2 ms in Nairobi and ~4 ms in Lagos.

Traffic between Tanzanian networks is exchanged in Dar es Salaam. The Tanzania Internet eXchange has run there since 2003 as a project of TISPA, the Tanzanian ISP association; PeeringDB records 32 networks and 798G of connected capacity there, with Akamai, Meta, Cloudflare and TTCL among them, and no fee to join. The point of a local exchange is a plain one: a packet from one Tanzanian network to another changes hands in the city, instead of being hauled to Europe and back to travel four kilometres.

International capacity comes ashore in the same city: SEACOM, EASSy and SEAS land at Dar es Salaam, a named landing point on 2Africa as well. Inland, the National ICT Broadband Backbone carries it onward — government fibre managed by TTCL, 13,820 km laid of a 16,280 km target as of FY2024/25, reaching every region and crossing into Zambia, Malawi, Kenya, Uganda, Rwanda and Burundi. One origin in Dar es Salaam therefore has a real answer for a user in Mwanza, a site office outside Geita and a clearing agent at Tunduma.

TCRA's count for the quarter ending March 2026 tells you who is at the other end: Vodacom 36.19 million subscriptions, Yas 31.85 million, Airtel Tanzania 23.75 million, Halotel 18.32 million, against 58.9 million internet subscriptions nationally, roughly 99% of them mobile wireless. The largest reaches under a third of the country: no carrier arrangement covers a Tanzanian audience, and being inside Tanzania covers all of them at once.

Live

Tanzania

Dar es Salaam

~6 ms

typical, within metro · Data stays in Tanzania

Live

Kenya

Nairobi

~2 ms

typical, within metro · Data stays in Kenya

Live

Nigeria

Lagos

~4 ms

typical, within metro · Data stays in Nigeria

Expansion zonesUganda · ug-1aSouth Africa · za-1aGhana · gh-1a

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

1

Pick region, version & cluster type

Choose your region, a Kubernetes version, and Basic or Fault Tolerant control plane.

2

Add worker pools

Size pools in vCPU, RAM, and storage, and set autoscaler bounds per pool.

3

Deploy with your tools

Download the kubeconfig, then kubectl apply or helm install like any cluster.

4

Let it run

The autoscaler tracks demand and auto-healing replaces bad nodes — day and night.

Uptime SLA

99.9%

  • When hardware fails
  • When the region is the risk
  • Service credits applied automatically when we miss the SLA

Support

A Tanzanian line, and a clock that already matches yours

Call +255 761 847 121. Tanzania is on East Africa Time all year with no daylight saving, so there is no drift to track and no arithmetic before you dial — business hours mean the same thing in March as in November. A ticket opened at the start of a Dar es Salaam morning lands inside a working day, rather than at the bottom of a queue that wakes up as yours is ending.

That match is worth the most at the moment you can least afford it. Month-end, last Friday, 16:40: the reconciliation job has stalled, the settlement file has not written, and the deadline is Monday. What you want then is an engineer who is awake and at work with your instance ID in front of them — a resize that needs a reboot window, a snapshot restored into a new instance, a routing question, a port that has stopped answering. Not a form, and not a five-hour wait for somebody's morning.

[email protected] takes the commercial half, and it is worth using before you order: your TIN and registered name as the TRA holds them, a purchase-order or grant code the invoice must carry, an annual invoice that fits the budget year. Migration planning and assistance come at no extra charge, from a rack in Frankfurt or from across town. Customer references are available under NDA.

Tanzania

+255 761 847 121

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.

CapabilityLineserveSelf-managed / global cloud
Control plane run and upgraded for you
Billing in KES, TZS & NGN
Single-digit local latency
Data stays on the continent
Autoscaling worker poolsSometimes
Support in your timezone
No card or forex required

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 Tanzania and stays in-country, giving you data residency for Tanzania's Personal Data Protection Act. It isn't moved out of Tanzania without your instruction.

In our Dar es Salaam data centre (tz-1a). Your content is stored and served from Dar es Salaam, 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 TZS. Prices can be viewed in USD, KES, TZS, or NGN, but as a Tanzania customer you pay in TZS 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