accepted
on 2023-12-08 Use SuperTokens for authentication and authorisation
Context and Problem Statement
To protect the API endpoints, I need an auth mechanism.
Decision Drivers
- It must be free
Considered Options
- SuperTokens
- Auth0
- Keycloak
Decision Outcome
Chosen option: “SuperTokens”, because it is free and easy to integrate with.
Pros and Cons of the Options
SuperTokens
- Good, because it is free
- Good, because it is easy to integrate
- Good, because it is open source
- Good, because it is a managed service
- Good, because it can handle passwordless and social logins
- Bad, because it is a start up
Auth0
- Good, because it has a Next.js integration
- Good, because it is a managed service
- Good, because it can handle passwordless and social logins
- Bad, because it can get expensive quickly
- Bad, because it is closed source
- Bad, because it has suffered recent data breaches
Keycloak
- Good, because it is free
- Good, because it is open source
- Good, because it can handle passwordless (partial) and social logins
- Bad, because it is not a managed service
- Bad, because it is complicated to integrate