The following are the systems that Robocorp tests on. Other operating systems might also work, but we cannot guarantee that.
It is recommended to keep Windows systems up-to-date according to Microsoft release information in the links below, as older versions always have potential security concerns.
For development tasks, the user usually needs some elevated permissions (for installing the software), but in Robocorp applications, we avoid requiring admin permissions while running.
- Professional and Enterprise editions.
- Windows Server 2019 version or later with long path support enabled.
There is no clear statement on the versions of macOS that are officially supported, but the majority rule from Apple seems to be
the latest two releases are supported, so we aim to adhere to that as well.
The supported macOS versions at the time of writing are:
Sonoma was released on the 5th of June 2023; limited tests ran at the time of writing.
For ARM architecture machines (M1/M2), the support of many tools and libraries is still very limited, so we support those via Rosetta 2 translation layer.
Supported Linux distributions are specified per component. Other Linux distributions may work just fine, but our standard support agreement covers the following.
- Debian 12 "bookworm"
- Ubuntu 22.04
- Debian 12 "bookworm"
- Note! Ubuntu 22.04 is NOT supported with unattended Chrome browser automations due to Chrome being distributed as a Snap package
- Technical support is provided only under an extended support contract. Get in touch with your account manager if interested.
- The latest version of Chrome is the recommended browser.
- Tools and libraries also support other browsers, but we limit our tests to Chrome.
Minimum system requirements are always subjective because even a low-end system can edit and execute robots.
Developers creating the automation should always have a capable machine because there is nothing worse than wasting development time due to hardware limitations.
- At least 6 cores, 16GB of memory, 40GB of free disk space on a fast disk (SSD)
- The Robocorp toolchain is designed to utilize multicore CPUs, so more logical cores are always better.
- For example, virus scanners commonly utilize one CPU core.
- Testing multiple browser automations and running multiple applications at the same time is common when developing, so memory needs to match the needs
- Automations and Python are normally really file I/O intensive
- Developers need to build and test the Python environments, so here, a fast disk is a crucial thing
When executing automations, the system requirements can vary a lot. The most significant factors for the system requirements are:
- The operating system needed:
- Windows needs a lot more than Linux
- The target automation:
- Big websites require a lot of memory
- Heavy Windows applications and virus scanners can eat up a lot of CPU cores and processing power
- Automations that work with thousands of PDF files require a lot of file space and a fast file I/O
- 4 CPU cores, 8GB of memory, 40GB of free disk space on a fast disk (SSD):
- File I/O speed affects execution times a lot.
- Features like video streaming on a system with fewer cores is not recommended
We recommend getting RCC tool and running
rcc config speedtest to evaluate your system.
The speed test performs a standard action that tests CPU, network, and disk speed to gather relative numbers.
filesystem, results above zero are good; values below indicate slower performance.
- A good developer machine:
- Dell XPS 15 9520, 16GB RAM, 14 cores (20 logical processors), 500GB NVMe SSD
- Antivirus and disk encryption on
Score for network=89, filesystem=96, and time=39 with 19 workers on "windows_amd64".
- Robocorp hosted Cloud Worker running on a Debian Linux Docker container
- The disk on virtualized systems is normally the slowest part, but the Cloud worker still manages an overall good time of just over a minute
Score for network=85, filesystem=-131, and time=65 with 7 workers on "linux_amd64".