# System Requirements

### Supported Operating Systems:

The recommended method to install Keeper Connection Manager is via the[ automated docker install](/keeper-connection-manager/installation/auto-docker-install.md). This removes any operating system, system pre-requisites and other requirements. If the underlying system supports a current version of Docker, the container is fully supported.

### Supported KCM Versions:

* Glyptodon 1.x - Full support for 2 years after any major release
* Glyptodon 2.x - Full support for 2 years after any major release
* Keeper Connection Manager 2.x - Full support for 2 years after any major release

### Minimum system specs for production deployment:

{% hint style="success" %}
The generalized formula for sizing Keeper Connection Manager is 1 CPU core and 2 GB of memory for every 25 concurrent users anticipated. We recommend a minimum of 8GB RAM and 2 cores for any small deployment.
{% endhint %}

#### Minimum host recommendations:

<table><thead><tr><th width="269"># Concurrent connections</th><th width="187">CPU</th><th width="187">Min. RAM</th></tr></thead><tbody><tr><td>0-25</td><td>2</td><td>8gb</td></tr><tr><td>26-50</td><td>3</td><td>12gb</td></tr><tr><td>51-100</td><td>4</td><td>16gb</td></tr><tr><td>101-200</td><td>8</td><td>32gb</td></tr><tr><td>200+</td><td>Contact us</td><td>Contact us</td></tr></tbody></table>

For anything over 200 concurrent sessions, we have several options, and it may be best to talk through this with our sales engineering team to find the right solution based on your needs and connection types.

### Disk space requirements

A single session recording can vary based on the content being shown. This is affected by the type of connection. GUIs typically have higher recording sizes versus CLI connections like SSH, which can be quite small.

{% hint style="info" %}
There are far too many variables in play to accurately predict disk space needs for recordings. The best practices are to monitor the recordings folder and offload them to another location as needed.
{% endhint %}

### Network throughput for concurrent connections

Network throughput also varies based on activity, type of session and connection settings. From actual examples, we've found that for a system running about 100 concurrent sessions, network traffic varies between 9Mbit/s and 15Mbit/s for all 100 connections. Each connection would be on average 1/100th of the 15Mbit value.

In the same above scenario with 100 connections, we would expect about 15gb total traffic per hour on the network adaptor. Comparing inbound and outbound traffic, just over 90% of the traffic is outbound from the server to the clients.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.keeper.io/keeper-connection-manager/installation/system-requirements.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.