Single command to get a unique URL for anyone to connect from their laptops, mobile devices. Custom subdomains, endpoint authentication, SSL and content minification available.
Single ingress controller to route traffic to any namespace. Cloud agnostic. Define ingress resource once, run anywhere whether it is Google Cloud, Azure, AWS, Docker for Mac with Kubernetes support or Minikube. The only requirement is Internet connectivity.
Whether you need a one-way fan-out webhook delivery system or two-way traffic for your server, mobile app, IOT device or Kubernetes service - we have a solution, no public IP is required.
Test mobile apps against a development backend running on your machine. Point relay at your local development server and then configure your app to use the webrelay URL. It won't change, even when you change servers, networks or environments.
No need to constantly redeploy your work in-progress to get feedback from teammates or clients. Webrelay creates a public endpoint (http://yourapp.webrelay.io) bridging to a private (or local) webserver. Anyone can connect.
Use relay agent with Keel to receive Webhooks from DockerHub, Quay, Azure or any other registries to enable automated updates on image push. See this example for a step-by-step guide.
Runs anywhere. To expose your web server to the world, all you need is the Relay agent and access to the Internet. Because the tunnel to the Webhook Relay is established by an outbound TLS connection, it works through NAT environments (e.g. a home or office network) without having to configure port forwarding, or in cloud computing environments with ephemeral IP addresses.
Dynamically configure tunnels, input endpoints and outgoing destinations through UI, CLI, API or ingress controller at runtime as your environment changes.