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

41–50 of 144 posts

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

#41

Post by Rafsark »

JeanEdern wrote: post #35

How do you compare with other processes and workflows to manage billing? For example: using snowflake + DBT to track billable metrics?

You can still use Snowflake + DBT to track usage. However, this won't cover billing use cases. On top of this, you could need to create invoices, trigger payments, handle coupons, and issue credit notes. Many customers use warehouses to track usage and send usage-based HTTP events to Lago. This is the first step towards a full consumption-based or hybrid billing model. Ensure continued revenue and customer satisfaction by covering the entire billing, pricing, and invoicing workflow (not only aggregating usage)

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

#42

Post by harrylucas »

rvz wrote: post #29
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.

I always get confused with AGPL and seems to have differing opinions online, so wanted to ask here. If I use Lago in my app, and don't change it all, do I need to opensource my entire application?

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

#43

Post by jmacd »

Exciting to see the progress of Lago and the attention being given to the challenges in the SaaS billing world.

We're also working in the billing space with a complementary tool, Tier (https://github.com/tierrun/tier). Although we currently do not support Lago directly, it's exciting to see more options emerging. Their content marketing has been particularly impressive on HN and in general.

With metering, entitlement management, CPQ, feature gating, and everything else required in a modern SaaS company, the PriceOps space can be quite complex for developers.

Congratulations on the launch and best of luck!

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

#44

Post by dang »

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…

Each YC funded startup gets one "Launch HN" post (see https://news.ycombinator.com/newsfaq.html, https://news.ycombinator.com/launches, https://news.ycombinator.com/yli.html). It's fine if they've already launched. If they're already well-known to the community it might be different, but that's rare. In this case, for example, none of the posts you linked to got much attention.

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

#45

Post by Kiro »

Rafsark wrote: post #36
nylonstrung wrote: post #31

How do you guys differ from Lotus, the other YC open-source usage based billing company?

Hi, First of all, we launched our open source billing repository months before they did. In fact, they even reached out to us for inspiration. This could be related to the fact that our team has prior experience building billing engines, so we have a better understanding of the space. From a product perspective, our coverage is more extensive. We provide more advanced coupons, usage-based components and billing use-c…

That's a pretty obnoxious reply, especially considering they are your alumni. Be more humble.

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

#47

Post by Rafsark »

Kiro wrote: post #45
Rafsark wrote: post #36

Earlier quoted context omitted.

Hi, First of all, we launched our open source billing repository months before they did. In fact, they even reached out to us for inspiration. This could be related to the fact that our team has prior experience building billing engines, so we have a better understanding of the space. From a product perspective, our coverage is more extensive. We provide more advanced coupons, usage-based components and billing use-c…

That's a pretty obnoxious reply, especially considering they are your alumni. Be more humble.

Hi Kiro, I don't consider this an impudent response. We strive to base our answers on facts, from both the team and product perspectives. We tried to detail differences from a product point of view. We respect everyone in this space, including established vendors and newcomers. They all have a positive influence on our product, pushing us to deliver faster with higher quality.

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

#48

Post by Rafsark »

jmacd wrote: post #43

Exciting to see the progress of Lago and the attention being given to the challenges in the SaaS billing world. We're also working in the billing space with a complementary tool, Tier ( https://github.com/tierrun/tier ). Although we currently do not support Lago directly, it's exciting to see more options emerging. Their content marketing has been particularly impressive on HN and in general. With metering, entitleme…

Thanks! The space is becoming more and more exciting. Many players will emerge in different verticals, creating a great impact. Companies will be able to price, invoice, and track usage with greater precision.

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

#50

Post by louis-lau »

harrylucas wrote: post #42
rvz wrote: post #29

Earlier quoted context omitted.

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.

I always get confused with AGPL and seems to have differing opinions online, so wanted to ask here. If I use Lago in my app, and don't change it all, do I need to opensource my entire application?

As far as I understand it there's no legal precedent, so we're not completely sure. Some say calling an api means it's part of your application, meaning you need to open source your app. Some say that that's not the case. I think this unknown is why the license is banned in some companies.

I think what matters more is how the creators of the software intend the license. In case of Lago it's clear they want you to use it this way, and AGPL is only really meant to restrict businesses that want to fork it and start a proprietary billing service.

Post reply on HN