The relay can’t redirect your agent.
Your local destination is fixed at startup. A remote message never gets to choose a new address.
Developer preview Localhost, with a way out
A public URL for
the server on your laptop.
PortWisp carries HTTP traffic through one encrypted outbound tunnel to a fixed service on your machine. No router changes. No mystery configuration.
$
curl -fsSL https://get.portwisp.com/install.sh | sh
$
portwisp http 3000
Install the client, point it at a local port, and share the generated URL.
ONLINEconnected 14m 08s
- Public
- https://quiet-fox.portwisp.com
- Local
- http://127.0.0.1:3000
128 requests2.4 MB out384 KB in
TIMEMETHODPATHSTATUSDURATION
12:41:09POST/webhooks/stripe20042ms
12:40:56GET/api/users/4220018ms
12:40:51GET/assets/app.css3047ms
12:40:47PUT/api/settings42231ms
How it works
One command.
One command.
One narrow path in.
- 01
Start locally
Point PortWisp at a loopback HTTP port or URL selected by you.
- 02
Connect outward
The agent opens an encrypted connection to the PortWisp relay.
- 03
Share the URL
Requests to your temporary hostname travel back through that tunnel.
Loopback means loopback.
PortWisp defaults to 127.0.0.1 and never silently opens a listener to your network.
A tunnel, not a data warehouse.
Request bodies are not stored or replayed. The early service is designed around temporary hostnames.
See what reaches your app.
A focused terminal interface shows request metadata, status, timing, and transfer totals.
Built for webhook debugging, demos, mobile testing, and the small moments when localhost needs an audience.
PortWisp is under active development.hello@portwisp.com →