Agents

The agent is the component that runs automations on your infrastructure. It connects to the Sinfonia orchestrator, receives executions from the queue and sends logs and status back. Without a connected agent, no bot runs.

Sinfonia offers three agents. The type of bot you publish and the environment where it will run determine which one you need:

Docker: an agent deployed as a container on a Docker Host, which runs Docker bots from the published images.
Windows: a binary that runs directly on Windows and executes Script, Zip and Git bots, including those that use a graphical interface.
Linux: a binary that runs directly on Linux and executes Script, Zip and Git bots, and can be set up as a service.

Differences between the agents

	Docker	Windows	Linux
Bot types	Docker	Script, Zip and Git	Script, Zip and Git
Where it runs	Linux machine with Docker Engine and Docker Compose	Windows 10, 11 and Server	Linux distributions
How it is installed	Image downloaded from the platform, loaded with `docker load` and started with Docker Compose	`agent.exe` binary downloaded from the portal and run on the machine	`agent` binary downloaded from the portal and run on the machine
Continuous execution	Container with `restart: unless-stopped`	`agent.exe` process running on the machine	systemd service, `nohup`, `tmux` or `cron`
Bot dependencies	Included in each bot’s image	Installed on the agent’s machine (Python, Node, etc.)	Installed on the agent’s machine (Python, Node, etc.)
Isolation	Each execution runs in a separate container	Bots run directly on the operating system	Bots run directly on the operating system
Graphical interface	No, containers run without a graphical interface	Yes, in `Headed` modes, with its own RDP session	Yes, in `Headed` modes, when the agent runs inside a graphical session
Network	Outbound HTTPS (port 443) to the orchestrator, UDP ports `49252` to `49292` and access to the image registries	Outbound HTTPS (port 443) to the orchestrator	Outbound HTTPS (port 443) to the orchestrator
Selection in the bot	`Docker Host` field	`Agent` field	`Agent` field
Monitoring	Docker Hosts screen	Agents screen	Agents screen
Licensing	Premium feature, purchased separately	Available on the platform	Available on the platform

Which agent to use

Use the Docker agent for automations packaged as Docker images, when you want a reproducible, isolated environment with the runtime and dependencies inside the image.
Use the Windows agent for automations that interact with the screen, depend on software installed on the machine or need to run on Windows.
Use the Linux agent for automations on Linux servers, which use the Python, Node or binaries installed on the machine.

The agents can be combined in the same account: each bot is run by the agent selected when it was created.

Haven’t set up an agent yet?

Pick the environment and follow the deployment steps:

Docker

For Docker bots: deploy the agent as a container on a Docker Host

Windows

For Script, Zip and Git bots: download agent.exe and connect the machine

Linux

For Script, Zip and Git bots: download the binary and set it up as a service

Tip

Just getting started? Install the agent for Windows or Linux first and move on to Your First Bot. The Docker agent can be added later.

Last updated on 06/10/2026