Earlier quoted context omitted.
This is my question as well. It's an honest question and hopefully someone can educate me. Why would anyone trust a third party with what is the most important asset, their users? Thank you in advance.
Hey, Braden one of the founders. It's a good question, and a question that gets asked a lot. Out of curiosity would you trust a more established company like Auth0 or Firebase? We hope to gain developers trust over time, and we want to build a tool that makes it dramatically easier to build out session management, and a lot of these user flows. A similar question that was asked only a few (10?) years ago, was "why wo…
Show HN: Clerk – all of user management as-a-service, not just authentication
61–70 of 234 posts
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#62I'm even hesitant to trust Auth0 for this, why would I trust a new company?
Also, is this permitted under the GDPR?
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#63Nice. If you could also add the ability to charge subscriptions from users and manage their subscription plans this would become a no-brainer. Also your pricing model could become very lucrative—you could charge a percentage of the revenue.
Definitely! We've found that developers want to apply subscriptions against either Users or Organizations, so first we're planning to build out Organization management first (create an org, invite members, setup SAML auth, etc). Subscription management will follow sometime after, and will probably look like a Stripe integration that automatically creates Stripe Customer objects for your Users and Organizations. Is th…
If I'm building a photo-hosting app, it would be a bummer to pay for/build out a big "Organization Subscriptions" feature; if I'm building an enterprise-oriented chat application, I wouldn't want to spend many hours or dollars on individual "User Subscriptions".
But that said, I recognize splitting out those two features is more of a cherry on top; the main value here is just having them available to me in the first place. Either way, definitely keeping my eye on Clerk! Good luck folks!
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#64Earlier quoted context omitted.
I forget what this effect is called. Every once in a while a new service comes along that tries to compete with Amazon and there is a huge cost of entrusting the new entrant.
I think I've seen the term "trust moat" used before, which I like for describing this effect.
Do I trust a new service or continue with one of the most trusted service from AWS?
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#65Earlier quoted context omitted.
Hi dubcanada, Thanks for your questions! It's good feedback that there's no security documentation up yet. We have a lot more content coming live in the next few weeks - but let me try to hit some of the most important points: * Session management is handled with secure, httpOnly cookies. We have you set a CNAME in production so we can set cookies in a first-party context (SameSite=Lax). * Cookies are scoped only to…
SOC 2?
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#661) Pricing is free up to 5,000 MAU
2) But the next pricing grade starts at 1,000 MAU for $49/mo + $0.05/MAU additional
so if you have 5,001 MAU you take a big leap from $0 to $249/mo
Is there a reason for that huge bump? Why doesn't the first pay tier start at 5,000 MAU?
And how is MAU even calculated? Like, aren't all users in the system active users? Or are you able to have a bunch of unactive users in the system as well not counted?
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#67Earlier quoted context omitted.
I can answer with the opposite question. Why would you trust your homemade solution instead of heavily invested experts? Auth0 (and Okta and a thousand others) do nothing but auth and customer management and do it at 1000X the scale as most enterprises. They do it way better than your IT team could possibly do it. And support every cutting edge feature and potential use case. You can also get them to absorb indemnity…
Because I'm a software engineer who has been building stuff like this for years...
Now, trusting this particular third-party? Definitely a big question mark! It's on them to earn your trust. But I think to say that third parties in general can't be trusted with your users is to be a little ignorant of the modern web engineering landscape. We trust a lot of people with a lot of things, and not in an unreasonable manner.
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#68Earlier quoted context omitted.
I can answer with the opposite question. Why would you trust your homemade solution instead of heavily invested experts? Auth0 (and Okta and a thousand others) do nothing but auth and customer management and do it at 1000X the scale as most enterprises. They do it way better than your IT team could possibly do it. And support every cutting edge feature and potential use case. You can also get them to absorb indemnity…
Authentication is webdev 101. If you can't roll your own you're in the wrong industry. I really can't think of any good reason to hand crucial control of a site over to any third party, much less user authentication where one breach will potentially cost you millions and land you in jail. The whole business model seems to revolve around being a crutch for people not capable or competent of running their own services.
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#69Earlier quoted context omitted.
This is my question as well. It's an honest question and hopefully someone can educate me. Why would anyone trust a third party with what is the most important asset, their users? Thank you in advance.
Hey, Braden one of the founders. It's a good question, and a question that gets asked a lot. Out of curiosity would you trust a more established company like Auth0 or Firebase? We hope to gain developers trust over time, and we want to build a tool that makes it dramatically easier to build out session management, and a lot of these user flows. A similar question that was asked only a few (10?) years ago, was "why wo…
The other concern is what happens if you shut down or decide to change your plan to be prohibitively expensive? (I'm not implying that's the case for you, but it's a consideration that has to be made). There have been vendors in the past that have abruptly shut down without warning, leaving their customers scrambling to build or find alternatives. In all honesty, I'd rather build an authentication system from the beginning than having to take my service down at a critical time.
This is actually a really interesting product though, and i would definitely consider it on future projects.