Community Edition onboarding

Install one Agent. Connect one real device.

This page keeps the complete free-start path in one place: create an account, choose the correct package, install the Agent, register it, and connect a first camera, Modbus device, or MQTT source.

Step 1 · Account and connectivity

Create the account used to register your free Agent.

Community Edition uses a free Banalytics Portal account to associate one Agent with you. Create the account now, or install the Agent first and return when the local console asks you to register its UUID.

What “local-first” means: installation, JDK and Core downloads, account creation, and Community Agent registration require Internet access. After setup, acquisition, storage, local processing, dashboards, and local device automation run on your Agent; raw sensing data does not have to be uploaded to the Portal. If the deployment must be fully isolated, confirm provisioning and update requirements as part of pilot planning.
Step 2 · Packages

Choose the package that matches the Agent computer.

Version 2.1.0 packages are small bootstrap archives. During installation they download the matching Banalytics Core and JDK 25 runtime, so keep the computer online until installation completes.

Why the installation scripts request elevated privileges

Windows: administrator rights are used for operating-system setup: checking or, with your approval, installing the required .NET Framework, stopping or registering the Banalytics Windows service, configuring its restart policy, and starting it.

Linux: root privileges are used to install operating-system packages, update the installing user's video and audio group membership, create required system links, write and enable the systemd service, and give that service access to detected video, audio, serial, USB, input, I2C, SPI, GPIO, and graphics devices. The generated service currently runs as root so it can reach this hardware.

Adapt it to your infrastructure: both installers are readable scripts that your administrator can review and modify before execution. You may preinstall approved dependencies, use a dedicated service account, narrow device and group permissions, change installation paths, or split the procedure into internally approved deployment steps. Validate the adapted script under your change-management and least-privilege policies, while retaining access only to the devices and network endpoints the Agent actually needs.

Steps 3–5 · Install and register

Continue from the archive to a registered local Agent.

03

Run the installer

Follow the Windows or Linux guide. The installer downloads and verifies JDK 25 and the selected Core, installs required dependencies, and registers the Agent as a service.

04

Open the local console

Open http://localhost:8080 on the Agent computer, or use that computer’s LAN address from another authorised device. Sign in with the initial password shown by the installer and change the local access PIN.

05

Register the Agent UUID

In the local Product section, use Add server UUID to my Banalytics account. Sign in to the Portal, confirm the UUID, then enter the local access code when requested.

Confirm both sides

The local service should be running and the Portal should show the Agent as connected. If either side is unavailable, use the platform installation guide before adding devices.