Hono + Cloudflare Workers + D1 + Drizzle Starter
TanStack Router, Hono, Cloudflare Workers, SQLite, Cloudflare D1, and Drizzle form a split app configuration where the frontend and backend are generated as separate primary parts. Better Fullstack can scaffold this exact compatibility-checked selection.
01 / selection
Stack at a glance
| Role | Technology | Repository description | Scope |
|---|---|---|---|
| Frontend | TanStack Router | Modern type-safe router for React | Primary frontend |
| Backend | Hono | Ultrafast web framework | Primary backend |
| Runtime | Cloudflare Workers | Serverless runtime for the edge | Scoped to Hono |
| Database | SQLite | File-based SQL database | Project-wide |
| Database hosting | Cloudflare D1 | Serverless SQLite-compatible database for Cloudflare Workers | Scoped to the database |
| ORM | Drizzle | TypeScript ORM | Scoped to Hono |
| API | tRPC | End-to-end typesafe APIs | Scoped to Hono |
| Authentication | Better-Auth | The most comprehensive authentication framework for TypeScript | Scoped to Hono |
| CSS | Tailwind CSS | Utility-first CSS framework | Scoped to TanStack Router |
| UI library | shadcn/ui | Re-usable components built with Radix and Tailwind | Scoped to TanStack Router |
02 / architecture
How the pieces fit
- The frontend and backend are separate primary stack parts.
- Cloudflare Workers is scoped to Hono.
- Cloudflare D1 is scoped to the database.
- Drizzle is scoped to Hono.
- tRPC is scoped to Hono.
- Better-Auth is scoped to Hono.
- Tailwind CSS is scoped to TanStack Router.
- shadcn/ui is scoped to TanStack Router.
- Tailwind CSS and shadcn/ui are selected together.
03 / output
What gets generated
The virtual generator produced 75 files across 23 directories. The output is a workspace.
Top-level entries
- ./.gitignore
- ./AGENTS.md
- ./CLAUDE.md
- ./README.md
- ./apps
- ./bunfig.toml
- ./package.json
- ./packages
- ./tsconfig.json
- ./turbo.json
Representative files
- README.md
- apps/server/package.json
- apps/web/package.json
- package.json
- packages/api/package.json
- packages/auth/package.json
- packages/config/package.json
- packages/db/package.json
04 / create
Create command
This is the canonical Bun command generated for the selection.
bun create better-fullstack@latest my-app --ecosystem typescript --frontend tanstack-router --css-framework tailwind --ui-library shadcn-ui --shadcn-base radix --shadcn-style nova --shadcn-icon-library lucide --shadcn-color-theme neutral --shadcn-base-color neutral --shadcn-font inter --shadcn-radius default --backend hono --runtime workers --api trpc --auth better-auth --payments none --email none --file-upload none --logging none --observability none --feature-flags none --integrations none --ecommerce none --realtime none --job-queue none --caching none --rate-limit none --bot-protection none --i18n none --search none --vector-db none --file-storage none --cms none --effect none --ai none --state-management none --forms react-hook-form --validation zod --testing vitest --animation none --web-mcp none --database sqlite --orm drizzle --db-setup d1 --package-manager bun --git --web-deploy none --server-deploy cloudflare --install --part workspaceRunner:universal:turborepo --examples none --ai-docs claude-md agents-md05 / builder
Open in the builder
- rt
- workers
- dbs
- d1
- sd
- cloudflare
06 / checks
Compatibility notes
Compatibility checked against Better Fullstack types version 2.8.0.
The generated record has 0 graph issues and 0 disabled selected options. This is a compatibility check, not a claim that this exact scaffold received a runtime smoke verification.
- The selected shadcn/ui setup is paired with Tailwind CSS.
07 / fit
When to choose this shape
Choose this shape when the browser frontend and API server should remain separate generated parts.
08 / next
Related stacks and guide
09 / faq
Questions
Is this combination supported?
It passes the repository's compatibility analysis, selected-option checks, stack graph validation, project schema parsing, and virtual generation. That result is described here as compatibility checked.
Does it generate one app or separate parts?
The frontend and backend are generated as separate primary parts. The actual generated output uses a workspace layout.
How can I customize the selection?
Open the generated builder link above. Its query parameters reproduce this selection, and the builder can change compatible options before generating a new command.