> For the complete documentation index, see [llms.txt](https://docs.exavault.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exavault.com/installing-and-upgrading-the-appliance/system-requirements.md).

# System Requirements

ExaVault is delivered as a virtual appliance. You are responsible for providing the cloud or virtualization environment in which it runs.

ExaVault requires a 64-bit Intel processor. ARM environments, including AWS Graviton instances, are not supported.

The ExaVault appliance is tested and supported in these environments:

* VMware ESXi 5.x, 6.x, 7.x, and 8.x
* Microsoft Hyper-V
* Amazon Web Services (AWS)
* Microsoft Azure
* Linux KVM

Provision at least these resources:

* **CPU:** 4 cores at 2.4 GHz or greater
* **Memory:** 12 GB of memory (RAM)
* **Primary disk:** 100 GB
* **Data disk:** Size this disk for the workload. The appliance stores its data here; we recommend starting with at least 500 GB.

The minimum supported instance sizes on AWS are `c5n.xlarge`, `m6i.xlarge`, or `m7i.xlarge`.

You will also need a static (or rarely-changing) IP address because your installation's [license is associated with its IP address](/administration/license-keys.md#ip-address-changes). Frequent updates to the appliance's IP address will invalidate the license.

Workloads vary widely across our customer base, so sizing guidance beyond these minima is hard to give in the abstract. Monitor RAM and CPU usage and upscale the instance when either resource is constrained.