Skip to content

Compare

Graphide CI or Depot for your GitHub Actions jobs

Both keep your workflows on GitHub Actions and move jobs to their own runners by changing each job’s runs-on line. They differ in what they run, who tunes the jobs and how you pay. Here is what each company’s own pages say, so you can choose for your workflows.

Depot’s side quotes its own pages, read on November 19, 2026. Graphide’s side quotes How Graphide CI works, CI security and Pricing.

Side by side

CriterionDepotGraphide CI
What changes in your workflowAfter you connect your Depot organization to your repository, “switching to Depot is a one-line change to your runner label”, such as runs-on: depot-ubuntu-24.04. “GitHub continues to orchestrate your workflows.” OverviewYou press Switch to Graphide CI on a repository, or ask your coding agent to. Graphide opens one pull request that changes each moved job’s runs-on line to runs-on: graphide; your workflows stay on GitHub Actions. To move back, Switch back to GitHub Actions opens a pull request that puts each line back. /docs/ci/
What runs, and the resultDepot “runs the entire job using GitHub’s standard runner image on the instance.” OverviewEvery test your job runs on GitHub runs on Graphide’s runners too, and a failing test always fails the job: Graphide CI changes how long you wait, never whether a job passes. /docs/ci/
Machine sizes2, 4, 8, 16, 32 and 64 vCPUs for Ubuntu x64, Ubuntu Arm and Windows; 8 vCPUs for macOS. An 8 vCPU Ubuntu x64 runner has 32 GB of memory. x64 runners use AMD EPYC Genoa CPUs, Arm runners AWS Graviton4. Runner types · OverviewOne label: “an x64 Linux machine with 8 vCPUs and 16 GiB”. Jobs that ask for more than 8 vCPUs keep running where they do today. /docs/ci/
PlatformsUbuntu x64 and Arm, Windows Server 2022 and 2025, and macOS 14, 15 and 26. Runner typesx64 Linux: jobs on GitHub’s standard Ubuntu runners or on your own x64 Linux runners. macOS, Windows and Arm jobs, your own runners for another platform, deploy jobs (environment:) and npm provenance publishes keep running where they do today. /docs/ci/
Where jobs run“Ephemeral EC2 instances that are never reused”, single-tenant, “in our cloud or your AWS account”. “No concurrency limits, cache size limits, or network limits.” Egress filtering with allow and deny rules. OverviewMicrosoft Azure, in its West US and West US 2 regions. One job per machine, destroyed when the job ends; an 8 vCPU runner is a virtual machine on an Azure VM that Graphide runs, which several customers’ machines share. /docs/security/ci/
CachingRunners are “automatically integrated into our distributed cache architecture”, with “zero configuration required”. Cache entries are scoped by repository. OverviewDependencies and build caches are already on the runner when the job starts. /docs/ci/
Who tunes the jobsYou pick each job’s runner label. Analytics track CPU and memory use, with “automated runner sizing recommendations”. OverviewGraphide’s agents tune how your jobs run (caches, machines, and test splits where a check shows they are safe), all on our end. /docs/ci/
How you payPublished monthly plans that include a number of runner minutes, then a published per-minute rate; a Business plan is custom. Larger runners use minutes faster. A 7-day free trial, “no credit card required”. Overview · Runner typesA service at one fixed monthly price, quoted from what you run today. A free trial of 7 days or $10 of CI usage, whichever comes first; nothing is ever charged automatically. /pricing/
GitHub account“Depot GitHub Actions runners only support repositories owned by GitHub organizations.” Depot CI, Depot’s own CI engine, also takes personal accounts. Overview“Graphide CI needs a GitHub organization; its runners do not take jobs from a personal GitHub account.” /docs/ci/

Depot’s own speed claims. Depot’s overview says its runners “are up to 3x faster than a GitHub-hosted runner” and give “10x faster caching”. Those are Depot’s figures; we have not tested them. This page states no speed or cost figure for Graphide CI against Depot.

Where Depot fits better

  • Your jobs run on macOS, Windows or Arm. Depot documents runners for all three; Graphide CI moves x64 Linux jobs only.
  • A job needs more than 8 vCPUs. Depot lists sizes up to 64 vCPUs; Graphide CI leaves such jobs where they run today.
  • You want the runners in your own AWS account, or egress rules on what a job may reach.
  • You want published plans and per-minute rates, and to choose each job’s runner size yourself.
  • You build Docker images with Depot’s container builds, which run next to its GitHub Actions runners.

Where Graphide CI fits better

  • You would rather not tune runners yourself: Graphide’s agents tune each job’s caches and machine on our end, and split a test step only where a check shows it is safe.
  • You want dependencies and build caches already on the runner when each job starts.
  • Your jobs are x64 Linux and fit in 8 vCPUs and 16 GiB.
  • You want one fixed monthly price, quoted from your usage, after a trial that never charges automatically.

How to measure it yourself

Neither company’s numbers tell you how your jobs will run. Run your own workload on each runner and time it against a stated baseline.

  1. Pick the workloads

    Choose the x64 Linux jobs you wait on most. Those are the jobs both can run, since Graphide CI moves only x64 Linux jobs.

  2. State the baseline

    Time the same jobs at the same commit on the runners you use today, and write down their size. Compare like with like: at 8 vCPUs, Depot lists 32 GB of memory and Graphide CI’s runner has 16 GiB.

  3. Measure push to verdict

    Count from the push until the check reports pass or fail, queue time included, over several runs of each job. Use the median, not the best run.

  4. Check the verdict

    Compare test names and results in each runner’s log. A faster run that tested less is not the same job.

  5. Read it per workload

    A speedup on one job says nothing about another. Report each job’s result on its own, never as one number for all your CI.

Next steps

  • How Graphide CI works: what moves, what stays, and how to switch a repository and back.
  • Pricing: how the fixed monthly quote and the free trial work.
  • Graphide review is a separate product that checks each pull request with evidence. It works on its own, with or without Graphide CI.

Pages we read

Depot’s pages change. Check them before you decide; where they differ from this page, they are right.

  1. Depot docs: Depot GitHub Actions runners

    https://depot.dev/docs/github-actions/overview · read on November 19, 2026

  2. Depot docs: GitHub Actions runner types

    https://depot.dev/docs/github-actions/runner-types · read on November 19, 2026

  3. How Graphide CI works, CI security and Pricing

    Graphide’s own docs and pricing page, for every Graphide CI cell.