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

AreaTechnologyRole
FrameworkVoid Pages and @void/reactFile-based pages, server rendering, loaders, and form actions
UIReact 19, TypeScript, Tailwind CSS 4, Base UI, LucideComponents and styling through @kit/ui
AuthenticationSelf-managed Better AuthSessions, sign-in methods, organizations, and account security
DatabasePostgres and Drizzle through void/dbTyped queries, schema definitions, and SQL migrations
Local databasePGlite through @kit/dev-dbPostgres-compatible development database on port 54323
Production database accessCloudflare HyperdriveConnects Workers to your hosted Postgres database
StorageCloudflare R2 through void/storageUploaded files
Emailvoid/emailDevelopment inbox locally; Cloudflare Email Sending in production
Background workCloudflare Queues and cronsTransactional outbox jobs, retries, and scheduled work
BillingStripe hosted Checkout and customer portalSubscription checkout and billing management
Content@void/mdMarkdown content and documentation
Toolingpnpm and VitePlus (Vite+, vp)Workspace dependencies, development, builds, formatting, linting, and unit tests
Browser testsPlaywrightEnd-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 tests
packages/ Shared @kit/* packages
tooling/ Local database, MCP server, scripts, TypeScript config
docs/ Kit documentation
.prds/ Product requirements managed through the MakerKit MCP server

The 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 →