Introducing Edge Kit: TanStack Start SaaS starter for Cloudflare

We just launched Edge Kit, a TanStack Start SaaS starter kit for Cloudflare. It is a complete codebase for a SaaS that runs on Cloudflare Workers from the first line: sign-in, Stripe subscriptions, a D1 database, file uploads, background jobs, email, and streaming AI, already connected and deployed as a single Worker.

Most SaaS starters, including our own Core Kit, are Node.js apps backed by Postgres. You can deploy them to Cloudflare, but you are adapting an app built for a server to a runtime that isn't one, and you still sign up with separate vendors for email, storage, analytics, and feature flags. Edge Kit takes the opposite route. It starts from the Workers runtime and Cloudflare's own services, so local development, data, files, email, and deploys all live on one platform.

Watch the 42-second launch video:

Prefer to click around yourself? The live demo covers the marketing site, sign-in, account settings, billing, and the streaming AI chat:

What's inside Edge Kit

Edge Kit covers the parts of a SaaS that customers never pay for directly but every product needs: accounts, payments, data, files, email, background work, and an AI foundation. Each one connects to a Cloudflare service through a Wrangler binding, so your features call typed APIs instead of juggling third-party SDKs and API keys.

On top of that infrastructure, the product layer is already built:

• Authentication with Better Auth: email and password with verification and recovery, Google, GitHub, and Cloudflare sign-in, anonymous sessions, and account settings for profile, avatar, linked accounts, and active sessions.
• Subscription billing with Stripe: hosted checkout, monthly and yearly plans, optional trials, promotion codes, the customer portal, webhook-synced subscriptions, and server-side checks that gate features by plan.
• A marketing site with landing sections, pricing, a contact form, an MDX blog, legal pages, SEO metadata, sitemaps, and social previews.
• Internationalization in English and Spanish, with localized routes, language detection, and type-safe Paraglide messages for both the interface and emails.
• UI built on Kumo, Cloudflare's React component library on Base UI, with Tailwind CSS, light and dark mode, and TanStack Form with Zod validation.
• Testing and tooling: Vitest (with a project that runs inside the Workers runtime), Playwright across Chromium, Firefox, and WebKit, type-aware Oxlint and Oxfmt, envin for environment validation, and Renovate for dependency updates.

Every piece has a guide in the Edge Kit documentation: more than 60 pages that take you from local setup to a production deploy.

Why TanStack Start on Cloudflare Workers?

TanStack Start gives you full-stack React on Vite: file-based routes, server rendering, and typed server functions in one app. Cloudflare's Vite plugin runs that same app inside workerd, the open-source Workers runtime, so what you test locally is what you deploy. No adapter rewrites your build for production.

The two projects work closely together. TanStack's hosting guide lists Cloudflare Workers as an official partner, and Cloudflare maintains its own TanStack Start framework guide. For a SaaS, the combination pays off in three ways:

1. Local development matches production. pnpm dev runs your Worker in workerd and simulates D1, KV, R2, Queues, and rate limits on disk. There is no Docker and no local Postgres. You can browse local tables, R2 objects, and KV values in Cloudflare's Local Explorer while you work.
2. Bindings replace vendor setup. Your code reads DB, UPLOADS, or QUEUE from the Worker environment. Wrangler decides which database, bucket, or queue each name points to in every environment, and pnpm cf-typegen keeps the types in sync.
3. Types run from route to database. TanStack Router types your URLs and search params, server functions validate input with Zod, and Drizzle types your queries. The data flow is explicit, which also makes it easier for a coding agent to follow.

Here is the pattern Edge Kit uses for protected reads, from the protected calls guide. The server function resolves the customer from the session, validates the input, and scopes the query to that customer:

import { createServerFn } from "@tanstack/react-start";

import { enforceAuth } from "@/lib/auth/middleware";

import { noteIdSchema } from "./notes.schema";
import { findNote } from "./notes.server";

export const getNote = createServerFn({ method: "GET" })
  .middleware([enforceAuth])
  .validator(noteIdSchema)
  .handler(({ data, context }) => findNote(context.user.id, data.id));

The client calls getNote({ data: { id } }) and never sends a user ID, so it cannot request another customer's record.

One Worker, one Cloudflare account

Edge Kit deploys your public website, customer dashboard, API endpoints, and queue consumer as a single Cloudflare Worker. Outside Cloudflare, the only accounts you need are Stripe and the OAuth providers you enable, plus a model provider if you route AI Gateway to one. Fewer accounts means fewer secrets to rotate and one dashboard to check when something breaks.

Every customer action follows the same path through the stack. The React interface collects input, a server function validates it and checks the session, the operation reads or writes the right Cloudflare resource, and the client refreshes the affected data. The architecture guide walks through that lifecycle in detail.

Going to production takes a handful of Wrangler commands and one deploy:

pnpm wrangler d1 create my-app-production
pnpm wrangler r2 bucket create my-app-uploads
pnpm wrangler queues create my-app-jobs
pnpm wrangler kv namespace create KV

# Add the resource IDs to wrangler.jsonc and set secrets with `wrangler secret put`
pnpm deploy

pnpm deploy builds the app, applies pending D1 migrations, and publishes the Worker. Connect the repository to Cloudflare's GitHub integration and every push to your production branch deploys, while pull requests get their own preview URLs. The deployment guide covers secrets, custom domains, and preview environments.

Built for coding agents

Most models still default to Next.js, ESLint, and barrel imports, and none of those fit this stack. Edge Kit ships the context that corrects them before the first edit: rules with the stack's gotchas, skills for each framework it uses, a review subagent, a feature scaffolding command, and a hosted docs MCP server.

• AGENTS.md rules, referenced from CLAUDE.md, covering commands, project layout, how bindings work, and the mistakes that break a Worker build, like Node-only APIs or reading bindings from the wrong env.
• Skills for TanStack Start, TanStack Router, the wider TanStack ecosystem, Kumo, and Better Auth, plus React performance and web design guidelines.
• A read-only code-reviewer subagent and a /setup-new-feature command that scaffolds a module the same way the billing module is built.
• A docs MCP server at https://www.turbostarter.dev/mcp, plus llms.txt, so Cursor, Claude Code, Codex, and other tools can search the Edge docs instead of guessing.

All of it works with any tool that reads AGENTS.md. The AI-assisted development guide shows the setup for each editor, and our boilerplate vs vibe coding guide explains why agents do better on top of a real foundation than in an empty repo.

Edge Kit vs Core Kit: which should you choose?

Choose Edge Kit for a web-only SaaS sold to individual customers that you want running entirely on Cloudflare. Choose Core Kit if you need organizations and teams, a mobile app or browser extension, PostgreSQL as your system of record, or a payment provider other than Stripe. Core can deploy to Cloudflare as well, through OpenNext.

A quick test: answer "where does it run, who pays, and how?" If the answers are "the web", "individual customers", and "Stripe subscriptions", and you want the whole product on Cloudflare, Edge Kit is the shorter path. If any answer differs, or might within a year, start with Core. The two kits are separate codebases, so switching later is a framework migration, not a config change.

Already on Core and only want Cloudflare hosting? Our guide to deploying TurboStarter to Cloudflare Workers covers the OpenNext and Hyperdrive setup. For the full decision across every kit, including AI Kit and OpenClaw Kit, see choose a kit.

What does it cost to run a SaaS on Cloudflare?

Edge Kit is a one-time purchase. Running it costs whatever your Cloudflare usage costs, which for most early SaaS products means the Workers Paid plan: a $5 per month account minimum that includes 10 million requests. Cloudflare's Email Sending is only available on Workers Paid, so budget for the paid plan from your first production deploy.

These allowances come from Cloudflare's Workers pricing page, checked in October 2026:

A few more details matter for budgeting:

• No egress fees. Workers, D1, and R2 don't charge for data transfer, and requests to static assets are free.
• R2 includes 10 GB-month of storage, 1 million Class A operations, and 10 million Class B operations each month on its free tier.
• Workers AI includes 10,000 Neurons per day, then bills $0.011 per 1,000 Neurons on Workers Paid (pricing). Third-party models behind AI Gateway bill through your provider account or Unified Billing.
• Email Sending (public beta since April 2026) and Flagship (public beta since May 2026) are newer services, so check their current terms before launch.
• Stripe charges its own processing fees per transaction.

A free Cloudflare account is enough to develop locally, although AI and feature flags call your account even in development. For production, start on Workers Paid.

Get started with Edge Kit

After purchase, one CLI command clones the kit, writes your environment files and Wrangler config, installs dependencies, and seeds a local D1 database. Then pnpm dev runs the app on the Workers runtime and pnpm deploy ships it.

npx @turbostarter/cli@latest new -k edge

cd my-app
pnpm wrangler login
pnpm dev

Pricing and launch offer

Edge Kit is a one-time purchase with lifetime access to the private GitHub repository, every future update, and the TurboStarter Discord. One license covers unlimited end products, including client projects, and teams buy one seat per developer.

The EDGE code is applied automatically at checkout. After launch week, existing customers can still claim a one-time 10% code for their next kit from the dashboard. The license has the full terms, and the pricing section shows regional discounts where they apply.

Frequently asked questions

Ship your SaaS on the edge

Edge Kit is the TanStack Start SaaS starter we wanted for Cloudflare: one codebase, one Worker, one account, with the setup work already done. If your product is web-first and sold to individuals, it is the shortest path we know from an idea to a globally deployed SaaS.

Click through the live demo, read the Edge Kit docs, or get Edge Kit at the launch price before October 14. Not sure it fits your product? Email hello@turbostarter.dev before you buy and we will help you decide.