P

Payload Stack

Turso + Nuxt

CMS Admin

Scale-to-zero architecture

Publish once, serve fast everywhere.

Payload wakes on demand in Fly.io, writes to Turso, and triggers a Cloudflare Pages build. The site ships as SSG through the CDN, while R2 stores media with on-demand processing.

Release summary

Stack pulse

live

CMS

Payload on Fly.io

Sleeps until an editor signs in.

Storage

Turso + R2

libSQL writes and CDN-ready media.

Delivery

Cloudflare Pages

SSG deploys on publish with hooks.

Stories

Latest posts

SSG feed
No posts published yet. Publish one in Payload to see it here.

Architecture

How it flows

1. CMS wakes

Fly.io auto-starts Payload when editors open the admin panel.

2. Content commits

Turso persists entries via libSQL while R2 keeps media close to the edge.

3. CDN refresh

A deploy hook triggers Cloudflare Pages to rebuild the static site.

Notes

Ready for the next publish.

Keep Payload and Pages connected with a deploy hook. Every publish stays fast, fresh, and cost-aware.

Launch editor