GitHub
Meet WireRiftA small binary. A direct connection. Your infrastructure.InstallationNative binaries for your machine. No runtime to manage.Run your own serverThe public edge belongs to you.HTTP & WebSocket tunnelsShare web apps, receive webhooks, and keep WebSockets connected.TCP tunnelsA path for the protocols beyond HTTP.Security & accessLayer access controls around what you share.Traffic inspectorSee the request. Understand the response. Try it again.Under the wireOne connection. Many independent streams.Dashboard APIYour tunnels and traffic, programmatically.ConfigurationKeep your connections together in a readable config file.Docker deploymentGive your public edge a reproducible home.Local HTTPS developmentA trusted development edge, without a public domain.TroubleshootingGet back to a working connection.
Documentation, without the detour.ESC to close
Browse documentation
DOCUMENTATION / TUNNELS

HTTP & WebSocket tunnels

Share web apps, receive webhooks, and keep WebSockets connected.

Expose a local HTTP service

Pass your local port and optionally a subdomain. WireRift forwards public requests to that local service.

terminal
wirerift http 3000 myapp --server tunnel.example.com:4443 --token YOUR_TOKEN

WebSockets come along

HTTP upgrade requests pass through the tunnel, so local WebSocket applications can keep their full-duplex connections. No separate WebSocket tunnel command is required.

See the conversation

Add --inspect to capture request and response details. The dashboard exposes methods, paths, status codes, duration, headers and JSON bodies.

terminal
wirerift http 3000 myapp --inspect \
  --server tunnel.example.com:4443 --token YOUR_TOKEN

Share a static directory

Serve files directly through a tunnel without starting another local web server.

terminal
wirerift serve ./dist --server tunnel.example.com:4443 --token YOUR_TOKEN

Based on the upstream WireRift reference . Check the source for the latest options.

PreviousRun your own serverUp nextTCP tunnels