# Mission control

## Introduction

With **Versio.io Mission Control**, Versio.io supports its customers in the operation and maintenance of Versio.io Managed instances (on-premises). The use of this service is **optional** and can be deactivated in the Versio.io server settings.

## How it works

Versio.io Mission Control is activated by default after a new installation. The installed Versio.io server instance sends and receives data from Versio.io Mission Control. **Versio.io Mission Control does NOT send data to the Versio.io server instance.**

![Versio.io Mission Control architecture](<https://docs.versio.io/img/settings/mission-control/versio.io-mission-control.drawio.svg>)

*Figure: Versio.io Mission Control architecture*

The following table shows what data is sent to Versio.io Mission Control and for what reason:

| What data? | Why? |
| --- | --- |
| Installed versions of Versio.io components | Notification of Versio.io software updates and monitoring of support status |
| Server and environment identification IDs | Creation of environment-specific subscriptions |
| Health check info of the server (CPU and RAM usage), microservices and messaging queues | Proactive support for technical problems |
| Subscription usage of each environment | Optimising the scope of subscriptions, avoiding overuse and enabling billing |
| Requests for new user experience optimizations and product functionality as well as messages for malfunctions | Customer interaction |
