theAuth vs better-auth
Both are MIT TypeScript libraries and both ship an MCP OAuth 2.1 server and an agent plugin or module. better-auth is the larger project with the larger community. theAuth adds delegation chains, approvals bound to arguments, an audit chain, devices and a Go library, some of which are on the release branch and not yet in a published release (npm
@glinr/theauth is 1.2.0). The page lists each row with its source.theAuth vs Keycloak
Keycloak is the closest rival on devices and delegation: CIBA, Device Grant, DPoP and RFC 8693 are supported, with delegation and SPIFFE in Preview. It is a server you deploy, not a library. The page shows where its own docs stop.
theAuth vs Hanko
Hanko is a passkey-first library with an AGPL backend. If passkeys are your entire auth story and you have no agent workloads, it’s worth a look. If you need any agent identity or RBAC, you’ll be building on top of it yourself.
theAuth vs Casdoor
Casdoor is a deployed Go IAM service with LDAP, CAS, and RADIUS support. It targets employee SSO in Go shops. theAuth is a library, not a service, and it’s built for agent-native TypeScript apps.
theAuth vs paid options
Clerk and Auth0 are polished, fast to start, and expensive at scale. Both are proprietary hosted services with MIT licensed SDKs, and Auth0 sells a private deployment add-on on Enterprise. This page covers the open-source vs. managed tradeoff without reproducing any pricing tables.