WordPress Hosting in South Africa: xneelo, AWS Cape Town, and International Options (2026)

The hosting question every WordPress site eventually asks

Every WordPress site we audit, in South Africa or anywhere else, ends up at the same hosting question. The site started somewhere convenient: a shared plan at the registrar, a recommendation from a developer, a free year of hosting bundled with a domain. It worked. Then traffic grew, or the product catalogue grew, or the checkout slowed down, and the host stopped being the right shape.

This post is the conversation we have at that point. It is anchored on the South African market because that is where most of our clients sit, but the comparison applies equally to international clients whose audience is in Europe, North America, or split across regions. The hosting decision is structurally the same one. The right answer just lands on a different provider depending on where your visitors actually are.

We are going to compare three practical hosting patterns for WordPress sites in 2026:

1. xneelo (shared, Managed Servers, Self-managed Dedicated, and xneelo Cloud)
2. AWS Cape Town or Vultr Johannesburg (SA-local hyperscaler regions, self-managed)
3. International VPS providers (Hetzner Germany, NetCup, Vultr) paired with a Cloudflare edge strategy

The right answer depends on where your visitors actually are, how much engineering time you can spend on the stack, and how comfortable you are with Linux when something breaks at 2am.

A note on naming before we go further: xneelo is the South African hosting company previously branded as Hetzner (Pty) Ltd. It rebranded in July 2019 to disambiguate from the unrelated German company Hetzner Online GmbH. The two share a former name, no current branding, no ownership, and no infrastructure. Whenever this post mentions Hetzner without qualification it means the German company; xneelo is always called xneelo.

Latency: the number that decides most of this

Before anything else, work out where your visitors load the site from. Open Google Analytics, look at the country breakdown for the last 90 days, and write down the rough split.

That split decides the rest. Here are the latencies that matter, measured from a Cape Town visitor to common origins:

These are TTFB numbers before any caching, before Cloudflare, before optimisation. The point is structural: a Cape Town origin is fast for South African visitors and slow for everyone else. A London origin is the inverse. Cloudflare's edge network changes the calculation for cached pages (more on that in a moment), but the cache miss path still hits the origin.

If your audience is 90% South African, you want a local origin. If your audience is 40% SA, 30% Europe, 20% US, 10% other, you probably want a European origin plus aggressive edge caching.

Option 1: xneelo

xneelo is the default for South African WordPress hosting. They run datacentres in Newlands (Cape Town) and Samrand (Johannesburg), they bill in ZAR, support speaks English without time-zone friction, and their shared plans are cheap. They are the company previously branded as Hetzner SA, and they are entirely separate from the German Hetzner discussed later in this post.

We host nothing on xneelo's shared product ourselves, but we manage plenty of sites that sit on it. The xneelo product range goes much further than shared though, and the higher tiers (xneelo Cloud, Managed Servers, Self-managed Dedicated) are credible options for serious WordPress workloads.

What xneelo does well

The fundamentals are fine. The datacentres are real. Uptime in our experience is competitive. The support team is reachable in business hours and capable of answering hosting-control-panel questions. ZAR billing keeps invoicing simple, the FICA-style verification matches what SA businesses expect, and SARS-friendly VAT-included invoicing is built in.

For a brochure site under 5,000 monthly visits, xneelo shared hosting is fine. You pay R100 to R300 per month, you get a working WordPress install, and you do not need to think about it.

The xneelo product range, briefly

• Web Hosting (shared): cheapest tier, suitable for brochure sites and small blogs. No control over PHP-FPM, no object cache.
• xneelo Cloud: pay-as-you-go IaaS, scale up or down at any time, billed in ZAR. The closest xneelo product to a typical international cloud VPS.
• Managed Servers: xneelo manages the OS, security patches, and stack updates. Good middle ground for teams that want a server without managing one.
• Self-managed Dedicated (TruServ): physical hardware, root access, your responsibility. RAM goes up to 256GB on the Commerce tier per CPU. Suitable for high-traffic WooCommerce, membership sites, and any database-heavy workload.

For most SA-anchored WordPress sites with non-trivial traffic, the xneelo Cloud or Self-managed Dedicated tiers are the right place to land on this option, not the shared product.

What xneelo's shared tier does not do well

PHP version freshness lags. We have seen xneelo shared plans pinned to PHP versions that the official PHP project marked end-of-life eighteen months ago. You can request newer versions, but only on certain plans, and the upgrade path is manual.

You have no real control over PHP-FPM. The pm.max_children setting we wrote about in our PHP-FPM tuning post is managed by xneelo, not by you. On busy shared plans this means 503 errors during traffic spikes and no way to tune around them.

No object cache. Redis and Memcached are not available on most xneelo shared plans. Page caching options are limited to the standard plugin route, which the WordPress installation runs in PHP rather than at the server level. For a site that needs to handle real concurrency this is a meaningful ceiling.

The xneelo Cloud and Self-managed Dedicated tiers do not have these limits. You get a real Linux box and run the stack you want.

When xneelo is the right call

For shared: small brochure site, SA-only audience, owner who wants to call someone in Cape Town when WordPress breaks, budget under R500 per month, no commerce or low-volume commerce.

For xneelo Cloud or Dedicated: SA-anchored audience, serious workload (WooCommerce, membership, custom plugin), ZAR billing is important, you (or your agency) can run a Linux server.

Option 2: AWS Cape Town or Vultr Johannesburg

The second SA-local pattern is to use one of the international cloud providers that happen to have a region inside South Africa. There are exactly two as of 2026: AWS Cape Town (region af-south-1, launched April 2020, three availability zones) and Vultr Johannesburg (single datacentre).

Neither is managed in the xneelo sense. You get raw compute and you run the WordPress stack on top of it yourself. The trade-off versus xneelo Cloud is product breadth: AWS gives you the full hyperscaler toolkit (RDS, S3, CloudFront, Route 53, Secrets Manager, plus everything else), and Vultr gives you a cleaner, simpler control panel at a lower price point.

AWS Cape Town directly

The AWS Africa (Cape Town) region has three availability zones (af-south-1a, af-south-1b, af-south-1c), which means a properly architected WordPress deployment can survive a single-AZ outage without going down. That is something xneelo cannot offer at any tier.

A typical WordPress on AWS Cape Town setup uses an EC2 instance for the application, RDS MariaDB or Aurora for the database, S3 for media offload, CloudFront for edge caching (with a Cape Town POP), and either ElastiCache Redis or a Redis on the application server itself. Pricing is in USD, which means FX exposure, and AWS's published rates for af-south-1 are higher than the equivalent US or EU region (Cape Town carries a small regional premium, typically 5-15% above us-east-1 on common instance types).

For SA businesses that need the broader AWS toolkit (Lambda, SQS, EventBridge, the full IAM model), AWS Cape Town is the only practical option. For a pure WordPress workload it is often overkill, and one of the other options on this list lands cheaper.

Vultr Johannesburg

Vultr opened a Johannesburg region in late 2022. It is one datacentre, no multi-AZ guarantees, but the product is simple, the control panel is clean, and pricing is competitive with the cheapest international VPS providers. Vultr's certification list for Johannesburg (ISO 27001, SOC 1 Type 2) is reasonable for a single-datacentre region.

A typical small WooCommerce store runs comfortably on a Vultr Johannesburg High Performance instance at $12-$24/month with 2 vCPU and 4-8GB RAM. You get root access, a real Linux box, and the same stack patterns work as on xneelo Cloud:

# Edge: Caddy with automatic HTTPS
# App: PHP 8.3 FPM, tuned to the workload
# DB: MariaDB 11, innodb tuned for the dataset
# Cache: Redis for object and full-page cache
# Queue: WP Cron disabled, system cron driving wp-cli

Vultr bills in USD, so there is forex exposure, but the pricing is low enough that the rand swing matters less in absolute terms than on a Hetzner Germany or NetCup box billed in EUR at a similar spec.

When AWS Cape Town or Vultr Johannesburg is the right call

AWS Cape Town: you need the broader AWS toolkit, you have engineering capacity to run a properly architected multi-AZ deployment, the budget supports the regional premium, USD billing is not a problem.

Vultr Johannesburg: you want a simple SA-local VPS with international cloud ergonomics (API, snapshots, instant scaling), you are billing internationally so USD is fine, you are running a Woo store or membership site where local origin matters and the engineering investment of xneelo Self-managed Dedicated is more than you need.

Option 3: International VPS plus Cloudflare

This is the option most people overlook for SA sites and the obvious choice for our international clients. Host the WordPress origin on a competent international VPS provider and put Cloudflare in front of it.

The three providers we run production sites on, in rough order of how often we reach for them:

Hetzner Germany

The German Hetzner is the spiritual home of cheap, reliable European VPS hosting. Hetzner Cloud regions in 2026 are Nuremberg, Falkenstein, and Helsinki in Europe, plus Hillsboro (Oregon) and Ashburn (Virginia) in the US, and Singapore in Asia. Entry-level Hetzner Cloud (CX22: 2 vCPU, 4GB RAM, 40GB SSD) starts at around €3.79/month, billed in EUR with hourly metering and a monthly cap. Hetzner Dedicated runs out of Falkenstein and Nuremberg with significantly more spec per euro than the cloud product, suitable for high-traffic Woo stores or database-heavy workloads.

For a SA site on Hetzner Germany, the origin sits in Europe and Cloudflare's Cape Town, Johannesburg, and Durban POPs absorb the bulk of the page views. For an international client whose audience is in Europe, Hetzner Germany is often simply the right answer with or without Cloudflare.

NetCup

NetCup is the value-conscious alternative to Hetzner Cloud. Founded in 2003, headquartered in Karlsruhe, datacentres in Nuremberg and Vienna. VPS plans start at around €3.99/month for 2 vCPU, 4GB RAM, and 128GB SSD (more disk than the equivalent Hetzner Cloud at a similar price). The Root Server line (RS) gives you dedicated CPU cores rather than shared, with the RS 1000 G12 at €8.74/month offering 4 dedicated AMD EPYC 9645 cores, 8GB DDR5 ECC RAM, 256GB NVMe, and 2.5 Gbps networking.

NetCup's billing model is monthly contracts (not hourly), and the entry-level plans are tied to Nuremberg, with Vienna and Amsterdam available on higher tiers. The 99.6% annual uptime guarantee is lower than Hetzner Cloud's, but in practice we have not seen a meaningful uptime difference between the two on production WordPress workloads.

For sites that need real dedicated cores at a low price (which is where NetCup beats Hetzner Cloud most clearly), the RS line is hard to ignore. For pure shared-cloud workloads the two are close enough that it usually comes down to control panel preference.

Vultr (international regions)

Vultr's 30+ datacentres cover Frankfurt, London, Paris, Amsterdam, Stockholm, Warsaw, and Madrid in Europe; New York, Chicago, Dallas, Seattle, Los Angeles, Atlanta, Silicon Valley, Toronto, Miami, and Mexico City in North America; plus Singapore, Tokyo, Seoul, Mumbai, Bangalore, Delhi, Osaka in Asia and several others.

The Johannesburg region we covered under Option 2 is the same Vultr product, just the SA-local datacentre. For international clients, picking a Vultr region close to the audience is the simple, predictable choice. The product is essentially the same as Hetzner Cloud (root access, API, snapshots, instant scaling) at slightly higher prices but with vastly broader geographic coverage. Vultr High Performance instances run a typical Woo store comfortably from $12-$24/month per region.

The Cloudflare layer

All three of these international VPS options work for SA visitors only when Cloudflare is properly configured in front. Cloudflare has POPs in Cape Town, Johannesburg, and Durban, plus Cairo, Luanda, Mombasa, and Djibouti across the rest of the continent. For cached content (which on a competently configured WordPress site is the vast majority of page views) the South African visitor never hits the origin. They hit the nearest Cloudflare POP, which is faster than any origin host in the country.

For cache misses (dynamic Woo cart, logged-in admin, checkout), the request goes to the origin in Europe and pays the 170-200ms tax. Whether that matters depends on what those uncached requests are: a shopper hitting the cart page once is fine, but if every checkout step is a cache miss and they pay 200ms per step, the checkout feels sluggish.

Where this combination wins

A Hetzner Germany cloud box at €5/month gets you significantly more spec than a comparably-priced xneelo Cloud box. The same applies to NetCup. Add Cloudflare's free or pro tier and you have an edge network that serves most of your traffic faster than any SA local host could.

For a content site (blog, brochure, news, SaaS marketing), this is usually the right pattern in 2026 regardless of where the audience sits. Most pages are cached at the edge. The origin is cheap and far away. The visitor never notices the geography.

Where this combination breaks

Real-time, logged-in, commerce-heavy. WooCommerce checkout pages cannot be cached at the edge for the visitor's session. Every cart interaction is a round trip to the origin. If your origin is in Frankfurt and your buyer is in Cape Town, that is 200ms per interaction. The visitor notices. Cart abandonment goes up.

For a high-volume Woo store with a SA-heavy audience, an international origin is the wrong shape. xneelo Cloud, xneelo Dedicated, AWS Cape Town, or Vultr Johannesburg are the right shapes. For an international audience or a content-heavy site, the international VPS plus Cloudflare combination is hard to beat.

When this combination is the right call

Content-heavy site, regardless of audience region. Sites with mixed or international audiences. Sites where the customer base has shifted, post-launch, from local to international. Sites where ZAR billing is not a constraint and EUR or USD billing is fine. Teams comfortable configuring Cloudflare cache rules properly (which is more involved than the default settings suggest, and we have written about Cloudflare and WP Rocket configuration elsewhere).

Other providers worth mentioning, and a couple worth avoiding

The three options above cover the patterns we actually deploy onto. The four providers below come up in almost every client conversation, so it is worth saying clearly where we land on each.

Domains.co.za (worth considering, SA-local)

Domains.co.za is the realistic alternative to xneelo at the entry tier. They have been running since 2001, host out of Teraco Isando in Johannesburg (which is the premier neutral SA datacentre, also home to NAPAfrica), and their WordPress packages run from R119 to R499 per month. The hosting is positioned as a performance-optimised shared product, not a managed WordPress stack.

What we like: NVMe storage on all WordPress plans, SSH, WP-CLI, SFTP, and Git access included (which xneelo does not give you on its equivalent shared tier), free migration from another host, free SSL, free .co.za domain on selected tiers, 99.9% uptime guarantee, and the Teraco-Isando location which gives genuinely good peering to other SA networks.

Where it stops: same general ceiling as any shared hosting product. No object cache. No real PHP-FPM control. For a small SA business that wants WP-CLI access and a cleaner developer experience than xneelo shared, Domains.co.za is a legitimate pick. For serious WooCommerce or membership workloads, you outgrow it quickly.

Kinsta (worth considering, premium managed)

Kinsta sits in a different price tier from everything else on this list. They run managed WordPress hosting on Google Cloud, billed in USD from $35/month for the Starter plan (1 site, 25K monthly visits, 10GB storage), through $70/month Pro, $115/month Business 1, and up to enterprise plans north of $675/month.

What you pay for: Cloudflare Enterprise CDN included on every plan (which on its own retails at thousands per month), Google Cloud's C2 and C3D compute-optimised VMs as the underlying compute, daily backups, free staging environments, and 24/7 support from WordPress-focused engineers who will actually fix things rather than reading a script. Free site migrations are part of every plan.

The catch for SA-anchored sites: Google Cloud does not have a Johannesburg region in 2026, so Kinsta's closest region for a SA-audience site is typically Frankfurt or London. The Cloudflare Enterprise CDN absorbs most of this for cached content, but logged-in and checkout requests still pay the transatlantic round trip. Kinsta is a strong fit for SA businesses whose audience is international, or for SaaS marketing sites, or for any team that wants the hosting layer simply taken off their plate. It is overkill for a brochure site.

Afrihost (not recommended for serious WordPress)

Afrihost is the SA hosting brand most clients will mention because of its consumer marketing presence (ISP, mobile, hosting). Hosting starts at R79/month for shared. Their datacentres are in Johannesburg. They won MyBroadband's Best Hosting Provider award in 2025, which reflects their consumer brand strength rather than their suitability for serious WordPress workloads.

We do not host or recommend Afrihost for WordPress. The technical reasons are concrete: their managed WordPress offering is limited compared to xneelo's or Domains.co.za's; they use a proprietary control panel rather than cPanel or industry-standard tools, which makes migration to a better host harder than it needs to be; they lack the caching, object cache, and CDN integration that production WordPress needs; and their TrustPilot score is 1.3 out of 5 from over 270 reviews, which is not a number we feel comfortable sending clients toward.

For a personal blog or low-stakes brochure site where the owner already has an Afrihost account, leaving it there is fine. For anything we would put our retainer behind, we move it.

GoDaddy (not recommended for any WordPress)

GoDaddy is the global elephant in the room. They market hard, they upsell hard, and they have a long history of WordPress hosting that ranges from mediocre to actively harmful. Out-of-box WordPress load times are typically 3-4 seconds even on their managed WordPress plans, and server response degrades sharply (over 1 second under 1,500 concurrent visitors) because the underlying infrastructure is sized for marketing margin, not throughput.

There is no built-in CDN integration on standard plans. The company has a documented history of security breaches affecting WordPress customers. Renewal pricing climbs steeply from the introductory rate, often quietly. Customer support tends to push solutions that require buying more GoDaddy products rather than fixing the underlying issue.

We have migrated many WordPress sites off GoDaddy, and rarely the other direction. If a client is on GoDaddy and the site is working, the question is when (not whether) to move it. We typically recommend xneelo or Domains.co.za for SA-anchored clients, and Hetzner Germany or NetCup with Cloudflare for international clients.

What we actually recommend, by site type

We see enough WordPress sites to recognise the patterns. Here is what we typically recommend, covering both SA-anchored and international clients.

The bigger picture: hosting decisions follow audience geography and stack maturity. Move the origin closer to the visitors. Run the stack at the level of engineering investment you can actually sustain.

What the audit usually finds

When we audit a WordPress site, the hosting layer is one of the first things we look at. Common findings across our SA and international clients:

• PHP version one or two majors behind, on a host that lets you upgrade with one click. Nobody clicked.
• Shared hosting plan that has been the right shape since 2019 but the site has tripled in traffic since then. The host is now the ceiling.
• VPS sized for peak load three years ago, costing 3x what a current-sized VPS would cost.
• Origin in Frankfurt, audience 80% South African, no edge caching configured. Every visitor pays a 200ms tax that did not have to exist.
• Origin in Cape Town, audience 70% United States, no CDN. Every visitor pays a 250ms tax that did not have to exist.
• Origin in us-east-1, audience 60% European, no edge caching. Same problem, different geography.

These are all fixable in an afternoon. The first step is knowing which one applies to your site.

Related reading

• PHP-FPM Tuning for WordPress: Stop Guessing, Start Measuring. The single biggest performance variable on a VPS-hosted WordPress site, regardless of which host you pick.
• WP Rocket and Cloudflare: how to configure them so they actually work together. The edge caching half of the international-host strategy.
• Redis Object Cache for WordPress: what it actually does (and when it doesn't help). Object caching is available on xneelo Cloud, AWS Cape Town, Vultr, Hetzner, and NetCup. It is not available on xneelo shared.
• WordPress Slow After 2 Years? Here's What's Actually Wrong. When the host is fine and the site is still slow, this is usually why.