If you live in Iran and want to buy a VPS outside Iran, you face two separate problems. One is technical: which datacenter, which virtualization, which traffic model. The other is payment, when an international card is not an option, as it is not for most people in Iran. This guide takes both step by step: from deciding whether you need a server abroad at all, through the selection criteria and why Hetzner datacenters are so popular, to the Toman payment model with hourly billing and the critical first-day tasks once the server is delivered.
A server outside Iran or a server in Iran? Your users' location decides
The first rule of server geography is simple and has few exceptions: put the server close to your users, not close to yourself. Every web visit involves several network round trips (opening the connection, the TLS handshake, the page's successive requests), and each round trip over an international route costs a few dozen milliseconds more than one over a domestic route. The sum of those round trips is what users call "a slow site". We explain how this latency arises, and the real ways to reduce it, separately in our guide to reducing server ping.
By the same rule, a VPS outside Iran is the right choice when at least one of these three conditions holds for your project:
- You have an international audience. A store that sells to Europe, a site for Persian speakers living abroad, or a product with users around the world. For these visitors, a VPS in Europe or the US plays exactly the role that a server in Iran plays for users inside the country: a short route and a fast response.
- You need direct access to global services. Calling foreign APIs, pulling images from Docker registries and packages from npm, sending transactional email with better deliverability, or connecting to other cloud infrastructure all have a shorter, more stable path from a server in Europe than from one in Tehran.
- You run a multi-region architecture. One node in Iran for domestic users and one in Germany for the rest of the world: many serious services keep exactly this combination and split traffic between the two regions with DNS.
To be honest about the other side of the coin: for a visitor inside Iran, a foreign server always has higher latency than a domestic one, and that latency also fluctuates when international routes are busy. If most of your traffic comes from inside the country, a server in Iran is the technically better choice. If your audience is mixed, caching and optimization, along the lines of our guide to speeding up WordPress, close only part of that gap, not all of it.
There is an even earlier question: do you need a VPS at all? If you only have one site with ordinary traffic and running a server would be an extra burden, shared hosting in a location abroad gives you the same result with far less hassle; we draw the line between the two in our comparison of shared hosting and a VPS.
What to check before you buy a VPS outside Iran
1) Datacenter location: the point closest to your audience
"Abroad" is not a single point; it is a map, and a wrong choice on that map wipes out the whole benefit of moving. For audiences in Europe, the Middle East and North Africa, Germany and Finland are the sensible starting points; for users in the Americas, a US datacenter; and for East and Southeast Asia, Singapore. If you will manage the server yourself from Iran, don't worry: the latency of your management path only makes your SSH sessions feel a little slower and has nothing to do with how fast the site is for its end users.
We have measured the real numbers behind this choice: the ping to all six Hetzner locations from inside Iran, their traceroute paths, and how their traffic and prices differ are in our comparison of ping from Iran to servers in Germany, Finland, the US and Singapore.
2) KVM virtualization and NVMe storage
In the market for foreign servers, just as in Iran's domestic market, all sorts of things are sold as a "VPS", and some of them are containers: you get no kernel of your own, kernel modules cannot be loaded, and Docker, network tunnels and low-level firewalls run into trouble. The standard to insist on is full KVM virtualization: the output of systemd-detect-virt must be exactly kvm. For storage, what makes your database and site fast is random reads and writes on NVMe, not the advertised sequential-speed figure. Fortunately, both claims can be verified in ten minutes, and we show how further down.
3) Understand the traffic model before you buy, not after the bill
Traffic is the main hidden cost of foreign servers, and three questions make it transparent. How much is included in the plan? Which direction is counted: outbound only, or both? And what happens once the allowance runs out: is the service cut off, slowed down, or charged per gigabyte? You should have all three answers in writing before you buy. We explain the difference between bandwidth and traffic volume, and how to measure real usage, in our VPS bandwidth guide; the same tools work on a foreign server too.
4) Hourly or monthly billing?
A short-term project (a test, a demo that runs for a few days, a temporary processing job) turns out expensive on a monthly rental, and so does a long-running project on a fixed rent that has nothing to do with what it actually uses. There is a third model: hourly billing based on actual usage, where you pay hour by hour and only for the time the server exists. The break-even formula, and the usage patterns for which hourly billing pays off, are in our guide to hourly servers, and the general criteria for choosing a configuration (CPU, RAM, disk) are in our VPS buying guide; both apply whether the server is in Iran or abroad.
Why are Hetzner datacenters a popular choice for a VPS in Europe?
When we talk about a Hetzner server, we are talking about one of the best-known names in European infrastructure: a German company with close to three decades of history that has built and runs its own datacenters (Nuremberg and Falkenstein in Germany, Helsinki in Finland) and also has locations in the US and Singapore. Hetzner's reputation in the developer community rests on two pillars: its price-to-performance ratio, and hardware and networking that need no sales pitch (current-generation CPUs, NVMe storage and stable connections to Europe's major networks).
For a project whose audience is in Europe and the Middle East, Germany and Finland are almost always the first choice; the US and Singapore make sense when your users really are there. We deliberately quote no prices or plan specifications here, because those figures change over time; you should see the exact numbers for each configuration at the moment you order.
But this is exactly where the big obstacle for users in Iran appears: signing up directly requires an international card and identity verification, and that is the subject of the next section.
The payment problem: a foreign server without an international card
Because of sanctions, international card networks such as Visa and Mastercard do not operate in Iran, and Iranian bank cards work only inside the country. To buy directly from foreign providers, a user in Iran therefore has three options, and all three are costly. You can try to obtain an international card in your own name through some workaround, which in practice is out of reach. You can open an account with a borrowed card and borrowed documents and accept the risk that, at the first identity check, the account is closed and every server and all your data are lost, usually with no time to migrate. Or you can buy through private middlemen and tie the ownership of the server, and every future payment, to one individual's good faith.
The fourth way is a different model: an Iranian provider that itself holds the contract for the foreign infrastructure and resells its capacity for payment in Toman. Paying in Toman means paying in Iranian currency from a prepaid wallet that you top up through Iranian bank gateways (the Toman is the everyday unit of Iran's currency; 1 Toman = 10 rials). The financial relationship with the foreign datacenter is the provider's problem, not yours; you deal with one Iranian provider, its panel, a Toman wallet and support in Persian. Mehran Host's "International servers" service is built on this model: the server is created in Hetzner datacenters (Germany, Finland, the US or Singapore), but ordering, payment and management happen in the same panel, from the same Toman wallet, that run Mehran Host's Iran cloud servers.
Know the billing model precisely, before it catches you out
International servers are billed by the hour: for every hour the server exists, its cost is deducted from your wallet. In practice, a server that lived for three days and was then deleted costs only those three days. The monthly figure you see when ordering is an estimate based on that day's exchange rate; because the price is calculated at the daily rate, a change in the exchange rate also changes the month's cost. Traffic has a set allowance included in the plan, and anything above it is charged only for outbound traffic, per gigabyte; you see the exact allowance and the overage rate when you order.
What happens to the server when the money runs out is also defined in advance, and you should know it: if your wallet stays empty, the server is first powered off and suspended, and if no top-up arrives, it is permanently deleted at the foreign provider after a set number of days. The policy is not hidden and its logic is simple (a machine that exists in a foreign datacenter generates a cost in foreign currency every hour), but in practice it leaves you with two rules: keep enough in your wallet to cover the monthly estimate, and always keep a backup of critical data somewhere other than the server itself.
After delivery: security first, then quality checks
A new server in a large, well-known datacenter becomes a target within its first minutes for automated scanners that sweep entire IP ranges looking for open SSH ports and weak passwords. Four tasks in the first hour make most of these opportunistic attacks useless:
# Update the system and create a non-root user
sudo apt update && sudo apt -y upgrade
sudo adduser deploy && sudo usermod -aG sudo deploy
# Key-only SSH login — run this from your own computer
ssh-copy-id deploy@SERVER_IP
# Disable password login — files in sshd_config.d take precedence over the main sshd_config
echo 'PasswordAuthentication no' | sudo tee /etc/ssh/sshd_config.d/10-hardening.conf
sudo systemctl restart ssh
sudo sshd -T | grep -i passwordauthentication # should print: passwordauthentication no
# Firewall with the fewest possible open ports
sudo ufw allow OpenSSH
sudo ufw allow 80,443/tcp
sudo ufw enableThis is the acceptable minimum, not the whole story; the full version, from fail2ban and automatic updates to the basics of looking after your keys, is in our Linux server security guide.
The second step is to verify what you have been given. The same tests we wrote for servers in Iran (steal time with vmstat, real disk throughput with fio, KVM detection with systemd-detect-virt and route quality with mtr) work unchanged on a foreign server; the commands and the pass threshold for each are in our server quality test guide. Just run the network test from your audience's point of view: if your users are in Europe, measure ping and route from a European location, not only from your own home connection in Tehran.
If the new server cannot be reached from inside Iran, first find out whether its IP is blocked by Iran's internet filtering or the problem lies elsewhere; we describe testing from inside and outside Iran at the same time, and replacing the IP from the panel, in our guide to checking whether a server IP is blocked in Iran.
Finally, move your domain: point the A and AAAA records at the new IP, lower the TTL before the migration so the change propagates quickly, and don't forget the email records. Each record is explained in full in our DNS records guide.
Decision checklist: eight questions before you buy a foreign server
Write down your answers to these eight questions before you pay. Any row whose answer stays vague is the part of your purchase that will cost you later:
| Question | Why it matters | An acceptable answer |
|---|---|---|
| Where are most of your end users? | The distance between server and user sets the latency of every click | Outside Iran → a foreign server; inside → a server in Iran; mixed → two servers |
| Which location? | "Abroad" is not one place; a wrong choice wipes out the benefit of moving | Europe and the Middle East: Germany or Finland; the Americas: the US; East Asia: Singapore |
| What is the virtualization? | A container has no kernel of its own and limits Docker and kernel modules | KVM: systemd-detect-virt prints exactly kvm |
| What type of disk? | A database lives on fast random reads, not on the advertised sequential speed | NVMe, with a figure you have confirmed yourself with fio |
| How is traffic counted? | It is the main hidden cost of foreign servers | A set allowance, outbound-only counting, and a published overage rate per gigabyte |
| What is the billing model? | Monthly billing is expensive for a short project | Hourly and based on actual usage: only for the hours the server exists |
| How do you pay? | A foreign account opened with borrowed documents risks closure and data loss | Payment in Toman from a wallet, with a clear, itemized transaction history |
| What happens if your wallet runs empty? | The fate of your data is tied to this policy | A published grace period before deletion, plus an off-server backup from day one |
Next step
A VPS outside Iran is neither a replacement for a server in Iran nor its rival; it is a different tool for a different audience. If your project has international users or connects to global services, take the criteria in this guide and put them to a practical test: in the Mehran Host panel, create an international server in a Hetzner datacenter (paid in Toman from the same wallet, billed by the hour), test it for a few days, and if you are not convinced, delete it. You also see the exact price of each configuration and its traffic allowance right there, before you confirm the order.
Frequently asked questions
What kinds of projects is a VPS outside Iran the right choice for?
A VPS outside Iran suits projects whose users are outside the country, or that need direct, stable access to global services such as APIs, software repositories and email infrastructure. The general rule is that a server should sit close to its end users, so if most of your visitors are inside Iran, a server in Iran gives lower latency and is the better choice. Multi-region projects usually combine the two.
Why are Hetzner datacenters a popular choice for a VPS in Europe?
Hetzner is popular for its price-to-performance ratio and its stable European hardware and network, which have made it one of developers' default choices for a cloud server in Europe. It builds and runs its own datacenters in Germany (Nuremberg and Falkenstein) and Finland (Helsinki), and also has locations in the US and Singapore. For projects with an audience in Europe and the Middle East, Germany and Finland are the sensible starting points.
How can I buy a server outside Iran without an international card?
The low-risk route is to buy from an Iranian provider that itself holds the contract for the foreign infrastructure and sells its capacity for payment in Toman. Mehran Host's "International servers" service works this way: the server is created in Hetzner datacenters, but you order and pay from the Toman wallet in your panel, with hourly billing based on actual usage. Opening a foreign account directly with a borrowed card or borrowed documents risks having the account closed and losing your servers and data.
Does a server outside Iran stop billing when I power it off?
No. On international servers, as long as the machine exists, whether on or off, its resources and IP address stay reserved at the datacenter and the billing meter keeps running. To stop the cost completely, you have to delete the server. If your wallet stays empty, the server is first powered off and suspended, then permanently deleted after a set number of days, so always keep a backup of important data outside the server itself.
What should I do first after my VPS outside Iran is delivered?
In the very first hour, update the operating system, create a non-root user, enable SSH key login and disable password login, and bring up a firewall with as few open ports as possible. New servers in large datacenters are targets for automated scans from their first minutes, and these four steps defeat most opportunistic attacks. Once the server is secure, verify the quality you received with a few ten-minute tests: steal time, real disk throughput and network route quality.