Yeah, we rolled our own auth as well. Everybody says you shouldn’t, it’s a risk, etc etc.
replybut to me that’s less risk than our auth getting bought by somebody whose business goals don’t necessarily align with mine.
The data lives in your server, everything is yours, if that happens, you just fork or write your own.
Not sure what writing yourself first buys here.
replyUsing something third party isn’t free - even for zero monetary cost there’s integration cost, documentation, support, and maintenance uncertainty.
replyThe choice between rolling your own and third party is already a trade-off. The future uncertainty around third party services without a clear business just tips the scales, it’s not the whole justification.
why not instead fork repo just in case but still use better auth until proven wrong? In case they go evil you just build from you forked one. At that point you would still have to either maintain your own auth or better auth fork.
replyWith current AI your agents probably still will be better with maintaining a fork. Auth libs have pretty limited API surfaces comparing to e.g. ui frameworks.
I prefer to maintain my code, tailored for my need, than maintaining a massive library that has support for every authentication method there is, while trying to be as generic as possible and fit every business.
reply