Skip to content

Graphide CI

10× faster CI, kept fast by AI agents

Your GitHub Actions jobs run on our runners. A team of agents keeps every job fast as your code changes, on every repo.

Backed by Y Combinator
aquasecurity/trivyBuild Test
GitHub-hosted runner23m 33s
Graphide CI30s

47× faster1

Change one line, and agents keep your CI fast

  1. Change one line

    Point runs-on at Graphide. Nothing else changes.

  2. Run on our runners

    Warm machines, sized to each job.

  3. Agents keep it fast

    Every job retuned as your code changes.

Ten long open-source CI jobs, timed on both1

JobGitHubGraphide CIFaster
aquasecurity/trivyBuild Test23m 33s30s47×
coredns/corednsTest Makefile.release17m 42s24s45×
tokio-rs/tokiomiri-test19m 58s50s24×
rclone/rclonebuild (other_os)4m 24s11s24×
bytecodealliance/wasmtimeMiri (wasmtime-cli)21m 42s1m 14s17.6×
bytecodealliance/wasmtimeMiri (component)11m 32s46s15.1×
rust-lang/futures-rscargo miri test10m 35s52s12.2×
rust-lang/hashbrownmiri6m 56s36s11.7×
microsoft/playwrightMCP (firefox)29m 54s2m 39s11.3×
webpack/webpacktest26227m 45s2m 35s10.7×

Every job runs in its own sandbox

How we keep jobs apart
  • One machine per job

    Fresh for every job, destroyed after.

  • Walled off

    No reach to other jobs or private networks.

  • Secrets stay with the job

    They reach only the machine running the job.

Graphide review

PR review that finds real bugs, with few false alarms

Works on its own, or beside Graphide CI.

Known bugs caught, of 363

  1. Graphide review26
  2. Greptile21

False alarms per clean PR3

  1. Graphide review0.02
  2. Greptile0.11

Built by Dan McGee and Benjamin McIntyre in San Francisco

Questions

Does Graphide CI ever change whether a job passes?

No. If a test fails on our runners, the job fails.

How do we start?

Book a call, or install the Graphide GitHub App and press Switch to Graphide CI on a repository. That opens one pull request that changes its Linux jobs’ runs-on line.

What does it cost?

Graphide CI is one fixed monthly price, quoted from what you run today. PR review is $1 per pull request after the first 10. See pricing.

Where does our code go?

We read only the repositories you turn on. We never train a model on your code and never sell it. Privacy policy.

One fixed monthly price for your CI

Try it free for 7 days or $10 of CI usage, whichever comes first. Nothing is charged.

How we measured
  1. 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.

  2. 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.