Skip to content
BeamUpbeamup docs

Install The BeamUp CLI

Install the beamup CLI first, then create your browser account and run beamup login. The private beta does not require Cargo, npm, a Dockerfile, or a BeamUp app SDK for the supported deploy path.

macOS With Homebrew

Section titled “macOS With Homebrew”
Terminal window
brew install beamup-run/tap/beamup

Verify:

Terminal window
beamup --version

Homebrew owns the PATH setup through your Homebrew installation. Update later with:

Terminal window
brew update && brew upgrade beamup

Linux glibc 2.39+

Section titled “Linux glibc 2.39+”
Terminal window
curl -fsSL https://beamup.run/install.sh | sh

The Linux installer currently supports glibc 2.39+ x86_64 and glibc 2.39+ arm64. It writes the binary to $HOME/.beamup/bin and prints PATH guidance when needed instead of modifying shell startup files.

Verify:

Terminal window
beamup --version

Rerun the same installer command to update later.

Windows

Section titled “Windows”

Use PowerShell 7 when available:

Terminal window
pwsh -NoProfile -Command "irm https://beamup.run/install.ps1 | iex"

If pwsh is not installed, use Windows PowerShell:

Terminal window
powershell -NoProfile -Command "iwr https://beamup.run/install.ps1 -UseBasicParsing | iex"

The installer writes beamup.exe to %LOCALAPPDATA%\BeamUp\bin and updates only the current user’s PATH. Open a new shell if the current shell cannot find the command immediately.

Verify:

Terminal window
beamup --version

Rerun the same installer command to update later.

What The Installers Do

Section titled “What The Installers Do”

The Linux shell and Windows PowerShell installers download BeamUp-controlled release metadata from https://beamup.run, select the matching supported target, verify the published SHA-256 checksum, and install into a user-writable directory.

They do not read, ask for, print, migrate, or store BeamUp tokens, WorkOS tokens, beta access codes, app names, source paths, or keychain entries. Login is a separate step after browser registration.

Supported private-beta targets are macOS Apple Silicon, macOS Intel, Linux x86_64 glibc 2.39+, Linux arm64 glibc 2.39+, and Windows x86_64. Unsupported targets are 32-bit operating systems, Windows ARM64, older glibc Linux distributions, Alpine/musl Linux, BSDs, and source-build-only paths such as cargo install or npm.

Next Step

Section titled “Next Step”

Create your browser account before CLI login. Open the dashboard URL from your invitation, sign in with GitHub, and redeem your one-time beta access code. Then continue with Quick Start.