Hacker Newsnew | past | comments | ask | show | jobs | submit | AnhTho_FR's commentslogin

Lago (YC S21) | Europe+USA | Remote or Hybrid | Full-time |

The AI-Native, Open-source, usage-based billing platform. Lago is now trusted by CoreWeave, Synthesia, Groq, PayPal and Mistral AI to manage their billing. YC & FirstMark backed.

Open Roles Include:

- Account Executive (Remote USA)

- Product Engineer (Growth/Building AI Agents)(Europe or USA)

- Product Engineer (Core product)

- Infrastructure Engineer (Remote Europe, Canada or Brazil)

Lago Website: https://getlago.com/hiring YC Jobs Page: https://www.ycombinator.com/companies/lago

Looking forward to seeing some great applications!


Been following along with Lago from the early days. Great to see how much progress you guys have made!

Lago | Europe+US | Remote or Hybrid | Full-time |

Open-source usage-based billing (Customers include CoreWeave, Groq, PayPal). YC & FirstMark backed.

Hiring across teams: https://getlago.com/hiring


Impressive performance!


Awesome, love the name. In terms of use cases, would you replace an agent created by something like Glean (let's say the agent was dedicated to retrieving internal knowledge for CS teams or Sales teams)?


100%, at much lower cost and accessible by SMBs on top of that. You can typically retrieve any data from your Intercom tickets, CRMs, Slack conversations, websites and documentation tools. We'll be also adding meeting transcripts but for now our customers build a custom sources and index these with our API.


« Oso has been succeeding while Zanzibar clones have not » -> Oso looks great but don't you think they will end up selling to Google, which is just sad for Open-Source? We've seen this movie before


Love the transparency - Interesting to see the (limited) impact of Product Hunt!


Lago (YC S21) | Open-Source Usage Based Billing | Full-time | EU or Bay Area | https://www.getlago.com/

Lago is the leading open-source usage-based billing API, bringing flexibility, transparency and control to teams to handle subscriptions, usage metering and pricing iterations. Lago has been chosen by companies such as Mistral.ai, Swan.io, Together.ai, Groq.com, and raised a total of $22M (FirstMark, Y Combinator).

We’re hiring either from SF and the Bay Area or Paris, France: - Product Marketers - Content Marketers - Customer Experience Lead - (Post-Sales) Contact talent[a]getlago.com if interested! Please include all relevant information (Linkedin profiles, sample of work, where you’re based, helps us respond faster).


Lago | https://www.getlago.com/about-us | Founding Marketing Team | US (San Francisco) | Full-time

We build open-source billing, and are used by companies like Groq.com, Mistral.ai, Together.ai.

So far our marketing has been very organic and founder-led, we're looking for the initial 3-4 people team to take it to the next level: product marketing, brand, demand generation, etc.

We've raised a total of $22M, here's our series A deck: https://www.linkedin.com/posts/anhthochuong_fundraising-deck...

You can apply at talent@getlago.com, if you can add a few bullet points of context, it helps!


Applied to this role. Also a former founder with tons of experience in GTM, growth, strategy, ops!


The question is: how can we (Lago) make it much easier (if you think it's not the case today) than working with the data from Sigma and from data pipeline exports?


I don’t think you can, which is why I criticized this blogpost for failing to demonstrate a compelling answer, and instead relying on misleading arguments based on invalid pricing assumptions.

If you think it’s easier to calculate MRR with Lago than with data derived from Sigma or the reporting data exports, I suggest showing how it’s done in each case and explaining why Lago’s schema makes it easier.

Arguing that it’s harder on Stripe because if you’re DoorDash you would have to pay a lot of money for Sigma is not honest.


I'll reach out in DM re: invalid pricing assumptions (genuinely wand to gather feedback and iterate). Re: "how it's done with Lago" : I assume you've seen the SQL queries we shared as examples... but you still don't think it makes the point, what would have? https://github.com/getlago/lago/wiki/Stripe-Data-vs-Open%E2%...

Disclaimer: the example (for the sake of the article) is relatively simple, as it's our first article on this topic, but we're willing to go much deeper, so feedback/inputs are welcome.


We shared our product hunt handbook if it can be useful: https://github.com/getlago/lago/wiki/Product-Hunt-launch-:-o...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: