Lago

“Billing is easy.” Sure. Cooking is easy too, until every guest orders à la carte, changes ingredients mid-meal, eats a different amount, splits the bill by department, and asks for usage-based pricing on the sauce.

Congrats @GroqInc !

@byAnhtho @TalendCommunity Beautifully written!

The ultimate founder perk is to hand pick your team and who you end up spending 95% of your time with! Honored to welcome Michael, bringing 17y+ of data and open-source experience cc @TalendCommunity, and he's a corporate card nerd too (Yokoy/Perk, we were early at Qonto). I'm still "chief copywriting officer" at Lago but he wrote this all by himself, and I wouldn't have done better!

The better your AI product gets, the worse your margins can get. Jevons, 1865: make it cheaper, people use far more. Coal then. Tokens now. Most platforms let you meter AI usage. Lago lets you protect the margin behind it too. #bill-in-tokens-or-in-dollars" target="_blank" rel="nofollow noopener">getlago.com/docs/guide/ai-…

We're one step closer to Agentic Payments. Thanks @laravelphp's team for the contribution. Open-Source FTW! #agent-sdk-bill-the-dollar-cost-of-llm-calls-with-your-margin-built-in" target="_blank" rel="nofollow noopener">getlago.com/docs/changelog…

1/ Stripe bought Metronome. Adyen is buying Orb. Easy to read as payments consolidating. Then Salesforce bought m3ter.

Let AI agents buy your product on your customers' behalf. @GetLago now supports Agentic Payments through Stripe Payment Tokens. Thanks @laravelphp for the contribution. Open-Source for the win! docs.getlago.com/integrations/p…

If you're a B2B SaaS adding AI credits onto seat-based pricing, or an AI-native company, we've launched the AI Agent SDK. You can price on top of LLM tokens, without rebuilding the plumbing. docs.getlago.com/guide/ai-agent…

Enterprise companies don't churn because of missing features. They churn because of unanswered tickets, slow escalations, and the feeling that no one is watching their back. That's why we're excited to raise the bar and welcome Jon Tanamachi as head of customer support at Lago!

We ran thousands of queries trying to break our own AI agent at @GetLago Some versions executed actions without waiting for confirmation. Others were so detailed they burned through the context window before a single useful response. This wasn't a side project. Prompt engineering turned into a multi-week engineering effort in its own right — and we're a team that expected the hard part to be the infrastructure. Here's what we got wrong early: we thought hallucination prevention was a prompt problem. Write precisely enough, and the model behaves. That's true for a chatbot. It's not true for an agent that can void invoices, retry payments, and apply discounts to your customer base. In billing, a hallucination isn't a wrong answer. It's a financial incident. Over/undercharging the wrong customer can create big trust issues (and angry Slack DMs from finance). So we rebuilt the approach around three layers: Constrain. The agent only calls tools we've explicitly defined. No improvising, no adapting. More hand-holding required — but catastrophic outcomes become structurally impossible. Confirm. Before any consequential action — create, update, delete, void, retry — the agent shows a preview and waits for an explicit yes. No "always allow." Not optional. Exclude. Some tools we simply didn't build. Org management, API keys, webhook config — manual only. The best guardrail is one that doesn't need to exist. We also made a call that surprised some people: we built three separate assistants instead of one. A billing assistant that executes. A finance assistant that queries but can't modify. A pricing assistant that only advises. The reason: a product leader asking "what if we raised prices 20%?" should get strategic advice — not a price change. A lot went wrong. I wrote up the full picture — architecture, mistakes, and what I'd do differently from day one. Check it out here: getlago.com/blog/building-…

We're launching @GetLago Embedded today. A fully white-labelled billing system you can offer your customers under your own brand (no Lago branding). For the past year, we kept hearing the same thing from companies: "We've spent months with engineers full-time on billing. It's not good enough and it's consuming too many resources." Billing looks simple until you're building it. All the edge cases, pricing models, invoicing regulations… it all has to work together, reliably, at scale. Lago Embedded is a system that checks those boxes. It’s a fully white-labelled billing system you can drop into your product to ship billing in weeks, not years. It features: -Full invoicing engine -Scalable metering -Native support for subscriptions, credits, usage-based pricing and any hybrid (among others) -Open-source, so you host it wherever you want, e.g. on your own AWS/GCP/Azure No customer data ever leaves your environment, and there's zero vendor lock-in. If your product is adjacent to billing or your users want to monetize what they're building, this is for you. Find out more in @byAnhtho's article:

Discover Lago Embedded here: getlago.com/blog/lago-embe…

Today we're launching Lago Embedded. Building billing is a nightmare. Most teams learn this the hard way — months of engineering time, still not happy with the result. Lago Embedded is a fully white-labelled billing system you can drop into your product. Find out more⬇️