# Requirements

These requirements are for all operating systems.

* [Software/Hardware requirements](#software-hardware-requirements)
* [Network requirements/domain name](#networking-requirements)
* [Security](/mailscheduler/getting-started/requirements/security.md)
* [Database credentials](#database-credentials)
* [SSL Certificate](#ssl-certificates)
* [License](#license-requirement)
* [Installation files](#installation-files)

Each operating system can have different requirements:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Windows requirements</td><td><a href="/pages/QaCrKwwh778Hy0MaPU4o">/pages/QaCrKwwh778Hy0MaPU4o</a></td></tr><tr><td>Linux requirements</td><td><a href="/pages/9fuaj694niVqLExiX6ln">/pages/9fuaj694niVqLExiX6ln</a></td></tr></tbody></table>

### **Software/Hardware Requirements**

* Minimum hardware requirements:&#x20;
  * 4 (v)CPU, processing power
  * 8Gb RAM
  * 50Gb application disk space
  * 100Mbps or 1Gbps network-interface
* Temporary Internet Access for downloading missing component

### Network requirements

Firewall rules allow access to the port where the application will run. This applies to both internal and external networks, as well as server firewalls.

Ensure a valid web domain is available for the MailScheduler application to serve and distribute its content. When selecting a domain, it's important to consider how the application will be made available:

* Only within the internal/company network. This could be the machine/server name. The network DNS server will handle the request internally.
* Customers/users can use the MailScheduler application outside of the network. A web domain, for example, `<https://extension.company.com>` (create a DNS entry) which points to the host of MailScheduler.
* Ensure the server is accessible solely via a VPN or within the company's internal network.
* Read the security page and make sure you are compliant: [here](/mailscheduler/getting-started/requirements/security.md)

{% hint style="info" %}
When using a network/internal domain, the traffic of MailScheduler is available exclusively within the network (e.g., via VPN). Users outside the network cannot access the MailScheduler application.
{% endhint %}

### **Database Credentials**

Access to a running database is required. Supported databases include:

* SQL Server, minimal version 2019 or newer
* MySQL, min. version 5.7 or higher
* PostgreSQL
* SQLite

### **SSL Certificates**

SSL Certificates are optional unless you're not running the system behind a proxy/load-balancer.

We support the following SSL certificates:

* Using a `.key` and `.cer` certificate via the public keys method.
* Using a `.pfx` Windows-style certificate.

### **License Requirement**

A valid License for MailScheduler. The license can be found in our [portal](https://my-appsfortableau.infotopics.com/login).

### **Installation files**

One-Click Executable files for easy installation. These files can be downloaded via our [portal](https://my-appsfortableau.infotopics.com/login).

<table data-card-size="large" data-view="cards" data-full-width="true"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Next</strong></td><td>Getting started</td><td><a href="/pages/rz0WErYyMN93oVwurMeR">/pages/rz0WErYyMN93oVwurMeR</a></td></tr></tbody></table>


---

# 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.infotopics.com/mailscheduler/getting-started/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.