Back to BlogUnmanaged VPS Hosting: What You Manage and What Your Provider Handles
Unmanaged VPS hosting gives you control of a virtual server while the hosting provider operates the underlying infrastructure. You administer the operating system, applications, access controls, and data. This guide explains that division of work, how it differs from managed hosting, and what to prepare before deploying a production workload.
What does unmanaged VPS hosting mean?
A virtual private server is an isolated virtual machine with its own operating system. With an unmanaged service, you decide what software runs inside that machine and take responsibility for maintaining it. Root or Administrator access gives you flexibility, but it also means that changes, recovery procedures, and ongoing maintenance need an owner.
Managed vs unmanaged hosting
Managed hosting includes administration tasks specified by the provider’s service agreement. These may cover operating-system updates, application maintenance, or monitoring, but the exact scope varies. Unmanaged hosting leaves those tasks with you or a system administrator you appoint. Compare the actual service scope rather than assuming that the word “managed” includes every application, migration, or backup.
When comparing costs, include the time needed for maintenance, monitoring, incident response, and restore testing. An inexpensive server can still require substantial administration. Conversely, a team with established automation may prefer direct control over its software and deployment process.
What EDIS Global support handles
EDIS Global provides infrastructure-level support, billing assistance, technical analysis, and guidance to relevant documentation. Its support team does not log in to customer servers, install software, change internal settings, or perform server migrations between accounts or locations. Internal administration remains with the customer or their appointed administrator.
Read the EDIS Global support scope
Your server administration checklist
Assign responsibility for operating-system and application updates, user permissions, firewall configuration, certificate renewals, service monitoring, and recovery. Record who receives alerts and who can act when the usual administrator is unavailable. Keep a short deployment record so another administrator can understand how the service was built.
For Linux access, use SSH keys and restrict administrative privileges. Verify a new login method in a separate session before disabling the previous one. Plan firewall changes carefully so you retain access. Keep software updated and review authentication logs for unexpected activity.
Follow the SSH security hardening guide
Backups: plan the restore before you need it
EDIS Global’s backup documentation states that customers must manage their own VPS backups. Automatic backup services and instant snapshots are not included. A downloadable QCOW2 disk image can be requested for a fee; this is a separate request, not a recurring backup schedule.
Keep recoverable copies outside the VPS and test restoration. Include application data, database exports, and configuration required to rebuild the service. Decide how much recent data you can afford to lose and how long a restoration can take; those requirements should determine your backup schedule and recovery process.
Check the current backup options and QCOW2 request details
Is unmanaged hosting right for you?
It suits developers and teams that can maintain their own environment, automate deployments, and troubleshoot their applications. It can also work with an independent system administrator. If you need someone else to own updates, application incidents, and restores, arrange that administration before moving a critical service.
Frequently Asked Questions
No. Infrastructure support and server administration are different services. EDIS Global can help with platform-related issues and troubleshooting guidance; work inside the operating system remains your responsibility.
