Quickstart
From install to first result.
About 5 minutes, start to finish. Every command below is real — nothing here is aspirational.
All you need is a terminal — Terminal.app on macOS, PowerShell on Windows. No Python, no package manager required first.
1. Install
The fastest, best-supported way to install and stay up to date — no Python needed, self-upgrades on re-run:
curl -fsSL https://raw.githubusercontent.com/Nexus-InferGauge/infergauge-releases/main/install.sh | shchmod +x the binary if it isn't already executable.Other ways to install
pip:
pip install infergauge
infergauge init -y && infergauge runHomebrew (macOS/Linux):
brew install Nexus-InferGauge/infergauge/infergauge2. Create your account
Free — no card, no license key. 25 concurrent users, 120 seconds per run, 10 runs a month.
Create account3. Sign in and run your first test
infergauge login --server https://console.infergauge.com
infergauge init # interactive setup -> infergauge.yaml
infergauge run --sync # live dashboard opens, results sync to the consoleinit and you don't need an API key at all — it behaves like a real endpoint, degrading past a saturation point and rate-limiting under load, so every chart and insight in the dashboard lights up on the very first run.--sync and results show up in the console's Overview and Runs tabs automatically.infergauge.yaml — export it as an environment variable instead. Configs get committed, attached to bug reports, and shared with teammates; a key inside one will eventually leak. Full walkthrough (including the exact export commands per OS) is in the quick start guide.4. Need more than Free?
Spike or endurance tests, self-hosted endpoints, or unlimited runs need a license token from us — once you have one:
Paste it into the console
Sign in, click License, paste the token. Tier updates immediately, no restart needed.
Using the CLI
infergauge login --server https://console.infergauge.com
infergauge run infergauge.yaml --syncSigning in once and always passing --sync is enough — the CLI checks the account's real entitlement on the console at run time, so a console upgrade just works. Fully offline/air-gapped use is the one exception, using INFERGAUGE_API_KEY/INFERGAUGE_FERNET_KEY environment variables instead — see the quick start guide for that path.
Something not matching what you see?
The full guide covers every platform in detail, updating an existing install, and troubleshooting — from Gatekeeper warnings to a stray old pip install silently taking priority.