Skip to content

Hardware requirements

Watcher resource requirements depend on role distribution and actual load. This page describes system components and server preparation requirements. Calculate archive capacity and performance separately; a fixed camera count is not a guarantee for every configuration.

The package recipe for installing 26.11 is provided for Ubuntu 24.04 LTS x86-64. Before choosing another OS, check availability of all dependencies and run a trial installation of the same package set.

Single mode

Management and the media layer run on one server. The flussonic-watcher=26.11 package installs watcher-vms=26.11 and watcher-streamer=26.11 and requires PostgreSQL 14 or later, Redis and Central 26.10 or later.

The total resource budget includes:

  • Management — API, web processes and background jobs.
  • Application data — PostgreSQL, Redis and Central.
  • Video — stream ingest, viewer delivery, archive recording and reading.
  • Additional processing — analytics and video conversion, if enabled.

Separate system data and video archive storage by purpose. Prepare mount points and write permissions before enabling the archive. Calculate storage size from bitrate and retention depth.

Cluster mode

The management server can be installed as watcher-standalone. In this configuration Angie serves HTTP(S), and the package does not install a local media layer. At least one separate streamer is needed for video.

The management server needs memory and disk performance for the database, episodes and background jobs. Watcher process count depends on CPU and memory; reducing process count when RAM is insufficient does not make every small machine suitable for the workload.

For streamers, consider separately:

  • Incoming network — all camera streams in use.
  • Outgoing network — simultaneous views, exports and inter-server transfers.
  • Disks — simultaneous archive writing, reading and cleanup.
  • Computing — processing selected codecs and additional features.
  • Reserve — the camera load from another server on failure.

The streamer Channel limit and Total bandwidth limit parameters participate in camera placement. They must reflect measured server limits. Setting a high limit does not add server resources.

Network and time

Required ports depend on the protocols used. The web interface and HTTP(S) video need access to configured HTTP(S) listeners. RTSP, Agent connections and other transmission methods require their own listeners and network rules. Do not expose all service ports externally based on a single general list.

Provide DNS resolution and time synchronization. The database and Redis must not be accessible to viewers. Check routes from the streamer to the camera and from the client to the public video delivery address.

Watcher mobile app

For Watcher Android 26.10.01 the technical minimum is Android 9; for iOS 26.10.02 it is iOS 15. Check compatibility of the specific package in its App Store or Google Play listing and on the target devices. The server version does not determine the mobile app's minimum OS version.

Besides sign-in, check live video, archive and notifications. Decoding support for the selected codec depends on the device and app. Check server access from the network where the user will work.

Browser requirements

Use a supported current browser version and check the selected cameras on the working devices. The video player requires codec support and connectivity over the playback protocol in use; opening the interface successfully does not establish these.

For an HTTPS interface, configure HTTPS video delivery with a valid certificate. Check live video, archive, mosaic operation and file downloads with the required permissions. Check H.265 support on the specific browser and device combination.