Skip to main content
A desktop is a Windows machine that runs the application you are automating. Every job executes against a desktop, and everything the automation does happens there: the clicks, the keystrokes, the screen reads, the recording. Each desktop runs the Minicor Desktop Service, the service that connects the machine to the platform, executes automation steps, and captures replays. Minicor provisions cloud desktops with it preinstalled, or you install it on a machine you control. Once the service is running, the desktop appears in your workspace with a live preview, ready for jobs. A connected desktop in the dashboard: healthy, with a live screen view and RDP access one click away.

​
Where automations run

Automations drive the target application through its interface, the pixels and controls on screen, so they run anywhere that interface appears.

​
Virtual machines

Minicor provisions a Windows VM with the Desktop Service installed, the fastest way to start. Or install the Desktop Service on a machine you control: your cloud project, your VPC, or on premises next to the system being automated. That is the usual choice when the target system is locked down or the data cannot leave your boundary. See Deploy on your cloud.

​
Browsers

Web applications run in a managed browser session on the desktop. The automation handles single-page apps, dynamic content, popups, and authentication flows, and a single job can mix browser and desktop steps: read from a web portal, write into a desktop application, in one run.

​
Citrix and remote desktops

Applications served through Citrix, RDP, or another virtual desktop environment automate the same way local ones do: the automation works the visual stream, so no Citrix-specific connectors are needed. Session disconnects, reconnects, and latency are handled as part of the run. Wherever it runs, the target application signs in with your existing account for that system. No separate integration user is required.

​
Watching and intervening

The dashboard shows a live view of each connected desktop. The same view appears on the job page while the builder works and while runs execute, so you always see what the automation sees. When you need to act on the desktop yourself (dismiss a one-time dialog, complete a manual sign-in), you can take control from the browser. For extended work on the machine, connect over RDP as usual.

​
Scaling out

One desktop is enough to build and go live. When volume grows, add more desktops and Minicor distributes work across them. Jobs that must not overlap on the same application serialize automatically, so two runs never fight over one screen.