Blacksmith valued at $1 billion after $66 million Series C
Blacksmith, a platform for building and testing software including AI-written code, has raised a $66 million Series C led by Sequoia at a $1 billion valuation. The company said its annual recurring revenue has grown 17-fold and that it has run more than 90 million continuous integration jobs.
The funding follows rapidly on the company’s $45 million Series B, raised two months earlier at a $550 million valuation. Blacksmith said it has raised $125 million in total. Its customers include Mercury and Granola.
Continuous integration under AI code pressure
Blacksmith was founded to make continuous integration less painful, co-founder and CEO Aditya Jayaprakash said. CI is the process of building, testing, merging and validating code changes through automated checks before software moves forward in development.
The company argues that many organizations are struggling to handle the amount of CI work they need to run, particularly as AI produces more code. Jayaprakash framed the resulting issue as one of trust: as agents write a larger share of software, teams need to establish whether that software can be trusted.
That focus also puts the new round in context with Blacksmith’s $45 million Series B at a $550 million valuation only two months ago, underscoring how quickly Blacksmith’s financing valuation has changed.
What the financing signals for engineering teams
Blacksmith’s reported 90 million-plus CI jobs point to the volume of automated checks being handled on its platform. In a development workflow, each job can build or test a code change, making CI infrastructure part of the process for validating changes before they are merged.
The company’s stated 17x annual recurring revenue growth and its customer list indicate commercial demand for that workflow. The funding does not change the underlying challenge described by Blacksmith: more code generation creates more code that requires building, testing and validation.
For businesses expanding AI-assisted software development, the practical implication is to plan CI capacity and automated validation alongside code-generation tools, so that the pace of new changes does not exceed the team’s ability to test and trust them.