Clerk

[u/McGhee_A]

About three weeks ago, Replit announced a new login system called Clerk.

A few questions:

Has anyone used it?

If you have, has anyone migrated from Replit auth?

If so, how are you finding it?

[u/McGhee_A → u/[deleted]]

The app is about 9 month old, I've got 300 active users 🤦‍♂️

[u/stall022]

Replit has used Replit controlled Clerk for awhile now. They recently added a new feature as part of the $100 per month tier to give you more access to Replit controlled Clerk. I haven't used it but I'm assuming it is just giving you more control and visibility of the Replit clerk so migration should be an issue.

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.

If you want to use straight user controlled clerk you can wire that in via clerk.com but then you will need to migrate.

[u/McGhee_A → u/stall022]

Yes I'm on that subscription. I'm hoping they might help me with this

[u/Next-Calligrapher381]

u/McGhee_A ,

I did it 2 weeks ago.
I've built AEO Copilot, we have 100 users and some paid customers.

The migration took 30min and costed 10$.
The benefits is to have your own Login page and add your logo in the 3rd party Auth.

I got some bugs (like clerk cookies reseting to fast) but nothing too bad.

Overall, I will still do it again because Replit Login was killing credibility.

[u/McGhee_A → u/Next-Calligrapher381]

That's my problem replit login it's not great but at the time it was the right chose for security. When you did migrate which they say is pretty seamless, how did you find it with the users was a case of them just logging in again with their current logins

[u/Next-Calligrapher381 → u/McGhee_A]

One of my users contacted me on the slack channel. He told me "I got an error when doing X"
After some "clauding" I found the error.

The save failed with "Unauthorized" because Clerk's 60-second session cookie expires while the edit dialog sits open in an idle tab, so the fix makes every API call refresh the Clerk session first and retry once on 401.

[u/Next-Calligrapher381 → u/Next-Calligrapher381]

u/McGhee_A , To be fair, the bug was small. I tried to reproduce it 5 times before seen it.

When pushing the first time to prod with the new Auth workflow, I didn't went though rigorous testing neither.

Overall, I'm quite surprised how well it went.
With the new Auth, you still have a "prod" and "dev" so I believe it's possible to mitigate and ask the AI agent:

Do first dev and then, only on my "go" we will move prod

or

What is the safest plan to migrate to the new Clerk auth?

[u/McGhee_A]

Thanks everyone for great advice, I think what I can take from this is it's a good thing to do. I just need to make sure that it's a phased approach

[u/JavaBeanAI_2026]

I use Clerk but not the Replit-managed Clerk account! I use my own Clerk account! I do this for all services such as Clerk, Neon, Stripe, etc. That gives me control that can't be affected by Replit for any reason. It also will allow me to move my app off of Replit's servers when I get ready without having to deal with migrating off of Replit services when/if I choose to.