LINESERVE

Kampala — ug-1a

Cloud Servers in Uganda

Built per vCPU, per GB, per disk — in Kampala, from UGX 51,750 a month.

There is no predefined flavour to fit yourself into. A cloud server is priced as the sum of what you build it from: UGX 16,150 per vCPU, UGX 11,400 per GB of RAM, UGX 930 per GB of Universal SSD and UGX 5,600 per public IPv4, with a /64 of IPv6 free and Linux images at no charge. The smallest real machine — 1 vCPU, 1 GB, 20 GB and one address — is UGX 51,750 a month and boots in under 60 seconds. Each dimension resizes on its own, up to 32 vCPU, 128 GB of RAM and 16 TB of storage. And all of it runs in ug-1a, Kampala, which is the only kind of cloud region a Ugandan workload can currently have in its own country.

Starting atUGX 51,750/month

1 vCPU · 1 GB RAM · 20 GB SSD · IPv4 included — build exactly the server you need.

  • Built per resource — pay for the vCPU, RAM and storage you actually use
  • Deploy in under 60 seconds, resize each dimension independently
  • Four locally-hosted regions — Nairobi, Dar es Salaam, Lagos & Kampala
  • Data residency for Uganda's Data Protection and Privacy Act — your data stays in-country
  • 99.9% uptime SLA, free DDoS protection, unlimited local traffic

No credit card required · Billed in UGX

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

vCPU
1 vCPU32 vCPU
GB
1 GB128 GB
GB
20 GB16,384 GB

Minimum 20 GB for Linux images.

IPs
0 IPs8 IPs

Your server

Hosted in Nairobi, Dar es Salaam, Lagos & Kampala

  • Compute2 vCPU · 4 GB RAM
  • Storage40 GB Universal SSD
  • Public IPv41 address
  • ImageLinux (free)
ComputeUGX 77,900/mo
StorageUGX 37,200/mo
Public IPv4UGX 5,600/mo
IPv6 /64 Free
Total (Monthly)UGX 120,700/mo
Deploy this server Talk to Sales

Unit rates

ResourceUnitPrice /mo
vCPUper vCPUUGX 16,150
RAMper GBUGX 11,400
Storage — Universal SSDper GBUGX 930
Public IPv4per addressUGX 5,600
Windows Server 2019 Standardper serverFrom UGX 29,800
Windows Server 2022 Standardper serverFrom UGX 37,200
Windows Server 2025 Standardper serverFrom UGX 44,800
Bandwidth1 Gbps port, unlimited local trafficFree
IPv6 (/64)per serverFree
Linux imagesUbuntu, Debian, Rocky, AlmaLinuxFree

Prices exclude VAT and any applicable taxes. Annual billing gives you two months free. Local currency figures are indicative and settled at checkout.

Why here

The nearest cloud region to Kampala is in another country. Several, in fact.

Start with the map, because for a Ugandan architect the map is the whole argument. Amazon runs one region on this side of the world at Cape Town. Microsoft runs Johannesburg and Cape Town. Google runs Johannesburg, opened in January 2024. Every one of them is thousands of kilometres south of Kampala, across several borders, and none of them has any plan a Ugandan buyer can point at for something closer.

What Uganda's neighbourhood does have is edge. Amazon's African edge locations are Cape Town, Johannesburg and Nairobi, and it opened a Direct Connect location near Nairobi in September 2025; Google's interconnect sites include Nairobi and Lagos. Edge is genuinely useful and it is not a region. It caches your static assets; it does not run your database, terminate your API, or hold the ledger your reconciliation job reads. The compute stays where the region is.

Now compound it with the fact that makes Uganda different from every coastal market on this site. Uganda is landlocked. There is no cable landing station here, because there is no coast. All international capacity arrives as terrestrial fibre from Mombasa across Kenya through Malaba or Busia, or from Dar es Salaam across Tanzania through Mutukula — roughly 900 to 1,000 kilometres of another country's backbone before it reaches a rack in Kampala. So the nearest edge cache, in Nairobi, sits on the far side of that haul. And the nearest actual region sits on the far side of the haul, plus the length of the continent, or the ocean and Europe beyond it. Every request to it, and every reply, pays the whole distance.

That is what a Ugandan business is choosing between when it picks where to run an application: a machine on the near side of the border, or a machine several countries away with a cache somewhere in the middle. Put the compute in ug-1a and the round trip starts and ends in Kampala. The database call, the API hop, the TLS handshake, the mobile money callback coming in from MTN or Airtel — all of them stay inside a city rather than crossing a national backbone and a sea.

Domestic traffic has somewhere to go once it is here, too. UIXP, the Kampala exchange, has run as a non-profit since 2001 and carries 26 participating networks, 29 connections and 380G of connected capacity on PeeringDB, reachable from two interconnected locations in the greater Kampala area. Around it sit MTN Uganda and Airtel Uganda — more than 90% of subscriptions between them — plus the enterprise layer of Roke Telkom, CSquared, Liquid, BCS Group, Tangerine, Africell and Paratus, the research network RENU, and NITA-U's National Backbone Infrastructure reaching regional centres and the border posts. The UCC put the national fibre network at 80,257 km in June 2026. Everything a Ugandan application needs to reach its users already terminates in the city the server is in.

0

Hyperscale cloud regions in Uganda, or in any bordering country

0

Submarine cables landing in Uganda — capacity arrives overland

UGX 51,750

Smallest cloud server, per month, excluding VAT

32 / 128

Maximum vCPU and GB of RAM on a single instance

A cache is not a region

It is worth being exact about what edge infrastructure does for a Ugandan application, because the marketing rarely is. A content delivery point of presence holds copies of your static assets closer to the user. It does not execute your code, hold your data, or shorten the path for anything dynamic — the login, the search query, the checkout, the report. Those go all the way to the region, wherever it is. Moving the region is the only thing that moves them.

Build the machine, not the plan

vCPU, RAM, storage and addresses are billed per unit per month, so the shape of the server follows the shape of the workload rather than a vendor's tier list. A memory-hungry analytics job takes RAM without taking cores it will never use. A CPU-bound encoder takes cores without paying for RAM it will never touch. And each dimension resizes on its own, which means growth is a line on next month's invoice instead of a migration to a bigger plan.

Windows, if the application needs it

Windows Server Standard is licensed per vCPU on a minimum of four cores, on top of compute: from UGX 29,800 a server for Server 2019, UGX 37,200 for 2022 and UGX 44,800 for 2025, all activated at first boot with administrator rights over RDP. If you would rather not build it yourself, fixed Windows VPS plans start at UGX 119,000 a month with the 2022 Standard licence already in the price. Linux images cost nothing at all.

Payments

A bill that changes size, paid the way Uganda pays

Resource-priced compute means the number moves when you resize, which is exactly why the settlement rails matter. Uganda runs on two wallets — MTN Mobile Money and Airtel Money, on the networks that carry more than 90% of subscriptions, with 37.8 million active mobile money users moving 2.55 billion transactions in the quarter ending June 2026 — plus bank transfer and card. All four are available here, all of them in shillings, all of them settling inside Uganda.

MTN Mobile Money and Airtel Money

Both wallets, as first-class methods rather than one and a footnote. A UGX 51,750 starter instance or a UGX 195,000 build is an ordinary wallet payment authorised with a PIN on your own handset — no card, no bank onboarding, no forex conversation.

Bank transfer

The rail for a month that grew. A fleet of instances, a large build, or a year taken up front at ten months for twelve will usually sit above a wallet limit, and UNISS and the Kampala Automated Clearing House are what Ugandan business uses for numbers that size. One transfer, one reference, one line your reconciliation recognises.

Card

Visa and Mastercard, charged in shillings, for the finance teams that would rather keep a card on file than authorise a payment every time an instance changes size. A virtual Mastercard issued through MTN MoMo also lets a subscriber without a bank card clear a card-only checkout.

One account, one shilling invoice

Instances in Kampala, an object storage bucket, a dedicated machine and a standby in Nairobi all bill to one account from LINESERVE, INC., in UGX, with the 18% VAT on its own line. Annual billing on eligible plans is ten months for twelve — one approval instead of twelve, which is what a budget-cycle buyer is actually optimising for.

Displayed prices exclude VAT; Uganda's 18% is calculated and shown separately at checkout. You can start without a payment method on file and add one later.

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

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.

Live

Uganda

Kampala

~3 ms

typical, within metro · Data stays in Uganda

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

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

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

1

Choose region, OS & size

Pick a region, Linux or Windows, and the instance that fits your workload.

2

Deploy in under 60 seconds

We provision your server and run your setup — no manual first-run steps.

3

Connect & scale

Log in over SSH or RDP, then resize or snapshot anytime from the console or API.

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.

Why Lineserve

Decided on what actually matters here

CapabilityLineserveGlobal cloud
Billing in UGX
Single-digit local latency
Support in your timezone
No card or forex required
Full API & console
Pay in your currency — no forex
Data stays in Uganda

Tax & invoicing

A variable bill still has to satisfy URA

Uganda's standard VAT rate is 18%, administered by the Uganda Revenue Authority, and hosting is named rather than inferred: URA's published list of taxable electronic services opens with the words "web hosting". Prices here exclude VAT and the 18% is calculated and shown separately at checkout, so a UGX 310,000 build is UGX 310,000 of infrastructure spend in the forecast with the tax on its own line.

Resource-priced compute makes the invoicing question sharper rather than softer, because the amount is not the same every month. What your finance function needs is not a fixed figure — it is a document with the right identifiers on it, every time. In Uganda that means your TIN, your registered name as URA holds it, a unique invoice number, the service and the period, the taxable value and the VAT stated separately. EFRIS, URA's real-time Electronic Fiscal Receipting and Invoicing Solution, sets the standard the whole market now works to: a Fiscal Document Number, an invoice identification number, a verification code and a QR code, with the buyer identified by TIN, business registration number or national ID. URA lists claiming a VAT credit on purchases not supported by an e-invoice among the non-compliance it rejects, and information technology and communications is one of the twelve sectors bound by EFRIS whether VAT-registered or not.

So send the identifiers once, at the order, and the billing account is configured before the first resize rather than corrected after the fourth. And put the purchase in front of your tax adviser at the same time — the reverse charge on imported services and the 15% withholding regimes that have applied to non-residents' digital services income since 1 July 2025 are both questions with a number attached, and both are cheaper to answer in advance.

What to send before the first instance

Your TIN, your registered name exactly as URA holds it, a billing email that reaches finance rather than an engineer, and any purchase-order or cost-centre reference. [email protected], once, and it is on every invoice from the first billing run.

Keeping a variable bill predictable

Two things help. Annual billing on the steady part of the estate — ten months for twelve — turns the baseline into one approved figure for the year. And resizing deliberately, rather than provisioning for a peak that happens twice a year, keeps the variable part genuinely variable: capacity added in September and given back in November costs what those months cost.

The full Ugandan billing treatment — the 18%, URA's electronic-services rules, EFRIS and the withholding questions — is set out on the pricing page.

Data residency

Where the instance is, and where its copies are

Uganda's Data Protection and Privacy Act, 2019 — Chapter 97 — has been in force since May 2019, with the Personal Data Protection Office, seated within NITA-U, operational since August 2021 and registration required annually of data collectors, processors and controllers. Section 19 allows personal data to leave Uganda only where the destination offers protection at least equivalent to the Act, or where the data subject has consented, and the Office expects records of the legal basis, the safeguards and the justification for every transfer, available for inspection on audit.

A cloud server in ug-1a is created in Kampala and its storage is created with it. Data you put there is held in Uganda and is not moved out of the country without your instruction. That is data residency for Uganda's Data Protection and Privacy Act, and it means the cross-border file simply has nothing to record for that workload.

The part worth thinking about twice is not the instance — it is the copies. Snapshots, scheduled backups, object storage buckets and a standby database in another region are all real data in real places, and where you put them is a decision rather than a default. Nairobi, Dar es Salaam and Lagos are one API call away on the same account, which makes disaster recovery a configuration change. Just make it deliberately: a copy of Ugandans' personal data in ke-1a, tz-1a or ng-1a is a transfer out of Uganda. Application images, build artefacts, container registries and telemetry without personal data raise no such question and are the right things to replicate freely.

Uganda enforces this, including against companies with no presence here

The registration duty under the Act is written to reach entities outside Uganda that process Ugandan citizens' personal data, and the Personal Data Protection Office has applied it that way — in July 2025 it found a foreign technology company in breach for failing to register and for failing to evidence a lawful basis for taking complainants' data out of the country, and ordered it to register within thirty days. Penalties under the Act reach 245 currency points, or up to 2% of annual gross turnover for a corporation.

Who runs here

The Ugandan workloads that want a machine they can reshape

Mobile money and fintech platforms

Collections and disbursement endpoints receiving callbacks from MTN and Airtel in parallel, USSD gateway backends, KYC document stores, credit scoring, and reconciliation running against two wallet providers rather than one. These estates grow in one dimension at a time — more RAM for the queue, more cores at month end — which is precisely what resource pricing is for. The callbacks originate in Uganda; so should the endpoint that acknowledges them.

Financial institutions under supervision

The Bank of Uganda's Cyber and Technology Risk Management Guidelines have bound supervised financial institutions since 1 December 2024, with penalties reaching 2% of gross earnings, and infrastructure governance sits inside that supervision. Core systems, member and customer portals, agent-banking backends, batch runs at month end. Tier 4 institutions licensed by the Uganda Microfinance Regulatory Authority buy the same shapes at smaller sizes.

NGO and donor programme platforms

DHIS2 and other health and monitoring systems, ODK and KoboToolbox form servers taking field submissions from Gulu, Arua and the west, donor reporting dashboards, grant accounting on ERPNext or Odoo, beneficiary registries. The load arrives in bursts around reporting deadlines rather than evenly, which makes a machine you can grow for a fortnight and shrink afterwards worth more than a bigger machine all year.

Oil, gas and Albertine service contractors

With first oil targeted for the second half of 2026 across Tilenga in Buliisa, Kingfisher in Kikuube and the 1,443 km EACOP pipeline to Tanga, the buyers are the Ugandan contractors, logistics firms, HSE consultancies and surveyors around Hoima, headquartered in Kampala. Document control, incident reporting, local-content and contractor management, tender portals, and telematics ingest aggregating from remote sites over constrained links into a server on the same side of the border.

Coffee, agriculture and traceability datasets

Coffee and gold are Uganda's two leading foreign exchange earners, and export buyers increasingly ask for geolocation and traceability data down to the plot. Cooperative membership and payout systems, warehouse receipt platforms, exporter portals, SMS and USSD extension services. Traffic follows the harvest and the shipping calendar, so seasonal capacity added and given back beats a permanently oversized machine.

Universities, research and edtech

RENU carries Uganda's higher education sector and is one of the larger participants at the Kampala exchange. Moodle and other learning platforms at term-start scale, student information systems, institutional repositories, research data. Term start is a date in the diary, not a forecast — which is the cleanest case there is for scaling a machine up for a fortnight and back down afterwards.

Agencies, ISVs and internal platform teams

Kampala's agency and product scene runs several environments per client and several clients per engineer: production, staging, a build runner, a database, a small object store for assets. Resource pricing keeps the non-production half of that estate honest, because a staging box does not have to be sized like production to exist.

Cloud servers from UGX 51,750/month built per resource, Linux VPS plans from UGX 81,750, Windows VPS from UGX 119,000 with the licence included, dedicated LineServe Core hardware from UGX 1,151,000 plus setup, object storage from about UGX 228.16 per GB with transfer and requests free, and colocation in Kampala quoted per footprint. Prices exclude VAT.

Migrating

Moving compute to Kampala

From a hyperscaler region abroad

The parts that transfer cleanly transfer cleanly: standard Linux images, cloud-init, SSH, RDP, snapshots, an API and a CLI, and object storage at an S3-compatible endpoint your SDK already understands. What you give up is a catalogue of managed services you were probably using three of. What you get back is distance — the round trip stops crossing a border, a national backbone and an ocean — and a bill in shillings you can forecast, from a supplier your finance team can pay from a Ugandan wallet or a Ugandan bank account. Run both for a day, move the DNS, and keep the old account open for a week if it makes the change easier to approve.

From a fixed plan or a box under a desk

Coming off a fixed VPS tier, the win is that the machine stops being a size somebody else chose: take the RAM without the cores, or the cores without the RAM, and change either one later. Coming off hardware in your own office, the win is bigger and more Ugandan. Electricity distribution passed from Umeme to UEDCL on 1 April 2025 and the transition has meant ageing inherited assets, poles due for replacement and load-shedding taken to enable repairs, with tariffs high enough that a diesel generator is standard equipment. A server behind that runs on a cost that tracks the diesel price. Moving it turns the whole arrangement into one fixed shilling line, and a power cut at your address becomes an inconvenience for the people rather than an outage for the customers.

Migration planning and assistance are included at no extra charge. One question settles where a machine really is: which building is it in, and in which country is that building? Ask it of every provider you shortlist, this one included. For Lineserve the answer is ug-1a, Kampala.

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.

By the resource, per month: UGX 16,150 per vCPU, UGX 11,400 per GB of RAM, UGX 930 per GB of Universal SSD and UGX 5,600 per public IPv4, with a /64 of IPv6 free and Linux images at no charge. The smallest real machine — 1 vCPU, 1 GB RAM, 20 GB SSD and one address — is UGX 51,750 a month. Prices exclude VAT.

Up to 32 vCPU, 128 GB of RAM and 16 TB of storage. Each dimension resizes independently with minimal downtime, so you can add memory without adding cores, or storage without touching either.

The same platform, bought two ways. A cloud server is built from resources and priced as their sum, which suits a workload with a shape of its own. A VPS is a fixed plan at a fixed monthly figure from UGX 81,750, which suits a workload that fits one. Both boot in under 60 seconds in ug-1a and both carry the same port, IPv4, IPv6, snapshots, backups and DDoS filtering.

No. Amazon's African region is Cape Town, Microsoft's are Johannesburg and Cape Town, and Google's is Johannesburg. There is no hyperscale region in Uganda or in any bordering country. The nearest edge and interconnect infrastructure is in Nairobi, which is in another country and on the far side of Uganda's overland transit route to the coast.

For static assets it helps. For everything else it does not do the job people assume: a cache holds copies of files, it does not run your code, hold your database or terminate your API. Logins, queries, checkouts and reports go all the way to wherever the compute lives. Moving the compute is the only thing that moves them.

Because Uganda has no cable landing station. International capacity reaches Kampala as terrestrial fibre from Mombasa across Kenya or from Dar es Salaam across Tanzania — roughly 900 to 1,000 km of another country's backbone before it gets here. A request to a server abroad pays that haul and then the ocean, in both directions. A request to ug-1a pays neither.

In ug-1a, our Kampala region. The instance and its storage are created there and stay there unless you move them yourself.

Yes. Windows Server Standard is licensed per vCPU on a minimum of four cores, on top of compute — from UGX 29,800 a server for 2019, UGX 37,200 for 2022 and UGX 44,800 for 2025 — activated at first boot with administrator rights over RDP. Fixed Windows VPS plans with the 2022 licence already included start at UGX 119,000 a month.

In shillings, by MTN Mobile Money, Airtel Money, bank transfer or card. Both wallets are supported, not one. Mobile money suits a monthly bill; a bank transfer suits a large build or a year taken up front at ten months for twelve.

No. Displayed prices exclude VAT. Uganda's standard rate is 18%, administered by URA, and it is calculated and shown separately at checkout.

No. Every instance includes a 1 Gbps port with unlimited local traffic, and object storage transfer in, transfer out and API requests are free. There is no per-gigabyte line to model.

Yes. Data in ug-1a is held in Kampala and is not moved out of the country without your instruction, which gives you data residency for Uganda's Data Protection and Privacy Act. Where your snapshots, backups and any standby replica live is your decision, and worth making deliberately.

Yes — Nairobi, Dar es Salaam and Lagos are on the same account and the same API. Treat personal data carefully when you do: a copy of Ugandans' personal data in another country is a transfer out of Uganda under section 19 of the Act. Images, build artefacts and non-personal telemetry raise no such question.

NVMe-backed storage, a 1 Gbps port with unlimited local traffic, a dedicated IPv4 and a free /64 IPv6, always-on DDoS mitigation, on-demand snapshots and scheduled backups, private networking between your instances, a browser console, and a full API and CLI. Nothing is gated behind a larger size.

Yes. Create, resize, snapshot and destroy from the command line, from Terraform or from CI — every action the console offers is scriptable. The parts underneath are standard: SSH, RDP, cloud-init and open images, so what your team learns here is not one vendor's control panel.

[email protected] and the ticket system. Uganda runs on East Africa Time, UTC+3, all year with no daylight saving, so business hours mean the same thing in January and in July.

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 · Billed in UGX