Cloud hosting in Rwanda, run from Kigali and Huye.
We build and operate this cloud, we do not resell someone else’s. Shared hosting through to private cloud and bare metal, on one self-service platform and one account, across two cloud regions in Rwanda. Kigali and Huye, 130 km apart and 2.2 ms from each other. Web hosting from RWF 4,400 a month, cloud servers from RWF 17,700, invoiced in francs and payable by mobile money.
Most Rwandan organisations run their websites and their data on servers in another country, priced in a currency they do not earn.
We operate two cloud regions inside Rwanda, in Kigali and Huye, and put every hosting and infrastructure service on them.
Your data stays home, your bill stops moving with the dollar, and the person who fixes it is in your timezone.
A multi-cloud strategy you can run in Rwanda without leaving one console.
Shared hosting, public cloud servers, a full infrastructure platform, a private region and physical hardware are usually five vendors, five contracts and five bills. Here they are five rungs of the same platform, in the same two Rwandan regions, on one account.
-
01
Shared hosting
A website, WordPress, email and a domain. Managed for you.
Self-service -
02
Public cloud servers
Your own VPS with full root access, running in under a minute.
Self-service -
03
Infrastructure platform
Compute, storage, Kubernetes, databases and networking by API.
Self-service -
04
Private & hybrid cloud
A dedicated region for regulated workloads, joined to the public one.
Scoped -
05
Bare metal & colocation
Single-tenant hardware and rack space, connected to the same network.
Quoted
Moving up a rung is a migration inside one provider, one network and one invoice. Not a new procurement, a new contract and a data export across a border.
Three steps, whichever rung you start on.
Find it in the directory
Filter by what you need. Every entry shows the provider, the zones it runs in, and the starting price. Not a form to fill in before you learn anything.
Order it or scope it
Self-service services you buy and deploy in minutes. Regulated or large workloads get a scoping call with an engineer who runs the regions, not a reseller.
Run it from Rwanda
Your workload lives in Kigali or Huye, invoiced in francs if you want, with local support and a second region to fail over to.
Everything we run in Rwanda, in one place.
78 entries across the Kigali and Huye regions, including all 57 one-click apps. Each row shows which regions it runs in, so you are not guessing. Filter by category, or read the whole index.
KGL1 = Kigali region · HUY1 = Huye region. Plus 57 one-click apps: WordPress, Docker, PostgreSQL, GitLab, Odoo, Kubernetes and more, each with its own page. Starting prices in Rwandan francs, excluding VAT. Invoiced in francs and payable by mobile money, card or bank transfer. cloud.rw is published by Gewape Cloud Group, which operates both regions and every service listed above.
Two cloud regions inside Rwanda.
Two independent cloud regions, each with its own control plane, each able to hold more than one availability zone. They work identically. Huye is not a warm spare running a cut-down stack. It is the same platform, the same services and the same self-service console as Kigali. Deploy in either, run across both, and keep every copy inside the country.
Kigali
Independent cloud region with its own control plane. Compute, storage, Kubernetes, databases, hosting and the platform console.
- Role
- Production
- Facility
- Carrier-neutral Tier III
- Hardware
- Ours
- Network and IP space
- Ours
- Egress
- Local links
- To Huye region
- 2.2 ms
- Status
- Live
Huye
An independent region with its own control plane, 130 km south of Kigali on separate power and separate fibre. Identical platform, not a warm spare.
- Role
- Production
- Facility
- Carrier-neutral Tier III
- Distance from Kigali
- 130 km
- Round trip to Kigali
- 2.2 ms
- Power and fibre
- Separate
- Use
- Live workloads
- Status
- Live
Dual-stack, dual-homed, and peered on both sides.
A cloud is only as good as the path to it. This is the part most providers will not put in writing, so here it is.
Dual-stack IPv4 and IPv6
Workloads can be reachable over both IPv4 and IPv6, on address space that is ours. No waiting list for v6, and no translation workaround bolted on later.
Dual-homed infrastructure
More than one path out of the infrastructure, so a single upstream failure is not an outage. The same principle as the second region, applied to the network.
Peered locally in Rwanda
Traffic between your service and Rwandan networks is exchanged inside Rwanda instead of hair-pinning through Europe and back. Shorter path, lower latency, cheaper.
Peered internationally
Direct peering and transit onto global networks, so international routes do not depend on one reseller path or one subsea cable staying up.
Our own IP space
The addresses are ours, not rented from an upstream. They stay yours across zones and do not change because a provider upstream of us changed.
API first, and MCP ready
Everything the console does is available over the API, and through Terraform, Ansible and Pulumi. The platform also speaks MCP, so an AI agent can provision infrastructure here directly. Very few providers anywhere offer that, and none of the others in Rwanda do.
No egress fees
Traffic leaving the platform is not metered as a separate line item. The bill does not punish you for serving your own users, or for leaving.
Fast is a number, not an adjective.
Anyone can write “blazing fast”. These are measured figures from a customer instance in the Kigali region, on an encrypted volume, using fio. It is the same test you can run yourself on your first server, in your first hour.
NVMe-backed storage, current-generation server hardware, and a short network path because your users are in the same country. Disk figures measured on a customer instance in the Kigali region; the inter-region round trip measured between the Kigali and Huye edge routers over 20 probes with no loss. Ask us for the raw fio output and the ping log. We send the files, not a screenshot.
Meet your RTO and RPO without sending data out of Rwanda.
Every continuity plan comes down to two numbers: how long you can be down, and how much data you can afford to lose. Answering them needs a second site, and in Rwanda that has normally meant a second country. It no longer has to: the two regions are 2.2 ms apart, close enough to replicate against and far enough apart to survive each other.
| Design | Where the second copy lives | Recovery time objective | Recovery point objective | Data leaves Rwanda |
|---|---|---|---|---|
| Backup and restore | Huye, as snapshots and object copies | Hours | Up to the last backup window | No |
| Warm standby | Huye, with replicas kept running small | Minutes | Minutes | No |
| Active-active across both regions | Both regions serve live traffic | Near zero | Near zero | No |
Targets are indicative. The RTO and RPO that matter are the ones scoped against your workload and written into the agreement, along with the test schedule that proves them. What does not change across all three designs: every copy of the data stays inside Rwanda, so none of them trigger a cross-border transfer assessment.
Built for the sectors that cannot simply pick a cheap host.
Financial services, health and critical information infrastructure are each governed by rules about where data lives, how far apart the copies are, how it is separated from other tenants and how it is encrypted. Those four things are the whole argument, so here is where we stand on each.
Fintech, banks and payment operators
Supervisors expect customer and transaction data to stay in-country, with a recoverable second copy and demonstrable separation. Both zones are in Rwanda, so the localisation question is answered by the architecture rather than by an undertaking.
Healthtech and providers
Patient data is the most sensitive category the Data Protection Law recognises. It stays on encrypted volumes in Rwanda, in an isolated project, with access logged at the platform and operating-system layer and retained for audit.
Operators of essential services
Utilities, telecoms, transport and government-adjacent operators are held to availability and incident-reporting duties. Two production zones 130 km apart and a tested recovery plan are what turn those duties into something you can evidence.
| What the regulator asks about | Why it is asked | What you get here |
|---|---|---|
| Data residency | A copy abroad is a cross-border transfer, whichever copy it is. | Every copy in Kigali or Huye, in Rwanda, named in the contract |
| Geographic separation | Two racks in one building share one fire, one grid and one flood. | 130 km apart, separate power and separate fibre |
| Tenant separation | Shared infrastructure must not mean shared blast radius. | Isolated projects, private networks, per-instance firewalling, or a dedicated private region |
| Encryption at rest | A disk that leaves the building must be unreadable when it does. | LUKS AES-XTS 256-bit volumes, keys in a managed key service, not on the host |
| Access and audit | You have to be able to show who did what, months later. | Single sign-on with enforced MFA, role-based access, platform and OS audit logs |
| Recoverability | An untested recovery plan is a document, not a control. | RTO and RPO scoped per workload, tested on a schedule, report shared |
Whether a specific deployment satisfies a specific supervisor is a question we answer with your compliance team and the actual control set, not with a badge on a homepage. Bring us the requirement and we will map it control by control.
The twelve questions serious organisations send us. Answered here.
Banks, ministries, hospitals and insurers ask the same things before a workload moves. These are the answers, before the meeting. Where something is in progress we say so rather than imply it is done.
In the Kigali or Huye region, in Rwanda, on hardware we own, inside carrier-neutral data centre facilities rather than a single operator’s or a government-run building. We will name the facility, the rack space and the region in writing, and it does not change without notice to you.
Rwandan courts under Rwandan law. There is no foreign parent that can be served an order in another jurisdiction and no obligation to hand data to another government.
We operate to the Rwanda Data Protection Law and align our controls to ISO 27001, with certification in progress. We will send the evidence pack and the open gap register. We do not claim badges we do not yet hold.
In transit with TLS. At rest with LUKS AES-XTS 256-bit encrypted volume types, with keys held in a managed key service rather than on the hypervisor.
Single sign-on with mandatory multi-factor authentication, role-based access control per project, per-instance firewalling, and audit logging at both the platform and the operating-system layer.
Scoped per workload across the two zones and written into the agreement, together with the test schedule. An untested recovery target is a guess, so we test on a calendar, and you get the report.
Snapshots and object copies land in the other Rwandan region, 130 km away, on separate power and separate fibre. Restores are tested rather than assumed.
The platform speaks open, standards-based APIs, not a proprietary interface with a marketing name. Your images, volumes and objects export with ordinary tooling, and there are no egress fees to bill you for leaving.
A 99.99% availability commitment on the platform, with service credits defined in the agreement rather than negotiated after an incident.
An operations team in Kigali, in your timezone, with a named escalation path to the engineers who run the regions. Not a queue in another hemisphere.
Yes. Audit rights, evidence access and log retention go in the contract. Regulated customers get a scheduled review rather than an annual questionnaire.
Subprocessors are declared and change with notice. The regions, the network and the public IP space are ours, so the list is short by design.
Need this as a completed vendor questionnaire, a security schedule or an RFP response? Ask and we will send it.
How to check any cloud claim made in Rwanda.
This market runs on superlatives. Almost every provider here is the only something. Superlatives are not procurement evidence, so here is the question that turns each one into a fact. Ask them of us too, and hold the answers side by side.
| The claim you will hear | The question that settles it | Our answer |
|---|---|---|
| “We are a sovereign cloud” | Which entity operates it, where is its parent registered, and which law governs the contract? | Rwandan entity, Rwandan law, in the agreement |
| “Your data stays in Rwanda” | Where does the second copy live? A backup abroad is still a cross-border transfer. | Second copy in Huye, 130 km away |
| “We run the data centre” | Who operates the building, and is that a party you would separately have to trust with your data? | Carrier-neutral facilities, hardware ours |
| “Tier III data centre” | Which facility, and is the certification for design, build or operations, and who holds it? | Facility named in writing on request |
| “99.9-something uptime” | Does it cover one building or the service, and what is the credit when it is missed? | 99.99% on the service, credits defined |
| “We are a cloud” | Can you create and destroy a server yourself, by API, at 23:00, without raising a ticket? | Yes. Self-service and API, under a minute |
| “No lock-in” | What does it cost to leave with 5 TB, and is the API a standard one or yours? | No egress fees, standards-based API |
| “Local support” | Who is on call at 02:00, and what is the named escalation path above them? | Kigali operations team, named escalation |
| “We are the only…” | Ask for the document. Every “only” in this market should arrive with evidence attached. | We publish what we can prove |
We would rather you ran this list across every provider you are considering, including us, than take a homepage adjective at face value. Where we are still working on something, certification for example, the answers above say so.
What changes when the cloud is actually here.
The three options Rwandan organisations usually weigh.
| Criterion | In Rwanda, with us | Hyperscaler region abroad | Single-site local host |
|---|---|---|---|
| Where the data physically sits | Kigali or Huye, Rwanda | Usually Johannesburg, Europe or the Gulf | One facility in Rwanda |
| Type of facility | Carrier-neutral Tier III partner facilities | The operator’s own global estate | Varies, sometimes state-operated |
| Second region inside the country | Yes. 130 km away in Huye | No zone in Rwanda at all | Typically none |
| Who can compel access | Rwandan courts, under Rwandan law | The operator’s home jurisdiction | Rwandan law |
| Currency on the invoice | RWF or USD, your choice | USD or EUR, exchange risk is yours | Usually RWF |
| Payment methods | Mobile money, card, bank transfer | International card or invoice | Bank transfer, sometimes mobile money |
| Charges for data leaving | No egress fees | Metered egress, often the largest line | Varies |
| Time to a running server | Under a minute, self-service | Minutes, once the account clears | Often a quote and a provisioning ticket |
| Availability commitment | 99.99% with service credits | Per-service SLAs, credits on request | Building uptime, one site |
| Who answers at 02:00 | The team that runs the hardware, in Kigali | Tiered support, another timezone | Local team |
Cloud hosting in Kigali. Cloud hosting in Huye.
Two cities, two independent regions, one platform and one account. Pick the one nearest your users, or run in both.
Cloud hosting in Kigali
Kigali is where most Rwandan traffic starts and where the country’s networks meet. Hosting here puts your site or application on the same side of the local exchange as your users, so a page load is a short local hop rather than a round trip to Johannesburg or Europe. Web hosting, cloud servers, managed databases, Kubernetes, object storage and all 57 one-click apps run in this region, invoiced in Rwandan francs.
Cloud hosting in Huye
Huye is a full second region, not an overflow site. Same platform, same services, the same console, 130 km south of Kigali on separate power and separate fibre and 2.2 ms away. Run production here in its own right, or use it as the in-country second copy that makes a recovery plan real without sending anything abroad.
Gewape Cloud Group operates the Gewape Cloud Platform.
One group, three brands, one platform underneath them. Whichever brand you buy from, the workload runs in the same Kigali and Huye regions, on the same network, supported by the same team.
Megabit Cloud
The self-service brand: web hosting, WordPress, cloud servers, business email and .rw domains, sold and supported locally. The +250 788 125 000 line on this page is the Megabit Cloud team, and they are the fastest route to getting something running today.
Gewape Cloud Infrastructure
The enterprise arm: private and hybrid cloud, data residency written into contracts, and the engineering conversation for banks, ministries, hospitals and regulated operators. It runs the Gewape Cloud Platform that the console and the API belong to.
Metal on Cloud
Single-tenant hardware: dedicated bare metal, colocation and direct connect into the same regions, for workloads where shared infrastructure is not an option and performance variance is a business risk.
cloud.rw is published by Gewape Cloud Group and lists what the group operates inside Rwanda. It is our index, not an independent review site. That is exactly why every claim on it comes with the question that verifies it.
Questions people actually ask.
Is there a cloud provider with data centres inside Rwanda?
Yes. We run two cloud regions inside Rwanda. Kigali and Huye, roughly 130 km apart, on our own hardware, network and public IP space. A workload placed in a Rwandan zone stays on Rwandan infrastructure.
How much does web hosting cost in Rwanda?
Web hosting starts at RWF 4,400 a month and cloud servers at RWF 17,700. Prices are published rather than quoted, and there are no egress charges on top of them.
Can I pay in Rwandan francs or with mobile money?
Yes. Megabit Cloud bills in local currency and accepts mobile money, card and bank transfer. That matters more than it sounds: a dollar-denominated infrastructure bill silently re-prices every month the franc moves.
What is the difference between Megabit Cloud and the Gewape Cloud Platform?
Megabit Cloud is the self-service route. Websites, WordPress, business email, .rw domains and cloud servers you can order and run without talking to anyone. The Gewape Cloud Platform is the engineering route. A console and API with compute, storage, managed Kubernetes, managed databases, load balancers and private networking, for teams that build on infrastructure rather than buy hosting. Both run in the same two Rwandan regions.
Does hosting here help with the Rwanda Data Protection Law?
Keeping personal data on infrastructure physically located in Rwanda, operated by a locally established entity, removes the cross-border transfer question, usually the hardest part of a data protection review. It does not remove your own obligations as a controller, and we put the residency and processing terms in writing rather than ask you to trust a badge.
Can I register a .rw domain?
Yes. .rw and co.rw, alongside more than 400 other extensions, with DNS, free SSL and business email on the same account.
How quickly can I get a server running?
A cloud server provisions in under a minute with full root access and your choice of OS. On the Gewape Cloud Platform you launch instances, volumes, Kubernetes clusters and managed databases from the console, the API or Terraform.
Who publishes cloud.rw?
Gewape Cloud Group. The operator of the Kigali and Huye regions and of every service in the directory, through Megabit Cloud, Gewape Cloud Infrastructure and Metal on Cloud. This is our index of what we run in Rwanda, not an independent review site.
Tell us what you are running, and what it costs you now.
One conversation, no pitch deck. If an RWF 4,400 hosting plan is the right answer, skip us entirely and order it in five minutes. If it is a regulated workload, an engineer who runs the regions will be on the call.
+250 788 125 000 (Megabit Cloud sales) · WhatsApp +250 791 500 571 · sales[at]gewapecloud.com · Kigali, Rwanda