Move your CI to FlameWill
Once your organization is added (see Get started), moving a repository is a label change per job.
1. Change runs-on
| what the job ran on | its memory there | FlameWill label |
|---|---|---|
GitHub-hosted ubuntu-latest, private repository |
2 vCPU / 8 GB | flamewill-arm-2c8g |
GitHub-hosted ubuntu-latest, public repository |
4 vCPU / 16 GB | flamewill-arm-2c16g |
Blacksmith blacksmith-2vcpu-* |
8 GB | flamewill-arm-2c8g |
Blacksmith blacksmith-4vcpu-* |
16 GB | flamewill-arm-2c16g |
| anything that peaks above 14.5 GB | — | flamewill-arm-4c32g |
Size by the job’s measured peak memory, never a sibling job’s. Without a measurement, keep the memory the job has today. Every
FlameWill job log ends with a FlameWill: job report line that shows the peak, so after the first run you can size down with
evidence.
2. What is different from a GitHub-hosted machine
- ARM64 (Graviton), not x64. Node, bun, Python, Go, Rust, Java, Docker images with an
arm64variant, esbuild, sharp, workerd and Playwright all run natively. A binary or Docker image published for x64 only will not run. - A lean image, not GitHub’s 60 GB one: see what is preinstalled. Anything else installs as
usual with
sudo apt-get install …oractions/setup-*. - Docker starts on its first use, and its images and layers live on the fast local NVMe disk.
- Disk: the job’s work folder sits on local NVMe (≈ 110 GB on the 2-vCPU classes, ≈ 220 GB on
4c32g). - Fresh machine per job, destroyed after it. The npm cache is restored for you; anything else heavy (
node_modules, browsers, toolchains) can be kept withfw-cache. - Spot: in the rare case AWS takes a machine back, the job fails with “runner lost”. Re-run it from GitHub.
- Start time: a job waits for a machine to boot, about 45 to 60 seconds today. FlameWill keeps no idle machines waiting, because idle machines are paid for.
3. Secrets and environments
Repository and environment secrets, OIDC (id-token: write) and protection rules work exactly as on GitHub-hosted runners: they
belong to GitHub, not to the machine.
4. Roll back
Change the label back. Nothing else on your side depends on FlameWill.
