Skip to main content
Go to the Studio
Runner

Installing the Runner

System requirements, the available editions, and a full guide to installing the Roberty Runner on a computer or a server.

Installing the Runner

System requirements​

Before installing, check that the environment meets everything below. Skipping this step is the single most common cause of performance and connectivity trouble.

Hardware​

ResourceMinimumRecommended
RAM4 GB8 GB or more
Storage10 GB freeAn SSD with 10 GB or more
ProcessorDual-core 2 GHzQuad-core 2.5 GHz or better

Operating system​

Servers and production environments:

  • Windows Server 2016, 2019 or 2022
  • Windows 10 or 11 (64-bit)
  • Ubuntu 20.04 LTS or later (Roberty Production Runner only)

Development machines:

  • Windows 10 or 11 (64-bit)
  • macOS 12 Monterey or later
Windows Server 2012 R2 (legacy environment)

Google Chrome no longer ships updates for Windows Server 2012 R2. On those machines, use Chromium 109: Download Chromium 109

Once downloaded, extract it into C:\Program Files\Google\Chrome\Application.

Required software​

SoftwareWhen you need it
Microsoft Visual C++ Redistributable 2015-2022 (download)Always — it provides the runtime libraries Roberty uses to reach Windows' native APIs
.NET Framework 4.8 or later (download)Always — required to integrate with the operating system
Google Chrome or Microsoft Edge (latest version)Always — required for web automation
Microsoft Office 2016 or laterOnly for robots that handle Excel files (.xlsx / .xls) or automate Office

Firewall rules you will need​

Roberty needs a set of endpoints reachable on the network where the Runner is installed — both to build robots and to run them. Environments with a restrictive firewall or proxy must allow those addresses before installing.

How to get the list of endpoints

Our support team provides the list. Contact them through the support channels and say you need the firewall rules to install the Runner or Roberty Studio Desktop.

caution

A firewall or proxy blocking the required endpoints causes connection failures, a device showing as offline, or a failure to update the action library.

Notes for virtual machines​

The Runner runs on virtual machines, on local infrastructure and on public clouds (AWS, Azure, GCP) alike. A few extra precautions keep the robots from being interrupted.

Keeping the session alive after logoff​

For runs to continue after the user logs off the VM, the virtual machine's display has to stay active. Create a .bat script with the content below and run it as you end the session:

bat
@echo off
tscon %sessionname% /dest:console

Automatic logon after a restart​

If the VM does not log the user in automatically after a restart, set up Microsoft Autologon so runs continue without anyone stepping in.

Fixing a standard resolution​

A standard screen resolution avoids errors interacting with graphical interfaces and makes several machines easier to maintain. To set it through the Registry Editor:

  1. Press Windows + R, type regedit and press Enter.
  2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration.
  3. Find the key for your display and set PrimSurfSize.cx (width) and PrimSurfSize.cy (height) to the resolution you want — 1920 and 1080, for example.
  4. Restart the computer to apply it.
caution

Back the registry up before changing anything.

The available editions​

Roberty offers two installations, each with its own purpose. Pick the one that matches what you are doing.

Roberty Studio Desktop​

For development and testing. It bundles the Designer — where you build the robots — and the Runner that executes them into a single application.

  • Available for: Windows and macOS
  • What it gives you: early access to experimental features, which land in the Desktop edition before they reach the Studio on the web

Roberty Production Runner​

For servers and production environments. A lean installation dedicated to running robots, with no design interface.

  • Available for: Windows and Linux
  • Best for: data-centre servers, virtual machines, high-availability environments and running at scale

Downloading it​

  1. Open your workspace at studio.roberty.app.
  2. In the top menu, click Download Roberty.
  3. Pick the edition that suits your environment:
    • On my computer → Roberty Studio Desktop
    • On a server → Roberty Production Runner
  4. Click Download to fetch the installer.

Installing on Linux​

The Roberty Production Runner is available for:

  • Debian and derivatives (such as Ubuntu)
  • RHEL — Red Hat Enterprise Linux

Contact our support channels for the installation instructions for these.

Step by step​

Step 1 — Run the installer​

Open the file you downloaded. If Windows shows "Windows protected your PC":

  1. Click More info.
  2. Click Run anyway.
Why does Windows show that warning?

To automate anything, Roberty needs permission to drive the mouse and keyboard and to reach the file system. Windows Defender raises this alert for any software asking for those permissions without a major publisher's digital signature. Roberty is safe — this is a standard operating-system measure, not a sign of risk.

File blocked by Windows Explorer?

If Windows blocks the file before you even run it: right-click the installer, choose Properties, tick Unblock on the General tab and click OK. Then run it normally.

Step 2 — Sign in​

  1. Enter the email and password of your Roberty account.
  2. Select the workspace this device will belong to.

If this is your first time with Roberty, create your account at studio.roberty.app first.

Step 3 — Name the device​

Give this device a name. It appears in the Studio and in the run logs — pick something that will still be easy to recognise later.

Good practice
  • Use descriptive, consistent names: SERVER-PROD-01, DESKTOP-DEV-JOAO, VM-FINANCE
  • Prefer uppercase and hyphens — avoid spaces and special characters
  • Include the environment (DEV, STAGING, PROD) to keep a workspace with many devices manageable

Step 4 — Service settings​

This step sets the Runner's technical preferences. The defaults suit most cases — change them only if your environment requires something specific.

SettingWhat it isDefault
Local databaseThe database that stores logs and the run queueSQLite
Admin panel portThe HTTP port of the local admin panel — generated during installationGenerated automatically
Admin panel passwordThe password to reach the local admin panel(you choose it)
Keep the admin panel password

The panel's password is set once, on this screen. Keep it somewhere safe — you will need it every time you open the admin panel. If you have to reset it later, contact support.

Port conflict?

If the automatically generated port is already taken by another service on the machine, change it here to a free one. Check first with netstat -a in the terminal.

Step 5 — Finish​

Click Get started. The Runner will:

  1. Register the device against your Roberty account
  2. Start its background services
  3. Connect to Roberty Studio automatically

Within seconds the device shows as Online in the Studio.

Checking the installation​

Confirm everything works before linking a robot:

In the local panel:

  1. Open a browser on the installed machine and go to the URL shown at the end of the installation (e.g. http://localhost:PORT).
  2. Sign in with the password you set during installation.
  3. Check that the service status reads Active.

In Roberty Studio:

  1. Go to studio.roberty.app.
  2. In the side menu, open Devices (or open any robot's settings → Devices tab).
  3. The new device should be there, Online.

If it is not, see the troubleshooting below.

Troubleshooting​

The device does not show as online in the Studio

  • Confirm the machine reaches the internet with no proxy blocking outbound connections.
  • Check whether a firewall or antivirus is blocking the port configured during installation.

The admin panel does not open in the browser

  • Confirm the port: use the URL shown at the end of the installation. If you did not note it down, check the Runner's settings.
  • In some corporate environments localhost is blocked. Try 127.0.0.1 in the URL instead.

Authentication error when signing in to the installer

  • Confirm the email and password work at studio.roberty.app.
  • Check that your account is allowed to add devices to the workspace.

Windows blocks it even after clicking "Run anyway"

  • Right-click the installer → Properties → General tab → tick Unblock → OK.
  • If it persists, try turning the antivirus off for the installation and back on afterwards.

Next​