FAQ

Is it free?

Yes. Hookgres is MIT licensed. There are no per-message fees, because it runs on your own database.

Does it work with Supabase, Neon, RDS, Cloud SQL...?

It should work with any Postgres 14+. Hookgres uses plain SQL and needs no extensions. CI tests it on Postgres 14, 15, 16, 17 and 18.

It also uses no session state: no LISTEN/NOTIFY, no named prepared statements, and only transaction-level advisory locks. So it should work through a pooler in transaction mode, such as PgBouncer or Supavisor. Pooler setups aren't part of CI yet.

Can I use it with Prisma, Drizzle or Kysely?

Hookgres needs a pg.Pool for itself. Your ORM can keep its own connection. For transactional sends, pass send() a client with a node-postgres style query(text, values) method that runs inside your transaction. If your ORM can't give you one, call send() right after the commit instead. You lose the outbox guarantee, but everything else works.

Is delivery exactly once?

No, at least once. A worker can crash after the receiver answered but before the result was saved, and then the webhook is sent again. This is true of every webhook system, which is why receivers should deduplicate on webhook-id.

Are webhooks delivered in order?

Not strictly. Deliveries are claimed roughly in the order they become due, and several are sent in parallel, so retries let later events overtake earlier ones. If order matters, include a version or timestamp in the payload, or have receivers fetch the current state.

How do I show customers their delivery history?

Use listDeliveries({ endpointId }) and listAttempts(deliveryId), or query the tables directly. The playground source is a small working example of a delivery dashboard.

Can it receive webhooks from Stripe, GitHub and others?

No. Hookgres is for sending. verifyWebhook exists so receivers, including your own tests, can check what Hookgres sends.

How big can payloads be?

Postgres allows large jsonb values, but keep webhooks small, well under a megabyte. Large bodies slow down every retry, and many receivers reject them. A common pattern is to send ids and let the receiver fetch the details.

Does it run on Bun or Deno?

It's built and tested for Node.js 22.12+. Other runtimes with node-postgres and fetch may work, but they aren't tested.

Why Standard Webhooks?

It's an open spec, adopted by Svix and others. It comes with verification libraries in many languages, so your customers don't need anything from you to verify webhooks.

Why not just use a job queue?

You can build webhooks on pg-boss or graphile-worker. You'd then still need signing, per-endpoint health, auto-disable, secret rotation, a delivery log and replay. Hookgres is those parts, built on the same SKIP LOCKED technique.

Something's wrong. Where do I look?

1. listDeliveries({ status: "failed" }) and listAttempts show exactly what each endpoint answered.
2. onError logs problems with the worker itself.
3. The monitoring queries show the backlog and failing endpoints.

Still stuck? Open an issue.