- Use Case
- Log in →
- Security & Tech
- Webhook Forwarding
- Functions (transform)
- Exec Commands
- WebSocket Server
- HTTP Tunnels
- TLS Tunnels
- Global Infrastructure
- Ingress Controller (Tunnels)
- Webhook Relay Operator (Forwarding)
Internet of Things
- Home Automation
- Internet of Things (IoT)
- CLI commands
- Proxy Configuration
- Self-hosted deployment
- Client configuration
Webhook Relay is a fast, reliable and secure tunneling service.
For web developers:
- Forward webhooks to your local machine during development. For example Stripe, Github, Slack integrations.
- Forward webhooks to internal network machines.
- Skip deployments to public servers and just demo your websites from your development machine.
- Connect to low-traffic services through tunnels instead of getting public IP and domains (for example internal Grafana, Prometheus instances)
For hackers and home automation enthusiasts:
- Make your Raspberry Pi, a laptop or even smartphones servers.
- Expose your Home Assistant, Node-RED or other automation solutions to the internet without router configuration.
- Protect your privacy. With TLS pass-through tunnels, not even Webhook Relay could be forced to spy on your traffic.
For system administrators, DevOps engineers and SREs:
- Receive & process webhooks on your Jenkins CI server without exposing it to the internet.
- Host Drone.io server from anywhere in your infrastructure and let agents connect to it over the tunnels.
- Use our Kubernetes ingress controller to quickly, on-demand establish tunnels to mission-critical services for debugging or testing.
How does it work?
This services works by creating a reverse tunnels for one-way or bidirectional data transfer to internal services. Webhook Relay is designed to be easy-to-start-with and remain flexible enough for advanced use cases. Webhook Relay is perfectly capable of powering sophisticated use cases where performance and dynamic routing configuration is required.
- Q: How is this different from a regular NGINX ingress?
A: Regular NGINX or other ingress controllers require an external service/load balancer to point at them while Web Relay ingress controller doesn’t need any of that. A reverse tunnel is created from inside of your environment.
- Q: Why do I have to pre-create tunnels when I am on a free plan?
A: Since free plan does not have custom subdomain names (where you choose your own host), ingress controller will not be able to create specified tunnels. Therefore, you need to create a tunnel first and once you know your randomly generated host, you can add it to the ingress resource file.
- Q: I want to use it with TCP based services (SSH, etc). How can I achieve this?
A: At the moment underlying
relaydtunneling agent only supports HTTP protocol. Support for TCP exists but it has not been released. Furthermore, ingress resources can only define HTTP services and are not meant for any other purpose.
- Q: Can I have my own custom domain name?
A: Yes, you can have custom domains for your tunnels. Functionality for custom incoming webhook domains will be enabled in near future.