Hardware for the work.
Choose 2, 4 or 8 vCPUs with local NVMe storage. Host capacity is shared across isolated runners; each job gets a fresh VM.
GITHUB ACTIONS. SENGI RUNNERS.
Cut your
runner rate.By up to 50%.
Your workflows have places to go.
Your runner bill doesn’t need to follow.
A drop-in switch for supported GitHub-hosted Linux jobs. Built for high-clock CPUs, local NVMe, and fresh VMs on dedicated bare metal.
Runner activation is coming soon.
RUNNER ARCHITECTUREFIG. 01 / SCHEMATIC
One fresh VM. One job.
UBUNTU 24.04 / X642, 4 OR 8 vCPUEXECUTION-SECOND BILLINGNO MONTHLY MINIMUM
01 / THE DIFFERENCEMORE OF YOUR BUDGET. STILL YOUR WORKFLOW.
Same size.
Different rate.
Keep GitHub Actions.
Pay a lower runner list rate.
No assumed speedup required.
| Runner size | GitHub-hosted | Sengi | Lower list rate |
|---|---|---|---|
| 2 vCPU / 8 GB | $0.006 | $0.003 | 50%↘ |
| 4 vCPU / 16 GB | $0.012 | $0.006 | 50%↘ |
| 8 vCPU / 32 GB | $0.022 | $0.012 | 45.5%↘ |
61 seconds. $0.00305.A 2-vCPU Sengi job is billed by execution seconds. GitHub rounds each job up to a whole minute: $0.012 for that duration, before included minutes.
Rates checked September 8, 2026. GitHub comparison: standard private-repository 2-vCPU and larger 4/8-vCPU Linux runners. CPU/RAM match; hardware, storage and images differ. Included standard minutes, free standard public-repository usage, discounts and runtime can change your bill. Larger runners do not use included minutes. Lower list rates do not guarantee a lower total bill.
Pricing & billing increments ↗Standard specifications ↗Larger specifications ↗
02 / THE SWITCHGITHUB IN. GITHUB OUT.
Your workflow.
A different runner.
Same Actions. Same steps. Same GitHub reviews.
Sengi prepares the runner change. You review and merge it in GitHub.
5min
OUR SETUP TARGET
Designed to get your pull request ready within five minutes of connecting GitHub. Timing is not yet measured; approvals, review and builds take their own time.
- 01
Connect & select.
Connect GitHub and choose a repository. Sengi shows which jobs you can switch; you pick the runner size.
- 02
Read the change.
See exactly what Sengi will change. Your build steps, triggers and secrets stay the same.
- 03
Open your pull request.
Click Enable and Sengi creates the pull request for you.
- 04
Let GitHub do its thing.
Review the change and merge when you’re ready. Follow your builds in GitHub as usual.
03 / UNDER THE WORKFLOWBARE METAL. NO INFRASTRUCTURE HOMEWORK.
Built close
to the metal.
High-clock CPUs. Local NVMe.
A dedicated-server foundation for the build.
Without another fleet for your team to maintain.
YOUR REPOSITORYGitHub Actions
ISOLATED EXECUTIONFresh virtual machine
AFTER THE JOBClean up. Start fresh.
Bring your build habits.
Keep your Actions cache steps, Docker builds and familiar Ubuntu tools. Sengi runs the jobs; your workflow stays yours.
Know where the time goes.
See which runners are preparing, waiting or running, how long they’ve spent there, and their vCPU counts. Open any job’s logs in GitHub.
04 / THE PRICEPAY FOR EXECUTION. NOT A SUBSCRIPTION.
A little room.
Or a lot.
Three sizes. Straightforward rates.
Ubuntu 24.04 x64 across the board.
EVERYDAY BUILD & TEST
2vCPU
8 GB RAM
$0.003/ minute equivalent
For focused builds and everyday checks.
PARALLEL WORKLOADS
4vCPU
16 GB RAM
$0.006/ minute equivalent
More room for builds and larger test suites.
DEMANDING BUILDS
8vCPU
32 GB RAM
$0.012/ minute equivalent
Additional headroom for your heavier work.
No monthly minimum.
No idle or provisioning charges.
No idle or provisioning charges.
Pay as you go, billed by execution seconds. Rates above are minute equivalents for comparison. Billing terms will be confirmed before runner activation.
PUT YOUR NUMBERS THROUGH IT
Your next bill.
Minus the guesswork.
An estimate from your execution time.
No assumed speedup. No minimum to hit.
Which workflows does Sengi support?
Linux jobs on Ubuntu 24.04 x64 in private GitHub repositories. Choose 2, 4 or 8 vCPUs. Sengi checks which jobs it can switch before you approve the change; Windows, macOS and ARM jobs aren’t supported.
Do I need to rewrite my workflows?
No. Sengi changes the runner for you in a pull request. Your build steps, triggers and secrets stay the same. Automatic setup supports compatible Ubuntu jobs.
Can I switch back?
Yes. Revert Sengi’s pull request and future jobs use your previous runners again.
How fast will jobs start?
Startup time varies with demand and runner preparation. Jobs start when a runner is ready; they may queue when capacity is busy.
Can I run jobs in parallel?
Yes. Run multiple jobs at once, within your account’s concurrency limit and available capacity. Extra jobs wait in the queue.
What happens to my caches and Docker builds?
Keep using your Actions cache steps and Docker builds. Each job gets a fresh VM, so local Docker layers only carry over if your workflow saves them to a remote cache.
Is there a monthly minimum?
No. Pay only for the execution time you use, billed by the second. No usage means no usage charges.
What about my included GitHub Actions minutes?
They stay with GitHub. Sengi usage is billed separately, so included GitHub minutes don’t reduce your Sengi bill. If GitHub already covers your jobs for free, moving them to Sengi adds a charge.
When can I activate runners, and where can I get help?
Soon. You can create an account now; runner activation is coming next. Check Sengi Help for setup status.