Deployment Payload

A Deployment Payload is a tool that ResorsIT installs onto a desktop or a server, rather than integrating as a web app. The platform’s deployer ships it as a packaging artefact matched to the target host – for example an rpm or deb Linux package, a Windows installer, a Homebrew formula, a desktop bundle, or a container / Kubernetes payload.

How ResorsIT integrates it

• The deployer places the software on a managed host and keeps it current
• The tool runs where it is installed (agent, desktop app, CLI, or service)
• Any identity or configuration is handled by the tool’s own mechanisms – though a tool that keys off the logged-in OS user is reached through a governed local host account

Precedence: only when the web modes do not apply

Some tools are both a web app and installable. Those are labelled by their web mode – Web App with SSO or Web App without SSO – because that is the primary way ResorsIT would adopt them. A tool is labelled Deployment Payload only when the web modes do not apply: command-line tools, desktop applications, agents, and background services that live on a host rather than being reached in a browser.

Operating systems and hardware are not payloads in this sense – see Device Class. Code libraries are Library.