Skip to main content
Live. This area is documented as current, user-reliable behavior.

​
Goal

Install the agent cleanly and know how to verify success on the host itself.

​
Prerequisites

  • A Linux host
  • SSH access
  • Dashboard access

​
Workflow

1
Generate the install command from the dashboard.
2
Run it on the target host.
3
Verify the service status and the node heartbeat in the dashboard.

​
Install paths that exist today

  • Manual install command generation from the dashboard
  • SSH-assisted install flow from the node page
  • Direct download paths for amd64 and arm64 agent binaries from the control plane

​
What the install does

The install command uses a short-lived install token to register the host with the control plane and start the agent as a service. The agent is what runs your containers and the Caddy ingress on that host and reports heartbeats back to StackShift.

​
Verifying the install

  • Check the agent service is running on the host.
  • Confirm the node appears with a fresh heartbeat and a healthy status in the dashboard.
  • Only place workloads once the node reports healthy.

​
Expected result

The node is attached and the agent is running.

Node overview

What a node is, what the agent does, and what node health means in StackShift.

Upgrade the agent

Use the maintenance-first path to move an existing node to a newer agent version.

Node health, diagnostics, and deletion

Read node diagnostics correctly and understand when deletion is safe or blocked.