Breaking
Google Ventures leads $10M Series A - closed in 14 days 3,000+ organizations now run CI on Blacksmith 50M+ jobs processed every month Every job boots a Firecracker microVM in under 3 seconds Up to 2x faster GitHub Actions at roughly half the cost Vercel, Supabase, Mercury & Clerk on board Google Ventures leads $10M Series A - closed in 14 days 3,000+ organizations now run CI on Blacksmith 50M+ jobs processed every month Every job boots a Firecracker microVM in under 3 seconds Up to 2x faster GitHub Actions at roughly half the cost Vercel, Supabase, Mercury & Clerk on board
Company Dossier  /  Developer Tools  /  San Francisco
Blacksmith logo

Blacksmith

The CI cloud rebuilding GitHub Actions from the hardware up - faster builds, lower bills, one line of config.

BLACKSMITH, SAN FRANCISCO - a drop-in runner replacement that boots each job into a Firecracker microVM on bare-metal gaming CPUs. Founded 2024. Backed by Y Combinator and Google Ventures.
2xFaster Pipelines
50M+Jobs / Month
3,000+Organizations
$13.6MTotal Raised
The Story

A compute company, dressed as a build tool

By the YesPress Desk

Ask most engineers where their day disappears and, sooner or later, someone will name the culprit: the pipeline. The commit is pushed, the checks spin up, and then everyone waits. Blacksmith, a San Francisco startup founded in 2024, was built around a blunt observation - that continuous integration is often the slowest and most expensive part of shipping software, and that it does not have to be.

Blacksmith runs GitHub Actions on its own bare-metal hardware. Instead of the general-purpose servers behind most cloud runners, it uses high single-thread gaming CPUs - the kind prized for raw speed - and pairs them with a software stack written specifically for CI. Every job boots into an isolated Firecracker microVM in under three seconds. The pitch is deliberately unglamorous: change one line in your workflow file, keep everything else, and watch your builds finish roughly twice as fast at close to half the cost.

The founders did not arrive at this from theory. Aditya Jayaprakash, Aayush Shah and Aditya Maru met at the University of Waterloo and went on to build large-scale distributed systems at Faire and Cockroach Labs. At Faire, Jayaprakash - who goes by JP - watched how directly build and deploy speed tied to the business. "Every minute of downtime is a minute of lost revenue," he recalled of that period. Conversations across the industry kept surfacing the same complaint: fast compute was hard to get instantly, pricing was unpredictable, and no one could see where the time actually went.

We're building a CI cloud - a hardware-software stack designed from first principles to provide best-in-class compute, observability and security for CI workloads.

- Blacksmith, on its mission

That framing matters. Blacksmith is not trying to build a prettier dashboard on top of someone else's cloud. It owns the layer that competitors rent, which is what lets it undercut GitHub's runner pricing by 60% or more. As the team puts it, if your bread and butter is compute, it makes sense to control the metal it runs on.


The Problem It Solves

Where the minutes go - and how Blacksmith claws them back

Reported performance vs. standard GitHub-hosted runners
Single-thread CPU~2x
Cache throughput (~400 MB/s)up to 4x
Docker builds on cached layersup to 40x
Cost vs. GitHub runners-60%

The bottlenecks Blacksmith targets are the ones every team quietly tolerates. Cloud runners lean on general-purpose CPUs; Blacksmith uses faster silicon. Cache typically lives far from the job; Blacksmith co-locates it so artifacts download at roughly 400 MB/s. Docker layers get rebuilt from scratch each run; Blacksmith persists them on local NVMe, making cached builds dramatically faster.

The result is a compounding effect. A pipeline that was slow because of hardware, then slow again waiting on cache, then slow once more rebuilding containers, gets attacked at all three points. For teams pushing dozens of commits a day, minutes saved per run turn into hours saved per week.


Products & Services

Three layers of a CI cloud

Compute first, then observability, then security
SHIPPING

Blacksmith Runners

A drop-in replacement for GitHub Actions runners. Jobs run in isolated Firecracker microVMs on bare-metal gaming CPUs, with co-located cache and persistent Docker layers. One line of config to switch.

SHIPPING

Blacksmith Console

Observability built for CI - global log search, pipeline debugging, performance metrics over time, and inline failed-test reporting posted directly on your pull requests.

Blacksmith Sandboxes

On-demand, isolated compute environments - the next layer of the CI cloud, extending Blacksmith's microVM stack beyond the pipeline.


Who Uses It

Trusted by teams that ship constantly

3,000+ organizations - 30K+ developers - grown largely by word of mouth
VercelSupabaseMercury ClerkAshbyVEED ExpensifyDescriptMintlify PostHogGitbookPlex ChromaExaFinch

Blacksmith's growth has come mostly through developers telling other developers - the kind of adoption that is hard to buy and hard to fake. Its customers are startups and scale-ups that live in their pipelines: infrastructure companies, AI teams, and product shops where a slow CI queue is felt across the whole engineering org.


How It's Different

Owning the metal, not renting the cloud

The managed-runner space is crowded - WarpBuild, BuildJet, Namespace, Depot and others all promise faster GitHub Actions, and self-hosted runners on AWS or GCP remain the do-it-yourself default. Blacksmith's distinction is where it sits in the stack. Many rivals resell hyperscaler compute; Blacksmith runs its own bare-metal fleet, which is what makes both the speed and the price hard to match.

The other differentiator is scope. Blacksmith frames CI through a hierarchy of needs: compute at the base, observability above it, security above that. Runners solve the first, the Console the second, and its Firecracker isolation and SOC 2 posture the third. The bet is that teams want one purpose-built stack rather than a runner here and a monitoring tool there.

Owns bare-metal hardwareYES
Firecracker microVM isolationYES
Built-in CI observabilityYES
SOC 2 compliantYES
Migration effort1 line

Funding & Milestones

$13.6M raised, twice from the same investor

Google Ventures backed Blacksmith at seed, then led its Series A four months later
2024

Founded & launched via YC

Three Waterloo classmates launch Blacksmith out of Y Combinator's Winter 2024 batch and ship their first runners.

MAY 2025

$3.5M Seed round

Led by Google Ventures and Y Combinator, joined by angels including Spencer Kimball, David Cramer and Kelsey Hightower.

2025

Scale milestone

Crosses 3,000+ organizations and 50M+ CI jobs run per month.

SEP 2025

$10M Series A

Google Ventures doubles down, leading a Series A that closes in just 14 days.

ARR TRAJECTORY

~$1M → ~$3.5M

Annual recurring revenue grew several-fold while the team stayed small - roughly 4 people in May, about a dozen by September.

Google Ventures doubled down on Blacksmith just four months after its seed round.

- TechCrunch, September 2025

Where It Fits

A wedge into the developer-infrastructure market

Blacksmith enters at the exact point where teams feel pain daily and switching is cheap: the CI runner. That wedge - one line of config, immediate speed - gives it a foothold that broader platforms struggle to defend. From there, its roadmap points toward a fuller CI cloud spanning compute, observability and, with Sandboxes, on-demand isolated environments.

The timing lines up with a broader shift. As AI-assisted development pushes more code through pipelines faster, the cost and speed of CI become harder to ignore. Blacksmith's fundraise pitch leaned on exactly that: fast CI as a way to unblock modern, high-velocity software teams. Whether it grows into the category-defining CI cloud its founders describe is still an open question - but the traction, and the fact that a serious investor wrote a second check before the first was spent, suggest the problem is real.


Frequently Asked

The short version

What does Blacksmith do?

Blacksmith runs your GitHub Actions on bare-metal gaming CPUs as a drop-in replacement for GitHub-hosted runners, making CI pipelines up to 2x faster at roughly half the cost.

How does Blacksmith make CI faster?

It uses high single-thread gaming CPUs, boots each job into a Firecracker microVM in under 3 seconds, co-locates cache at ~400 MB/s, and persists Docker layers on NVMe for up to 40x faster cached builds.

Who uses Blacksmith?

Over 3,000 organizations - including Vercel, Supabase, Mercury, Clerk, Ashby and Expensify - run more than 50 million CI jobs a month on the platform.

Who funds Blacksmith?

It's backed by Google Ventures and Y Combinator, with a $3.5M seed in May 2025 and a $10M Series A led by Google Ventures in September 2025.

Is Blacksmith secure?

Yes. Jobs run in isolated Firecracker microVMs on Blacksmith's own hardware, and the company is SOC 2 compliant with security features built specifically for CI workloads.

Links & Sources

Go deeper