Hi everyone! About a year ago, I began working on a side project aimed at creating a platform for "Webhook as a Service." The idea is to serve as a proxy for services like Stripe, GitHub, and Shopify, allowing them to send webhooks to multiple destinations, such as your API or Slack. My platform includes features like automatic retries, filtering, payload transformations using JavaScript, monitoring, and alerts. I also developed a webhook inspector tool to help debug and visualize the headers and body of webhooks. However, I've noticed that most users are primarily using the webhook inspector. Considering that there are already some competitors in this space, I'd love to get your thoughts as developers and infrastructure engineers. Do you think my service is valuable, or should I consider pivoting my project, Hooklistener, to something else? Thanks for your input!
2 Answers
How do you plan to compete with Hookdeck? They're quite established.
I’ve looked into webhook tools before but I'm not using them currently. While your features sound impressive, I tend to avoid adding external services into critical paths due to the potential dependency issues. It feels like the risk might not be worth the benefits you're offering.
That's a fair point. I guess these services might be more appealing for smaller teams that can't afford to spend too much time on infrastructure. As teams grow, managing it in-house usually makes more sense. Appreciate your insight!
I’m aiming for feature parity at a lower price and I want to provide a simpler user experience. For instance, I'm working on customizable dashboards where users can monitor relevant metrics. Recently, I’ve been focusing on adding features like cronjob services and even exploring real-time services using websockets for applications like chat. What features do you wish Hookdeck had?