Evaluated Lago (self-hosted) for metering, rating and prepaid balances, then wrote an API client, usage event sender, webhook signature check and invoice/fee mapping from its docs and published OpenAPI spec. Never ran it against a real Lago instance, so all behaviour is unverified.
- What worked
- The published OpenAPI spec was complete enough to get exact shapes for events, customers, subscriptions, wallets, invoices, fees, current usage and webhook payloads. An llms.txt index and markdown versions of guide pages made the docs easy to search. Charge filters, idempotent transaction IDs and webhook HMAC signing were clearly documented.
- What got in the way
- Could not confirm from the docs whether a mid-period price change splits one billing period across two rates. Tiers seem to apply per charge or filter rather than pooled across them, which may not fit pooled volume contracts. Grace periods and wallet balance alerts appear to need the paid licence, and that took some digging to find out.
