In the Netcup vs Contabo decision, Netcup is the better default for a smaller WordPress site when you value transparent contract choices, hourly billing, and a straightforward VPS range. Contabo is the stronger raw-capacity buy when RAM and storage per dollar matter more than flexibility. Neither provider manages WordPress for you by default.
That last point decides more projects than the plan table. A virtual private server gives you compute, memory, storage, and root access. You still need to install and maintain the web stack, secure SSH, configure backups, monitor resources, and recover from failures. You can do that yourself or connect either provider to xCloud through the Other Providers workflow.
This Netcup vs Contabo for WordPress hosting comparison uses current first-party plan information checked on September 24, 2026. It does not claim first-hand performance testing. Prices, taxes, promotions, and regional availability can change, so confirm the final checkout total before ordering.
TL;DR
| If you want to… | Better fit | Why |
|---|---|---|
| Run a small or moderate WordPress site with clearer term choices | Netcup | Monthly, 12-month, and 24-month options are visible, with hourly billing described on the VPS page |
| Maximize RAM and storage at a low displayed promotional price | Contabo | The current Cloud VPS range advertises larger memory and disk allocations at low entry prices |
| Operate several memory-heavy test sites | Contabo | More advertised RAM provides headroom, although allocation alone does not prove faster WordPress performance |
| Minimize long promotional commitments | Netcup | The product page exposes multiple contract periods instead of centering the offer on a first-24-month promotion |
| Avoid manual WordPress stack administration | Either provider with xCloud | xCloud can provision a fresh Ubuntu VPS from an unsupported/custom provider and manage WordPress workflows |
| Buy managed hosting with provider-owned application support | Neither raw VPS by itself | Netcup and Contabo sell infrastructure; you still own the operating system and WordPress stack |
Netcup vs Contabo for WordPress hosting at a glance
Netcup wins on visible billing flexibility, while Contabo wins on advertised resources per entry-level dollar. Raw specifications do not settle WordPress performance because shared CPU scheduling, storage latency, database behavior, caching, and traffic shape also matter.
The plans below are representative starting points, not equivalent performance tiers. Netcup displayed German VAT on the page used for this review. Contabo’s indexed US pricing displayed dollar-denominated promotional prices. Do not compare the numbers without accounting for tax, billing term, location, setup options, and the price after a promotion ends.
| Category | Netcup | Contabo | WordPress consequence |
|---|---|---|---|
| Entry plan reviewed | VPS 500 G12.5 | Cloud VPS 4 | Both exceed the minimum resources of a basic WordPress installation |
| Displayed CPU | 2 x86 vCores | 4 vCPU cores | Core count alone does not reveal single-thread speed or contention |
| Displayed RAM | 4 GB | 8 GB | Contabo offers more memory for database cache, PHP workers, or multiple sites |
| Displayed storage | 64 GB SSD | 100 GB SSD | Contabo provides more capacity; neither figure replaces a backup plan |
| Displayed price | €8.26/month before 19% VAT, €9.50 including VAT on a 12-month term | $5.28/month promotional display for Cloud VPS 4 | Currency, tax, duration, region, and renewal price make this an imperfect comparison |
| Billing signal | 1, 12, or 24 months; VPS page also describes hourly billing | Promotional pricing shown for a fixed introductory period | Netcup exposes more visible term choices on the product page reviewed |
| Traffic | Included | Advertised as unlimited traffic with an asterisk | Read fair-use and port terms before a traffic-heavy launch |
| Management | Unmanaged VPS | Unmanaged VPS | You install, secure, update, monitor, and recover WordPress unless you add a management layer |
| xCloud path | Other Providers | Other Providers | Start with fresh supported Ubuntu and working root SSH access |
How this comparison works
This comparison separates facts from recommendations. Plan names, displayed resources, prices, billing signals, and included features come from first-party provider pages checked on September 24, 2026. Recommendations interpret those facts for common WordPress workloads.
Netcup’s official VPS product page was directly accessible during research. It displayed the VPS 500 G12.5 at €8.26 per month before 19% German VAT, or €9.50 including VAT, on a 12-month term. It also showed one-, 12-, and 24-month selections, a 30-day money-back guarantee, traffic included, snapshots, a remote console, preconfigured images, DDoS protection, and API access.
Contabo’s official “Cloud Services and Infrastructure Pricing” page was protected by an automated security challenge during research. Current indexed first-party results from that page displayed Cloud VPS 4 with 4 vCPU cores, 8 GB RAM, 100 GB SSD, a 200 Mbit/s port, and a $5.28 monthly promotional price. The same first-party listing displayed Cloud VPS 6 with 6 vCPU cores, 12 GB RAM, 200 GB SSD, a 300 Mbit/s port, and $7.20 per month. Because the live page could not be independently rendered, confirm the plan, promotion duration, location surcharge, tax, and renewal price at checkout.
No benchmark is presented here. A VPSBenchmarks result ranks for this query because it supplies measurements across general server workloads, but it does not answer how a specific WordPress database, plugin set, cache configuration, and traffic pattern will behave. Treat every plan table as a shortlist, then measure your own site.
Pricing and contract terms
Contabo shows the lower entry price and more resources, but Netcup gives the clearer flexibility story. In a Netcup vs Contabo for WordPress hosting cost comparison, the practical winner depends on whether you optimize for the first invoice or for the ability to change direction.
Netcup’s reviewed 12-month VPS 500 G12.5 price was €8.26 per month before VAT. The page also allowed one-month and 24-month selections, with visible discounts on longer terms. That structure makes it easier to compare the cost of flexibility with the cost of commitment.
Contabo’s current indexed pricing advertised Cloud VPS 4 at $5.28 per month and Cloud VPS 6 at $7.20 per month. Contabo also uses introductory pricing language on product results, so the displayed number should not be treated as a permanent monthly rate. Confirm the regular price, minimum term, setup fee, regional surcharge, and tax for your billing address.
| Cost question | Netcup | Contabo |
|---|---|---|
| Lowest reviewed monthly display | €8.26 before VAT on a 12-month VPS 500 term | $5.28 promotional display for Cloud VPS 4 |
| Currency in reviewed page | Euro | US dollar |
| Tax treatment seen | German 19% VAT explicitly displayed | Depends on region and checkout; verify before purchase |
| Longer-term discount | Visible for 12 and 24 months | Promotional period shown in current indexed product results |
| Short-term option | One-month selector and hourly billing statement on VPS page | Verify current term and cancellation rules at checkout |
| WordPress software cost | WordPress is free, but administration time is not | WordPress is free, but administration time is not |
The honest comparison includes your time. A $5 server that needs manual security updates, backup checks, failed-certificate recovery, and weekend incident response can cost more than a higher-priced managed workflow. If you are deciding between unmanaged infrastructure and a managed platform, xCloud’s xCloud vs Cloudways comparison explains the broader control-versus-convenience trade-off.
CPU, RAM, and storage
Contabo offers more advertised capacity in the entry plans reviewed. Netcup’s smaller plan can still suit a focused WordPress site, but the plan table cannot establish which server is faster.
The Netcup VPS 500 G12.5 includes 2 x86 vCores, 4 GB RAM, and 64 GB SSD. The VPS 1000 G12.5 moves to 4 vCores, 8 GB RAM, and 128 GB SSD at €14.50 per month before VAT on the reviewed 12-month term. That progression is easy to understand for a site that needs more PHP workers, database cache, or storage.
Contabo’s indexed first-party pricing displays Cloud VPS 4 with 4 vCPU cores, 8 GB RAM, and 100 GB SSD. Cloud VPS 6 increases that to 6 vCPU cores, 12 GB RAM, and 200 GB SSD. On paper, Contabo clearly supplies more memory and storage for the displayed price.
WordPress performance does not scale in a straight line with core count. A slow database query, an uncached page, a blocking external request, or a heavy plugin can dominate response time even when several cores sit idle. Shared-vCPU products can also differ in sustained CPU availability. Without equivalent, current benchmarks, the defensible conclusion is capacity, not speed.
Choose memory headroom when you expect several PHP workers, a busy database, object caching, image processing, or multiple staging sites. Choose storage based on the live media library, database growth, local backup retention, logs, and temporary files. Do not fill the boot disk with the only copy of your backups.
Network and location fit
Pick the provider location closest to the audience and the rest of the application path. A low server price does not compensate for avoidable latency between visitors, the WordPress origin, external APIs, and payment services.
Netcup’s VPS page includes traffic and DDoS protection but the exact network terms depend on the selected product and location. Contabo advertises port speeds per plan and “unlimited traffic” with an asterisk. Read the current usage policy because unlimited wording can still carry fair-use, port, or sustained-transfer conditions.
For a mostly European audience, compare the precise city and network route available at checkout. For an international audience, use a CDN for cacheable assets and pages, but remember that WordPress administration, uncached requests, login, cart, checkout, and API operations still reach the origin.
Run a simple pre-purchase checklist:
- Is the target region available for the selected plan?
- Does that region change the monthly price or setup fee?
- Is one public IPv4 address included, optional, or separately billed?
- What IPv6 allocation is supplied?
- What port speed and traffic policy apply to this exact plan?
- Can you move or rebuild in another region later?
Do not copy region or network details from a review written years ago. Provider footprints and surcharges change. The checkout configuration is the authoritative answer for the server you are about to buy.
WordPress setup and daily management
Netcup and Contabo both leave the WordPress operating system and application stack to you. A raw VPS is not the same product as managed WordPress hosting.
A complete self-managed build normally includes a supported Ubuntu release, SSH hardening, a firewall, NGINX or OpenLiteSpeed, PHP, a database server, TLS certificates, WordPress, scheduled jobs, caching, backups, monitoring, and update procedures. You also need a recovery method that works when the web dashboard does not.
| Task | Raw Netcup or Contabo VPS | Either VPS connected to xCloud |
|---|---|---|
| Install web and database stack | You build and maintain it | xCloud provisions the supported stack |
| Create WordPress site | Manual or third-party script/panel | xCloud site-creation workflow |
| Issue and renew SSL | You configure ACME tooling | xCloud exposes Let’s Encrypt site controls |
| Manage firewall | Provider and operating-system tools | Provider controls plus xCloud firewall workflow |
| Monitor connection | Your monitoring stack | xCloud server and site status, plus your external monitoring |
| Restore after provider-level loss | Your off-server backup and runbook | Still your responsibility; management does not replace independent backups |
The management layer should match the workload. A single personal blog can be reasonable to manage by hand if you understand Linux administration. An agency with many customer sites usually benefits from repeatable provisioning, role separation, site-level controls, and a documented recovery process.
Do not install two control panels on one server. If you plan to connect the VPS to xCloud, start with fresh supported Ubuntu rather than preinstalling another web panel. Conflicting services, ports, users, and package sources make provisioning less predictable.
Backups, snapshots, and recovery
A provider snapshot is useful, but it is not a complete WordPress backup strategy. Your recovery plan needs copies outside the server and a restore procedure tested against the application.
Netcup’s VPS page lists snapshots among the plan features. Contabo product snippets also advertise snapshot availability on current Cloud VPS plans, while backup products or additional snapshot capacity may vary by plan. Verify the exact quantity, retention, and price before relying on either provider’s control panel.
For WordPress, protect four different things:
-
Database data, including posts, users, orders, settings, and plugin tables.
-
Uploaded files, especially media and customer-generated content.
-
Configuration, including web server, PHP, cron, firewall, and environment settings.
-
Recovery knowledge, including credentials, DNS ownership, backup locations, and the order of restoration.
Keep at least one backup copy outside the VPS and outside the same provider account. Encrypt sensitive backups, define retention, and monitor failed jobs. A backup that has never been restored is an assumption, not evidence.
Snapshots make fast rollback convenient before a risky change, but they can capture a database at an inconsistent point and they disappear with the provider account or region if that is your only copy. Use snapshots as one recovery layer, not the whole system.
Support boundaries
Provider support can restore infrastructure access, but it does not automatically debug WordPress. Support scope is a deciding factor in any Netcup vs Contabo for WordPress hosting choice because neither raw VPS includes full application management.
Typical infrastructure questions include billing, a failed host node, provider networking, console access, or a server that will not boot. WordPress questions include plugin conflicts, PHP errors, database locks, cache behavior, malware cleanup, theme failures, and slow queries. Those application problems remain yours on an unmanaged VPS unless you buy a separate service.
This boundary changes the real cost calculation. If nobody on your team can recover SSH, inspect logs, restore a database, or rebuild a server, a cheap VPS is not operationally cheap. Add the cost of a management platform, a system administrator, or a managed hosting product to the decision.
xCloud can standardize provisioning and common server/site operations, but it does not turn Netcup or Contabo into application-support providers. You still need provider access, independent monitoring, off-server backups, and an escalation path for the WordPress application.
Scaling and workload fit
Scale from measured bottlenecks, not from plan marketing. A useful Netcup vs Contabo for WordPress hosting decision starts with resource evidence, because more RAM helps only when memory is the constraint and more cores help only when the workload can use them.
A practical WordPress monitoring set includes CPU saturation, memory pressure, swap use, disk space, disk latency, database slow queries, PHP worker queues, cache hit ratio, error rate, and uncached response time. Add business signals such as checkout success for WooCommerce.
| Workload | Better starting bias | Reason |
|---|---|---|
| One small cached brochure site | Netcup VPS 500 or a comparable small plan | 4 GB RAM can be enough with disciplined plugins and caching |
| Several staging sites | Contabo capacity bias | More displayed RAM and storage provide room, subject to measured CPU and I/O behavior |
| Media-heavy site | Contabo capacity bias, plus object storage consideration | More local storage helps, but media growth should not consume the system disk indefinitely |
| WooCommerce store | Benchmark both or use managed hosting | Uncached database and checkout behavior matter more than the headline core count; review the broader WooCommerce hosting requirements before sizing |
| Agency fleet | Either provider with a management layer | Repeatability, access control, backups, and recovery dominate the provider logo |
| Short-lived test environment | Netcup flexibility bias | Visible short-term and hourly billing can reduce commitment |
Do not place unrelated production workloads on one VPS merely because memory remains. Isolation simplifies recovery, security boundaries, and performance diagnosis. Recent xCloud guides to OpenPanel deployment, Instatic hosting, and Postiz hosting cover different application patterns; they should not be treated as spare processes for a WordPress production server.
Connect either provider to xCloud
Netcup and Contabo can both fit xCloud’s custom-provider workflow when the VPS meets the current requirements. The provider creates the infrastructure. xCloud connects to the fresh server and provisions the management stack.
The high-level flow is:
-
Create a VPS at Netcup or Contabo with a fresh Ubuntu image supported by xCloud.
-
Record the public IP address and prepare working root SSH access.
-
Ensure ports 22, 80, and 443 are reachable.
-
In xCloud, add a server and choose Other Providers.
-
Enter the server details, select the supported web server stack, and start provisioning.
-
Point the WordPress domain to the server.
-
Create the site in xCloud, enable SSL, and verify the public site plus
/wp-admin.
Follow xCloud’s Other Providers server guide for current operating-system and field requirements, or the provider-specific walkthroughs for Netcup and Contabo. The August 2026 xCloud release notes also show how the app-first site-creation and server dashboard workflows have evolved.
Do not connect a server that already runs a production control panel or unrelated application. Reinstalling to a clean image is usually safer than asking two management systems to own the same packages and ports.
Choose Netcup if
Choose Netcup when billing flexibility and a simple progression of VPS sizes matter more than maximizing every advertised resource. It is the safer default for a small WordPress site, a short proof of concept, or an operator who wants visible one-, 12-, and 24-month choices.
| ✅ Strengths | ❌ Trade-offs |
|---|---|
| Visible term choices and hourly billing language | Less RAM and storage than the reviewed Contabo entry plan |
| Traffic included, snapshots, remote console, images, API, and DDoS protection listed on the VPS page | German VAT changes the displayed total for applicable buyers |
| Straightforward VPS 500, 1000, 2000 progression | A raw VPS still requires WordPress and Linux administration |
| 30-day money-back guarantee displayed | Headline specs do not establish WordPress performance |
Best for: a technically capable WordPress operator who values shorter commitment choices, clear plan steps, and enough resources for one disciplined site.
Choose Contabo if
Choose Contabo when memory and storage per displayed dollar are the priority, and you accept the need to verify promotional and regional terms carefully. Its current Cloud VPS listings are difficult to ignore for multi-site labs, staging workloads, and storage-heavier projects.
| ✅ Strengths | ❌ Trade-offs |
|---|---|
| More advertised RAM and SSD capacity in the entry plans reviewed | Promotional display can obscure the long-term monthly comparison |
| Higher displayed vCPU count at the entry level | More cores do not prove faster or more consistent WordPress performance |
| Several capacity steps for larger workloads | Live pricing page blocked automated verification during this research |
| Current product snippets list port speed and snapshot availability | A raw VPS still requires WordPress and Linux administration |
Best for: a budget-sensitive operator who needs generous memory or disk allocation, can validate checkout terms, and will benchmark the real WordPress workload after deployment.
Frequently asked questions
Is Netcup or Contabo better for WordPress?
Netcup is the better default for a small or moderate WordPress site when contract flexibility matters. Contabo is more attractive when you need more advertised RAM and storage per dollar. Neither provider guarantees better WordPress performance from specifications alone, so benchmark the same site and stack before moving production traffic.
Is Contabo trustworthy for WordPress hosting?
Contabo is an established infrastructure provider, but “trustworthy” should be tested against your requirements. Review the exact plan terms, region, support scope, backup options, provider status history, and cancellation rules. Keep independent backups and a documented rebuild path so no single VPS provider becomes the only recovery option.
Does Contabo offer managed WordPress hosting?
Contabo’s Cloud VPS product is infrastructure, not a complete managed WordPress service. You receive server resources and root access, then install or connect a management layer. If you use xCloud, start with fresh supported Ubuntu and add the server through Other Providers before creating the WordPress site.
How much RAM does a WordPress VPS need?
A small cached WordPress site can run within 2 to 4 GB RAM, but that is not a universal recommendation. WooCommerce, page builders, many PHP workers, large databases, image processing, staging sites, and memory-heavy plugins increase demand. Measure memory pressure and leave headroom for updates, backups, and traffic spikes.
Can I use xCloud with Netcup or Contabo?
Yes, when the VPS meets xCloud’s current custom-provider requirements. Create a fresh supported Ubuntu server, verify root SSH access, open the required ports, and choose Other Providers in xCloud. Then provision the server, point DNS, deploy WordPress, and enable SSL through the xCloud workflow.
Which provider is cheaper after tax and renewal?
The answer depends on billing country, VAT or sales tax, selected region, contract term, setup options, and promotional renewal. Netcup explicitly displayed €8.26 before 19% VAT and €9.50 including VAT for the reviewed 12-month plan. Contabo displayed a lower promotional dollar price, but you should compare the checkout total and regular price over the same period.
Verdict
Netcup wins this comparison for a typical smaller WordPress deployment because its contract choices and billing model are easier to reason about. Contabo wins on advertised capacity for the money. The right decision changes when your site needs more RAM or storage than the Netcup entry tier provides.
Choose Netcup for one well-scoped site, short-term testing, or a preference for visible billing flexibility. Choose Contabo for memory-heavy labs, several staging sites, or storage-biased workloads where you will verify the promotion and measure performance yourself. Choose neither raw VPS alone if your team cannot own Linux, WordPress, backups, monitoring, and recovery.
xCloud does not erase the provider decision. It makes the operating workflow more consistent on either provider by provisioning the supported stack and centralizing common WordPress server and site tasks.
Choose the server, then define the operating model
Start with the workload, not the cheapest card. Estimate active sites, PHP concurrency, database size, media growth, backup retention, traffic geography, and recovery objectives. Then price the server, management layer, backups, monitoring, and administrator time over the same period.
After ordering, deploy one representative copy of the site and measure uncached response time, WordPress administration, database behavior, resource pressure, and recovery. Move production traffic only when the result meets the target and the restore procedure works.
Connect your chosen VPS through xCloud’s Other Providers workflowto build a repeatable WordPress management path on Netcup or Contabo.
If you have found this blog helpful, feel free to subscribe to our blogs for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our Facebook community to share insights and engage in discussions.
Last updated September 22, 2026
← All articles