I met this team when they were just launching, not so long ago, they've been so inevitable since then!
Congrats @useblacksmith!
Glad to be a tiny part of the journey with Lago!
Love love love!
@MistralAI new launch (Voxtral)...
... and French 🇫🇷 humor 😅 x with Hacker News (passive) agressive comments
Congrats on the launch @GuillaumeLample @arthurmensch & team!
New Neocloud to watch! >> @blackfuelai
How are they different?
They come out of stealth with $250M+ of contracted revenue, not a $250M seed round.
+ they're French!
+ low-key super strong team!
Excited for them, and for Europe.
From side project to production, @laravel Cloud helps developers ship in seconds and grow with control over their costs.
Hats off to @driesvints and the team. Proud to power the billing behind Cloud ☁️
getlago.com/blog/laravel-bil…
Congrats to the amazing team at @MistralAI 👏
Such a major milestone for AI, Open-Source, Europe!
Proud to be a tiny part of this journey with our team at @GetLago
Replying to @ErikVoorhees
Credits solve the seat problem.
Then the customer asks what a credit is worth.
We mapped the trade-offs here 👇
Lago retweeted
Replying to @KamilMouhid @teddy_riker
There were really 3 tier 1 players in billing: Metronome, Orb and @GetLago.
- Stripe acquired Metronome
- Adyen acquired Orb
=> Lago’s the only independent Metering and Billing player in the field right now!
In case today’s router traffic is confusing:
Aug 19, 2026
@tryramp launched Router.com. One API, many models, built on the router it had run internally for three years. Probable domain bill: a few million.
Stripe acquired OpenRouter. Reported bill: $8B+.
One bought the company. One bought the URL.
Who got the better deal?
We bought router.com.
Now we're building the best one.
Our customers buy quadrillions of tokens every month through Ramp, and we've run our own AI on this router for 3 years to keep costs down.
Today it's yours at router.com
AI gateways are proliferating.
Stripe is reportedly nearing a deal to buy @OpenRouter for more than $7B. @vercel, @tryramp , @merge , @Cloudflare and others are building gateways too.
They want the same position in the request path. They don’t all want to make the same decision.
Very proud to work with @GroqInc. They’re already operating 13 data centers and planning 200+ MW for 2027. Huge congrats to the whole team!
Today we announced a $350M Series A led by @disruptivetech, with planned participation from @nvidia, valuing Groq at $3.5B and bringing our total to $1B raised in two months.
Inference is becoming the largest and most critical layer of AI infrastructure and it's what we do better than anyone. The injection of capital will support those seeking usage of medium and larger sized clusters of NVIDIA accelerated computing for training and inference. Groq expects to scale from 54 megawatts to 200+ megawatts next year.
Today, more than 6 million developers, Fortune 500 enterprises and thousands of AI-native companies build on Groq, generating trillions of tokens every week.
groq.com/newsroom/groq-close…
Huge congrats to the @useblacksmith team, a $45M Series B at a $550M valuation and 7x CI volume growth since January is an incredible run.
Honored to work with them at @GetLago, very inspiring team to watch.
Try them out if you're not using them already!
We raised a $45M Series B led by Peak XV in March, valuing @useblacksmith at $550M. We somehow never got around to announcing it until now; this year has been pretty busy.
One thing I’ve been thinking about is how we were both right and wrong about what was coming. When we raised our Series A in April 2025, we believed AI was going to lead to a lot more code being written, and that all of that code would still need to be built, tested, and validated before it could be merged. That part was right, but what we underestimated was how fast it would happen.
I have a suspicion that something changed over the holidays. Opus 4.5 came out in November; a lot of developers had time to really use Claude Code over the holidays. I think a lot of people who were still skeptical went back to work in January having fully embraced it.
Since the start of the year, the number of CI jobs running on Blacksmith has grown more than 7x. We see customers adopt coding agents, produce way more PRs, and then run into the next problem: how do you actually validate all of this code and get it merged?
There are a lot of people working on making code easier to produce. What I find strange is how little attention goes into everything that has to happen after the code is written and before it can be merged. The labs and hyperscalers are mostly focused elsewhere, yet developers and agents spend an enormous fraction of their time here.
A lot of companies touch parts of this problem. For us, it’s *the* problem. We started Blacksmith by building a much better CI cloud, but ultimately what we care about is helping developers and agents validate and merge code faster. I sometimes tell candidates that if we don’t solve the whole thing, I’m not sure who will.
I don’t think we fully appreciate yet how much more software is going to be produced. The infrastructure we have today wasn’t designed for that volume. There’s a lot we need to rethink from first principles, and I think we’re barely scratching the surface.
If you’re extremely good at what you do and this is a problem you want to spend the next several years working on, we’re hiring in SF and NYC: blacksmith.sh/careers
Agentic loops are not magic. At least not on "real-life" engineering workflows.
They are dozens, sometimes hundreds, of calibrations around one hard question: when should the agent act, and when should it stop?
A huge amount of work, rules enforcing, retraining, happens before production.
That’s how we do it at @GetLago!
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!






















