Auth Kit

Branded sign-in that matches your site

Your colors, copy, and account menu — not a generic login wall. Password and email-code paths that feel like part of the product.

What every install includes

Shared package — not a one-off paste that drifts between client sites.

  • Sign-in, sign-up, and forgot-password that look like your product
  • Password and email-code paths for accounts that never set a password
  • Account menu with your brand — no third-party chrome in the UI
  • Brand tokens in one CSS file; one shared package across sites

Built for real account chaos

Password users, code-only users, and deep links back into the app they left.

Identifier-first sign-in

Email lookup, then password or code — same flow families already know from modern apps.

Email-code rescue

Passwordless accounts get a clear code path instead of a dead-end error.

Social sign-in

Optional Google (and friends) with a site-owned callback — users stay on your domain.

Bot checks when you need them

Drop Cloudflare Turnstile (or similar) on continue / submit without forking the kit.

Deep-link returns

After sign-in, send people back to the page they were trying to open — on allowlisted hosts only.

One package, many brands

Shared auth UI; each site only owns config + token colors.

How it lands on a site

Three site-owned pieces. Everything else comes from the package.

  1. 01

    Install

    Drop in the shared auth package and wrap your app with the kit provider.

  2. 02

    Config

    Set site name, routes, after-sign-in URLs, and which hosts may deep-link back.

  3. 03

    Brand

    Paint brand tokens — buttons, focus rings, shell — so login matches the rest of the site.

Ready for login that looks like you?

Tell us the site — we wire the kit, tokens, and return paths so staff and families never see a generic auth wall.