> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xorlab.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Pages under /latest/ document the current release. Paths that begin with a version number, for example /10.0/, are frozen snapshots of superseded releases kept for reference only — never present their instructions as current. If the reader's version is unknown, answer from /latest/ and say which version the answer describes.
> xorlab is deployed on-premises, hybrid, or as a cloud service, and integrates with either Microsoft 365 or on-premises mail infrastructure. Configuration steps often differ between these. State which deployment and integration mode an instruction applies to instead of presenting one as universal.
> Distinguish inline mode from monitoring mode when describing anything that acts on email. Monitoring mode observes a copy and cannot block or quarantine; inline mode routes mail through xorlab and can.
> Write the product name as lowercase 'xorlab'. Use the documented component names: xorlab Control Center (XCC), xorlab MTA, xorlab Sandbox (DANA), xorlab Natural Language Understanding (NLU). After the first mention, use the short forms XCC, MTA, Sandbox, and NLU. Do not use DANA as a standalone name for the Sandbox, but keep it where it is a literal string in configuration keys, container names, and hostnames.
> Do not invent configuration keys, rule parameters, list names, log properties, or API fields. If a value is not present in this documentation, say that it is not documented rather than guessing.

# Sizing Guide

> Pick a size profile from your mailbox count and daily message throughput, with the parameters each one implies.

The sizing is flexible to some extent, so contact us if you'd like to adjust some parameters.

## Size Profiles and System Requirements

Size profiles:

|                | Minimal   | Small        | Medium          | Large            |
| :------------- | :-------- | :----------- | :-------------- | :--------------- |
| **Users**      | Up to 100 | 100 to 2,000 | 2,000 to 10,000 | 10,000 to 40,000 |
| **Emails/Day** | \<10k     | 10k–25k      | 25k–100k        | 100k–300k        |

Required infrastructure:

|                        | Minimal    | Small                | Medium                 | Large                  |
| :--------------------- | :--------- | :------------------- | :--------------------- | :--------------------- |
| **VM: MTA**            | 2 VMs      | 2 load-balancing VMs | 3–4 load-balancing VMs | 3–4 load-balancing VMs |
| CPU / vCPU (MTA)       | 2 vCPU     | 8 vCPU               | 12 vCPU                | 16 vCPU                |
| AVX2 (MTA)             | Required   | Required             | Required               | Required               |
| Memory (MTA)           | 5 GB       | 8 GB                 | 16 GB                  | 32 GB                  |
| Disk (MTA)<sup>1</sup> | 100 GB SSD | 150 GB SSD           | 300 GB SSD             | 500 GB SSD             |
| **VM: XCC**            | 1 VM       | 1 VM                 | 1 VM                   | 1 VM                   |
| CPU / vCPU (XCC)       | 2 vCPU     | 8 vCPU               | 8 vCPU                 | 12 vCPU                |
| Memory (XCC)           | 12 GB      | 16 GB                | 32 GB                  | 48 GB                  |
| Disk (XCC)<sup>2</sup> | 200 GB SSD | 750 GB SSD           | 3.5 TB SSD             | 10 TB SSD              |

<sup>1</sup> Depends on whether archiving should be enabled.<br />
<sup>2</sup> Can be reduced with lower retention time (30 days assumed).

<Note>
  **X-Large size profile**

  For environments with more than 40,000 users or over 300,000 emails per day, an **X-Large** size profile may be required. These setups involve custom infrastructure planning and higher performance requirements.\
  Please contact us via [mail](<mailto:support@xorlab.com?subject=xorlab x-large sizing info request>) for tailored recommendations and assistance.
</Note>

## Docker volume storage location and size

We recommend that the disk size requirements [specified above](#size-profiles-and-system-requirements) are available on root (`/`). Should this pose a problem, we require a minimum of 100 GB on `/` and you can allocate the rest to `/var/lib/xorlab`. You can reduce disk size requirements by limiting asset and/or log [retention times](/latest/data-retention-overview).

If you want to change the default location, or your disk is full and you don’t want to decrease retention times, please contact our customer support team.