Point DeployManage at a VPS from any provider and it takes over the management work: the stack, the certificates, the firewall, the databases, the mailboxes and the deploys. You keep root and you keep the cloud bill. This page covers what VPS management actually involves, where managed and unmanaged hosting really differ, and what a panel does and does not take off your plate.
# free plan · no credit card required
hetzner digitalocean aws ovhcloud vultr linode
VPS management is the ongoing work of keeping a virtual private server running: patching the operating system, configuring the web server, issuing and renewing TLS certificates, running databases, locking down SSH and the firewall, taking backups, and shipping code without downtime. On a managed VPS the host does most of that and charges for it. On an unmanaged VPS it is entirely yours. A management panel is the third option: you keep the cheaper unmanaged server and root access, and the panel automates the routine work through a browser.
Last updated August 2026
Connect DigitalOcean, Hetzner, AWS, Vultr, Linode or OVHcloud with an API key and build the box from the panel, or point it at a VPS you already own over SSH. The server is created inside your account, billed to you at provider rates, and you hold the root credentials the whole time.
Nginx, PHP with the version you pick per site, MySQL or PostgreSQL, Redis, Node and the supervisor that keeps queue workers alive. Managing a VPS by hand means owning every one of those config files. Here they are generated from settings you can read and override.
Let's Encrypt certificates are issued when you add a domain and renewed before they expire, with the reload handled for you. Expired TLS is one of the most common ways a self managed VPS takes a site offline, and it is entirely avoidable.
Open only the ports a site needs, manage authorized keys per user instead of sharing one root password, and keep separate isolated users per application so one compromised site is not a whole compromised server.
Add mailboxes and forwarding addresses for the domains already on the server, billed once instead of per user. Laravel Forge, Ploi, RunCloud and Envoyer do not manage mail at all, so this is usually the piece people are still paying a separate provider for.
Push to your branch and the panel builds the release in a fresh directory, runs migrations and asset builds, then switches a symlink so no request ever hits a half built application. If the release is bad, the previous one is still on disk and one click puts it back.
Buy an unmanaged VPS from whichever provider gives you the best price for the specs, or let DeployManage create one through your cloud account. Any Linux VPS you can reach over SSH works, and nothing about your provider relationship changes.
DeployManage installs and configures the web server, database, cache, queue supervisor and firewall, creates isolated system users, and hardens SSH access. What normally takes an afternoon of following a setup guide finishes while you get a coffee.
Point a domain at the server, add the site, and the certificate is issued automatically. Create databases, mailboxes and forwarders from the same screen instead of three different tools and a text editor over SSH.
Link the repository, pick a branch, and every push builds a new release and swaps it in atomically. Scheduled jobs, queue workers and daemons are managed from the panel, so a restart during a deploy does not leave a worker running last week's code.
The choice is usually framed as managed versus unmanaged hosting, which hides a third option most developers end up on. Prices below were read off the vendors' own pricing pages in August 2026 and change often.
swipe to see all columns →
| Unmanaged VPS with DeployManage | Managed VPS hosting | Unmanaged VPS, no panel | Hosting panel on a VPS | |
|---|---|---|---|---|
| Who patches the OS and stack | You approve, the panel runs the updates | The host does it on their schedule | Entirely you, over SSH | You, the panel does not patch the OS |
| Who holds root | You do | Usually the host, access can be limited | You do | You do |
| Whose account the server lives in | Yours, billed by your cloud provider | The host's, billed by the host | Yours | Yours |
| Cheapest verified entry price for 2 GB | DigitalOcean Basic at $12.00 per month plus the panel | Cloudways Micro at $11.00 per month, fully managed | DigitalOcean Basic at $12.00 per month | $12.00 server plus cPanel Solo at $29.99 or DirectAdmin Standard at $29.00 |
| Licence model | Flat panel fee across every server you connect | Billed per server, per month | No licence | cPanel meters by account, Plesk by domain |
| Git deployments with rollback | Built in, zero downtime with one click rollback | Varies by host, often manual or via Git only | You script it yourself | Not the panel's job, usually add Envoyer at $10 to $50 per month |
| TLS certificates | Issued and renewed automatically | Issued and renewed by the host | You run certbot and watch the renewals | Issued and renewed automatically |
| Mailboxes and forwarders | Included per domain, billed once | Usually included | Postfix and Dovecot, configured by you | Included per domain |
| Queue workers and scheduled jobs | Managed with supervisor from the panel | Sometimes, ask before you buy | Systemd or supervisor, written by you | Cron only, workers are your problem |
| Best fit | Developers and agencies who want control without the maintenance | Teams with no server skills and no wish to acquire any | People who enjoy this and have the time | Shared hosting resellers with tenant accounts to meter |
The $6 or $12 box looked like an obvious win against managed hosting until the certificate expired on a Sunday, the disk filled with logs, and an unattended upgrade restarted PHP FPM mid deploy. The saving is real, but only if something else absorbs the routine work.
Twenty clients on twelve servers across three providers is where per server management billing stops making sense. One panel across all of them, with isolated users per site and per domain mailboxes, keeps the fleet legible and the invoices flat.
You are good at shipping features and indifferent to nginx directives. Managed VPS hosting solves that by taking root away from you. A panel solves it by keeping root with you and making the routine work a button.
You need a specific PHP version, a Redis instance, a long running queue worker and a staging copy. Those are exactly the things a managed VPS plan tends to charge extra for or refuse outright, and exactly what an unmanaged box with a panel does without asking.
VPS management is everything that has to keep happening after a virtual private server is created. The provider hands you an IP address, a root password and a blank Linux install. From that moment the operating system needs patching, the web server needs configuring, TLS certificates need issuing and renewing, databases need creating and backing up, the firewall needs closing, SSH needs hardening, log files need rotating before they fill the disk, and application code needs getting onto the box without taking it offline.
None of that is optional and none of it is done for you on an unmanaged plan. The phrase covers three quite different arrangements, and most confusion about it comes from people arguing about different ones.
| Arrangement | What you are buying | What is still yours |
|---|---|---|
| Managed VPS hosting | A server plus a support contract from the host | Your application, your data, your content, and whatever the host's plan excludes |
| Unmanaged VPS | Raw compute and an IP address | Everything above the hypervisor |
| Unmanaged VPS plus a management panel | Raw compute, plus software that automates the routine administration | Root, the cloud account, and any decision the panel deliberately leaves to you |
The third arrangement is what Laravel Forge, Ploi, RunCloud, CloudPanel and DeployManage all sell. It exists because the second option is cheaper and more flexible than the first, but only pays off if the maintenance load comes down.
On a managed VPS the hosting provider handles operating system updates, security patching, monitoring and support, and charges a premium for the labour. On an unmanaged VPS you get the raw server and nothing else, so you own every update, configuration file, certificate renewal and backup yourself. Managed costs more money, unmanaged costs more of your time.
The interesting part is that the money gap is far smaller than the marketing suggests. Compare like for like on entry tier specifications, read off the vendors' own pages in August 2026:
| Option | Specs | Price | Who administers it |
|---|---|---|---|
| Cloudways Flexible Micro (managed platform) | 2 GB RAM, 1 vCPU, 50 GB disk, 2 TB transfer | $11.00 per month | Cloudways, on their cloud account |
| DigitalOcean Basic droplet (unmanaged) | 2 GB RAM, 1 vCPU, 50 GB disk, 2 TB transfer | $12.00 per month | You |
At the entry tier the managed option is a dollar cheaper than the identical unmanaged droplet. That is worth sitting with, because it kills the usual argument. Self managing does not win on the price of one small server.
Where it does win is at scale and on control. Managed platforms bill per server, so the second, fifth and tenth box each carry the full premium again, and add ons stack on top of that. A management panel is a flat fee covering every server you connect. The crossover arrives as you add servers, and it arrives faster if you need things managed plans meter separately, like extra applications, staging copies or backup retention.
The control argument is simpler. On a managed VPS the host decides when your kernel reboots and which PHP versions exist. On an unmanaged box you decide, and if you want a preview PHP release or an unusual Redis configuration nobody has to approve it.
There are three ways, and the right answer depends on how much of your week you want back rather than on how skilled you are.
Over SSH, by hand. You log in, edit config files, run package updates, write systemd units for background workers, run certbot and hope the renewal timer fires. This gives total control and total responsibility. It is fine for one server you care about. It scales badly to five, because the servers drift apart and only you remember which one had the custom nginx tweak.
With a hosting control panel. cPanel, Plesk and DirectAdmin organise a server into tenant accounts, which is the right shape if you resell hosting and need to meter customers. They are the wrong shape for one team's applications, and they do not deploy code from Git.
With an application management panel. This organises the server around applications and releases instead of accounts. You get the stack, certificates, firewall, databases, mailboxes and Git deploys from one interface, and the server stays in your cloud account. That is the model DeployManage uses, and it is the one worth choosing if the thing you actually ship is software rather than hosting plans.
Whichever route you take, the same tasks have to land somewhere. A useful test before you commit to unmanaged hosting is to read this list and decide, honestly, who is doing each item on a Tuesday in eight months.
| Task | How often | What happens if it slips |
|---|---|---|
| Operating system security updates | Weekly to monthly | Known exploits stay open on a public IP address |
| TLS certificate renewal | Every 60 to 90 days | Browsers show a full page security warning and traffic stops |
| Database backups, and a restore test | Daily backup, quarterly test | You discover the backup was empty on the day you need it |
| Log rotation and disk headroom | Continuous | The disk fills, MySQL refuses writes, the site 500s |
| Firewall and SSH review | Quarterly | A forgotten open port becomes the way in |
| Queue worker and cron health | Continuous | Jobs silently stop running and nobody notices for days |
| Deployments | Every release | Half deployed code serves errors to live traffic |
You do not need cPanel to manage a VPS, and for an application server it is usually the wrong tool. cPanel and WHM exist to divide one machine into hosting accounts and bill them, which is why cPanel retail pricing meters by account: Solo is $29.99 per month for a single account and Premier is $69.99 for up to 100 plus $0.49 for each one beyond that, read off cpanel.net in August 2026. If you are not reselling hosting you are paying for a metering model you will never use.
The alternatives, roughly in order of how much they leave you to do:
| Approach | Cost | Deploys from Git | Good fit for |
|---|---|---|---|
| Pure SSH and config files | Free | Only what you script | One server, an owner who enjoys it |
| Webmin or Cockpit | Free | No | Occasional system administration through a browser |
| DirectAdmin | $5 to $29 per month, Standard is $29 for unlimited accounts | No | Cheaper tenant hosting than cPanel |
| Plesk | From 6.60 EUR per month, metered by domain | Limited | Mixed Windows and Linux hosting estates |
| Application panel such as DeployManage | Flat fee, free to start | Yes, zero downtime with rollback | Teams and agencies shipping their own applications |
The practical answer for most people reading this: skip the hosting panel entirely, use an application panel for the routine work, and keep SSH for the rare occasions you genuinely need it. You lose nothing, because root is still yours.
An unmanaged VPS means the provider guarantees the hardware, the network and the hypervisor, and nothing above that. They will replace a failed host and keep the IP routable. They will not patch your kernel, fix your nginx config, recover your database or tell you the disk is full.
Buy unmanaged if at least two of these are true. You have someone on the team who is comfortable in a terminal. You need software or versions a managed plan will not install. You run enough servers that per server management fees have started to look absurd. You want the server inside your own cloud account so migrating providers is a weekend, not a negotiation.
Buy managed instead if the business has no technical staff, if downtime during business hours is genuinely expensive and nobody is on call, or if you are running a single small site and the difference is a few dollars a month. There is no prize for administering a server badly to save eleven dollars.
The most common mistake is the middle case: a competent developer buys unmanaged to save money, then quietly spends four hours a month on maintenance. At any reasonable billing rate that is the most expensive hosting decision available. Either accept the work as a real cost or automate it away.
Everything above is manageable on one server. The failure mode appears on the fourth. Servers built at different times drift: different PHP patch levels, one with a firewall rule added during an incident, another where somebody disabled unattended upgrades to stop a restart and never re-enabled them. Nobody documents any of it, and the person who knows leaves.
Centralised VPS management is mostly about removing that drift. One place that knows every server, every site on it, which PHP version each site runs, which certificates expire when, which users hold SSH access, and which release is currently live. When a CVE lands you want to answer "which of our boxes is affected" in a few seconds, not by SSHing into nine machines.
It also changes the economics. Per server billing punishes you for splitting workloads sensibly, so people cram a database, a queue worker and four sites onto one overloaded box to avoid a second bill. A flat fee removes that pressure: you can give the noisy client its own server because the only extra cost is the provider's, and the provider's is honest.
Once several servers are under one panel, the operational habits worth keeping are unglamorous. Standardise the stack so every box is built the same way. Deploy from Git so the running code always matches a commit. Keep an audited server setup checklist and run it on every new server. And test one restore a quarter, because an untested backup is a rumour.
VPS management is the ongoing administration of a virtual private server: patching the operating system, configuring the web server and databases, issuing and renewing TLS certificates, managing the firewall and SSH access, taking backups, and deploying application code. On a managed plan the host does most of it. On an unmanaged plan it is entirely yours.
On a managed VPS the hosting provider handles updates, security patching, monitoring and support, and charges a premium for that labour. On an unmanaged VPS you receive the raw server and own every update, configuration file, certificate renewal and backup yourself. Managed costs more money, unmanaged costs more of your time.
You can administer it directly over SSH, install a hosting control panel such as cPanel or Plesk, or connect it to an application management panel. SSH gives full control and full responsibility, hosting panels suit reselling accounts, and an application panel automates the stack, certificates, firewall, databases and Git deployments while leaving root with you.
Use SSH for one off tasks and a panel built for applications rather than hosting accounts. cPanel meters by account, which only makes sense if you resell hosting. Free alternatives such as Webmin or Cockpit cover basic system administration, while an application panel adds the stack, TLS, mailboxes and zero downtime Git deployments.
Unmanaged VPS means the provider is responsible only for the hardware, network and hypervisor. They keep the machine powered and the IP routable, and nothing above that. Operating system patching, web server configuration, security, backups, monitoring and recovery are all yours, and the plan usually includes no technical support for them.
It is worth it if nobody on the team is comfortable administering Linux, or if downtime is expensive and there is no one on call. It is poor value once you run several servers, because managed platforms bill per server while a management panel charges a flat fee for all of them. Control is the other trade: managed hosts decide your software versions.
It depends on which layer you pay for. A 2 GB DigitalOcean Basic droplet is $12.00 per month unmanaged, and Cloudways Flexible Micro with the same specifications is $11.00 per month fully managed, both read in August 2026. Panels sit on top: cPanel Solo is $29.99 per month, DirectAdmin Standard $29.00, and DeployManage is free to start.
For an unmanaged VPS with no panel, yes. You need to be comfortable with SSH, package management, nginx or Apache configuration, and Linux permissions. A management panel lowers that bar considerably by generating the configuration for you, though you still need to understand DNS, domains and what your application requires to run.
Yes. A management panel connects servers from different providers into one dashboard, so DigitalOcean, Hetzner, AWS and a legacy box in a colocation rack all appear together. That matters most for patching and certificate expiry, where the useful question is which of your servers is affected rather than the state of any single one.
It depends on what the server is for. cPanel, Plesk and DirectAdmin are best for reselling hosting to tenants. Laravel Forge, Ploi, RunCloud, CloudPanel and DeployManage are built around applications and deployments instead. If you ship your own software rather than hosting plans, an application panel is the right category.
You are, completely. The provider secures the hypervisor and the physical network, and stops there. Closing unused ports, disabling password based SSH login, applying kernel and package security updates, isolating sites from each other and keeping recoverable backups are all your responsibility, and no unmanaged plan includes support for any of them.
No, a VPS runs perfectly well with nothing but SSH, and plenty of experienced administrators prefer it that way. A panel is a time trade rather than a requirement. It becomes hard to argue against once you pass roughly three servers, or the moment more than one person needs to make changes safely.
Connect a server from any provider and DeployManage installs the stack, issues the certificates, locks the firewall down and gives you zero downtime Git deploys with one click rollback. Your cloud account, your root access, one flat fee. Free plan to start.
# free plan · no credit card required