Hosting from Nepal: local data centre vs AWS, Azure, GCP

For most Nepali businesses in 2026, the sensible default is a split: put the website and static files behind a CDN edge in Kathmandu, run the app in an Indian cloud region, usually Mumbai, and keep data inside Nepal only when the rules or your customers require it. Price barely separates the options. Law, payment and latency do.

That's the short answer. The longer one depends on what you run, who your customers are, and whether a regulator will ever ask where your database lives.

What are the real hosting options for a Nepali business?

There are three layers to choose from, and most companies end up mixing them.

The first is hosting inside Nepal. The government runs its own Integrated Data Management Centre in Kathmandu, with a disaster recovery site in Hetauda. It hosts websites for more than 2,500 government offices, including all 753 local units, plus data for Nepal Rastra Bank, Nepal Police and the Nagarik app, according to the Kathmandu Post. It's for government bodies, not for you.

Commercial capacity has grown fast. WorldLink's Data World in Chandragiri has 3.5 MW of IT power and 520 racks, and WorldLink bills it as Nepal's first tier-3 facility. Ncell runs a Tier III data centre in Nakkhu with recovery sites in Pokhara and Hetauda, and in April 2025 it became the first provider listed by the Department of Information Technology under the new data centre directive. Smaller cloud providers such as DataHub sell virtual servers by the month, in rupees.

The second layer is a hyperscaler region in India. None of AWS, Microsoft Azure or Google Cloud has a region in Nepal. The nearest are AWS Mumbai (ap-south-1), Google Cloud Mumbai (asia-south1) and Delhi (asia-south2), and Azure Central India in Pune, with more Azure regions in Mumbai and Chennai.

The third layer is a CDN edge. Cloudflare opened a data centre in Kathmandu in February 2018, its 123rd worldwide. An edge keeps copies of your public files close to users. It isn't hosting. Your origin server and your data stay wherever you put them.

How does a request from Kathmandu actually reach your server?

It helps to follow one page view. A customer opens your site on a phone. Their ISP, say WorldLink or Nepal Telecom, looks for the route to your server. If the page is cached at the Cloudflare edge in Kathmandu, it comes back almost at once. If your server sits in a Nepali data centre, the request never leaves the country.

Otherwise it heads for the border. Most Nepali ISPs buy international bandwidth from Indian carriers such as Airtel, Tata and Sify, and Nepal Telecom also buys some from China Telecom. Nepal's total international bandwidth was reported at 1,342 Gbps in 2023. From there the request crosses into India, reaches the cloud region's load balancer, then your app, then your database, and comes back the same way.

Two things follow. The CDN only helps with what can be cached, so logins, carts and forms still make the full trip. And the border link is shared, so a busy evening can add delay you'll never see in a test run at 10 a.m.

How much does latency really matter?

Less than people fear, as long as you pick the right region. Light in fibre travels at about 200,000 km a second, as APNIC's George Michaelson notes. That sets a hard floor. From Kathmandu, a round trip to Mumbai can't be faster than about 16 ms, to Delhi about 8 ms, to Singapore about 35 ms, and to the US east coast about 124 ms.

Real routes are longer than a straight line, and a page load needs several round trips before anything shows. So the gap between Mumbai and Virginia is felt. The gap between Mumbai and a server in Kathmandu mostly isn't, for an ordinary website. It matters more for chatty apps: point-of-sale systems, live dashboards, anything that talks to the server on every tap.

If most of your users are outside Nepal, say a trekking agency selling to Europe, flip the logic. Host near your buyers and let the Kathmandu edge serve the local visits.

What does hosting cost once you're paying from Nepal?

On list price, a small server costs about the same everywhere. As of August 2026, a 2 GB AWS Lightsail server in Mumbai is USD 12 a month with 60 GB of disk. Google Cloud's e2-small is USD 14.69 a month in either Mumbai or Delhi, without disk. Azure's B1ms in Central India works out to about USD 15. DataHub's comparable plan was listed at NPR 2,100 a month, roughly USD 13.70 at the Nepal Rastra Bank rate of NPR 152.99 to the dollar on 17 August.

The headline number isn't what you pay, though. Four things change it.

• Card limits. Foreign providers bill in dollars by card. Under NRB's Unified Circular 2082, IT businesses can hold prepaid dollar cards of up to USD 3,000 a year, and IT exporters with documented foreign earnings up to USD 5,000, according to ICT Frame. A growing cloud bill can outrun that.
• Tax. Non-resident digital companies selling to Nepali customers above a turnover threshold must register and charge 13% VAT, and cloud services are named explicitly. Microsoft and Google are among those registered, so expect it on the invoice.
• Traffic. Hyperscalers include some data transfer, then charge per GB. Lightsail's overage in Mumbai is USD 0.1093 per GB, and Mumbai plans get half the transfer allowance of most other regions.
• Currency. A rupee price stays put. A dollar price moves with the exchange rate, and every rupee of depreciation lands on your bill.

What do Nepal's rules actually say about where data can live?

The main text is the Data Center and Cloud Service (Operation and Management) Directives, 2081, approved on 28 January 2025 under Section 79 of the Electronic Transactions Act. Its preamble says the aim is to encourage secure storage of data within the country. Its operative clauses are narrower than the headlines suggested.

• Data centres and cloud providers must be listed with the Department of Information Technology before offering services.
• Any data centre storing government data must be rated tier three or higher.
• Government security agencies must use the government's own data centre, and other government bodies must move their departmental data centres into it on a timeline the steering committee sets.

What it doesn't do, as Pioneer Law's reading points out, is flatly ban private businesses from using a foreign cloud. If you sell to government, though, plan on hosting in Nepal from day one.

Banks and financial institutions answer to Nepal Rastra Bank. Its IT Guidelines allow data about Nepali operations to be stored or processed abroad, but only with segregation, strict access controls and proof to the supervisor, who must keep access to the records. Banks are also told to settle which country's law applies before signing a cloud contract. Check the current circulars with your compliance team. This isn't legal advice.

So which should you choose?

A rough rule of thumb, based on what you run:

• A marketing site or blog: static hosting plus the Kathmandu CDN edge. Where the origin sits barely matters.
• A web or mobile app for Nepali customers with no regulatory flag: an Indian hyperscaler region, Mumbai or Delhi, behind the CDN. You get managed databases and backups without running them yourself.
• Government work, or a bank's core systems: a listed Nepali data centre, tier three or better, with a recovery site in another city.
• A mix, which is most real companies: sensitive records in Nepal, everything else in the region with the services you need.

Whatever you pick, write down where every copy of your data sits, including backups and logs. That list is what an auditor, a bank partner or a large customer will ask for first.

For the bigger picture on why this is becoming a political question as well as a technical one, our piece on Nepal's sovereign AI compute plans covers it. If your cloud bill has already crept up, the cloud cost audit blueprint shows where waste usually hides, and the high-availability rebuild walks through what multi-zone hosting involves.

Where does NeuralYug fit in?

We build and run hosting for Nepali companies on both sides of the border: Nepali data centres where the rules demand it, Indian cloud regions where the services are better, and a CDN in front of both. Tell us what you run and who it serves, and we'll map where each piece should live. Talk to us or read about our cloud and DevOps work.