Cloud Servers — Nairobi (ke-1a), Dar es Salaam (tz-1a) & Lagos (ng-1a)
Cloud servers inside Kenya, Tanzania and Nigeria
Three countries no hyperscaler runs a region in. Pick one at deploy time.
Amazon's African region is Cape Town. Microsoft's is in South Africa. Neither Kenya, Tanzania nor Nigeria has a region from any of them, which means a company serving Nairobi, Dar es Salaam or Lagos from a global cloud is serving those cities from another continent — and holding their customers' personal data there. Lineserve puts the compute in the country. You build the machine resource by resource — vCPU at $4.33, RAM at $3.06 a GB, SSD at $0.25 a GB, IPv4 at $1.50, IPv6 free — from $13.89 a month, in whichever of the three regions the workload belongs in. Billed in US dollars, by card or bank transfer, from wherever you are.
1 vCPU · 1 GB RAM · 20 GB SSD · IPv4 included — build exactly the server you need.
- Three regions — ke-1a Nairobi, tz-1a Dar es Salaam, ng-1a Lagos
- No hyperscale cloud region exists in any of the three countries
- Priced per vCPU, per GB of RAM and per GB of SSD, from $13.89/month
- Data held in the country you deploy into, under that country's law
- Quoted and settled in USD by card or bank transfer — or pay locally
No credit card required · Local billing in KES, TZS & NGN
Pricing calculator
Build exactly the server you need
No fixed plans — pay per vCPU, per GB of RAM and per GB of SSD. Linux images are free; Windows Server adds a license fee. In your currency, no forex.
Operating system
Minimum 20 GB for Linux images.
Your server
Hosted in Nairobi, Dar es Salaam & Lagos
- Compute2 vCPU · 4 GB RAM
- Storage40 GB Universal SSD
- Public IPv41 address
- ImageLinux (free)
Unit rates
| Resource | Unit | Price /mo |
|---|---|---|
| vCPU | per vCPU | $4.33 |
| RAM | per GB | $3.06 |
| Storage — Universal SSD | per GB | $0.25 |
| Public IPv4 | per address | $1.50 |
| Windows Server 2019 Standard | per server | From $8 |
| Windows Server 2022 Standard | per server | From $10 |
| Windows Server 2025 Standard | per server | From $12 |
| Bandwidth | 1 Gbps port, unlimited local traffic | Free |
| IPv6 (/64) | per server | Free |
| Linux images | Ubuntu, Debian, Rocky, AlmaLinux | Free |
Prices exclude VAT and any applicable taxes. Annual billing gives you two months free. Local currency figures are indicative and settled at checkout.
Network
Three countries that are not on anybody's region list
Open the region map of any global cloud and look at East and West Africa. Amazon's African region is Cape Town. Microsoft's is in South Africa. Kenya, Tanzania and Nigeria — roughly 300 million people between them, three of the continent's most active technology markets — have none. Whatever you deploy for those users executes somewhere else, and whatever it writes is written somewhere else too.
The part that is easiest to misread is edge. Nairobi and Lagos carry a real presence from the large clouds: content-delivery points of presence, local zones, interconnect. Dar es Salaam carries none of it — the nearest content-delivery nodes to Tanzania sit in Nairobi, Mombasa, Lagos, Johannesburg and Cape Town. But edge and region are different products doing different jobs. Edge terminates a connection and serves a cached copy of something static. It does not run your application server, it does not hold your database primary, it does not accept a write, and it does not put a customer's personal data inside the country when a regulator asks where that data is. A cached product image in Lagos and a Postgres primary in Cape Town are two separate facts, and only one of them is on the procurement form.
The second thing buyers misread is distance. Cape Town looks close to Nairobi on a map and behaves nothing like it on a network: paths between African networks have long been carried north to Europe and handed back rather than exchanged on the continent, which is the routing problem the local exchange points were founded to fix. Published measurement research puts intercontinental round trips from African networks at roughly 100 to 400 ms, averaging near 200. A request from Lagos to Nairobi has commonly taken longer than the same request from Lagos to London. Geographic proximity is a poor predictor of network proximity here, and a South African region is an international deployment from all three countries.
What each city does have is its own connectivity, and it is better than the region map suggests. Kenya's subsea capacity lands at Mombasa and runs roughly 480 km inland to Nairobi, where KIXP has exchanged domestic traffic since 2002 across 136 peer networks and 2.9 Tbps of capacity, with Amazon, Microsoft, Netflix and Meta among the networks present; ke-1a peers there. Dar es Salaam skips the inland haul entirely, because SEACOM, EASSy and SEAS come ashore in the city itself, and 13,820 km of state backbone fibre carries the rest of Tanzania. Lagos is the densest landing point in West Africa with eight subsea systems ashore, and IXPN now runs 13 points of presence across seven states with more than 130 connected networks and peak domestic traffic past 2 Tbps by March 2026.
All of which reduces to one sentence a procurement form can hold. A request from a user in Nairobi, Dar es Salaam or Lagos reaches a machine in the same city, on an in-metro round trip typically in single-digit milliseconds, rather than crossing an ocean and coming back — for the page, and then for every image, script, API call and database query behind it.
0
Hyperscale cloud regions in Kenya, Tanzania or Nigeria
3
Live Lineserve regions — ke-1a, tz-1a and ng-1a
2.9 Tbps
Capacity connected at KIXP, Nairobi (PeeringDB)
130+
Networks connected at IXPN, Lagos, across 13 points of presence
The test that settles it in one question
Ask your current provider which country the machine running your application is physically in. Not the console, not the cache, not the account's billing address — the hypervisor. If the answer is Cape Town, Frankfurt or northern Virginia for users who are in Nairobi, Dar es Salaam or Lagos, then everything on this page applies to you, and the fix is a region code rather than a rewrite.
What the buildings are
The three regions sit inside carrier-neutral, Tier III data centres run by specialist facility operators, and Lineserve runs its own hardware and network inside them. That distinction matters to an international buyer, because a security questionnaire asks two separate questions — which country the building stands in, and who has physical access to the machine. Both have a straight answer.
Payments
Buy in dollars from anywhere, or let the local entity buy locally
From outside the three countries you are quoted, invoiced and settled in US dollars, by card or bank transfer, whichever region you deploy into. The dollar figures are a price list rather than a conversion applied at the moment you click: a vCPU is $4.33, a gigabyte of RAM is $3.06, a gigabyte of SSD is $0.25, an IPv4 address is $1.50, and the smallest real Linux server is the sum of those at $13.89 a month. What changes underneath is who pays, and from which country.
Card
Visa and Mastercard, charged in USD. Cards suit development and staging instances, month-to-month capacity, and the teams that would rather keep a card on file than raise a transfer instruction every thirty days for a bill in the tens of dollars.
Bank transfer
The rail procurement is already configured for, and the practical one once a deployment is real: a fleet of L1-sized instances at $83.30 each, a year taken up front at ten months for twelve, or compute alongside dedicated hardware on the same invoice. One reference, one reconciliation line.
Or bill the local subsidiary, in local currency
If your Kenyan, Tanzanian or Nigerian entity is the one that should carry the cost, switch it to that market and it settles in KES, TZS or NGN. Kenya and Tanzania add M-Pesa alongside bank transfer and card; Nigeria settles in Naira by bank transfer or card. Each price list is maintained per currency rather than converted from dollars, so the figure a local finance team approves in March is the figure that clears in November.
A metered bill needs a decision up front
Per-resource pricing means the invoice follows the infrastructure: add four vCPU for a launch and the next bill shows it, give them back and it shows that too. Most international teams put annual billing on the steady tier — ten months for twelve — and leave the elastic part monthly.
Displayed prices exclude tax; where VAT applies it is calculated and shown separately at checkout. Annual billing is ten months for twelve on eligible plans.
The platform
A full cloud, not just a server
Every Cloud Server sits on a platform built to grow with you — automate it, resize it, connect it, and protect it, all from one place.
Deploy in 60 seconds
Provision a production-ready instance in under a minute, from console or API.
Resize on demand
Scale vCPU, RAM, and storage up as you grow, with minimal downtime.
NVMe SSD storage
Enterprise NVMe throughout for fast boot, quick builds, and low-latency databases.
Snapshots & backups
Capture point-in-time snapshots and schedule automated backups in a click.
Private networking
Isolated internal networks to connect your instances securely, region by region.
Free DDoS protection
Always-on network-layer mitigation included on every instance at no extra cost.
Full API & CLI
Manage everything as code — create, resize, snapshot, and destroy through a clean API.
IPv4 & IPv6
A dedicated IPv4 address plus native IPv6 on every instance.
Console access
Reach your server directly through a browser console when SSH or RDP isn't enough.
Regions
Nairobi, Dar es Salaam or Lagos — and what decides it
The rule is unglamorous and it holds nearly everywhere: put the workload in the country whose users and whose records it serves. Per-unit prices are identical in all three regions, so the decision is geography and law rather than cost — and there is no useful midpoint, because traffic between the three cities is still commonly carried through Europe.
ke-1a is for Kenyan users and Kenyan records, and for regional teams whose head office is already in Nairobi. Every Kenyan subsea cable — TEAMS, SEACOM, EASSy, LION2, DARE1 and PEACE — comes ashore at Mombasa, and that capacity is carried roughly 480 km inland to the city where the carriers and the customers are. Domestic traffic never makes that trip: it is exchanged inside Nairobi at KIXP, the neutral exchange TESPOK has run since 2002, with 136 peer networks and 2.9 Tbps of connected capacity. Lineserve peers there.
tz-1a is for Tanzanian users, and it is where moving an origin changes the most: Tanzania has no content-delivery edge of its own, so a Dar es Salaam viewer is served from another country however the CDN is configured. There is no inland haul either — SEACOM, EASSy and SEAS come ashore in the city itself, and Dar es Salaam is a named landing point on 2Africa. Tanzanian networks meet at TIX, run since 2003 by the country's service-provider association, and 13,820 km of state fibre carries one origin on to Mwanza, Arusha and Dodoma.
ng-1a is for scale and for regulated Nigerian workloads. Eight subsea systems land in and around Lagos, among them MainOne, SAT-3, WACS, Equiano and 2Africa, which comes ashore at Lekki. Nigerian networks exchange domestic traffic at IXPN, founded in 2006 to stop domestic packets being hauled to London and now running 13 points of presence across seven states. Lagos also has a date attached: a Central Bank circular directs payment transaction data generated in Nigeria to be stored there from 1 January 2027.
All three give a buyer based elsewhere the same pair of things: a request from a user in the city reaches a machine in that city, typically in single-digit milliseconds, and the records it touches sit under one named country's law.
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 apps & APIs
Host Node, Python, Go, PHP, or .NET behind a load balancer with room to scale.
Databases
Run PostgreSQL, MySQL, SQL Server, or Redis on fast NVMe with the memory they need.
Containers & CI
A clean host for Docker, Compose, and build runners, close to your team and users.
Business systems
ERPs, internal tools, and line-of-business apps on Linux or Windows, run reliably.
How it works
Live in three steps
Choose region, OS & size
Pick a region, Linux or Windows, and the instance that fits your workload.
Deploy in under 60 seconds
We provision your server and run your setup — no manual first-run steps.
Connect & scale
Log in over SSH or RDP, then resize or snapshot anytime from the console or API.
Uptime SLA
99.9%
- Service credits applied automatically when we miss the SLA
- Measured monthly, per region, on network and power availability
- Tier III colocation facilities across all live regions
Support
You are on a different continent from your infrastructure
That is the real reservation, and it is answerable with what exists. Architecture, quotes, contracts, a data processing agreement, the registered names and tax identifiers that have to appear on your invoices: [email protected], in writing, in a thread you can forward to your own legal and finance people. Running services are driven from the console, the API and the ticket system on your account. Two phone lines are published for the region — +254 119 039 063 in Kenya and +255 761 847 121 in Tanzania.
Scheduling across the distance is the practical problem, and the arithmetic is friendlier than it looks. Nairobi and Dar es Salaam run on East Africa Time, UTC+3; Lagos on West Africa Time, UTC+1. Neither observes daylight saving, so the gap between your clock and theirs moves only when your own clocks change, and a window agreed in June still means what you thought it meant in December. From London, Nairobi is three hours ahead in winter and two in summer, and Lagos an hour ahead in winter and level in summer. From New York in July, a 09:00 call is 14:00 in Lagos.
Most of what would be a phone call elsewhere is a call you make yourself. Building, resizing, rebooting, snapshotting and rebuilding an instance are API and console operations that behave identically at three in the morning your time or theirs, and a browser console reaches a machine that has lost its own networking. What needs a person in the building is a physical fault — and that person is there already.
Why Lineserve
Decided on what actually matters here
Tax & invoicing
One supplier, three tax authorities, and the paperwork that follows
The rate that reaches your invoice follows where you buy from and which market bills you, not which region the instance runs in. Buy from Amsterdam or Austin and you are billed in dollars against your own entity while the workload runs in Lagos. Buy through a local subsidiary and that country's treatment applies: Kenya charges 16% VAT on digital and hosting services through the Kenya Revenue Authority, whose published list of taxable digital services names cloud backup and email hosting explicitly; Tanzania's mainland rate is 18% through the Tanzania Revenue Authority, with Zanzibar administered separately; Nigeria charges 7.5% through the Nigeria Revenue Service, the body most Nigerian buyers still call FIRS. On identical infrastructure the Tanzanian tax line is more than twice the Nigerian one, which is worth knowing before you model a three-country deployment.
The mechanics differ as much as the rates. Tanzania requires an Electronic Fiscal Device verification code on a mainland receipt before a VAT-registered buyer can claim input tax. Nigeria replaced its framework wholesale on 1 January 2026, when the Nigeria Tax Act 2025 and the Nigeria Tax Administration Act 2025 took effect, and large taxpayers are already inside a mandatory e-invoicing regime. Kenya's claimable invoice carries the seller's and the buyer's tax identifiers, the taxable value and the VAT as its own line. Send [email protected] the identifiers for every entity that will appear on an invoice — a KRA PIN, a TRA TIN, a Nigerian TIN — and the account is configured once rather than corrected in month three.
Withholding is the question a CFO raises on the first call, and it is cash flow rather than a footnote. A Tanzanian business paying a non-resident for services withholds 15% of the gross consideration unless a double tax agreement reduces it, irrespective of where the service is performed, and a Nigerian payer is frequently a withholding agent filing a monthly schedule naming each supplier. Your adviser places your purchase against those; bring us into the conversation early and the invoicing is set up to match how you remit.
One account, or one per country
The default is one account, one console and one USD invoice covering all three regions — which is what most international buyers want, because it is one supplier relationship and one renewal date. The alternative is each subsidiary holding its own account in its own currency so the cost lands in the right ledger and the right tax return. Both work. The second is a conversation to have before you order rather than a migration afterwards.
What a resize does to the paperwork
Cloud servers are metered by resource, so an instance that grew during a campaign produces a different invoice from the one before it — which surprises a finance team that has only ever bought fixed plans. Annual billing on the baseline and a named cost centre per region fix it, and both are set at account creation in a few minutes.
Prices exclude VAT. Nigeria's tax framework changed on 1 January 2026, so guidance written before that date is worth re-reading before you rely on it.
Data residency
Choosing a region is a legal decision before it is a technical one
Three countries, three statutes, three regulators. Kenya's Data Protection Act, No. 24 of 2019 is enforced by the Office of the Data Protection Commissioner. Tanzania's Personal Data Protection Act, 2022 has been in force since 1 May 2023, with the Personal Data Protection Commission operational since April 2024. Nigeria's Data Protection Act 2023 sits with the Nigeria Data Protection Commission, and its General Application and Implementation Directive took effect on 19 September 2025. All three attach conditions to moving personal data out of the country, and the conditions are not the same shape, which is why a single global architecture rarely survives contact with all three.
Tanzania is the strictest. Personal data leaves the country on a permit from the Commission, applied for with the recipient, the categories of data, the purpose and duration, the destination country and the security arrangements at the far end set out in the application. The Commission may approve, ask for more, or refuse, and it monitors the permit afterwards. That is prior authorisation: it finishes when a regulator says so, not when your sprint does. Administrative penalties run to TZS 100,000,000.
Nigeria is the most dated. Section 41 of the NDPA permits transfer where the recipient is covered by an adequate law, binding corporate rules, contractual clauses, a code of conduct or a certification mechanism. Sitting on top of that, a Central Bank of Nigeria circular of 15 June 2026 directs that payment transaction data generated within Nigeria be stored and managed in Nigeria, with full compliance from 1 January 2027 — in scope are banks, microfinance banks, mobile money operators, fintechs, switching companies, payment service providers and super agents, and the affected data is reported to reach merchant records, transaction identifiers, timestamps, settlement information and processing logs. If you are entering Nigerian payments from abroad, that is a date in your delivery plan.
Kenya is the most permissive and still has a limb worth reading. Sections 48 and 49 allow transfer on proof of appropriate safeguards, and Regulation 26 goes further for six named purposes — civil registration and identity, elections, public finance systems, protected computer systems, basic education, and primary or secondary health care — requiring at least one serving copy inside Kenya. Programmes in health and education meet that limb more often than their architects expect.
Deploy into ke-1a, tz-1a or ng-1a and the data you put there is held in Nairobi, Dar es Salaam or Lagos, under that country's law, and it does not leave without your instruction. That is data residency for Kenya's Data Protection Act, Tanzania's Personal Data Protection Act and Nigeria's Data Protection Act — the part a hosting provider supplies. The assessment, the registrations and the sign-off stay with your own compliance function, where they belong.
Hosting abroad moves the machine, not the obligation
Kenya's Act reaches a controller who is not established or ordinarily resident in Kenya but processes the personal data of people located in Kenya. A company in Berlin or Boston with Kenyan users sits inside that Act whether its servers stand in Frankfurt or Nairobi. The same logic runs through the other two statutes. In-country hosting does not create an obligation you did not have — it removes the cross-border transfer analysis from the data that stays.
A second region is a decision, not a default
Nairobi, Dar es Salaam and Lagos share one account and one API, so standby and replication are configuration rather than a project. Make the call deliberately for personal data: a copy of Tanzanian personal data in Lagos is a transfer out of Tanzania under the permit regime, and Nigerian payment data that follows a replica out of the country takes its localisation position with it. Application images, container registries and telemetry without personal data raise none of these questions.
Who deploys here
What international teams run in ke-1a, tz-1a and ng-1a
SaaS with customers in the country
You run in Frankfurt or Virginia, you have signed enough customers in Nairobi or Lagos that they mention the loading time on calls, and one of them has now sent a security questionnaire asking where their data is held. The usual answer is a regional tier rather than a migration: application servers and a read replica in-country, the control plane left where it is, DNS steering each user to the nearer origin. A 2 vCPU / 4 GB instance is $42.40 a month; the read replica is another one.
Fintech and payments entering the market
API endpoints and webhook receivers taking callbacks that originate inside the country, ledger and reconciliation databases, KYC document stores, fraud scoring, and transaction logs that only ever grow. Nigeria carries the hardest deadline — payment transaction data generated in the country is directed to be stored and managed there from 1 January 2027 — and the callbacks arriving from a local switch have a much shorter path to an endpoint in Lagos than to one in Ireland.
Donor programmes and international NGOs
DHIS2 and other health information platforms, KoboToolbox and ODK form servers taking submissions from field teams on mobile data, monitoring-and-evaluation dashboards, file sync for staff days away from a capital. Two questions arrive from different directions and one deployment answers both: the donor audit asks which country the beneficiary data sits in, and the country office asks why the survey server times out on a 3G connection.
Agencies and systems integrators with clients in-region
Your client's tender says the data is held in-country and your standard architecture says Frankfurt. Multi-tenant client hosting, staging environments, Git-based deploys, and an in-country IP so client sites resolve locally. One account covers all three countries, which means one supplier to onboard through your client's procurement rather than three.
Media, streaming and anything with heavy origin traffic
Distance costs most where the bytes are biggest. Tanzania has no content-delivery edge at all, so a Dar es Salaam viewer is served from another country however the CDN is configured, and an origin in the wrong hemisphere pays for it on every cache miss. The shape that works is an origin in-country with a cache in front — object storage at $0.061 per GB a month with transfer and API requests free, and the transcode tier on cloud servers next to it.
Enterprises with a country office and no local IT
A regional sales office in Nairobi, a project team in Dar es Salaam, a distribution operation in Lagos, and a head office with no intention of running a server room in any of them. File services, a domain controller, line-of-business applications, and a landing zone for systems that should not traverse a VPN to Europe. Windows Server 2019, 2022 and 2025 Standard are licensed per vCPU on a minimum of four cores, from $31.95 a month.
Cloud servers from $13.89/month; a Linux VPS from $21.95; a Windows VPS from $31.95 with the licence included; managed Kubernetes from $27.86 a month for the cluster plus the worker resources it consumes; dedicated LineServe Core hardware from $309 plus a one-time $99 setup.
Getting here
Move the workload, or just add the country
From your cloud's nearest region
Today your Kenyan, Tanzanian or Nigerian users are served from Cape Town, Frankfurt or northern Virginia, and every request pays that distance twice. The move itself is an ordinary afternoon of work, because nothing about the stack changes: same Linux, same containers, same Postgres dump. Build the instance, rsync the files, restore the database, run both in parallel for a day, cut the DNS over. What changes afterwards is bigger than the server. Your users stop crossing an ocean. Your data stops being a cross-border transfer somebody has to document, defend and refresh. And when the next enterprise prospect's procurement form asks which country their data will be held in, the answer is a city.
Alongside the provider you already have
This is the more common shape and there is nothing second-best about it. Keep AWS in Frankfurt or Google Cloud in London for everything already working there, and put a Lineserve region under the part that has to be in-country: the user-facing tier, the read replica, the payment records, the object store the customer's regulator asks about. An IPsec or WireGuard tunnel between the two, replication across it, DNS routing each user to the right origin. Nothing has to be migrated, and you end up with a region in a country where your current provider does not have one. The second and third countries are the same configuration with a different region code.
Migration planning and assistance are included at no extra charge, whether you are coming from a hyperscaler region on another continent, a rack you have outgrown, or a local provider in one of the three countries. Tell [email protected] what you run and where, and the reply is an architecture rather than a quote.
FAQ
Questions, answered
None — they're the same product. "Cloud Server" is our name for the virtual machine; the Linux VPS and Windows VPS pages are just that server viewed by operating system. Pick whichever entry point suits you.
Yes. Choose your operating system at deploy time. Linux images (Ubuntu, Debian, Rocky, AlmaLinux) are free; Windows Server adds a license fee from $8/month that scales with the size of your server — the calculator shows the exact figure for your configuration.
Your server is the sum of its parts: $4.33 per vCPU, $3.06 per GB of RAM, $0.25 per GB of SSD storage, and $1.50 per public IPv4, each per month. IPv6 is free. There are no fixed plans — change any dial independently.
Yes. Scale vCPU, RAM, and storage up as you grow, with minimal downtime — every resource moves independently, so you never pay for a bundle you don't need.
Under 60 seconds. Your instance provisions and runs any setup you provide, so it's ready to use — not just powered on.
Yes. Every action — create, resize, snapshot, destroy — is available through a clean API and command-line tool, so you can manage infrastructure as code.
Every instance supports on-demand snapshots and scheduled automated backups. Snapshot storage is billed per GB beyond your included allowance.
Yes. Our team assists with moving existing workloads into Lineserve at no extra charge. Reach out to support to plan the move.
No. Amazon's African region is Cape Town and Microsoft's is in South Africa. Nairobi and Lagos carry edge infrastructure — content delivery, local zones, interconnect — but the compute regions are in another country, and Tanzania has neither a region nor a content-delivery presence.
No. Edge terminates connections and serves cached copies of static content. It does not run your application server, hold your database primary, accept a write, or place personal data inside the country for a regulator. A cached image in Lagos and a database in Cape Town are separate facts, and only the second one answers a residency question.
Yes, and it is the default. You are quoted, invoiced and settled in USD by card or bank transfer, whichever region you deploy into. Switching to the Kenya, Tanzania or Nigeria market changes the currency to KES, TZS or NGN and adds that country's local payment methods.
No. The account is yours wherever you are, and the region is a choice at deploy time. Whether you have a local entity affects how you want to be billed and taxed, not whether you can run in ke-1a, tz-1a or ng-1a.
LINESERVE, INC., registered in Dover, Delaware. What is in Kenya, Tanzania and Nigeria is the infrastructure: three regions, data held in-country, and local-currency billing available in each of the three markets.
By where your users and your data are — Kenyan in ke-1a, Tanzanian in tz-1a, Nigerian in ng-1a. There is no useful midpoint between them, and per-unit prices are identical in all three, so serving two countries properly means running in two regions rather than picking a compromise.
Yes. Data placed in a region is held in that region's city and is not moved out of the country without your instruction. That gives you data residency for Kenya's Data Protection Act, Tanzania's Personal Data Protection Act or Nigeria's Data Protection Act, depending on the region.
No. Kenya's Act reaches a controller not established or ordinarily resident in Kenya who processes the personal data of people located in Kenya, and the other two statutes work along similar lines. Hosting in Frankfurt moves the servers, not the obligation. In-country hosting removes the cross-border transfer analysis for the data that stays.
A Central Bank of Nigeria circular of 15 June 2026 directs that payment transaction data generated within Nigeria be stored and managed in Nigeria, with full compliance from 1 January 2027. It covers CBN-licensed participants — banks, mobile money operators, fintechs, switching companies, payment service providers and super agents. ng-1a is in Lagos. Where your own licence and data sit inside that scope is a question for your Nigerian counsel.
Yes — one account and one API reach all three. Do it deliberately for personal data: replicating Tanzanian personal data to Lagos is a transfer out of Tanzania, which requires a permit from the Personal Data Protection Commission. Replicating application images, container registries and telemetry raises no such question.
By resource, not by plan: $4.33 per vCPU, $3.06 per GB of RAM, $0.25 per GB of Network Universal SSD and $1.50 per IPv4 address, with a /64 of IPv6 included free. The smallest real Linux server — 1 vCPU, 1 GB, 20 GB, one address — is $13.89 a month. Prices exclude VAT.
vCPU, RAM and storage each move independently with minimal downtime, so a launch week and the month after it can be different machines without a rebuild. Windows Server 2019, 2022 and 2025 Standard are available, licensed per vCPU on a minimum of four cores; Linux images are free.
That path is intercontinental and always will be — your engineers reach the console over the same internet as everybody else, and the console is not the workload. The region exists for your users in Nairobi, Dar es Salaam and Lagos, whose in-metro round trips are typically single-digit milliseconds instead of a subsea crossing each way.
Displayed prices exclude tax, and where VAT applies it is calculated and shown separately at checkout. The domestic rates differ — Kenya 16%, Tanzania 18% on the mainland, Nigeria 7.5% — and which one reaches your invoice follows which market bills you, not which region your instance runs in.
Customer references are available under NDA. Tell [email protected] what you are building and which country it is for, and you will be pointed at the closest match.
Tell [email protected] which one and what you would run there. Uganda, South Africa and Ghana are the regions in planning, and colocation in the three live cities is quoted per footprint if what you need is your own hardware in a specific building.
Deploy your first Cloud Server in under 60 seconds
Linux or Windows, running close to your users. Pay in local currency, with no card required to start.
No credit card required · 99.9% uptime SLA · Local billing in KES, TZS & NGN