GitHub Actions that pay for the memory they use

you pay per second for what it used

$3.00 of jobs free every month.

The same jobs, side by side

Public repositories' jobs run on a GitHub-hosted runner and on Play Compute, from the same commit.

The race loads with the page.

Per second, memory you used

vCPUs are billed per second at the size you asked for. Memory is billed per second on what the job actually used, not on the size's maximum.

A GitHub-hosted runner bills its whole machine for every minute it starts. Play Compute bills the memory a job is using, second by second.

Pay for the memory a job used

Price your month

One line to switch

  1. 1

    Install the App

    Pick the repositories it may serve. It never reads your secrets.

  2. 2

    Review the pull request

    It changes runs-on and nothing else, with a size suggested for each job.

  3. 3

    Merge it

    The next push runs here, with the same actions, caches and secrets.

Questions

Is a job isolated from other jobs?

Yes. Each job gets a new microVM with its own kernel, and the machine is deleted when the job ends. Jobs share nothing but the caches you save.

How do I switch back?

Change runs-on back, for one job or for all of them. There is no contract to end and nothing to uninstall first.

What is on the machine?

An image that follows GitHub's ubuntu-24.04 runner image: the same languages, Docker, browsers and tools, with passwordless sudo, so setup actions find what they expect.

How long can a job run, and how many at once?

Up to 6 hours, as on GitHub-hosted runners. We set no limit on how many jobs run at once.

What does a slow queue or a lost job cost me?

Nothing. Billing starts when the runner picks up the job, and a job lost to the platform is re-run without a charge.

Try it on your next push

Join the waiting list