System Configuration Suggestions for Leapwork
System Configuration Suggestions for Leapwork
Leapwork's SME and Enterprise Editions each come with their own suggested system configurations for the Agent and Controller/server. This page will give you details of both:
Note: Permission for installing Leapwork (Studio, Controller, or Agent)
You must have full administrative access to the Windows computer you wish to install or upgrade Leapwork on. Full administrative privileges are essential because installation requires access to the Windows registry and Windows System folders.
If you are trying to install software on a computer in a corporate or networked Windows environment but do not have the necessary privileges, you will need to contact your system administrator to install the software for you. These rights are not required to run Leapwork once it is properly installed.
SME Edition
All three components of the Leapwork SME Edition can be installed on the following versions of Windows:
| Operating System Supported | Windows 10, Windows 11, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, and Windows Server 2022. |
Note: Windows core operating systems are not supported.
Note: .
- versions prior to 2025.2 use .NET 4.8 ( https://dotnet.microsoft.com/en-us/download/dotnet-framework/thank-you/net48-web-installer)
- versions from 2025.2 onward use .NET 6 ( https://dotnet.microsoft.com/en-us/download/dotnet/6.0)
- versions from 2025.3.0 onward use .NET 8, bundled with Leapwork Studio. ( https://dotnet.microsoft.com/en-us/download/dotnet/8.0)
Typically, the Studio and Agents are installed on desktop versions, whilst the Controller is installed on a Windows server. Some operating system does not work remotely due to technology challenges. Please check the following requirements for remote servers and operating systems. Similarly, click here to read about the Prerequisite for using Windows Credential for auto-login.
The studio should be installed on the user’s workstation; hence its configuration remains the same for SME and Enterprise editions. The studio is comparable to a normal Office installation, so, in most cases, no special configuration is required.
The recommended hardware configuration for the Studio is:
- 8 GB RAM as a minimum; 16 GB and more is recommended.
- At minimum, an Intel i5 processor is required.
- SSD-based internal storage. 100 GB to begin with.
- A wired internet connection.
Controller
The Controller is the central hub in the Leapwork system and needs to be configured to accommodate the workload. The workload depends on various factors. These include:
- The number of automation flows.
- The complexity and duration of automation flows.
- The frequency of automation flow execution.
- Retention settings/policy for saving the video outputs.
The recommendation is to start with a standard server configuration and monitor the Controller machine's memory usage, I/O activity, CPU usage, etc. The user can then down/upgrade the machine as required. A standard server configuration (minimum) could be:
- 16 GB RAM ( For optimal performance and scalability, 32 GB of RAM is recommended)
- 6-12 Cores
- Flexible and fast disk system (SSD, SAN, or similar; 500 GB to start).
The Controller can run on both physical and virtual servers.
Note: If the user wants to install all components on one machine, the following hardware configuration is required:
- Minimum 32 GB RAM ( For optimal performance and scalability, 64 GB is preferred).
- 6–12 Cores.
- 500 GB SSD
Agent
The Agent is used for executing automation flows. While deploying the Agent in the Data Center, it may not be possible to obtain a Windows desktop version. Therefore, the Agent will also run on a Windows Server with Desktop Experience enabled. The Server is installed on a Windows server. Here is how to choose the configuration for the Agent machine:
- Simulating applications for an end-user:
- In this case, the machine should be as similar as possible to the end-users machine. This will increase the reliability of the automation flows. However, we recommend that the CPU has at least two cores.
- The recommended hardware configuration, in this case, would be:
- 8 GB RAM as a minimum; 16 GB is recommended
- Intel i5 CPU in a physical machine. In the case of a virtual machine CPU, there should be at least two cores
- SSD-based internal storage
- Running automation flows in parallel:
- In the case of executing web automation flows, it is possible to set up an Environment that points to a Selenium Grid. Selenium Grid allows multiple browsers to run web automation flows in parallel on the same machine. The more powerful the machine, the more browsers can run in parallel.
- In this case, a recommended hardware configuration (assuming 4 parallel browser executions) would be as follows:
- 16 GB RAM
- 4-8 cores
- Flexible and fast disk system (SSD, SAN, or similar. 100 GB to start with)
Enterprise Edition
For the Enterprise Edition, please be aware that infrastructure configurations vary widely from company to company and may impact system requirements. For example, the performance of Leapwork’s software can be significantly impacted by high-latency or low-throughput network conditions, virtual server configurations with noisy neighbors, degraded SAN disk performance at write time, and many other factors.
For this reason, we suggest an agile approach in which one or more environments are initially set up in real-life conditions and adjusted as usage is increased during the first 90 days of operation.
Additionally, permission & roles required to install Leapwork on a windows computer can be found here. In general, remember
- Hardware requirements for Agents are also dependent on the application(s) under test, particularly RAM and CPU. You may find that dimensioning of the Agent is actually driven by this instead.
- The more disk space you have, the more data you can store – the alternative is harsh retention policies.
- The more CPU cores you have, the faster processing and parallelization will work.
- Use high-speed SSDs for data storage with high write or read patterns, and combine them with extra RAM.
The following table shows the suggested operating system and SQL server versions supported for the Enterprise Edition:
| Operating System Supported | MS SQL Supported |
|---|---|
| Windows 10, Windows 11, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, and Windows Server 2022. | MS SQL (version 13), 2017 (version 14), 2019 (version 15), 2022 (version 16). Azure SQL is also supported. MS SQL Edition Supported - SQL Enterprise (Recommended), SQL Standard. |
Windows core operating systems are not supported
The following table shows the suggested hardware configurations for Leapwork's Enterprise Edition Servers, Agents, and MS SQL Server database:
| Installation scenario | Leapwork Server | Leapwork Agent | MS SQL Server |
|---|---|---|---|
| Multiple teams, medium usage - 25 users, 500 flows, 10 agents, 2 runs per day - 500 \* 10 \* 2 = 10,000 flows run per day - 500 keyframes per-flow run, 100 bytes per keyframe = 10,000 \* 500 \* 100 = 500 MB new run data per day |
- 16 GB RAM - 64-bit, 4-8 cores - 500 GB regular drives - Virtual machines are recommended for most scenarios - avoid noisy neighbors Note: In some cases, based on your specific usage requirements and database size, you may need to upgrade to a 6 -12 core processor to ensure optimal performance and system stability. |
- 4-16 GB RAM - 64-bit, 2-4 cores - 100 GB regular drive - Virtual machines are recommended for most scenarios - avoid noisy neighbors |
- 16 GB RAM - 64-bit, 4-8 cores - 1 TB regular drives - Shared MS SQL Server instance recommended - avoid noisy neighbors |
| Multiple teams, high usage - 25 users, 500 flows, 25 agents, 10 runs per day - 500 \* 25 \* 10 = 125,000 flows run per day - 500 keyframes per-flow run, 100 bytes per keyframe = 125,000 \* 500 \* 100 = 6.5 GB new run data per day |
- 32 GB RAM - 64-bit, 16 cores - 1 TB SSDs - Physical machine recommended - Consider splitting into multiple servers, depending on the network, disk performance, and spikes in usage |
- 4-16 GB RAM - 64-bit, 2-4 cores - 100 GB regular drive - Virtual machines are recommended for most scenarios - avoid noisy neighbors |
- 32 GB RAM - 64-bit, 16 cores - 2 TB SSDs - Physical machine recommended - A shared instance may be relevant, depending on spikes in usage |
| Department, high usage - 50 users, 5,000 flows, 50 agents, 10 runs per day - 5000 \* 50 \* 10 = 2,500,000 flows run per day - 500 keyframes per-flow run, 100 bytes per keyframe = 2,500,000 \* 500 \* 100 = 125 GB new run data per day |
- 32-64 GB RAM - 64-bit, 16 cores - 1 TB SSDs - Physical machine recommended - High-throughput, low-latency network with Agents and MS SQL Server recommended - Consider splitting into multiple servers, depending on the network, disk performance, and spikes in usage |
- 4-16 GB RAM - 64-bit, 2-4 cores - 100 GB regular drive - Virtual machines are recommended for most scenarios - avoid noisy neighbors |
- 64 GB RAM - 64-bit, 16 cores - Large disk array Shared instances and virtual machines not recommended - Consider splitting into multiple servers, depending on the network, disk performance, and spikes in usage |
| Company or site-wide, high usage - 250 users, 15,000 flows, 250 agents, 10 runs per day - 15000 \* 250 \* 10 = 37,500,000 flows run per day - 500 keyframes per-flow run, 100 bytes per keyframe = 37,500,000 \* 500 \* 100 = 2 TB new run data per day |
- 64 GB RAM - 64-bit, 16 cores - 1 TB SSDs - Physical machine recommended - High-throughput, low-latency network with Agents and MS SQL Server recommended - Multiple (departmental or project-related) servers recommended |
- 4-16 GB RAM - 64-bit, 2-4 cores - 100 GB regular drive - Virtual machines recommended for most scenarios - avoid noisy neighbors |
- 64 GB RAM - 64-bit, 16 cores - Large disk array - Shared instances and virtual machines not recommended - Consider splitting into multiple servers, depending on the network, disk performance, and spikes in usage |
Typically, the Studio is installed on the desktop version. We also recommend this for the Agent.
However, when deploying the Agent in the Data Center, it may not be possible to obtain a Windows desktop version. Therefore, the Agent will also run on a Windows Server with Desktop Experience enabled. The Server is installed on a Windows server.
For any clarification, please contact our Priority Support.