Better Auth owns identity
Sessions, password hashing, verification, reset, OAuth, and two-factor flows stay in a vetted authentication library.
Read the guideSkrum combines vetted identity, encrypted secret storage, explicit consent, and permission checks. The documentation explains each boundary.
Sessions, password hashing, verification, reset, OAuth, and two-factor flows stay in a vetted authentication library.
Read the guideAI keys and integration secrets are encrypted at rest with a master key that never enters the client bundle.
Read the guideRecording is explicit and join flows require acknowledgement when a meeting requires recording consent.
Read the guideWorkspace provider keys are encrypted, hint-only in responses, and omitted from prompts, logs, and usage telemetry.
Read the guideProduct routes resolve workspace membership and resource visibility; foreign resources return 404 rather than revealing existence.
Read the guideEligible plans add SAML or OIDC SSO, SCIM provisioning, session controls, two-factor policy, and IP allowlists.
Read the guideSee managed plans, explicit caps, and credit packs on the pricing page.