@User , it might actually be possible to have multi tenancy support with one core and one db (one table for all tenants) and simulate the properties of multi tenancy. For example, for email password: The constraint our tables have is that the userId must be unique and the emails must be unique. So you could use the

override

recipe functions feature on the backend to modify emails by adding the tenantId to them, so that if a user uses the same email across tenants, it will still be unique from the core's point of view. So an email like

user@example.com

would be modified to

user+tenantId@example.com