ControlUp Architecture - On-Premises

The following diagram is a high-level overview of ControlUp architecture in On-Premises mode:

For more details, see:

• ControlUp Components
• Connection Types

On-Premises backend components

ControlUp On-Premises Server

The ControlUp On-Premises (COP) Server is powered by a Windows Server which is designed to provide the functionality of the ControlUp Cloud Server within your network. After configuring the COP Server, all ControlUp Consoles and Monitor service instances running in your network will connect to the COP Server which provides login, licensing, central configuration, and database services for the Consoles and Monitors services.

The COP server is designed primarily for environments where internet connection is limited or blocked, or where regulation doesn't permit organizational data to be stored outside the company’s network.

The COP Server requires the following software components:

1. Windows Server 2016 or higher.
2. .NET Framework 4.8.
3. Lightweight Directory Services.
4. IIS services.
5. ControlUp Web Services hosted on IIS.
6. MS SQL database: 2019, 2017, 2016, 2014. These can be Express, Standard, and Enterprise editions.

During the initial login phase, ControlUp Consoles and Monitor services instances authenticate themselves against the COP Server using either the user’s account token or an explicitly provided AD username and password.

The authentication protocol between the console/monitor instances and the COP Server is based on Windows Authentication (HTTP 401 Challenge) over HTTPS.

ControlUp Insights On-Premises Server

The ControlUp Insights On-Premises (IOP) Server is a query database server that runs on your network, facilitating the use of ControlUp IOP for analytics and reporting. The server is an internal data collector which processes and creates data models to allow advanced reporting and analytics capabilities, without any external network connection.

ControlUp In-RAM Database

A proprietary database is used by each ControlUp Console/Monitor service instance to store all real-time performance and configuration data gathered by the data collection agents. This database is volatile, which exists only when the console/monitor executable is running. The Security Policy in the console allows for proper role-based maintenance of its various features. The in-RAM data retention policy allows up to 100 historical transactions per counter.

ControlUp Configuration Database

The ControlUp central configuration is hosted on a Lightweight Directory Services database.

The configuration database for a COP deployment is stored on the COP Server running inside the customer network.

For more details on the configuration database, see ControlUp Architecture & Security Concepts > Configuration Database.

ControlUp Incidents Database

Incidents in ControlUp are stored in the SQL database that you need to deploy.
For details on the Incidents Database, see ControlUp Architecture & Security Concepts > Incidents Database.