For WooCommerce
WooCommerce hosting
without the gotchas
Self-host the world's most popular store on a real VM with S3-compatible product imagery and a global CDN. Faster checkout, no visit caps, zero egress fees.
# Bootstrap WooCommerce on a VM
$ edge compute create \
--image ubuntu-24-04 --plan small \
--script ./bootstrap-woocommerce.sh
# Offload media to Edge Storage
define('AS3CF_SETTINGS', serialize([
'provider' => 's3',
'access-key-id' => '...',
'bucket' => 'shop-media',
'endpoint' => 'https://storage.edge.run',
]));
# Front the store with the CDN
$ edge cdn create shop.example.com \
--origin https://<vm-ip>
Why merchants move to Edge
All the platform polish of premium WP/WC hosts, with hardware your store actually owns.
Real CPU for checkout
A dedicated VM means cart and checkout queries don't fight for resources with 50 other stores. Faster pages = better conversion.
S3 media library
Use WP Offload Media (or similar) to push product images and uploads to Edge Storage. Catalogue scales to terabytes without bloating your VM.
On-the-fly product imagery
Skip pre-generating six sizes of every variant — Edge Image Optimization resizes from a URL. Faster builds, smaller storage, snappier galleries.
Global CDN, zero egress
Cache catalogue HTML for guests, all static assets and Storage URLs globally. Your origin VM only sees logged-in users and checkout traffic.
MySQL on the same network
Run MariaDB on the same VM for cart-write latency you can't get on a SaaS host. Move it to a dedicated VM the day you outgrow that — same private network.
Predictable bills, even on launch day
No metered visit caps, no per-order fees, no per-GB egress. A small VM, a CDN deployment and a bucket — sized to your store, not their spreadsheet.
Reference architecture
How WooCommerce maps to Edge
Standard LEMP + WooCommerce stack, media offloaded, catalogue cached at the edge, checkout safely at origin.
Runs WordPress + WooCommerce + Nginx + PHP-FPM (and MariaDB) on a VM
S3-compatible bucket for `wp-content/uploads` (product images, downloads)
Caches static assets, catalogue HTML for guests, and Storage URLs
On-the-fly responsive product images, AVIF/WebP, smart cropping
Anycast DNS for the apex, www and email records
Indicative cost
A growing online store
~250k monthly visits, 2,000 SKUs, 500GB image bandwidth
Indicative figures. Payment processing fees not included anywhere.
Common questions
Will my payment gateway work?
Yes — WooCommerce gateways (Stripe, PayPal, GoCardless, Klarna, Mollie, etc.) are all client-side or server-to-server. No special infrastructure required, they'll work the same as on any other LEMP host.
How does this compare to dedicated WP/WC hosts?
Cheaper and faster (real CPU on a real VM with NVMe), no visit caps, no transaction fees on top of your gateway, and you keep root. Trade-off: one bootstrap script (or our Expert Services) instead of a fully managed control panel.
How do I cache HTML safely?
Use a plugin like W3 Total Cache, LiteSpeed Cache or WP Rocket to bypass cache for logged-in users, cart pages and checkout. The Edge CDN serves the cached guest HTML; everything else hits origin.
What about huge catalogues?
No problem. Storage is unlimited, the CDN handles delivery, and you can scale the VM vertically (or split MySQL onto its own VM) as the catalogue grows. We have customers running 100k+ SKUs.
By Stack
Other stacks on Edge
Move your store to Edge
30-day trial. Migrate one store, see the speed and savings before you commit anything else.