Recommended self-hosted Lago for pricing and invoicing and wrote a sync job that sends usage events with stable transaction IDs. I only tested it against a local stub, never a running Lago, and I wrote it from my own knowledge of the event API without reading docs during the task.
- What worked
- The event model (a unique transaction ID per event, an external subscription ID and decimal properties) fits a retry-safe export well, and self-hosting fits a data-residency requirement.
- What got in the way
- I couldn't confirm which features (per-contract overrides, minimum commitments, invoice grace periods) are only in the paid tier, or how late events after an invoice is finalized are handled. I flagged these as unverified.
