Blacksmith CI Platform Boosts Code Validation Speed and Growth

•

 9 min video

•

 5 min read

YouTube video ID: S-2kdhU74lQ

Source: YouTube video by Y Combinator — Watch original video

PDF

Blacksmith is a company that provides infrastructure to run Continuous Integration (CI) checks rapidly. CI is the process developers use to validate their code, ensuring nothing is broken before shipping. Blacksmith has experienced significant growth, expanding 20x in the past year and recently raising a $66 million Series C round at a billion-dollar valuation, led by Sequoia.

The Bottleneck of Code Validation

With the rise of agentic coding tools, developers are writing more code than ever before. However, the ability to ship this code has become the new bottleneck. It's not useful to write 100 times more code if it cannot be validated and shipped at the same speed. This validation process, primarily waiting on CI to ensure tests pass and the code works, is where Blacksmith steps in.

Origins and Naiveté

The founders of Blacksmith were outsiders to the platform engineering and DevOps space, none of them having written a CI pipeline before. This "naive enough in the right way" approach allowed them to pursue an unconventional solution without prematurely dismissing a good idea. The CEO always aspired to start a company in Silicon Valley, drawing inspiration from technology companies he read about in high school. He attended the University of Waterloo, known for its strong startup program and technical founders. Blacksmith is his second application to Y Combinator.

The three co-founders were friends from undergrad in Toronto, all engineers who recognized a universal problem: CI infrastructure "sucked" due to its slowness and difficulty to manage. They believed they had a better way.

The Mismatch and the Solution

Initially skeptical, their conviction grew with research. They observed that the characteristics of CI workloads are fundamentally different from what hyperscalers like AWS, GCP, and Azure are optimized for. Hyperscalers excel at multi-threaded execution, but CI workloads, much like desktop applications or video games, prioritize single-thread execution speed. This mismatch was the root cause of the pain.

Blacksmith's solution was to build a cloud specifically designed for CI workloads, leveraging the "best tool for the job." They started by renting servers from a German data center company known for hosting Minecraft and Call of Duty game servers. As they scaled, they began to own more of the stack, now operating at much larger agreements with data center providers, effectively buying megawatts of power instead of individual machines.

An early investor, who led Blacksmith's initial Y Combinator round and later their Series A, found their use of gaming CPUs for CI particularly innovative and unusual. This approach, which involved deploying hundreds of these powerful, single-thread optimized machines, was a key differentiator.

The "Special Sauce": Caching and Customer Acquisition

A significant factor in Blacksmith's speed is its ability to skip redundant work through intelligent caching. Their "special sauce" involves moving cache artifacts physically close to the compute nodes, minimizing latency.

Acquiring the first 200 customers was challenging. They initially leveraged friends working at companies to get a foot in the door, securing logo rights to build credibility. With these logos, the CEO personally reached out to CTOs, VPs of Engineering, and platform engineers. Their earliest customers were small companies, similar to Blacksmith itself, who prioritized speed and had minimal red tape. The key to winning over engineers, they found, was superior performance and solving problems in ways engineers couldn't easily do themselves. Engineers are discerning and willing to try new tools, though they aren't always the "stickiest" customers.

Impact and Growth

Blacksmith's ease of use and performance allowed them to secure large five- and six-figure contracts without a dedicated sales team. They offer a one-click solution to switch over CI.

A notable example is Langchain, which previously ran its CI on GCP. Developers there routinely waited 15-20 minutes just to acquire compute. On Blacksmith, this wait time plummeted to 10-15 seconds due to an effectively infinite pool of compute, drastically improving developer velocity.

Blacksmith is now focused on a massive marketing campaign in San Francisco and New York, including taking over 15 subway stations and wrapping a subway train in their bright yellow color, to ensure that any engineering team considering CI velocity or code trust immediately thinks of Blacksmith.

The team has grown from five people to 30, with 12 engineers, managing a cluster that has scaled by many orders of magnitude. This growth is attributed to:

  • Bespoke software: For fleet management and observability across the stack.
  • Ruthless focus on product surface area: Keeping the product small and manageable, scaling it only with team size rather than accommodating every bespoke customer requirement. This focus allows a small team to manage a large number of machines and customers.

Challenges and Future Vision

One of Blacksmith's biggest challenges is keeping up with demand. New LLM releases, for instance, cause massive spikes in CI usage as developers rush to test and ship code. Since ordering and installing machines takes time, they employ technical creativity, including better job placement algorithms, more efficient job packing, and optimized network topologies, to handle the load.

A power surge in Phoenix, which took out both primary and backup cooling systems in a major data center, highlighted the critical importance of geographical distribution.

Blacksmith's future vision includes autonomous QA, where they gather artifacts like screenshots or video snippets to instill confidence in code changes. With the sheer volume of code being produced, developers will increasingly rely on evidence rather than manual verification. Blacksmith aims to provide this confidence, remove bottlenecks, and enable developers to ship software at the speed of thought.

  Takeaways

  • Blacksmith built a cloud‑native CI service that uses single‑thread‑optimized gaming CPUs, addressing the mismatch between hyperscaler hardware and CI workloads.
  • By physically colocating cache artifacts near compute nodes, Blacksmith’s “special sauce” eliminates redundant work and reduces CI job latency from minutes to seconds.
  • The company grew 20× in a year, raised a $66 million Series C at a $1 billion valuation, and expanded its team from five to 30 while scaling its machine fleet through bespoke fleet‑management software.
  • Early customer acquisition relied on personal outreach and logo credibility, allowing Blacksmith to secure large contracts without a dedicated sales force and to win engineers with superior performance.
  • Future plans focus on autonomous QA with artifact‑based confidence and continued infrastructure innovations to handle spikes from new LLM releases and ensure global reliability.

Frequently Asked Questions

Why does Blacksmith use gaming CPUs for CI workloads?

Blacksmith uses gaming‑grade CPUs because CI jobs are typically single‑threaded and need high per‑core performance, whereas hyperscalers are built for multi‑threaded, distributed workloads. Gaming processors deliver the fastest single‑core speed at lower cost, directly cutting the time each CI task spends on compute.

How does Blacksmith’s caching strategy reduce CI latency?

Blacksmith’s caching layer moves build artifacts physically next to the compute nodes, so subsequent jobs can retrieve them over a local network instead of a distant cloud store. This proximity eliminates network round‑trip delays and prevents re‑executing identical steps, shrinking CI runtimes from minutes to seconds.

Who is Y Combinator on YouTube?

Y Combinator is a YouTube channel that publishes videos on a range of topics. Browse more summaries from this channel below.

Does this page include the full transcript of the video?

Yes, the full transcript for this video is available on this page. Click 'Show transcript' in the sidebar to read it.

Helpful resources related to this video

If you want to practice or explore the concepts discussed in the video, these commonly used tools may help.

Links may be affiliate links. We only include resources that are genuinely relevant to the topic.

Full transcript is not shown on this page

This page focuses on the summary and original notes. For full verification, refer to the original YouTube video.

PDF