Skip to content

For WooCommerce

WooCommerce hosting that doesn't meter your visits

Run WordPress and WooCommerce on a real VM, push product media to S3-compatible storage and serve the catalogue from 988 locations. Checkout gets dedicated CPU and the bill stays flat on launch day.

Free to sign up. No egress fees on any product.

Why WooCommerce on Edge

Checkout on dedicated CPU, media in a bucket

Everything the managed WooCommerce hosts sell you, on hardware your store has to itself.
  • Real CPU for checkout

    Cart and checkout queries run on dedicated vCPUs and local NVMe, not a pool shared with fifty other stores.
  • Media in a bucket

    WP Offload Media moves wp-content/uploads to Edge Storage. The catalogue grows to terabytes; the VM disk doesn't.
  • Product images from the URL

    Stop generating six thumbnails per variant. Ask for ?width=600&format=auto and the CDN resizes, converts and caches.
  • Cache guests, not carts

    Guest catalogue pages and every asset cache in 988 locations. Only carts, checkout and logged-in customers reach the VM.
  • MySQL next door

    The WordPress script installs MySQL alongside PHP. Move it to its own VM on a private network when orders outgrow it.
  • Launch day, same bill

    No metered visits, no per-order fees, no per-GB egress. A VM, a CDN deployment and a bucket, sized to your store.

Reference architecture

One LEMP VM, with guests and media offloaded

A standard LEMP stack with WooCommerce on top. Media lives in a bucket, guests are served from the CDN, and checkout stays safely at origin.
  • Compute

    Runs WordPress, WooCommerce, Nginx, PHP-FPM and MySQL on one VM.

  • Storage

    Holds wp-content/uploads: product galleries, variant images and downloadable goods.

  • CDN

    Caches guest catalogue pages, theme assets and every media URL worldwide.

  • Image optimisation

    Responsive product images from one master: resize, crop, AVIF and WebP.

  • DNS

    Anycast DNS for the apex, www and your email records.

  • Shield

    Scores order and signup posts so card-testing bots never reach the gateway.

  • Assist

    Answers sizing, shipping and returns questions from your store content.

  • Pulse

    Multi-step checks on the add-to-cart and checkout path from real user locations.

Deploy

From empty VM to taking orders

The WordPress library script does the heavy lifting. After that it's one plugin, one config file and a CDN domain.
  1. 01

    Create the VM with the WordPress script

    Nginx, MySQL, PHP-FPM and WP-CLI are installed on first boot. Leave db_password out and one is generated for you.

    shell
    $ edge compute create --name shop --size s-4vcpu-8gb \
        --image ubuntu-24 --region london --script wordpress \
        --script-param site_title="Acme Shop" \
        --script-param admin_email=ops@acme.com
  2. 02

    Install WooCommerce and the media offloader

    Run WP-CLI from the WordPress root. New VMs come with the firewall on; the default allow-web group opens 80 and 443.

    shell
    # on the VM, from the WordPress root
    $ wp plugin install woocommerce --activate --allow-root
    $ wp plugin install amazon-s3-and-cloudfront \
        --activate --allow-root
  3. 03

    Offload media to Edge Storage

    A must-use plugin sets the bucket and points the S3 client at Edge Storage. Existing uploads can be offloaded from the plugin screen.

    wp-content/mu-plugins/edge-storage.php
    <?php
    define('AS3CF_SETTINGS', serialize([
        'provider'          => 'aws',
        'access-key-id'     => '<edge-access-key>',
        'secret-access-key' => '<edge-secret-key>',
        'bucket'            => 'shop-media',
        'copy-to-s3'        => true,
        'serve-from-s3'     => true,
    ]));
    
    add_filter('as3cf_aws_s3_client_args', function ($args) {
        $args['endpoint'] = 'https://storage.edge.network';
        $args['use_path_style_endpoint'] = true;
        return $args;
    });
  4. 04

    Put the CDN in front

    Then tell your caching plugin to skip /cart, /checkout, /my-account and any request carrying a woocommerce_items_in_cart cookie.

    shell
    $ edge cdn create --name acme-shop
    $ edge cdn domains add cdn-a1b2c3 \
        --domain shop.acme.com \
        --origin https://<vm-ip> \
        --jit-image

Prefer to hand it off? Give the job to your AI agent or have our engineers do it.

What it costs

What 250k visits a month costs

Managed WooCommerce plans meter visits and charge more as you grow. Here the same store is one VM, one CDN deployment and a bucket.
  • No visit caps and no per-order fees
  • Image resizing included with the CDN
  • Payment fees stay between you and your gateway
  • Billed hourly from a prepaid balance
See compute pricing

Estimated monthly bill on Edge

~250k visits a month, 2,000 SKUs and 500 GB of image bandwidth

USD
  • Compute$38.47Performance VM: 4 vCPU, 8 GiB, 160 GB NVMe
  • CDN$1.004.5M requests: first 500k free, then 4M × $0.25 per million
  • Storage$0.6045 GB of product media: first 5 GB free, then 40 GB × $0.015
  • Snapshots$1.0020 GiB of pre-update VM snapshots at $0.05/GiB-mo
  • DNS + Shield$0.00Zone, records and checkout bot checks
  • Egress$0.00
Total$41.07

Indicative monthly cost for ~250k visits, 2,000 SKUs and 500 GB of images

  • Managed WooCommerce (WP Engine eCom)~$200–500
  • Shopify Advanced + apps~$400+
  • Edge (VM + CDN + Storage)~$30–70

Indicative figures based on public pricing. Payment processing fees are not included anywhere.

FAQ

WooCommerce on Edge, answered

Something else? Ask an engineer.
Will my payment gateway work?
Yes. Stripe, PayPal, GoCardless, Klarna, Mollie and the rest run client-side or server-to-server, so they behave exactly as they do on any other LEMP host.
How does this compare to managed WooCommerce hosts?
You get dedicated CPU and NVMe, no visit caps, no transaction fees on top of your gateway, and root access. The trade-off is a bootstrap script instead of a fully managed console, or our Expert Services team runs it for you.
How do I cache HTML without caching carts?
Use W3 Total Cache, WP Rocket or similar to bypass the cache for logged-in users, cart, checkout and account pages, and for any request with a WooCommerce cart cookie. The CDN serves guest pages; everything personal goes to the VM.
What about large catalogues?
Media sits in Storage, so the VM disk only holds code and the database. Scale the VM up as order volume grows, then split MySQL onto its own VM over a private network when you need to.
Does Action Scheduler keep up?
Swap WP-Cron for a real system cron on the VM so scheduled actions, webhooks and emails run on time, not only when a visitor happens to load a page.

Bring your WooCommerce store over

Start free and migrate one store. See the speed and the bill before you move anything else.

Free tiers hard-cap. Nothing bills until you add a card.