| Aspect | Blacksmith | Depot | BuildJet |
|--------|------------|-------|----------|
| Starting Price | Publishes per-minute pricing for standard Linux images and advertises a free monthly minute allowance (public materials) | Offers a developer plan with included minutes and published per-minute overage in public materials | Publishes baseline per-runner pricing for typical runner sizes in public documentation and advertises a small one-time credit |
| Primary Use Case | Teams using GitHub Actions seeking faster job runtimes, lower per-minute costs in some scenarios, and integrated CI analytics with minimal workflow changes | Teams prioritizing a single-tenant ephemeral EC2 runner model and per-second billing | Teams seeking transparent pricing and defined concurrency caps with per-runner pricing |
| Key Strength | Emphasizes minimal workflow changes and integrated CI analytics (run history, log search, cost breakdowns) | Explicit single-tenant runner model and per-second billing; clear plan structures | Transparent pricing table and explicit concurrency limits |
| Key Weakness | Limited public third-party review volume; enterprise identity/compliance details beyond GitHub SSO are not fully documented publicly; depends on GitHub control plane | Requires organization-owned GitHub repos and plan fees that may be overhead for small usage; still integrates with GitHub control plane | Less public evidence about observability features compared to Blacksmith; enterprise compliance depth less clear in available materials |
- Direct competitors and their key differentiators
- Depot
- Positions runners as single-tenant ephemeral instances and bills by the second without a one-minute minimum in public materials.
- BuildJet
- Publishes per-runner pricing and emphasizes concurrency limits and capacity controls.
- WarpBuild
- Offers performance-focused runners and describes enterprise options that include dedicated deployments (not fully analyzed here due to limited source retrieval in this review).
- Feature comparison: where this vendor appears to excel vs lag behind
- Potential advantages
- Observability features for GitHub Actions runner usage (CI analytics dashboard, global log search, run history, cost breakdown views) are prominent in vendor documentation.
- The vendor documents an isolation model using Firecracker microVMs and provides a narrative around cache architecture and cache token models.
- Potential gaps
- Public review ecosystem maturity is limited (few public reviews on major platforms in accessible searches).
- Some competitors publish explicit single-tenant guarantees and per-second billing granularity.
- Pricing comparison: value proposition vs alternatives
- Blacksmith vs GitHub-hosted
- Public GitHub rates provide context for the vendor’s pricing claims. The vendor’s baseline Linux price undercuts some published GitHub rates, but true savings depend on runner equivalence (vCPU, RAM, I/O) and workload characteristics.
- Blacksmith vs Depot
- Both list similar baseline per-minute pricing for a Linux runner in public materials; Depot’s model includes plan fees and included minutes, while this vendor lists a free-minute allowance and additional storage add-ons.
- Customer testimonials comparing products
- Community discussions indicate buyers primarily compare these vendors on economics, billing granularity, and isolation guarantees.
- Market share and adoption trends
- The vendor reports several thousand engineering teams and many millions of jobs monthly; these are vendor-reported figures and were not independently verified in this review.
- Press coverage summarized vendor-reported revenue figures and customer counts for 2025.
- When customers choose competitors instead (and why)
- Buyers requiring strict single-tenant isolation and per-second billing may select vendors that document those guarantees.
- Buyers seeking to leave GitHub Actions entirely may evaluate other CI/CD platforms that offer end-to-end CI solutions separate from GitHub Actions.