Better Auth
Verified sessions, magic links, social providers, recovery, onboarding, and platform roles.
Cloud-native SaaS foundation
Build the product. Skip the platform work.
Authentication, workspaces, projects, billing, content, feedback, AI, email, media, and realtime—built on React Router, TanStack Query, Better Auth, and Cloudflare D1.
Workers-native · Tenant-safe · Retryable by default
Revenue$24.8k
Workspaces1,284
Active users8,492
Acme product launch
ReviewPending approval
Q3 onboarding refresh
ActiveUpdated 12 minutes ago
A modern stack with deliberately boring boundaries
React 19React RouterTanStack QueryBetter AuthCloudflareDrizzle
One coherent platform
Every foundation your product team should not have to rediscover.
Each capability is implemented as a real workflow with explicit ownership, observable failure states, and Workers-compatible request handling.
Cloudflare D1
Forward-only migrations, tenant-scoped data, tested triggers, and full-text search.
Queues + outbox
Versioned messages, leases, retries, idempotency, dead letters, and scheduled recovery.
Cloudflare R2
Authorized uploads, durable object keys, lifecycle cleanup, and public content media.
Durable Objects
Authenticated WebSockets fan out project, notification, and cache invalidation events.
Ultimate surface
Billing, CMS, feedback, roadmap, docs, notifications, AI, email, and administration.
Composable integrations
Use the providers you already trust.
Stripe, Resend, OpenAI, Unkey, Google, GitHub, and Twitter sit behind small adapters and idempotent jobs.
StripeResendOpenAIUnkeyGoogleGitHub
“The best starter is not the one with the most folders. It is the one whose invariants still hold after the product becomes real.”
Start with the right boundary
Choose how much platform you want to own.
Starter
Open source
Core Workers architecture, identity, D1 schema, tenant authorization, jobs, media, and deployment primitives.
Read the quickstartUltimate parity
Production-ready
The complete customer, administrator, content, billing, feedback, notification, AI, and operations surface.
Start buildingCustomize
Own the stack
Replace provider adapters, extend projections, and ship domain features without surrendering your data model.
Review boundariesBuilt for teams with a roadmap
Less platform risk. More product momentum.
The tenant boundary is explicit everywhere. That is the difference between a demo and a foundation I can trust.
We started on product flows instead of rebuilding auth, billing webhooks, invitations, and background jobs.
Workers compatibility is the default, not a deployment patch at the end of the project.
Questions, answered
Designed to be understood before it is customized.
Is this a Next.js application?
No. React Router renders directly on Cloudflare Workers. TanStack Query manages client caching, and loaders/actions own request-time data.
Does D1 replace every Supabase capability?
The product behavior is preserved through explicit D1 authorization, triggers, Queues, R2, Durable Objects, FTS5, and Cloudflare observability—not through API imitation.
Can I change authentication or payment providers?
Better Auth and the payment gateway are isolated behind application services. Application-owned user projections and billing records keep provider data from leaking across the product.
How are background failures handled?
Mutations commit outbox records with application data. Versioned workers lease work, retry safely, record receipts, and move exhausted work to a dead-letter queue.
Ship the differentiated part.
Keep the architecture, own the data, and turn platform months into product days.