I’m a contributor to StripeMeter, a tiny open-source tool to prove Stripe usage invoices are correct before they finalize. What it does (small surface):

- POST /v1/replay — reconcile late/duplicate events (dry-run or apply)

- GET /v1/reconciliation/summary — see drift and counters before/after

- GET /v1/usage/history — time-series to visualize the effect

Why: real systems have retries, late events, and dupes. StripeMeter sits beside your billing/pricing layer to ensure the numbers are exact pre-invoice.

Not: a pricing/plan/entitlement system or a warehouse.

Scope & limits: aimed at early/mid-stage SaaS on Stripe usage billing; local target ~10k late-event replay in ≤ ~2s (queue/workers recommended at scale).

Contributors & Feedback wanted: docs polish, SDKs (Node/Python), replay worker improvements, minimal visualizer, observability (Prom/Grafana), integrations. Check Good First Issues and our pinned Design Partners thread if you want to run a quick parity session.

If you haven't already, would you mind reading about HN's approach to comments and site guidelines?