Skip to main content
Settings groups account-level configuration: your profile, security (password and MFA), the hardware quotas your account is authorised to use, and account deletion.

Multi-factor authentication

Lyceum Cloud supports TOTP-based multi-factor authentication using any standard authenticator app (1Password, Google Authenticator, Authy, etc.) plus a set of one-time backup codes for recovery. The flow is:
  1. EnrolPOST /mfa/enroll returns a secret and a qr_code_url for your authenticator app, plus a set of backup codes you should save somewhere safe
  2. ConfirmPOST /mfa/verify-enrollment with a code from the app activates MFA on your account
  3. Sign in — From now on, sign-in requires both your password and a current TOTP code (or one of your backup codes)
If you lose your authenticator, use a backup code to sign in, then regenerate the codes via POST /mfa/regenerate-backup-codes (which invalidates all the old ones).
MethodEndpointPurpose
GET/mfa/statusCheck enrolment status
POST/mfa/enrollStart enrolment
POST/mfa/verify-enrollmentConfirm enrolment
POST/mfa/verifyVerify a code during login
POST/mfa/disableDisable MFA (requires a current code)
POST/mfa/regenerate-backup-codesGenerate new backup codes

Quotas

Your account has a quota for each hardware profile. By default new accounts can launch CPU machines; GPU access is granted by Lyceum based on your usage and any agreements in place. Quotas exist to prevent accidental over-spend and to keep capacity available for everyone.
MethodEndpointReturns
GET/user/quotasBoolean per hardware profile
GET/user/quotas/available-hardwareJust the profiles you can launch right now
If you need a profile you don’t have access to, contact info@lyceum.technology.

Account lifecycle

MethodEndpointPurpose
GET/user/statusCurrent user profile
DELETE/user/deletePermanently delete your account
Account deletion is irreversible. It removes your runs, VMs, deployments, storage, secrets, API keys, and billing history. Export anything you want to keep first.