--- title: Managed vs Unmanaged Hosting description: "The difference in who handles the OS, patches, backups, and monitoring. Choose based on team skills, not price alone." canonical: https://penasihathosting.com/en/hosting-wiki/managed-vs-unmanaged type: wiki locale: en updated: 2026-10-29 author: Willya Randika --- # Managed vs Unmanaged Hosting ## Overview - **Summary:** The difference in who handles the OS, patches, backups, and monitoring. Choose based on team skills, not price alone. - **Author:** Willya Randika ([profile](/penulis/willya-randika)) ## Article Managed hosting means the provider also handles the server layer: OS installation, security patches, panel updates, basic monitoring, and often backups. Unmanaged hosting gives you a raw server with root access. You install, secure, and maintain everything. The word managed has no single definition. Read the contract instead of trusting one word on the pricing page. ## Who does what With unmanaged hosting, OS patches, firewall, web server, backups, and monitoring are your tasks. With managed hosting, the provider takes over most of that work. Application code, WordPress plugins, themes, and store configuration remain yours unless there is an add-on service. Managed server covers the OS, panel, and web stack. Managed WordPress usually adds core and plugin updates, caching, staging, and WordPress-specific support. Check whether automatic plugin updates include testing and rollback. ## Questions before paying Ask who patches the kernel, whether a backup restore has been tested, what the P1 response time is, whether root access is provided, and what is excluded from the plan. If a provider promises “managed” without details, assume the coverage is limited to infrastructure. On managed cPanel, the provider usually handles cPanel and WHM updates, OS patches, and daily backups with 7 to 30 day retention. You still own plugins, themes, and credentials. On unmanaged, `apt list --upgradable`, `unattended-upgrades`, and `systemctl status nginx` are your work. ## When to choose unmanaged Unmanaged makes sense when the team has a sysadmin, needs custom configuration the panel does not support, or has stable load and can handle incidents. Managed pricing can also feel high compared with the risk you can actually manage. Managed is better when the team wants to focus on the product, needs a clear patch and backup schedule, has no one to respond at 2 a.m., or is willing to pay a premium for [uptime](/en/hosting-wiki/uptime) and support. ## The limits of managed Managed does not mean every problem is solved. Malware from a plugin, slow queries, and application bugs can still happen. Some providers restrict root access, so make sure you can migrate your data if you need to leave. Managed services can fail too. Keep a backup copy outside the provider. For server context, see [cPanel](/en/hosting-wiki/cpanel), a [Linux firewall](/en/hosting-wiki/linux-firewall), and the [SLA](/en/hosting-wiki/hosting-sla). ## FAQ Not automatically. Patching and firewalls help, but application security, admin access, and plugins still depend on you. Often yes, for an added fee. Check whether the provider reinstalls the server or adds services without disrupting data. Usually not all of them. Many providers update and offer guidance. Custom fixes or plugin debugging are often out of scope.