The library · The stack

Better Auth with passkeys

Keep accounts, organisations and passkey sign-in in your own Hono API and Postgres database.

2 files · 5 KB

Better Auth ↗

Why I keep it

I use Better Auth for WithSeismic’s accounts and organisations, so the user records and sessions live in my own Postgres database. Hono mounts the auth handler; the front end talks to that API through the same origin, where cookies and passkeys need to agree.

Auth APIs move, so I’ve given you the architecture and a prompt for your agent to build against the current docs. GUIDE.md sets out the origin, tables, plugins and passkey rules; PROMPT.md asks the agent to prove sign-in on localhost with your own setup.

Take the files

2 files · 5 KB

  • GUIDE.md3 KB
  • PROMPT.md2 KB

Keep building your setup: The stack

Back to the shelves →
  • 015 files · 151 KB

    The SaaS starter

    Start with accounts, organisations, email and analytics wired into a React app and Hono API.

  • 025 files · 6 KB

    Turborepo

    Run builds, tests and type checks across your apps in dependency order, with cached results.

  • 0316 files · 18 KB

    Hono

    Give your API typed routes, generated docs and a consistent error response before adding features.

  • 048 files · 8 KB

    Drizzle

    Keep your database schema typed and your SQL migrations checked in beside the code that needs them.

  • 059 files · 10 KB

    TanStack

    Keep React routes, session checks and cached server data working from the same types.

  • 065 files · 5 KB

    Lefthook and Biome

    Check staged code at commit time and types before a push, including work written by your agents.