TanStack Start SaaS BoilerplateBuilt to Ship on Cloudflare

34 presets and a customizer, not one theme

Thirty-four light and dark presets ship out of the box, and the visual customizer drives colors, five border-radius steps, light/dark/system modes, and sidebar, floating, and inset sidebar variants with collapsible offcanvas and icon modes through CSS variables. Rebrand by changing values in the UI — theme files stay untouched.

Custom themes persist per user and re-apply on reload, so buyers preview the exact experience your customers will get.

Eight modules, with live workflows

The template includes eight AI modules — summarization, translation, tagline generation, text-to-speech, image description, two image-generation views, and image editing. The core workflows call Cloudflare Workers AI directly and deduct in-app credits, so the live workflows show real execution and real credit deductions, while the remaining tool interfaces are intentionally designed as extensible demos.

A complete credit system handles metering, rate limits, and deductions across plans, with demo quotas configured per plan. Swap in your own quotas when you ship.

For a buyer, that means the connected AI workflow pages demonstrate real behavior on day one — generate a tagline, translate a paragraph, and watch the credit counter move. The metering, rate limits, and per-plan quotas all work before you connect your own model provider.

Changelog with visible progress

The template includes a versioned Changelog page so buyers can see how the codebase evolved. The same page becomes part of your product, ready to announce your own releases.

The full sign-up to session flow

Once your OAuth and email keys are configured, email/password and Google OAuth work from the first deploy. Registration triggers email verification, sign-in creates a managed session through Better Auth’s cookie handling, and every authenticated request validates that session — all pre-configured for TanStack Start.

The flow covers what a real product needs end to end: sign-up, verification, sign-in, session management, and account recovery when users forget their password. Because the auth routes ship inside the delivered codebase, you adjust fields, providers, and redirects in one place instead of building the flow from scratch — and the whole loop runs locally against the same D1 database you deploy to.

Pick a provider, flip a switch

Set PAYMENT_PROVIDER in your environment and the checkout, webhook, and portal routes bind to that provider. Creem suits fast digital-goods checkout, Stripe brings subscriptions plus Alipay for one-time payments, and PayPal covers subscription billing in its own ecosystem.

Every adapter owns its external calls — checkout sessions, customer portals — while shared orchestration keeps order handling and access rules identical across providers. Adding another provider later is adapter work, not flow rework: the checkout page, dashboard billing views, and webhook handlers are already provider-agnostic.

Test keys and sandbox modes let you exercise the full checkout lifecycle before you activate live credentials, so integration testing does not require real payments.

Drizzle, D1, and migrations that run

The schema ships with 18 ready-made tables: users, sessions, subscriptions, orders, newsletter subscriptions, contact messages, and more. Typed queries catch mistakes at compile time, not in production.

Migrations generate and apply through the same D1 binding locally (Miniflare) and remotely — you are never guessing whether the production database matches your code.

Resend, wired for both languages

Authentication and notification emails ship as bilingual Resend templates — welcome, verification, password reset, and receipts read naturally in English and Chinese.

Swapping in your own Resend keys and sender is a configuration change, not a refactor.