Cards / needs / Federated Identity & Authentication

Federated Identity & Authentication

Self-hosted alternatives to Auth0, Clerk, AWS Cognito and Firebase Auth.

What people say

• add sign-in to my site or app
• members sign-up and login
• one login for my apps
• keep my user list myself

Why people self-host it

People leave Auth0, Clerk, AWS Cognito, Firebase Auth for it. Why, strongest first: control, cost, privacy.

Does it suit a machine of your own?

Fits, with conditions works well for apps you build; the sign-in service must stay up, or nobody can log in

Questions that decide it

• who signs in: people you invite, or the public?
• is the content served by something that checks the sign-in?

How to publish it

Usually

sign-in pages on none, the admin console on org (the accounts card)

When the data is private or sensitive

the same, with the admin console on org only

Who sees what inside it

roles and organizations in the identity app decide what each signed-in person may see; the content must be served by something that checks them

The machine

always on

For builders

sign-up, sign-in, and a user list for a product prototype, kept on a machine you control

Cards for it

• accountsSign-up and sign-in for your visitors, and the console that manages themnot tested yet

Category from awesome-selfhosted.