Getting Started Cameras & Video Detection & Recording Industry & Edge Automation & Events Actions Integration & Connectivity Network & Discovery AI & Remote Control MQTT Modbus Pi4J & Raspberry Pi GPIO ZeroMQ System & Administration Comparisons Use Cases Troubleshooting About & Legal
Home / Documentation / Install Banalytics Agent on Linux x86_64 or ARM64
LinuxInstallation10 min

Install Banalytics Agent on Linux x86_64 or ARM64

A complete text guide for Debian/Ubuntu-family systems, industrial PCs, ARM edge computers, and Raspberry Pi-class devices.

The Linux package is a small bootstrap archive. The installer detects the platform-specific Core version, downloads and verifies JDK 25, installs native dependencies, and registers Banalytics as a systemd service.

Community setup pathInstall on WindowsCommunity Edition
// Requirements

Confirm the operating system and installation boundary

Linux x86_64

Use a 64-bit Debian/Ubuntu-family installation with systemd and apt on a PC, mini server, industrial computer, or VM with access to the required devices.

Linux ARM64

Use a 64-bit Debian/Ubuntu-family ARM installation on a Raspberry Pi-class device or ARM edge computer. A 32-bit operating system is not supported by this package.

  • Privileges: sudo or root access is required to install packages, configure hardware groups, and create the systemd service.
  • Connectivity: Internet access is required during installation for Portal metadata, JDK 25, Banalytics Core, and operating-system packages.
  • Utilities: ensure wget, tar, sed, and sudo are available before running the installer.
  • Package manager: the current installer uses apt to install media, USB, audio, and system utilities.
Production review: the current installer creates a system service with broad local hardware access. Review the generated unit, device permissions, network policy, and host-hardening requirements before using the Agent in production.
// Linux x86_64

Download the x86_64 package

mkdir -p ~/banalytics
cd ~/banalytics
wget https://storage.googleapis.com/banalytics-packages/banalytics-box/linux-x64/linux-x64-2.1.0.tar.gz
tar xzf linux-x64-2.1.0.tar.gz
cd banalytics-box
chmod +x *.sh
sudo ./install.sh

The archive is approximately 3.1 KB because it contains the bootstrap installer rather than the complete runtime. Keep the terminal open while the installer downloads JDK 25, Core, native dependencies, and media utilities.

// Linux ARM64

Download the ARM64 package

mkdir -p ~/banalytics
cd ~/banalytics
wget https://storage.googleapis.com/banalytics-packages/banalytics-box/linux-arm64/linux-arm64-2.1.0.tar.gz
tar xzf linux-arm64-2.1.0.tar.gz
cd banalytics-box
chmod +x *.sh
sudo ./install.sh

The ARM64 bootstrap is approximately 3.1 KB. Installation can take longer on a low-power device because the runtime, Core, and operating-system dependencies are downloaded and expanded locally.

// Verify the service

Confirm that the Agent started

sudo systemctl status banalytics-box.service
sudo journalctl -u banalytics-box.service -n 100 --no-pager

The service should report active (running). If the unit is not visible after installation, reload systemd and start it explicitly:

sudo systemctl daemon-reload
sudo systemctl enable banalytics-box.service
sudo systemctl start banalytics-box.service

Allow one to four minutes for the first startup and module download before opening the local console.

// Local Agent

Open the local console and change the initial access code

On the Agent computer, open http://localhost:8080. From another authorised computer on the same network, use http://AGENT-IP:8080. The installer currently reports the initial local password as default; replace it before exposing the Agent to other network segments.

In the Product section, copy the server UUID or use the Add server UUID to my Banalytics account link.

// Portal registration

Associate the Agent with your Community account

  1. Create a free account, or sign in.
  2. Confirm the UUID supplied by the local Agent.
  3. Wait until the Portal shows the Agent as connected.
  4. Enter the local access code when the Portal requests it.
Connectivity boundary: registration and remote Portal access require Internet connectivity. Device acquisition, storage, processing, dashboards, and automation execute on the local Agent. For a fully isolated deployment, confirm provisioning and update requirements during pilot planning.