Deliver webhooks to automation services without public IP or domain

Automation tools like Jenkins, GoCD or Drone heavily rely on webhooks. Most of the time these services are used internally and there is no need to expose them to the internet. What is more, exposing them to the public is a security risk.
Webhook Relay allows you to securely deliver webhooks to internal services. See a blog post for a step-by-step guide on how to receive webhooks on Jenkins through a Webhook Relay agent.

Fan-out webhooks to multiple services at once

Most providers allow you to specify only one endpoint for outgoing webhooks. While it does make sense from the provider's perspective, quite often you need to receive those webhooks in multiple services or just different environments (production, staging or development). Webhook Relay allows you to specify multiple destinations for each incoming webhook. It works for both public and private endpoints.

Easy access to Kubernetes services on-demand, no external loadbalancer configuration required

Need an access to Prometheus, Grafana or just debug some service?
Relay ingress controller can be deployed in seconds and will provide you a tunnel to any service in your cluster with a custom subdomain. Ingress controller tunnels can have basic or token auth and HTTPS.

SEE EXAMPLE

Lightweight container, can be used as a sidecar

Need a lightweight solution to receive webhooks on Kubernetes? Webhook Relay agent can be deployed as a sidecar container to your application. All traffic is encrypted end-to-end. Typical memory usage is just ~10-15MB RAM.

Ready to sign up? Free plan available.

SIGN UP