LINESERVE

Fedora VPS in Nairobi, Dar es Salaam or Lagos

Fedora VPS Hosting in Kenya, Tanzania and Nigeria

The box you build, use and throw away — next to the fleet it stands in for.

Fedora carries the kernels, compilers and container tooling that reach the enterprise distributions years later, on a roughly six-month cadence with about thirteen months of support per release. That makes it the wrong home for a machine you want to forget and the right one for almost everything short-lived: staging, runners, preview environments, the experiment that answers a question and then goes away. Deploy into ke-1a in Nairobi, tz-1a in Dar es Salaam or ng-1a in Lagos from $21.95 a month, or build to your own spec from $13.89.

Starting at$21.95/month
  • Deploy in under 60 seconds
  • 99.9% uptime SLA
  • Four locally-hosted regions — Nairobi, Dar es Salaam, Lagos & Kampala
  • Data sovereignty — your data stays in-country
  • Free DDoS protection

No credit card required · Local billing in KES, TZS, NGN & UGX

Pricing

Simple plans, billed in your currency

Pay in local currency — no cards, no forex surprises. Every plan is full root, full network, no throttling. Annual billing gets you two months free.

Linux VPS – 2 GB RAM

Small workloads and personal projects.

$21.95/mo

Hosted in Nairobi, Dar es Salaam, Lagos & Kampala

  • 1 vCPU
  • 2 GB RAM
  • 40 GB SSD
  • 1 Gbps · unlimited local traffic
  • 1 dedicated IPv4
  • /64 IPv6 included
Deploy

Linux VPS – 4 GB RAM

Web servers and small databases.

$42.40/mo

Hosted in Nairobi, Dar es Salaam, Lagos & Kampala

  • 2 vCPU
  • 4 GB RAM
  • 80 GB SSD
  • 1 Gbps · unlimited local traffic
  • 1 dedicated IPv4
  • /64 IPv6 included
Deploy
Most popular

Linux VPS – 8 GB RAM

Production web applications.

$83.30/mo

Hosted in Nairobi, Dar es Salaam, Lagos & Kampala

  • 4 vCPU
  • 8 GB RAM
  • 160 GB SSD
  • 1 Gbps · unlimited local traffic
  • 1 dedicated IPv4
  • /64 IPv6 included
Deploy

Linux VPS – 16 GB RAM

High-traffic applications.

$165.10/mo

Hosted in Nairobi, Dar es Salaam, Lagos & Kampala

  • 8 vCPU
  • 16 GB RAM
  • 320 GB SSD
  • 1 Gbps · unlimited local traffic
  • 1 dedicated IPv4
  • /64 IPv6 included
Deploy

Linux VPS – 32 GB RAM

Enterprise applications.

$328.70/mo

Hosted in Nairobi, Dar es Salaam, Lagos & Kampala

  • 16 vCPU
  • 32 GB RAM
  • 640 GB SSD
  • 1 Gbps · unlimited local traffic
  • 1 dedicated IPv4
  • /64 IPv6 included
Deploy

Linux VPS – 64 GB RAM

Massive workloads and consolidation.

$655.90/mo

Hosted in Nairobi, Dar es Salaam, Lagos & Kampala

  • 32 vCPU
  • 64 GB RAM
  • 1280 GB SSD
  • 1 Gbps · unlimited local traffic
  • 1 dedicated IPv4
  • /64 IPv6 included
Deploy

Prices exclude VAT. Local currency figures are indicative and settled at checkout. Need more cores or memory? Talk to Sales.

Weighing up Windows too? Compare all Linux & Windows plans on the VPS Hosting page.

Why Fedora

Why Fedora on Lineserve

Fedora is where tomorrow's enterprise Linux is built: new kernels, GCC, Python and container tooling land here first — ideal when you need what shipped last month, not three years ago.

  • The newest kernels, compilers and language runtimes in mainstream Linux.
  • Upstream of RHEL — what you build here is where the RHEL family is heading.
  • First-class container tooling with Podman built in.
  • The image is free on every plan — you only pay for the server.

Fedora images

Updated regularly

Latest releaseFast-moving — new major about every 6 months
Custom ISO upload supported on all plans.

Use cases

What people run on Fedora

Development environments

Build against the toolchain versions your team will standardise on next.

Latest-kernel workloads

Features and drivers that haven't reached LTS distros yet — eBPF, new filesystems, fresh hardware support.

Podman & containers

Rootless containers with Podman and Buildah, no daemon required.

CI & build runners

Disposable, always-current build machines — snapshot, run, destroy.

Testing before RHEL family

Validate your stack against what's coming to Rocky and AlmaLinux later.

Modern language stacks

Current Python, Go, Rust and Node without third-party repos or version managers.

Who runs here

The short-lived machines that are worth putting in-country

A staging box on the paths your users are actually on

Your test environment in Frankfurt tells you what your application does on a European network. A staging copy in ke-1a tells you what it does for someone in Nairobi on a mid-range Android over mobile data, which is the audience these markets are overwhelmingly made of. Same code, different vantage point, and the second one is the one your users have.

A CI runner beside the fleet it deploys to

Pipelines that build in one continent and deploy to another pay the distance twice on every artefact. A runner in the same region as the production tier turns that into a local copy, and Fedora keeps the toolchain current enough that the runner is not the reason a build fails.

Previewing what your Rocky and AlmaLinux boxes get later

Fedora runs upstream of the RHEL family, so it is where you meet the kernel, the Python, the OpenSSL policy and the container stack your in-country fleet will inherit. Run it in the same region as that fleet and you are testing against the same network as well as the same software.

Podman, rootless containers and current observability tooling

No daemon, rootless by default, and the eBPF-era tracing tools that arrive here first. Pointing them at an in-country application tier tells you things a dashboard aggregated over an intercontinental link will not.

A development box where the engineer actually sits

Distributed teams end up with people in Lagos, Nairobi or Dar es Salaam working on infrastructure registered somewhere else. Giving that engineer a machine in their own city makes an interactive session feel like a local one — in-metro round trips are typically single-digit milliseconds — while the account, the token and the invoice stay with head office.

Three cities for an afternoon

Cloud servers are priced by the vCPU, GB of RAM and GB of storage you ask for, from $13.89 a month, and the region is one parameter on the create call. Standing up an identical box in all three cities to compare behaviour is a script and an afternoon, not a project.

Fedora VPS from $21.95/month; cloud servers built to spec from $13.89, with on-demand snapshots and a full API and CLI on every plan. Prices exclude VAT.

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.

Live

Kenya

Nairobi

~2 ms

typical, within metro · Data stays in Kenya

Live

Tanzania

Dar es Salaam

~6 ms

typical, within metro · Data stays in Tanzania

Live

Nigeria

Lagos

~4 ms

typical, within metro · Data stays in Nigeria

Live

Uganda

Kampala

~3 ms

typical, within metro · Data stays in Uganda

Expansion zonesSouth Africa · za-1aGhana · gh-1a

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.

FAQ

Questions, answered

The current Fedora release, kept up to date — Fedora ships a new major roughly every six months, and our image tracks it. You can also bring your own image with a custom ISO.

Fedora releases are supported for about 13 months, so they suit servers you actively maintain and upgrade. For boxes you want to set up and leave for years, Ubuntu LTS, Debian, Rocky or AlmaLinux are the better fit — we offer them all.

Yes. All Linux images, Fedora included, are free on every plan — the plan price is the full price of the server.

Yes. Every Fedora VPS gives you complete root access and SSH key authentication from the moment it boots. It's your server to configure however you like.

Yes. Provide cloud-init user data at deploy and your server bootstraps itself on first boot — packages installed, users created, keys in place before you ever log in.

Yes. Fedora's dnf system-upgrade moves you to the next release in place — snapshot first so you can roll back in a click. Or rebuild fresh; deploys take under a minute.

Every plan supports on-demand snapshots and scheduled automated backups. Snapshot storage is billed per GB beyond your included allowance.

Usually not. Around thirteen months of support per release means a machine you want to leave alone will need a release upgrade before you have forgotten it exists. For the production tier take Ubuntu LTS or Debian, or Rocky Linux and AlmaLinux if you are in the Red Hat family — then keep Fedora beside them for the work it is good at.

The current one, kept up to date, with a new major arriving roughly every six months. Moving between releases is dnf system-upgrade in place, or a fresh instance since deploys take under a minute. Snapshot first either way.

The same one as the thing it is standing in for. A staging environment in a different country from production tests your code but not your deployment, and the differences that bite in these markets — origin distance, domestic routing, mobile clients — are exactly the ones a distant staging box hides.

A 2 GB plan is $21.95 a month, and a cloud server built to your own spec starts at $13.89 for 1 vCPU, 1 GB of RAM, 20 GB and an IPv4. Instances go on and come off as you use them and arrive on one invoice at the end of the month, which is the shape most experimentation actually takes.

Yes, on one console, one API token and one invoice. The region is a parameter on the call rather than a separate endpoint or account, so a script that provisions ke-1a, tz-1a and ng-1a in one loop is the normal way to do it.

How your origin behaves when the request does not cross an ocean: how many round trips your page really makes, which of them are uncached, and what your TLS and API sequences cost when the base distance is a city rather than a continent. In-metro round trips in these cities are typically single-digit milliseconds, which changes what your slowest endpoint turns out to be.

If it is a copy of production, yes. A dump of Tanzanian customer records taken to a laptop or a European staging box is a transfer of personal data out of Tanzania, which requires a permit from its Commission — and Kenya's and Nigeria's statutes have their own conditions. Testing in-region on synthetic data avoids the whole conversation.

That is what the API and CLI are for. Instances, snapshots, private networking and IP allocation are all covered, one token works across all three regions, and cloud-init runs your setup on first boot so a box is ready before you would have finished logging into it.

Your data stays in the region you deploy to. Across our data centres in Nairobi (Kenya), Dar es Salaam (Tanzania), and Lagos (Nigeria) it never has to leave the continent — deploy in the country closest to your users and your data is held there.

In whichever of our three regions you choose — Nairobi (ke-1a), Dar es Salaam (tz-1a), or Lagos (ng-1a). Your content is stored and served from that in-country facility.

Pay in USD by card or bank transfer — or switch to our Kenya, Tanzania, Nigeria or Uganda market to pay locally in KES, TZS, NGN or UGX with methods like M-Pesa and MTN Mobile Money.

You can view and pay in USD, or switch to a local market to pay in KES (Kenya), TZS (Tanzania), or NGN (Nigeria). You're settled in the currency you choose at checkout.

Deploy your Fedora VPS in under 60 seconds

Full root, 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 & UGX