“im by no means an expert in clerk or your specific use case, so forgive me for some curiosities. but once you expose email login, your existing google/apple sso users are going to see that form, which you are ok with”
“the server-side utm storage before the clerk redirect is the right repair. i'd add one more layer so the attribution survives every auth path, not just the current google flow”
“Clerk stripping UTMs is such a pain, we had the exact same thing happen last year. Took us forever to even notice because the numbers looked fine at a glance, just slightly off in ways that didn't trigger any alarms.”
“Turns out Clerk (our auth provider) was stripping our UTM parameters during the signup flow, so we couldn't actually trace signups back to the right campaigns. That's fixed now too, but man, attribution debugging is a rabbit hole.”
“Phase that actually stings is everything your saas silently leans upon. Sendgrid for email, auth0/clerk for auth and a managed postgres or stripe webhooks calls back to your own api.”
“> How many paid auth providers let you export user password hashes so that you can seamlessly migrate to another vendor, if you want to?Clerk is surely one of the biggest and allows you to do this.”
“You can use tools like Lovable, Bolt, Replit, Cursor, Claude Code, Supabase, Firebase, Flatlogic, Clerk, Stripe, Vercel, Render, Railway, Bubble, Webflow, Framer, Retool, Appsmith, n8n, Zapier, Make, PostHog, Sentry, and others to get from idea to something that looks like a real product much faster than before.”
“I had hopes for clerk.dev, but unfortunately the auth business optimizes for deep lock-in + steadily escalating prices.After working through a few transitions to/from Auth0 that is something I never ever want to do again at scale.”
“the migration can look fine at login while existing accounts lose access to their data if the old replit id isn’t linked correctly to the new clerk id. i’d test a few real account paths against a database copy first, then move one protected route at a time.”
“I would keep auth verification on the API and have Clerk issue the token, then the API checks it and decides which user the request belongs to. dont trust a user id sent by the app by itself.”
“If you don't pay the $100 a month tier then you will just have access to Replit controlled Clerk which means you have no access and is not great on a production app since the login splash screen says logging onto Replit instead your app/webpage.”
“Keep Server Actions on the web side, expose a proper API for mobile, and validate the Clerk token server-side to derive the user. A monorepo with shared types/API contracts can work really well too.”
“Convex is handling the database because I like the real-time sync, Clerk is handling auth because it’s easy to get running, and Linq is what I’m using to actually send and receive iMessages.”
“Auth and payments are exactly where boilerplate services earn their keep, Clerk or Supabase for auth and Stripe's prebuilt checkout will save more time than rolling your own for a first launch”
“The problem I am running to is with using Clerk Auth but currently have a method to get the session token and make sure it’s always correct. Essentially making sure I am getting the correct user info and data via token but just trying to understand if I am approaching this correctly.”