On: Billing systems are a nightmare for engineers

[asciimike]

Nit: there's a lot of noise being made in comments about it being an open source product, but I haven't found the source (maybe I have to speak to an expert to get it?). github.com/getlago has the docs, which is nice (and gives a lot more info than is available on the website about how the product works), but not quite the same.

Also note:

> Our open-core version is forever free. We will introduce paying add-ons in the future, with a consumption-based approach.

[AnhTho_FR → asciimike]

Hello! As promised, the repo is available here: https://github.com/getlago/lago ! We also opened our roadmap: https://github.com/getlago/lago/projects/2 You can request and vote for features here: https://community.getlago.com/c/feature-requests/11

[AnhTho_FR → asciimike]

It's coming soon, we're in the final steps of QA, but we could not wait to share this post! Thanks for the comments on the documentation, by the way!

[asciimike → AnhTho_FR]

Awesome, glad to hear, would love to take a look whenever it's available! Looking at the docs it seems like the current state of the product is much more about subscriptions than usage based billing (e.g. no aggregation or rating). Any plans to add those in?

[AnhTho_FR → asciimike]

We have an event-based architecture and offer 'aggregations' at the moment: https://doc.getlago.com/docs/guide/billable-metrics/aggregat... We plan to add more aggregation types, gauge metering as well!

We definitely want to address usage-based pricings, but also all the pricings that are hybrid between usage and subscriptions (ie the vast majority of software pricings). Feel free to reach out if you have more question: anhtho@getlago.com