Watcher installation ways
Flussonic Watcher is available in two editions:
Single is an easy to install and operate version requiring minimal configuration and allowing quick deploy but having a number of functional limitations. You can use this edition to get familiar with the product or to build a video surveillance system at small to medium sized secured facility.
Cluster is an advanced version providing much more features and requiring more resources, a bit more sophisticated in installation and maintenance. You can use it to deploy a VSaaS service for your subscribers or to build a video surveillance system at a large-scale facility.
You can upgrade Single to Cluster any time without loosing your settings or data. Please contact Flussonic technical support service for that.
Comparing Watcher editions
|Number of cameras||Only limited by hardware resources||Up to 500|
|Number of servers||Not limited||Up to 1|
|Branding (changing the logo, color and text)||✅||❌|
In Single mode, all cameras are connected to a single server where Flussonic Watcher, Flussonic Media Server and the database are installed, the web interface works, streams are ingested, and the archive is written.
The scheme below represents the Single mode principle of operation. The arrows show video streams.
In Cluster mode, the servers are dedicated as follows:
One managing server (endpoint). It has the web interface to Watcher, Flussonic Media Server, the business logic, and the PostgreSQL database engine. Watcher is installed on the managing server only.
Unlimited streaming servers (streamers) controlled by the managing server. Only Flussonic Media Server is installed on streamers. Streamers store DVR archive and handle camera streams.
All servers must have public IP addresses and the same cluster key (which is specified in Watcher settings). In addition, the host name of the management server must resolve to the IP address.
The following scheme shows general principle of Cluster operation. Solid arrows indicate video streams, and dashed arrows indicate data streams (for example, configuration parameters, status information, etc.)