Your front end is connected to the core via an API layer.

The api layer should use our node SDK

So it depends on how you have architected ur fronted / backend communication per app

So if you have multiple frontends that talk to the same API layer, then: (frontend1, frontend2.. frontendN) API Layer SuperTokens core If you have multiple API layers per frontend: (frontend1 API layer1, frontend2 API layer 2.. frontendN API layer 3) SuperTokens core. This will share the same users across all frontends Finally, you can run one core per frontend and backend. This will essentially create different users per app..

@User ^

Will there be an option at some point to choose a cloud service provider other than AWS (perhaps ... Linode?) for your managed service?

I’m the near term, we see ourselves supporting gcp and azure other than AWS.

But of course, we are open to supporting others too. Depends on engineering effort vs demand

For now though, you can use our self hosted version and run that anywhere you’d like

hey, i see you added social login, that nice! there is some video of how to basicaly setup supertokens.

@User we will be making a video shortly.

@User cool article about the auth0 acquisition

👍credit goes to @Adiboi

@User cool article 🙂

Thank you @User !

hello @User . We are here to help! What features of auth do you want? For example, social login or email password or magic links etc..

I think we're going to start with basic email/password auth.

There's some discussion of using magic links.

But my boss isn't fond of them.

Sounds good. Please see our emailpassword recipe here: https://supertokens.io/docs/emailpassword/introduction

it has email password sign up / sign in, forgot password flow and email verification flow

Thanks!

What are factors that will help you decide between us or other auth providers?

We like the ability you provide to run the system in-house rather than subscribing to a SaaS.

Makes sense!

Personally, I am not a fan of over-engineered, "enterprisey" systems.

We are engaged in rewriting an ancient ASP.NET app with a lot of middleware as a React/Express/Node app.

Got it. To be most helpful to you, there are other products out there as well which allow you to do in house auth - keycloak and fusionauth. In case SuperTokens doesn't work out for you, please have a look at those too (and would be great to get as much feedback from you as possible).

I looked at keycloak. It seems much more complex.

Our other developer is exploring fusionauth in parallel with my exploration of your product.