> All other providers require an OAuth implementation even if you do not need SSO because of the way they’ve architected their solution. With SuperTokens, we’ve decoupled the functionality for different use cases, making it possible to only worry about the features you need.
Eh? You’re either doing Oauth or you’re not? What have they decoupled?
For example, if you require email / password auth without SSO, then we do not use open ID connect or any of the oauth flows - because those are not needed in a simple setup.
