Sign-in for the people who use your app
Your users sign up and sign in with an address and a password, a magic link, a phone, or their Google, GitHub or Apple account. You choose which of those are on, and you get one address to point your application at.
One address
Where your users sign in
Your users
Managed from the console
Your domain
Or ours until you have one
Ways your users get in
Google, GitHub and Apple are the three you set up from the console. The platform carries the credentials for twenty more providers, and each reaches the console as it is proved.
Every way in is a switch
An address and a password, a magic link, a one-time code, a phone number, or no account at all. Turn one on in the console and your users have it.
Your users, in your console
When somebody cannot get in, look them up, see how they signed up and put it right. No admin tool to write before the product is usable.
Your name on all of it
Send your users' mail through your own relay in your own words, and serve sign-in from your own domain. Tokens already in a browser go on verifying.
A package of your own is coming
@hiveops/auth will be the client your application imports, written from scratch with no dependencies of its own. It is not published yet, so today your application talks to the group's own address directly, over ordinary HTTP.
Coming