payless.host
Managed vs unmanaged VPS: what you take on yourself
Updated Nov 22, 2026
1. Decide how much work you want to do yourself
Managed VPS means the provider handles most server care. Unmanaged means you or your developer do nearly everything.
On a managed VPS from a provider like uPress, the price (for example, 90.00 USD/month for VPS plans with the same price at renewal) includes management tasks such as configuration help and SSL installation on their VPS offers. On an unmanaged VPS from many providers, you only pay for the server; setup and maintenance are your job.
What can go wrong - You underestimate the time and attention a server needs. - You assume “VPS” always means “managed support” and later find routine tasks are chargeable extras or not included.
How to check - Read the VPS page and look for the word managed and for specific services included, such as SSL help, backups, or migrations. - If the offer is unclear, open pre‑sales chat or a ticket and ask, in one message: “Is this VPS fully managed, partly managed, or unmanaged, and which tasks are included in the price?”
2. Understand what “managed” usually includes
Managed VPS typically includes help with the operating system, web server, control panel, and sometimes migrations.
DreamHost sells shared hosting and a VPS Business plan at 13.75 EUR/month, which renews at 31.99 after 12 months with a three-year total of 932.76 EUR. That higher ongoing price, compared to their shared Web Hosting Launch at 2.89 EUR/month renewing at 10.99, reflects that more is handled for you at the VPS level, even if the exact management scope still needs reading on their site.
What can go wrong - You assume software updates, malware recovery or email setup are covered when they are not. - You think “managed” means the provider monitors your application (such as your specific plugin) rather than the server.
How to check - Look for a list such as: OS updates, control panel updates, security patches, firewall configuration, backups, migrations. - If you cannot find a list, ask support: “Which of these are included without extra charge: OS updates, web server updates, database updates, firewall setup, monitoring, daily backups, malware cleanup?”
3. List what you must do on an unmanaged VPS
On an unmanaged VPS, you are normally responsible for:
- Installing the operating system (if it is not preinstalled).
- Securing logins (SSH keys or strong passwords).
- Setting up a firewall.
- Installing a web server and database.
- Installing SSL certificates.
- Configuring backups and monitoring.
- Applying updates over the life of the server.
A provider like uPress sells managed WordPress VPS from 90.00 USD/month on a flat price, and includes free SSL installation and a free SSL certificate on managed VPS hosting. Those items are included tasks you would handle yourself on an unmanaged server.
What can go wrong - You rent an unmanaged VPS and only later discover you are expected to configure all of the above. - Tasks are split: the provider will reinstall the OS, but not secure it, unless you pay extra.
How to check - Before ordering, ask: “On this plan, which of these do I have to do myself: firewall, SSL, backups, updates, migrations?” - If the provider sells both managed and unmanaged VPS, confirm which one you are selecting at checkout.
4. Step‑by‑step: securing a fresh unmanaged VPS
If you choose unmanaged, you or your developer will follow steps like these on day one.
Step 1 – Log in to the VPS The provider emails an IP address, username and either a password or SSH key.
What can go wrong: You cannot connect, or you connect as the wrong user. How to check: Run a simple command such as `whoami` and confirm it shows the expected user name from the provider’s email.
Step 2 – Change or lock down root access You disable direct root logins or change the initial password.
What can go wrong: Automated attacks try default or reused passwords. How to check: Log out and log back in using the new method (key or new password). Only move on once this works reliably.
Step 3 – Create a non‑root user for daily work You add a regular user and give it the ability to run admin commands.
What can go wrong: You stay logged in as root for everything, making mistakes more serious. How to check: Log in as the new user and confirm you can run a simple admin command (your provider’s docs will show an example).
5. Step‑by‑step: basic firewall and updates
Step 4 – Turn on a basic firewall Only allow the ports you actually use (for example, web and SSH or your control panel).
What can go wrong: You lock yourself out by blocking SSH or your panel; or you leave the firewall off entirely. How to check: After applying firewall rules, disconnect and reconnect. Confirm you can still log in and that a simple port scan tool only shows the ports you intended.
Step 5 – Apply system updates On unmanaged VPS, you run the package manager to fetch and install updates.
What can go wrong: You skip this step, leaving known issues unpatched; or an update restarts services unexpectedly. How to check: Run the update command until it reports no more updates. Then check your web server and SSH are still reachable by reconnecting and loading a simple page.
6. Step‑by‑step: installing a web stack and SSL
Step 6 – Install a web server and database You install software such as a web server and database from the provider’s repository or control panel.
What can go wrong: Services listen on the wrong IP, or the database is left with a blank or simple password. How to check: Visit the IP in a browser and confirm you see the default web server page. Log into the database admin tool with the new credentials you set.
Step 7 – Install an SSL certificate On unmanaged VPS, you install and renew SSL yourself. On managed plans, this may be handled for you.
Namecheap offers a Private Email free trial at 0.00 USD/month, renewing at 1.24 after 1 months with a three-year total of 43.40 USD; email hosting like this often sits behind an SSL‑secured connection managed on their side. On an unmanaged VPS, you configure that layer yourself.
What can go wrong: The certificate is installed for the wrong domain, or auto‑renewal is not set, causing browser warnings later. How to check: Visit `https://yourdomain` and click the padlock in the browser; confirm it shows your domain and a valid certificate chain.
7. Ongoing care: backups, monitoring, and growth
Over time you need backup routines, monitoring, and a plan for scaling up.
A provider like Vangus sells VPS plans such as VPS S at 470.00 ILS/month with the same price at renewal. The flat VPS price is one part; the ongoing work of watching resource use and planning upgrades is another.
Backups What can go wrong: You only enable on‑server backups, and lose both data and backups in a single incident. How to check: Restore a test file or small database from backup to confirm the process works and you know the steps.
Monitoring What can go wrong: You only find out about outages from visitors. How to check: Set an external uptime or port‑check service and confirm it alerts you once with a controlled test (for example, briefly stopping the web service during a maintenance window).
Scaling What can go wrong: You delay upgrades until the server is already slow or unresponsive. How to check: Watch RAM, CPU and disk graphs in your provider’s panel. When graphs sit near their limits for long periods, talk to the provider about the next VPS size or a managed plan.
8. Using managed services to reduce your task list
Managed VPS or managed WordPress moves many of these tasks to the provider.
uPress sells managed WordPress hosting from 15.00 USD/month and managed VPS offers from 90.00 USD/month, with the same price at renewal and deals such as a 30‑day free trial for managed WordPress and free SSL certificates on managed VPS hosting. On such plans, you still look after your website content and plugins, but the provider handles more of the server work.
DreamHost DreamPress 1 at 14.99 EUR/month, renewing at 19.99 after 12 months with a three-year total of 659.64 EUR, is another example of paying more than a basic shared plan in exchange for managed WordPress infrastructure.
What can go wrong - You pay for managed hosting but continue doing low‑level server tasks yourself out of habit, making life harder than it needs to be. - Or you assume *everything* is covered and do not read which parts of the stack still need your attention.
How to check - Ask support for a one‑line summary: “On this plan, what do you manage, and what remains my responsibility?” - Keep a short written checklist of what is on your side: content, plugins, theme updates, and any external services you use.
