Aditya Maru (@adityamaru27) header
Aditya Maru (@adityamaru27) profile picture

Co-founder & COO @useblacksmith | Building the fastest way to run your CI.

New York, New York
Joined August 2016
Photo by Aditya Maru (@adityamaru27)Photo by Aditya Maru (@adityamaru27)Photo by Aditya Maru (@adityamaru27)Photo by Aditya Maru (@adityamaru27)Photo by Aditya Maru (@adityamaru27)Photo by Aditya Maru (@adityamaru27)Photo by Aditya Maru (@adityamaru27)Photo by Aditya Maru (@adityamaru27)Photo by Aditya Maru (@adityamaru27)Photo by Aditya Maru (@adityamaru27)
Replying to @useblacksmith
@useblacksmith draws enough power to run one in five homes in Miami Beach, and by next year we’ll be managing a footprint that could power every home in the city. We continue to build a formidable team to scale the CI cloud that every company writing software is going to need.
Replying to @sequoia
@sequoia is leading our Series C at a $1B valuation. We started Blacksmith in 2024 to make CI faster and less painful. In January we ran 5 million CI jobs a week. Today it's over 90 million and growing, and we’re still early.
3
28
1,288
Now more than ever, the devil is in the details. Concurrency caps are one of the biggest handicaps to your developers' productivity.
You can't have fast CI with a concurrency cap. So Blacksmith doesn't have one, and we go to great lengths to keep it that way. Managed CI shouldn't mean managing limits. When your agents open 100 PRs at once, none of them should wait in a queue.
2
14
1,717
Aditya Maru retweeted
Blacksmith (W24) is building a faster cloud for continuous integration (CI), helping developers test and ship code as AI coding tools generate more of it. As software production accelerates, testing and validation are becoming the new bottleneck. That shift has helped @useblacksmith grow 20x over the last year, and the company recently raised a $66 million Series C at a $1 billion valuation. The founders, @adijayaprakash, @aayush_shah15, and @adityamaru27, started as outsiders to DevOps and built their first infrastructure using the same high-performance CPUs found in gaming PCs, renting servers originally designed for Minecraft and Call of Duty. Today, they run a much larger fleet with a team of just 30 people, helping companies cut CI waits from minutes to seconds. They share how they found the idea, won their first 200 customers, and why faster testing will become even more important as agents write more of the world’s code. 00:00 — Making CI Faster With Gaming CPUs 03:46 — Winning Over Investors and Developers 06:46 — Scaling CI for the AI Coding Era
68
29
8
257
40,586
Aditya Maru retweeted
To restore a cache, Blacksmith runners pull from many storage servers at once, and under load those bursts kept stalling. We retuned the network path, and the median restore for caches over 256 MiB fell from 5.5 s to 2.8 s. The slowest 1% went from 35 s to 17 s.
1
3
2
44
3,416
Bazel, Go, Turborepo, what's next? @shreyaskal123 and team are getting very good at engineering default on caching solutions.
Turborepo caching is now on by default for free on Blacksmith. 400+ teams are already using it. One monorepo that runs over a thousand Turborepo tasks a day now sees cached runs finish 97% faster.
17
744
Aditya Maru retweeted
Our CEO @adijayaprakash is live on @etnshow at 9:30am ET to talk about our Series C and what's next for code validation.
GM. Friday. A lot going on. Here's the line up: - @rosstaylor90 (General Reasoning) - @max_buchan (Valarian) - @8eanmurray (Fuse Energy) - @alirhaddad (XRlabs) - @gluk64 (Matter Labs) - Richard Starson (Stellios Technologies) - @adijayaprakash (Blacksmith) See you on the show.
1
1
18
1,575
Aditya Maru retweeted
Blacksmith now supports GitHub Enterprise Server (GHES) and GitHub Enterprise Cloud with data residency. Companies who require their own GitHub instance or a fixed data region no longer have to pick between security and faster CI. Learn how to get set up in the comments.
1
4
1
26
3,479
Aditya Maru retweeted
Blacksmith is in the Disruptors 60 Class of 2026, curated by @GreenfieldVC at @TechCrunch Disrupt. Writing code isn’t the slow part anymore. Every generated change still has to be built and tested before it merges. 10,000+ companies run that step on Blacksmith.
3
2
24
2,216
Aditya Maru retweeted
this is an incredible use of VC money since everyone at the Jay street metro tech station in Brooklyn knows what a CI is (they raised $45 million in august)
46
14
12
536
171,231
another default on, free caching solution to speed up pipelines across the board
Go build caching is now enabled by default for every Blacksmith org, free of charge. Across customer CI jobs, the median Go step got 20% faster and the slowest ones got 74% faster, with one test suite dropping from 58s to 5s. Try now, link in first comment.
7
350
Aditya Maru retweeted
We were fortunate enough to have our CI accelerated and sponsored by @useblacksmith Simply swapping to blacksmith accelerated build times by nearly 2x. We then layered on more improvements. @blankparticle wrote about it here: alchemy.run/blog/2026-09-24-…
1
6
1
36
5,267
Last day in the office where @useblacksmith grew up. It saw a lot of highs and some lows over the past year. Next week, we move somewhere with room to match our ambitions. You're all invited once the coffee machine is working.
4
1
30
746
Aditya Maru retweeted
Nothing feels as good as optimizing whole CI pipeline performance 🤌 Down to ~3min from sporadic 12-15min with flaky runs on top. Over 4-5x improvement over 2k runs every week adds up quickly, but most of all, the amount of frustration and context-switching decreases 😌
5
4
19
522
Whenever the team at @useblacksmith can't stop using something before we launch it, developers end up feeling the same way. Proof is going to be good.
Fixing 11 ~1px layout shifts and asking for a [code]smith Proof feels like magic
3
381
Imagine running agents on your boy’s hotspot at the Beford L grind sesh
42
30
30
1,246
189,883
Aditya Maru retweeted
Can't thank enough @useblacksmith for sponsoring the @pnpmjs ci infra
2
1
1
43
3,895
Aditya Maru retweeted
Agents were shipping code faster than our CI pipeline could keep up. Our team optimized our pipeline, leading to a roughly 15% faster test suite and 50% reduction in runner-time spent per test, all while our test suite grew 4x in size. @moofeez explains how: linear.app/now/ci-bottleneck…
37
20
19
490
147,579
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
We 3x'ed PRs in 6 months at Amplitude by building an autonomous software factory: - PR cycle time 5.2 hours to 44 minutes - Frontend CI: 30 minutes to 3-4 minutes - Bug reports down 55% - 5% of our PRs now come from designers and product managers - 3x the PRs with the same headcount What worked: faster CI, risk-based auto-approval, automated legacy migrations, and the hardest part: cultural changes in the team. amplitude.com/3x Bonus: our designers even built out an interactive video game you can play to tell the story. Data monster speedruns the development pipeline.
3
3
23
1,821
Aditya Maru retweeted
I agree with Marc. Reviewing code produced by AI will soon feel as antiquated as reviewing the assembly produced by a compiler.
There's been a ton of talk about the role of humans in code review, and when and how humans should be signing off on changes. I believe that, long-term, humans have no role in routinely reviewing code.
1
2
8
1,124
Today, a lot of code review is about finding bugs or mistakes. As the amount of code being written explodes, I think we’ll care more and more about “evidence of correctness” that a change does what it’s supposed to do before we merge it. Code review and testing share an important limitation: not finding a bug isn’t the same as proving there isn’t one. Reminds me of this Dijkstra quote: “Program testing can be used to show the presence of bugs, but never to show their absence!”
There's been a ton of talk about the role of humans in code review, and when and how humans should be signing off on changes. I believe that, long-term, humans have no role in routinely reviewing code.
5
2
31
4,383
Aditya Maru retweeted
Next up on First Pass: A conversation with @adijayaprakash from @useblacksmith Everyone knows about the GPU crunch, but the CPU crunch is getting equally painful. In this episode we talk about the nuances of CPU clouds and how agents are driving a surge of CPU demand
4
3
1
23
7,340