Moving a VPS to another host without downtime

When you change hosts, your server gets a new IP address, and that is the main thing to plan around. There will be no downtime if the new server is ready and tested before the switch, the data is synced in advance, and the old server keeps accepting requests for a while. Below: the order of steps, the timing, and what most often breaks during a move.

Updated 14.11.2026 · Find a VPS for your needs →

The short answer. You set up the new server alongside the old one, copy the data over and test it while the site keeps running on the old server. On moving day you stop writes for a few minutes, copy the last changes and point DNS at the new address. For another week the old server forwards requests to the new one, so nobody lands on a stale copy.

Why your IP address will not move with you

IP addresses belong to the host: it gets them in blocks from a regional internet registry and lends them to customers. Only a company with its own address blocks and its own autonomous system can take its addresses along, and that never applies to an ordinary VPS. So everything rests on DNS: visitors and services find the server by name, and the move is the moment the name starts pointing to the new address. Within one host an address can be moved between your own servers (a floating IP, see Floating IP and Load Balancer), but it will not move to another host.

Before the move, find the places where the old IP is written directly rather than through a name:

  • allowlists at partners, payment systems and banks, IP-based access to other companies' APIs — warn them in advance, they may need several days;
  • the domain's SPF record if the server sends mail, and the reverse PTR record, which the new host sets up;
  • the server's own settings: configuration files, environment variables, firewall rules, database connections by address;
  • monitoring and external uptime checks.

The move, day by day

WhenWhat to do
2–3 days beforeLower the TTL of the domain's records to 300 seconds. Order the new server and list everything that runs on the old one.
1–2 days beforeBuild the new server, copy the files in a first pass, start the database copy. Test the site on the new server through the hosts file.
Moving dayStop writes, copy the remaining changes, switch DNS, turn on proxying on the old server.
The week afterWatch the logs on both servers, restore the TTL, shut down the old server once requests stop reaching it.

TTL (time to live) is how long ISPs' DNS servers cache a record. If it is currently set to a day, lower it at least a day before the move; otherwise some visitors will keep going to the old address for another day. More on records and TTL in the article domains and DNS for server owners.

Disk image or a fresh build

There are two ways to get the same system on the new server. The first is to transfer the whole disk image. That works if the new host lets you upload your own image or install the system from your own ISO. In the accsly catalog on 14 November 2026 this is confirmed at 325 of 1,857 VPS hosts; see the selection VPS with custom ISO. After moving an image you almost always have to fix the network settings: the new host has a different address, gateway and sometimes a different network interface name.

The second way is to install the system from scratch and move only the data and settings. It takes longer but is cleaner: the clutter of years does not move with you, and you also prove that the server can be rebuilt from zero. If your applications already run in containers, this path is shorter: on the new server you just install Docker and copy over the compose files and data volumes.

Files: syncing in several passes

When run again, rsync transfers only the files that have changed. That is what makes a move without a long stop possible:

  1. First pass: everything, while the site is running. With hundreds of gigabytes it can take hours, and that is fine.
  2. Second pass: the day before or an hour before the switch. Only changes are transferred, usually in minutes.
  3. Final pass: after writes are stopped, with the --delete option, so that files deleted on the old server are also deleted on the new one. It takes seconds.

User uploads, cache and sessions live in different directories. You can skip the cache, but file-based sessions are lost in a move, and users will have to log in again. If that matters, move sessions to the database or Redis in advance.

Database: dump or replication

You cannot copy a running database like ordinary files: the copy will be inconsistent. There are two ways to do it.

A dump with a short write freeze. Suits databases of up to a few gigabytes. The site goes read-only or shows a "maintenance in progress" page, the database is exported, transferred and imported on the new server. Writes are down for as long as the export and import take, so time this in advance in a test run.

Replication. For large databases the new server is connected to the old one as a replica and catches up with all changes in real time. In PostgreSQL, logical replication is convenient for moving between servers because it works across different versions. According to the documentation, it does not carry the database schema, so you transfer that first with pg_dump --schema-only. Sequence values (the id counters) are not carried either, and you must set them by hand before the switch; otherwise new rows will get numbers that are already taken. MySQL and MariaDB use ordinary replication based on the change log. At switchover you stop writes on the old server, wait for the replica to catch up and point the application at the new database. Writes are down for less than a minute.

How to set up the databases themselves on a VPS is covered in the article PostgreSQL and MySQL on a VPS.

Testing before the switch

You can test the new server before changing DNS: add the domain with the new address to the hosts file on your computer and open the site. Walk through the key scenarios: logging in, placing an order, uploading a file, submitting a form. Make sure the application writes to the new database and does not reach the old one through an address in its configuration.

The certificate is a separate issue. Let's Encrypt validates the domain over port 80 at the address in DNS, so before the switch the new server cannot get a certificate that way. There are two ways out: copy the current certificate from the old server, or issue a new one through DNS record validation, which does not depend on where the domain points.

Moving day

  1. Stop writes: maintenance mode, stop queues and cron jobs on the old server.
  2. Run the final rsync pass and the final dump, or wait for the replica to catch up.
  3. Start the application, queues and cron on the new server. Scheduled jobs must not run on two servers at once, or emails will go out twice and reports will be calculated twice.
  4. Change the A records (and AAAA records if you have IPv6) to the new addresses.
  5. On the old server, configure the web server to forward all requests to the new one. Visitors who still have the old address cached will reach the new server and will not write anything to the old database.

With a TTL of 300 seconds, most traffic moves to the new server within a few minutes. The rest, from software and ISPs that keep records longer than they should, keeps arriving at the old server for several days and is forwarded on.

Mail

If the server handles mail, the MX record is changed the same way as the A record. No mail is lost: a sending server that cannot reach the recipient keeps retrying, and under RFC 5321 it should not give up for at least 4–5 days. Mailboxes are moved with the same rsync or over IMAP. Before the switch, add the new address to SPF and ask the new host to set up PTR; otherwise mail from the new server will start landing in spam.

How long to keep the old server and how to roll back

Keep the old server running for at least a week. As long as it is up and its data is intact, a rollback means restoring the A records and stopping the new server. If new orders or messages have already arrived on the new server, they have to be moved back, so it is better to decide on a rollback within the first hours. Before shutting the old server down, make a final copy of it to separate storage; for the difference between a host snapshot and a backup, see the article snapshots and backups.

A week of running two servers costs money, and hourly billing helps here: in the accsly catalog it is confirmed at 159 VPS hosts; see the selection VPS with hourly billing. With hourly billing you can do a trial move on a new server, rehearse the switch and delete the server, paying only for the hours used. How to end the contract with your old host and get the remaining balance back is covered in the article how to leave a host without losses.

FAQ

5 questions with answers

Can I move a VPS to another host with no downtime at all?

For reads, yes: the old and new servers run in parallel for a while, and visitors do not notice the switch. Writes are usually stopped for a few minutes to transfer the last file and database changes. With database replication this pause shrinks to a minute or less.

Will I keep my IP address when moving to another host?

No. Addresses belong to the host, so the new server will have a new IP. The switch is done by changing DNS records, and every place where the old address is written directly (allowlists, SPF, application settings) must be updated in advance.

How far ahead should I lower the TTL before a move?

At least as far ahead as the current TTL: if it is a day, lower it to 300 seconds at least a day in advance. Then at the moment of the move, ISPs' DNS servers will keep the old address for no more than five minutes.

How do I move a large database without stopping it?

Connect the new server as a replica of the old one: logical replication in PostgreSQL, ordinary replication in MySQL and MariaDB. The replica keeps up with changes in real time, and at switchover writes stop for seconds. In PostgreSQL the schema and sequence values are transferred separately.

How long should I keep the old server after the move?

About a week. All that time it forwards requests to the new server and remains your rollback point. Shut it down once requests stop showing up in its logs, and after a final backup.

Plans on this topic

VPS for a websiteVPS for an online storeVPS for a databaseVPS with instant setupVPS with a money-back guaranteeBest cloud VPS with hourly billing 2026

More in the guide

  • Windows VPS for 1CA rented server for 1C saves you from the office PC under a desk that nobody updates or backs up. But 1C on a VPS has its own quirks: the software licence is tied to the parameters of the virtual machine, users need both 1C and Windows licences, and core speed matters more than core count. Here is how to put together a 1C server for a small company.
  • Scheduled jobs on a VPS: cron and queuesAlmost every project has work that runs without a user: a nightly export, a mailing, cleaning up old data, processing uploaded files. Here is when cron is enough, when you need a queue and what to set up so jobs are neither lost nor run twice.
  • Kubernetes or Docker Compose on a single serverKubernetes is often installed «for growth» while the whole application lives on one VPS. Here is what it gives on a single server compared with Docker Compose, how many resources it eats itself and when moving to a cluster is really justified.
  • A server for a Telegram Mini AppA Mini App is a web app that opens inside Telegram: a shop, a booking form, a game or a customer account. From the outside it is a bot with a button; inside it is an ordinary website with an API and a database. Here is which parts need a server and which VPS to take.
  • GPU server: which card for which jobYou choose a server GPU by its video memory first and its speed second. If the model or scene does not fit in the card's memory, the server will not do, however fast it computes. Below: which jobs run on which cards, how server cards differ from gaming ones, and what a month of each costs according to the accsly catalog.
  • Hosting for 1C-Bitrix1C-Bitrix, a CMS widely used in Russia, can run on ordinary shared hosting as long as the host passes the developer's check. But Bitrix is heavier than most CMS: it needs recent PHP and MySQL, cron jobs and enough script execution time for exchange with 1C. Below: what to check with a host before paying, what "Bitrix" plans offer and when to go straight for a VPS.
  • Hosting for a landing page or business card siteA landing page or a business card site does not need a powerful server or a VPS: the simplest shared hosting plan for a few dollars a month is enough. What matters more is that the plan includes free SSL, the domain stays yours and the page opens quickly on a phone. Below is how to choose a plan, what to check in it and what it costs.
  • Hosting for an online school and videoAn online school has three different loads: a website with student accounts, recorded lessons and live classes. Keeping everything on one server is usually a bad deal — video eats the bandwidth the website needs. Here is what goes where and how to size the server.
  • Paying for hosting by invoice as a Russian company: documents and VATCompanies and sole proprietors registered in Russia pay for a server from their bank account, and the accountant needs documents to book the expense. Here is what the host must send, when the invoice includes VAT and what changes if the host is foreign.
  • A server for n8n and automationsn8n is an automation platform you can install on your own server: workflows connect a CRM, email, spreadsheets, bots and AI model APIs. n8n itself is undemanding, but without a couple of settings the server eventually runs out of memory or disk. Here is which VPS to take and what to configure right away.
  • A host's plan grid: vCPU, fair use and burstMost hosts arrange their plans in a grid: several plan lines, each with resources growing in steps. The same "2 vCPU" means different things in different lines: in one it is a share of a core split with neighbours, in another the core is yours alone, and in a third it is the right to a short burst. Here is how to read the grid and what to check before you pay.
  • IPv6-only VPS: savings and limitationsA host buys or leases each IPv4 address, so a server with IPv6 only is usually cheaper — by a dollar or two a month. But such a server cannot see part of the internet, and users without IPv6 cannot connect to it. Here is where the saving makes sense and what to check before you pay.
  • S3 object storage at hostsAlmost every cloud host offers S3 object storage: files go into a bucket over HTTP, and you pay for the gigabytes stored, requests and traffic. It does not replace the server's disk, but it is convenient for backups, website media and archives. Here is how to choose a storage service, compare it with a storage VPS and avoid losing data.
  • Mail on your own domain: hosting or a separate serviceThere are three ways to get an address like info@yourdomain.com: the mail already included in your hosting plan, a separate business mail service or your own mail server on a VPS. They differ in price, in how reliably messages get delivered and in what happens to your mail when the website moves. Below: how to choose and how to set up DNS so that the website and mail can live in different places without trouble.
  • WordPress hosting: what mattersWordPress runs on almost any shared hosting, so the choice seems easy. But the plan decides how fast the site opens, whether it gets security fixes and whether you can bring it back after a plugin update goes wrong. Below: what WordPress requires, what to check in a plan, what it costs and when shared hosting is no longer enough.
  • ARM servers: who benefitsARM processors have long since moved beyond phones: cloud hosts offer VPS on Ampere Altra and Microsoft Cobalt 100, and there are dedicated servers with 80 and 128 cores. Below: how an ARM server differs from the familiar x86, whether it is always cheaper, who can switch at no cost and who is better off staying on Intel and AMD.
  • How to read a dedicated server configurationA dedicated server plan fits everything into one line: "Xeon E5-2680 v4, 128 GB, 4 TB SSD RAID-10, 1 Gbps". But lines that look the same mean different things at different hosts. Below: what stands behind each part of the configuration, where hosts write something other than what you expect, and what to clarify before you pay.
  • RAID on a dedicated server: 1, 10 or noneAlmost every dedicated server comes with two or four disks, and the host asks how to set them up. This decides whether the server survives a disk failure, how much space is left for data and how fast the database will run. Below: which RAID level suits which task, how software RAID differs from hardware RAID and what to check right after the server is delivered.
  • Floating IP and load balancer: when you need themA floating IP and a load balancer come in when one server is no longer enough, either for reliability or for capacity. Both tools only work with two or more servers. Below: how they differ, what downtime they remove, what you need to change in your application and what they cost at hosts in the accsly catalog.
  • Snapshots vs backups: what's the differenceSnapshots and backups are often confused, and hosts list them on the same line of a plan. They are different tools. A snapshot quickly takes a server back an hour after a failed update. A backup brings your data back when the server, the disk or the account is already gone. Below: how they differ, what each protects against and how to combine them on one VPS.
  • Hourly GPU rental: how to calculate the costAn hour of a GPU server costs from about $0.73 for an L4 or RTX 4090 to $3.30 for an H100, if you divide the monthly price by 730 hours. Hourly billing pays off for training, experiments and one-off jobs lasting a few days. For a server that runs all month it is almost always dearer. Below: the formula, four worked examples and the charges people forget.
  • Your own language model on a server: how much memory and GPU you needAn 8-billion-parameter model compressed to 4 bits takes about 4 GB and fits any server card; at a slow pace it even runs on a CPU. A 70-billion model with the same compression needs 35 GB for the weights plus memory for the context, so a 48 GB card. Below: how to calculate memory for your model, which card for which size, and what it costs.
  • VPS for a Telegram bot: what the bot needs and how to pick a planA bot with a menu and a few commands runs fine on the cheapest server, while a bot with broadcasts, files and a database hits completely different limits. Here is what a bot really consumes, which Telegram limits shape the choice of server and how to avoid overpaying.
  • Hosting for a company website and domain mailA company website rarely gets heavy traffic, but it comes with staff mail on the domain, lead forms with personal data and an accounts department that needs invoices. Shared hosting covers all of this in one plan, provided you check the mail limits in advance, set up SPF, DKIM and DMARC and choose a host that works with companies. Below is what to look at and what it costs.
  • How to choose hosting for an online shopA small shop on WooCommerce, OpenCart or 1C-Bitrix runs fine on a good shared hosting plan. Its requirements are stricter than those of a business card site, though: recent PHP and database versions, HTTPS on every page, headroom in the limits for sales and backups from which orders can be restored quickly. Below is what to check in a plan, what it costs and when it is time to move to a VPS.
  • A database on a VPS: PostgreSQL or MySQLA database is almost never limited by the processor; memory and disk are what hold it back. If the working set fits in the cache, queries are fast even on an inexpensive server; if it does not, disk speed decides everything. Here is how to choose between PostgreSQL and MySQL, how much memory to give the database, which disk to pick and how to avoid losing data.
  • File storage on a VPS: disks and object storageA project's files, such as user uploads, product photos, videos, documents and archives, grow faster than the database and the code. You can keep them on the server's disk, on a separate volume or in object storage, and the choice determines the price per terabyte, the speed and what happens to the files when you change servers. Here are the options and prices according to the accsly.io catalog.
  • How to leave a host without losing anythingPeople leave hosts for all sorts of reasons: prices went up, the server got slow, support stopped answering, or you need a different country. During a move you can lose data, emails, your domain and the money for months already paid. Here is an order of steps in which the old and new servers run side by side for a while, so that switching off the old one breaks nothing.
  • CI/CD on your own VPSA dedicated build server pays off when hosted CI minutes run out, builds are slow or jobs need access to internal resources. But a runner executes any code in the repository, so a mistake in its setup exposes the production server and every secret. Here is how GitLab and GitHub runners work, what resources they need, how to deploy over SSH and where to keep the keys.
  • Server logs and login auditingLogs answer three questions: what broke, who logged in to the server and what they did there. You only get an answer if logging is enabled, the logs are kept long enough and they are not stored only on the server that may have been compromised. Here is where to find logs on Linux, which commands show logins, how to set up rotation and what to do in advance so that there is something to investigate after an incident.
  • VPS for developers: staging environmentsA staging environment exists so that you find the bug before your customers do. It should match the production server in software and configuration, but it can have half the resources and live for just a few days. Here is how to keep staging cheap, how to run several versions on one server and how to make sure a copy of the site does not end up in search results or send emails to real customers.
  • Linux distributions for a server: Ubuntu, Debian, AlmaLinuxFor a server, the choice is most often between three free distributions: Ubuntu, Debian and AlmaLinux. All three are stable and suitable for a website or a bot; they differ in how long they are supported, in their packages and in which panels and programs officially run on them. According to the accsly.io catalog as of November 2026, all three images are offered by 631 of the 1,241 hosts whose template list is known.
  • Load testing a website before launchA load test answers two questions: how many visitors a site can handle on the chosen server and what breaks first. It is run on your own server and only there: the load generator is a separate machine, the host has been notified and external services are replaced with stubs. Here are the numbers to watch, the tools that produce them and how to use them to choose a plan.
  • Updating a server without downtimeA server must not be left without updates, yet every update risks taking the site down. The risk is managed with a process: small security fixes are installed automatically, major changes follow a plan with a snapshot, testing and a ready rollback, and reboots are grouped into a maintenance window. Here is how to set this up on a single VPS.
  • CDN: when a website needs oneA CDN stores copies of a site's files on servers around the world and delivers them to each visitor from the nearest one. This speeds up loading of images, scripts and video and takes load off your server, but it does not make a slow CMS faster and does not replace choosing the right country for your server. Here is when a CDN is really needed and when a single VPS in the right place is enough.
  • Domains and DNS for a server ownerYou can switch servers in an evening, but a domain stays with a project for years. Through DNS, the domain points to your server, your mail and third-party services, and a single wrong record can take the site offline or send your emails to spam. Here are the records a VPS owner will need, how caching works, where to keep the zone and how to move to a new server without visitors noticing.
  • SSL certificates: free and paidA free certificate encrypts the connection just as reliably as a paid one: browsers make no distinction between them in terms of security. The difference lies in what the certificate authority checks, how long the certificate lasts and who is responsible for renewing it. According to the accsly.io catalog as of November 2026, free SSL is explicitly listed in 1,449 shared hosting plans from 178 hosts. Here is when that is enough and when a certificate is worth paying for.
  • 152-FZ and hosting: where to store the dataIf a website or service collects personal data of Russian citizens, that data must be recorded and stored in databases located in Russia: this is Part 5 of Article 18 of Federal Law No. 152-FZ. For choosing a VPS, this means the data centre's country matters, not the host's, and copies abroad fall under separate rules. Here is what the law requires, what duties fall on the server owner, how it applies to companies outside Russia and which setups are used in practice.
  • GDPR and choosing a hostThe EU General Data Protection Regulation (GDPR) does not require data to be kept in the EU, but it does require a data processing agreement with the host and a lawful mechanism for any transfer of data out of the EU. According to the accsly.io catalog as of November 2026, 61% of VPS hosts have servers in the EU, but almost half of them are registered outside the European Economic Area. Here is why that matters and what to check in the terms.
  • Hosting provider jurisdiction: what it affectsEvery server has two countries: the one where the data centre stands and the one where the company renting it out is registered. According to the accsly.io catalog as of November 2026, these are different countries for 15% of VPS hosts. The first determines latency and the rules on where data is stored; the second determines the law of the contract, the court for disputes, the documents your accountant receives and whose authorities can request your data. Here is what each of them changes.
  • How to compare VPS prices: the price of a resource unitA plan's price tells you how much you will pay, but not how much you get for that money. According to the accsly.io catalog as of November 2026, a gigabyte of memory on a 1 GB plan costs a median $8.00 a month, while on a 4 GB plan it costs $5.00. Here is how to work out the price per vCPU, per gigabyte of memory and of disk, and what to bring to a common basis before you compare two offers.
  • SLA and uptime: what hosts promiseAn SLA of 99.9% allows a host 43 minutes of downtime a month, 99.99% about four. But a percentage in an advert is not yet a commitment: the commitment is the document that says what counts as downtime, what is excluded and how much you get back. Most often that is a discount on the next invoice, not money. Here is how to read such documents and how to check availability yourself.
  • Free trials and money-back guaranteesThere are two ways to test a server before paying for a month or a year: a free trial or a money-back guarantee. According to the accsly.io catalog as of November 2026, 11% of VPS hosts offer a trial and 36% a money-back guarantee. But at many of them the terms apply only to shared hosting, only to the first order or only to card payments. Here is what to check so that the guarantee actually works.
  • Cloud server or VPSA cloud server and a VPS are usually the same KVM virtual machine. The difference lies in what surrounds it: a cloud sells resources by the hour through an API and offers network disks, snapshots and ready-made services, while a classic VPS is a fixed monthly plan with a local disk and a traffic allowance. Here is which of this you actually need and what it costs.
  • Dedicated server or VPSA VPS is a slice of a physical server, a dedicated server is the whole machine. With 4 cores and 8–16 GB of memory a VPS costs almost half as much, with 4 cores and 32 GB the prices are equal, and with 64 GB on 8 cores or 128 GB on 16 cores a dedicated server in the catalog is a third cheaper than a virtual one. Here is what else changes besides the price: neighbours, guarantees, delivery time, hardware failures and remote management.
  • Shared hosting or VPS for a websiteShared hosting is a ready place for a site where the host looks after the server. A VPS is your own server where you set everything up. For a landing page or an ordinary WordPress site, hosting is enough and costs several times less. You need a VPS when the account limits are too tight for the site or when it needs software that hosting does not allow. Below is what each option includes, what it costs and a table to help you choose.
  • DDoS protection: what hosting providers actually give youEvery second host now lists "DDoS protection" in its plans. Behind that line there may be multi-terabit filtering, or only the right to take your address offline when an attack bothers the neighbours. Here is what protection is made of, how L3/L4 differs from L7, and how to tell from the contract what you are buying.
  • Mail server on a VPS: SPF, DKIM, DMARCInstalling Postfix or a ready-made bundle like Mailcow on a VPS takes an hour. Getting your mail into the inbox rather than spam is harder: mailbox providers look at the port, the server's address, its reputation and three DNS records. Here is what to check with the host before buying and how to set up SPF, DKIM and DMARC.
  • Server monitoring: uptime, load, alertsWithout monitoring you learn that the server is down from your visitors, and that the disk is running out when the database stops writing. A few checks from outside and a dozen metrics from inside are enough to see a problem before users do. Here is what to measure, where to run checks and how to do it for free.
  • How to read hosting plans: the hidden limitsA plan card shows cores, memory, disk and a monthly price. Yet two plans with identical numbers can cost different amounts a year later and behave differently under load. The difference lies in terms printed in small type, in the acceptable use policy, or only in the contract. Below are eight places worth checking before you pay.
  • IPv4 and IPv6 on a serverA typical VPS has one public IPv4 address and, if the host supports it, an IPv6 subnet. An extra IPv4 address almost always costs money, and the cheapest plans sometimes come without their own IPv4 at all. Here is where the shortage comes from, what you can do with IPv6 alone and which address settings a mail server needs.
  • Bandwidth and traffic: what 1 Gbps and unlimited really meanA server plan usually has two network lines: port speed and traffic volume. The first says how fast the server can send data, the second how much it can send in a month. They are linked by simple arithmetic, and once you know it, it is easy to see what "1 Gbps unlimited" actually offers and whether "5 TB" will be enough for you.
  • Docker on a VPS: getting startedDocker lets you run a bot, a website, a database and monitoring on one server without them getting in each other's way, and moving to another VPS comes down to copying a couple of files and the data. Installation takes five minutes; the real trouble starts later: database ports exposed to the internet, logs growing to tens of gigabytes and data that vanished along with a container. Here is how to avoid all of that from the start.
  • How to move a website from shared hosting to a VPSThe move itself takes a couple of hours; the mistakes usually happen around it: a forgotten cron job, .htaccess rules that nginx does not read, an AAAA record with the old address, or mail that disappeared along with the IP change. Below is the order of steps with commands and checks for a PHP and MySQL site.
  • Server control panels: ISPmanager, FASTPANEL, aaPanelA panel turns a VPS into the kind of dashboard you know from shared hosting: sites, databases, mail and certificates are set up with a few clicks instead of editing config files. The three panels most often installed on Russian and budget international servers are ISPmanager, FASTPANEL and aaPanel. They differ in price, memory requirements and how much of the server they take over.
  • Windows VPS: licensing, RDP and secure sign-inA Windows server costs more than Linux not only because of memory: the price includes a licence, and how it is arranged decides whether you are compliant and how many people can connect. An exposed RDP port is also the most common way such servers get hacked. Here are both topics.
  • When to move from shared hosting to a VPSA VPS does not make a site faster by itself: it gives you resources and freedom, and with them the job of running a server. Here is how to tell that hosting has become too small, when the problem can be solved without moving, and how to migrate a site so visitors notice nothing.
  • VPS backups: strategies and toolsOn a VPS, backups are your job, even if the plan says "backups included". We go through what exactly to back up, why a host snapshot is not enough, how to set up restic or BorgBackup in half an hour, and how to make sure you can actually restore from a backup.
  • First 10 steps after buying a VPS: securityBots start guessing passwords on a new server within minutes of it getting a public IP. Below are ten steps that close the most common holes in about an hour: commands for Ubuntu and Debian, the differences for AlmaLinux and Rocky Linux, and the checks that keep you from locking yourself out of your own server.
  • How to choose a country for your serverPut the server where your visitors are. For an audience across Europe, Germany, the Netherlands and Finland are convenient; for North America, the US East Coast. If you serve EU users, keeping the data in the EU makes GDPR simpler. Price hardly decides it: at the same host a server in Frankfurt, Amsterdam or New York usually costs the same, and only Asia and Australia are noticeably more expensive.
  • Hourly billing: when it pays offHourly billing pays off if you need the server for less than three weeks a month: for a test, a build, a one-off heavy job. At most hosts an hour costs exactly the monthly price divided by 730 hours, so over a full month you hardly overpay. The overpayment hides elsewhere: hourly plans are dearer on average, and for a server that runs all year, monthly billing or a year paid in advance usually comes out cheaper.
  • How much RAM and how many cores a website needsMost websites are fine with 2 GB of memory and one or two cores; a shop with thousands of products needs 4 GB and two cores. Memory matters more than cores: when it runs out, the site slows down or crashes, while an extra core without memory adds almost nothing. Below I show how to work out the memory for your site and how to see what it actually uses.
  • KVM or OpenVZ: which to chooseIn 2026 KVM is almost always the right pick: it costs a dollar or two more per month than OpenVZ, but everything runs on it, from Docker to Windows. OpenVZ makes sense in one narrow case, explained below, and at the end you will find the commands to check your own server in a minute.
  • NVMe or SSD: does it matter for a websiteFor a small site the difference between NVMe and SSD is barely noticeable, because pages are served from memory rather than from disk. It shows up in shops and sites with a large database. At the same host NVMe costs only about $0.50–1 a month more, and sometimes less, so what usually decides it is not the disk type but its size and how the host has limited it.
  • What is a VPS, in plain EnglishA VPS is a slice of a powerful physical server that you rent and that behaves like a separate computer, with its own operating system, its own IP address and full control. Below is how it differs from shared hosting, who needs one, what it costs and what to check right after you buy it.
  • How to test VPS ping and speed before you payThe numbers in a plan do not tell you the latency to your users or how fast the disk really is. Most of this can be measured before you pay, the rest in the first hour after launch. Here are the tools and how to read the results.
  • Corporate network on a VPS: remote access to the officeA rented server can become the hub of a company's private network: remote employees and branch offices connect through it to the ERP, file server, CRM and Git. Here are the common layouts, protocols, server requirements and security basics.
  • How to choose a VPS: the 7 specs that matterTwo plans with the same "2 cores, 4 GB, 50 GB" can differ several times in speed and twice in price a year later. Here is what stands behind each line of a VPS plan and what to check before you pay.
  • VPS vs VDS: is there a difference and what actually mattersIn most markets VPS and VDS mean the same thing: a virtual server. The difference that really affects your work is hidden not in the name but in the virtualization type and whether resources are guaranteed.