Hey everyone, just wanting to find out as Im struggling to seperate the two. Is SuperTokens only used for token management for users, or is it more similar to a self hosted Auth0 where SuperTokens also handles the creation, and management of users in a database?

hey @jordz2203 it's used for both - creation and sign in of users, as well as session token management.

Ah I see, thank you @rp_st . So am I correct in saying that SuperToken is very much like a self hosted Auth0 where we create an API to handle signups, sign in, session management, etc? Almost in a "decoupled" sense as the Auth system would be seperate to the rest of our services database which we work with directly?

yes and no. Our architecture is slightly different compared to auth0. We make it easier to customise the auth logic to meet your business needs.

Our client is wanting us to setup a SveltJS website for them as well as another service we have running already, but they want multiple different websites/platforms to all interact with the same user database. Similar to SSO but their own one I suppose. Which is why SuperTokens is attractive because one website is PHP based and another is Svelte based to the API is useful. Only thing Im struggling to workout is how "custom" we can store additional data in SuperTokens for our users, so if we need to store some credit they have, would we do it in their Super Tokens user or would we need another Database which we link with their UserID

you could store in our db or in yours (linked to the user ID we generate). Have a look at this architecture page to get started with: https://supertokens.com/docs/emailpassword/introduction

Thank you, I will take a look :)

will the two websites both have a login page? Or do you want to redirect the user to a common login portal from thr client websites?

@rp_st either works, I feel like a commin login page would be nice but not required

Having a login screen per website is possible whilst sharing the same user pool across all websites.