// Platform

Jaws Deploy Agents

A lightweight service that runs on your servers and handles deployment execution — without opening a single inbound port. Agents work with Jaws Deploy Cloud and Jaws Deploy Stack.

What agents do

Agents are the bridge between Jaws Deploy and the machines where deployment work actually runs. They receive deployment tasks from the Jaws Deploy server, execute steps against local targets, stream logs back in real time, and report completion status — all without requiring the Jaws Deploy server to reach directly into your infrastructure.

Your servers stay behind the firewall

The security model is the most important thing to understand about agents. The agent initiates an outbound connection to the Jaws Deploy server using a secure, persistent WebSocket channel — your servers do not need to accept any inbound connections. No firewall rules to open. No VPN tunnels to maintain. No exposed ports.

This means the agent model works naturally with corporate security policies, DMZ layouts, on-premises networks, and private cloud environments where inbound access to production servers is prohibited or impractical.

Outbound-only connection The agent opens a secure WebSocket channel to the Jaws Deploy server. Your infrastructure never needs to accept inbound connections from the platform.
Windows and Linux Agents run as a Windows Service or Linux daemon. Any server or VM your deployments need to reach can run an agent.
Self-updating Agents update themselves when new versions are released. Teams running Jaws Deploy Stack can point agents at a custom update server for controlled rollouts.
Approved before execution When an agent connects for the first time it sends a handshake. An administrator approves it in the Jaws Deploy interface before the machine can receive any deployment work.
Getting started

Installation takes minutes.

The Jaws Deploy interface provides a ready-to-run install script for each target. Run it on the target machine/deployment target, the Agent registers itself and sends a handshake, and an administrator approves the connection. From that point the machine is available as a deployment target.

// Next step

Ready to connect your infrastructure to Jaws Deploy?