---
title: "Deploy HonorBox Webhook Relay"
description: "Signed Stripe webhook relay for instant HonorBox GitHub fulfillment."
category: "Automation"
url: https://railway.com/deploy/honorbox-webhook-relay
---

# Deploy HonorBox Webhook Relay

Signed Stripe webhook relay for instant HonorBox GitHub fulfillment.

**[Deploy HonorBox Webhook Relay on Railway](https://railway.com/template/honorbox-webhook-relay)**

- **Creator:** Tom
- **Category:** Automation

## Template content

### HonorBox Relay https://raw.githubusercontent.com/Honorboxx/honorbox/v0.5.1/assets/logo.svg

- **Source:** https://github.com/monotykamary/railway-template-honorbox-relay
- **Health check:** /health
- **Public domain:** Yes

## Documentation

# Deploy and Host the HonorBox Webhook Relay on Railway

The HonorBox Webhook Relay turns successful Stripe Checkout events into immediate GitHub `repository_dispatch` events for an HonorBox private operations repository. It is the optional low-latency companion to HonorBox's default scheduled fulfillment poll.

## About Hosting the HonorBox Webhook Relay

This template packages the HonorBox v0.6.0 relay. The relay verifies Stripe's webhook signature with a five-minute replay window before contacting GitHub. It rejects request bodies over 1 MiB with HTTP `413`. It forwards no buyer identity, email, amount, or raw Checkout Session ID. GitHub receives only the event type, mode, creation timestamp, and a short hash reference. If GitHub refuses the dispatch, the relay returns `502` so Stripe retries automatically.

This template deploys the relay only. Your storefront and fulfillment workflow remain in GitHub, exactly as HonorBox's architecture requires. Keep the scheduled poll enabled as a safety net.

## Common Use Cases

- Deliver private GitHub repository products within seconds of Stripe payment
- Add signed webhook validation without operating a general-purpose server
- Preserve HonorBox's polling fallback while reducing normal delivery latency

## Dependencies for HonorBox Webhook Relay Hosting

- An HonorBox private ops repository with `fulfill-on-sale.yml`
- A Stripe webhook endpoint signing secret
- A fine-grained GitHub token restricted to the ops repository
- Stripe events `checkout.session.completed` and `checkout.session.async_payment_succeeded`

### Deployment Dependencies

- [HonorBox](https://github.com/Honorboxx/honorbox)
- [HonorBox v0.6.0 webhook mode documentation](https://github.com/Honorboxx/honorbox/tree/v0.6.0/webhook-mode)
- [HonorBox v0.6.0 MIT License](https://github.com/Honorboxx/honorbox/blob/v0.6.0/LICENSE)

### Why Deploy the HonorBox Webhook Relay on Railway?

Railway supplies HTTPS, secret variables, health checks, logs, and automatic restarts for the small dependency-free Node relay. No database or persistent volume is required.


## Similar templates

- [N8N Main + Worker](https://railway.com/deploy/n8n-main-worker) — Deploy and Host N8N with Inactive worker.
- [Evolution API with n8n](https://railway.com/deploy/evolution-api-with-n8n) — [Jul'26] WhatsApp automation platform using Evolution API, n8n & PostgreSQL
- [Postgres Backup](https://railway.com/deploy/postgres-s3-backups) — Cron-based PostgreSQL backup to bucket storage

Open this page in a browser: https://railway.com/deploy/honorbox-webhook-relay
