Pipenet

pipenet.dev · Egress and tunnels · 1 record · JSON

Pipenet Egress and tunnels

fails: egressanonymousno cardDrequest-rate

pipenet.dev/ · http tunnel · egress/pipenet · JSON · compare

Free tier	Open-source and 100% self-hostable. Public instance at *.pipenet.dev if you don't want to self-host. unit none; metered on unstated
Price	USD 0
Per-object cap	not applicable
Retention	not applicable
Egress	No allowance is published for the public instance.; ingress: http-only free_allowance: none published
Identity	anonymous No account is described: the public instance is a hostname you point a client at. The README shows no signup.
Limits	request-rate maxTcpSockets per client defaults to 10 source
Binding	request-rate The only published control is a socket cap per client, so concurrency fails long before any byte allowance would. The transport is also HTTP-only, so a UDP datagram has no path at all.
Interface	cli, rest Node client plus a REST status API at /api/status.
Tooling	npm client; self-hostable Node server.
Composes with	Only useful as an HTTP ingress for an MCP or webhook endpoint.
Reliability	Public instance is a courtesy run by the maintainer with no stated capacity or SLA.
Notes	Launched 2026-01-19. A localtunnel rewrite with multiplexing over one port, built for an MCP inspector. It is a software project with a courtesy public instance, not a capacity provider.
Evidence rung	documented A measured run against the public instance would show whether it is still up and what it rate-limits; the UDP question is already answered by the maintainer.
Checked	2026-10-23 (live); stale on 2026-11-22
Parsed numbers	`$.price_per_tb_month` price-per-tb USD0.0 TB / month

Evidence (2)

date	source	what it proved
2026-10-23	pipenet.dev/	Server options include maxTcpSockets default 10 and tunnelPort; the API is an HTTP tunnel server, no UDP or raw port.
2026-01-19	news.ycombinator.com/item?id=46680597	Launch post and maintainer reply that the implementation is HTTP-focused and UDP support is not planned.

More fields (7)

{
 "wg_path": "none",
 "wg_detail": "HTTP-focused by the maintainer's own answer: The current implementation is HTTP-focused as that was the primary use case. TCP tunneling is possible architecturally but not something I've had in mind.",
 "ingress": "http-only",
 "volume_tib_month": null,
 "volume_stated": "No allowance is published for the public instance.",
 "bytes_transit": "yes",
 "transit_note": "The pipenet.dev instance relays HTTP requests to the local client."
}

Unknown or withheld values (2)

$.per_object_cap.stated not-applicable
$.retention.stated not-applicable