Runners for every repository.
On your servers or ours.
Every CI job gets a fresh microVM next to a cache that is already warm. Repositories on Fir run Fir Actions on Frazer Runners, with Frazer CI. Repositories that stay on GitHub run their Actions jobs on GitHub runners. One rate and one bill for both.
Where your code lives decides.
Each product has its own page.
- Code on Fir
Frazer CI on Frazer Runners
Native CI for repositories on Fir. Fir Actions declare each task’s inputs, so a task whose inputs did not change is answered from its signed result before any machine starts.
- Definitions
- Fir Actions in
.frazer/ci/ - Free
- 200 minutes a month on a standard 4 vCPU runner
- Cache hits
- Free: no machine starts
- Code on GitHub
GitHub runners
Your GitHub Actions workflows, unchanged except one line:
runs-on: frazer-8c. Each job gets a fresh microVM, and agent pull requests get their own lane, cap and daily budget.- Definitions
- Your GitHub Actions workflows
- Free
- No free minutes
- Your servers
- No per-minute fee
The same machines and the same cache.
Never the same pool.
A fresh microVM per job
Its own kernel, never reused; nothing survives the job.
Your servers or the fleet
On your servers, runners are part of the per-core server fee. On the Frazer fleet, billed per second with no minimum.
A cache that is already warm
One cache per organization per site, shared with devboxes and agent sandboxes. Only trusted builds write what others read. How the cache works.
Agents as their own class
Agent work runs in its own lane with a floor, a cap and a daily budget, so it never starves the jobs people wait for.
Results as data
Every job and task reports structured results over the API and MCP, so agents read results instead of scraping logs.
Separate pools
The two products share the price and the bill, never a host, a pool or a queue.
One rate for both.
Included on your servers.
Frazer CI and GitHub runners cost the same per vCPU-hour on the Frazer fleet, billed per second with no minimum and no rounding up. On your own servers they are part of the per-core server fee.
See every priceRunners, answered.
Which runners does my repository use?
It depends on where the code lives. Repositories on Fir run Fir Actions on Frazer Runners, with Frazer CI. Repositories that stay on GitHub keep their GitHub Actions workflows and run them on GitHub runners.
Can one organization use both?
Yes. Repositories move to Fir one at a time: a converter drafts Fir Actions from your workflows, both run side by side while the repository rehearses, and you switch when every difference is explained. Both products appear on one bill at the same rate.
Are there free minutes?
Frazer CI includes 200 minutes a month on a standard 4 vCPU runner on the Frazer fleet, for every personal account and every organization; public repositories draw from the same minutes. GitHub runners have no free minutes. On your own servers, neither has a per-minute fee.
Do the two products share machines?
They share the machine types, the price and the bill. They never share a host, a pool or a queue, so a burst of GitHub Actions jobs never delays a Fir Actions task, and the other way around.