> For the complete documentation index, see [llms.txt](https://docs.monolithforensics.com/monolith/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monolithforensics.com/monolith/deployment-and-security/on-premises-deployments/requirements.md).

# Requirements

Review the Docker, hardware, email, and optional storage requirements for deploying Monolith on-premises.

Before deploying Monolith on-premises, review the infrastructure and supporting services required for your environment.

The exact deployment may vary depending on how your organization plans to host Monolith, provide user access, store files, and integrate with internal systems.

### Docker

Docker or Docker Desktop is required for a standard Monolith on-premises deployment.

Install Docker on the system that will host the Monolith containers before beginning the deployment process.

Follow the existing Docker installation link for installation guidance.

### Hardware

The following minimum hardware is required to run the Monolith application backend within Docker:

* **Operating System:** Ubuntu Server 20, 22, or 24
* **Memory:** 4 GB RAM
* **CPU:** 2 cores
* **Storage:** At least 100 GB

More than **500 GB of storage is recommended** for environments that expect to retain a larger amount of Monolith data or uploaded files locally.

Storage requirements may increase substantially depending on how your organization plans to use Monolith and where uploaded files will be stored.

### SMTP for Email

To use Monolith email functionality, your organization must provide access to an SMTP service.

Required SMTP information includes:

* SMTP host
* SMTP port
* SMTP user
* SMTP password

These values are supplied to the Monolith application container at runtime.

SMTP configuration supports features that send email from Monolith, such as account, notification, and other supported email workflows.

### Amazon AWS S3 Integration

Organizations that want to store Monolith files in Amazon S3 can configure S3 as part of the on-premises deployment.

Required information includes:

* AWS Access Key
* AWS Secret Key
* AWS Region
* AWS Endpoint

S3 integration is optional and depends on how your organization plans to store Monolith files.

Organizations may instead use other supported storage configurations documented in the on-premises deployment section.

### Before Deployment

Before continuing, confirm that your technical team has determined:

* Where the Monolith containers will run
* How much storage should be allocated
* Whether Monolith email functionality will be enabled
* Where uploaded Monolith files will be stored
* Whether AWS S3 or another supported storage option will be used
* How users will connect to the Monolith environment

After confirming these requirements, continue to [**Monolith Containers (Docker)**](/monolith/deployment-and-security/on-premises-deployments/monolith-containers-docker.md) for information about the application components used in the deployment.

### Related Documentation

* [**On-Premises Deployments**](/monolith/deployment-and-security/on-premises-deployments.md)
* [**Monolith Containers (Docker)**](/monolith/deployment-and-security/on-premises-deployments/monolith-containers-docker.md)
* [**Deployment**](/monolith/deployment-and-security/on-premises-deployments/deployment.md)
* [**Monolith Data**](/monolith/deployment-and-security/on-premises-deployments/monolith-data.md)
* [**Connecting to File Shares**](/monolith/deployment-and-security/on-premises-deployments/connecting-to-file-shares.md)
* [**Using External MySQL Database**](/monolith/deployment-and-security/on-premises-deployments/using-external-mysql-database.md)