Craft CMS hosting, production-grade and predictable

Deploy

Craft on Edge in five steps

The Craft deploy you already know, with Edge Storage for assets and the CDN in front.

~/acme-agency — zsh

$ edge compute create --name craft \

--size s-2vcpu-4gb --script lemp \

--image ubuntu-24 --region london

✓ vm-9a0c4e running · 64.34.86.52

$ composer install --no-dev

$ php craft up

✓ Migrations run · project config applied

$ edge cdn domains add cdn-a1b2c3 \

--domain acme.agency --jit-image \

--origin https://64.34.86.52

Per-view fees$0

acme.agencyLive

Craft5 · PHP-FPM 8.3

AssetsS3 → acme-assets

1. 01

   Create the VM and the asset bucket

   The lemp script installs Nginx, MySQL 8 and PHP 8.3, which covers Craft 5's PHP 8.2+ requirement.

   shellCopy

   $ edge compute create --name craft --size s-2vcpu-4gb \
       --image ubuntu-24 --region london --script lemp
   
   $ edge storage create acme-assets

2. 02

   Configure an S3-compatible filesystem

   Craft's first-party Amazon S3 plugin has no custom endpoint setting, so use an S3-compatible filesystem plugin and reference these variables in Settings → Filesystems.

   .envCopy

   EDGE_KEY="..."
   EDGE_SECRET="..."
   EDGE_BUCKET="acme-assets"
   EDGE_REGION="us-east-1"
   EDGE_ENDPOINT="https://storage.edge.network"
   EDGE_ASSETS_URL="https://assets.acme.agency"

3. 03

   Deploy the Craft way

   Pull, install, apply migrations and project config, then clear the CDN. Wrap it in CI or point Forge or Envoyer at the VM.

   shellCopy

   $ git pull && composer install --no-dev
   $ php craft up
   $ php craft clear-caches/all
   $ edge cdn purge cdn-a1b2c3

4. 04

   Put the CDN in front

   One domain for the site, one for assets with image transforms switched on.

   shellCopy

   $ edge cdn create --name acme-agency
   $ edge cdn domains add cdn-a1b2c3 \
       --domain acme.agency --origin https://<vm-ip>
   $ edge cdn domains add cdn-a1b2c3 \
       --domain assets.acme.agency --jit-image \
       --origin-type storage --storage-bucket acme-assets

5. 05

   Serve transforms from the CDN

   Append parameters to the asset URL. Native transforms still work where you'd rather keep them.

   templates/_partials/hero.twigCopy

   {% set image = entry.heroImage.one() %}
   <img
     src="{{ image.url }}?width=1200&format=auto"
     srcset="{{ image.url }}?width=800&format=auto 800w,
             {{ image.url }}?width=1600&format=auto 1600w"
     alt="{{ image.alt }}"
   >

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