3 ms·
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?
by punkpeye 4y ago
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?
- kondro 4y agoYou 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).
- asommer12 4y agoStripe 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 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.]
- thedangler 4y agoHi asommer, How can I contact you about Kable.io?
- asommer12 4y agoadam@kable.io -- looking forward to chatting!