| What changes in your workflow | After 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.” Overview | You 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 result | Depot “runs the entire job using GitHub’s standard runner image on the instance.” Overview | Every 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 sizes | 2, 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 · Overview | One 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/ |
|---|
| Platforms | Ubuntu x64 and Arm, Windows Server 2022 and 2025, and macOS 14, 15 and 26. Runner types | x64 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. Overview | Microsoft 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/ |
|---|
| Caching | Runners are “automatically integrated into our distributed cache architecture”, with “zero configuration required”. Cache entries are scoped by repository. Overview | Dependencies and build caches are already on the runner when the job starts. /docs/ci/ |
|---|
| Who tunes the jobs | You pick each job’s runner label. Analytics track CPU and memory use, with “automated runner sizing recommendations”. Overview | Graphide’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 pay | Published 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 types | A 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/ |
|---|