Kavachos Is Now theauth
Kavachos has been rebranded to theauth. Here's what changed, what didn't, and how to migrate.
Gagan Deep Singh
Founder | GLINR Studios
The name changed. The problem it solves didn't.
Kavachos is now theauth. Same auth system built for the AI-native era -- identity for both humans and AI agents, scoped permissions, delegation chains, full audit trails -- just under a name that says what it does.
The core thesis hasn't moved: AI agents need auth too. The identity layer is the next platform, and most existing auth providers were designed around a session-per-human model that breaks down the moment your "user" is an autonomous agent running a multi-step workflow.
What actually changed
- Source and docs: the GitHub repo and documentation now live under theauth, with docs at docs.theauth.dev.
- A Go implementation: theauth-go ships alongside the TypeScript core -- sessions, magic links, WebAuthn/passkeys, TOTP, SAML, and SCIM, backed by Postgres, MySQL, or in-memory storage, for teams not on a JS stack.
What hasn't changed yet
The published npm packages -- kavachos, @kavachos/react, @kavachos/nextjs -- still ship under the original name. The rename started at the source and domain level; the package rename is a separate, deliberate step so nobody's install scripts break overnight.
If you're already using the kavachos packages, nothing breaks. If you're evaluating it fresh, start at docs.theauth.dev.
Why this matters more than a cosmetic rename
Auth is infrastructure people stake their product on. Renaming it isn't free -- every doc link, every npm install command in a README, every blog post (including the original Kavachos post) now points at a name that's technically still correct but no longer the whole story. Doing it in stages -- rename the source and docs first, migrate packages later, keep both names discoverable in the interim -- is the version of this that doesn't quietly break someone's CI at 3am.