Install
Romp ships as a single tarball. The installer drops it under
/opt/romp, sets up a per-otter systemd service so each
module restarts on crash, and adds romp to your PATH.
Linux — quickest path
curl -fsSL https://jandgstudios.fun/install.sh | sh
sudo systemctl enable --now romp.target
romp status
That fetches the latest tarball, verifies the SHA-256 against the one
on the download page, extracts to /opt/romp, installs an
Ed25519 license-verifier public key, and registers a systemd template
unit (romp@.service) plus a target
(romp.target) that pulls all eight otters and the
watchdog up at boot.
Linux — verifying before piping
If you don't curl-pipe-bash strangers (good), grab the bundle and check the signature first.
VER=$(curl -s https://jandgstudios.fun/releases/LATEST)
curl -sLO https://jandgstudios.fun/releases/romp-${VER}.tar.gz
curl -sLO https://jandgstudios.fun/releases/romp-${VER}.tar.gz.sha256
sha256sum -c romp-${VER}.tar.gz.sha256
sudo tar -xzf romp-${VER}.tar.gz -C /opt/
sudo /opt/romp/install.sh
macOS
Same tarball, no systemd. Use the bundled launchd helper:
brew install node ffmpeg jq
curl -sLO https://jandgstudios.fun/releases/romp-latest.tar.gz
sudo tar -xzf romp-latest.tar.gz -C /opt/
sudo /opt/romp/install.sh --launchd
romp status
Windows
PowerShell wrapper. Requires Windows 10+ with PowerShell 5.1 and Node 20+ on PATH.
iwr -useb https://jandgstudios.fun/install.ps1 | iex
romp status
License key
After install, drop the license JSON you got from your purchase email
at /opt/romp/.license.json (Linux/macOS) or
%PROGRAMDATA%\Romp\.license.json (Windows).
romp license verify # confirms the Ed25519 signature
romp license info # shows tier + expiry
Romp validates the signature against a public key bundled at install time. The license file is harmless to share between your own machines (it's tied to your tier, not a single host).
Optional — LAN scanning
By default Romp refuses to scan RFC1918 / loopback targets. If you're scanning your own LAN or staging:
echo 'ROMP_ALLOW_PRIVATE_TARGETS=1' | sudo tee /etc/romp/env
Cloud-metadata endpoints (169.254.169.254) stay blocked
regardless.
Next
Walk the CLI cheatsheet or jump to The Pack to see what each otter actually does.