Launched this week
BillingEngine
Usage-based billing for APIs — real-time rating
3 followers
Usage-based billing for APIs — real-time rating
3 followers
Billing Engine is a simple tool for pricing events and service usage. Send a usage record → our engine finds the right price list and returns the price. Built for simplicity. Perfect for SaaS, API, telco, IoT platforms, and more — wherever high service usage needs to be billed accurately. Try it free. Upgrade when you're ready. We don't need to know anything about your customers — just a unique identifier. Apply customer pricing, partner commissions, or margins through flexible pricing rules.
The flat usage-based pricing model here is interesting but I'd want to understand how it scales with volume. For a finance team, the billing of the billing tool itself matters a lot. The promise of sending a usage record and getting back the right price instantly is appealing but how does it audit and reconcile at month end?
@aina_finance
Thanks for the great questions — audit and reconciliation are exactly the right things to dig into.
A few ways we handle this:
1. Every event you send to the API is rated individually and returned immediately. You store the priced record on your side — so at month-end, your stack already has everything it needs to generate invoice data. BillingEngine is the rating layer, not a full billing platform.
2. For reconciliation, you can call /dr/billing on our API — it returns aggregated billing items grouped however you need, for any date range, with summary totals similar to what you'd see on an invoice.
3. For audit, every rated event is stored with a reference to the exact price list and pricing rule that was applied. You can retrieve the full history of received and rated events at any time.
4. If you need deeper backward review — for example, which price list items were used, from which price lists, for which customers, over a given period and at what cost — that kind of reporting can be added. Let us know what you'd need and we can look into it.
Hope that covers it — happy to answer any follow-up questions!
Hi everyone 👋
I'm Michal, a programmer with 10+ years of experience in telecommunications and payment services — and that's exactly where BillingEngine was born.
After working with complex billing systems daily, I wanted something simple: Send a usage record → find the right price list → return the price instantly.
Most billing platforms were either:
Too expensive
Too complex
Focused on subscriptions instead of real usage
BillingEngine focuses purely on rating and usage billing — built for SaaS, API, telco, IoT platforms and more. No customer data needed, just a unique identifier. Split usage across services, apply customer pricing, partner commissions or margins through flexible pricing rules.
Try the free plan and upgrade when you're ready.
Would love your feedback: How are you currently handling usage-based billing?