Sign-in methods
Superheat Cloud has no passwords. You sign in with a six-digit code sent to your email, or with Google or GitHub.
| Method | What you do | Creates the account too |
|---|---|---|
| Email code | Enter your address, then the six digits we send | Yes |
| One redirect to Google and back | Yes, on first use | |
| GitHub | One redirect to GitHub and back | Yes, on first use |
Sign in with an email code
- Open cloud.superheat.xyz and enter your email address.
- Check your inbox for the six-digit code and type it. Pasting works too — one paste fills all six boxes.
- The console verifies the code and takes you to the dashboard.
The code screen also offers Resend code and Change email. Codes expire, so request a fresh one with Resend code if yours stops working.
This single flow both signs you in and creates accounts. There is no separate registration page.
Sign in with Google or GitHub
Choose GitHub or Google below the email field. You approve the request at the provider and come back signed in.
To use Google or GitHub on an account you started with an email code, link the provider first from Settings → Connected accounts.
Connected accounts
Settings → Connected accounts lists GitHub and Google, each marked Connected or Not connected, and lets you attach a provider to the account you are already signed in to.
- Connect sends you to the provider and links that identity when you return. An account started with an email code gains a Google or GitHub login without losing anything.
- Disconnect removes the link. The console refuses to remove the last one, so at least one sign-in method always remains.
Identity linking does not merge two separate accounts. It attaches a provider to the account in the current session.
Second factors
If you have an authenticator app or a passkey enrolled, the console asks for it after your email code, before it lets you in. See Two-factor authentication and Passkeys.
API keys are not a sign-in method
An shk_ API key authenticates scripts against the REST API. It acts as a member of its own organization and is rejected on account endpoints and on every admin action. It cannot be used to sign in to the console. See API keys.
Signing out
Settings → Sign out ends the session and returns you to the sign-in screen. Signing back in repeats the first factor, and any second factor you have enrolled.