Better Auth Fournisseur IAM
Open-source, framework-agnostic authentication and authorization library for TypeScript. Embedded directly in your application and backed by your own database, with a plugin system covering 2FA, passkeys, organizations, SSO/SAML, SCIM, an OAuth 2.1 / OpenID Connect provider and MCP/agent auth. Core differentiator: it is a library, not a hosted service, so there is no vendor server, no per-user pricing and no redirect to a third-party domain. An optional paid Better Auth Infrastructure adds a dashboard, audit logs, security detections and managed email/SMS.
Fonctionnalités
- 🇸🇪🇱🇫🇭🇴🇸🇹🇪🇩Self-hosted
- On-premisesAny cloud
- TypeScriptJavaScriptNext.jsNuxtSvelteKitSolidStartAstroTanStack StartReact RouterWakuExpressHonoFastifyElysiaNestJSNitroEncoreConvexExpoElectronLynx
Si vous souhaitez comparer les fonctionnalités IAM de différents fournisseurs, consultez le benchmark des fournisseurs d'identité (C)IAM.
Vous cherchez la compatibilité du protocole OpenID Connect de Better Auth ? Voir Better Auth sur le benchmark des fournisseurs OpenID Connect.
Foire aux questions
Better Auth prend-il en charge Nom d'utilisateur et mot de passe méthode d'authentification ?
Better Auth prend en charge Nom d'utilisateur et mot de passe méthode d'authentification. Email/password sign-up and sign-in built in (scrypt hashing by default, pluggable via custom hash/verify), with email verification and password reset. The username plugin adds username-based sign-in with configurable length, validator and normalization. En savoir plus
Better Auth prend-il en charge Connexion sociale méthode d'authentification ?
Better Auth prend en charge Connexion sociale méthode d'authentification. Over 35 built-in social providers (Google, GitHub, Apple, Microsoft, Discord, LinkedIn, X, and more). Any other OAuth 2.0 / OIDC provider can be added with the Generic OAuth plugin. En savoir plus
Better Auth prend-il en charge Passkey méthode d'authentification ?
Better Auth prend en charge Passkey méthode d'authentification. Passkeys (WebAuthn/FIDO2) via the passkey plugin, built on SimpleWebAuthn. Supports conditional UI / autofill and a passkey-first registration flow. Documented as a primary sign-in method only, not as a second factor. En savoir plus
Better Auth prend-il en charge Email Passwordless méthode d'authentification ?
Better Auth prend en charge Email Passwordless méthode d'authentification. Email one-time codes via the Email OTP plugin (sign-in, email verification, password reset). The application supplies the email delivery function. Configurable code length, expiry, attempt limit and storage (plain, encrypted or hashed). En savoir plus
Better Auth prend-il en charge Phone Passwordless méthode d'authentification ?
Better Auth prend en charge Phone Passwordless méthode d'authentification. Phone number sign-up/sign-in with SMS one-time codes via the phone number plugin. The application supplies the SMS delivery function (any provider, including Twilio Verify through a custom verifyOTP). Also supports phone number plus password. En savoir plus
Better Auth prend-il en charge Magic Link méthode d'authentification ?
Better Auth prend en charge Magic Link méthode d'authentification. Email magic links via the magic link plugin. Single-use tokens (default 5 minutes), optional hashed token storage, built-in rate limit. The application supplies the email delivery function. En savoir plus
Better Auth prend-il en charge Anonymous / Guest méthode d'authentification ?
Better Auth prend en charge Anonymous / Guest méthode d'authentification. The anonymous plugin issues a session for a guest user with a generated placeholder identity. An onLinkAccount callback migrates data to the real account when the guest later signs in or up, and the anonymous record is removed by default. En savoir plus
Better Auth prend-il en charge Time-based One-Time Password (TOTP) MFA ?
Better Auth prend en charge Time-based One-Time Password (TOTP) MFA. TOTP authenticator apps via the two-factor plugin (30-second period, enrollment verification, configurable issuer, optional trusted devices for 30 days). Account lockout after repeated failed verifications is on by default. En savoir plus
Better Auth prend-il en charge HMAC-based One-Time Password (HOTP) MFA ?
Better Auth ne prend pas en charge HMAC-based One-Time Password (HOTP) MFA. The two-factor plugin documents TOTP and OTP only; no counter-based HOTP. En savoir plus
Better Auth prend-il en charge Universal 2nd Factor (U2F) MFA ?
Better Auth ne prend pas en charge Universal 2nd Factor (U2F) MFA. No FIDO U2F second factor is documented. Passkeys are offered as a sign-in method, not as a second factor. En savoir plus
Better Auth prend-il en charge WebAuthn MFA ?
Better Auth ne prend pas en charge WebAuthn MFA. The passkey plugin is documented as a passwordless sign-in method only; the two-factor plugin does not list WebAuthn as a second factor. En savoir plus
Better Auth prend-il en charge Email Code MFA ?
Better Auth prend en charge Email Code MFA. Second-factor OTP codes delivered by email through the application-provided sendOTP function of the two-factor plugin. En savoir plus
Better Auth prend-il en charge Phone Code MFA ?
Better Auth prend en charge Phone Code MFA. Second-factor OTP codes delivered by SMS through the application-provided sendOTP function of the two-factor plugin. Requires an SMS provider chosen by the application. En savoir plus
Better Auth prend-il en charge Recovery Code MFA ?
Better Auth prend en charge Recovery Code MFA. Backup codes generated by the two-factor plugin. Each code is single-use and can be regenerated, which invalidates the previous set. En savoir plus
Better Auth prend-il en charge Push Notification MFA ?
Better Auth ne prend pas en charge Push Notification MFA. No push-based approval second factor is documented.
Better Auth prend-il en charge Adaptive / Risk-Based MFA MFA ?
Better Auth ne prend pas en charge Adaptive / Risk-Based MFA MFA. No risk-based adaptive MFA. Better Auth Infrastructure (Sentinel) can challenge or block risky sign-ins, but it does not trigger MFA step-up. En savoir plus
Better Auth prend-il en charge Cisco Duo MFA ?
Better Auth ne prend pas en charge Cisco Duo MFA. No Cisco Duo integration is documented.
Better Auth prend-il en charge Step-Up Authentication MFA ?
Better Auth prend partiellement en charge Step-Up Authentication MFA. Sensitive endpoints require a fresh session (session.freshAge, default 1 day) and password re-entry for actions such as enabling 2FA or deleting an account. There is no ACR/AMR-based step-up policy; the OAuth provider advertises acr_values_supported as ["0"]. En savoir plus
Better Auth prend-il en charge OpenID Connect (OIDC) protocole d'intégration ?
Better Auth prend en charge OpenID Connect (OIDC) protocole d'intégration. Acts as an OpenID Connect provider through the OAuth 2.1 Provider plugin (authorization code with PKCE, refresh tokens, client credentials, discovery, UserInfo, RP-initiated and back-channel logout). The older OIDC Provider and MCP plugins build on the same capability. Also consumes OIDC providers as a relying party. En savoir plus
Better Auth prend-il en charge SAML 2.0 protocole d'intégration ?
Better Auth prend partiellement en charge SAML 2.0 protocole d'intégration. SAML 2.0 Service Provider only, through the SSO plugin (signed AuthnRequests, encrypted assertions, IdP-initiated SSO). Better Auth cannot act as a SAML identity provider. En savoir plus
Better Auth prend-il en charge WS-Federation protocole d'intégration ?
Better Auth ne prend pas en charge WS-Federation protocole d'intégration. WS-Federation is not supported.
Better Auth prend-il en charge Machine-to-Machine (M2M) Authentication protocole d'intégration ?
Better Auth prend en charge Machine-to-Machine (M2M) Authentication protocole d'intégration. OAuth 2.0 client_credentials grant via the OAuth Provider plugin (fail-closed: scopes must be explicitly allowed per client), plus the API Key plugin for key-based service authentication. En savoir plus
Better Auth prend-il en charge OpenID Connect (OIDC) Federation fédération d'identité ?
Better Auth prend en charge OpenID Connect (OIDC) Federation fédération d'identité. Generic OAuth plugin connects any OIDC provider through a discovery URL (ID token signature, issuer, audience and nonce validation, PKCE on by default). The SSO plugin registers per-domain OIDC providers at runtime. En savoir plus
Better Auth prend-il en charge SAML 2.0 Federation fédération d'identité ?
Better Auth prend en charge SAML 2.0 Federation fédération d'identité. Inbound SAML 2.0 federation via the SSO plugin, with domain-based provider resolution, DNS domain verification, certificate rotation, InResponseTo validation, replay protection and deprecated-algorithm checks. Single Logout is not documented. En savoir plus
Better Auth prend-il en charge Active Directory / LDAP fédération d'identité ?
Better Auth ne prend pas en charge Active Directory / LDAP fédération d'identité. No built-in LDAP or on-premises Active Directory connector. Microsoft Entra ID is reachable over OIDC.
Better Auth prend-il en charge Azure Active Directory (Entra ID) fédération d'identité ?
Better Auth prend en charge Azure Active Directory (Entra ID) fédération d'identité. Microsoft social provider and a Microsoft Entra ID helper for the Generic OAuth plugin (ID token verification enabled automatically). Entra ID tenants can also be registered as OIDC/SAML providers through the SSO plugin. En savoir plus
Better Auth prend-il en charge Bulk User Import gestion des utilisateurs ?
Better Auth prend partiellement en charge Bulk User Import gestion des utilisateurs. No dedicated bulk import endpoint. Migration guides and scripts cover importing users from Auth0, Clerk, Supabase Auth, WorkOS and Auth.js, and because data lives in the application database, users can also be loaded with SQL or the ORM. En savoir plus
Better Auth prend-il en charge Password Hash Import (Multiple Formats) gestion des utilisateurs ?
Better Auth prend partiellement en charge Password Hash Import (Multiple Formats) gestion des utilisateurs. Imported users keep their existing hashes by overriding emailAndPassword.password.hash/verify with the legacy algorithm (for example bcrypt). The default algorithm is scrypt. En savoir plus
Better Auth prend-il en charge Bulk User Export gestion des utilisateurs ?
Better Auth prend partiellement en charge Bulk User Export gestion des utilisateurs. No dedicated export endpoint. User data lives in the application-owned database, and the admin plugin lists users with pagination. En savoir plus
Better Auth prend-il en charge Bulk User Update / Delete gestion des utilisateurs ?
Better Auth ne prend pas en charge Bulk User Update / Delete gestion des utilisateurs. The admin plugin documents single-user operations only; no bulk update or delete. En savoir plus
Better Auth prend-il en charge Inbound SCIM Provisioning gestion des utilisateurs ?
Better Auth prend en charge Inbound SCIM Provisioning gestion des utilisateurs. SCIM 2.0 server (RFC 7643/7644) via the SCIM plugin: Users and Groups resources, bearer-token connections, discovery endpoints, and managed token rotation. Requires a database adapter with interactive transactions. Better Auth Infrastructure adds a managed Directory Sync dashboard. En savoir plus
Better Auth prend-il en charge Outbound SCIM Provisioning gestion des utilisateurs ?
Better Auth ne prend pas en charge Outbound SCIM Provisioning gestion des utilisateurs. The SCIM plugin is inbound only; Better Auth does not push users to downstream applications. En savoir plus
Better Auth prend-il en charge SCIM Groups Provisioning gestion des utilisateurs ?
Better Auth prend en charge SCIM Groups Provisioning gestion des utilisateurs. SCIM Groups resource with direct memberships. Groups can be projected to application roles through role mapping. En savoir plus
Better Auth prend-il en charge Just-In-Time (JIT) User Provisioning gestion des utilisateurs ?
Better Auth prend en charge Just-In-Time (JIT) User Provisioning gestion des utilisateurs. Users are created on first social or SSO sign-in. The SSO plugin offers provisionUser (per new user or on every login) and automatically adds users to the linked organization with a default or computed role. En savoir plus
Better Auth prend-il en charge Self-Service Profile Management Portal gestion des utilisateurs ?
Better Auth prend en charge Self-Service Profile Management Portal gestion des utilisateurs. Built-in client APIs to update profile, change email (with verification), change or set password, list and revoke sessions, link and unlink accounts, and delete the account. En savoir plus
Better Auth prend-il en charge User Account Linking gestion des utilisateurs ?
Better Auth prend en charge User Account Linking gestion des utilisateurs. Automatic linking of providers that confirm a verified email, trusted-provider list, manual linking (including with ID tokens), unlinking, and an option to disable implicit linking. En savoir plus
Better Auth prend-il en charge User Blocking / Banning gestion des utilisateurs ?
Better Auth prend en charge User Blocking / Banning gestion des utilisateurs. The admin plugin can ban and unban users with an optional reason and expiry. Banning blocks sign-in and revokes existing sessions. En savoir plus
Better Auth prend-il en charge User Metadata gestion des utilisateurs ?
Better Auth prend en charge User Metadata gestion des utilisateurs. The user table can be extended with additional typed fields, and plugins add their own fields. Fields live in the application database and in the same schema as the rest of the application. En savoir plus
Better Auth prend-il en charge Application Metadata gestion des utilisateurs ?
Better Auth prend en charge Application Metadata gestion des utilisateurs. Additional fields can be declared as not settable by the end user (input: false) and written only by server code, which covers admin-only attributes. The admin plugin stores role and ban state this way. En savoir plus
Better Auth prend-il en charge User Search gestion des utilisateurs ?
Better Auth prend en charge User Search gestion des utilisateurs. The admin plugin lists users with search (contains, starts_with, ends_with on email or name), filters, sorting and offset pagination. En savoir plus
Better Auth prend-il en charge Role-Based Access Control (RBAC) gestion des utilisateurs ?
Better Auth prend en charge Role-Based Access Control (RBAC) gestion des utilisateurs. Role-based access control with custom resources and actions via createAccessControl. Admin plugin roles are global, organization plugin roles are scoped per organization, and users can hold multiple roles. En savoir plus
Better Auth prend-il en charge Organizations (Multi-Tenancy B2B) gestion des utilisateurs ?
Better Auth prend en charge Organizations (Multi-Tenancy B2B) gestion des utilisateurs. Organization plugin: organizations, members, invitations, teams, an active organization per session, per-organization roles with optional runtime-defined (dynamic) roles, lifecycle hooks and configurable limits. En savoir plus
Better Auth prend-il en charge Password Strength Policies gestion des utilisateurs ?
Better Auth prend partiellement en charge Password Strength Policies gestion des utilisateurs. Default password length of 8 to 128 characters. The Have I Been Pwned plugin rejects breached passwords. No built-in composition rules or strength scoring; custom rules can be added with hooks. En savoir plus
Better Auth prend-il en charge Username Restrictions gestion des utilisateurs ?
Better Auth prend en charge Username Restrictions gestion des utilisateurs. The username plugin supports minimum length (default 3), maximum length (default 30), custom validators for the username and the display username, and configurable normalization (lowercase by default). En savoir plus
Better Auth prend-il en charge Progressive Profiling / Forms gestion des utilisateurs ?
Better Auth ne prend pas en charge Progressive Profiling / Forms gestion des utilisateurs. No built-in progressive profiling; the application owns the UI and can collect extra fields itself.
Better Auth prend-il en charge Attribute-Based Access Control (ABAC) contrôle d'accès ?
Better Auth ne prend pas en charge Attribute-Based Access Control (ABAC) contrôle d'accès. Access control is role and permission based (resource to actions). There is no attribute-based policy engine. En savoir plus
Better Auth prend-il en charge Fine-Grained Authorization (FGA / ReBAC) contrôle d'accès ?
Better Auth ne prend pas en charge Fine-Grained Authorization (FGA / ReBAC) contrôle d'accès. No relationship-based or policy-based authorization engine. Dynamic organization roles, teams and API key permissions cover coarser use cases. En savoir plus
Better Auth prend-il en charge API Authorization (Scopes / Permissions) contrôle d'accès ?
Better Auth prend en charge API Authorization (Scopes / Permissions) contrôle d'accès. The OAuth Provider plugin issues audience-bound JWT access tokens (RFC 8707 resource indicators) with per-resource scopes, introspection, and verifyAccessTokenRequest for resource servers. The API Key plugin supports per-key permissions, rate limits and expiry. En savoir plus
Better Auth prend-il en charge Audit Log Retention fonctionnalité de sécurité ?
Better Auth prend partiellement en charge Audit Log Retention fonctionnalité de sécurité. The open-source library has no built-in audit log. Better Auth Infrastructure records user, session, account, organization and security events, with retention of 1 day (Starter), 7 days (Pro) and custom (Enterprise). En savoir plus
Better Auth prend-il en charge Audit Log Streaming fonctionnalité de sécurité ?
Better Auth prend en charge Audit Log Streaming fonctionnalité de sécurité. Log drain is part of Better Auth Infrastructure Enterprise and listed as a $25/month add-on. En savoir plus
Better Auth prend-il en charge Security Center (Threat Monitoring Dashboard) fonctionnalité de sécurité ?
Better Auth prend en charge Security Center (Threat Monitoring Dashboard) fonctionnalité de sécurité. The Better Auth Infrastructure dashboard surfaces Sentinel security events: blocked requests, credential stuffing, impossible travel, geo-blocking, bots, suspicious IPs, velocity abuse and compromised passwords. En savoir plus
Better Auth prend-il en charge Encryption at Rest fonctionnalité de sécurité ?
Better Auth prend partiellement en charge Encryption at Rest fonctionnalité de sécurité. Encryption of the database is the host application's responsibility. The library encrypts JWT private keys with AES-256-GCM by default and supports versioned secrets for rotation, but OAuth provider tokens stored in the account table are not encrypted by default. En savoir plus
Better Auth prend-il en charge Encryption in Transit fonctionnalité de sécurité ?
Better Auth prend en charge Encryption in Transit fonctionnalité de sécurité. Secure, httpOnly, SameSite=Lax cookies are issued automatically for HTTPS base URLs. TLS itself is terminated by the host application or its infrastructure. En savoir plus
Better Auth prend-il en charge Customer Managed Keys (BYOK) fonctionnalité de sécurité ?
Better Auth prend partiellement en charge Customer Managed Keys (BYOK) fonctionnalité de sécurité. Everything is self-hosted, so secrets are customer-controlled. The JWT plugin supports custom signing functions backed by an external KMS (Google KMS, AWS KMS, Azure Key Vault) with a remote JWKS URL. En savoir plus
Better Auth prend-il en charge Bot Detection fonctionnalité de sécurité ?
Better Auth prend en charge Bot Detection fonctionnalité de sécurité. The captcha plugin protects sign-up, sign-in and password reset with reCAPTCHA v2/v3, Cloudflare Turnstile, hCaptcha, CaptchaFox or Vercel BotID. Better Auth Infrastructure (Sentinel) adds bot blocking. En savoir plus
Better Auth prend-il en charge Brute Force Protection fonctionnalité de sécurité ?
Better Auth prend en charge Brute Force Protection fonctionnalité de sécurité. Built-in rate limiting on all routes with stricter rules for sensitive ones (for example 3 requests per 10 seconds on email sign-in and on two-factor routes), account lockout on repeated failed 2FA attempts, and attempt limits on OTP codes. En savoir plus
Better Auth prend-il en charge Suspicious IP Throttling fonctionnalité de sécurité ?
Better Auth prend en charge Suspicious IP Throttling fonctionnalité de sécurité. Per-IP rate limiting with configurable trusted proxy headers and IPv6 subnet grouping in the open-source library. Better Auth Infrastructure (Sentinel) adds blocking or challenging of known malicious IPs and geo allow/deny lists. En savoir plus
Better Auth prend-il en charge Breached Password Detection fonctionnalité de sécurité ?
Better Auth prend en charge Breached Password Detection fonctionnalité de sécurité. The Have I Been Pwned plugin rejects compromised passwords at sign-up and password change using k-anonymity (only a 5-character hash prefix is sent). Sentinel also checks passwords at sign-in. En savoir plus
Better Auth prend-il en charge Credential Guard (Dark Web Monitoring) fonctionnalité de sécurité ?
Better Auth prend partiellement en charge Credential Guard (Dark Web Monitoring) fonctionnalité de sécurité. Sentinel in Better Auth Infrastructure detects credential stuffing from failed-login velocity and issues a proof-of-work challenge or a block. There is no dark-web credential monitoring. En savoir plus
Better Auth prend-il en charge Tenant Access Control List (IP ACL) fonctionnalité de sécurité ?
Better Auth prend partiellement en charge Tenant Access Control List (IP ACL) fonctionnalité de sécurité. Sentinel in Better Auth Infrastructure supports country allow/deny lists and suspicious IP blocking. No TLS-fingerprint-based restrictions are documented. En savoir plus
Better Auth prend-il en charge Device Fingerprinting fonctionnalité de sécurité ?
Better Auth prend en charge Device Fingerprinting fonctionnalité de sécurité. Sentinel uses a client-sent visitor ID (X-Visitor-Id header) for credential stuffing, free-trial abuse and device tracking detections. En savoir plus
Better Auth prend-il en charge Per-Organization Branding multi-tenant ?
Better Auth ne prend pas en charge Per-Organization Branding multi-tenant. No hosted pages to brand; the application owns all UI and can theme it per organization itself.
Better Auth prend-il en charge Per-Organization MFA Policy multi-tenant ?
Better Auth ne prend pas en charge Per-Organization MFA Policy multi-tenant. The organization plugin has no per-organization MFA policy. Organization hooks can be used to enforce one in application code. En savoir plus
Better Auth prend-il en charge Hosted / Universal Login Page fonctionnalité de branding ?
Better Auth ne prend pas en charge Hosted / Universal Login Page fonctionnalité de branding. No hosted login page. Better Auth is headless: sign-in, consent and account-selection screens are built in the application.
Better Auth prend-il en charge Embedded / Native Login Components fonctionnalité de branding ?
Better Auth prend en charge Embedded / Native Login Components fonctionnalité de branding. Authentication runs in the host application on its own domain with a typed client SDK; there is no redirect to a vendor domain. En savoir plus
Better Auth prend-il en charge White-Label / Full Brand Removal fonctionnalité de branding ?
Better Auth prend en charge White-Label / Full Brand Removal fonctionnalité de branding. No vendor branding anywhere in the flow, since every screen and email is part of the host application.
Better Auth prend-il en charge Localization / i18n fonctionnalité de branding ?
Better Auth prend partiellement en charge Localization / i18n fonctionnalité de branding. The i18n plugin translates API error messages (22 built-in languages, detection by header, cookie, session or callback). UI and email copy are owned by the application. En savoir plus
Better Auth prend-il en charge Prebuilt UI Components (SDK) fonctionnalité de branding ?
Better Auth ne prend pas en charge Prebuilt UI Components (SDK) fonctionnalité de branding. No official pre-built UI component kit; the client SDK is headless. Community UI libraries exist. En savoir plus
Better Auth prend-il en charge Login / Auth Analytics Dashboard analytique ?
Better Auth prend en charge Login / Auth Analytics Dashboard analytique. The Better Auth Infrastructure dashboard provides user, organization and session analytics and activity tracking. The open-source library does not include analytics. En savoir plus
Better Auth prend-il en charge GDPR: Data Export (Portability) conformité ?
Better Auth prend partiellement en charge GDPR: Data Export (Portability) conformité. No dedicated export endpoint. All user data lives in the application-owned database and can be exported by the application. En savoir plus
Better Auth prend-il en charge GDPR: Right to be Forgotten (User Deletion) conformité ?
Better Auth prend en charge GDPR: Right to be Forgotten (User Deletion) conformité. Account deletion (disabled by default) authorized by password, fresh session or an emailed verification link, with beforeDelete/afterDelete hooks. Deletion is a hard delete. En savoir plus
Better Auth prend-il en charge Consent Management conformité ?
Better Auth prend partiellement en charge Consent Management conformité. OAuth consent for third-party clients can be listed, updated and revoked per user, with skip_consent for trusted clients. No privacy or marketing consent management. En savoir plus
Better Auth prend-il en charge Region Deployment conformité ?
Better Auth prend en charge Region Deployment conformité. The library runs wherever the host application is deployed, so data residency is determined by the application and database hosting.
Better Auth prend-il en charge Private Cloud Deployment conformité ?
Better Auth prend en charge Private Cloud Deployment conformité. Runs inside the application on any cloud or on-premises infrastructure. There is no separate Better Auth server to deploy.
Better Auth prend-il en charge SDK Coverage intégration développeur ?
Better Auth prend partiellement en charge SDK Coverage intégration développeur. TypeScript/JavaScript only. A framework-agnostic client plus official integrations for the frameworks listed. There is no SDK for non-JavaScript backends. En savoir plus
Better Auth prend-il en charge Management API intégration développeur ?
Better Auth prend en charge Management API intégration développeur. Server-side auth.api exposes every endpoint as a typed function, and the admin and organization plugins cover user, session, organization, member and role management. There is no separate remotely hosted management API to authenticate against. En savoir plus
Better Auth prend-il en charge Authentication API Rate Limits intégration développeur ?
Better Auth prend en charge Authentication API Rate Limits intégration développeur. Configurable rate limiting (default 100 requests per 10 seconds in production) with per-route rules, wildcards, memory/database/secondary storage and custom storage. Server-side auth.api calls are exempt. En savoir plus
Better Auth prend-il en charge Actions / Extensibility Pipeline intégration développeur ?
Better Auth prend en charge Actions / Extensibility Pipeline intégration développeur. Request hooks (before/after), database hooks, per-plugin lifecycle hooks, and a plugin system for adding endpoints, schema and client behavior. En savoir plus
Better Auth prend-il en charge TypeScript Support in Extensibility intégration développeur ?
Better Auth prend en charge TypeScript Support in Extensibility intégration développeur. All hooks, callbacks and plugins are written in TypeScript in the host application with end-to-end inferred types. En savoir plus
Better Auth prend-il en charge Custom Domain intégration développeur ?
Better Auth prend en charge Custom Domain intégration développeur. Authentication is served from the application's own domain. Better Auth Infrastructure additionally offers a custom dashboard domain as a $25/month add-on. En savoir plus
Better Auth prend-il en charge Deploy CLI (Infrastructure as Code) intégration développeur ?
Better Auth prend partiellement en charge Deploy CLI (Infrastructure as Code) intégration développeur. The Better Auth CLI generates and migrates the database schema, but it does not export or import tenant configuration. Configuration lives in application code and is deployed with it. En savoir plus
Better Auth prend-il en charge Terraform Provider intégration développeur ?
Better Auth ne prend pas en charge Terraform Provider intégration développeur. No Terraform provider. Configuration is application code.
Better Auth prend-il en charge Custom Database Connections intégration développeur ?
Better Auth prend en charge Custom Database Connections intégration développeur. Bring your own database: PostgreSQL, MySQL, SQLite, MS SQL, MongoDB, and Drizzle/Prisma/Kysely adapters, plus community adapters and a guide for writing custom adapters. Stateless (database-less) sessions and secondary storage such as Redis are supported. En savoir plus
Better Auth prend-il en charge Native Webhook Support intégration développeur ?
Better Auth ne prend pas en charge Native Webhook Support intégration développeur. No outbound webhooks. Request and database hooks run in-process and can call any HTTP endpoint. En savoir plus
Better Auth prend-il en charge Universal Login / Hosted Login Page Customization intégration développeur ?
Better Auth ne prend pas en charge Universal Login / Hosted Login Page Customization intégration développeur. There is no hosted login page to customize; the application owns the UI.
Better Auth prend-il en charge Custom Email Provider (SMTP) intégration développeur ?
Better Auth prend en charge Custom Email Provider (SMTP) intégration développeur. Email is sent through application-provided callbacks (sendVerificationEmail, sendResetPassword, sendMagicLink, sendVerificationOTP and others), so any provider can be used. Better Auth Infrastructure also offers a managed email service. En savoir plus
Better Auth prend-il en charge Email Templates intégration développeur ?
Better Auth prend partiellement en charge Email Templates intégration développeur. Core library sends no templated email; the application renders its own. Better Auth Infrastructure Pro adds hosted email templates. En savoir plus
Better Auth prend-il en charge Custom OIDC Claims / Token Enrichment intégration développeur ?
Better Auth prend en charge Custom OIDC Claims / Token Enrichment intégration développeur. The OAuth Provider plugin supports customIdTokenClaims, customAccessTokenClaims, customUserInfoClaims and customTokenResponseFields. The JWT plugin supports a custom payload. En savoir plus
Better Auth prend-il en charge No-Code Auth Flow Builder / Orchestration fonctionnalité ?
Better Auth ne prend pas en charge No-Code Auth Flow Builder / Orchestration fonctionnalité. No visual flow builder; flows are code.
Better Auth prend-il en charge Identity Verification / Document Proofing fonctionnalité ?
Better Auth ne prend pas en charge Identity Verification / Document Proofing fonctionnalité. No built-in identity proofing or document verification.
Better Auth prend-il en charge Decentralized / Verifiable Credentials fonctionnalité ?
Better Auth ne prend pas en charge Decentralized / Verifiable Credentials fonctionnalité. No W3C Verifiable Credentials or DID support. Sign In With Ethereum (SIWE) is available as a wallet-based sign-in method. En savoir plus
Better Auth prend-il en charge Built-in Billing / Subscription Management fonctionnalité ?
Better Auth prend en charge Built-in Billing / Subscription Management fonctionnalité. Payment plugins for Stripe, Polar, Autumn, Dodo Payments, Creem, Chargebee and Commet link customers and subscriptions to users and organizations. En savoir plus
Better Auth prend-il en charge Agentic AI / MCP Server Authentication fonctionnalité ?
Better Auth prend en charge Agentic AI / MCP Server Authentication fonctionnalité. The MCP plugin and OAuth Provider (resource indicators, DPoP, Client ID Metadata Documents) support OAuth for MCP servers and AI agents. The Agent Auth plugin implements the Agent Auth Protocol (agent registration, capability grants, user approval via device authorization or CIBA, signed short-lived agent JWTs) but is under heavy development and may change. En savoir plus
Better Auth prend-il en charge Post-Quantum Digital Signature Algorithms fonctionnalité de cryptographie post-quantique ?
Better Auth ne prend pas en charge Post-Quantum Digital Signature Algorithms fonctionnalité de cryptographie post-quantique. The JWT plugin signs with EdDSA (default), ES256/ES512, RS256 and PS256, and the OAuth provider accepts the classical RS/PS/ES/EdDSA algorithms. No ML-DSA, SLH-DSA or FN-DSA support is documented. En savoir plus
Better Auth prend-il en charge Post-Quantum Token & Data Encryption fonctionnalité de cryptographie post-quantique ?
Better Auth ne prend pas en charge Post-Quantum Token & Data Encryption fonctionnalité de cryptographie post-quantique. No ML-KEM or HPKE token encryption is documented.
Better Auth prend-il en charge Post-Quantum Certificate & mTLS Support fonctionnalité de cryptographie post-quantique ?
Better Auth ne prend pas en charge Post-Quantum Certificate & mTLS Support fonctionnalité de cryptographie post-quantique. No post-quantum or hybrid certificate support is documented; the library does not terminate mTLS.
Better Auth prend-il en charge Post-Quantum Stateful Hash Signatures fonctionnalité de cryptographie post-quantique ?
Better Auth ne prend pas en charge Post-Quantum Stateful Hash Signatures fonctionnalité de cryptographie post-quantique. No NIST SP 800-208 stateful hash-based signature support is documented.
Comparer avec d'autres fournisseurs
Remarque : Les données actuelles sont basées sur la documentation/l'expérience des fournisseurs et peuvent ne pas être exactes à 100 %.