Ross ROSS = Recommend OSS · open-source software intelligence for agents

hookdeck/outpost

Open Source Outbound Webhooks and Event Destinations Infrastructure observed · 2026-08-28

github.com/hookdeck/outpost · homepage · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

84/100

  • Activity 98
  • Release rhythm 85
  • Longevity 53
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 0
  • age_days: 742
  • days_rel: 20
  • days_push: 14
  • n_releases_24m: 102

Full methodology

Adoption not part of the score

1052 stars · 59 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Outpost is open-source outbound webhook and event delivery infrastructure that lets SaaS platforms reliably send events to their customers' destinations (webhooks, AWS SQS/S3/EventBridge/Kinesis, GCP Pub/Sub, Azure Service Bus, RabbitMQ, Kafka). Written in Go and self-hostable via binary or Docker, it provides at-least-once delivery, retries, multi-tenancy, topic-based subscriptions, observability, and a self-service tenant portal.

Use cases

  • send outbound webhooks from my SaaS platform
  • deliver events to customer-managed destinations like SQS or Kafka
  • self-host webhook delivery infrastructure with retries
  • give my customers a portal to manage their webhook endpoints
  • fan out platform events to multiple tenants and topics
  • replace building in-house webhook delivery with retries and observability
  • publish events to customer queues like RabbitMQ or GCP Pub/Sub

When to choose

  • you operate a multi-tenant SaaS/API platform that must deliver events to customers' own systems
  • you need at-least-once delivery, automatic/manual retries, and delivery observability out of the box
  • you want to support diverse destination types (webhooks, queues, event buses) without building each integration
  • you want a self-hostable, dependency-light (Redis, PostgreSQL, a message queue) alternative to a managed webhook service

When to avoid

  • you only need to receive/consume inbound webhooks rather than send them
  • you need per-tenant delivery rate limiting or event transformation, which Outpost deliberately omits
  • you want a fully managed solution and prefer not to run Redis, PostgreSQL, and a message queue yourself
  • your event volume is trivial and a simple HTTP call with a basic retry loop suffices

Facets

service · maturity active

webhook message-queue api-framework monitoring alerting web-development backend apis developer-tools self-hosted go self-hosted cloud outbound-webhooks event-destinations event-delivery multi-tenant retries tenant-portal eventbridge sqs pubsub kafka rabbitmq saas-infrastructure messaging docker web-server

10 sources

Member repositories

RepositoryRoleHealth v2
hookdeck/outpostmain84

For agents

markdown · JSON · MCP: product_card(name="hookdeck/outpost")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem