Hookdeck

New year, new product. Introducing Hookdeck Outpost. A fully managed, serverless service for sending webhooks and event destinations.

What you get: - At-least-once delivery, retries + topic-based subscriptions - Multi-tenant support with a user portal for customers - Deliver to webhooks, SQS, RabbitMQ, Kafka, Pub/Sub, EventBridge+more - Serverless scaling, SOC2 compliance, and proper support

New year, new product. Introducing Hookdeck Outpost. A fully managed, serverless service for sending webhooks and event destinations.

We've been working on the open-source version of Outpost for well over a year—shipping destination filters, expanded destination support, and stability improvements based on your feedback. But one request kept coming up: "Can you just host it for me?" So we did.

"We didn't know if we had received a webhook or not. We just hoped everything worked." 😬 See how Pennylane eliminated webhook guesswork across Shopify, WooCommerce, Lago + more, and turned daily firefighting into reliability ↴

What shipped in December: ↳ Custom Columns in Event Gateway ↳ Outpost v0.10.0: destination filtering and custom headers ↳ CLI v1.4.0: API integration & docs updates Plus, new guides for @ShopifyDevs, @StripeDev, and Outpost

📊 New: Prometheus metrics export in Hookdeck Monitor your webhook infra in the same stack as your services: • Request rates, delivery attempts, queue depth • Latency + failure rates • Rich labels (team, org, source, destination) • Pre-built @grafana dashboard

August 2025 Hookdeck product updates: - Webhook deduplication reduces processing overhead - Free metrics provide full observability - MS Teams alerts for real-time notifications - Outpost v0.5.0 adds Amazon S3 event destination support

🛠️ Shopify app builders: shipping multiple apps with the same webhooks? Problem: - You built inventory, fulfillment, and analytics apps - A merchant installs all three - An 𝗼𝗿𝗱𝗲𝗿𝘀/𝗰𝗿𝗲𝗮𝘁𝗲 event comes in three times - once per app - That’s triple the webhook traffic and processing overhead

With Hookdeck’s deduplication rule, you only need to handle each order once per store, regardless of how many of your apps are installed. Idempotency is still essential in your app, but deduplication cuts down the noise so your backend isn’t overwhelmed.

Hookdeck Metrics are now free on all plans. No more gating. You get full delivery, throughput, and retry visibility from day one. A few nice UX improvements too 👇 🔗 hookdeck.com/blog/metric...

🚢 Outpost 0.4.0 released Outpost is our open source, self-hosted event delivery service. It gives you full control over how events are delivered as webhooks and directly to queues, with retries, delivery logs, and multi-tenant routing built in.

🔄 Highlights: - Azure Service Bus support (queues and topics) - New SDKs (TypeScript, Go, and Python, generated with @speakeasy.com) - Azure deployment scripts - Example showing how to create a tenant, add a destination, and publish an event with the SDKs

🚢 Outpost 0.4.0 released Outpost is our open source, self-hosted event delivery service. It gives you full control over how events are delivered as webhooks and directly to queues, with retries, delivery logs, and multi-tenant routing built in.

The Hookdeck Event Gateway allows full control over transformation and filter order in your event pipeline. Options include: → Filter or transform first → Cleanup data pre-delivery → Deliver only essential data Available via dashboard UI and API.

Webhooks are not a trivial problem at scale. When you're processing thousands of events per second, your strategy matters. Webhooks are usually delivered at-least-once. Assume duplicates and out-of-order events are the norm, not the exception.

Event-driven architecture with robust queuing is your friend. Decouple, buffer, and process webhooks reliably.

Webhooks are not a trivial problem at scale. When you're processing thousands of events per second, your strategy matters. Webhooks are usually delivered at-least-once. Assume duplicates and out-of-order events are the norm, not the exception.

Event-Driven Architecture: Beyond the Basics Choosing the right infrastructure for event-driven systems is a strategic move that can define your application's performance, scalability, and responsiveness.

Key considerations include: - Selecting appropriate message brokers - Understanding distributed streaming platforms - Designing flexible event gateways - Creating resilient microservices architectures The goal? Build systems that react in real-time and adapt to changing business needs.

Our new dashboard v4 is a serious upgrade. It's a fundamental rebuild for clarity and speed. We tackled the core challenge of making event metrics instantly readable.

Performance: We optimized loading times, streamlined navigation, and created a dashboard that feels responsive from the first click. We've reimagined how developers interact with complex event infrastructure. Clean, fast, informative.

Our new dashboard v4 is a serious upgrade. It's a fundamental rebuild for clarity and speed. We tackled the core challenge of making event metrics instantly readable.

Resource management used to feel cramped. Now? Your core workflows have room to breathe. We built this base so future iterations can be even faster and more intuitive.

💡 Ever wondered how to manage complex event streams without cluttering your application code? Event filtering and routing is your secret sauce.

Use inclusion filters to define which events flow through specific connections explicitly. This means less noise, more signal.

💡 Ever wondered how to manage complex event streams without cluttering your application code? Event filtering and routing is your secret sauce.