I got experience mainly with firebase and identity server. What is the usecase for supertoken instead something like identity server for .net, whatever Java spring uses or something like django or flasks authentication?
I’m far from an expert, but in past startups I’ve been scrambling to get SSO working for b2b saas, they bluntly said. Without sso we don’t want to use your service. So that was moved up our roadmap.
Even something like e-mail verification is something I will not go without anymore. It’s mandatory in some countries.
Honestly, next service that I will build will just be federated or magic email link if I can get away with it.
From the frontpage I cannot understand yet what makes this easier then the options above. Is this something you would use for your first 3000 customers? Imagine being the cto, when would I feel confident going for something like supertoken?
Also, it’s easy to ask questions like this, less so than building amazing things, so definitely Congratulations on the announcement!
> What is the usecase for supertoken instead something like identity server for .net, whatever Java spring uses or something like django or flasks authentication?
We plan on building a much more feature rich auth solution in a modular way - providing passwordless, 2fa, social, email / password login (exists already) + very secure session management using rotating refresh tokens (exists already). Being "modular" will enable users to only pick what they care about making it easy for them to implement. So we differentiate in terms of features and simplicity of use.
> Even something like e-mail verification is something I will not go without anymore.
Makes sense! Next on our feature list
> Is this something you would use for your first 3000 customers?
We aim that this would scale to a very large number of users - so you can implement it once, and then spend minimal time on it after.
I’m far from an expert, but in past startups I’ve been scrambling to get SSO working for b2b saas, they bluntly said. Without sso we don’t want to use your service. So that was moved up our roadmap.
Even something like e-mail verification is something I will not go without anymore. It’s mandatory in some countries.
Honestly, next service that I will build will just be federated or magic email link if I can get away with it.
From the frontpage I cannot understand yet what makes this easier then the options above. Is this something you would use for your first 3000 customers? Imagine being the cto, when would I feel confident going for something like supertoken?
Also, it’s easy to ask questions like this, less so than building amazing things, so definitely Congratulations on the announcement!