One more question, since I have not implemented supertokens yet, and considering that all four frontends have their own user account login and separate accounts database on the single backend and the backend has one instance of supertokens core, will using the same instance of supertokens on the backend to manage all four types of sessions be fine? (While using a variable in JWT payloads to verify that the session token is of the right frontend depending upon the request route). The session gets verified since it is not expired and exists on the single supertokens core, but then a manual check of the JWT payload variable on the route to validate that the request comes from a session which was issued for the same frontend as that of the request.