🚀
Hosting

Is it time to move from shared hosting to a VPS?

17.11.2026
← All articles

As a site grows, someone asks whether it should move to a VPS. A VPS does offer more freedom: your own OS, root access, dedicated resources and any software you like. It also moves updates, security, backups and monitoring from the provider to you. So the real question is not whether a VPS is better, but whether your project needs one and who will run it.

The core difference

Shared hosting is a ready environment: web server, PHP, database and mail are configured, and the provider maintains the server. A VPS starts with just an operating system and you install the rest.

CriterionShared hostingVPS
Server administrationProviderYou
Root accessNoYes
Long-running processesUsually restrictedAllowed
ResourcesShared limitsDedicated CPU, RAM, disk
Updates and securityProvider's jobYour job
Best forOrdinary sites, blogs, shopsComplex apps, custom software

When a VPS is genuinely needed

The clearest sign is software that shared hosting cannot run: an always-on Telegram bot, a WebSocket server, queue workers, Redis or custom Python and Node.js services that need a persistent process and their own port. The second sign is outgrowing the largest shared plan after caching, image compression, bot limiting and query tuning are already done. The third is needing server-level control, such as custom PHP or database settings, your own firewall rules or several projects under separate users.

When shared hosting is enough

For a company site, blog, landing page or mid-size WordPress shop, good shared hosting is often the sensible choice. Without someone who can run a Linux server, a VPS may reduce reliability: an unpatched system and missing backups are far riskier than shared limits. Sometimes the right answer is simply a bigger shared plan.

Example: a delivery service in Samarkand

A food delivery service in Samarkand ran misol.uz happily on shared hosting until it added a Telegram bot for orders and a live courier map over WebSocket. Both need persistent processes, which shared environments are not built for. The site, bot and WebSocket service moved to one VPS, each running as a systemd service with automatic restart.

Prepare the server first

Update the system, work as a separate sudo user, enable a firewall and automatic security updates. On Ubuntu, this sets up Nginx, MariaDB and PHP-FPM:

sudo apt update && sudo apt upgrade -y
sudo adduser deploy
sudo usermod -aG sudo deploy
sudo apt install -y nginx mariadb-server php-fpm php-mysql unattended-upgrades
sudo ufw allow OpenSSH
sudo ufw allow 'Nginx Full'
sudo ufw enable

Then disable SSH password login and set up backups stored off the server.

Migrating without downtime

A day or two ahead, lower the DNS TTL to about 300 seconds. Copy files and the database, ideally with mysqldump and rsync over SSH.

# on the old hosting: dump the database
mysqldump -u dbuser -p --single-transaction misol_db > misol_db.sql

# on the VPS: pull files and the dump
rsync -avz user@eski-server:www/misol.uz/ /var/www/misol.uz/
rsync -avz user@eski-server:misol_db.sql ~/

# on the VPS: create the database and import
sudo mysql -e "CREATE DATABASE misol_db CHARACTER SET utf8mb4;"
sudo mysql misol_db < ~/misol_db.sql

Test the new server by temporarily adding the domain to your local hosts file, so only you see the new copy.

# temporarily in the hosts file on your computer
198.51.100.20  misol.uz www.misol.uz

When everything works, point the A record to the new IP, issue the SSL certificate on the VPS and pick a quiet hour or a short maintenance window. Keep the old hosting for a few days as a fallback.

Ongoing duties

After the move you own updates, monitoring, backup checks and log rotation, or you need a specialist who does. You can order and manage a VPS in the sayt.uz cabinet, where your domain and DNS settings also live, so changing the A record takes minutes. Move for a concrete technical reason and the VPS will genuinely strengthen your project.

Related articles

💾 Swap on a VPS: do you need it, how much, and how to set it up 🗂️ Working with the ISPmanager File Manager: Uploads, Archives, Editing and Permissions ⏱️ 504 Gateway Timeout: what causes it and how to fix it step by step 📜 Hosting SLA Explained: Uptime Guarantees and Compensation
🌐 Language
🇺🇿 O'zbek 🇺🇿 Ўзбек 🇷🇺 Русский 🇬🇧 English ✓