# System Requirements

The following system requirements apply to both the core XRP Ledger server, `rippled`, and the Clio server for API access.

## Recommended Specifications

For reliable performance in production environments, it is recommended to run a server on bare metal with the following characteristics or better:

- Operating System: Ubuntu (LTS), Red Hat Enterprise Linux (latest release), or a compatible Linux distribution.
- CPU: 3+ GHz 64-bit x86_64 processor with 8+ cores.
- Disk: SSD / NVMe (10,000 IOPS sustained - not burst or peak - or better). Minimum 50 GB for the database partition. Do not use Amazon Elastic Block Store (AWS EBS) because its latency is too high to sync reliably.
- RAM: 64 GB.
- Network: Enterprise data center network with a gigabit network interface on the host.


For a validator in AWS, consider `z1d.2xlarge` with an extra 1 TB disk for logging and core dump storage.

## Minimum Specifications

These specifications are not enough to reliably [stay synced with Mainnet](/docs/infrastructure/troubleshooting/server-doesnt-sync). For production use, follow the recommended specifications above.

For testing purposes, you can run an XRP Ledger server on commodity hardware with the following minimum requirements:

- Operating System: macOS, Windows (64-bit), or most Linux distributions (Red Hat, Ubuntu, and Debian supported).
- CPU: 64-bit x86_64, 4+ cores.
  - For development purposes, it is also possible to compile `rippled` for some Apple Silicon or ARM processors. See the [Build instructions](https://github.com/XRPLF/rippled/blob/develop/BUILD.md) for guidance. However, architectures other than x86_64 are not officially supported and are not recommended for production.
- Disk: SSD / NVMe (10,000 IOPS sustained - not burst or peak - or better). Minimum 50 GB for the database partition. Do not use Amazon Elastic Block Store (AWS EBS) because its latency is too high to sync reliably.
- RAM: 16 GB+.


Amazon EC2's `i3.2xlarge` VM size may be appropriate depending on your workload. A fast network connection is preferable. Any increase in a server's client-handling load increases resources needs.

## System Time

A `rippled` server relies on maintaining the correct time. It is recommended that the system synchronize time using the Network Time Protocol (NTP) with daemons such as `ntpd` or `chrony`.

## See Also

- **Concepts:**
  - [The `rippled` Server](/docs/concepts/networks-and-servers)
  - [Consensus](/docs/concepts/consensus-protocol)
- **Tutorials:**
  - [Capacity Planning](/docs/infrastructure/installation/capacity-planning) - More information on the recommended specifications and planning for production needs
  - [Install `rippled`](/docs/infrastructure/installation)
  - [Troubleshoot rippled](/docs/infrastructure/troubleshooting)
- **References:**
  - [rippled API Reference](/docs/references/http-websocket-apis)
    - [`rippled` Commandline Usage](/docs/infrastructure/commandline-usage)
    - [server_info method](/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info)