Pipenet: Self-hostable tunneling service with multiplexing over single port

What it does

Pipenet is an open-source tunneling service that exposes local servers to the internet. It multiplexes traffic over a single port, solving a constraint that affects localtunnel users behind strict firewalls or on platforms like Fly.io that do not allow random port assignment. The tool works in two modes: as a client that connects a local service, or as a server that operators self-host. It supports HTTP, HTTPS, WebSocket, Server-Sent Events, and HTTP streaming protocols.

Who it is for

Developers who need to share local servers during development, test webhooks, or demo applications without deploying to production. Teams embedded in restrictive network environments benefit from the single-port design. Organizations that require full control over tunnel infrastructure—security, domains, and uptime—can self-host their own instance. The tool also serves as a building block for teams integrating tunneling into their own applications, as shown by its use in mcp-proxy to connect local MCP servers with remote AI clients.

Pricing

The site does not show prices. A public instance is available at *.pipenet.dev for free use without self-hosting.

How it stands out

Pipenet's core differentiator is single-port multiplexing, which allows deployment in environments where per-client random ports are not feasible. The codebase is written in TypeScript and uses ES modules, marking it as more modern than localtunnel. The project is actively maintained and offers both a managed public server and complete self-hosting flexibility. Client and server ship in one package, reducing deployment friction. The tool supports programmatic usage via a JavaScript API for testing and automation.

What a founder should check

First, validate how many users rely on random-port workarounds or face deployment blockers that localtunnel cannot solve. The addressable market depends on the prevalence of these constraints in the wild. Second, examine switching costs: localtunnel users with existing scripts and workflows may hesitate to migrate if the commands differ significantly or require retraining. Third, understand the moat. Localtunnel's limited maintenance creates an opening, but a well-funded competitor entering with a managed service, better uptime guarantees, or enterprise features could pressure both pricing and adoption.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.