Overview
Edge CMS treats Markdown files in a Git repo as the source of truth. Each deploy is a static bundle cached on the CDN, and incremental content is served from a Turso SQLite database reachable from every edge region. Editor changes propagate in under 50ms anywhere on Earth.
Problem
Most git-based CMSs need a full site rebuild before readers saw a typo
fix. The team wanted editorial speed without abandoning their beloved
git log.
Approach
- A
Postgres → Litesync job keeps read replicas small enough to fit on each edge node. - An Edge Function reads the closest replica, falls back to a static HTML render for anonymous traffic.
- The admin UI posts write hooks that trigger both a git commit and a row upsert — readers see updates before the build even finishes.
The CDN cache becomes a stale snapshot you can warm on demand.
Outcome
- Median TTFB: 38ms across 8 regions (was 240ms on a serverless build).
- Editorial team doubled output — no more “wait for the build” pause.
