How does the webhook deployment runner authenticate GitHub or GitLab requests?

SSH Desktop validates the X-Hub-Signature-256 header using your shared secret and HMAC-SHA256 cryptography, rejecting unauthorized or forged webhook payloads before executing any deployment commands.

Can it trigger Docker Compose restarts and database migrations?

Yes. You can define sequential post-receive pipeline hooks (e.g., git pull, npm install, docker compose build, docker compose up -d) with real-time log streaming and rollback on non-zero exit codes.

🚀 CI/CD • Automated Deployment Engine

Webhook & CI/CD Deployment Server

Automate remote Linux deployments straight from GitHub, GitLab, or Bitbucket. Receive webhooks, verify HMAC-SHA256 signatures, stream live build logs, and trigger zero-downtime rollouts — without installing bloated CI agents.

📦 Download SSH Desktop Free Explore All 25 Apps

✓ HMAC-SHA256 Signature Security ✓ Zero CI Runner Memory Overhead ✓ Live Build Log Streaming ✓ Auto-Rollback on Failure

deploy.production — Webhook Receiver (Port 22 SSH Tunnel)

Listening ● 200 OK

🚀

api-service • push event (main branch)

Commit: 7c4a10e • author: sarah-dev • 2 minutes ago

Deployment Succeeded (2.4s)

[14:22:01] POST /webhooks/api-service -> 200 OK (HMAC-SHA256 verified)

[14:22:02] $ git pull origin main && docker compose up -d --build

[14:22:03] Container api-service-v3: recreated and healthy

[14:22:04] Deployment complete: 0 errors, zero downtime.

Automated DevOps

Zero-Downtime Deployments Made Simple

Trigger instant server rollouts from GitHub, GitLab, and Bitbucket with secure signature validation and automatic failure rollback.

🔒

HMAC-SHA256 Cryptography

Every incoming webhook payload is verified using your shared secret and SHA-256 HMAC digests, guarding your server against spoofed or unauthorized triggers.

🚀

Pipeline Post-Hooks

Chain sequential deployment commands: git pull, composer install, npm run build, and systemctl restart with custom exit-code error traps.

🔄

Auto-Rollback Protection

If a build fails or tests crash, SSH Desktop automatically rolls back the commit or restarts the previous container image, preventing production outages.

Frequently Asked Questions

Common questions regarding webhook automated deployment.

Do I need to keep my client app open to receive webhooks?

In client desktop mode, the webhook receiver operates through an encrypted reverse tunnel while your app is running. In CLI server mode, the lightweight standalone daemon runs continuously in the background on your server host.

Can I restrict webhooks by Git branch?

Yes. You can configure branch filters (e.g. only trigger on pushes to main or production, while ignoring feature branches).