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