Skip to content
Sengi
Menu

SENGI PREMIUM · BUILT FOR PERFORMANCE

GitHub Actions.
Built for speed.Up to 1.9× faster builds.
Up to 3.8× the builds per dollar.

Your time is worth more.
Run demanding builds on our performance tier.

AMD Ryzen 9 7950X3D CPUs, local NVMe, and a fresh VM for every job. Explore the hardware and the measured build times below. Premium starts at $0.003/min for 2 vCPU; 4 and 8 vCPU are $0.006 and $0.012. Same GitHub Actions. Same one-line change.

.github/workflows/ci.yml1 line changed
  test:-   runs-on: ubuntu-latest+   runs-on: sengi-premium-4-ubuntu-2404    steps:      - uses: actions/checkout@v4
02 / PREMIUM HARDWARE & BENCHMARKSMEASURED AGAINST GITHUB’S UBUNTU-LATEST.

The fastest hardware
for GitHub Actions.

AMD Ryzen 9 7950X3D desktop CPUs boosting past 5 GHz, on bare metal, with local NVMe.
A fresh VM for every job; 2 vCPU jobs ready in 2 seconds.

DOCKER BUILDS

1.9×

Faster Docker builds than GitHub’s runner. A production Docker image in 7m34s on Sengi Premium. 14m36s on GitHub. Same 4 vCPU.

MULTI-CORE CPU

Up to 3×

The multi-core CPU of GitHub’s runner. Every 2 vCPU runner runs on a 16-core AMD Ryzen 9 7950X3D, not a cloud server CPU.

DISK READS

15×

The random-read disk speed of GitHub’s runner. 296k random-read IOPS against 19.6k, and 3× the random writes. Local NVMe on bare metal, not network storage like AWS EBS.

SINGLE CORE

1.65×

Faster single core. 5 GHz desktop CPUs against the server CPUs behind GitHub’s runners.

PRICE PER BUILD

3.8×

More Docker builds per dollar. $0.045 a build on Sengi Premium. $0.175 on GitHub.

RUST, TYPESCRIPT, DOCKER

1.8×

Rust, TypeScript and Docker. 3.6× the builds per dollar. $0.069 on Sengi Premium for the lot. $0.249 on GitHub.

DOCKER LAYER CACHE

1.9×

Faster Docker builds with layer caching. 68 s down to 36 s with a warm type=gha layer cache. Included.

EVERY JOB

Same CPU

One 5 GHz CPU model on every job we ran. GitHub’s jobs landed on four different server CPUs. Sengi Premium: a Ryzen 9 7950X3D, every run.

PRE-BOOTED RUNNERS

2 s

Ready in 2 seconds. Your 2 vCPU job lands on a fresh VM that’s already running. Boot time is never billed.

RunsOn’s open benchmark, same 4 vCPU.

BuildGitHubSengi PremiumFaster
Docker image (PostHog)14m36s$0.175 a build7m34s$0.045 a build1.9×
Rust, TypeScript and Docker together20m43s$0.24911m28s$0.0691.8×
Rust build3m53s$0.047 a build2m25s$0.015 a build1.6×
TypeScript typecheck (opencode)2m14s$0.027 a build1m29s$0.009 a build1.5×

Real CI, same 2 vCPU.

JobGitHubSengi PremiumFaster
Node + Docker build539 s$0.054 a run299 s$0.015 a run1.8×
Vite build and test552 s$0.060 a run328 s$0.018 a run1.68×
Mastodon Docker image build252 s$0.030 a run172 s$0.009 a run1.47×
fd (Rust) build and test76 s$0.012 a run51 s$0.003 a run1.49×
GitHub CLI (Go) test and build367 s$0.042 a run284 s$0.015 a run1.29×

4 vCPU: RunsOn’s open benchmark harness, run on Sengi Premium October 9, 2026, against RunsOn’s published GitHub results. Measured October 2026 against GitHub’s ubuntu-latest, same 2 vCPU. Medians at list prices.

03 / PREMIUM COST PER BUILDFASTER, AND IT COSTS LESS.

Faster builds.
Up to 3.8× the builds per dollar.

Up to half the price per minute.
Builds finish up to 1.9× faster.
Together: up to 3.8× the builds per dollar.

Linux x64 · same vCPU and RAM · Speed and total savings: Rust build on 2 vCPU, Docker build (PostHog) on 4 and 8 vCPU, RunsOn’s open harness, October 9, 2026
Runner sizeGitHub per minuteSengi Premium per minutePer minuteBuilds finishBuilds per dollar vs GitHub
2 vCPU / 8 GB$0.006$0.0032× the minutes / $1.9× faster3.8×
4 vCPU / 16 GB$0.012$0.0062× the minutes / $1.9× faster3.8×
8 vCPU / 32 GB$0.022$0.0121.8× the minutes / $1.5× faster2.7×

Fewer minutes. Each one cheaper.Builds finish up to 1.9× faster, and every minute GitHub bills at $0.006, Sengi Premium bills at $0.003. Boot and teardown are never billed.

GitHub’s published Linux runner rates, September 2026. Builds per dollar vs GitHub: each side’s run time for the same build at its per-minute price. Rust build: 6m50s on GitHub, 3m33s on Sengi Premium. Docker build: 14m36s and 7m34s at 4 vCPU, 9m46s and 6m26s at 8 vCPU.

05 / THE DETAILS

Good
questions.

Something else on your mind?
Sengi Premium Help

What is Sengi Premium?

Sengi Premium is a managed GitHub Actions runner service: the fastest hardware for your jobs, 5 GHz AMD Ryzen 9 7950X3D bare metal with local NVMe and a fresh VM for every job. You keep GitHub Actions, your workflows and your logs; Sengi Premium runs the jobs up to 1.9× faster, delivering up to 3.8× the builds per dollar.

How much do Sengi Premium runners cost?

Sengi Premium charges $0.003/min for 2 vCPU and 8 GB RAM, $0.006/min for 4 vCPU and 16 GB RAM, or $0.012/min for 8 vCPU and 32 GB RAM. Billed per minute of each job, like GitHub; boot and teardown are never billed. No subscription, no minimum. See pricing and the cost calculator.

Do I need to rewrite my workflows?

No. You change one line per job, the runner name, by hand or with your coding agent. Steps, triggers and secrets stay exactly as they are.

Will the PRs my coding agent opens run here?

Yes. Once the runner change is merged, your pushes and pull requests run on Sengi Premium, delivering up to 3.8× the builds per dollar. The more PRs your agents open, the more you save.

Can I switch back?

Yes. Change runs-on back, or revert the pull request, and your next job runs on GitHub’s runners again.

When is Sengi Premium worth it?

Whenever your team pays GitHub for Actions minutes: private-repository CI past your plan’s included usage, every 4 or 8 vCPU job (GitHub bills those at two to nearly four times the Linux rate), and the steady stream of pull requests your coding agents open. On Sengi Premium those minutes cost half as much, $0.003 against GitHub’s $0.006, and builds finish up to 1.9× faster: together, up to 3.8× the builds per dollar.

How do I know which jobs to switch?

Every job on ubuntu-latest or ubuntu-24.04. Sengi Premium is built for Linux x64 on Ubuntu 24.04. The agent prompt finds every one of those jobs for you.

How fast will jobs start?

Sengi Premium keeps 2 vCPU runners pre-booted, so your job lands on a VM that’s already running: ready in 2 seconds. Every job still gets its own fresh VM, boot time is never billed, and your dashboard shows each job’s start and run time.

Are Sengi Premium runners faster than GitHub’s?

Yes. On RunsOn’s open benchmark harness, run October 9, 2026 at 4 vCPU, Sengi Premium builds a production Docker image 1.9× faster than GitHub’s runner, delivering 3.8× the builds per dollar, and runs the Rust, TypeScript and Docker builds together 1.8× faster, delivering 3.6× the builds per dollar. Random disk reads are 15× faster and random writes 3×. A job that finishes sooner bills fewer minutes, so the speed cuts the bill too.

What hardware runs my jobs?

Bare-metal machines built like gaming PCs: AMD Ryzen 9 7950X3D desktop CPUs boosting past 5 GHz, DDR5 memory and local NVMe storage, every one picked for single-core speed. Dedicated bare metal with local NVMe, not network-attached storage like AWS EBS. A 2 vCPU runner gets up to 3× the multi-core and 1.65× the single-core CPU of GitHub’s 2 vCPU runner, and a 4 vCPU runner gets 15× the random-read disk speed and 3× the random writes of GitHub’s. Each job gets its own fresh VM.

Can I run jobs in parallel?

Yes. Matrix and parallel jobs each get their own fresh VM.

What happens to my caches and Docker builds?

They keep working, with no workflow changes, and they’re included. actions/cache and the setup actions’ caches are served from Sengi Premium’s own cache. Docker builds keep their layers between runs with cache-from: type=gha and cache-to: type=gha,mode=max, and run 1.9× faster warm. See Docker layer caching on Sengi Premium.

YOUR WORKFLOW. OUR PERFORMANCE TIER.

Spend less time
waiting on CI.