Key Facts
- ✓ Pipenet is a new open-source tunneling tool written in TypeScript that serves as a modern alternative to localtunnel.
- ✓ The tool solves a critical port allocation issue where localtunnel requires random ports per client, which fails on platforms like Fly.io or behind strict firewalls.
- ✓ Pipenet features multiplexing over a single port, allowing it to function in restrictive network environments that block arbitrary port access.
- ✓ The project is fully self-hostable and also offers a public instance at *.pipenet.dev for developers who prefer not to manage their own server.
- ✓ Originally built at Glama to support their MCP Inspector, Pipenet is a generic tunneling solution with no dependencies on its creator's infrastructure.
- ✓ The software is available as open-source on GitHub under the punkpeye organization, allowing for community contributions and customization.
Quick Summary
A new open-source tunneling solution has emerged to address specific compatibility issues with modern deployment platforms. The tool, named Pipenet, was developed as a TypeScript rewrite of existing tunneling software to overcome port allocation limitations.
Traditional tunneling tools often require random ports per client, a requirement that conflicts with the architecture of platforms like Fly.io and networks with strict firewall policies. Pipenet solves this by implementing multiplexing over a single port, ensuring functionality across diverse hosting environments.
While originally built to support the MCP Inspector at Glama, the project is a generic tunneling solution with no dependencies on its creator's infrastructure. It offers developers full control through self-hosting or the convenience of a public instance.
The Port Allocation Problem
Many developers rely on tunneling services to expose local development servers to the public internet for testing and sharing. However, a fundamental architectural choice in some popular tools creates significant barriers in modern cloud environments.
The core issue lies in how the server handles client connections. Localtunnel, a widely used tool, requires its server to allocate a random port for each connecting client. While this works in open network environments, it becomes problematic when deployed on platforms with restricted networking capabilities.
Platforms like Fly.io and networks behind strict firewalls often do not support arbitrary port allocation. This limitation prevents the tunneling server from functioning correctly, blocking developers from using these essential tools in their preferred hosting environments.
The constraints created by this port requirement led to the search for a more flexible alternative that could operate within the networking boundaries of contemporary cloud infrastructure.
A TypeScript Solution
To address these networking challenges, the development team at Glama created Pipenet from the ground up. The project was rewritten in TypeScript, bringing modern language features and type safety to the tunneling infrastructure.
The defining technical feature of Pipenet is its ability to perform multiplexing over a single port. Instead of requiring a range of random ports for different clients, all connections are funneled through one port. This approach maintains full functionality while remaining compatible with restrictive network configurations.
Key architectural decisions include:
- Single-port multiplexing for all client connections
- TypeScript implementation for robust codebase
- Generic design with no vendor lock-in
- Open-source availability under a permissive license
Despite its origin as a tool to support the MCP Inspector, Pipenet was designed as a standalone, generic tunneling solution. It operates independently of Glama's infrastructure, making it suitable for any development workflow.
Deployment Flexibility
Pipenet offers two distinct deployment paths to accommodate different user needs and technical requirements. The first option is self-hosting, which provides complete control over the tunneling infrastructure.
For developers who prefer not to manage their own server, a public instance is available at *.pipenet.dev. This hosted option allows immediate use without setup, though self-hosting remains the recommended path for production environments or those with specific security requirements.
The open-source nature of the project ensures transparency and allows for customization. Developers can inspect the codebase, contribute improvements, or modify the software to fit specialized use cases.
By being fully self-hostable, Pipenet empowers organizations to maintain their own tunneling infrastructure, keeping data and traffic within their controlled environments while avoiding the port allocation limitations of other services.
Availability & Access
The Pipenet project is publicly available on GitHub, hosted under the punkpeye organization. The repository contains the complete source code, documentation, and setup instructions for both self-hosting and using the public instance.
Developers interested in exploring the codebase or contributing to the project can access it directly through the GitHub repository. The project welcomes community engagement and contributions to enhance its functionality and reach.
For those looking to implement a tunneling solution in their development workflow, Pipenet represents a modern alternative specifically engineered for the constraints of today's cloud hosting platforms.
Looking Ahead
Pipenet addresses a specific but critical gap in the developer tooling landscape. By solving the port allocation problem that plagues traditional tunneling services on platforms like Fly.io, it enables smoother development workflows in modern cloud environments.
The combination of single-port multiplexing, TypeScript implementation, and open-source availability positions Pipenet as a valuable tool for developers facing strict network policies. Its generic design ensures it can serve a wide range of use cases beyond its original purpose at Glama.
As cloud platforms continue to evolve with stricter networking rules, tools like Pipenet that adapt to these constraints will become increasingly essential for development teams seeking reliable local-to-public tunneling capabilities.









