Pay for the memory your job needs.
A job that peaks at 13 GB does not need eight cores, so FlameWill does not charge for them. Each job runs on its own machine, billed per second, and nothing costs anything while you have no jobs.
Launch prices: in preview, nothing is billed yet
flamewill-arm-2c8g
2 vCPU, 8 GB
$0.0006
per minute, $0.036 per hour
For jobs that peak at up to 6.5 GB, with 110 GB of local NVMe.
The same job: $0.0025/min on Blacksmith, $0.005/min on GitHub.
flamewill-arm-2c16g
2 vCPU, 16 GB
$0.001
per minute, $0.060 per hour
For jobs that peak at up to 14.5 GB, with 110 GB of local NVMe.
The same job: $0.008/min on Blacksmith, $0.012/min on GitHub.
flamewill-arm-4c32g
4 vCPU, 32 GB
$0.0013
per minute, $0.078 per hour
For jobs that peak at up to 30.5 GB, with 220 GB of local NVMe.
The same job: $0.010/min on Blacksmith, $0.022/min on GitHub.
Compared job by job
The fair comparison is the cheapest runner on each that can hold the same job, not the price of a minute alone.
| Compared | FlameWill | GitHub-hosted | Blacksmith |
|---|---|---|---|
| Price for a 2.5 GB job | $0.0006/min | $0.005/min | $0.0025/min |
| Price for a 13 GB job | $0.001/min | $0.012/min | $0.008/min |
| Price for a 15 GB job | $0.0013/min | $0.022/min | $0.010/min |
| Memory per vCPU | up to 8 GB | 4 GB | 3 to 4 GB |
| Linux on ARM64 | |||
| Linux on x64 | Coming | ||
| Windows and macOS | |||
| Dependency cache with no workflow change | Faster actions/cache | ||
| Docker layer cache | Coming | ||
| Cost and peak memory of each job | In the job’s log | In a dashboard |
Prices from each vendor’s own price page on 24 Oct 2026: GitHub, Blacksmith. GitHub does not state its larger runners’ memory; we assume the 4 GB per vCPU of its standard ones. FlameWill’s prices are launch prices.
What the price includes
- The machine for the seconds your job runs, on AWS in Stockholm. No idle time, no standing fee.
- Local NVMe for the job’s work folder, and its public network address.
-
The npm cache, restored and saved for every job, and
fw-cachefor anything else you keep. - The report at the end of every job: peak memory, CPU time, and what the job cost.
Try it on your most expensive job.
Change one label, read the cost at the end of the log, and decide.