GitHub Actions at up to 10× less compute cost.

Each job runs on its own spot VM in your AWS, GCP or Azure account. Your cloud bills you, so your cloud credits apply.

# Paste into Claude Code, Codex, or another coding agent
set up https://backmesh.com/SKILL.md

Try free, no credit card required.

Install manuallySee the costs
One install across three cloudsGitHub's queued jobs go to one backmesh install, which runs each on its own spot VM in AWS, Google Cloud or Azure.GitHub$ backmesh installAWSGCPAzure
  • No cloud keys storedInstall connects each cloud with a role from your own cloud CLI session.
  • Your code never reaches usCode, secrets, caches and logs go between GitHub and your runners, never to backmesh.
  • One small event per jobIt describes the runner and never names the repo, workflow, job or branch. What's sent
  • CI rides out our outagesRunning jobs finish, and new ones keep starting through a backmesh.com outage of up to about 30 minutes.

150,000 minutes a month: $1,800 on GitHub, $210–$260 on backmesh.

4-vCPU Linux jobs on AWS, each on its own spot VM; the range runs over the VM types a job may get.

GitHub-hosted$1,800
backmesh on AWS$120–$173+ $0.40–$0.58 per 1,000 jobs for their VMs' boot, about 30 s each
backmesh on Azure$80–$89+ $0.53–$0.69 per 1,000 jobs for their VMs' boot, about 60–70 s each
backmesh on GCP$214–$291+ $1.43–$2.27 per 1,000 jobs for their VMs' boot, about 60–70 s each
Compute a month: GitHub's list price against the clouds' spot prices on 2026-11-07, one VM per job, without disks. The headline adds AWS's fixed cost. It leaves out each job's VM boot, which the tiles price per 1,000 jobs, and runners the planner starts that no job takes, so it's a floor; see What does it cost?

Try free, no credit card required.

backmesh's core features are free. Your clouds bill you for the VMs your jobs run on.

Jobs start in seconds, not minutes.

Your coding agent tells backmesh when its pre-push checks start, so the run's first jobs start in a median 17 s instead of 100.5 s (measured on AWS).

Learn moreAgent instructions
Your coding agent
# your agent's pre-push checks start
$ backmesh cue --in 120
Cued acme/app main.
# two minutes later
$ git push
What your coding agent runs before it pushes. Measured on AWS on 2026-11-10: 24 jobs with a cue sent 120 s ahead and 24 without, 8 per push; 20 of the 24 cued jobs found a runner already started.

Pick the cloud per workflow.

Each label runs in one cloud. Out of spot capacity, the next VM type launches, never the next cloud. Spot by default; backmesh-od-* labels for jobs that shouldn't be interrupted.

Learn more
strategy:
  matrix:
    cloud: [aws, gcp, azure]
runs-on: backmesh-${{ matrix.cloud }}-4
  • backmesh-aws-4test · aws
  • backmesh-gcp-4test · gcp
  • backmesh-azure-4test · azure

Every job log ends with what it used.

Peak memory, OOM kills, CPU and disk, to size each job.

Learn more
Job log
backmesh: resources over 312 s,
sampled every 5 s
  Memory  peak 9.8 GiB of 15.5 GiB,
          0 OOM kills
  CPU     average 2.41 cores,
          peak 3.91 of 3.98
  Disk    work directory peak 3.4 GiB

One status for every cloud.

Runner VMs, queue, 24 h and 7 d job times, and month-to-date cost, in one command.

Learn more
backmesh status
$ backmesh status
Runners: each job runs in its own VM
  backmesh-aws-4: 6 assigned, 6 running
    24 h: 42 jobs; queued to started
      p50 21 s, p95 1.6 min
Cost since 2026-11-01: $41.80
Abridged; the numbers here and below are illustrative.

One GitHub App, and what its key can do.

Four permissions, its webhook off, and its key held by backmesh, never in your accounts. The same key works in every org that installs the App.

Learn more

Its key can

  • Register a runner in any runner group and take its jobs, with their code and secrets
  • Dispatch or rerun a workflow
  • Change the OIDC subject claim your cloud trust policies match on
  • Read, cancel or delete runs and logs
  • Write check runs

It can't

  • Read code through the API
  • Manage repository secrets
  • Change administration settings
  • See org members

Before you install

Will it work?Linux x86-64 only. Private repos only.
  • No macOS, Windows, Arm or GPU runners.
  • Public repositories can't use the runners.
  • Each job waits for its own VM to boot: about 30 s on AWS, 60–70 s on GCP and Azure. For a run's later jobs, the planner mostly hides it, and your coding agent's cue hides it for the first ones.
  • A reclaimed spot VM fails its job. When reclaims were the run's only failures, backmesh reruns the failed jobs once the run finishes, up to twice.
  • Each job starts with an empty Docker layer cache.
Is it safe?Each job gets its own VM.
  • Jobs from every repo in the org use the same labels.
  • Run code you trust as you trust your org's members.
  • Per-repo isolation is planned.
What does it cost?No VM while idle.
  • Your clouds bill you directly.
  • Your cloud credits apply.
  • Idle: only the control plane, about $86 a month on AWS, $74 on GCP, $111 on Azure.
  • Each job's VM bills from its boot until the job ends, then goes.

One install. Your clouds. Your bill.

# Paste into Claude Code, Codex, or another coding agent
set up https://backmesh.com/SKILL.md

Try free, no credit card required.

Install manually