// the find
hookdeck/outpost
Open Source Outbound Webhooks and Event Destinations Infrastructure
Outpost is a self-hostable webhook delivery system for platform builders — companies that need to send events to their customers' endpoints. It handles the full lifecycle: multi-tenant delivery, retries, observability, and a customer-facing portal. Think Svix or Convoy, but with first-class support for non-HTTP destinations like SQS, Pub/Sub, and Kafka.
1. Destination breadth is genuinely useful: supporting Kafka, SQS, RabbitMQ, GCP Pub/Sub, and EventBridge alongside plain HTTP webhooks means customers aren't locked into a single integration pattern. 2. The architecture is honest about its dependencies — Redis + Postgres + a message queue is a known, operable stack, not a bespoke storage engine you have to learn to debug. 3. The managed/self-hosted parity story (same binary, same codebase) is a real differentiator; you can evaluate locally and graduate to managed without a feature cliff. 4. OTel support built-in means you can drop it into an existing observability stack without bolting on a sidecar or writing custom exporters.
1. The customer portal is an opaque embedded UI — there's a guide on 'building your own UI' but the default portal is a black box, which will frustrate anyone with strict white-labeling requirements or custom auth flows. 2. At 984 stars and v0.x versioning, the API surface is still unstable; the upgrade guides for v0.12 through v0.17 in the docs suggest schema-breaking changes are frequent enough to warrant dedicated migration docs for nearly every minor version. 3. Redis is required even if you're running a single-node deployment for a small platform — there's no lightweight mode that runs without it, which raises the floor for self-hosting. 4. The filtering feature exists but the docs are thin on what filter expressions actually support — you have to read the OpenAPI spec to understand what's possible, and that's a bad sign for operator ergonomics.