Install on Linux Hosts

This method will install the Steadybit agent on your Linux machine using the respective package managers. By default, it will install the agent as well as the extensions extension-http, extension-container, and extension-host.

Supported Package Managers

  • apt

  • yum / dnf


To install the agent, you must be able to access the following URLs via HTTPS (443) on your target environment:

  • (Platform)

  • (.deb and .rpm packages)

  • (Setup Scripts)

Agent Installation

To install the agent on your Linux system, you can copy the installation script from the setup page in the SaaS platform.

Alternatively, you can update and run the script below with your agent key, which you find in the platform's setup page:

chmod a+x
./ --key <agent-key>


The API key the agent uses


The extensions to install



If running on-prem, the URL of your platform installation


Override the used package version


Override the default package repository URL{yum}-public/ or{deb}-public/


Override the username for accessing the package repository


Override the password for accessing the package repository

Configure HTTP Proxy Server

The Steadybit Agent uses HTTP and websockets to communicate with the platform and to download updates. To simplify the agent deployment, consider allowing direct communication to our platform.

If you require a single entry into and out of your network, you can configure the agent to use a proxy:

  1. Edit /etc/steadybit/agent and set the values for these variables:

STEADYBIT_AGENT_PROXY_HOST="<hostname or address of your proxy>"
STEADYBIT_AGENT_PROXY_PORT="<port of your proxy>"
STEADYBIT_AGENT_PROXY_PROTOCOL="<proxy protocol e.g. http>"
STEADYBIT_AGENT_PROXY_USER="<username of the proxy (if needed)>"
STEADYBIT_AGENT_PROXY_PASSWORD="<password of the proxy (if needed)>"
  1. Restart the service

When using systemd

systemctl daemon-reload && systemctl restart steadybit-agent

When using InitV

service steadybit-agent restart

Managing the Agent and Extension


The logs for agent and extensions are located in /var/log/steadybit-*.log


The configurations for agent and extensions are located in /etc/steadybit


When using systemd

systemctl start steadybit-agent
systemctl stop steadybit-agent
systemctl restart steadybit-agent

When using InitV

service steadybit-agent start
service steadybit-agent stop
service steadybit-agent restart

The same applies to extensions. The services are named steadybit-extension-*.

Removing the Agent

Remove the packages using the package manager:

apt-get remove --purge steadybit-agent \
  steadybit-extension-http \
  steadybit-extension-container \

Or when using yum:

yum remove steadybit-agent \
  steadybit-extension-http \
  steadybit-extension-container \

Additional Extensions

If you want to use additional extensions (e.g. extension-jvm for attacking Java applications), you can apply the --extensions parameter.

./ --key <agent-key> --extensions steadybit-extension-host,steadybit-extension-container,steadybit-extension-http,steadybit-extension-jvm

Using a single agent across multiple hosts

By default the installs the agent and extension on a single host. When installed on multiple hosts, each runs an agent instance, allocating many resources. Installing the agent on a dedicated host and only the container and host extension on each host is possible.

Non-Agent Hosts

  • Install only container and host extensions by using --no-agent flag

./ --key <agent-key> --no-agent --extensions steadybit-extension-host,steadybit-extension-container
  • Reconfigure the extension to listen on http by editing /etc/steadybit/extension-container and /etc/steadybit/extension-host and removing the STEADYBIT_EXTENSION_UNIX_SOCKET=... line. If you want to override the default port set STEADYBIT_EXTENSION_PORT.

  • Restart the extensions

systemctl restart steadybit-extension-container
systemctl restart steadybit-extension-host

Agent Host

  • Install the Agent as usual

  • For each extension running on a different host, create a /etc/steadybit/extensions.d/extension-*.yaml to configure the remote-located extensions

url: # replace with your host

Last updated