How to sign in to HyperMonitors with Google or GitHub
The login and signup pages offer Continue with Google and Continue with GitHub. What that round-trip does, how it differs from email and password, and when Continue with SSO is the right button.
Google and GitHub sign-in are on both the login page and the signup page. The buttons are “Continue with Google” and “Continue with GitHub”. You authenticate with that provider and come back to HyperMonitors. You do not type a HyperMonitors password for that path, and you do not hand the password to us.
What the round-trip actually does
- The button sends you to Google or GitHub. Approving there is the credential. HyperMonitors sees the identity the provider returns, not your password.
- You land on /auth/callback on the same site, then on the page you were trying to open. Use the same Google or GitHub account next time and you sign into the same HyperMonitors account.
- A new account gets an organization of its own. You do not join someone else’s organization by signing in with a work Google account. That joining behaviour is the SSO path below, and only there.
Password, provider, or SSO
Use Google or GitHub when that account is one you already protect and you do not want another password. Use email and password when you want a login that does not depend on either provider, including the reset flow: a recovery link that fails (it was opened on a different device, or it expired) sends you to a page that accepts the six-digit code from the same email.
If the account has a TOTP factor, a password sign-in stops and asks for the code before you are fully in. That step is the authenticator app, not the email. Provider sign-in does not replace a factor you already enrolled; do not assume the Google button skips it.
Continue with SSO is an Enterprise login
“Continue with SSO” is on the login page only. It asks for a work email or a domain, finds the identity provider that organization connected, and sends you there. The provider is SAML — Okta, Azure AD, Google Workspace, or whoever can publish metadata. An Enterprise organization connects it with a metadata URL. Teammates whose email is on a verified domain are added to that organization on their first SSO login. Nobody else sees the button do that, and a Free or Solo account does not gain it by typing a domain.
After you are in, the app can run in German. The language is a setting on the account, and an organization can set a default for team emails. The marketing site has the same choice. Neither Google nor GitHub picks it for you.