We raised a $45M Series B led by Peak XV, with YC and GV tripling down. Blacksmith is now valued at $550M. We closed this back in March. CI volume is up 5-10% every week as codegen makes writing code easy and validating it the bottleneck. 6,000+ companies run CI on us. What's the money for? Compute. We're building a cloud and that ain't cheap. We're hiring in NYC + SF. Links below.

Imagine running agents on your boy’s hotspot at the Beford L grind sesh

Most important part missing. Switch to @useblacksmith 🫡

been working on devex with an awesome team, we've seen incredible results by introducing: - automatic PR approvals w/ evals against all historical incidents - 10x faster CI by updating build tools & using @useblacksmith - preview environments for every PR

How do you know when a scheduling approach stops working as you scale? We built simulations to find out, and used them to validate our scheduler designs as we built them. Andrew Werner (@ajwerner) ran them live at infra.nyc last week. Thanks to Megan for having us, and to Chelsea Dole and the other speakers for a great evening. Interactive version + technical deep dive coming this week 👀

Before it became an anvil head, [code]smith almost ended up as a hammer with eyes, a literal blacksmith, or a clanker robot. We tried them all. Here’s the story behind how we designed the character, brought it to life, and made room for some fun personality in a product that takes performance really seriously. Read more here: blacksmith.sh/blog/does-a-co…

Container caching is now on by default for every Blacksmith org. And it’s free. Every Docker-based CI job pulls the same images over and over: Postgres, Redis, Compose stacks, base images. On Blacksmith, those pulls disappear. We persist each org’s Docker image store on a sticky disk, so the images are already local when the next runner starts. No config. No cache keys. No workflow changes. Across six real CI jobs, this made them 25–89% faster end to end. More details in the blog soon.

Heading to LDX3 New York, September 15-16? Come find Blacksmith at booth 102 👋 Waiting on GitHub-hosted runners? Still self-hosting CI? Blacksmith is fast CI for GitHub Actions, running your jobs up to 2x faster on high-performance bare metal. Change one line of YAML and keep your existing Actions and workflows. We’ll handle the autoscaling, caching, and infrastructure behind them. Stop by booth 102 and tell us what your builds look like. #LDX3NewYork #LeadDev #Blacksmith #DeveloperExperience #CICD

Blacksmith now offers zero-configuration remote caching for Bazel. We measured 31% faster p50s and 52% faster p90s across 2000 builds. Most of these customers already had different caching solutions in place. Try it for yourself. docs.blacksmith.sh/blacksmit…

This is the Broadway-Lafayette station this morning. We didn't just buy one ad, we bought the entire station. We plastered every wall, column and stairwell with Blacksmith branding, including four more stations across the city, and another 800 platforms screens inside the cars. It turns out that buying a subway station is its own engineering discipline, but with worse documentation. Why the subway? The parallels with CI were just too good to resist. When you stand on a platform waiting for a train, you're feeling the same pain as an engineer waiting for their CI jobs to run. You probably both check your phone, shift your weight around, and quietly contemplate the universe. When your product cuts down wait times, it makes sense to find where most people spend time waiting. Our timing isn't an accident. Since January, CI jobs running on Blacksmith have grown more than 7x, mostly because coding agents made it easy to produce code faster than anyone can validate it. A lot of the people dealing with that problem ride these trains. So we thought we'd say hello. More coming in October. If you spot us on your commute, take a photo and tag @useblacksmith.

30-80% faster builds with a one-line YAML change.