Convex's self auth system
Currently, I am converting all my client projects from Supabase to Convex and for all the new clients I am directly asking them to give Convex a chance.
But the clients are only hesitant majorly about one thing that I have noticed :
Is the Costing
They don't want to pay separately for backend and authentication and want a single-stop solution that includes both auth and backend together.
So I request the Convex team to think about this and in future add Convex self-auth system
11 Replies
I know we can still push our own in-house auth, but it will be more time-consuming and will add more complexity to project
@Abhishek we hear you, makes sense. we actually have plans to roll something out here soon
thanks for the patience!
auth.js should be working fine with convex. In case you are interested to go forward with that
@trace any example repo ?
Thank you so much @jamwt
https://discord.com/channels/1019350475847499849/1206723995781832765/1206751852826337330
I am working on one with next.js based on the code from there. Will let you know once I am confident enough to share it.
@jamwt , great to hear this. Beyond cost, keeping things in sync across web and mobile without an external auth would be great. One thing we particularly liked about supabase was being able to use the same supabase auth id as the userProfile id. This was done via a database webhook, and make it very easy to streamline the same auth user to db user.
yep. all this is pretty doable with e.g. clerk, but it is more work for sure. it's a pretty common request we get for projects (especially in the early iterative phases) to use some sort of on-platform first party auth thing. it will never be as full-featured as, say, clerk. but we can do something useful for projects that would love to keep things simple.
Clerk is giving me constant headaches. Now with the core2 upgrade i can't use Chrome. And for a long time i haven't been able to test with cypress. Clerk's new docs are partially updated and the components, middlewares have many breaking changes. It is chaos and their support service isn't enough to handle all the requests
I am willing to implement a custom simple auth so i can wait while Convex rolls its own auth
any advice is welcomed
Can you stick with the version of Clerk that’s been working for you (4.x) before they iron out any issues?
I'm trying to rollback
but the DevExperience has been deteriorating significantly since i first started to use it
still better than Auth0
