I submitted separately [0] your blogpost "Open-source licensing and why Lago chose AGPLv3" [1]. I find this a refreshing and good read that counters the usual FUD so many people raise when hearing about the AGPL. In the article is mentioned Plausible [2] who also managed to create a great business this way, and in direct competition to Google Analytics. Well done. https://news.ycombinator.com/item?id=34773891 https:/…
Regarding this blog post, I don't understand how AGPL is a good fit for the first stated use case. >Case 1: You fork our code to build your own billing system at your company. It’s awesome and we would be grateful if you could take some time to share your code as well, as it could help other companies. This is _strongly encouraged but not required_, as we understand not all companies can afford to do this. And later…
Launch HN: Lago (YC S21) – Open-source usage-based billing
91–100 of 144 posts
Re: Launch HN: Lago (YC S21) – Open-source usage-based billing
#92Interesting. Would you know how this compares to turnstile [0]? (I only know about them because I saw their hiring page on HN a week or two ago, and was intrigued.) [0] https://tryturnstile.com/
Re: Launch HN: Lago (YC S21) – Open-source usage-based billing
#93Congrats! We built a usage-based telephony (voice & sms) billing system for our customers and appreciate the pain. Not to take anything away from your launch, but founders / product managers should carefully consider if usage-billing (even with a tool like Lago) is best for your business and customers. We started as usage-based then learned a few years in (once we understood customer usage trends - key) that customer…
Re: Launch HN: Lago (YC S21) – Open-source usage-based billing
#94Congrats! We built a usage-based telephony (voice & sms) billing system for our customers and appreciate the pain. Not to take anything away from your launch, but founders / product managers should carefully consider if usage-billing (even with a tool like Lago) is best for your business and customers. We started as usage-based then learned a few years in (once we understood customer usage trends - key) that customer…
Re: Launch HN: Lago (YC S21) – Open-source usage-based billing
#95Congrats! We built a usage-based telephony (voice & sms) billing system for our customers and appreciate the pain. Not to take anything away from your launch, but founders / product managers should carefully consider if usage-billing (even with a tool like Lago) is best for your business and customers. We started as usage-based then learned a few years in (once we understood customer usage trends - key) that customer…
I'm interested how you handle suppliers that have usage-based pricing (which I imagine are the norm in the telephony space) if you can't pass this on to the customer. Do you offer your customers an unlimited plan, price it high and just hope they don't use so much that you go backwards?
Re: Launch HN: Lago (YC S21) – Open-source usage-based billing
#96Happy Lago customers here at Mono, we we're able to "hack"our way to billing connecting a Kafka listener to n8n and orchestrate all the billing from n8n, rather than expending lots of time integrating. We did all the integrations in 1 week in a "low-code" environment without requiring any developer to work on in.
Re: Launch HN: Lago (YC S21) – Open-source usage-based billing
#97great project and thank you for open sourcing! this is something I need for a future project and you have already built all or most of the features I need for the billing aspect. I'll explore the product more on my own and will try to contribute back where possible
Re: Launch HN: Lago (YC S21) – Open-source usage-based billing
#98This is such a great product and a must have for new age API based products. Congrats on the launch!
Re: Launch HN: Lago (YC S21) – Open-source usage-based billing
#99Wow this is finally happening! Big fan of this team and this product! Congrats for this launch, this is the first milestone of an amazing journey reinventing billing for tech companies!
Re: Launch HN: Lago (YC S21) – Open-source usage-based billing
#100Earlier quoted context omitted.
What would be the use case for you and the reasons to leave Stripe Connect? We're working with one company to replace their Stripe Connect stack, but it really depends on the specifics of the use case. My email if useful: anhtho[at]getlago.com
payfac flexibility (aka, no vendor lock-in) — requires an independent platform ledger (where payments have two legs: payee to platform and platform to merchant). Refunds and chargebacks may affect both legs :)