Hello - I'm the cofounder of Clerk.dev. Congrats on your launch!
Indeed, we support password-based authentication. Developers can also choose social login, passwordless, or web3 (instead, or in combination). In practice, ~60% of developers are enabling passwords for their applications.
Our technology is agnostic and also supports traditional frameworks (node/express and ruby/rails have SDKs, python/django is under development).
We also support auth across N subdomains and mobile (currently just react native).
I read this to mean you support a session on a.domain.com being valid for b.domain.com -- but you still don't support the same email address tied to different users at different subdomains, correct?
Thanks for the feedback and kind words! Really looking forward to making authentication and account management easier for developers and end-users with you!
Indeed, we support password-based authentication. Developers can also choose social login, passwordless, or web3 (instead, or in combination). In practice, ~60% of developers are enabling passwords for their applications.
Our technology is agnostic and also supports traditional frameworks (node/express and ruby/rails have SDKs, python/django is under development).
We also support auth across N subdomains and mobile (currently just react native).