Skip to main content
Casdoor is a deployed Go IAM service. You run it as a separate process alongside your app, and it handles SSO, LDAP, CAS, RADIUS, and a native MCP OAuth server. It’s designed for organizations that need a standalone identity provider, especially in Go environments. theAuth is a library, not a service. You import it into your TypeScript app and it runs in-process. Same MCP OAuth 2.1 spec, very different deployment model. A migration guide from Casdoor is coming soon.

Feature matrix

Pick theAuth if

  • You’re building a TypeScript or edge-native app and want auth in-process, not as a sidecar.
  • You need first-class agent primitives: delegation, ephemeral sessions, trust scoring, and cost attribution.
  • Your MCP OAuth story needs to know which agent made which call, not just which client.

Pick Casdoor if

  • You want a deployed IAM service that your whole organization can log into, including non-TypeScript services.
  • You need LDAP, CAS, or RADIUS compatibility for employee SSO.
  • You’re in a Go shop and want to own the full server.
The clearest signal: if you’re writing import { createTheAuth }, theAuth. If you’re writing docker run casdoor, Casdoor.

theAuth vs better-auth

How theAuth compares to the TypeScript-native auth library.

theAuth vs Hanko

theAuth versus the passkey-first Go auth library.

MCP OAuth 2.1

How theAuth implements the MCP authorization server spec.

Agent identity

First-class agent identities with delegation and audit.
Last modified on October 7, 2026