Account & access
Choose a sign-in method, understand approval, and keep your workspace recoverable.
Choose a sign-in method
When available, Create account with a passkey opens your device’s sign-in prompt. Use Touch ID, Face ID, a PIN or a security key. No email or password is required. Your device keeps the private credential; Reliquary stores its public credential, never your fingerprint. Already have a passkey? Choose Sign in instead.
Google and EVM or TAO browser wallets remain alternative sign-in methods. Google opens an explicit account chooser. Wallet sign-in verifies a signed challenge; choose an EVM extension explicitly when several are installed. Signing in does not approve a product or start a workload.
In Account & access, add a second passkey or explicitly link Google or a wallet for recovery. Adding a sign-in method requires confirmation from an existing method. Matching email addresses never merge accounts. Keep at least one working sign-in method; a member ID alone cannot recover a lost account.
A passkey-only or Google-only account can request early access without an email. Link an EVM or TAO wallet before pilot activation. Adding the first wallet within five minutes of signing in preserves the member ID and saved work. Administration, funding and paid execution retain their existing wallet confirmation and product permissions.
The temporary-account option uses a seven-day browser cookie. Add a passkey, Google or wallet while it remains signed in to preserve that account. A lost temporary session without a linked sign-in method cannot be recovered.
Sign in — Use a passkey, Google or a supported browser wallet.
Account workspace — Review sign-in methods, sessions, and product access.
Check access before execution
Approval is specific to a product. It does not start work, fund the account, or make an unavailable runtime executable. Read the access state and the action message in the workspace.
| Stage | What it gives you |
|---|---|
| Public browsing | Inventory, catalogs, provider comparison, and public monitoring. |
| Signed-in account | Account management and permitted private workspace features. |
| Product approval | Permission to use the approved training, dataset, or evaluation workflow. |
| Runtime availability | An executable qualified profile or enabled order route. |
| Reviewed confirmation | An explicit launch or service-credit reservation after checks pass. |
Request early access
Choose Training Data, Training or Compute. Sign in with a passkey, Google or wallet, then submit your request. It belongs to your account immediately and you can follow it across visits. A contact email and pilot details are optional. Every product remains subject to its own manual approval.
If you explicitly choose your linked Google email when submitting, a recently authenticated Gmail or Google Workspace address can be confirmed immediately. Other addresses receive a one-use verification link when sending is available. Email verification never blocks submission of an account-owned request.
Without an account, you can leave an email first and verify it later. A verification link lasts 30 minutes. Open it, confirm the address, sign in and explicitly associate the request. Typing an email alone cannot claim someone else’s request. Contact verification is not an email sign-in or recovery method, and submission does not grant product access or subscribe you to marketing.
Request pilot access — Tell us what you want to build.
Finish email verification
Verification emails are transactional messages for requests you initiate, not a newsletter subscription. Never share verification links, invitation links, wallet recovery material, or API keys.
- Use the latest verification email. Links expire and can be used only once; opening the page does not itself verify the address.
- Check the account shown before confirming the association. Use the passkey, Google or wallet account you intend to keep.
- If delivery is unavailable or the link has expired, return to the early-access form. A saved request remains distinct from email delivery and verification.
- An invitation is a separate approval step. Link a verified EVM or TAO wallet to the intended account before pilot activation and invitation acceptance, then open one of the products it grants. Google sign-in alone does not activate a pilot.
Manage your sessions and records
The account workspace shows active-session metadata and lets you manage passkeys. Signing out other sessions requires a fresh passkey or linked-wallet approval, or a Google sign-in within two minutes. The current browser stays signed in. Removing a passkey signs out sessions using it; you cannot remove your last sign-in method.
The account-record export contains up to 100 recent metadata records per collection, including sign-in-method metadata and account-owned access requests. File contents, artifacts, credential values, configurations, and order payloads are excluded. Download your datasets and run artifacts separately when you need those contents.
Privacy & data — Read the current storage and data-handling information.
Early-access terms — Review the terms for pilot workflows.