Holesail
holesail.io · Egress and tunnels · 1 record · JSON
Holesail Egress and tunnels
caveatanonymousno cardD
| Free tier | Holesail is the world's first truly peer-to-peer proxy for TCP and UDP ports. No port forwarding, servers or configuration required. unit unlimited; metered on none |
|---|---|
| Price | USD 0 |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | No allowance exists: the bytes travel between the two peers, and the public DHT only coordinates the holepunch.; ingress: tcp+udp free_allowance: none published |
| Identity | anonymous No account, email or card: the connection string is a public key derived from a keypair the client generates. |
| Limits |
|
| Binding | none Nothing meters the bytes, so at 1 TiB/month the limit is the peer's uplink and NAT behaviour, not a vendor counter. |
| Interface | cli npm i holesail -g; holesail --live 3000 prints an hs:// connection string. |
| Tooling | npm i holesail -g; holesail --live <port> then holesail <connection-string>. |
| Composes with | Carries a WireGuard handshake between a free VM and a laptop without opening a port on either, at the cost of installing a client on both ends. |
| Reliability | Depends on public HyperDHT bootstrap nodes; symmetric NAT defeats the holepunch and falls back to TCP, which breaks UDP-only protocols. |
| Notes | Not a hosted ingress: a third party cannot connect unless they run holesail with the connection string. It qualifies as free UDP capacity between two machines the client controls, which covers a WireGuard endpoint only if the far side also runs it. |
| Evidence rung | documented A measured transfer between two peers behind different NATs would show the real throughput and whether the DHT path holds; that is the missing rung. |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
| Parsed numbers |
|
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | github.com/holesail/holesail | Peer-to-peer proxy for TCP and UDP; npm install; connection string replaces a public address. |
| 2025-12-03 | news.ycombinator.com/item?id=46131627 | Launch post: no port forwarding, no VPNs, no servers in the middle, supports both UDP and TCP. |
| 2026-10-23 | news.ycombinator.com/item?id=46172495 | Mechanism: peers announce to HyperDHT, DHT nodes coordinate a UDP holepunch, then UDX carries the data; TCP fallback exists. |
More fields (7)
{
"wg_path": "inside-udp",
"wg_detail": "The transport after holepunching is UDX, a custom UDP protocol, with a TCP fallback. A WireGuard datagram can ride that path between two peers running holesail.",
"ingress": "tcp+udp",
"volume_tib_month": null,
"volume_stated": "No allowance exists: the bytes travel between the two peers, and the public DHT only coordinates the holepunch.",
"bytes_transit": "overlay-only",
"transit_note": "Bytes go peer to peer after holepunching; only coordination metadata crosses the public DHT."
}Unknown or withheld values (2)
$.per_object_cap.statednot-applicable$.retention.statednot-applicable