> Eldridge horrors

Just FYI, I think you probably meant "eldritch horrors":

https://www.merriam-webster.com/dictionary/eldritch

Stupid auto-correct.

Yeah, I almost didn't say anything - it looked autocorrect-y.

Just figured it would be useful to mention in case it was a genuine mondegreen.

Using Stripe here makes sense, if they have product for this. Wouldn't I need to store all of the same information in my database anyway as a source of truth?

Stripe is great for payments, but they don’t make usage data super useful for data purposes — their primary use case is payments.

If you want access to your data for other business purposes - stakeholder data, embedded dashboards, alerts and notifications about usage, etc - then you’ll want a system more purpose-built for usage data than Stripe.

Check out https://kable.io. Kable is purpose built as a data and billing solution, where your data is available for purposes ancillary to payments.

[Disclaimer: I am a Kable founder, but what you’re describing is precisely what we’re built for. If you’d like to chat, either about Kable or about your design in general to build this in-house, I’d be happy to.]

Hi asommer, How can I contact you about Kable.io?

[email protected] -- looking forward to chatting!

You could (I would) but you could care a lot less about it and treat it mostly as a log to use for reconciliation later if there's an issue or if you want to migrate to a different billing system.

The data is going to still be available in Stripe to download later if you need the raw events (or just the summaries from the invoices).