Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Lago (YC S21) – Open-source usage-based billing

news.ycombinator.com

Post reply on HN
Print view View original

21–30 of 144 posts

Re: Launch HN: Lago (YC S21) – Open-source usage-based billing

#21

Post by Rafsark »

canadiantim wrote: post #16

Congrats on the launch! I fully intend on using Lago for my SaaS. I wonder, would it ever be possible to use the structure provided by lago to also set up a marketplace where user can buy/sell from eachother?

Thanks, we're excited to have you on board! We've had some requests about billing for marketplaces. Currently, Lago is designed to bill subscriptions with embedded fixed fees and usage-based fees, resulting in a consolidated "end of period" invoice. Marketplaces, however, require immediate invoicing with a different logic. We have a product vision dedicated to SaaS for now, but this could be a use-case to tackle in the future.

Re: Launch HN: Lago (YC S21) – Open-source usage-based billing

#22

Post by Rafsark »

ferdi05 wrote: post #20

Congrats on the launch! And thanks for helping the open-source ecosystem to thrive. I'm always happy to see open-source companies challenging the status quo. Open Source is very often the most reliable choice, and you contribute to spreading the word.

Thanks for the kind words. At Lago, we want to break the notion that billing is always a "buy or build" option. Billing can be so different between companies that it may require a custom setup, infrastructure, and model. Furthermore, the "buy" options available are often not scalable enough for large companies.

With our open source version of Lago, we offer: - Fair pricing: scale your billing as your company grows - Composability: build the pricing/billing you have in mind, without the limitations of vendors - Participative approach: contribute to the entire billing engine so other companies can benefit from it.

Re: Launch HN: Lago (YC S21) – Open-source usage-based billing

#25

Post by super256 »

rabidonrails wrote: post #2

Congrats on the launch, definitely an interesting product and really interesting space. But...didn't you guys launch a while ago? Is there something specific you're launching now? >> The tech stack we use to build Lago (YC S21), the open source billing API ( https://news.ycombinator.com/item?id=32438355 ) >> Lago: The Open Source Stripe Billing Alternative ( https://news.ycombinator.com/item?id=32438355 ) >>Lago: The…

Might be interesting for some: https://youtube.com/watch?v=3xU050kMbHM&feature=shares

YC video about launching and launching again.

Re: Launch HN: Lago (YC S21) – Open-source usage-based billing

#27

Post by jdenquin »

haolez wrote: post #24

After clicking on your repo link, for a moment I was taken aback by the repo being 100% written in shell script. :) But then I've noticed that you use git submodules for the frontend and backend. It's actually a Rails application from what I can tell.

Hey @haolez, yes the main repo contains all the docker configurations and 2 subsmodules, so you just have to clone this one and have Lago up in 2 minutes if you want to try it out! Our api uses Ruby On Rails and our front end is build with React!

Re: Launch HN: Lago (YC S21) – Open-source usage-based billing

#29

Post by rvz »

rapnie wrote: post #15

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:/…

Yes. AGPL is a great choice and counters SaaS companies that are trying to grift and abuse open-source with a modified competing product without contributing back.

Re: Launch HN: Lago (YC S21) – Open-source usage-based billing

#30

Post by rileyphone »

Brad Cox laid out a scheme similar to this in hopes of solving the software crisis, in his 1995 book Superdistribution. Now, it wasn't really technically feasible when software was local and native, but in the cloud era it makes a lot more sense. I've personally felt the pain of creating a bespoke multitiered billing system so I appreciate what you're trying to do here, good luck!
Post reply on HN