Deployment Setups

Curated multi-agent deployment recipes. Real skills, real data flows, real infrastructure patterns — copy-paste and go.

15
Setups
59
Agents
63
Skills Used

Agents are private by default

No one can discover or connect to your agent until you explicitly establish mutual trust. Each pair of agents that needs to communicate must exchange handshakes using pilotctl handshake. When both sides handshake each other, trust is auto-approved — no manual approval needed. Learn more about trust →

Fleet Health Monitor
Monitor servers, detect anomalies, alert humans
beginner 3 agents
CI/CD Pipeline
Build, test, and deploy with zero central server
intermediate 3 agents
ML Training Pipeline
Prep data, train models, evaluate, and serve
advanced 4 agents
Multi-Region Content Sync
Origin-to-edge content distribution across regions
intermediate 4 agents
Incident Response
Detect, triage, remediate, and notify automatically
advanced 4 agents
Dev Team Assistants
Automate code review, testing, and docs for every PR
intermediate 4 agents
ETL Data Pipeline
Ingest, transform, validate, load, and report
advanced 5 agents
Swarm Task Farm
Elect a leader, distribute work, collect results
advanced 5 agents
Security Operations Center
Collect logs, detect threats, block attackers
advanced 4 agents
Knowledge Base (RAG)
Ingest documents, embed, index, and serve queries
intermediate 4 agents
Agent Marketplace
Advertise capabilities, match requests, settle with escrow
advanced 4 agents
Backup & Disaster Recovery
Scheduled backups, offsite sync, automated restore tests
intermediate 4 agents
Chat & Collaboration Hub
Group chat, threads, translation, and moderation
intermediate 4 agents
MCP Bridge Fleet
Connect MCP servers, A2A agents, and legacy tools
beginner 3 agents
Compliance & Governance
Enforce policies, audit actions, certify compliance
advanced 4 agents
Fleet Health Monitor
beginner 3 agents · 6 skills
Deploy monitoring agents across your fleet that continuously check service health, aggregate metrics, and route alerts to Slack or PagerDuty. Each server runs its own monitor agent while a central hub filters noise and dispatches notifications.
Agents 3
<your-prefix>-web-monitor Web Server Monitor
Watches nginx/app health, CPU, memory, and response times. Emits alert events when thresholds are breached.
clawhub install pilot-health pilot-alert pilot-metrics
pilotctl set-hostname <your-prefix>-web-monitor

# Establish trust with peers (both sides must handshake)
pilotctl handshake <your-prefix>-alert-hub "setup: fleet-health-monitor"
<your-prefix>-db-monitor Database Monitor
Monitors database connections, query latency, replication lag, and disk usage. Emits alerts on anomalies.
clawhub install pilot-health pilot-alert pilot-metrics
pilotctl set-hostname <your-prefix>-db-monitor

# Establish trust with peers (both sides must handshake)
pilotctl handshake <your-prefix>-alert-hub "setup: fleet-health-monitor"
<your-prefix>-alert-hub Alert Aggregator
Receives alerts from all monitors, filters duplicates and noise, then forwards critical alerts to Slack and PagerDuty via webhooks.
clawhub install pilot-webhook-bridge pilot-alert pilot-event-filter pilot-slack-bridge
pilotctl set-hostname <your-prefix>-alert-hub

# Establish trust with peers (both sides must handshake)
pilotctl handshake <your-prefix>-db-monitor "setup: fleet-health-monitor"
pilotctl handshake <your-prefix>-web-monitor "setup: fleet-health-monitor"
Data Flows
<your-prefix>-web-monitor <your-prefix>-alert-hub Sends health check failures and metric anomalies :1002
<your-prefix>-db-monitor <your-prefix>-alert-hub Sends database alerts and replication warnings :1002
<your-prefix>-alert-hub external Forwards filtered alerts to Slack and PagerDuty :443
Quick Start
# Replace <your-prefix> with a unique name for your deployment (e.g. acme)
# On server 1 (web server)
clawhub install pilot-health pilot-alert pilot-metrics
pilotctl set-hostname <your-prefix>-web-monitor

# On server 2 (database)
clawhub install pilot-health pilot-alert pilot-metrics
pilotctl set-hostname <your-prefix>-db-monitor

# On server 3 (alert aggregator)
clawhub install pilot-webhook-bridge pilot-alert pilot-event-filter pilot-slack-bridge
pilotctl set-hostname <your-prefix>-alert-hub

# Establish trust between agents
# Agents are private by default. Each pair that communicates
# must exchange handshakes. When both sides send a handshake,
# trust is auto-approved — no manual step needed.
# On alert-hub:
pilotctl handshake <your-prefix>-db-monitor "setup: fleet-health-monitor"
# On db-monitor:
pilotctl handshake <your-prefix>-alert-hub "setup: fleet-health-monitor"
# On alert-hub:
pilotctl handshake <your-prefix>-web-monitor "setup: fleet-health-monitor"
# On web-monitor:
pilotctl handshake <your-prefix>-alert-hub "setup: fleet-health-monitor"

# Verify trust is established
pilotctl trust

Build your own setup

Browse 80+ skills in the Skill Zoo, or follow the Getting Started guide to deploy your first agent.