Docs · Getting Started
Installation
The Fleet installs with a single command and runs anywhere Python 3.8+ is available. The desktop app is built from source with the Tauri toolchain.
pip install nexus-fleet and apply your token viaNEXUS_LICENSE. Both on one machine — install each; redeem the Pro code once in the GUI and the CLI reuses the same device-bound license automatically (no second code).Nexus Fleet (CLI)
Pick either package manager — both install the umbrella nexus command + five twins.
With pip (recommended)
pip install nexus-fleet
nexus --version # nexus 2.2.1With npm
The npm package is a thin Node wrapper around the Python engine; it still requires Python on the host.
npm install -g nexus-fleetEither way you get the umbrella command nexus plus:
nexus-manager— the central API server + web dashboardnexus-agent— the endpoint daemonnexus-cli— the interactive SOC consolenexus-dashboard— standalone dashboard servernexus-license— license generation & inspection
Python 3.8+ — no cluster, indexer, or heavy runtime to manage.Nexus Desktop (GUI)
Install the released app (recommended)
Download and run the installer — it bundles the Python engine and runtime, so end users need nothing else. On first launch the Setup Wizard handles the ethical-use agreement and optional one-click tool installation.
Nexus_2.2.1_x64-setup.exe # Windows x64 installer (NSIS)Build from source
The GUI is a Tauri 2 application. Building it from source needs Node, Rust and Python installed.
git clone https://github.com/chandafa/cyber-nexus-.git nexus
cd nexus
npm install
npm run tauri:dev # development with hot reload
npm run tauri:build # production installer (.exe / .msi / .dmg / .AppImage)Toolchain
- Windows — Visual Studio C++ Build Tools + WebView2
- macOS —
xcode-select --install - Linux —
libwebkit2gtk-4.1-dev build-essential libssl-dev libgtk-3-dev librsvg2-dev
After installing — what next?
If you installed the CLI (Fleet)
- Verify it:
nexus --version(printsnexus 2.2.1). - Start a manager, then enroll agents — see Fleet.
- Apply a Pro token with
export NEXUS_LICENSE=<token-or-file>ornexus cli apply-license.
If you installed the Desktop app (GUI)
- Launch it; the Setup Wizard handles the ethical-use agreement and tool detection.
- Redeem your Pro code in Settings → License — it binds to this device.
- Free modules work immediately; Pro modules unlock once the license is valid.
I already have one — can I add the other?
Yes. Install the second one normally. You do not need a second license code. Redeem your Pro code once (in the GUI or via the CLI) and it is stored device-bound at~/.nexus/desktop_license.txt — the desktop app, the CLI, and Fleet all read the same token automatically. One device, one code, everything unlocked.