Skip to main content

VIKTOR Desktop

VIKTOR Desktop is a Windows application that lets you install, authenticate, run, and monitor your personal workers from one place. Instead of downloading a separate installer and generating a connection key for every worker, you install VIKTOR Desktop once, log in with your VIKTOR account, and start the workers you need. Workers run managed inside the VIKTOR Desktop and each worker has its own formatted logs.

Organization workers are managed by environment administrators and are not affected; they continue to use the existing installation flow.

VIKTOR Desktop showing your workers and their status

Supported workers​

The following workers are available in VIKTOR Desktop, and this list will expand over time: AxisVM, Dynamo, ETABS, Excel, Grasshopper, GRLWEAP, Idea RCS, Matlab, Plaxis, Python, Revit, RFEM, Robot, SAP2000, SCIA, Tekla, D-Foundations, D-Geostability, D-Settlement, D-Sheetpiling and D-Stability. In addition, the generic worker is available to integrate with any other software that supports command-line interaction.

note

Personal workers that were installed with the previous per-worker installers are not picked up by VIKTOR Desktop — see VIKTOR Desktop and existing worker installations.

Requirements​

  • Operating system: Windows (64-bit AMD or Intel processor). macOS and Linux are not supported.
  • The third-party software that is to be integrated is installed and licenses are available on the same machine.
  • Outgoing TCP access to the internet over port 443.
  • A web browser to log in with your VIKTOR account.
For IT administrators

Logging in to VIKTOR Desktop uses OAuth 2.1 with PKCE: the app opens the system browser and completes the login through a temporary redirect to a local loopback address (localhost). No ports need to be opened for incoming traffic from the network.

Install VIKTOR Desktop​

  1. Download the VIKTOR Desktop installer (a signed .msi Microsoft Installer). You can download it directly below, or from:
    • the "My integrations" tab in your personal settings, using the "Download VIKTOR Desktop" button on the "Local software" tab, or
    • the editor of an application: when the application has a worker as a dependency and the platform does not detect a connected VIKTOR Desktop (not installed, or not running), the editor offers the download
  2. Run the installer and complete the installation wizard
  3. Launch VIKTOR Desktop
Download VIKTOR Desktop for Windows

The "My integrations" page with the "Download VIKTOR Desktop" button

You only need to do this once per machine; all your personal workers are managed from within the app. When a new version of VIKTOR Desktop is available, the app prompts you to update; once you confirm, it updates automatically — you never need to download and run the installer again.

Log in​

On first launch, VIKTOR Desktop asks you to sign in: paste the URL of your VIKTOR environment, click "Next", and log in with your VIKTOR account in the browser that opens. After logging in, return to the app.

The VIKTOR Desktop sign-in page

You log in once for all your personal workers: no connection keys need to be generated or pasted. To log out, or to switch to a different VIKTOR environment, click your profile in the top-right corner of VIKTOR Desktop and select "Log out".

Add and configure a worker​

  1. In VIKTOR Desktop, click "Add"

  2. Select the software you want to integrate with

    Selecting the software when adding a worker

  3. Configure the worker where needed. The configuration differs per software:

    • For Python-based workers, select the Python environment of your choice by setting the path to its python.exe as the executable path. This can be your system Python, or the python.exe in a dedicated virtual environment.
    • For workers that run a local program (e.g. Dynamo), set the path to that executable.
    • For the generic worker, VIKTOR Desktop exposes the worker's config.yaml file, in which you define the executables, arguments and paths yourself.
note

The first release of VIKTOR Desktop does not expose the executable arguments for dedicated workers; only the generic worker allows for arguments (through its config.yaml).

Run and stop workers​

Workers are started and stopped inside VIKTOR Desktop and run managed by the app — there is no separate terminal window. The worker list shows for each of your workers whether it is "Running" or "Stopped". When a worker update is available, VIKTOR Desktop prompts you to update; once you confirm, the worker updates automatically — there is no installer to rerun.

View logs​

Each worker has its own log inside VIKTOR Desktop. Logs are formatted, showing when tasks are started and completed and any errors the worker encounters.

The log view of a worker in VIKTOR Desktop

Worker status in the editor​

The editor shows whether your worker is online or offline (see also worker status). If a worker is offline, the editor can take you directly to the right worker in VIKTOR Desktop to start it. When the platform does not detect a connected VIKTOR Desktop at all, the editor offers to download it.

VIKTOR Desktop and existing worker installations​

VIKTOR Desktop does not alwayss pick up existing worker installations. Personal workers that were installed with the previous per-worker installers keep running, but they are not necessarily detected by or migrated into VIKTOR Desktop: to move a personal worker over, add and configure it again in VIKTOR Desktop.

Stop your old personal workers

When you move a personal worker over to VIKTOR Desktop, uninstall (or at least stop) its existing installation. If both keep running, two workers with potentially different configurations compete for the same tasks, which leads to unpredictable results.

New personal workers can only be added through VIKTOR Desktop: with the release of VIKTOR Desktop, the per-worker installer download and the connection-key flow are no longer available on the "My integrations" page for personal workers.

Organization workers and workers running on (shared) servers continue to use the existing installers.

Troubleshooting​

  • Logging in does not complete: make sure a default browser is available and that the browser can reach your VIKTOR environment. If your organization restricts localhost redirects or uses a proxy, see the note for IT administrators under requirements.
  • The editor shows the worker as offline: check in VIKTOR Desktop that the worker is running, and inspect its log for errors.