These architecture diagrams presents the idea behind the decentralized nature of the Stats Service API.

Scenario 1

Stats Service API interaction with MONARC

The Stats Service is installed on a dedicated server, gathering stats sent by the front office (FO). It can also return the aggregated stats to the MONARC backend (FO) for the dashboard of the MONARC users (with the CEO role).


The Stats Service only communicates with the backend of MONARC thanks to its API.

The stats collection (from the FO to the stats node) can be triggered with a cron job.

Scenario 2

Stats Service API interaction with MONARC

In the company A, the difference is that Stats Service API (stats) is installed on the same server where the MONARC back office is deployed. Not on on a dedicated server. The server hosting the back office of MONARC is a good choice.

Scenario 3

Stats Service API interaction with MONARC

stats collects data from the two MONARC front offices of the company B. These aggregated data can be used for the dashboard for the CEO role of MONARC client instances in this company. But also, in the future, for the MONARC back office.

Scenario 4

Stats Service API interaction with MONARC

Wendy is simply connected to a MONARC front office deployed in a local Virtual Box instance. Stats Service (stats) is running next to MONARC in this virtual machine.

Important notes


In all scenario, locally collected statistics (in stats node) can optionally be sent to which is a global instance. It’s the same software. You can configure the global dashboard statistics sharing option in the General Settings / Sharing statistics view of your MONARC instance (see here).

However, stats must always be collected in your local Stats Service instance. This is required for the proper functioning of the global dashboard of your MONARC instance.


It is as well possible to run your own alternative to And then you can configure the variable REMOTE_STATS_SERVER of your local Stats Service instance with the address of your “global” instance.

Organization level

Higher architecture level

A company has the possibility to push stats from selected clients with the same account on, for example, The service behind is operated by CASES Luxembourg and aims to provide relevant data about the current cybersecurity trends, focused in the Luxembourg area.

Integration with external services


A Stats Service instance is able to query MOSP.