Warpkit gives you OTP auth, Stripe billing, and a per-user SQLite database so you can focus on building your product: not the plumbing.
Not a demo , this stack runs real, live products
Auth, billing, email, database: you spend weeks on plumbing before writing a single line of product logic.
Stop rebuilding auth and billing for every project. Start with a solid foundation and build the thing only you can build.
Passwordless login via email OTP. Users stay signed in across devices with multi-session support built in.
Checkout, customer portal, and webhook handling. One boolean: hasAccess: tells you everything you need.
Every user gets their own isolated SQLite database. No shared schema, no cross-user leaks, no row-level security to forget.
SQLite-backed queue with retries and dead-letter handling (jobs that keep failing get set aside for review instead of retrying forever). Survives server restarts.
User management, impersonation, and access control at /dashboard/admin, guarded and audit-logged.
Every server function returns Result<T>, not a thrown exception. Errors are values you check, not surprises you catch.
Full-stack React with server functions, file-based routing, and TanStack Query. The modern way to build.
Durable, crash-safe account deletion and full data export, built in, not bolted on later.
Content collections with MDX support. Write posts in Markdown, get a fast statically-rendered blog.
Not just wiring , the parts that take real hours to get right: race conditions, replay safety, crash-safe state machines.
Passwordless auth
OTP + magic link, rate limiting, disposable-email gating
Stripe billing
Checkout, portal, safe even if Stripe resends the same webhook twice
Per-user SQLite
Writes queued per user, migrations, no collisions between simultaneous writes
Background jobs
Retries, dead-letter (failed jobs set aside for review, not retried forever), graceful shutdown, stale-job recovery
Admin panel
Impersonation guard, audit trail, promotion flow
GDPR deletion + export
Durable multi-step state machine, crash-safe resume
Typed error handling
Result<T> across every server function, nothing to try/catch
Security headers + rate limiting
Security headers, rate limiting tracked per IP address on every auth endpoint
A checked-in CLAUDE.md and six real Claude Code skills, not a marketing claim. Your AI assistant reads actual conventions on day one, not a wiki it ignores. Works just as well with Cursor, Windsurf, and GitHub Copilot.
/codingserver functions, feature structure, gate ordering/architecturewhere things live and why/testingreal SQLite, no DB mocks/convention-auditfull codebase check against the rules/commit-messageConventional Commits, Seven Rules/commandsCI, dev server, DB, lintDon't take our word for it , every page under /docs on this site is rendered straight from the `docs/` folder in the repo you clone. Same files, same context, no separate marketing copy to drift out of sync.
I'm Daniel, known online as bitclaw. 17 years building production systems for U.S. companies, remote. Currently leading a team of engineers taking a monolith to microservices. Warpkit is the stack I actually reach for , it's what runs RunMist and WeatherDestination too , backed by the same CI discipline I'd want on a team I'm responsible for: hundreds of tests, boot-smoke checks, and convention audits, not just a README.
Stop rebuilding the same foundation. Clone Warpkit, customize the config, and own your stack , no row-level security to write and maintain, no lock-in.
One-time purchase. Lifetime access.
Everything you need to launch your SaaS. One-time purchase, lifetime access.
Secure checkout via Stripe , GitHub repo access sent to your purchase email