# Suggested Hardware Configurations

## Basic configuration (Development/QA environment)

### Web server and database installed on 1 server

* Quad-core processor
* 8 GB RAM
* SATA hard disk with 40 GB free

  **Note:** The amount of hard disk space required depends on the level of usage, especially if process file data (such as attachments) are stored in the database.
* Windows Server 2008 or 2012 (all versions)
* SQL Server 2008, 2012, or 2014 (all versions), or Oracle 10+

### Example of usage

* 500 potential users
* 50 requests/actions per day

## Recommended configuration

### Web server

* Quad-core processor
* 8 GB RAM
* High-speed hard drive array

  **Note:** The amount of hard disk space required depends on the level of usage, especially if process file data (such as attachments) are stored in the database. A minimum of 10 GB is recommended for WorkflowGen data.
* Windows Server 2008 or 2012 (all versions)
* SQL Server 2008, 2012, or 2014 (all versions) or Oracle 10+

### Example of usage

* 5000 potential end-users
* 500 requests/actions per day

## High availability configuration (web farm)

### 2 web servers in a web farm architecture

* Quad-core processor
* 8 GB RAM
* High-speed hard drive array or SAN

  **Note:** The amount of hard disk space required depends on the level of usage, especially if process file data (such as attachments) are stored in the database. A minimum of 10 GB is recommended for WorkflowGen data.
* Windows Server 2008, 2012, or 2014 (all versions)

### 2 database servers: 1 primary and 1 read-only replica

* Quad-core or more processor
* 8 GB RAM
* High-speed hard drive array (NAS/SAN or SSD)

  **Note:** The amount of hard disk space required depends on the level of usage, especially if process file data (such as attachments) are stored in the database. A minimum of 10 GB is recommended for WorkflowGen data.
* Gigabit Ethernet
* SQL Server 2008, 2012, or 2014 (all versions) or Oracle 10+

### NAS/SAN appliance

* High-speed hard drive array
* Gigabit Ethernet

### Example of usage

* 10,000 potential end-users
* 1000 requests/actions per day