<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Vojislav Mihailovic</title>
    <description>The latest articles on Forem by Vojislav Mihailovic (@taskobit).</description>
    <link>https://forem.com/taskobit</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3818737%2F9b841ffa-a272-47bc-b25b-b10cebad8cb9.png</url>
      <title>Forem: Vojislav Mihailovic</title>
      <link>https://forem.com/taskobit</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/taskobit"/>
    <language>en</language>
    <item>
      <title>Why I built a self-hosted alternative to webhook.site</title>
      <dc:creator>Vojislav Mihailovic</dc:creator>
      <pubDate>Wed, 11 Mar 2026 16:31:40 +0000</pubDate>
      <link>https://forem.com/taskobit/why-i-built-a-self-hosted-alternative-to-webhooksite-e9o</link>
      <guid>https://forem.com/taskobit/why-i-built-a-self-hosted-alternative-to-webhooksite-e9o</guid>
      <description>&lt;p&gt;If you've ever developed a webhook integration, you've probably used webhook.site. &lt;br&gt;
It's convenient — paste the URL, fire your event, inspect the payload. Done.&lt;/p&gt;

&lt;p&gt;But then I started working on a Stripe integration and realized something uncomfortable: &lt;br&gt;
I was sending live payment event data to a third-party server I know nothing about.&lt;/p&gt;

&lt;p&gt;So I built HookDash.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem with cloud webhook tools
&lt;/h2&gt;

&lt;p&gt;Tools like webhook.site are great for quick tests, but they have real limitations:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Your sensitive payloads go through someone else's server&lt;/strong&gt; — Stripe events, 
GitHub push hooks, internal API callbacks&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Monthly fees&lt;/strong&gt; — $9 to $29/month for features that should be basic&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Request history disappears&lt;/strong&gt; — close the tab, lose everything&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No multi-user support&lt;/strong&gt; on free plans&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Zero control&lt;/strong&gt; over data retention&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For hobby projects this is fine. For anything with real user data, it's a problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I built
&lt;/h2&gt;

&lt;p&gt;HookDash is a self-hosted webhook inspector you deploy on your own server. &lt;/p&gt;

&lt;p&gt;Here's how it works:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Create a named endpoint in the dashboard&lt;/li&gt;
&lt;li&gt;Point any service (Stripe, GitHub, Shopify) at your unique URL&lt;/li&gt;
&lt;li&gt;Watch requests stream in live&lt;/li&gt;
&lt;li&gt;Inspect headers, body, and query params in a collapsible JSON tree&lt;/li&gt;
&lt;li&gt;Replay any request with a single click&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Everything runs on your infrastructure. Your data never leaves your server.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tech stack
&lt;/h2&gt;

&lt;p&gt;I built it with tools I already use daily:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Laravel 12&lt;/strong&gt; — backend, routing, queue jobs&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;React 19 + Inertia.js v2&lt;/strong&gt; — frontend without the API overhead&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;shadcn/ui&lt;/strong&gt; — clean, accessible components&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Laravel Reverb&lt;/strong&gt; — WebSockets for real-time request streaming&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;MySQL 8&lt;/strong&gt; — persistent request history&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Laravel Fortify&lt;/strong&gt; — authentication out of the box&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The real-time part was the most interesting challenge. Laravel Reverb made WebSocket &lt;br&gt;
broadcasting surprisingly straightforward — each incoming webhook fires a broadcast &lt;br&gt;
event that the React frontend picks up instantly via Echo.&lt;/p&gt;

&lt;h2&gt;
  
  
  The replay feature
&lt;/h2&gt;

&lt;p&gt;My favorite feature is one-click replay.&lt;/p&gt;

&lt;p&gt;During development you often need to re-trigger a webhook handler — maybe you fixed a &lt;br&gt;
bug, or you want to test a different code path. Normally you'd have to go back to Stripe &lt;br&gt;
dashboard, find the event, and manually resend it.&lt;/p&gt;

&lt;p&gt;With HookDash you just hit replay. The original request — headers, body, everything — &lt;br&gt;
gets re-sent to your handler instantly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;Live demo: &lt;strong&gt;&lt;a href="https://demo.hookdash.io" rel="noopener noreferrer"&gt;https://demo.hookdash.io&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No signup needed, just click around and fire some requests at the demo endpoint.&lt;/p&gt;

&lt;p&gt;I'd love feedback — especially if you have feature requests or things that feel off in &lt;br&gt;
the UX. What would make this more useful for your workflow?&lt;/p&gt;

</description>
      <category>laravel</category>
      <category>webdev</category>
      <category>php</category>
      <category>selfhosted</category>
    </item>
  </channel>
</rss>
