---
title: Remote Agents
slug: remote-agents
docTags: 
createdAt: 2025-08-11T11:13:48.000Z
---

Swimlane Remote Agents run automation actions on networks outside your primary Swimlane environment. Agents use outbound Secure Websockets (TLS/443) to Turbine. Connectors and action data travel over that connection; a VPN to the customer network is not required.

Remote agents require a container host (**Docker** or **Podman**). You install an agent with the install script from **Admin Panel** > **Settings** > **Tenant** > **Nodes**. For the full procedure, see [Installation](https://docs.swimlane.com/installation).

## Choose Your Path

| **I want to…**                                              | **Start here**                                                                     |
| ----------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| Understand how remote agents work                           | [Architecture](./#architecture)                                                    |
| Install an agent (including Quadlet or override registries) | [Installation](https://docs.swimlane.com/installation)                             |
| View agents and pools                                       | [Viewing Remote Agents](https://docs.swimlane.com/viewing-remote-agents)           |
| Assign pools to playbook actions                            | [Assigning Pools to Actions](https://docs.swimlane.com/assigning-pools-to-actions) |
| Uninstall an agent                                          | [Uninstall Remote Agent](https://docs.swimlane.com/uninstall-remote-agent)         |

## Architecture

Remote agents use containers to isolate workloads. Connectors run as containers inside an internal Podman engine, next to a Turbine agent container. The agent opens an outbound Secure Websocket to Turbine. All traffic to the primary instance uses TLS/443. During install and upgrade, base images pull from `quay.io` unless you override image locations.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/A9m-tbMgPsjUe_CkDREQH_remote-agent-arch.png" size="68" width="1027" height="612" darkWidth="800" darkHeight="476" position="center" showCaption="false"}

Agents schedule automatic updates with a cron job created at install time. Older agents can still connect after a platform upgrade; the update job replaces them on the next cron run.

:::hint{type="info"}
Starting in **Turbine 26.3.0**, you can install with **Podman Quadlet** (`-Q`) and pull connector images from override registries (`-B` / `-C`). See [Installation](https://docs.swimlane.com/installation).
:::

## Related Guides

- [Installation](https://docs.swimlane.com/installation)
- [Viewing Remote Agents](https://docs.swimlane.com/viewing-remote-agents)
- [Assigning Pools to Actions](https://docs.swimlane.com/assigning-pools-to-actions)
- [Uninstall Remote Agent](https://docs.swimlane.com/uninstall-remote-agent)