| What changes in your workflow | Each job’s runs-on line changes to a blacksmith-* tag: “Transitioning to Blacksmith is as simple as changing a single line in your workflow file.” A Migration Wizard updates the workflow files. Overview · Quickstart | You press Switch to Graphide CI on a repository, or ask your coding agent to. Graphide opens one pull request that changes each moved job’s runs-on line to runs-on: graphide; your workflows stay on GitHub Actions. To move back, Switch back to GitHub Actions opens a pull request that puts each line back. /docs/ci/ |
|---|
| What runs, and the result | “Blacksmith runners boot off of the same image(s) as GitHub’s runners and have the exact same environment.” Overview | Every test your job runs on GitHub runs on Graphide’s runners too, and a failing test always fails the job: Graphide CI changes how long you wait, never whether a job passes. /docs/ci/ |
|---|
| Machine sizes | 2, 4, 8, 16 and 32 vCPUs for Ubuntu x64, Ubuntu ARM and Windows; 6 and 12 vCPUs for macOS. An 8 vCPU Ubuntu x64 runner has 32 GB of memory. Overview | One label: “an x64 Linux machine with 8 vCPUs and 16 GiB”. Jobs that ask for more than 8 vCPUs keep running where they do today. /docs/ci/ |
|---|
| Platforms | Ubuntu x64 and ARM, Windows Server 2025 (public beta), and macOS “on Apple Silicon M4 chipsets”. On Windows, “Docker Linux containers are not supported”. Overview | x64 Linux: jobs on GitHub’s standard Ubuntu runners or on your own x64 Linux runners. macOS, Windows and Arm jobs, your own runners for another platform, deploy jobs (environment:) and npm provenance publishes keep running where they do today. /docs/ci/ |
|---|
| Where jobs run | Linux and Windows jobs run “in ephemeral Firecracker microVMs”, in us-east (Ashburn), us-west (Phoenix), eu-west (Amsterdam) or eu-central (Frankfurt). “Blacksmith has no concurrency limits.” Overview · Concurrency | Microsoft Azure, in its West US and West US 2 regions. One job per machine, destroyed when the job ends; an 8 vCPU runner is a virtual machine on an Azure VM that Graphide runs, which several customers’ machines share. /docs/security/ci/ |
|---|
| Caching | “All official GitHub and popular third-party cache actions transparently interact with our co-located cache”. Docker layer caching uses Blacksmith’s own build actions and is a paid add-on. Overview · Quickstart · Pricing | Dependencies and build caches are already on the runner when the job starts. /docs/ci/ |
|---|
| Who tunes the jobs | You pick each job’s runner size. Right-sizing “finds jobs on the wrong size and opens a PR to move them”. Run history, logs, SSH access, test analytics and CI analytics are in the product. Overview | Graphide’s agents tune how your jobs run (caches, machines, and test splits where a check shows they are safe), all on our end. /docs/ci/ |
|---|
| How you pay | Published per-minute rates by runner type, 3,000 free minutes a month, paid add-ons (Docker layer caching, sticky disks, static IPs) and an Enterprise plan. Pricing | A service at one fixed monthly price, quoted from what you run today. A free trial of 7 days or $10 of CI usage, whichever comes first; nothing is ever charged automatically. /pricing/ |
|---|
| GitHub account | “Blacksmith is limited to GitHub organizations and not available for personal repositories.” Its GitHub App goes on every repository that uses a blacksmith-* tag. Quickstart · Overview | “Graphide CI needs a GitHub organization; its runners do not take jobs from a personal GitHub account.” /docs/ci/ |
|---|