> A great alternative to Auth0, Firebase Auth and AWS Cognito
Can you elaborate a bit on how it's a great alternative, or what is different?
Sick of spending time on Auth, we built an open source 'Stripe for Auth'
91–100 of 347 posts
Re: Sick of spending time on Auth, we built an open source 'Stripe for Auth'
#92I know most people are not like this, but I don’t mind setting up auth “over and over” It’s always a chance to read about what’s changed in the technologies/ideas you usually lean on for it. Apply that simplification that you wish you could have for your already launched application. Maybe you have a need to make your auth slightly more proprietary. If you churn out applications all the time yeah I get why this could…
Ofcourse, everyone has their own preference. Thats an interesting perspective as well. My only counter to that would be that its time consuming to roll your own auth for a complex or large scale app. It starts off easy but soon you have to make significant investments in various aspects of auth. That isnt true for all apps ofcourse. Definitely good to keep learning though!
Part of it too is that I tend to work on smaller projects that don’t grow and change indefinitely like startup saas does. If you’re getting something up quickly where the requirements will change all the time, a service like this starts to make way more sense :)
Re: Sick of spending time on Auth, we built an open source 'Stripe for Auth'
#93> A great alternative to Auth0, Firebase Auth and AWS Cognito Can you elaborate a bit on how it's a great alternative, or what is different?
Indeed I’ve chosen each of the above for different projects. I’d really like to know what is different, specifically, about this product.
Re: Sick of spending time on Auth, we built an open source 'Stripe for Auth'
#94I know most people are not like this, but I don’t mind setting up auth “over and over” It’s always a chance to read about what’s changed in the technologies/ideas you usually lean on for it. Apply that simplification that you wish you could have for your already launched application. Maybe you have a need to make your auth slightly more proprietary. If you churn out applications all the time yeah I get why this could…
I hate doing auth and commodity features like user admin along with SSO integration, and hooking it all up to both the front and back end. I'd rather be busy doing business related features.
Nothing wrong with that, that’s the right mindset for getting things done
Re: Sick of spending time on Auth, we built an open source 'Stripe for Auth'
#95I really love what you are doing guys. Self-hosted option with SaaS model as an alternative - sweet, perfect pricing balance.
I don't know about others but I am really tired of settings up auth over and over again for over 8 years already. Don't give me firebase it sucks so hard I can't even open my eyes when auth needs more control or extension. Im going to give you a shot in my next project
Re: Sick of spending time on Auth, we built an open source 'Stripe for Auth'
#96Authentication is a solved problem; authorization is not. External authentication makes your system brittle, so I'm glad to see you can self-host SuperTokens for free. I've been working on Enterprise Access Control (EACL) in my spare time, an embedded Datalog-based library with a uniform declarative Clojure API that lets you write grant/deny ACL rules in the shape: Who, What, Why, When, Where & How that goes a little…
Authentication is not a solved problem. Every ecommerce website out there rolls their own, usually with obvious flaws. Some major banks too.
Re: Sick of spending time on Auth, we built an open source 'Stripe for Auth'
#97I would absolutely consider this once email verification exists for new accounts. But not until then. It looks like a good feature set and yes, I would love to use a solution from someone who focuses on auth vs. rolling my own. I do think your documentation could be expanded. You have some examples of how to use it with Netlify, but I'd love to see example apps for other cloud providers as well (Heroku, in my case.)…
I've been using Nhost backend plus in a project and it has email verification for new accounts: https://github.com/nhost/hasura-backend-plus
Re: Sick of spending time on Auth, we built an open source 'Stripe for Auth'
#98Hey, this product looks like a pretty decent "stack agnostic" way to handle auth. I've definitely considered using services like Cognito but always returned to "DIY" for the data ownership. A couple questions:
1. How will you keep bigger engineering teams on your platform if access to the data (and therefore migration) is easy?
2. I mainly work with Python. Typically I use Django's user system with my own user model and I copy and paste the client company's "general email template" into the verification / signup / reset emails and I'm done with it. If I need it on multiple services I install a JWT plugin. It takes maybe 10 minutes at the start of a project, and the developer experience is similar from what I have heard in Rails with Devise. Does this service have anything to offer to these "mature" stacks, or are you generally targeting newer ecosystems like Node / "frontend first" projects?
Also, your landing page looks great!! :)
Re: Sick of spending time on Auth, we built an open source 'Stripe for Auth'
#99I really love what you are doing guys. Self-hosted option with SaaS model as an alternative - sweet, perfect pricing balance. I don't know about others but I am really tired of settings up auth over and over again for over 8 years already. Don't give me firebase it sucks so hard I can't even open my eyes when auth needs more control or extension. Im going to give you a shot in my next project
Thank you! Really appreciate your kind words :) Have a great day
Re: Sick of spending time on Auth, we built an open source 'Stripe for Auth'
#100I know most people are not like this, but I don’t mind setting up auth “over and over” It’s always a chance to read about what’s changed in the technologies/ideas you usually lean on for it. Apply that simplification that you wish you could have for your already launched application. Maybe you have a need to make your auth slightly more proprietary. If you churn out applications all the time yeah I get why this could…
I never did it, what is a good guide to start? Thanks!
Hey! I don’t have a guide on hand, maybe another commenter will see this and have some resources :) Honestly my experience is just collected from 10 years working with and around other web applications, and as such is a bit ephemeral. I’d say any guides out there on the topic will arm with you enough knowledge to get started, or even working with services like the subject of this post. You’ll see the pieces at play in action, and can learn from them.