Technical Details
The kit's framework, database, authentication, Cloudflare runtime, and workspace structure.
The kit uses Void Pages with React for the application and deploys to Cloudflare Workers in your own account. Node.js runs development and build tools on your computer; the deployed application runs in the Workers runtime.
Technology Stack
| Area | Technology | Role |
|---|---|---|
| Framework | Void Pages and @void/react | File-based pages, server rendering, loaders, and form actions |
| UI | React 19, TypeScript, Tailwind CSS 4, Base UI, Lucide | Components and styling through @kit/ui |
| Authentication | Self-managed Better Auth | Sessions, sign-in methods, organizations, and account security |
| Database | Postgres and Drizzle through void/db | Typed queries, schema definitions, and SQL migrations |
| Local database | PGlite through @kit/dev-db | Postgres-compatible development database on port 54323 |
| Production database access | Cloudflare Hyperdrive | Connects Workers to your hosted Postgres database |
| Storage | Cloudflare R2 through void/storage | Uploaded files |
void/email | Development inbox locally; Cloudflare Email Sending in production | |
| Background work | Cloudflare Queues and crons | Transactional outbox jobs, retries, and scheduled work |
| Billing | Stripe hosted Checkout and customer portal | Subscription checkout and billing management |
| Content | @void/md | Markdown content and documentation |
| Tooling | pnpm and VitePlus (Vite+, vp) | Workspace dependencies, development, builds, formatting, linting, and unit tests |
| Browser tests | Playwright | End-to-end application tests |
Better Auth runs inside the app: the kit owns its configuration, database tables, and /api/auth/* handler. TanStack Form, Table, and Query provide forms, tables, and client caching; routing belongs to Void Pages.
How a Page Works
Page components live in apps/web/pages/. A companion *.server.ts file loads data and handles actions on the server. The page renders on the server initially, then hydrates in the browser for interaction. API handlers live in apps/web/routes/; middleware handles shared concerns such as sessions, locale, and security headers.
Shared @kit/* packages contain reusable services and UI. The app binds them to its database, authentication, and infrastructure through apps/web/config/. Start customizations in these configuration files and your own pages.
Project Structure
apps/ web/ Application, pages, API routes, config, database, jobs e2e/ Playwright testspackages/ Shared @kit/* packagestooling/ Local database, MCP server, scripts, TypeScript configdocs/ Kit documentation.prds/ Product requirements managed through the MakerKit MCP serverThe production target is your own Cloudflare account. Workers use Hyperdrive to reach Postgres. The kit's deployment task also configures its supporting Cloudflare resources. See Deployment for the production workflow.
Next: Prerequisites →