Explorme Tunnel
A self-hostable ngrok alternative for exposing localhost
Open Explorme TunnelWhat it does
Explorme Tunnel lets you expose a local development server to a public URL so you can test webhooks, share work-in-progress with clients, or connect external services to your local environment. It uses a CLI to establish a WebSocket-based tunnel between your machine and a tunnel server, which forwards incoming requests to your local port. Features include token-based authentication, a dashboard for managing active tunnels, and usage limits to prevent abuse. The server component is self-hostable, so you can run it on your own infrastructure.
Who it is for
Explorme Tunnel is built for developers who need to expose local servers during development and testing. It is useful for testing webhook integrations, demonstrating local projects to clients, running local API servers that need public access, and developing against services that require a public callback URL.
Main features
CLI Tunnel Client
Start a tunnel from your terminal with a single command and get a public URL for your local port.
WebSocket Transport
Tunnels use WebSocket connections for reliable, firewall-friendly transport.
Authentication
Protect tunnels with token-based authentication to prevent unauthorized access.
Dashboard
View and manage active tunnels, monitor usage, and review request logs from a web dashboard.
Usage Limits
Configure rate limits and connection limits to keep tunnels stable and prevent abuse.
Self-Hostable
Run the tunnel server on your own infrastructure for full control over data and access.
Privacy notes
Explorme Tunnel is a developer tool, not a consumer product. Traffic flowing through a tunnel passes through the tunnel server you configure. When self-hosted, you control the server and all data that passes through it. When using a hosted instance, review the provider data handling practices. Always use authentication on tunnels exposed to the public internet.
Common use cases
- Testing a Stripe webhook integration against a local server
- Sharing a local development preview with a client or teammate
- Running a local API server that needs a public callback URL
- Connecting a mobile app to a local backend during development
- Testing OAuth callback flows that require a public redirect URI