Hooklayer vs RelayHQ

Hooklayer has no write-up on Specifiction yet; its figures are above.

RelayHQ receives provider webhooks, queues them, and delivers them to configured services with routing rules, retries, and request logs. Permanent inbound URLs can fan requests out to multiple destinations. Rules can filter by JSON payload path or HTTP header and combine conditions with AND or OR. Failed deliveries can be retried up to five times with exponential backoff, and requests can be replayed manually from the dashboard. The site names Stripe, GitHub, and Shopify as webhook sources.

The service documents a REST API that accepts bearer API keys or a valid session cookie. Its Free plan includes a CLI local tunnel for development. RelayHQ says setup can be completed in under five minutes without managing infrastructure or configuring message brokers. The service runs on cloud infrastructure in US East (IAD). The privacy policy says traffic uses TLS 1.2 or higher, API keys are hashed before storage, and passwords use bcrypt. The maker says it does not sell personal information or use webhook payloads beyond delivery to configured destinations. The Free plan allows three endpoints and 500 requests monthly; paid plans start at $23/mo (annual).