- A business card site, a blog or a small WordPress shop is fine on ordinary shared hosting, where the host looks after the server for you. A plan for one site with 2–10 GB of disk in Russia costs from $0.66 a month, and half of these plans cost less than $3.23, about $39 a year.
- You need a VPS when the site hits the limits of shared hosting or when you run something it cannot: Node.js, Python, Docker, Redis. To start, 2 cores, 2 GB of RAM and 30 GB of NVMe are enough.
- Such a VPS in Russia costs from $4.59 a month, and half of the plans cost less than $10.82, about $130 a year. But updating the system, making backups and fixing the server at night are now your job.
Plans under $1 are left out of this list. They often come with less than a gigabyte of disk or quote a monthly price that you can only get by paying for a whole year, and further down I will show how to spot them yourself.
Why a server in Russia? If your site has a contact form, a cart or sign-up, it collects personal data. Since 1 July 2025 the new wording of Article 18(5) of Russia's personal data law 152-FZ explicitly bans collecting Russians' data into databases abroad, and lawyers read it as a requirement to keep the whole processing chain inside the country. For a site that serves Russian customers, a server in a Russian data centre is simpler than proving later where the database lives. How Russian prices compare with other countries is in How much does a VPS cost in 2026: median prices in 20 countries.
What actually differs between hosting and a VPS
With shared hosting you rent a folder on a big server where hundreds of other people's sites live next door. The host maintains the system, updates PHP and the database and issues a certificate with one button. In return it caps how much CPU and memory your site may take, so that one heavy shop does not bring down the neighbours.
A VPS is your own virtual server. The cores and memory are reserved for you, and you can install anything, from a website to 1C for a small accounting team on a Windows server. But an empty server does nothing on its own: you set up the web server, PHP, the database, the certificate and the backups yourself, and you are the one who answers when something breaks.
| Shared hosting | VPS | |
|---|---|---|
| System, PHP and database updates | the host Done for you, you pick the PHP version in the panel | you An update command once a week and a move to a new Ubuntu release every couple of years |
| Backups | usually the host Many plans copy the site daily, check how long copies are kept | you A paid option from the host or your own script copying to another server |
| HTTPS certificate | the host A button in the panel | you One certbot command, then it renews itself |
| CPU and memory | Shared with neighbours, your site has a cap | Reserved by the plan, no process caps |
| What you can run | PHP, MySQL, scheduled jobs | Anything: Node.js, Python, Docker, Redis, queues |
| Median price in Russia | $3.23 a month for 1 site and 2–10 GB | $10.82 a month for 2 cores and 2 GB |
That leads to the main question to ask yourself before choosing a plan: who will fix the site if it goes down on a Saturday? If the answer is “nobody”, take shared hosting, even if a VPS sounds more serious.
Which kind of site do you have?
Two things decide it: what the site is built on and how many sites you have. Traffic matters less than it seems. A WordPress site with page caching easily serves thousands of pages a day from ordinary hosting, while a custom Node.js service simply will not install there.
Business card site, blog, landing page
One site on WordPress, a static export or plain PHP, up to a few thousand visitors a day.
- shared hosting
- 1 site
- 2–10 GB disk
- PHP 8.3+
- HTTPS in the panel
We downloaded a fresh WordPress 7.1: unpacked, it takes about 120 MB. Over time the space goes to images and backups, not to the engine itself. Two gigabytes will last a blog for several years. Five is plenty.
Look at the PHP version rather than the gigabytes. WordPress recommends PHP 8.3 or newer and MariaDB 10.11+ or MySQL 8.0+. A plan whose panel only offers old PHP 7 is already slower, and over time new plugins will stop working on it.
A shop or several sites
WooCommerce or another engine with a catalogue, or five to ten sites on one account.
- shared hosting
- 5+ sites
- 10–40 GB disk
- NVMe
- daily backups
For a shop the load cap matters more than the disk size. Every catalogue search and every cart runs PHP and database queries, and during a sale there are many times more of them than on a blog. So ask the host how many simultaneous processes the plan allows, and pick NVMe: a database answers faster on it than on a regular SSD.
If you have several sites, keep them on one plan with spare room in the site count. It is cheaper than five separate plans, but remember that if the account goes down, every site goes down with it.
Your own code or a heavy site
A service on Node.js, Python or Docker, a site with queues and Redis, or a shop that no longer fits into shared hosting limits.
- VPS
- 2 cores
- 2 GB RAM
- NVMe 30 GB+
- own IPv4
Two gigabytes is a sensible minimum for a web server, PHP and MariaDB together, with the database keeping the most frequent queries in memory. On one gigabyte such a server runs, but under load it starts swapping to disk and slows down. The second core keeps a heavy database query from stalling pages for everyone else.
If you would rather not work in a terminal, pick a plan with the ISPmanager or FASTPANEL control panel: they set up the site, the database and the certificate in a browser. Such plans are collected on the VPS for a website page.
Chart data
| Plan | Plans | Minimum | Quarter under | Median |
|---|---|---|---|---|
| Hosting, 1+ site, 2–10 GB | 106 | $0.66 | $1.92 | $3.23 |
| Hosting, 5+ sites, 10–40 GB | 100 | $1.20 | $3.63 | $5.44 |
| VPS, 2 cores, 2–3 GB, NVMe 30+ | 60 | $4.59 | $7.12 | $10.82 |
| VPS, 2 cores, 4 GB, NVMe 40+ | 93 | $3.61 | $12.51 | $15.29 |
I would aim for the dark part of the bars: up to $1.92 for one site and up to $3.63 for a shop plan. Above that you usually pay for site builders, mail for hundreds of mailboxes and a famous name, and the site does not get any faster. VPS prices work differently: very cheap 4 GB plans do exist, but there are only a handful, and they look more like a promotion than the norm.
When shared hosting is no longer enough
Many hosts limit sites with CloudLinux. It gives each account its own share of CPU, memory and simultaneous processes. While the site fits into it, you never notice the limits. When it hits them, visitors get an error instead of a page: CloudLinux says in its documentation that once the entry process limit is reached the server answers with code 508, and Plesk describes the same “Resource limit is reached” error.
It is time to think about a VPS if at least one of these happens:
- visitors or your monitoring see error 508, and the load graphs in the hosting panel hit the ceiling;
- the host has emailed you about excessive load or offered a more expensive plan;
- you need something a shared server cannot run: Node.js, Python, Docker, Redis, websockets for a chat;
- you need scheduled jobs more often than the host allows, or they run longer than its execution time limit.
Try the cheap option first. A page caching plugin and compressed images often cut the load several times over, and then the move can wait another year. If that does not help, a bigger hosting plan usually costs less than a VPS and gives you no extra work. Take a VPS when what stops you is not money but something shared hosting simply cannot do.
Where a plan lets you down
- “$1.56 a month”, but only for two years at once
Some Russian hosts quote the monthly price for a 24-month payment. A plan at $1.56 a month really costs $37.41 in one go, and if the site does not take off, you will not get the money back.
How to tell: the order form has no “1 month” term, and the shortest period is a year or two.
- The yearly discount and the renewal price
84 of the 305 Russian plans in the catalogue give a discount for paying a year or more ahead, usually about 20%. That is a fair saving if you compare it with the same plan's monthly price. But sometimes the first year is a promotional price and renewal costs more.
How to tell: look for the word “renewal” in the terms or the price list. If it is not there, ask support before you pay.
- A load cap the plan page does not mention
The plan page lists gigabytes and the number of sites, while the CPU and simultaneous process limits are tucked away in the rules. That cap is exactly what decides whether a shop survives a sale.
How to tell: look in the description for “CPU”, “processes”, “load”, “LVE” or “Entry Processes”. No numbers? Ask support for them.
- Old PHP and an old database
The cheapest plans sometimes live on an old server with PHP 7 and MySQL 5.7. WordPress will start there, but it will be slower, and new plugins will refuse to install.
How to tell: check the list of PHP versions on the plan page or during the trial. It should include 8.3 or newer.
- A server abroad for a site with forms
European hosting can be cheaper, but if the site takes orders, requests or sign-ups from people in Russia, the database holding that data must be in Russia. A breach means a fine, and you will be the one dealing with it, not the host.
How to tell: the plan description names the data centre city. “Hosting in Russia” on the shop window without a city is a reason to ask.
How to move a site to a VPS in one evening
The example below is for a PHP and MySQL site such as WordPress, moving to a VPS with Ubuntu 24.04. This release installs PHP 8.3 and MariaDB 10.11 from its standard packages, exactly what WordPress recommends. Do not cancel the old hosting until you are sure the new server works.
- Make a copy of the site on the hosting
You need two files: an archive of the site folder and a database dump. In the hosting panel these are the “Backup” button and phpMyAdmin, and over SSH it looks like this:
tar czf site.tgz -C ~/public_html . mysqldump -u USER -p DATABASE > db.sql - Lower the domain's TTL
A day before the move, set the time to live of the A record to 300 seconds in DNS. Then visitors will see the new server within minutes of the address change, not a day later.
- Update the VPS and install the web server
Log in to the server as root and install nginx, PHP and the database in one command:
apt update && apt -y upgrade apt -y install nginx mariadb-server php8.3-fpm php8.3-mysql \ php8.3-curl php8.3-gd php8.3-mbstring php8.3-xml php8.3-zip php8.3-intl - Create the database and load the dump
Use the same database name, user and password as on the hosting, and you will not need to change the site's settings.
mysql -e "CREATE DATABASE site; CREATE USER 'site'@'localhost' IDENTIFIED BY 'PASSWORD'; GRANT ALL ON site.* TO 'site'@'localhost';" mysql site < db.sql - Unpack the files and set up nginx
Copy the archive to the server with
scp, unpack it into/var/www/siteand give the folder to the web server user.mkdir -p /var/www/site && tar xzf site.tgz -C /var/www/site chown -R www-data:www-data /var/www/siteThen create
/etc/nginx/sites-available/site. The simplest working config for WordPress looks like this:server { listen 80; server_name example.com www.example.com; root /var/www/site; index index.php index.html; location / { try_files $uri $uri/ /index.php?$args; } location ~ \.php$ { include snippets/fastcgi-php.conf; fastcgi_pass unix:/run/php/php8.3-fpm.sock; } }Enable it and check that nginx accepted the settings without errors:
ln -s /etc/nginx/sites-available/site /etc/nginx/sites-enabled/ nginx -t && systemctl reload nginx - Test the site before changing DNS
On your own computer, add the new server's address next to the domain in the hosts file and open the site in a browser. Click through the home page, the admin login and checkout if it is a shop.
# Windows: C:\Windows\System32\drivers\etc\hosts, macOS and Linux: /etc/hosts SERVER_IP example.com www.example.com - Switch the domain and issue a certificate
Change the A record in DNS to the VPS address. Once the domain opens from the new server, issue a free Let's Encrypt certificate. It is valid for 90 days, and certbot renews it on its own.
apt -y install certbot python3-certbot-nginx certbot --nginx -d example.com -d www.example.com
Panel or terminal. If the commands above look alien, take a VPS with the ISPmanager or FASTPANEL panel: steps 3–7 are done with a mouse there. Without a panel the server is lighter and exposes nothing extra to the internet.
Backups. On shared hosting the host made them, on a VPS it is now your job. Dump the database and the site folder every night to another server or to cloud storage, or a disk failure will take the site together with its copies.
If your site has not outgrown shared hosting yet, have a look at our breakdowns of VPS prices in 2026 and cheap VPS plans for 100–300 roubles: they show what the next step will cost. All hosting plans with filters by number of sites, disk and panel are on the website hosting page, with separate selections for hosting in Russia and WordPress.
Prices come from hosting companies' websites, converted at the Central Bank of Russia rate. The live blocks refresh hourly and may differ from the text. Minimums and medians were calculated from the accsly.io catalogue on 10 November 2026: plans with servers in Russia, monthly price with monthly billing, no setup fee and no required prepayment for several months.