Fedora — six months ahead
Fedora VPS Hosting in Uganda
A small, specific group of Ugandan developers, each with a good reason.
Fedora is not the server you configure once and leave for five years, and the people who choose it worked that out long ago. It is the box a Kampala developer keeps because their laptop runs Fedora too, the build runner that needs a compiler no long-term release ships yet, and the machine a careful team points at next year's Red Hat before their production estate has to meet it. Deploy the current release in ug-1a and rebuild it whenever you feel like it.
- The current Fedora release — a new major roughly every six months
- Current Go, Rust, Node and Python without third-party repositories
- Rootless containers with Podman and Buildah, no daemon required
- Deployed in ug-1a, Kampala · billed in Uganda Shillings
- From UGX 81,750 a month — destroy it and rebuild it as often as you like
No credit card required · Billed in 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.
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
Linux VPS – 4 GB RAM
Web servers and small databases.
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
Linux VPS – 8 GB RAM
Production web applications.
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
Linux VPS – 16 GB RAM
High-traffic applications.
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
Linux VPS – 32 GB RAM
Enterprise applications.
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
Linux VPS – 64 GB RAM
Massive workloads and consolidation.
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
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.
The network
The workload with a human waiting on every packet
Most of this site argues about where your users are. This page is different, because the person who feels the distance on a Fedora box is usually you. These machines get used interactively — an SSH session held open all afternoon, a remote editor attached to the instance, a container rebuilt and re-run a dozen times before lunch, a log tailed while something misbehaves. Every keystroke in that session is its own round trip.
Uganda is landlocked and has no cable landing station, so a development box on another continent puts a full overland haul into each of those keystrokes: out through Malaba or Busia toward Mombasa, or through Mutukula toward Dar es Salaam, then under an ocean, then back the same way. It is tolerable for a page load and genuinely unpleasant for an editor. Anyone who has tried to work this way from Kampala on a Thursday afternoon already knows what it feels like.
The same box in ug-1a is reached from Kampala without leaving the country, and from Gulu, Mbale, Mbarara or a campus network over domestic fibre. Uganda's fibre network reached 80,257 kilometres by June 2026 on UCC's quarterly reporting, and the state backbone connects the regional towns to the capital. That is the practical case for the region on this page: not your customers' experience, but yours.
And the boring reason
A build that runs on your laptop stops when the laptop does — and a Kampala office runs on a distribution grid that changed operator in April 2025 and a generator that costs more per unit than the grid. A pipeline running in ug-1a is indifferent to what the power did that afternoon.
Working hours are the same hours
Kampala is on East Africa Time, UTC+3, all year, with no daylight saving to reason about. A cron job you write at 09:00 and a log timestamp you read at 16:00 agree with each other and with the clock on the wall — which is not true of a server whose timezone you set to a European city in 2019 and never revisited.
Paying for it
Small boxes, bought the way small things get bought here
Fedora instances tend to be short-lived and personally owned. The payment story should match that rather than assume a procurement department.
MTN Mobile Money or Airtel Money
Whichever wallet is already on your phone. Both are supported for Ugandan customers, which is the correct answer in a country where the second wallet is not an afterthought — UCC counts around 37.8 million active mobile money users across the two networks.
A shilling price you can reason about
UGX 81,750 a month for the 2 GB plan, UGX 158,000 for 4 GB. Ugandan price-list figures, not a dollar amount converted the day the payment clears, so the number in your head is the number on the invoice. Prices exclude VAT; 18% is added at checkout.
Card or bank transfer when it stops being personal
The moment a runner becomes team infrastructure rather than your own experiment, it usually moves onto a company card or a monthly bank transfer. Both work, on the same account, without changing anything about the instances themselves.
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
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
Who actually deploys Fedora in Kampala
The developer whose laptop is already Fedora
Same dnf, same SELinux behaviour, same Podman, same package names. For someone who works this way the server is an extension of the desk rather than a second environment to learn, and the gap where bugs hide — it works locally, it fails on the server — narrows to almost nothing.
Build and CI runners
Current Go, Rust, Node and Python toolchains without third-party repositories or a version manager per language, on a runner that belongs to you rather than a shared queue. Running it in ug-1a also means the source, the artefacts and the signing keys sit on a machine in Uganda rather than wherever the free tier happens to schedule you.
An early warning for a conservative estate
This is the strongest reason a cautious Ugandan team keeps one. Fedora is upstream of Red Hat Enterprise Linux, so the package that will eventually argue with your Rocky or AlmaLinux fleet argues here first. One small instance is a much cheaper way to find that out than a production release weekend.
University and research groups
Project machines at Ugandan universities and technical institutes, on campuses reached through the national research and education network. The work often needs a kernel, a filesystem or a library that no long-term release has picked up yet, and the box is expected to be rebuilt at the end of the semester regardless.
Container work that has outgrown a laptop
Rootless Podman, Buildah for the images, and a compose file with more services in it than a laptop enjoys running. A 4 GB plan at UGX 158,000 or an 8 GB plan at UGX 310,000 gives that stack somewhere to live where closing the lid does not stop it.
The hub and the hackathon team
Kampala's innovation hubs and the teams that pass through them build against whatever shipped last month, not what shipped three years ago. Fedora is where those toolchain versions arrive first, and a small instance rebuilt between projects costs less than the coffee.
Regions
Kampala is home. The other three are a border you choose to cross.
Deploy in ug-1a and the machine is in Kampala, in the country its users are already standing in. The region is chosen per instance rather than per account, so nothing about this decision is permanent or global: a production database in Kampala, a build runner wherever is convenient, a backup target somewhere else entirely, all on the same key and the same API.
The other three are Nairobi, Dar es Salaam and Lagos, on that same account, the same API and the same shilling invoice. Here is where a Ugandan buyer has to read the map differently from everyone else on it. For a business in Nairobi, ke-1a is home. For you it is abroad twice over: a copy of Ugandan personal data held there is a transfer out of Uganda that belongs in your section 19 record, and a request served from there still crosses the border at Malaba or Busia before it reaches your customer. Regional is not the same word as local, and Uganda is the market where the difference is easiest to see.
That said, the corridor is real and some businesses genuinely live on it. Trade moves between Kampala, Kisumu, Nairobi and Mombasa; the crude pipeline out of the Albertine region runs 1,443 km to Tanga on the Tanzanian coast; freight, agri-export, logistics and contracting firms bill customers in three countries. When your operation is actually in two markets, tz-1a or ke-1a stops being a distant region and becomes the second half of your own footprint. And when what you want is somewhere to put a standby, a replica or an offsite copy, another region on the same account is a configuration change rather than a second supplier to onboard.
Uganda
Kampala
~3 ms
typical, within metro · Data stays in Uganda
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
Uptime SLA
99.9%
- DDoS filtering is included, and so is the traffic
- Service credits applied automatically when we miss the SLA
- Measured monthly, per region, on network and power availability
Support
East Africa Time all year, and a queue that already knows Uganda
Two channels with two different jobs. A signed-in ticket arrives already carrying the account, the region and the instance, so the first reply is about the fault rather than about which machine you meant. [email protected] is the commercial door: a quotation against a purchase order, transfer details ahead of a payment run rather than during it, a billing account configured with your TIN and registered name before the first invoice, and the SLA terms and credit process in writing while you are still choosing.
Ahead of both sits status.lineserve.net. A region-wide event is published there while a reply is still being typed, and thirty seconds on it turns "the site is down" into "my instance is unreachable and the status page is clear" — a different ticket, and a far shorter one.
What that ticket should carry, in the order it is read: the region and the instance, the EAT time the behaviour started, the last thing that changed before it, the actual error text rather than a description of it, and whether it reproduces from more than one Ugandan network. That last one carries more weight here than almost anywhere. Uganda is a two-operator market, and an MTN handset, an Airtel handset and an office fibre line disagreeing about your service is a completely different fault from all three failing together — it is worth thirty seconds of your time and it can save an hour of everyone's.
Uganda runs on East Africa Time, UTC+3, and has never observed daylight saving, so a change window agreed in EAT means the same thing in January and in July. You share that clock exactly with Nairobi and Dar es Salaam and sit two hours ahead of Lagos, which matters when you are scheduling work across regions. The Ugandan commercial day generally runs 08:00 to 17:00, Monday to Friday. One scheduling detail that catches people out: a Ugandan public holiday falling on a weekend stays on that date rather than moving to the Monday, so the calendar is not the same shape as some of its neighbours'.
The last part of local support is vocabulary rather than hours. The person reading your ticket knows what an operator collections callback is and why it retries, knows what the border crossing at Malaba has to do with the traceroute you are staring at, and knows why your finance office wants a TIN on the document before the first billing run. None of that has to be explained before the actual problem can be. Buy from somewhere that has never sold into Uganda and the first twenty minutes of every serious ticket go on describing the country.
Sales
[email protected]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, and it is worth saying so plainly. A new major release arrives roughly every six months and the supported window for each one is short, which is exactly what you want on a development or build machine and exactly what you do not want under a system a Ugandan business depends on. For production, Rocky Linux and AlmaLinux are the Red Hat-family answer and Debian is the quiet one — all free on the same plans.
Plan on a major version every six months or so, which sounds worse than it is. Fedora's in-place upgrade path is well travelled, and on a disposable box most Ugandan teams simply rebuild from a fresh image and re-run their provisioning rather than upgrading at all. Snapshot before you do either.
Because a laptop stops when the power does, sleeps when you close it, and travels with you. A Fedora instance in ug-1a keeps building while you are in a meeting, is reachable from the office and from home, and does not lose an afternoon's work to a load-shedding window. It is also a machine your colleague can reach when you are on leave.
More than for most workloads, because you are the one waiting. An interactive session is the most distance-sensitive thing there is, and Uganda being landlocked means an overseas box adds an overland haul to the coast and an ocean crossing to every keystroke. A Kampala instance is the difference between an editor that feels attached and one that feels remote.
More CPU than RAM, generally. The 4 GB plan at UGX 158,000 a month gives two vCPU and handles most single-project pipelines; the 8 GB plan at UGX 310,000 gives four and is where container-heavy builds stop being annoying. You can resize vCPU, RAM and storage independently, so start small and grow the dimension that actually hurts.
That is one of the best reasons to keep one. Fedora sits upstream of Red Hat Enterprise Linux, so libraries, compilers and container tooling land here first. Run your build against it now and you find out about the incompatibility months before it reaches the production fleet — and both distributions deploy into ug-1a from the same account.
For most Ugandan teams, yes. Podman is daemonless and runs containers rootless, the command-line is close enough that muscle memory carries over, and Fedora ships it as a first-class citizen. Where a vendor's compose file assumes Docker specifically, our Ubuntu page is the more comfortable host.
By MTN Mobile Money or Airtel Money, in shillings, which is the least ceremonious option available. Card and bank transfer work too. Nothing about the instance changes if you switch method later.
On the instance's volume in ug-1a, in Kampala, along with any snapshot you take of it. For a runner that holds signing keys, deployment credentials or a client's source code, knowing the country that machine is in is not an academic question.
Yes — the same Fedora image deploys into ke-1a, tz-1a and ng-1a from the same account. Teams working across the region sometimes keep a runner in each, so a build that deploys to a Nairobi production estate is not pushing artefacts across a border to get there.
Yes. Your data is hosted in Uganda and stays in-country, giving you data residency for Uganda's Data Protection and Privacy Act. It isn't moved out of Uganda without your instruction.
In our Kampala data centre (ug-1a). Your content is stored and served from Kampala, close to your users.
Pay in Uganda Shillings using MTN Mobile Money, Airtel Money, bank transfer, or card. No foreign card or forex conversion is required.
You're billed in UGX. Prices can be viewed in USD, KES, TZS, or NGN, but as a Uganda customer you pay in UGX with no forex conversion.
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 · Billed in UGX
Related products
Every plan below runs in the same three regions, on the same network, billed the same way.