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

# Requirements

## General Requirements

Your Curator server must be its own standalone web server. Installing on the same web server as Tableau Server is
**not** supported.

Containerized deployments are also **not** currently supported.

Your Curator server will need to be able to communicate directly with your Tableau Server, and your
Tableau Server will need the REST and Metadata APIs enabled.

<u>Curator Standard/Enterprise</u>

If you are hosting, you will need a standalone web server on which to install the software. By
choosing to self-host, you are also accepting responsibility for:

* Ensuring a robust backup routine beyond Curator's built-in full backup functionality.
* Performing server upgrades and maintenance for security patches, etc.
* Applying and maintaining SSL/TLS certificates, DNS, and firewall protections.

This can be highly customized, but plan on following minimum specifications:

* Linux (preferred) or Windows
* At least 4 CPU, 8GB of RAM and 20GB of disk space available
* Ports open for web traffic (80 and 443)
* A disaster recovery plan

For AWS-hosted instances, we recommend:

| Linux (preferred)                    | Windows                              |
| :----------------------------------- | :----------------------------------- |
| t4g.large                            | t3a.xlarge                           |
| Ubuntu 24.04 LTS or newer            | Windows 2019 or above                |
| 20GB of gp3 SSD @ 3000 IOPS/125 MB/s | 20GB of gp3 SSD @ 3000 IOPS/125 MB/s |

## High Availability (Multiple Instances)

<u>Curator Standard/Enterprise</u>

Curator supports running multiple application instances behind a load balancer in a high availability (HA)
topology. In this setup, two or more application nodes share a single database and filesystem, allowing traffic
to be distributed across nodes for better uptime and increased concurrent user capacity.

Running multiple Curator instances on the **same single server** is **not** supported. Each Curator instance must
run on its own dedicated server (or virtual machine) that meets the standard server requirements listed above.

For full details on supported HA topologies, infrastructure components, and setup instructions, see the
[High Availability](/setup/high_availability/high_availability) guide.