Authentication included
Better Auth is wired with Google, email and password, and email OTP flows backed by the database.
Nuxt 4 • Better Auth • Cloudflare Workers
Start every SaaS build with the foundations already wired.
A focused template for shipping product ideas faster: authentication, database migrations, Cloudflare bindings, email delivery, and a clean app shell are ready from the first commit.
4
Auth methods
1
Cloud target
0
Custom CSS
Project readiness
Ready for customization
AuthenticationGoogle, password, OTP
DatabaseDrizzle schema and migrations
RuntimeCloudflare Workers
Deploy pipeline
Wrangler config included
Feature foundation
Everything a template should solve before product work starts.
The stack stays intentionally small and predictable, so new projects can inherit the basics without carrying a custom platform team.
Database-ready by default
Drizzle schema files and migrations are organized for Cloudflare D1 from local development through deployment.
Cloudflare-first deployment
Wrangler configuration, environment placeholders, and runtime-safe defaults reduce the setup work for every new app.
Clean UI foundation
Shadcn Vue, Tailwind utilities, a reusable app shell, and responsive page sections keep the interface consistent.
Billing-friendly boundaries
The template leaves clear server-side ownership for Stripe checkout, webhook handling, and account entitlement logic.
Transactional email path
The email service uses server-only configuration and can send OTP messages through Resend without client exposure.
Architecture
A practical stack with clear ownership.
Each layer has a simple job: Nuxt handles the app, Better Auth handles sessions, Drizzle describes persistence, and Cloudflare runs the whole thing close to users.
Nuxt 4 application shell
Vue 3 composition patterns
Better Auth session layer
Cloudflare storage bindings
Drizzle schema and migrations
Cloudflare Workers runtime
Workflow
From template to product in three direct steps.
Configure the project
Update app metadata, environment variables, OAuth credentials, and Cloudflare bindings for the new product.
Build domain features
Add models, services, pages, and API routes inside the existing boundaries instead of rebuilding platform plumbing.
Deploy with confidence
Run checks, apply migrations, and ship through the Cloudflare workflow already prepared by the template.
Setup checklist
Keep launch preparation visible.
The template is ready to be renamed, connected, and extended. These are the first edits every new project should make.
Project handoff list
- Copy .env.example and fill the required secrets.
- Set the OAuth callback URL for Google.
- Create Cloudflare resources and keep bindings aligned.
- Replace template copy with product-specific messaging.