1. Add a passkey from your account settings
Sign in as you do today, open Account, then Security, and find the Passkeys section. Give the passkey a name (the device it lives on is a good one), choose Add passkey, and approve the prompt your browser or device shows. A passkey belongs to you, not to the company account: every team member adds their own.
2. Sign in with it
On the login page choose Sign in with a passkey, or start typing your email and pick the passkey from the browser's suggestion list where your browser offers that. Approve the prompt and you are in. Synced passkeys (iCloud Keychain, Google Password Manager) work on every device they sync to; a hardware security key works wherever you plug it in.
3. Keep a second way in
A passkey works alongside your password and any linked Google, GitHub, or Apple sign-in; none of them is removed by adding one. realuptime will not remove your last sign-in method, and it asks you to confirm before a passkey becomes your only way in. Add a passkey per device you sign in from, and rename or remove one at any time from the same Passkeys section.
4. What it protects against
A passkey is a cryptographic key bound to realuptime.io and unlocked by your device's biometric or PIN, so it cannot be phished, reused on a look-alike site, or guessed. Every passkey added, removed, or used to sign in appears in your account's audit log.
5. Stack frames link to the source line
Once a release carries both a repoUrl and a commitSha, every frame on an issue from that release links to that file and line on GitHub or GitLab at that exact commit (GitHub Enterprise and self-hosted GitLab hosts use their own URL shape and are recognized by hostname). For a frame symbolicated from an uploaded source map the link targets the original source path and line; for a raw frame, the bundler prefix (webpack://) and leading ./ or ../ segments are stripped. An absolute filesystem path, a CDN URL, or a node_modules frame gets no link rather than a guessed one.
Go deeper
The full reference lives in the docs: Security overview. Error codes named above are each explained in the error-code reference.