StifleR Server Considerations


The StifleR Server will have incoming and outgoing communications to all StifleR clients so this should be a major consideration when determining the location of the server. In a network with multiple geographical locations, it might be optimal to install multiple StifleR servers and place them in key hub locations. The StifleR server can be configured to query Configuration Manager deployment data so it might be useful to place them within close proximity.

The StifleR Dashboard is typically installed on the same server as the StifleR Server, but it can reside on any server hosting IIS.


The following table can be used as a summarized view of the hardware requirements for StifleR.


StifleR is CPU intensive. Since StifleR does not use that many threads, a higher frequency (Ghz) is recommended. We recommend at least a 2.4Ghz processor with 8 cores. Don’t forget that most CPU’s must also handle some of the network connectivity management.


StifleR writes a lot of historical data to databases, as well as maintaining in-RAM memory objects. Since each connection and all connection data is stored in RAM a decent allocation of RAM is recommended but 32GB should be plenty for most installations.


StifleR saves a lot of information to ESENT databases, especially with the System Resource Tracking features enabled. Fast SSD disks are preferred for housing these databases.

Network Connectivity

Each client initiates a non-managed SignalR client connection (web sockets) to the server, so if you want 100k clients to connect to a single server you need to beef up the network connectivity.

If you are supporting a large number of clients, you probably want dual or quad 10Gb/s NIC’s for your StifleR server. This will ensure that the NIC’s have enough power to manage the large number of connections.


StifleR server requires Windows Server 2019 (or above) with Microsoft .NET version 4.8 or higher.

There are also requirements around IIS settings. Please refer to the Dashboard installation section for more information.


Multiple StifleR servers can be configured for larger enterprises so that clients can fail-over to a second server should the primary server become unavailable.

Large Enterprise Considerations

For larger installations we recommend splitting the load across several StifleR servers. For example one server per geographical region.

Last updated