# System Requirements and Ports Configuration
## **Overview**
This document outlines the system requirements and port configurations for deploying and operating **Autom Mate**, including **Autom Center** and [**Mate Agent**](https://docs.autommate.com/userguide/product-features/my-environment/mate-agent). These requirements are crucial to ensuring optimal performance, especially in data-intensive environments and scenarios with multiple automations (Automs). Additionally, this document provides a detailed breakdown of port configurations required for different deployment scenarios.
***
## Hardware Requirements
### **Autom Center**
For on-premises deployments, the following hardware specifications are required to ensure efficient operation:
| **Deployment Environment** | **Free Disk Space** | **RAM** | **Processor** |
| -------------------------- | ------------------- | ----------------- | --------------- |
| On-Premises | 250 GB | **16 GB or over** | 2.4GHz, 4 cores |
***
### **Mate Agent**
The Mate Agent requires the following hardware resources for on-premises deployments:
| **Deployment Environment** | **Free Disk Space** | **RAM** | **Processor** |
| -------------------------- | ------------------- | ----------------- | --------------- |
| On-Premises | 250 GB | **16 GB or over** | 2.4GHz, 4 cores |
{% hint style="warning" %}
#### **Note**
**While 16 GB of RAM is sufficient for standard operations, we recommend upgrading to 32 GB of RAM for data-heavy processing or if performance issues are encountered with 16 GB. Please refer to this document if any resource-related issues arise.**
{% endhint %}
***
## Supported Operating Systems
| Environment | Requirement |
| -------------------------------------- | ------------------------------------------------------ |
| Autom Center
| Windows Server 2012 or above |
| Mate Agent
| Windows 7 or above |
| Supported Browsers
| - Google Chrome
- Microsoft Edge
|
***
## Network and Ports
### **Usage Ports for Communication**
Below is a list of the ports required for communication and system functionality between **Mate Agent** and **Autom Center**:
5051 (TCP)
* **Mate Agent**: **Inbound** traffic allowed.
* **Autom Center**: **Outbound** traffic allowed.
443 (TCP)
* **Mate Agent**: **Outbound** traffic allowed.
* **Autom Center**: **Inbound** traffic allowed.
{% hint style="warning" %}
**Note: Outbound traffic is restricted on the server hosting the Mate Agent, except for ports 443 and 5051.**
{% endhint %}
***
## Ports Configuration Based on Deployment Scenarios
### **Cloud Deployment Ports**
In a **Cloud Deployment**, both **Autom Center** and **Mate Agent** are managed by Autom Mate’s Cloud services. Users are not required to configure any ports in this scenario.
***
### **Hybrid Deployment Ports**
A **Hybrid Deployment** means **Autom Center** is hosted in Autom Mate’s Cloud server, while **Mate Agent** is installed on the user’s on-premises infrastructure or personal cloud server.
**Mate Agent (On-Premises)**
5051 (TCP)
**Inbound** traffic should be allowed to enable communication between the Mate Agent and the Autom Center.
443 and (TCP)
**Outbound** traffic should be allowed for accessing Autom Center and other external services.
Users need to ensure that **Mate Agent** has the necessary port configurations to communicate with Autom Mate’s Cloud services.
{% hint style="info" %}
#### **Hint**
To ensure seamless OAuth authentication in hybrid and on-premises environments, make sure to include the **Autom Center wildcard .pem file** in the Mate Agent configuration. This step is essential if the Mate Agent and Autom Center operate on separate networks, preventing authentication errors.
{% endhint %}
{% hint style="danger" %}
#### **Warning**
If the **Autom Center wildcard .pem file** is not added to the Mate Agent configuration, OAuth authentication will fail when the Mate Agent and Autom Center are on different networks. Ensure this setup is complete to avoid service disruptions.
{% endhint %}
{% hint style="warning" %}
#### **Note**
OAuth authentication in hybrid or on-premises setups now requires importing the **Autom Center wildcard .pem file** into the Mate Agent. This update ensures compatibility and prevents errors in environments where the Mate Agent and Autom Center are not on the same network.
{% endhint %}
***
### **On-Premises Deployment Ports**
In an **On-Premises Deployment**, both **Autom Center** and **Mate Agent** are installed on the user’s infrastructure, either on-premises or in a personal cloud environment.
Autom Center and Mate Agent on the Same Server
When **Autom Center** and **Mate Agent** are installed on the same server, **no additional port configuration is required**, as all communication happens internally within the same machine.
Autom Center and Mate Agent on Different Servers
When **Autom Center** and **Mate Agent** are installed on separate servers, the following ports must be configured.
1. 5051 (TCP)
* **Autom Center**: **Outbound traffic** should be allowed to communicate with the Mate Agent.
* **Mate Agent**: **Inbound traffic** should be allowed to receive data from Autom Center.
2. 443 (TCP)
* **Autom Center**: **Inbound traffic** allowed.
* **Mate Agent**: **Outbound traffic** allowed.
By following these system and port configuration requirements, users can ensure smooth operation and optimal performance of **Autom Mate** in their chosen deployment environment. For Cloud deployments, no port changes are required. In Hybrid and On-Premises setups, it is essential to configure the correct inbound and outbound traffic on specific ports for effective communication between **Autom Center** and **Mate Agent**.