Tunnelr

We’re a custom CRM company, and a big part of our work involves webhooks, APIs, and integrations that deal with sensitive data. For a long time, we relied on tools like ngrok or Cloudflare Tunnel. They work well, but we kept running into the same constraint: clients were okay exposing webhooks to us, but not via third-party cloud services. Our workaround was to deploy everything directly on our own VPS and use those endpoints as webhook URLs. That solved the compliance problem, but it broke the developer experience. Developing and testing on localhost is still far faster and cleaner. So we built Tunnelr as an internal tool. Tunnelr lets you: 1.) run everything on your own VPS 2.) use your own domain 3.) keep all traffic on your own infrastructure 4.) choose between path-based or subdomain-based tunnels 5.) avoid timeouts, forced redirects, or external SaaS dependencies It started as a practical fix for our own workflow. We’re sharing it openly in case it helps others dealing with similar constraints. Happy to answer questions or hear feedback.