Skip to content
Changelog v1.14.0 New Improved

Usage metering, pay-as-you-go, and entitlements

Per-unit usage metering on an idempotent ledger, pay-as-you-go and subscription billing with overage and spending limits, and a general entitlements layer.

Published 2 min read
On this page

Building on the Paddle plumbing shipped earlier, this release adds the metering and entitlements that billing sits on top of. Usage is now counted precisely, and what a workspace is allowed to do is decided in one place.

Added

  • Usage metering — attempts, replays, and batch replays are metered into usage counters backed by an idempotent ledger, so the same event is never double-counted. The current period is backfilled from existing deliveries.
  • Pay-as-you-go and subscriptions — plans gain a billing mode, included events, and an overage rate, with block-ceiled overage pricing calculated per period. Spending limits cap how far usage can run.
  • Entitlements layer — a single entitlement service decides capabilities and usage limits, failing closed when a limit is reached rather than allowing an unbounded overrun.

Improved

  • Plan-capped retention — data retention is capped by plan, with a guard on downgrade so a lower plan cannot silently exceed its retention window.
  • Threshold notifications — usage crossing 70%, 90%, and 100% of the included allowance sends a notification once per period, so a bill is never a surprise.
  • Atomic ingest — a delivery, its usage record, and its forward job are written in one transaction, so metering can never drift from the deliveries it counts.

HookWatch is in beta; see the pricing page for current plans.

Notes

Release date comes from the v1.14.0 git tag (17 July 2026).

Get started

See what happened to every webhook.

HookWatch keeps the request, the response, and every attempt for each delivery — so the debugging, retry, and replay steps in this article are a matter of reading, not reconstructing.