Supabase + Cloudflare D1: edge-runtime databases — full-stack Postgres vs global SQLite

3 sources

Supabase (RLS 2.0 + Realtime GA improvements + Edge Functions cold-start improvements) and Cloudflare D1 (global SQLite + read replicas + Time Travel) are two edge-runtime database surfaces that ship milestones in the same week. They represent two bets on edge-runtime databases: Supabase on full-stack Postgres with auth + RLS + realtime; D1 on global SQLite with read replicas + Time Travel. The two are not equivalent: Supabase ships the full Postgres feature surface; D1 ships the global-replica surface but trades Postgres features for SQLite simplicity.

Why now

Both shipped in the same week — edge-runtime databases are now a buyer-side market with two distinct bets.

Why it is worth publishing

Demo potential: side-by-side of the same edge-runtime workflow on Supabase vs D1, measuring cold-start and global-replica latency.

Evidence basis

Two independent vendor primary sources + The Decoder weekly roundup

“Supabase and Cloudflare D1 both shipped milestones this week — and together they make edge-runtime databases a buyer-side market: full-stack Postgres with RLS vs global SQLite with read replicas + Time Travel.”

Angle

Frame the two as 'full-stack Postgres with RLS vs global SQLite' — pick based on whether the workload needs Postgres features (Supabase) or global-replica + Time Travel (D1).

Format

Long-form explainer

Demo idea

Record a 10-minute explainer: 3 min intro on 'full-stack vs global' framing, 3 min on Supabase (RLS 2.0 + Edge Functions cold-start), 3 min on D1 (global SQLite + read replicas + Time Travel), 1 min on the bet comparison.

Platform notes

Specific Realtime quotas, Edge Function cold-start numbers, and D1 query performance benchmarks beyond the captured summary are not extracted; confirm specific surface details against the underlying vendor docs before stating them on the record.

Usable claims

Supabase shipped RLS 2.0 (simplified policy authoring with helper functions), Realtime GA improvements (presence broadcast + authorization hooks), Edge Functions cold-start improvements.
Cloudflare shipped D1 GA — global SQLite with read replicas, 5x query performance improvement, D1 Time Travel (point-in-time restore within last 30 days).

Evidence pipeline

From the news

Breakdown

Supabase ships the full Postgres feature surface with RLS + auth + realtime; D1 ships global SQLite with read replicas + Time Travel. This explainer uses the full-stack-vs-global framing as the lens for picking an edge-runtime database, rather than treating 'edge database' as a single category.

Sources

Risks

Use The Decoder and IT之家 as media-type corroboration, but read the underlying vendor docs for any specific performance claim or pricing before stating it on the record. Verify specific capability claim against the underlying vendor docs and the actual license / pricing matrix before stating it on the record; do not paraphrase per-platform pricing or license terms into specific dollar figures or commercial-use clauses.
Vendor docs confirm feature existence but specific pricing and limits beyond the captured summary are not in this pass. Verify specific capability claim against the underlying vendor docs and the actual license / pricing matrix before stating it on the record; do not paraphrase per-platform pricing or license terms into specific dollar figures or commercial-use clauses.

Demo ideas

Side-by-side edge-runtime workflow: Supabase vs D1, measure cold-start and global-replica latency.
Bet matrix: full-stack vs global — plot each surface on Postgres features vs SQLite simplicity vs global-replica surface.
Migration story: 'migrate from D1 to Supabase', measure porting work and surface delta.