Ranked and reviewed
Cloudflare Workers is a fundamentally different runtime. Kits ported from Vercel-native templates struggle. Here are the three actually built for the edge.
2026-07-01
I deployed 12+ production apps on Cloudflare Workers before the ecosystem was mainstream. I know the runtime quirks: no Node.js APIs, streaming response edges, D1 eventual consistency. When reviewing Cloudflare SaaS kits, I filtered out Next.js templates adapted via Cloudflare adapter—those hit runtime edge cases constantly. The three below are genuinely Workers-native, using D1/R2/KV as first-class citizens, not afterthoughts.
Built from day one for Cloudflare — Workers + D1 + R2 + KV + Queues. Not ported. Edge cold starts under 5ms globally.
Best For Founders committed to the Cloudflare stack.
Not For Vercel loyalists.
Free community-maintained Cloudflare Workers SaaS starter. Barebones but genuinely edge-native — useful for learning the platform end-to-end.
Best For Learning Cloudflare Workers end-to-end.
Not For Founders trying to launch fast.
Some teams take ShipFast/Makerkit and deploy through the Cloudflare Next.js adapter. Works, but you fight runtime differences constantly.
Best For Teams already committed to a Next.js kit.
Not For Anyone starting fresh.
The runtime differences from Node/Vercel are significant. Most kit authors optimize for the biggest market (Vercel).
Yes, via the adapter — but you'll hit edge cases with Node APIs and streaming.
D1 hit GA in 2024 and is production-ready. TanStack Ship uses it in production.
Yes, significantly at scale. See our Cloudflare Workers vs Vercel guide.
Clerk, Better Auth, or Auth.js all work on Workers. TanStack Ship uses a Better Auth-based approach.
If you're evaluating SaaS boilerplates, see it running. Pricing starts at $99.