Depot CI runs your workflows on Depot's own orchestration and compute. Depot GitHub Actions runners give your GitHub Actions jobs faster machines and caching while GitHub continues to schedule the workflow. Both use GitHub Actions YAML. You can use either product or both in the same Depot organization.
Choose where your workflows run
Use Depot CI when you want Depot to handle the whole CI run. It starts jobs in pre-warmed Linux sandboxes, includes Depot Cache, and lets you run workflows against uncommitted changes from your terminal. Engineers and coding agents can fetch logs, retry jobs, and debug a sandbox through the Depot CLI.
Use Depot GitHub Actions runners when you want to keep your workflows in GitHub Actions and speed up the jobs.
Change the runs-on label in your existing workflow. GitHub continues to handle triggers, job dependencies,
secrets, and the Actions UI; Depot provides the runners. Linux, macOS, and Windows runners are available.
| Depot CI | Depot GitHub Actions runners | |
|---|---|---|
| Workflow files | .depot/workflows/ | .github/workflows/ |
| Schedules jobs and handles dependencies | Depot | GitHub Actions |
| Operating systems | Linux on x86_64 and Arm64 | Linux, macOS, and Windows |
| GitHub repository ownership | Personal accounts and organizations | Organizations |
| Logs and job details | Depot dashboard and CLI | GitHub Actions logs, plus Depot job metrics |
| GitHub Actions outages and slowdowns | Don't stop or delay your jobs | Delay or block job dispatch |
| Included compute allowance | Shared sandbox minutes | GitHub Actions minutes |
The Depot CI quickstart walks through migrating a workflow and checking compatibility. The runner quickstart connects your GitHub organization and configures runner labels. For a comparison with other CI platforms, see GitHub Actions alternatives.
Keep CI running through GitHub Actions incidents
Depot CI runs on Depot's own control plane and CI engine. Depot schedules each job, resolves dependencies between jobs, and starts the sandbox, so GitHub Actions outages, queue delays, and degraded performance don't stop or slow your Depot CI runs.
Depot GitHub Actions runners speed up the jobs themselves, but GitHub still dispatches every job to them. When GitHub Actions is degraded, those jobs wait for GitHub like any other runner.
Depot CI still receives repository events from wherever your code is hosted. Standalone Depot Code repositories and Origin-hosted repositories, including mirrors detached from GitHub, send events to Depot directly. Repositories that Origin mirrors from GitHub still receive their events through GitHub. For repositories on GitHub, steps that call GitHub, such as API requests or downloads from GitHub releases, still need GitHub to respond. The GitHub outage guide covers moving those dependencies.
Use Depot CI with macOS and Windows runners
You can run your Linux workflows on Depot CI and keep macOS and Windows workflows in GitHub Actions on Depot runners. For example, a mobile app can run its Linux build and test workflow in Depot CI while its Xcode build runs on a Depot macOS runner. A Windows desktop build can stay on a Depot Windows runner.
Keep those macOS and Windows workflow files in .github/workflows/. Select their labels from the
runner types reference. Put the Linux workflows you move to Depot CI in
.depot/workflows/. macOS and Windows runner labels belong to the GitHub Actions product; they don't select a
macOS or Windows environment in Depot CI.
If your current workflow has one matrix covering all three operating systems, split the Linux jobs into a separate
workflow before moving them to Depot CI. A needs dependency can't connect a Depot CI job to a GitHub Actions job.
Keep dependent jobs together, or coordinate the separate workflows explicitly. Update your branch protection rules
to require the checks from both systems. Depot CI reports its jobs as GitHub checks.
Choose one workflow to publish each release or deploy each service. Keeping the same deployment enabled in both systems would run it twice. The mobile build guide covers Xcode, Gradle, signing, and Android Emulator tests.
Understand the two compute allowances
Both products track usage by the second, with no one-minute minimum per job. They draw from separate included allowances on your Depot plan:
- Depot CI shares sandbox minutes with Sandboxes and Managed Agents. Included minutes are measured at 2 vCPUs; a 4-vCPU job running for one minute uses two included minutes. On Developer and Startup plans, additional compute is billed per vCPU-second.
- GitHub Actions runners use the GitHub Actions minutes allowance. Runner type and size determine the minute multiplier and the price for additional usage. The runner pricing tables list those rates.
You can use both allowances in the same organization. Unused GitHub Actions minutes don't become sandbox minutes, or vice versa. See pricing for included usage and current rates.