tunnl review
Self-hosted webhook tunnels with durable history, replay, inspection and response diffs.
Reviewed by iTechGuides Editors · Editorial team · Updated Nov 2026
For teams developing and debugging webhooks against local applications, tunnl provides a self-hosted reverse tunnel with persistent request history. Its CLI connects local services to a server you operate, while PostgreSQL stores incoming headers and bodies. A terminal inspector and web dashboard expose live and historical traffic, making the product suited to small, mid-market and enterprise teams that want control over deployment and data. The project is open source under the MIT license and includes an MCP server for AI coding agents.
The standout capability is replayable history. Captured requests can be replayed with their original signature headers, then compared through response diffing to show how behavior changed. Curl export turns a captured request into a portable command. The category specification lists request inspection, payload replay, forwarding tunnels and 30-day retention. MCP tools add request querying and replay for compatible coding-agent workflows. Listed integrations include Stripe, GitHub, Slack and Shopify, giving webhook-heavy teams familiar endpoints to exercise.
Operating tunnl means managing the supplied Docker Compose deployment alongside Caddy and PostgreSQL, plus maintaining the server infrastructure yourself. That model can fit organizations requiring self-hosted control, but teams seeking a vendor-operated service or a simpler hosted onboarding path should consider alternatives. Linux and macOS are the published CLI platforms, so platform fit should be checked before adoption. Choose tunnl when durable local-development history, replay fidelity and inspection depth matter more than managed operations; avoid it when your priority is outsourced hosting and minimal infrastructure responsibility.
tunnl pros and cons
- Where it wins
- Persistent PostgreSQL history supports replay and request auditing.
- Terminal, web dashboard and MCP interfaces cover varied workflows.
- Response diffs and original-header replay aid webhook debugging.
- Where it doesn't
- Deployment requires your team to operate Docker Compose, Caddy and PostgreSQL.
- CLI platform coverage is limited to Linux and macOS.
- Self-hosting puts upgrades, availability and infrastructure care on your team.
tunnl fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update