An open-source tool that creates public URLs for locally running HTTP(s) servers, enabling internet-wide access for testing and sharing.
Tunnelmole is an open-source tool that creates public URLs for locally running HTTP(s) servers, enabling developers to expose local applications to the internet. It solves the problem of testing webhooks, sharing work with collaborators, and debugging across devices without deploying to a staging environment. By tunneling traffic from a public domain to localhost, it simplifies development workflows.
Developers and teams working on web applications, APIs, or Docker containers who need to test locally with real internet traffic, debug webhooks, or share progress with clients or colleagues remotely.
Developers choose Tunnelmole because it's a free, open-source alternative to proprietary tools like ngrok, with easy installation via npm or binaries. It offers HTTPS URLs by default, supports custom subdomains, and can be integrated programmatically into Node.js projects for automation.
Tunnelmole - Connect to local servers from anywhere
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides a free, transparent option compared to proprietary tools like ngrok, with full source code available for self-hosting, as highlighted in the README's comparison and self-hosting links.
Supports installation via npm for Node.js 16.10+ or pre-built binaries for Linux, Mac, and Windows, making it accessible across platforms with simple copy-paste commands.
Can be used as a Node.js dependency for automation in NPM scripts or code, with examples in the README for both ES and CommonJS modules, enabling seamless workflow integration.
Generates public URLs with HTTPS automatically for secure connections, essential for testing webhooks and HTTPS-only features like PWAs, as shown in the demo output.
Custom subdomains require a subscription on the hosted service, which adds cost and complexity compared to free alternatives, and self-hosting involves setting up a separate service repo.
Telemetry is enabled by default and must be manually disabled via environment variables, which could be a privacy concern and requires extra configuration steps, as admitted in the README.
The npm installation requires Node 16.10 or later, forcing users with older versions to rely on binaries, which might not be ideal for all environments and adds setup friction.