STOP Using Clerk Auth : here is WHY (nobody talk about that)

### Transcript {ts:0} Why you should stop using Clerk right now. I'm pretty bullish about Clerk {ts:6} since it's been released and I really think it's a big mistake to use this tool right now, especially since the IIA {ts:15} area arrived, especially since the AI area arrived. So let's deep why you should not use clerk together. So I make {ts:26} main five six points as we have just here. So what is the first point? Authentification is the core of your {ts:36} application. O defines your apps architecture. Why you should delegate the most important part of your app to a {ts:46} company that you don't control? Because what you actually delegating first user data credential session metadata all on {ts:55} day server you don't own the data anymore second app architecture your middleware roots components depends now {ts:64} on clerk SDK so a migration cost a lot business continuity if cler change pricing pivot or die you're stuck okay {ts:74} because all your app depends on this tool so now you to continue to use clerk because all of this view all of these {ts:82} components use clerk security model. So this is one good argument for clerk for big company that doesn't want to look {ts:92} like they handle everything on their own. Clerk have a really good security. So this is one good argument and you {ts:100} have the user experience pre-built components. What happened? You get the great lock in again password are not {ts:107} exportable in plain text all user sation terminate everyone must relog if you migrate use o cler provider middle {ts:114} weight you need to rewrite everything so here it's a bit [ __ ] but the main point is do you want to delegate {ts:122} authentification because few months ago there is a sense to {ts:128} delegate this because it was boring to rebuild the UI again and again and again but Now in this area is this worse to do … {ts:372} why why you need to pay for user? What is the reason you would pay for any user in your app? It's no sense. Like I just {ts:384} don't understand why anyone would use this tool. So {ts:390} what you have here when you pay is then you have a lot of upsell. … {ts:522} Okay, I don't understand. Uh so here we have the bing. ... Like basically it's stripe and they are like {ts:531} okay stripe is already a good software. Let's add the fees on top of it. All of this to add you shitty feature that code {ts:539} can vibe code in less than three second, right? Like clo vood this billing software in less than 3 seconds. But {ts:546} they will charge each of your user 0.7%. 0.7%. Is this insane? Yes, it's insane. Okay, … So we add more feature and we {ts:600} pay wall some of our previously free feature or we add re feature that our user require request {ts:609} and we basically put a price on it. phase three extract pred predatory pricing vendor locking assume so they {ts:617} will print money cla is a company that lose money for sure I don't know actually verify this information I think {ts:624} so for example o zero raised massive here is what happened cla is the same trajectory so we have just here {ts:633} then technical problem clarness gs is not optimized 50% of your app bundle it's a lot of [ __ ] so clerk creates {ts:642} some latency. I I have no I I didn't try it. Okay, so take this with a some salt. Okay, it's okay. Community Exod Why do {ts:652} you think CL pricing is predatory though? So they asked this directly to Cler founder. The typical CL developer {ts:660} journey months one to six cler is amazing. Months 12 the pricing month they send months 18 locked in or {ts:668} switched. So uh when we eat 50k user cler quest 5,000 a month switch to better o in two weeks save 50,000 a year {ts:678} sation terminate randomly user locked out for no reason super say noun issue $100 a month surprise at an image me