Hardware and Software Requirements | MuleSoft Documentation
# Hardware and Software Requirements
Before using MuleSoft RPA, ensure that your environment meets the minimum hardware and software requirements to use the cloud-based control plane and the on-premise RPA applications.
## RPA Manager
  * Use any of the supported web browsers to access the platform:
    * Microsoft Edge
    * Google Chrome
    * Apple Safari
    * Mozilla Firefox
  * Ensure you have access to your organization’s RPA Manager instance
The URL to access RPA Manager is `https://<tenant>.rpa.mulesoft.com`, where `<tenant>` represents your organization’s instance. If you are not sure about the name of your instance, contact your organization’s administrator.


## RPA Builder 6.7
### Hardware Requirements
Minimum | Recommended  
---|---  
Dual-core 2 GHz CPU (MMX/SSE compatible) | Dual-core 2 GHz CPU (MMX/SSE compatible)  
4 GB of RAM | 8 GB of RAM  
30 GB of disk space | 30 GB (SSD) of disk space  
Graphics Accelerator Card  
### Software Requirements
Software | Required version  
---|---  
Microsoft .NET Framework  
Operating System |  Any of the following:
  * Windows 10 (64 bit)
    * Professional
    * Professional for Workstations
    * Enterprise No support for Enterprise multi-session (Windows 10 Enterprise for Virtual Desktops).
    * Enterprise LTSC
  * Windows 11
    * Professional
    * Professional for Workstations
    * Enterprise No support for Enterprise multi-session (Windows 11 Enterprise for Virtual Desktops).
  * Windows Server 2019
  * Windows Server 2022

  
Any of the following:
  * Java Runtime Environment 11 (JRE, 64-bit version)
  * Adoptium 11 (JRE, 64-bit version)

  
#### File System Permission Requirements
RPA Builder needs full write access to folders that are critical to its functioning. To avoid issues during the setup process and subsequent RPA Builder executions, ensure that:
  * You install RPA Builder as an administrator
If you don’t run the setup file as an administrator, the installation process might not finish successfully. If this happens, make sure you reinstall RPA Builder by running the setup file as an administrator.
  * RPA Builder has full write access to these folders and any subfolders and files inside them:
    * `C:\Users\<USERNAME>\Documents\Mulesoft`
    * `C:\Users\Public\Documents\Mulesoft`
    * `C:\Users\<USERNAME>\AppData\Local\MuleSoft_LLC`
    * `C:\Users\<USERNAME>\AppData\Roaming\MuleSoft`
    * `C:\ProgramData\Mulesoft\RPABuilder\Cache`
  * Your environment isn’t blocking the execution of any RPA process
The operating system can block the execution of certain files. Make sure that all executable (`.exe`) files inside the RPA Builder home directory and its subfolders are allowed to run.


#### Check for Software Interference
Some software can prevent RPA Builder from working properly. Resolve any software issues you find before installing RPA Builder.
Software | Problem | Solution  
---|---|---  
**Microsoft OneDrive** Microsoft OneDrive is an application for backing up data from a computer. |  When you turn on Microsoft OneDrive backup for the Documents folder on your computer, it moves this folder to a different location. When RPA Builder starts, it tries to clean up the cache folder, but OneDrive redirects this to the new location where RPA Builder doesn’t have permission to write:
  * From: `C:\Users\<username>\Documents\Mulesoft\Cache`
  * To: `C:\Users\<username>\OneDrive\Documents\Mulesoft\Cache`

This causes an error that you can find in the log files: `System.IO.IOException: Access to the path 'C:\Users\<username>\OneDrive\Documents\Mulesoft\Cache' is denied`. A user describes this problem in detail in a Microsoft Community thread. |  If you use RPA Builder on a computer that has OneDrive, don’t let OneDrive back up your Documents folder. The Microsoft OneDrive documentation explains how to exempt the Documents folder from the OneDrive backup.  
### Compatibility
Application | Version  
---|---  
RPA Recorder | 6.6.0 and later  
1.0.0 and later  
For Hardware and Software requirements for earlier RPA Builder versions, refer to the corresponding product documentation:
  * RPA Builder 6.6 Hardware and Software Requirements
  * RPA Builder 6.5 Hardware and Software Requirements
  * RPA Builder 6.4 Hardware and Software Requirements
  * RPA Builder 6.3 Hardware and Software Requirements
  * RPA Builder 6.2 Hardware and Software Requirements
  * RPA Builder 6.1 Hardware and Software Requirements
  * RPA Builder 6.0 Hardware and Software Requirements


## RPA Recorder 6.6
### Hardware Requirements
Minimum | Recommended  
---|---  
Dual-core 2 GHz CPU (MMX/SSE compatible) | Dual-core 3 GHz CPU (MMX/SSE compatible)  
8 GB of RAM | 16 GB of RAM  
5 GB of disk space | 10 GB (SSD) of disk space  
### Software Requirements
Software | Required version  
---|---  
Microsoft .NET Framework  
Operating System |  Any of the following:
  * Windows 10 (64 bit)
    * Professional
    * Professional for Workstations
    * Enterprise No support for Enterprise multi-session (Windows 10 Enterprise for Virtual Desktops).
    * Enterprise LTSC
  * Windows 11
    * Professional
    * Professional for Workstations
    * Enterprise No support for Enterprise multi-session (Windows 11 Enterprise for Virtual Desktops).
  * Windows Server 2019
  * Windows Server 2022

  
#### Recommended System Settings
  * Display resolution: Full HD 1080p (1920 × 1080) or higher


#### File System Permission Requirements
RPA Recorder needs full write access to folders that are critical to its functioning. To avoid issues during the setup process and subsequent RPA Recorder executions, ensure that:
  * You install RPA Recorder as an administrator
If you don’t run the setup file as an administrator, the installation process might not finish successfully. If this happens, ensure you reinstall RPA Recorder by running the setup file as an administrator.
  * RPA Recorder has full write access to the following folders and any subfolders and files inside them:
    * `C:\Program Files\MuleSoft\RPARecorder`
    * `C:\RPARecorder`
  * Your environment is not blocking the execution of any RPA process
The operating system can block the execution of certain files. Ensure that all executable (`.exe`) files inside the RPA Recorder home directory and its subfolders are allowed to run.


### Compatibility
Application | Version  
---|---  
RPA Builder | 6.6.0 and later  
1.4.0 and later  
For Hardware and Software requirements for earlier RPA Recorder versions, refer to the corresponding product documentation:
  * RPA Recorder 6.5 Hardware and Software Requirements
  * RPA Recorder 6.4 Hardware and Software Requirements
  * RPA Recorder 6.3 Hardware and Software Requirements
  * RPA Recorder 6.2 Hardware and Software Requirements
  * RPA Recorder 6.1 Hardware and Software Requirements
  * RPA Recorder 6.0 Hardware and Software Requirements


## RPA Bot 1.7
### Hardware Requirements
  * For optimal performance, use a dedicated computer for running the RPA Bot.
  * The following table shows the minimum and the recommended hardware requirements for running one process:
Minimum | Recommended  
---|---  
Dual-core 2 GHz CPU (MMX/SSE compatible) | Dual-core 3 GHz CPU (MMX/SSE compatible)  
8 GB of RAM | 16 GB of RAM  
30 GB of disk space | 30 GB (SSD) of disk space  
To run more than one process in parallel, when using Secure Sessions, you must add 2 GB of RAM plus the RAM needed to run the process for each parallel run to these recommended values.
For example, to run two different processes in parallel:
    * Process 1 requires one GB of RAM and runs 10 times in parallel.
    * Process 2 requires three GB of RAM and runs five times in parallel.
In this case, use the following formula to calculate that you need a computer with a minimum of 63 GB of RAM:


#### Unsupported Hardware Configurations
  * Notebooks with Intel Graphics 520 and 530


### Software Requirements
Software | Required version  
---|---  
Microsoft .NET Framework  
Operating System |  Any of the following:
  * Windows 10 (64 bit)
    * Professional
    * Professional for Workstations
    * Enterprise No support for Enterprise multi-session (Windows 10 Enterprise for Virtual Desktops).
    * Enterprise LTSC
  * Windows 11
    * Professional
    * Professional for Workstations
    * Enterprise No support for Enterprise multi-session (Windows 11 Enterprise for Virtual Desktops).
  * Windows Server 2019
  * Windows Server 2022

  
#### System Settings
  * Display resolution:
    * Minimum: 1280 x 1080
    * Recommended: Full HD 1080p (1920 × 1080) or higher
  * `Custom scaling` of text and other items on the screen: 100%
  * `ClearType`: turned off
#### Unsupported Hardware Configurations
  * Notebooks with Intel Graphics 520 and 530


### Software Requirements
Software | Required version  
---|---  
Microsoft .NET Framework  
Operating System |  Any of the following:
  * Windows 10 (64 bit)
    * Professional
    * Professional for Workstations
    * Enterprise No support for Enterprise multi-session (Windows 10 Enterprise for Virtual Desktops).
    * Enterprise LTSC
  * Windows 11
    * Professional
    * Professional for Workstations
    * Enterprise No support for Enterprise multi-session (Windows 11 Enterprise for Virtual Desktops).
  * Windows Server 2019
  * Windows Server 2022

  
#### System Settings
  * Display resolution:
    * Minimum: 1280 x 1080
    * Recommended: Full HD 1080p (1920 × 1080) or higher
  * `Custom scaling` of text and other items on the screen: 100%
  * `ClearType`: turned off


#### Requirements for the Secure Session Technology
Secure Sessions are hidden Desktop sessions that run in the background and are accessible only to the bot. An additional advantage of using Secure Sessions is that the bot can multiply itself to run several process instances in parallel.
To use Secure Sessions you must ensure that all prerequisites are met and all responsible persons are informed.
  * You can’t use Secure Sessions with any operating system running on the Microsoft Azure Virtual Desktop Infrastructure (VDI).
  * The RPA Bot service runs under the `Local System` account per default.
    * To use another account, ensure that it has permission to run Windows services.
  * The RPA Bot service runs processes under user accounts on the same computer or within the same domain.
    * Use dedicated accounts and a user-naming scheme to differentiate between local users and domain users and between human users and bot users.
    * User accounts used by the bot to run processes must belong to the `Remote Desktop Users` group and must have permission to establish a local RDP session via the local loopback address 127.0.0.2.
  * To enable a bot to run more than one (Windows 10, Windows 11) or two (Windows Server) Secure Sessions simultaneously, ensure that a terminal server software with enough licensed users is installed on the computer where the bot is installed. The computer must have enough resources to execute several processes simultaneously: 2 GB or more RAM per session.
Although other terminal server software can work, RPA has been validated with the following terminal server software:
    * Microsoft Remote Desktop Services
    * TSplus MuleSoft RPA Connector
  * Before deploying a run configuration on a bot that has only one licensed Secure Session, do not disconnect the session, instead sign out the specified user.
    * Do not sign in to a computer where a bot with one licensed Secure Session is running a process.


#### File System Permission Requirements
RPA Bot needs full write access to some folders that are critical to its functioning. To avoid issues during the setup process and later RPA Bot executions, ensure that:
  * You install RPA Bot as an administrator
If you don’t run the setup file as an administrator, the installation process might not finish successfully. If this happens, ensure you reinstall RPA Bot by running the setup file as an administrator.
  * RPA Bot has full write access to the following folders and any subfolders and files inside them:
    * `C:\Program Files\Mulesoft\RPABot`
    * `C:\ProgramData\Mulesoft\RPABot`
  * Your environment is not blocking the execution of any RPA process
The operating system can block the execution of certain files. Ensure that all executable (`.exe`) files inside the RPA Bot home directory and its subfolders are allowed to run.


#### Internet Route Requirements
To communicate with RPA Manager, RPA Bot requires you to enter the following Internet route in the **RPA Manager to connect** field on the RPA Bot Configurator pop-up:
  * `https://[your subdomain].rpa.mulesoft.com`


In addition, it is also necessary to open the internally used URL `https://*.cloudfront.net`, which is done typically by your network or security team.
See Configuring RPA Bot for more information about the RPA Bot Configurator pop-up.
### Compatibility
Application | Version  
---|---  
RPA Builder | 6.4.0 and later  
RPA Recorder | 6.4.0 and later  
For Hardware and Software requirements for earlier RPA Bot versions, refer to the corresponding product documentation:
  * RPA Bot 1.6 Hardware and Software Requirements
  * RPA Bot 1.5 Hardware and Software Requirements
  * RPA Bot 1.4 Hardware and Software Requirements
  * RPA Bot 1.3 Hardware and Software Requirements
  * RPA Bot 1.2 Hardware and Software Requirements
  * RPA Bot 1.1 Hardware and Software Requirements
  * RPA Bot 1.0 Hardware and Software Requirements


## See Also
  * Tutorial: Create an Automation from Start to Finish