Let's say I have two customers, C1 and C2, and we provide some integrations infrastructure to them where Auth is powered by Supertokens (self-hosted for development purposes). Both customers have a common user, U1. If the user signs in to their products P1 and P2 using google, supertokens will assume that it is the same user as

third_party_user_id

is the same but will create two

sessions

. This might lead to some issues in the future as we will be using user_id for lots of other stuff. 1. Is there any way to consider them as separate users? 2. Should we use separate supertokens instance (cloud or local) for each customer? I guess, you will have something internally to manage multiple clients on the supertokens cloud.

hey!

Yes, for now.

yea we deploy separate cores.

> yea we deploy separate cores. Thanks, this clarified my doubt. > If you use our managed service, we can do this for you easily. That would be great. Right now, I am getting used to the ST and testing if I can use ST for all my core use-cases. Will get back to you once the testing is complete. > For self hosted, you will have to deploy separate cores, or then modify the logic to make the thirdpartyuserId per tenant - this will require a bunch of custom override code, but it would work Are you panning to provide multiple tenant support via single ST account in future?

> That would be great. Right now, I am getting used to the ST and testing if I can use ST for all my core use-cases. Will get back to you once the testing is complete. Ok. Please note that this will be an additional paid thing on top of the MAU count. We can discuss pricing on a call.

> Ok. Please note that this will be an additional paid thing on top of the MAU count. We can discuss pricing on a call. Understood.