UiPath Documentation
orchestrator
2024.10
false
UiPath logo, featuring letters U and I in white

Orchestrator installation guide

Last updated Mar 24, 2026

Hardware Requirements

There are multiple enterprise cloud deployment options available to host your Orchestrator, such as Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform (GCP). Depending on your deployment option of choice and the size of the environment you plan to build, you need to consult different hardware requirements.

This chapter provides insight into the hardware requirements specific to some of these scenarios.

Small to Medium Deployments​

The hardware requirements differ from your development environment to the production environment. While the same hardware requirements as your production environment could be utilized for testing and development purposes, that implies higher and unnecessary costs, especially in large-scale deployments.

Development Environments​

These requirements assume a maximum of 100 Unattended robots running simultaneously. Two machines can be used, one for Orchestrator and (optionally) Elasticsearch, and one for SQL Server, configured as follows:

Web Application Server​
CPU Cores (>2GHz)RAM (GB)HDD (GB)
44150
SQL Server​
CPU Cores (>2GHz)RAM (GB)HDD (GB)
48300

Production Environments​

For production environments, it is highly recommended to provide one dedicated server for each role:

  • Orchestrator web application.
  • SQL Server Database Engine.
  • Elasticsearch and Kibana.

For a Multi-Node Installation, in addition to the above, the following is also required:

  • for Orchestrator (3+ HAA nodes are required for true high availability and 6+ HAA nodes for geo-redundancy.

    Note:

    Multi-node Orchestrator deployments use the RESP (REdis Serialization Protocol) for communication, and thus can be configured using any solution relying on this protocol.

    HAA is the only such solution supported by UiPath.

The hardware configuration for each required server depends upon the size of your deployment, as detailed below. The hardware requirements presented here were made based on tests where a Robot was defined as follows:

  • messages are sent from the Robot to Orchestrator with a frequency of 1 message per second
  • within 60 seconds, the Robot sends:
    • 15 message logs
    • 2 heartbeats
    • 6 get asset requests
    • 6 add queue item requests
    • 6 get queue item requests
Support up to 250 Unattended Robots​
Web Application Server​
Number of RobotsCPU Cores (min 2 GHz)RAM (GB)HDD (GB)
<2044100
<5044100
<10044150
<20044200
<25044200
Note:

For more than 200 Robots, increase to 500 the number of connections allowed in the pool of the SQL connection string from the UiPath.Orchestrator.dll.config file. To do this, add the Max Pool Size=500 parameter to the connection string, so that it looks similar to this example: &lt;add name="Default" providerName="System.Data.SqlClient" connectionString="Server=SQL4142;Integrated Security=True;Database=UiPath;Max Pool Size=500;" /&gt;

SQL Server​
Number of RobotsCPU Cores (min 2 GHz)RAM (GB)HDD (GB)
<2048100
<5048200
<10048300
<20088SSD 400
<250816SSD 400

Disc space requirements highly depend on:

  • Whether work queues are used or not. If work queues are used, it depends on average number of transactions added daily/weekly and size (number of fields, size of each field) of each transaction.
  • The retention period for successfully processed queue items (the customer should implement their own retention policy).
  • Whether messages logged by the Robots are stored or not in the database. If they are stored, a filter can be applied to only store in the DB specific levels of messages (for example, store in the DB the messages with log level Error and Critical, and store in Elasticsearch messages with log level Info,Warn and Trace).
  • Frequency of logging messages - the Robot developer uses the Log Message activity at will, whenever they consider a message is worth to be logged.
  • The retention period for old logged messages (the customer should implement their own retention policy).
  • Logging level value set up in the Robot. For example, if logging level in the robot is set to Info, only messages with levels Info,Warn,Error and Critical are sent to Orchestrator; messages with levels Debug,Trace and Verbose are ignored, they will not reach Orchestrator.
Elasticsearch Server​
Number of RobotsCPU Cores (min 2 GHz)RAM (GB)HDD (GB)
<2044100
<5044100
<10048150
<200412200
<250412300

Disc space requirements depend on:

  • The retention period (the customer should implement their own retention policy).
  • Frequency of logging messages - the Robot developer uses the Log Message activity at will, whenever they consider a message is worth to be logged.
  • Logging level value set up in the Robot. For example, if logging level in the Robot is set to Info, only messages with levels Info,Warn, “Error” and “Critical” are sent to Orchestrator; messages with levels “Debug”, “Trace” and “Verbose” are ignored, they will not reach Orchestrator.
    Note:

    For more than 50 Robots you need to instruct the Java Virtual Machine used by Elasticsearch to use 50% of the available RAM, by setting both the -Xms and -Xmx arguments to half of the total amount of memory. This is done either through the ES_JAVA_OPTS environment variable or by editing the jvm.options file.

Support Between 250 and 500 Unattended Robots​
Web Application Server​
Number of RobotsCPU Cores (min 2 GHz)RAM (GB)HDD (GB)
<30088200
<40088220
<5001616250
SQL Server​
Number of RobotsCPU Cores (min 2 GHz)RAM (GB)HDD (GB)
<3001632SSD 400
<4001632SSD 500
<5001632SSD 600
Note:

For SQL Server Standard Edition, 16 CPU cores is the maximum that the Standard edition will use. For a virtual machine, please ensure that this number of cores is obtained as 4 virtual sockets with 4 cores each (and not as 2 sockets with 8 cores or 8 sockets with 2 cores). For Enterprise edition, it does not matter what is the combination to obtain 16 cores.

For more than 300 Robots, please consider not storing all logged messages in the SQL Server database. Store in the DB only the messages with log level Error and Critical. Store all messages (including Error and Critical) in Elasticsearch.

Elasticsearch Server​
Number of RobotsCPU Cores (min 2 GHz)RAM (GB)HDD (GB)
<300412300
<400416500
<500416600

Large Deployments​

IaaS Attended Deployments​

The following section is an example of a large, scalable deployment using the Azure Infrastructure as a Service (IaaS) offerings. This configuration was used:

Architecture​
Note:

The architecture examples below contain optional and/or differing components (e.g. CyberArk, UiPath High Availability Add-on).

The Jumpbox depicted is not required but is a recommended best practice for your production environments, providing isolation and security.

Figure 1. Single-Node Architecture

Single-node architecture diagram

Figure 2. Multi-Node Architecture

Multi-node architecture diagram

Hardware Requirements​

This section describes the hardware configurations used for the performance testing listed in Scaling Your Deployment, below.

Orchestrator Nodes​

Each Orchestrator node must be configured as follows:

VCPUsRAM (GB)SSD (GB)
1632128
SQL Server​

The SQL Server virtual machine specifications must scale in line with the number of Orchestrator nodes:

Orchestrator NodesVCPUsRAM (GB)Disk
1 - 28161TB - ultra SSD disk for database, tempDB, and transactional log
516321TB - ultra SSD disk for database 1TB - ultra SSD disk for tempDB 1TB - ultra SSD disk for transactional log
1032641TB - ultra SSD disk for database 1TB - ultra SSD disk for tempDB 1TB - ultra SSD disk for transactional log
1540961TB - ultra SSD disk for database 1TB - ultra SSD disk for tempDB 1TB - ultra SSD disk for transactional log
Elasticsearch Availability Set​

The Elasticsearch availability set is comprised of 3 master nodes and 6 data nodes, for a total of 9 nodes, each with the following specifications:

VCPUsRAM (GB)OS SSD (GB)Data SSD (TB)
816128 (with 5000 IOPS and 100 MB/s Throughput)1 (with 5000 IOPS and 200 MB/s Throughput)
Software Requirements​

The versions listed above are those used for the deployments and performance tested loads described.

Load Balancing​

For multi-node deployments, it is recommended to use two Azure Standard load balancers:

  • One for the Orchestrator servers;
  • One for the Elasticsearch servers.
High Availability Add-on​
Scaling Your Deployment​

The number of nodes needed in your Orchestrator scale set depends on the number of Robots being deployed:

Orchestrator Scale Set NodesNo. of Robots
1up to 6,000
2up to 14,000
5up to 80,000
10up to 200,000
15up to 300,000

These deployments were tested using the hardware and software configurations above to exhibit no performance loss under the specified load below.

Performance Testing​

The data displayed in the following 2 tables is representative of an attended deployment.

Static Data

Static Data refers to the initial Orchestrator load.

EntityOne NodeTwo NodesFive NodesTen NodesFifteen Nodes
Tenants11111
Folders12446
Robots6,00014,00080,000200,000300,000
Packages8,00016,00048,00048,00048,000
Processes4,0008,00024,00024,00024,000
Queues6001,2001,8002,4003,000
Queue Items1,120,0001,500,0003,000,0005,000,0007,000,000
Assets5001,0001,5003,0004,500

Dynamic Data

Dynamic data refers to the data added to or changed in Orchestrator as processes are executed.

EntityOne NodeTwo NodesFive NodesTen NodesFifteen Nodes
Queue Items (per day)300,000600,0004,000,0009,000,00010,500,000
Jobs (per minute)7001,5003,0006,0007,500
Logs (per minute)20,00050,000300,000600,000800,000
Nuget Downloads (Maximum per minute)1,0003,00010,00014,00018,000
Robots Connected (Maximum)6,00014,00080,000200,000300,000
Heartbeat (per minute)12,00028,000160,000400,000600,000
Busy Robots3,0007,00040,000100,000150,000
Available Robots3,0007,00040,000100,000150,000

PaaS Attended Deployments​

The following sections offer an insight into the capabilities of a PaaS deployment in terms of performance.

Architecture​

The following prerequisites are needed:

  • Orchestrator:
    • Orchestrator App Service Plan: 20 P3V2 instances
    • Azure SQL Server: Premium P15: 4000 DTUs
    • Azure Redis cache P2 Premium 13GB
  • Identity Server:
    • Identity Server App Service Plan: 2 instances P3V2
    • Azure SQL Server: Standard S7: 800 DTU
  • Elasticsearch:
Performance Testing​

The data displayed in the following tables is representative of an attended deployment.

Static Data​

Static Data refers to the initial Orchestrator load.

EntityOne Node
Tenants1
Folders8,000
Robots80,000
Packages8,000
Processes8,000
Queues8,000
Queue Items2,000,000
Assets8,000
Dynamic Data​

Dynamic data refers to the data added to or changed in Orchestrator as processes are executed.

EntityOne Node
Queue Items (per day)5,000,000
Jobs (per minute)2,600
Logs (per minute)240,000
Nuget Downloads (Maximum per minute)2,000
Robots Connected (Maximum)80,000
Heartbeat (per minute)160,000
Busy Robots40,000
Available Robots40,000

TCP Ports​

PortDescription
443Default port for communication between Users and Orchestrator with the connected Robots.
1433Default port for communication between Orchestrator and the SQL Server machine.
9200Communication between Orchestrator and Elasticsearch.
9300Communication between Elasticsearch nodes, if applicable.
5601Default port used by the Kibana plugin, if applicable.
3389Required for RDP automation, needed for High-Density Robots.

You can also check out hardware requirements for Studio and Robot.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated