Skip to content
Sengi

GitHub Actions runner benchmarks: 12 open-source builds on Sengi and GitHub’s runner

How long do open-source builds take on Sengi and on GitHub’s runner, and what do they cost?

Measured November 17, 2026 on 12 open-source projects, each built at a pinned commit with its own CI commands, on Sengi runners with the same 4 vCPU as GitHub’s runner: building all 12 once cost $0.094 on Sengi Basic 4 vCPU against $0.624 on GitHub-hosted 4 vCPU, and Sengi Basic 4 vCPU cost less per build on 12 of 12. Sengi Basic 4 vCPU took less time than GitHub’s runner on 9 of 12 projects and more time on 3 (Codex CLI, Mastodon and Guava). Sengi Premium 4 vCPU took less time than GitHub’s runner on 11 of 11 projects; Mastodon had too few runs to compare because 1 of 3 runs on Sengi Premium 4 vCPU failed. Times are median job seconds over at least 3 runs; these results cover these builds only. 3 jobs failed, all on Sengi runners, and none is counted in any median. Mastodon on Sengi Basic 2 vCPU and Mastodon on Sengi Premium 4 vCPU: Sengi's build cache served a truncated layer, a short read ending in unexpected EOF, so the Docker image build failed. TypeScript on Sengi Basic 2 vCPU: the compiler test suite failed on mocha test timeouts.

Measured November 17, 2026, last checked November 17, 2026. Every number on this page is in one JSON file and a CSV file, and every median links to its run log in the public repository sengirunners/benchmarks.

Results at 4 vCPU: GitHub’s runner, Sengi Basic 4 vCPU and Sengi Premium 4 vCPU

One row per project and runner. Time is the median job run time in seconds, from the job’s start to its end, over the runs counted; min and max are the fastest and slowest of those runs. Cost per build is the median of the runs’ billed minutes, each job rounded up to a whole minute, at the runner’s list price. A cell with fewer than 3 runs prints “not enough runs”.

Median job time, run count and cost per build at 4 vCPU, measured November 17, 2026
ProjectCommitRunnerRunsMedian time (s)Min–max (s)Cost per build (USD)Time against GitHubCost against GitHub
Black87928e6GitHub-hosted 4 vCPU49996–133$0.024baselinebaseline
Black87928e6Sengi Basic 4 vCPU36967–90$0.00430% less time83% less cost
Black87928e6Sengi Premium 4 vCPU36953–82$0.01230% less time50% less cost
GitHub CLIfc4b137GitHub-hosted 4 vCPU4184170–198$0.042baselinebaseline
GitHub CLIfc4b137Sengi Basic 4 vCPU3163161–185$0.00611% less time86% less cost
GitHub CLIfc4b137Sengi Premium 4 vCPU3161153–167$0.01812% less time57% less cost
Codex CLI01fc69fGitHub-hosted 4 vCPU4368347–415$0.084baselinebaseline
Codex CLI01fc69fSengi Basic 4 vCPU3381369–391$0.0144% more time83% less cost
Codex CLI01fc69fSengi Premium 4 vCPU3286279–313$0.03022% less time64% less cost
Mastodon3987b9fGitHub-hosted 4 vCPU4153124–200$0.036baselinebaseline
Mastodon3987b9fSengi Basic 4 vCPU3168115–190$0.00610% more time83% less cost
Mastodon3987b9fSengi Premium 4 vCPU2 (1 failed)not enough runs––––
Flask22d9247GitHub-hosted 4 vCPU42218–29$0.012baselinebaseline
Flask22d9247Sengi Basic 4 vCPU31413–16$0.00235% less time83% less cost
Flask22d9247Sengi Premium 4 vCPU31413–16$0.00635% less time50% less cost
Guava666338cGitHub-hosted 4 vCPU4735730–740$0.156baselinebaseline
Guava666338cSengi Basic 4 vCPU3759754–772$0.0263% more time83% less cost
Guava666338cSengi Premium 4 vCPU3650632–680$0.06612% less time58% less cost
AI SDK45e1fbcGitHub-hosted 4 vCPU4184181–190$0.048baselinebaseline
AI SDK45e1fbcSengi Basic 4 vCPU3164160–173$0.00611% less time88% less cost
AI SDK45e1fbcSengi Premium 4 vCPU3123115–125$0.01833% less time63% less cost
Pydantic001dea0GitHub-hosted 4 vCPU4121113–133$0.030baselinebaseline
Pydantic001dea0Sengi Basic 4 vCPU3106104–112$0.00412% less time87% less cost
Pydantic001dea0Sengi Premium 4 vCPU38983–99$0.01226% less time60% less cost
TypeScript050880cGitHub-hosted 4 vCPU4409372–543$0.090baselinebaseline
TypeScript050880cSengi Basic 4 vCPU3394367–425$0.0144% less time84% less cost
TypeScript050880cSengi Premium 4 vCPU3310308–334$0.03624% less time60% less cost
Vite39ddf7cGitHub-hosted 4 vCPU4259254–266$0.060baselinebaseline
Vite39ddf7cSengi Basic 4 vCPU3183173–209$0.00829% less time87% less cost
Vite39ddf7cSengi Premium 4 vCPU3190162–240$0.02426% less time60% less cost
Vue5be58b4GitHub-hosted 4 vCPU46248–68$0.018baselinebaseline
Vue5be58b4Sengi Basic 4 vCPU34847–50$0.00223% less time89% less cost
Vue5be58b4Sengi Premium 4 vCPU34137–42$0.00634% less time67% less cost
fd4f81778GitHub-hosted 4 vCPU47063–72$0.024baselinebaseline
fd4f81778Sengi Basic 4 vCPU34846–53$0.00231% less time92% less cost
fd4f81778Sengi Premium 4 vCPU34441–46$0.00637% less time75% less cost

Sengi Basic 4 vCPU took less time than GitHub’s runner on 9 of 12 projects and more time on 3 (Codex CLI, Mastodon and Guava); building all 12 once cost $0.094 on Sengi Basic 4 vCPU against $0.624 on GitHub-hosted 4 vCPU.

Sengi Premium 4 vCPU took less time than GitHub’s runner on 11 of 11 projects; Mastodon had too few runs to compare because 1 of 3 runs on Sengi Premium 4 vCPU failed; building all 11 once cost $0.234 on Sengi Premium 4 vCPU against $0.588 on GitHub-hosted 4 vCPU.

Median job time at 4 vCPU, by project

Median job time in seconds at 4 vCPU, measured November 17, 2026: Black, GitHub-hosted 4 vCPU 99 s; Black, Sengi Basic 4 vCPU 69 s; Black, Sengi Premium 4 vCPU 69 s; GitHub CLI, GitHub-hosted 4 vCPU 184 s; GitHub CLI, Sengi Basic 4 vCPU 163 s; GitHub CLI, Sengi Premium 4 vCPU 161 s; Codex CLI, GitHub-hosted 4 vCPU 368 s; Codex CLI, Sengi Basic 4 vCPU 381 s; Codex CLI, Sengi Premium 4 vCPU 286 s; Mastodon, GitHub-hosted 4 vCPU 153 s; Mastodon, Sengi Basic 4 vCPU 168 s; Flask, GitHub-hosted 4 vCPU 22 s; Flask, Sengi Basic 4 vCPU 14 s; Flask, Sengi Premium 4 vCPU 14 s; Guava, GitHub-hosted 4 vCPU 735 s; Guava, Sengi Basic 4 vCPU 759 s; Guava, Sengi Premium 4 vCPU 650 s; AI SDK, GitHub-hosted 4 vCPU 184 s; AI SDK, Sengi Basic 4 vCPU 164 s; AI SDK, Sengi Premium 4 vCPU 123 s; Pydantic, GitHub-hosted 4 vCPU 121 s; Pydantic, Sengi Basic 4 vCPU 106 s; Pydantic, Sengi Premium 4 vCPU 89 s; TypeScript, GitHub-hosted 4 vCPU 409 s; TypeScript, Sengi Basic 4 vCPU 394 s; TypeScript, Sengi Premium 4 vCPU 310 s; Vite, GitHub-hosted 4 vCPU 259 s; Vite, Sengi Basic 4 vCPU 183 s; Vite, Sengi Premium 4 vCPU 190 s; Vue, GitHub-hosted 4 vCPU 62 s; Vue, Sengi Basic 4 vCPU 48 s; Vue, Sengi Premium 4 vCPU 41 s; fd, GitHub-hosted 4 vCPU 70 s; fd, Sengi Basic 4 vCPU 48 s; fd, Sengi Premium 4 vCPU 44 s. Black, GitHub-hosted 4 vCPU 99 s Black, Sengi Basic 4 vCPU 69 s Black, Sengi Premium 4 vCPU 69 s GitHub CLI, GitHub-hosted 4 vCPU 184 s GitHub CLI, Sengi Basic 4 vCPU 163 s GitHub CLI, Sengi Premium 4 vCPU 161 s Codex CLI, GitHub-hosted 4 vCPU 368 s Codex CLI, Sengi Basic 4 vCPU 381 s Codex CLI, Sengi Premium 4 vCPU 286 s Mastodon, GitHub-hosted 4 vCPU 153 s Mastodon, Sengi Basic 4 vCPU 168 s Flask, GitHub-hosted 4 vCPU 22 s Flask, Sengi Basic 4 vCPU 14 s Flask, Sengi Premium 4 vCPU 14 s Guava, GitHub-hosted 4 vCPU 735 s Guava, Sengi Basic 4 vCPU 759 s Guava, Sengi Premium 4 vCPU 650 s AI SDK, GitHub-hosted 4 vCPU 184 s AI SDK, Sengi Basic 4 vCPU 164 s AI SDK, Sengi Premium 4 vCPU 123 s Pydantic, GitHub-hosted 4 vCPU 121 s Pydantic, Sengi Basic 4 vCPU 106 s Pydantic, Sengi Premium 4 vCPU 89 s TypeScript, GitHub-hosted 4 vCPU 409 s TypeScript, Sengi Basic 4 vCPU 394 s TypeScript, Sengi Premium 4 vCPU 310 s Vite, GitHub-hosted 4 vCPU 259 s Vite, Sengi Basic 4 vCPU 183 s Vite, Sengi Premium 4 vCPU 190 s Vue, GitHub-hosted 4 vCPU 62 s Vue, Sengi Basic 4 vCPU 48 s Vue, Sengi Premium 4 vCPU 41 s fd, GitHub-hosted 4 vCPU 70 s fd, Sengi Basic 4 vCPU 48 s fd, Sengi Premium 4 vCPU 44 s
Median job time in seconds, measured November 17, 2026. Sengi runners in blue, GitHub-hosted 4 vCPU in grey. The same rows as the table above.

Not like-for-like: Sengi Basic 2 vCPU and Sengi Premium 2 vCPU

Sengi Basic 2 vCPU has half the cores of GitHub’s 4 vCPU runner. Sengi Premium 2 vCPU has half the cores of GitHub’s 4 vCPU runner. These Sengi runners were run on the same projects; they are not a like-for-like comparison, and no GitHub runner of their size was measured. The last two columns still set each against GitHub-hosted 4 vCPU.

Not like-for-like: median job time, run count and cost per build on Sengi Basic 2 vCPU (half the cores of GitHub’s 4 vCPU runner) and Sengi Premium 2 vCPU (half the cores of GitHub’s 4 vCPU runner), measured November 17, 2026
ProjectCommitRunnerRunsMedian time (s)Min–max (s)Cost per build (USD)Time against GitHubCost against GitHub
Black87928e6Sengi Basic 2 vCPU4117108–123$0.00218% more time92% less cost
Black87928e6Sengi Premium 2 vCPU47773–91$0.00622% less time75% less cost
GitHub CLIfc4b137Sengi Basic 2 vCPU4349340–455$0.00690% more time86% less cost
GitHub CLIfc4b137Sengi Premium 2 vCPU4311305–329$0.01869% more time57% less cost
Codex CLI01fc69fSengi Basic 2 vCPU4764604–2167$0.014108% more time84% less cost
Codex CLI01fc69fSengi Premium 2 vCPU4661540–777$0.03580% more time59% less cost
Mastodon3987b9fSengi Basic 2 vCPU3 (1 failed)208138–1643$0.00436% more time89% less cost
Mastodon3987b9fSengi Premium 2 vCPU4129127–159$0.00916% less time75% less cost
Flask22d9247Sengi Basic 2 vCPU41916–21$0.00114% less time92% less cost
Flask22d9247Sengi Premium 2 vCPU4139–15$0.00342% less time75% less cost
Guava666338cSengi Basic 2 vCPU4971900–2185$0.01732% more time89% less cost
Guava666338cSengi Premium 2 vCPU4813695–941$0.04211% more time73% less cost
AI SDK45e1fbcSengi Basic 2 vCPU4289227–333$0.00657% more time89% less cost
AI SDK45e1fbcSengi Premium 2 vCPU4210184–304$0.01214% more time75% less cost
Pydantic001dea0Sengi Basic 2 vCPU4133118–150$0.00310% more time90% less cost
Pydantic001dea0Sengi Premium 2 vCPU410794–117$0.00612% less time80% less cost
TypeScript050880cSengi Basic 2 vCPU3 (1 failed)583494–701$0.01043% more time89% less cost
TypeScript050880cSengi Premium 2 vCPU4565412–679$0.03038% more time67% less cost
Vite39ddf7cSengi Basic 2 vCPU4459444–500$0.00878% more time87% less cost
Vite39ddf7cSengi Premium 2 vCPU4401368–586$0.02355% more time63% less cost
Vue5be58b4Sengi Basic 2 vCPU48977–128$0.00243% more time89% less cost
Vue5be58b4Sengi Premium 2 vCPU46863–74$0.0069% more time67% less cost
fd4f81778Sengi Basic 2 vCPU47059–100$0.002the same time92% less cost
fd4f81778Sengi Premium 2 vCPU45649–62$0.00321% less time88% less cost

Where did Sengi take more time?

Every result where a Sengi runner’s median was above GitHub’s is printed in the tables above and listed here.

At 4 vCPU, the same size as GitHub’s runner

  • Codex CLI, Sengi Basic 4 vCPU: 381 s against 368 s on GitHub’s runner, 4% more time, at $0.014 a build against $0.084.
  • Mastodon, Sengi Basic 4 vCPU: 168 s against 153 s on GitHub’s runner, 10% more time, at $0.006 a build against $0.036.
  • Guava, Sengi Basic 4 vCPU: 759 s against 735 s on GitHub’s runner, 3% more time, at $0.026 a build against $0.156.

Not like-for-like: smaller or larger Sengi runners against GitHub’s 4 vCPU runner

  • Black, Sengi Basic 2 vCPU: 117 s against 99 s on GitHub’s runner, 18% more time, at $0.002 a build against $0.024.
  • GitHub CLI, Sengi Basic 2 vCPU: 349 s against 184 s on GitHub’s runner, 90% more time, at $0.006 a build against $0.042.
  • Codex CLI, Sengi Basic 2 vCPU: 764 s against 368 s on GitHub’s runner, 108% more time, at $0.014 a build against $0.084.
  • Mastodon, Sengi Basic 2 vCPU: 208 s against 153 s on GitHub’s runner, 36% more time, at $0.004 a build against $0.036.
  • Guava, Sengi Basic 2 vCPU: 971 s against 735 s on GitHub’s runner, 32% more time, at $0.017 a build against $0.156.
  • AI SDK, Sengi Basic 2 vCPU: 289 s against 184 s on GitHub’s runner, 57% more time, at $0.006 a build against $0.048.
  • Pydantic, Sengi Basic 2 vCPU: 133 s against 121 s on GitHub’s runner, 10% more time, at $0.003 a build against $0.030.
  • TypeScript, Sengi Basic 2 vCPU: 583 s against 409 s on GitHub’s runner, 43% more time, at $0.010 a build against $0.090.
  • Vite, Sengi Basic 2 vCPU: 459 s against 259 s on GitHub’s runner, 78% more time, at $0.008 a build against $0.060.
  • Vue, Sengi Basic 2 vCPU: 89 s against 62 s on GitHub’s runner, 43% more time, at $0.002 a build against $0.018.
  • GitHub CLI, Sengi Premium 2 vCPU: 311 s against 184 s on GitHub’s runner, 69% more time, at $0.018 a build against $0.042.
  • Codex CLI, Sengi Premium 2 vCPU: 661 s against 368 s on GitHub’s runner, 80% more time, at $0.035 a build against $0.084.
  • Guava, Sengi Premium 2 vCPU: 813 s against 735 s on GitHub’s runner, 11% more time, at $0.042 a build against $0.156.
  • AI SDK, Sengi Premium 2 vCPU: 210 s against 184 s on GitHub’s runner, 14% more time, at $0.012 a build against $0.048.
  • TypeScript, Sengi Premium 2 vCPU: 565 s against 409 s on GitHub’s runner, 38% more time, at $0.030 a build against $0.090.
  • Vite, Sengi Premium 2 vCPU: 401 s against 259 s on GitHub’s runner, 55% more time, at $0.023 a build against $0.060.
  • Vue, Sengi Premium 2 vCPU: 68 s against 62 s on GitHub’s runner, 9% more time, at $0.006 a build against $0.018.

How was it measured?

  • Time: Job run time, start to end, from the GitHub API. Queue time is kept apart.
  • Runs: Median of the measured runs, with n, min and max; a median needs n >= 3.
  • Cost: Billed minutes (each job rounded up to a whole minute) times the runner's list price per minute.
  • GitHub cost: GitHub does not bill public repositories for this runner; its cost is what a private repository pays at GitHub's listed rate for the measured size.
  • Order: One runner class at a time; at most four jobs at once within a run. One warm-up run per class first fills dependency caches.
  • Selection: The project list is the whole workload list of an existing open-source CI benchmark suite, adopted before running it here. Each project is pinned to a release commit.
  • Exclusions: Every run is listed. A job is left out of the medians only for the reason given next to it.
  • Dates: 2026-11-17 to 2026-11-17.
  • Runner size: the vCPU count printed for each runner was read with nproc inside the job, not taken from a label.
  • Prices: GitHub-hosted 4 vCPU $0.012, Sengi Basic 2 vCPU $0.001, Sengi Premium 2 vCPU $0.003, Sengi Basic 4 vCPU $0.002 and Sengi Premium 4 vCPU $0.006 a minute. GitHub does not bill public repositories for its standard runner, which is 4 vCPU there. The GitHub column is priced at GitHub’s listed rate for its 4 vCPU Linux larger runner (sold to Team and Enterprise Cloud organizations), $0.012 a minute: what a private repository pays for these minutes beyond its plan’s included usage.
  • Queue time is recorded for every run in the data files and is not part of the times above.

Which projects, at which commits?

The project list is the workload list of an existing open-source CI benchmark suite. We adopted the whole list before running it here and did not choose the projects. Each is pinned to a release commit. Every project we ran is shown, including the ones where Sengi took more time. A project is left out only when its build fails on GitHub’s runner as well, and this page lists it with the reason.

ProjectRepositoryLanguageWhat the job runsCommit
Blackpsf/blackPythonPython 3.13 test suite (tox)87928e6d6761a4a6d22250e1fee5601b3998086e
GitHub CLIcli/cliGoUnit and integration tests with the race detector, then a buildfc4b137cdef0a6bd28fd461b7cf9c84a5812a8cd
Codex CLIopenai/codexRustcargo clippy over the Rust workspace, tests included01fc69f4026735edfdf6789820549727a4867b11
Mastodonmastodon/mastodonDockerDocker image build (linux/amd64) after a one-file change, layer cache on3987b9fd624010eeeaeb7cad96606b05aa813f6a
Flaskpallets/flaskPythonPython 3.13 test suite (tox)22d924701a6ae2e4cd01e9a15bbaf3946094af65
Guavagoogle/guavaJavaMaven install and verify on JDK 25666338cc49d5686c07e3e4d17f0aa1cec25a2be6
AI SDKvercel/aiTypeScriptTurborepo build of three Next.js examples45e1fbc3ea10d22f852e12b1c1851e289c85e835
Pydanticpydantic/pydanticPythonpytest suite on Python 3.13001dea020e0809844e5b17666432c9135a976f46
TypeScriptmicrosoft/TypeScriptTypeScriptCompiler test suite on Node 24050880ce59e30b356b686bd3144efe24f875ebc8
Vitevitejs/viteTypeScriptBuild, unit tests and Playwright end-to-end tests on Node 2439ddf7ccf7e7469ff6a3ba37bca38c32ea804d6e
Vuevuejs/coreTypeScriptUnit tests (Vitest)5be58b4c475c1d14b4abacbfeda610394a0ee4e5
fdsharkdp/fdRustcargo build --release, then cargo test4f81778774463bf414a184cbe6d5219ad2229646

The benchmark workflows are at commit e73c896795525a61b47ce9f44657a1a045b0a98b of sengirunners/benchmarks. Project names identify the code that was built; none of the projects is affiliated with Sengi.

Is there a page for each project?

Yes. Each project has its own page with the same numbers for that project alone: its results, where Sengi took more time, any failed job and its run logs.

What was left out?

3 jobs failed, all on Sengi runners, and none is counted in any median. Mastodon on Sengi Basic 2 vCPU and Mastodon on Sengi Premium 4 vCPU: Sengi's build cache served a truncated layer, a short read ending in unexpected EOF, so the Docker image build failed. TypeScript on Sengi Basic 2 vCPU: the compiler test suite failed on mocha test timeouts. Each failed job is also counted in its row’s failures.

  • Run 44030937414: warm-up run: fills each runner's dependency caches first; not measured
  • Run 44033028003: warm-up run: fills each runner's dependency caches first; not measured
  • Run 44037191239: warm-up run: fills each runner's dependency caches first; not measured
  • Run 44039576472: warm-up run: fills each runner's dependency caches first; not measured
  • Run 44041540026: warm-up run: fills each runner's dependency caches first; not measured
  • Job 133910810755: the compiler test suite failed on mocha test timeouts
  • Job 134032483827: Sengi's build cache served a truncated layer, a short read ending in unexpected EOF, so the Docker image build failed
  • Job 134048517537: Sengi's build cache served a truncated layer, a short read ending in unexpected EOF, so the Docker image build failed

Where is the data?

Prices per minute for every runner are on Sengi pricing and in the runner comparison.

Frequently asked questions

Do Sengi runners finish open-source builds in less time than GitHub’s runner?

On these builds, at these commits: Sengi Basic 4 vCPU took less time than GitHub’s runner on 9 of 12 projects and more time on 3 (Codex CLI, Mastodon and Guava); Sengi Premium 4 vCPU took less time than GitHub’s runner on 11 of 11 projects; Mastodon had too few runs to compare because 1 of 3 runs on Sengi Premium 4 vCPU failed. Times are median job seconds over at least 3 runs at 4 vCPU, measured November 17, 2026.

What does a build cost on Sengi Basic compared with GitHub’s runner?

Measured November 17, 2026, building all 12 once cost $0.094 on Sengi Basic 4 vCPU against $0.624 on GitHub-hosted 4 vCPU. Cost is billed minutes, each job rounded up to a whole minute, at the list price: $0.002 a minute for Sengi Basic 4 vCPU and $0.012 for a 4 vCPU GitHub runner.

Why does the comparison use 4 vCPU?

The benchmark runs in a public repository so that every run log is public, and GitHub’s ubuntu-24.04 runner measured 4 vCPU there (nproc inside each job). The Sengi runners with the same vCPU count are compared with it directly; Sengi Basic 2 vCPU has half the cores of GitHub’s 4 vCPU runner, and Sengi Premium 2 vCPU has half the cores of GitHub’s 4 vCPU runner, so they are shown separately and not as a like-for-like comparison.

Why is GitHub’s runner priced if public repositories are not billed for it?

GitHub does not bill public repositories for its standard runner, which is 4 vCPU there. The GitHub column is priced at GitHub’s listed rate for its 4 vCPU Linux larger runner (sold to Team and Enterprise Cloud organizations), $0.012 a minute: what a private repository pays for these minutes beyond its plan’s included usage.

How were the projects chosen?

The project list is the workload list of an existing open-source CI benchmark suite, adopted whole before any of it was run here. Each project is pinned to a release commit. Every project run is shown, including the ones where Sengi took more time.

Where Sengi took more time, is that shown?

Yes. At 4 vCPU: Codex CLI on Sengi Basic 4 vCPU, 381 s against 368 s; Mastodon on Sengi Basic 4 vCPU, 168 s against 153 s; Guava on Sengi Basic 4 vCPU, 759 s against 735 s. 17 more results on smaller or larger Sengi runners, not like-for-like with GitHub’s 4 vCPU runner, took more time than it; all are listed on this page.

Can I check the numbers?

Yes. Every printed median links to the log of the run nearest that median in the public repository sengirunners/benchmarks, at commit e73c896. Every run, failed ones included, is in the JSON file on this page, and the CSV file has one line per project and runner.

Keep your workflow. Cut your runner rate.

Sengi Basic starts at $0.001 a minute for 2 vCPU. Choose 4 or 8 vCPU for $0.002 or $0.004 a minute. Premium stays optional at $0.003, $0.006 and $0.012.

Start without a card ↗︎

See Basic pricing · Switch with your coding agent