Components

Snap CD is made up of three components:

• Server — the centralised service that hosts the Dashboard, Web API, MCP server, hubs for Runners and Agents, and the resource catalogue
• Runner — the self-hosted process that picks up Jobs from the Server and executes Terraform / OpenTofu / Pulumi commands against your infrastructure
• Agent — the self-hosted process that consumes Snap CD events and runs AI-driven Missions in response. Enterprise-tier only

Each page covers what the component does, what must exist for it to start, how it’s deployed, what settings it reads, how it behaves operationally, and where to look when something is wrong.

For the conceptual overview, see The Basics. For the resource catalogue (Stacks, Modules, Hooks, Secrets, Missions and so on) see Resources.