Edge
WordPress logo

For WordPress

WordPress hosting
without the visit caps

A real VM, an S3-compatible media library, a global CDN with zero egress fees and on-the-fly image optimisation. Faster than the managed WP hosts, at a fraction of the price.

# Spin up a VM with WP + LEMP + MySQL

$ edge compute create \

--image ubuntu-24-04 --plan small \

--script ./bootstrap-wordpress.sh

# Offload uploads to Edge Storage

define('AS3CF_SETTINGS', serialize([

'provider' => 's3',

'access-key-id' => '...',

'bucket' => 'wp-uploads',

]));

# Front it with the CDN

$ edge cdn create example.com \

--origin https://<vm-ip>

Why move WordPress to Edge

Take the managed-WP performance promise — and actually deliver on it, for a fraction of the bill.

Faster than managed WP hosts

Dedicated vCPU and NVMe storage on a real VM, fronted by a global CDN. None of the noisy-neighbour problems of cheap shared WordPress.

S3 media library

Use a Media Cloud / WP Offload Media plugin to store uploads in Edge Storage. Survive any VM restore, scale to terabytes.

Image optimisation built-in

Skip the bloated optimisation plugins — Edge resizes, crops and converts to AVIF/WebP at the CDN. Faster site, fewer plugins.

CDN, SSL and DDoS-resistant

Global anycast CDN with automatic SSL. Soaks up traffic spikes so your origin VM stays calm and your editor experience stays fast.

Predictable bills

No metered visit limits, no per-GB egress, no "burst" upcharges. A small VM, a CDN deployment and a bucket — all known up front.

MySQL on the same box

Run MariaDB or MySQL on the same VM for low-latency queries. Move it to a separate VM the day you need to scale, no migration drama.

Reference architecture

How WordPress maps to Edge

Standard LEMP stack on a VM, uploads offloaded to S3-compatible storage, CDN out front. Boring on purpose — and that's the point.

Compute

Runs WordPress + Nginx + PHP-FPM (and MySQL) on a VM

Storage

Stores wp-content/uploads via WP Offload Media or similar

CDN

Caches HTML for guests, all static assets, and media URLs

Image Optimization

On-the-fly responsive images straight from the bucket

DNS

Anycast DNS for the apex, www and email records

Indicative cost

A busy WordPress site

~500k monthly visits, 250GB image bandwidth, WooCommerce

WP Engine / Kinsta ~$200–400
Cloudways + media offload ~$80–160
Edge (VM + CDN + Storage) ~$25–50

Indicative figures. Your usage will vary.

Common questions

Will my plugins still work?

Yes — this is a standard LEMP stack. Anything that works on a normal Linux VPS or a managed WordPress host works here, including WooCommerce.

How does this compare to WP Engine / Kinsta?

Cheaper, faster (real CPU on a real VM), no visit caps, no egress fees, and you keep root access. The trade-off is that you handle the OS — or we can quote our Expert Services team to manage it.

How do I cache HTML?

Use a plugin like W3 Total Cache or LiteSpeed Cache to generate static HTML, then let the Edge CDN serve it for guests. Logged-in users hit the origin as usual.

What about backups?

Use Edge Compute snapshots for the VM and an Edge Storage bucket for offsite database dumps and media — both fully automatable.

By Stack

Other stacks on Edge

View all stacks →

Faster WordPress, smaller bill

Run the trial. Migrate one site. See the speed and savings before you commit anything else.