Beta Registration
BeamUp private SLC access is code-gated. WorkOS proves browser identity with GitHub, and BeamUp admits new users only after a one-time beta access code is redeemed.
First Registration
Section titled “First Registration”- Open the private beta dashboard URL from your invitation.
- Select
Continue with GitHub. - Complete WorkOS/GitHub sign-in in the hosted browser flow.
- If this is your first BeamUp login, the dashboard redirects to
/register. - Enter the one-time beta access code from your invitation.
- After the code is accepted, BeamUp creates your user and starts a secure dashboard session.
- You land on the authenticated app dashboard. If no apps exist yet, the
dashboard shows the CLI path beginning with
beamup loginandbeamup deploy.
The beta access code is used only once. Returning browser sign-ins with the same WorkOS identity do not ask for another code.
Returning Browser Login
Section titled “Returning Browser Login”Open the dashboard URL and select Continue with GitHub. If the WorkOS identity
already maps to a BeamUp user, BeamUp starts a new dashboard session and sends
you to /dashboard.
Returning login does not create a new user and does not consume a beta code.
Browser Logout
Section titled “Browser Logout”Use the dashboard Log out action to end the browser session. Browser logout is
separate from CLI logout:
- Browser logout clears the dashboard session cookie.
beamup logoutrevokes and removes the stored CLI token from the OS keychain.- A browser session does not place a BeamUp token in browser storage or expose one to JavaScript.
Registration Errors
Section titled “Registration Errors”Invalid, expired, revoked, and already-used beta codes all show the same safe registration error. BeamUp does not disclose which condition applied.
If the registration window expires or cannot be verified, start sign-in again from the browser login page. If WorkOS or GitHub sign-in is temporarily unavailable, wait and retry. Existing unexpired CLI tokens and dashboard sessions are not invalidated just because the identity provider is unavailable.
Security Notes
Section titled “Security Notes”- Do not send beta access codes in shared logs or screenshots.
- Beta access codes are not accepted by
beamup login; the CLI can only log in after browser registration has created your BeamUp user. - BeamUp never receives your GitHub password.
