Infrastructure for what Uganda actually runs

It helps the part you control. Operator callbacks originate inside Uganda, so an endpoint in Kampala receives and acknowledges them without either direction leaving the country, and every retry is a round trip you would otherwise pay for twice. Put the receiver, the queue behind it and the reconciliation job in ug-1a and the loop stays domestic.

Close, yes. Domestic, no — and the second is what your architecture and your compliance file both care about. A request served from Nairobi still crosses the border at Malaba or Busia, and a copy of Ugandan personal data held there is a transfer out of Uganda under section 19. Nairobi, Dar es Salaam and Lagos make excellent second regions on the same account. For a Ugandan primary, ug-1a is the one in Uganda.

Yes — on a large instance, or on dedicated hardware where single tenancy is an audit or licensing requirement, with the database on its own storage and backups scheduled into object storage in the same region. Size around the month-end and dividend runs rather than the ordinary week, and confirm your own obligations with UMRA or the Bank of Uganda, depending on your tier, before you fix the topology.

Size for the ordinary month and resize for the season. vCPU, RAM and storage scale independently up to 32 vCPU and 64 GB with minimal downtime, so a machine goes up for the buying and shipping window and comes back down afterwards. Put documents and traceability attachments in object storage, where transfer and requests are unmetered.

Yes, and this is where it helps most. An upload from a district office to Kampala travels over domestic fibre — the national network was at 80,257 km in June 2026, and the state backbone reaches regional centres and the border posts. An upload to Europe makes the overland haul to the coast and then the ocean crossing, on a link that was already the weak part of the chain. Often that is the difference between a slow submission and a failed one.

For a tour operator or a lodge, usually yes, with a CDN in front. Guests browsing from abroad are served from a cache; the people touching the system every hour — reservations, rates, permits, accounts, the staff at the property — are in Uganda, along with the guest records. Where a workload genuinely serves a foreign audience end to end, put the origin near the audience: four regions on one account make that a deployment decision.

No. Compliance belongs to you as the controller, whatever country the server sits in. What a Kampala region gives you is residency: the data stays in Uganda, so the section 19 justification does not arise for it, and where the customer data is held becomes the name of a city rather than an appendix. Registration with the Personal Data Protection Office and its annual renewal remain yours.

Your TIN and registered name exactly as URA holds it, plus any purchase-order or cost-centre reference, sent to [email protected] before the order. Displayed prices exclude VAT; Uganda's 18% is shown separately at checkout, and annual billing runs ten months for twelve if the spend has to sit inside a funding year.

Yes — that is colocation, quoted per footprint because rack space, power, connectivity and term vary too much for a price card. Tell [email protected] the rack units, the power per rack, the connectivity you need and when the hardware ships. Start early: equipment bound for Kampala arrives through Mombasa or Dar es Salaam and travels inland, so the logistics leg is real rather than a formality.