Hosting used to be an afterthought for Nepali websites: buy a cheap shared plan from whoever registered the domain, and forget about it. That has changed for three reasons. More Nepali businesses are running real applications with logins and payments rather than brochure sites. Customers now notice a slow checkout on mobile data. And the question of where Nepali citizens' personal data is stored has moved from a policy discussion to something clients and regulators ask about. This is how we think about the choice for clients in Kathmandu and across the country.
The four realistic options
- A data centre in Nepal. Several providers in the Kathmandu Valley offer colocation, virtual servers and some managed services. Lowest latency to Nepali users and data stays in the country. Fewer managed services and less automation than the global clouds, and quality varies a lot between providers.
- A global cloud region in India. AWS, Google Cloud and Azure all run regions in Mumbai, and some in Hyderabad, Delhi or Pune. Usually tens of milliseconds from Kathmandu, with the full catalogue of managed databases, backups and monitoring.
- A global cloud region in Singapore. Slightly further than India for most Nepali users, but a common choice when the same app also serves Southeast Asia or Australia.
- A budget VPS or shared host in Europe or the US. Cheap and often what an older site is already on. Every request from Nepal crosses the world and back, which is fine for a static brochure and noticeable for anything interactive.
Latency matters less than you think, until it does not
For a mostly static site, a good CDN in front of any of these options makes the difference nearly invisible, because pages and images are served from an edge location close to the visitor. Latency starts to matter for interactive applications, where each click waits on the server and the database. A checkout that makes five round trips to a server two hundred milliseconds away feels sluggish on a Nepali mobile connection that already adds its own delay. If your users are overwhelmingly in Nepal and the app is interactive, measure from a real phone on Ncell and NTC data rather than from the office fibre, because that is the experience that loses orders.
What the law asks of you
This section is general information, not legal advice, and the rules are moving, so check the current position with a lawyer before you commit to anything for regulated data.
The Individual Privacy Act, 2075 (2018) sets out rights over personal information, and requires consent and a legitimate purpose for collecting and using it. The Electronic Transactions Act, 2063 (2008) covers electronic records and computer-related offences. Sector regulators add their own rules on top: Nepal Rastra Bank for banks, financial institutions and payment providers, and the telecom regulator for telecom operators. The National Cyber Security Policy, 2080 (2023) and related government direction push towards keeping government and sensitive data inside Nepal.
In practice, most ordinary businesses, such as a shop, a clinic's booking site or a SaaS product for Nepali customers, are not currently barred from hosting abroad. Banks, payment companies, government bodies and anyone handling government data face stricter expectations, and for them a Nepali data centre or an explicit written approval is often the only sensible starting point. Whatever your sector, the parts that matter most are within your control: collect only what you need, say clearly what you collect and why, protect it properly, and be able to delete it on request.
Reliability: what to check in a local provider
Power is much less of a worry than it was before load-shedding ended, but a data centre still depends on its generators, its fuel contracts and its links out of the country. Nepal's international bandwidth runs largely through India, with a growing northern route through China, and a cut or maintenance window on a major link is felt by every provider at once. Ask a local provider specific questions and get the answers in writing.
- How many upstream providers and international routes does the facility have, and has it lost connectivity in the last year?
- What is the generator runtime at full load, and how is fuel resupplied during a bandh or a blocked road?
- Are backups taken automatically, how often, and are they stored in a different building?
- What does support look like at 2am on a Saturday, and during Dashain?
- Is there a published uptime record, and what is the credit when it is missed?
The setup we recommend most often
For most Nepali businesses and startups: application and database in a global cloud region in India or Singapore, a CDN in front, automated daily backups copied to a second region, and personal data kept to the minimum the business actually needs. This gives you managed databases, proper monitoring and predictable deploys without a platform engineer, which is the approach set out in DevOps on a budget. The database choice underneath it is covered in choosing a database for a small product.
Where the law or a client requires data to stay in Nepal, we split the problem rather than moving everything. The personal and regulated data lives in a Kathmandu data centre, and the public website, images and anything non-sensitive stays on a CDN and the cloud, where it is cheaper and faster. The hard part of that design is the boundary between the two, which needs to be deliberate and documented, not something that grows by accident.
Decide where your data is allowed to live before you decide where your code runs. Moving a database across borders later is the expensive version of this decision.
Moving an existing site
If your current site is on an old shared host abroad and it is slow for Nepali visitors, moving it is usually a few days of work and one of the cheapest speed improvements available. Plan the DNS change, keep the old server running until the new one is confirmed, and check that email, which is often on the same shared host, has somewhere to go. Our site migration guide covers the SEO side. If you would like a second opinion on where your application should live, that is part of our cloud and DevOps service, and we work with clients across the Kathmandu Valley in person.
Abishek Bimali
Founder & Engineer
Abishek founded SiteCraft Innovation and leads its engineering. He writes about building web and mobile products that hold up in production, for teams in Nepal and abroad.
