For Static Sites

Static sites,
edge-delivered

Hugo, Eleventy, Jekyll, Astro, Zola — any SSG, served from a global CDN with zero egress fees. No origin server, automatic SSL, and on-the-fly image transforms when you need them.

Start your trial Read the deploy guide

# Build

$ hugo # or eleventy, jekyll, astro…

# Sync to Edge Storage

$ aws s3 sync ./public s3://my-site \

--endpoint https://storage.edge.run \

--delete

# Front it with the CDN

$ edge cdn create example.com \

--origin s3://my-site

# Purge after each deploy

$ edge cdn purge example.com

✓ Live, globally cached, ~$3/month

Bring any SSG you like

If it produces a folder of static files, it runs on Edge.

Hugo

Tens of thousands of pages in seconds

Eleventy (11ty)

Markdown, Nunjucks, Liquid

Jekyll

Classic Ruby SSG, GitHub Pages compatible

Astro

Component islands, partial hydration

Hexo

Node-based blogging

Pelican

Python-powered static sites

Zola

Single-binary Rust SSG

mdBook / VitePress / Docusaurus

Docs sites

Why static sites belong on Edge

Cheap, fast, durable. The web's original deployment model — done right.

No origin server

Static sites need no VM at all. Push the build to a Storage bucket, point a CDN deployment at it, you're live globally.

Global CDN, zero egress

Every page served from the edge location nearest your visitor — and never a per-GB egress bill on your way out.

On-the-fly image transforms

Stop pre-generating six sizes of every image at build time. Edge Image Optimization resizes from a URL, on demand.

CI-friendly deploys

Build in GitHub Actions or anywhere else, sync the output to Edge Storage with the AWS CLI, purge the CDN. Done.

Pennies per month

A bucket and a CDN deployment. Most static sites cost a few dollars a month — even at serious traffic volumes.

Automatic SSL

Bring your own domain, get a free SSL certificate, end-to-end TLS. No certbot, no renewals to track.

Reference architecture

How a static site maps to Edge

Two products, no servers. The simplest deployment story we offer.

Storage

Holds the built site bundle (HTML, CSS, JS, images)

CDN

Serves the entire bucket from edge locations worldwide

Image Optimization

On-the-fly transforms instead of build-time pre-generation

DNS

Anycast DNS for the apex, www and any preview branches

# .github/workflows/deploy.yml

on: { push: { branches: [main] } }

jobs:

deploy:

runs-on: ubuntu-latest

steps:

- uses: actions/checkout@v4

- run: hugo --minify

- run: |

aws s3 sync public s3://$BUCKET \

--endpoint $EDGE_ENDPOINT --delete

- run: |

curl -X POST $EDGE_API/cdn/.../purge \

-H "Authorization: Bearer $TOKEN"

Common questions

Which SSG is supported?

All of them. If your generator produces a folder of HTML, CSS and JS, we can serve it. Hugo, Eleventy, Jekyll, Astro, Hexo, Pelican, Zola, Docusaurus, VitePress, mdBook — all fine.

How do I deploy from CI?

Build the site in your CI of choice, then `aws s3 sync ./public s3://your-bucket --endpoint https://storage.edge.run --delete`, then trigger a CDN purge via the Edge API.

What about responsive images?

Skip the build-time image gymnastics. Push originals to Storage, link them through Edge Image Optimization with `?w=` query params for responsive `srcset` markup. Build times drop dramatically.

Can I do per-PR previews?

Yes — sync each branch build to a `branch-name/` prefix in the bucket, alias a `branch.preview.example.com` subdomain to it, tear it down on PR close.

By Stack