Built from the patterns behind Homi, SwipeStats, and Capient

Forge once.Launch again.

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.

system ready

Draupnir foundation

One working product, ready to become yours.

RuntimeNext.js 16.3 + React 19Row 1
IdentityBetter AuthRow 2
DataNeon + DrizzleRow 3
BillingPolarRow 4
InterfacestRPC + oRPCRow 5
Auth

connected

Billing

connected

Deploy

connected

A foundation earned in production

NEXT.JS 16.3REACT 19BETTER AUTHPOLARNEON

The name

Odin's ring made eight copies of itself every ninth night.

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

Start at the first product decision, not the first config file.

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.

Accounts that grow with the product

Better Auth covers email, OAuth, anonymous sessions, admin controls, organizations, teams, and invitations.

A database with a real lifecycle

Neon and Drizzle ship with typed schemas, migrations, development branches, and resource-scoped IDs.

Billing owned by your application

Polar handles checkout and the customer portal. Draupnir keeps entitlement policy explicit in your code.

Typed APIs in two proven shapes

Start with tRPC or use the contract-first oRPC reference. Both preserve organization and authorization boundaries.

AI patterns you can inspect

Working streaming, structured output, voice, image, and provider examples live beside the application code.

The unglamorous parts are connected

Email, uploads, analytics, onboarding, loading states, and account settings already agree on how the app works.

Where it came from

The boring work became the useful product.

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.

01

Homi

Collaborative home search with AI, organizations, and real users.

02

SwipeStats

A profitable data product with years of product and growth lessons.

03

Capient

A security-sensitive workspace where the shared foundation saved real build time.

The shape of the system

Clear boundaries survive the fork.

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

Ship with the same foundation I use.

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

  • Private Draupnir repository access
  • Unlimited personal and commercial products
  • Lifetime updates for founding customers
  • One 30-minute setup session with Kristian
Request a founding license

Checkout is not open yet. Request a license to join the first batch.