Three regions, each inside the country it serves

The word region gets used loosely in this part of the world, so it is worth being exact. ke-1a is in Nairobi. tz-1a is in Dar es Salaam. ng-1a is in Lagos. Compute, storage and the region's network endpoint are all in the named city, and an instance stays there unless you move it. That is a different thing from an edge presence with the compute in another country, and a different thing again from a rack in Johannesburg with a local brand on the website. Ask which building, and ask which country the building stands in. Both have an answer here, and both are fair questions to put to anyone else you are comparing.

The regions sit inside carrier-neutral, Tier III data centres operated by specialist facility companies, and Lineserve runs its own hardware and its own network inside them. That split is the normal shape of the industry and it answers the two questions procurement actually asks: who holds physical access to the machine, and which jurisdiction the building sits in. Power, cooling and physical security are the facility operator's discipline. The servers, the network and your data are ours.

Each city was chosen for the same reason: it is where the country's networks meet each other. Kenya's international capacity lands at Mombasa and is carried roughly 480 km inland, but Kenyan networks exchange domestic traffic in Nairobi at KIXP — 136 peer networks and 2.9 Tbps of connected capacity on PeeringDB — where ke-1a peers. Dar es Salaam has no inland haul at all: SEACOM, EASSy and SEAS land in the city, it is a named landing point on 2Africa, and Tanzanian networks exchange at TIX. Lagos is the densest landing point in West Africa with eight subsea systems terminating in the country, and IXPN runs 13 points of presence across seven states with more than 130 connected networks. A request from a user in one of these cities reaches a machine in the same city, on a round trip typically in single-digit milliseconds, rather than crossing an ocean twice.

What runs on top of that is deliberately unlayered. Cloud servers priced by the resource, Linux and Windows VPS plans, LineServe Core dedicated hardware, S3-compatible object storage, managed Kubernetes, and colocation quoted per footprint — with NVMe storage, a dedicated IPv4 and a free /64 of IPv6, always-on DDoS mitigation, snapshots and scheduled backups, private networking, a browser console, and a full API and CLI. The 99.9% uptime SLA carries service credits. There are no feature tiers to negotiate past and nothing on that list is gated behind a sales conversation.

Buying from outside all three countries, you contract with LINESERVE, INC., a company registered in Dover, Delaware, and you are quoted, invoiced and settled in US dollars by card or bank transfer. For most international buyers that is the point: a familiar legal system for the contract, a familiar currency for the ledger, and infrastructure in three countries where the alternative is three separate suppliers under three separate systems of law.

In Kenya it works differently, and better. Lineserve Limited is a Kenyan company, registered for VAT in Kenya, with an office in the Nairobi CBD. A Kenyan buyer purchasing through the Kenya market therefore contracts with a Kenyan supplier and receives a Kenyan tax invoice in shillings with the 16% shown separately — which matters, because a Kenyan business needs a valid tax invoice carrying its own KRA PIN to claim the expense and the input VAT. If your group has a Kenyan subsidiary, that is usually where you want the Kenyan spend to sit.

Tanzania and Nigeria are billed in their own currencies through their own markets, in TZS and NGN, with local payment rails and each country's tax treatment. So the shape of the relationship is yours to choose: one account and one dollar invoice covering all three regions, or an account per entity so each subsidiary carries its own cost in its own currency. Both are normal. The second is much easier to arrange before the first invoice than after it.