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 / START HERE

Meet WireRift

A small binary. A direct connection. Your infrastructure.

Local development, without the walls

WireRift connects a local service to a server you operate. The server receives public HTTP or TCP traffic and sends it through a multiplexed connection to your machine. Your application keeps running exactly where it is.

What you need

A local application, the WireRift client, and a reachable WireRift server. For public HTTPS, use a domain you control and configure DNS to point at your server. You do not need Go installed when using prebuilt binaries.

Your first tunnel

Once your server is running, point the client at its control address and authenticate with the same token. In this example the local app listens on port 3000.

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

Replace tunnel.example.com and YOUR_TOKEN with your own server and token. Public URLs throughout these docs are examples, not a shared hosted tunnel service.

Make the connection yours

Use HTTP tunnels for web apps and webhooks, TCP tunnels for databases and other raw protocols, and the built-in dashboard to inspect requests. Start with the installation guide, then follow the server setup.