Implementation recipes
These are not feature bullets. They are the guides that ship inside the product, on the Implement tab of each module. Each one carries a goal, prerequisites, the full file inventory, ordered steps with real code, verification at every stage, and a definition of done. Below is what each one covers.
Showing 9 of 173 recipes.
A new engineer's first week, compressed. You finish able to say where Better Auth ends and your Convex product data begins — who owns identity, sessions, organizations, and authorization decisions — with each section of the guide mapped to the real code that implements it, verified by the standard checks.
the boundary between auth and product data
One admin screen proves that email, analytics, error reporting, durable workflows, and plan gating really work on a fresh clone before a demo or a deploy. You finish able to read each card's Debug versus Configured badge and name exactly what flips an adapter live — no vendor dashboards required.
telling debug mode from real configuration
Let a change to an existing record start an automation, not just a brand new one. The updated trigger appears in the automation builder for your own tables, an edit never re-runs rules somebody wrote for created records, and a save that changes nothing stays silent — proven in both directions by tests.
edits and inserts stay separate triggers
Give a record in any table a first-response deadline that outlives your next deploy. Nothing polls for overdue work, the wake-up at the deadline records exactly one breach, one notification, and one audit event even if it runs twice, and answered or closed records never escalate at all.
a timer that survives a deploy
Optional providers such as Resend, PostHog, and Sentry run in debug mode from day one, so every feature works before any account exists. You finish knowing exactly which setting flips each provider live, with the Labs badges confirming what is configured — no guessing about which mode you are in.
knowing which adapter is really live
Move a running database onto its new tenancy column with nobody signed out. You dry-run first, backfill in batches with live progress you can watch and resume, count remaining legacy rows down to zero, then tighten the schema so the platform itself refuses the old shape forever.
a cutover with nobody signed out
Operators keep open access to admin reads, but anything destructive asks for the password again, and that approval lasts only fifteen minutes. Better Auth verifies the password, a stale window produces a clear re-auth error, and every sensitive action lands in the audit trail with who did it.
a stolen session that is still signed in
Turn a feature off for everyone during an incident, ramp it to a percentage of organizations with stable canary membership, or override a single customer. Everything happens from the admin console with no redeploy and no code change, gated behind password step-up and recorded in the audit trail.
per-org overrides on top of a rollout
Modules you write become installable and removable like the ones that ship in the box. You register the module with the CLI, and a drift check keeps its published copy in step with your source, while a remove-and-reinstall round trip proves an uninstall leaves the codebase byte-identical to where it started.
byte-identical removal from shared files