Blacksmith

Name: Blacksmith
Brand: Blacksmith

AI NativeLeader

The fastest way to run your GitHub Actions. Trusted by Ashby, Supabase, VEED, and 1000+ others.

Est 2024|Valuation $616.3M|Raised $125.3M|47 Ref Customers

LinkedIn 5K|Web traffic 72K|FTEs 29|HQ San Francisco, CA

MarketsContinuous Integration & Continuous Delivery (CI/CD)

Published Oct 15, 2026

01Common complaints

- If strict single-tenant compute guarantees are required by default - The vendor documents a multitenant model with microVM isolation; organizations that require dedicated single-tenant hosts by policy may prefer vendors that explicitly provide single-tenant or dedicated-host contracts. - If SAML/SCIM-based enterprise identity lifecycle management is mandatory - The vendor’s public security documentation emphasizes GitHub single sign-on. Organizations requiring SAML-based IdP integration with SCIM provisioning should confirm support directly with the vendor. - If independently validated benchmarks and extensive third-party reviews are required - Public review volume for this vendor is limited in accessible review platforms; buyers in regulated industries or those requiring extensive third-party validation should seek additional references or vendors with broader review footprints. - If workflows are dominated by very short jobs and billing granularity matters - If billing is rounded by the minute, short jobs may be less efficient compared with per-second billing offered by some competitors; confirm billing granularity. - If the organization requires near-zero tolerance for dependency on the GitHub control plane - The vendor relies on the GitHub control plane for job orchestration; documented incidents in vendor status pages show that upstream control-plane behavior can affect job adoption and execution. - Current limitations acknowledged by the vendor - The vendor documents some features as beta (for example, certain local agent-first features) and at times separates GA features from beta or add-on features in public materials. - Features on the roadmap - Public launch and roadmap materials have historically referenced incremental rollout of caching and persistence features; buyers should confirm GA status for specific features. - Scale limitations - The vendor publishes statements about large-scale capacity and high concurrency; contractual limits, fair-use policies, and actual provisioning behavior should be confirmed in enterprise contracts. - Security or compliance gaps - SOC 2 Type 2 compliance is documented by the vendor. - Coverage for other regimes (HIPAA, PCI DSS, ISO 27017/27018) and identity lifecycle provisioning (SCIM) was not clearly documented in public sources. - Performance/reliability limitations - Vendor status pages document incidents caused by internal reconciliation bugs and by upstream GitHub control-plane behavior. - API limitations or integration constraints - The product’s operation depends on GitHub integration and job adoption via GitHub’s control plane; GitHub outages or control-plane issues can affect job start and session creation.

02Why they buy

- Documented vendor differentiators and evidence - Independent validation is limited due to low public review volume; press coverage and investor materials provide some third-party visibility but do not substitute for broad user reviews. - Features and capabilities that appear distinctive in vendor materials - Integrated observability for GitHub Actions runner usage: CI analytics dashboard, global log search, run history, and cost breakdown views are featured in vendor documentation. - SSH-based debugging workflows tied to GitHub authentication (documented as an available administrative feature). - Differentiation from competitors based on available documentation - There is limited neutral review content to conclude strong differentiation based on user sentiment; documentation and feature sets provide primary evidence for positioning. - Areas where competitors have clearer public advantages - Some competitors document single-tenant models and per-second billing; these are clearer differentiators for buyers requiring those specific attributes.

03Field reports

- Review platform availability and limitations - G2 - The vendor’s G2 seller page shows no public reviews and indicates insufficient public feedback to provide broader buying insight. - Gartner Peer Insights - No product-specific Gartner Peer Insights reviews for this vendor were found in accessible search results (Gartner Peer Insights is often gated). - TrustRadius - No TrustRadius product page or reviews for the vendor were found in accessible search results; searches frequently returned unrelated products. - Vendor-published testimonials (presented as vendor marketing) - The vendor’s pricing page includes customer testimonial excerpts. Examples attributed to vendor customers include statements that the vendor reduced test times and provided responsive support. These testimonials are published by the vendor and should be treated as vendor-provided marketing content. - Community discussions (anecdotal and mixed) - Public community threads (e.g., Reddit) show early-stage buyer interest and anecdotal reports of perceived speed improvements; these posts are informal and not controlled benchmarks. - Community discussion also highlights general buyer concerns about third-party runner economics and dependency on the GitHub control plane. - Independent blog-style content - An independent blog post described perceived performance improvements in hands-on testing; methodology and representativeness are not controlled, so these should be treated as anecdotal evidence. - Negative or critical observations - Structured negative review content on major review platforms is limited, likely reflecting overall low review volume rather than a comprehensive signal. - Community threads raise general concerns that can apply to third-party runner services (cost surprises, dependency on GitHub control plane), but repeated, vendor-specific negative reports were not abundant in accessible sources. - Common reasons customers appear to choose this vendor (inferred from sources) - Desire for minimal workflow changes when replacing runners. - Interest in reduced CI runtime and improved caching throughput compared with typical GitHub-hosted runner configurations. - Preference for avoiding the operational burden of self-hosted runners. - Reasons customers might discontinue use (inferred; not strongly evidenced) - Changes in GitHub pricing that affect the comparative economics of third-party runners. - Reliability incidents or upstream GitHub outages that materially affect job adoption and availability. - Enterprise identity or compliance requirements that exceed what the vendor supports through GitHub SSO-based authentication.

Vendor-published outcomes

The vendor publishes performance claims such as substantial improvements in runner speed and cache download throughput. These claims are vendor-published and the benchmarking methodologies are not always disclosed in detail.
The magnitude of performance improvement is workload-specific (for example, CPU-bound compilation or Docker-heavy builds may see larger gains than network-bound tests).

Evidence of outcomes from third-party or semi-independent sources

Press coverage and some individual user blog posts reference reduced test times in specific cases; these are useful as anecdotal evidence but are not controlled independent benchmarks.

Mixed or negative case outcomes

The vendor’s incident postmortems show periods of degraded performance that prospective buyers should consider when assessing operational risk.

04Best fit

- Company sizes - Likely best fit - Organizations with engineering teams ranging from small startups to larger development organizations, or companies where CI minutes represent a significant cost and cycle-time constraint. - Startups and scale-ups experiencing rapidly increasing CI usage. - Also plausible - Enterprises that require SOC 2 vendor compliance and prefer a managed runner offering, subject to validation of identity and compliance needs. - Industries and verticals - Software companies with extensive test suites, monorepos, compiled language projects, container builds, and frequent pull request activity. - ML/AI development teams with heavy CI iteration workloads. - Roles and personas - Decision makers - VP Engineering, Head of Platform/Developer Experience, DevOps/SRE leadership, and Security/Compliance teams responsible for vendor risk. - End users - Developers and release engineers who experience slow CI feedback loops. - Pain points the product addresses - Long pull request feedback cycles due to CI runtime. - High GitHub Actions compute spend in organizations with large CI needs. - Operational overhead of maintaining self-hosted runners. - Qualification criteria: what makes a suitable fit - The organization uses GitHub Actions and prefers to avoid rewriting pipelines. - CI workloads are likely to benefit from faster compute or improved cache throughput. - The team values integrated observability features for CI performance and cost analysis. - Deal disqualifiers: what makes a poor fit - Organizations that require enterprise IdP SAML and SCIM provisioning as a mandatory requirement (capabilities may need to be validated). - Workloads that require fully custom runner images or very specific infrastructure control, which may be better served by BYOC/self-hosted options. - Teams with very low CI volume where switching costs outweigh potential savings.

05The pitch

What the product does (core value proposition in objective terms)

- Blacksmith is a managed CI runner platform for GitHub Actions designed to be configured as a replacement for GitHub-hosted runners (Linux, Windows, macOS) by changing workflow runner labels. The vendor reports objectives in the areas of: - Speed — the vendor reports notable performance improvements for certain workloads. - Cost — the vendor reports lower per-minute rates versus GitHub-hosted runners and potential savings from shorter runtimes. - Observability — searchable run history, log search, and cost and cache analytics. - Debugging — for example, SSH access into running jobs when enabled. - Architecturally, Blacksmith runs jobs in ephemeral Firecracker microVMs on bare metal and colocates cache storage near compute to reduce network/cache latency. This description reflects the vendor’s documentation.

Target market and market positioning

- Target users - Engineering teams that use GitHub Actions and seek different performance, reliability, or cost characteristics than GitHub-hosted runners. - Teams that prioritize minimal workflow changes for adoption (migration typically involves changing workflow runner labels in YAML). - Positioning - Positioned as a managed runner option with integrated CI analytics and observability features; positioned as an alternative to: - GitHub-hosted runners (simple managed offering but may be costlier at scale) - Self-hosted runners (flexible but requires operational management) - Other runner-focused vendors (examples: Depot, BuildJet, WarpBuild)

Get a comprehensive analysis of Blacksmith including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →