A WordPress site, an online shop and a custom application can run on very different hosting products. Your software requirements, actual workload and responsibility for operating the service matter most. A cheap server can cost more in practice than web hosting if you spend time maintaining it or pay someone to do so.
We compare web hosting, VPS, root servers and Managed Private Servers (MPS). The managed option is particularly relevant if you need more resources for websites and want to hand over system maintenance. The examples are decision scenarios rather than measured performance tests. Without knowing your application, there is no reliable visitor-count threshold for a particular plan.
How the four product types compare
| Criterion | Web hosting | VPS | Netcup root server | Managed Private Server |
|---|---|---|---|---|
| Environment | Prepared hosting environment with a control panel | Virtual machine with its own operating system | Virtual machine with dedicated CPU cores | Managed virtual machine with Plesk and dedicated CPU/RAM resources |
| Software choice | Within the plan features and available runtimes | Your own installation with root access | Your own installation with root access | Plesk environment; discuss special requirements with Netcup in advance |
| System operation | Netcup runs the hosting platform; you maintain your website | You administer the operating system and services | You administer the operating system and services | Netcup maintains and monitors the system; you maintain your website |
| Typical reason to choose it | Website and email with little system administration | Custom services, containers or specialist software | Custom services needing dedicated CPU capacity | More resources for websites without your own system administration |
A terminology detail matters here: Netcup root servers are also virtualised. Dedicated CPU cores are a key difference from a VPS. The name does not mean that you rent an entire physical machine or that Netcup administers your applications. Both server types provide root access. Netcup describes its server types in the official documentation (German). The MPS product overview describes the managed alternative.
Example 1: WordPress for a blog or business website
You want a business website with a contact form, some images and a blog. You need PHP, a database and email, but no custom system services. Web hosting is a sensible starting point: you configure the domain and CMS while the hosting platform is already in place.
Compare your plugins' requirements with the PHP version, PHP memory limit and available extensions. Count websites, databases and mailboxes as well. More storage will not solve a limit elsewhere in the application. Check that the function you need is available through the hosting panel.
A larger web hosting package can be more practical than your own server for several small WordPress sites. Every installation still needs updates, secure access and a backup you can restore. Maintaining the hosting platform does not replace maintaining WordPress, plugins and themes. Compare web hosting plans and coupons.
Example 2: A custom application with background services
Your application needs a continuously running worker, a particular database service or several Docker containers. Check the web hosting plan's capabilities first: support for a programming language does not automatically mean that every server function is available or permitted. If you need your own system packages or services, a VPS is often a better fit.
Budget RAM for the application, database, cache and operating system together. Allow storage for uploads, database growth, logs and temporary files. A test environment working with a few records is not a reliable basis for sizing the later production service.
The extra flexibility requires decisions: you configure network access, updates, TLS certificates and service startup after a reboot. If nobody on the project can handle those tasks, include outside administration in the budget. Browse VPS offers.
Example 3: A shop or application with a growing workload
A shop with many product variants, imports and complex search has different requirements from a largely cached information website. Base the decision on measurements: how much RAM is used? Are the CPU or database saturated during imports? Are slow external services holding up page loads?
A root server becomes interesting when your project needs custom server services and CPU resources are a significant bottleneck. Dedicated cores will not fix inefficient database queries or excessive plugin calls. Review caching, image sizes and application configuration first.
A business-critical shop also needs a backup operator: who responds if an update breaks checkout? If you need more resources but cannot take on system administration, check the Managed Private Server described below. If you want to operate the system yourself, you can compare root servers.
Managed Private Server: more resources with a maintained system
A Netcup Managed Private Server (MPS) combines a virtual hosting environment of your own with system administration by Netcup. It is KVM-virtualised and uses Plesk with web, database and mail services. The current offers list dedicated CPU and RAM resources. This does not give you an entire physical machine. Browse current Managed Private Server offers at Netcup.
An agency hosting several client websites is a useful example: it wants to manage hosting accounts and domains in Plesk, needs more resources and wants someone else to organise operating system updates. A shop using a supported PHP application may also fit. Check PHP versions, extensions and database requirements; the word “Managed” does not establish compatibility with your software.
- Netcup maintains the system: The described management includes security updates for the server environment, maintaining system services and regular monitoring.
- You maintain the application: Continue planning CMS, plugin and theme updates, secure user accounts and functionality checks. After a shop update, for example, test checkout and the payment integration yourself.
- Changes have limits: Root and sudo access are excluded. Discuss custom configurations and specialist software with support. SSH can be set up on request and does not provide root access.
If your project needs custom Docker stacks, a specialist search service or continuously running background processes, confirm support for those requirements before ordering. For system packages you choose yourself and complete control, a VPS or root server remains a more suitable starting point.
Plan backups separately: Netcup lists Backupspace and Managed Backup as extensions. Do not assume that “Managed” alone includes a complete backup of your data. Confirm the scope, schedule, retention and recovery process for files, databases and email. The MPS documentation explains customisation and backup options.
Include maintenance and backups in the decision
With a server you administer yourself, the work continues after installation. Set aside regular time for security updates, checking alerts, free storage and verifying backups. Plan major version upgrades as well. A precise hourly estimate would be unhelpful without knowing the services involved.
- Web hosting: Update the CMS and extensions, check PHP compatibility, secure access and back up the website and database.
- VPS and root server: Also maintain the operating system, web server, database and other services; configure the firewall, monitoring and recovery after outages.
- Managed Private Server: Hand over system maintenance while still organising application updates, functionality checks and a suitable backup plan.
- Every option: Store backups separately from the live project and practise restoring them.
For a database-driven site, files and database need to be consistent. Decide how much data loss you can tolerate: occasional manual backups are unlikely to be sufficient for daily orders. A snapshot before a change is useful, but should not be the only backup. Record how you will access backups if access to the production system fails.
Make these decisions before ordering
- Write down requirements: Which application, runtimes, domains, mailboxes and background services do you actually need?
- Assign operation: Do you want to maintain the system yourself or hand this over? Who maintains the CMS and restores the service?
- Check limits: Does the application need root access or special services? Compare specific plan details and confirm special requirements in advance for the managed option.
- Calculate the total: Include contract duration, extras, backups and administration if needed.
For an ordinary website without special system requirements, start with web hosting. For custom services, investigate a VPS. For a demonstrated CPU requirement with your own administration, compare root servers. If your websites need more resources and you want Netcup to maintain the system, investigate a Managed Private Server. Then choose the smallest plan that covers your needs with a sensible margin, and check upgrade options in advance.
The 12- and 24-month cost comparison helps with the next step. To choose a suitable discount and check the order, read the Netcup coupon redemption guide.
Sources
The product differences were checked against official Netcup information on 12 October 2026; the Managed Private Server information was added and checked on 13 October 2026. The project examples and decision questions are our editorial assessment. Some official pages linked below are in German.
- Netcup: Server types, virtualisation and dedicated CPU cores (German)
- Netcup: Web hosting interface and control panel (German)
- Netcup: Maintaining and securing web applications (German)
- Netcup: Managed Private Server offers, resources and system management
- Netcup: MPS administration, customisation and backup options