Blacksmith Sandboxes Coming soon
Aug 12, 2026
 ]

Announcing Blacksmith’s Series B led by Peak XV Partners

Aditya Jayaprakash
Co-founder, CEO
TL;DR
We raised a $45M Series B led by Peak XV. With AI codegen tools, developers are writing more code than ever. We’re building the infrastructure to validate it.
Get started!
Try us Free

We're happy to share that we've raised a $45M Series B led by Peak XV, with our existing investors, YC and GV, tripling down. The round valued Blacksmith at $550M.

We raised the round in March 2026, but we never got around to announcing it. But hey, better late than never.

The Claude Opus 4.5 drop in December last year meaningfully changed the way developers write software. Since the start of the year, the number of CI jobs run on Blacksmith has grown by 5–10% week over week, as more engineers adopt AI codegen tools. Every model improvement has expanded what coding agents can do and led to even more code being produced. All of that code still has to be validated and tested, and we've rapidly grown alongside our customers. Today, more than 6,000 companies run CI on Blacksmith, including Supabase, Clerk, Ashby, and Mercury.

Since March, we've heard versions of the same story from customers again and again:

"Our developers adopted Claude Code, PR volume increased 4x, and our CI infrastructure can't keep up. We're now having incidents almost every week that block engineers from merging code."

Two and a half years ago, we started Blacksmith with the goal of building a CI cloud with purpose-built infrastructure to run these workloads much faster. That remains our foundation, but the problem we want to solve is broader: we want to help developers validate and merge code faster. CI is a part of that, but the goal is to build a platform that gives developers confidence in every change they make.

We recently launched [code]smith, our cloud coding agent that you can delegate tasks to. It can build features and fix bugs, but it is also deeply integrated into the validation loop: diagnosing and autofixing CI failures, keeping PRs green, and helping developers merge code quicker.

[code]smith is also the foundation for what we're building next, including [code]smith QA, which will autonomously test changes before they're merged.

The volume of code produced over the coming decade is only going to explode. We're going to help developers (and agents) validate and merge that code a lot quicker.

What are we gonna do with this money?

Compute. We're building a cloud and that ain't cheap. We currently manage in the order of hundreds of thousands of cores of compute, with plans to grow that footprint by an order of magnitude in the coming months. The main reason we raised this capital was to expand our compute footprint and get more aggressive about staying ahead of demand.

Are you hiring?

Yes, we're hiring across the board in NYC and SF. Given there's a high likelihood you're an engineer reading this, you should really consider joining us. You'll work with an exceptional team on hard systems problems and products developers genuinely love using. Here are some problems our team is working on.

On Peak XV

I met Shailendra and Arnav for the first time over Thai food in Menlo Park. They understood the big picture rather quickly. I liked that they knew developer tools and product-led companies, having also backed Supabase and PostHog. They're genuine and hungry. I'm really glad we partnered with them.

World globe