Accounts that grow with the product
Better Auth covers email, OAuth, anonymous sessions, admin controls, organizations, teams, and invitations.
Draupnir is the production-ready Next.js foundation I wanted each time I started a serious product. The accounts, billing, data, email, AI patterns, and deployment plumbing already work together.
The first 20 licenses are $149 once. The deployed app is the reference, not a screenshot of a future product.
Draupnir foundation
One working product, ready to become yours.
connected
connected
connected
A foundation earned in production
The name
That is the job of a good product foundation. Solve the hard, repeated work once. Carry it into the next product without carrying the old product with it.
Draupnir keeps the durable parts and leaves room for the new idea to become its own thing.
What is already solved
This is opinionated application code with working seams between systems. You can replace a provider without rediscovering the product boundary it was meant to serve.
Better Auth covers email, OAuth, anonymous sessions, admin controls, organizations, teams, and invitations.
Neon and Drizzle ship with typed schemas, migrations, development branches, and resource-scoped IDs.
Polar handles checkout and the customer portal. Draupnir keeps entitlement policy explicit in your code.
Start with tRPC or use the contract-first oRPC reference. Both preserve organization and authorization boundaries.
Working streaming, structured output, voice, image, and provider examples live beside the application code.
Email, uploads, analytics, onboarding, loading states, and account settings already agree on how the app works.
Where it came from
Draupnir collects the infrastructure and interface decisions that survived contact with real products. It is maintained as a working application so those decisions keep getting tested together.
Homi
Collaborative home search with AI, organizations, and real users.
SwipeStats
A profitable data product with years of product and growth lessons.
Capient
A security-sensitive workspace where the shared foundation saved real build time.
The shape of the system
Provider clients stay small. Services own application policy. Routes enforce access. UI examples show the whole path working.
access
session > organization > resource
api
tRPC default + oRPC reference
navigation
Cache Components + instant validation
tenancy
organizations, teams, invitations
storage
typed resource attachments
delivery
React Email + Resend
Founding license
I am opening Draupnir to 20 developers before turning it into a larger catalog. The first release includes the private source, updates, and a setup call with me.
Want to see where it has already helped? Read the Boe Ventures case study.
One-time purchase
$149
One named developer
Checkout is not open yet. Request a license to join the first batch.