Requirements¶
Follow the link to learn about Hardware requirements before proceeding.
Software¶
ForensiQ requires the following software components:
Ubuntu Server LVM installation
Note that the Ubuntu Server installer uses Logical Volume Management (LVM) by default and, if enough disk space is available, allocates at most 100 GB of free space to the root logical volume.
-
Ubuntu 22.04, Ubuntu 24.04, Ubuntu 26.04 or Debian 12
-
Docker Engine
-
Docker container runtime
-
NVIDIA GPU driver version 580.95.05 or above
Only Nvidia GPUs of Turing architecture or newer are supported. Please check the Hardware Calculator for supported GPU models.
ForensiQ can be accessed via modern web browsers. The following are supported:
- Google Chrome
- Microsoft Edge
- Mozilla Firefox
Deployment setups¶
ForensiQ supports both standalone and distributed deployment setups.
-
In a Standalone setup, all core and indexing services run on a single server, which requires local NVIDIA GPU resources for video decoding and indexing.
-
In a Distributed setup, core and indexing services run on separate servers: a central Core node handles core services and web access, while one or more dedicated Indexer nodes equipped with NVIDIA GPUs decode and index video streams, store video data, and forward metadata to the core. This distributed architecture allows indexer nodes to scale horizontally.
Firewall settings¶
ForensiQ nodes communicate with each other and external clients over specific TCP ports. To ensure proper functionality of ForensiQ, make sure the following ports are open in your firewall settings:
The ports listed below are only for services listening on external interfaces.
| Port | Protocol | Description | Notes |
|---|---|---|---|
| 80 | TCP | HTTP access to the ForensiQ web interface | |
| 443 | TCP | HTTPS access to the ForensiQ web interface | |
| 29092 | TCP | Metadata broker communication. Indexer nodes connect to this port - If Primary indexer IP is set to the address of the standalone node, the relevant services will use this port. |
Traffic to this port is encrypted if internal encryption is enabled. |
| 54111 | TCP | Core nodes connect to this port if Primary indexer IP is set. |
Traffic to this port is encrypted if internal encryption is enabled. |
| 7177 | TCP | The Indexer (local) and the Core node connect to this port. | |
| 9092 | TCP | No external communcation, explicit localhost (127.0.0.1) connection. | |
| 9465 | TCP | On Standalone nodes, the monitoring proxy connects from the Docker network to the Video Storage metrics endpoint on the host. | Permit Docker-network-to-host traffic only. When internal encryption is enabled, mTLS is provided by the monitoring proxy on port 9464, not by this direct endpoint. |
| Port | Protocol | Description | Notes |
|---|---|---|---|
| 54111 | TCP | Core nodes connect to this port, if Primary indexer IP is set. |
Traffic to this port is encrypted if internal encryption is enabled. |
| 7177 | TCP | The Indexer (local) and the Core node connect to this port. | |
| 9092 | TCP | No external communication, explicit localhost (127.0.0.1) connection. | |
| 9464 | TCP | Core nodes connect to this port for monitoring purposes. | Traffic to this port is encrypted if internal encryption is enabled. |
| 9465 | TCP | The monitoring proxy connects from the Docker network to the Video Storage metrics endpoint on the host. | Permit Docker-network-to-host traffic only. When internal encryption is enabled, mTLS is provided by the monitoring proxy on port 9464, not by this direct endpoint. |