Show HN: Flexprice: Open-Source Usage-Based Billing Toolkit
11–17 of 17 posts
Re: Show HN: Flexprice: Open-Source Usage-Based Billing Toolkit
#12We've been building a GenAI application with fairly simple credit-based workflows to begin with. But just a month into launch, the workflows have started getting more complex, and we’re now rolling out 4 different pricing plans with volume-based tiers. I was exploring how best to build a flexible credit billing system when I came across Flexprice — and I have to say, it's a great product. Good to see you here on HN.…
We’re building Flexprice specifically to avoid that constant rewrite cycle, good to know it resonates. Happy to chat if you run into edge cases while scaling those new plans.
Good luck with your GenAI launch!
Re: Show HN: Flexprice: Open-Source Usage-Based Billing Toolkit
#13Re: Show HN: Flexprice: Open-Source Usage-Based Billing Toolkit
#14I run my startup for fine tuning llm models for enterprises and providing them inferencing trainmyllm.ai, would love to do a POC with you guys, would solve all my billing related problems with this. Cheers
I’ll DM you, we can run a quick POC and see if it fits your setup. Appreciate the interest.
Re: Show HN: Flexprice: Open-Source Usage-Based Billing Toolkit
#15Great work! The time-bucketed usage summaries and support for hybrid pricing models are super compelling. How are you handling billing-grade precision for things like token-based metering—especially when upstream services (like OpenAI) may have delays or partial responses? Also curious how you model retroactive adjustments without compromising invoice integrity.
Retroactive adjustments are handled by versioning usage records, so instead of overwriting historical events, we apply corrections as delta events. Invoices pull from the latest state, but we preserve full audit logs underneath to avoid integrity gaps.
Re: Show HN: Flexprice: Open-Source Usage-Based Billing Toolkit
#16so many of the eventually consistent stores reflect so late that its a pain to work with their SDKs
out of curiosity, what kind of metrics or observability do we get for events that got dropped due to some issue