[mhamann]

We envision a future without passwords and where you can take your identity around with you and plug it in wherever you want, while also maintaining control of that personal info. Interestingly, the first thing clerk.dev asks for when you sign up is a password...

Additionally, we don't think you should have to have a React/Vue/Next.js/etc site just to add auth. We want this to be plug-and-play anywhere and work across all of your web properties (and eventually mobile too). That could make the marketing, docs, and support experiences better at so many websites with a level of integration that used to take weeks or months to build (if anyone even bothered).

[colinclerk]

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).

[abuehrle]

Hey Colin

> We also support auth across N subdomains

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?

[rgthelen]

Hey Colin!

Thanks for the feedback and kind words! Really looking forward to making authentication and account management easier for developers and end-users with you!

[rgthelen]

I honestly think we are tackling two different problems - Clerk.dev protects an app or website. We create accounts that span apps and websites - and we happen protect them.

Clerk.dev focuses on creating a great login page using low-code tools to get there.

We want to kill the login page. We want first time users to be able to enjoy an app or website first and then, when they fall in love with the product, then you ask for validation/authentication.

We ask "what does it mean to be authenticated?". We go beyond authentication by creating accounts for end-users, giving them control over their data (GDPR, CCPA compliant) and allowing developers to use that account data to customize pages well beyond a single app. Authentication is more of a check box for us, what you do with the data is our product.

Overall, If you are using Clerk.dev, I'd feel confident that your apps are safe and your users are protected. They use the latest tech and have a great team.