Home / Egress and tunnels
Pipenet
pipenet.dev/HTTP tunnelegress/pipenetJSONcomparereport an errorprovider JSON
- Free allowance
- Open-source and 100% self-hostable.
- Verdict
- fails: egressdata cannot be read back out at a usable rate or price
- Cost
- not statedsee Price below
- Identity
- anonymousno card, no phone
- Binding limit
- request-ratemaxTcpSockets per client defaults to 10
- Evidence
- documented2 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| 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 |
|---|
| Limits | - request-rate (binding) 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. |
|---|
| Identity | anonymous No account is described: the public instance is a hostname you point a client at. The README shows no signup. |
|---|
| Egress | No allowance is published for the public instance.; ingress: http-only free allowance: none published |
|---|
| 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 note | 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. |
|---|
| Parsed numbers | |
|---|
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 6
| 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. |
|---|
| ingress | http-only |
|---|
| 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 values 2
- per object cap stated: the field does not apply to this kind of offer
- retention stated: the field does not apply to this kind of offer