Installation
Platform install commands, GUI pilot status, local listener defaults, and release trust boundaries for B3IQ.
B3IQ installs a host agent service, serves the setup wizard locally, and exposes
local APIs after the operator claims the node. Public install routes live on
b3iq.org.
Platform Commands
| Platform | Command | Service | GUI status |
|---|---|---|---|
| Linux | curl -fsSL https://b3iq.org/install/linux | sudo bash | systemd | DEB gated on package trust and desktop VM smoke |
| macOS | curl -fsSL https://b3iq.org/install/macos | bash | launchd | Signed and notarized DMG public pilot |
| Windows | irm https://b3iq.org/install/windows.ps1 | iex | Task Scheduler | NSIS gated on Authenticode and VM smoke |
What The Installer Sets Up
Download and verify release artifacts
Public installers verify downloaded host-agent binaries against published release checksum metadata before execution or installation.
Install the host agent
The service starts as the local owner context for macOS and Windows, and as a systemd service on Linux.
Bind local setup
The default local API and wizard listener is http://127.0.0.1:8831.
Appliance or LAN-exposed installs must set explicit environment gates.
Open setup
The operator claims the node, creates local owner auth, reviews inventory, and chooses Local or Managed Mode.
Trust Boundaries
Treat public installers as pilot installers
Use them for validation, local node setup, and controlled pilots while production trust gates continue to close.
Overstate production package trust
Windows Authenticode, Linux package trust, production update rollback, and clean or reused machine GUI smokes are still explicit launch gates.
LAN And Appliance Installs
The host-agent-owned Linux installer wrapper binds setup and local inference to loopback by default. Use an explicit non-loopback listener only when you are building an appliance or LAN-managed deployment and understand the exposure.
bashB3IQ_ALLOW_LAN_LISTEN=1 b3iq-host serve --listen 0.0.0.0:8831
Setup tokens, local owner sessions, support grants, and local API keys are powerful local credentials. LAN mode should be paired with real network controls and an operator-owned recovery plan.