Graphide CI
10× faster CI, and a team that tends it
Graphide CI runs the GitHub Actions workflows you already have on our runners. Then an AI and our engineers look after every job as your code changes, so your own engineers don’t have to.
Our target is 10–20× faster than GitHub’s hosted runners and a CI bill 70% or more lower. These are targets, not guarantees: they depend on your repository and the size of the deal, and larger deals get the most. Tuned by hand, ten long open-source CI jobs ran 10× to 47× faster.1
Moving a job is one line:runs-on: ubuntu-latestbecomesruns-on: graphide
Free for 7 days or $10 of usage, whichever comes first, and nothing is charged. Then we quote one fixed monthly price. Talk to us for a quote
or paste this into Claude Code, Codex or Cursor
Read https://graphide.com/setup.md and set me up with Graphide.47× fasterThe same job with the same results: GitHub’s median of 10 runs, without the disk clean-up step our runs left out, against our two runs of November 5, 2026.1
We garden your CI, so your engineers don’t have to
Fast runners are the start. An AI watches every job you run on them, and our engineers check its work and take it further.
Tuned to each job
Each job gets a machine sized to what it does, with its dependencies, toolchains and build outputs warm before it starts. Where a check shows every result stays the same, a long test step is split so its tests run side by side.
Kept tuned as your code changes
New dependencies, new tests and new workflows slow CI down over time. We keep tending your jobs as they change, so they stay fast as your team and your code grow.
Never at the cost of your results
Speed changes never touch your repository. Each is proved on a copy of it and reviewed by our team before it reaches your jobs. A fix that belongs in your code, such as a flaky test, comes as a pull request you review.
The job as written, on a GitHub-hosted runner
- Start a runner
- Install dependencies
- Build
- Tests, one after another
The same job on Graphide CI
- Start warm
- Build from cache
- Tests, in 64+ lanes
Ten long open-source CI jobs, timed on both
The same job from nine projects, on GitHub’s standard hosted runner and on Graphide CI, with the same results on both. Each project links to its runs on GitHub.1
| Repository and job | GitHub, 4 vCPU | Graphide CI | Faster |
|---|---|---|---|
| aquasecurity/trivyGo · Build Test | 23m 33s | 30s | 47× |
| coredns/corednsGo · Test Makefile.release | 17m 42s | 24s | 45× |
| tokio-rs/tokioRust · miri-test | 19m 58s | 50s | 24× |
| rclone/rcloneGo · build (other_os) | 4m 24s | 11s | 24× |
| bytecodealliance/wasmtimeRust · Miri (wasmtime-cli) | 21m 42s | 1m 14s | 17.6× |
| bytecodealliance/wasmtimeRust · Miri (component) | 11m 32s | 46s | 15.1× |
| rust-lang/futures-rsRust · cargo miri test | 10m 35s | 52s | 12.2× |
| rust-lang/hashbrownRust · miri | 6m 56s | 36s | 11.7× |
| microsoft/playwrightTypeScript · MCP (firefox) | 29m 54s | 2m 39s | 11.3× |
| webpack/webpackJavaScript · test262 | 27m 45s | 2m 35s | 10.7× |
* Our runs used 64 vCPU machines, but with the time saved the final price ends up cheaper than GitHub.
One fixed monthly price for your CI
No plans to pick and no per-minute bill. Teams with large CI bills can talk to us first and skip the trial.
Start free
Install the GitHub App and move a job. The trial runs for 7 days or $10 of usage, whichever comes first, and nothing is charged. It is there so we can see how your CI runs.
Get a quote
We reach out with one fixed monthly price for your CI, set from what you run today. It stays fixed unless your usage grows a lot.
We keep tending it
Our runners, the AI and our team, for that one price. Your engineers stop looking after CI.
Every job runs in its own sandbox
On Microsoft Azure, in the western US. The details are in CI security and accounts and access.
One job, one machine, then it’s destroyed
Each job gets a fresh micro-VM (Cloud Hypervisor), or a whole VM for 16 and 32 vCPU runners, and nothing else runs on it.
Walled off
A job’s machine can’t reach other jobs or any private address. Pull requests from forks run on hosts with no trusted machines.
Secrets stay with the job
Secrets reach only the machine running the job, as on any self-hosted runner. Runner registrations are encrypted (AES-256-GCM), with keys in Azure Key Vault. We keep job records and test results, not your logs.
Graphide review
Works with or without Graphide CI
A pull request review that finds bugs, with few false alarms
Agents write more code than a team can read. Graphide review reads each pull request with the code it touches, and checks each finding a second time before it posts it.
- Graphide review26 of 360.02 false alarms
- Greptile21 of 360.11 false alarms
It reads past the diff
Beside the change, it reads the code the change calls and is called by, and the rules you wrote for the repository.
It says how it knows
Each finding says how it was checked and how sure the review is, so you can tell a traced bug from a hunch.
It does not hold your merges
It blocks a merge only if you make its check a required check in GitHub.
run now packs the whole starting environment, base64-encoded, into one exported variable.
Linux caps a single environment string at MAX_ARG_STRLEN (128 KiB). If the starting environment is larger than about 96 KiB, exec "$bin" fails with E2BIG ('Argument list too long') and grail does not start at all. The script itself documents being started from a dev shell (a Graphide terminal), which is exactly where environments get large.
How it breaks. Startrunfrom anix developshell, or any shell whoseenv -0is over ~98,000 bytes. base64 grows that by 4/3, so GRAIL_DESKTOP_ENV=<~131k bytes> is over the 131072-byte per-string limit, and the finalexec "$bin" "$@"fails. Before this change the same launch worked.
Graphide · agent · 55% sure · in the change · likely · Open in Graphide
How we know: we traced it
The verify stage read the code and judged it real, and rare. Not run: the stages that write a test and run it on old and new code were off for this review.
Graphide’s review of a change to our own code, October 27, 2026.
About us
Dan and Ben met in middle school in Cincinnati and have built things together ever since. Graphide is in San Francisco.
Backed by Y Combinator
Dan McGee
CEO, co-founder
Built Matrix, Illumio’s policy simulation platform, then left UC Berkeley to start Graphide.

Benjamin McIntyre
CTO, co-founder
Founded UC’s Linux and FOSS club; studies Computer Engineering and Mathematics at UC.
Questions
Does Graphide CI ever change whether a job passes?
No. If a test fails on our runners, the job fails. Nothing moves until you press Switch to Graphide CI on a repository: that opens one pull request that changes its Linux jobs’ runs-on line, which you can revert like any other change.
Will the review hold up our merges?
No. It holds a merge only if you make its check a required check in GitHub.
Do we need both CI and review?
No. Each works on its own, and one free trial covers both.
How do we start?
Sign up, install the Graphide GitHub App and start your free trial. Review starts on your next pull request. For CI, press Switch to Graphide CI on a repository of your GitHub organization, or ask your coding agent to: one pull request changes its Linux jobs’ runs-on line.
What does it cost?
Graphide CI is one fixed monthly price per Graphide org, which we quote from your current usage. Start free for 7 days or $10 of CI usage, whichever comes first, with 10 free reviews; nothing is ever charged automatically. PR review past those is $1 per pull request. See pricing.
Where does our code go?
Graphide reads only the repositories you turn on and keeps a copy to check their changes. It never trains a model on your code, never sells it, and collects no telemetry except agent signals: your coding agents tell us when they start, push or merge, never your code. If your agent asks Graphide to test a commit, that commit is sent for the test. Turn signals off in your org’s Settings. More in the privacy policy.
For anything else, write to hello@graphide.com.
Where the numbers come from
Every number on this page, what was measured and when.
Ten long open-source CI jobs, timed on GitHub-hosted runners and on Graphide CI
Our runs were made on November 5, 2026, by hand, on our own copy of each project, with changes to how the job runs and none to what it tests. We picked each job’s warm machine image ourselves, and ran on 64 or 128 vCPUs; GitHub’s standard hosted runner for open-source projects has 4, and a customer’s runners on Graphide CI go up to 32 today. GitHub’s time is its own run of the same job: the median of its recent runs or its run at the same commit, and for rclone its fastest run with a warm cache. Steps left out on our side: trivy’s disk clean-up (also taken off GitHub’s time), rclone’s upload, library install and two cache steps, and webpack’s Codecov upload (GitHub’s 10-second median for it is added to ours). Ours is runner start to finish, without time in the queue. Every test name and result (for a build job, every target built) was compared with GitHub’s log of the same job. Eight of the ten are Rust Miri or Go jobs, and how much faster your own job gets depends on what it does.
Known bugs caught by Graphide review and by Greptile, on the same pull requests
74 real pull requests, 68 of them from one open-source project (typescript-go), held out while we tuned the reviewer, carrying 36 known bugs. Graphide review as it ships today ran on them once on October 26, 2026; Greptile’s reviews of the same pull requests were judged on October 24, 2026. The same grader, which was not told which tool wrote what, matched each tool’s findings to the known bugs and counted its false alarms on the pull requests with no known bug.
Start free, then get a quote
Install the GitHub App and move a job with one line. Nothing is charged: we reach out with a fixed monthly price.