# Out of GitHub Actions minutes on a personal account? Unlimited private-repo CI

> A personal account gets 2,000 free GitHub Actions minutes a month for private repos on GitHub Free, 3,000 on Pro, on a 2-core runner. Past that, every minute is billed or your jobs stop. Skipbox gives a personal account a 4 vCPU machine for a flat $39 a month with unlimited minutes.

On a personal account, private repositories get 2,000 free GitHub Actions minutes a month on GitHub Free, or 3,000 on Pro, all on a 2-core runner. Once they're gone, GitHub bills every minute, or stops your jobs until the 1st if there's no card on file.

Skipbox gives your personal account its own 4 vCPU machine for a flat $39 a month with unlimited minutes. Change `runs-on` to `skipbox` and the job runs without touching your GitHub minutes.

- $39 a month for 4 vCPU and 16 GB: twice `ubuntu-latest`'s cores, however many minutes you run
- No GitHub minutes used, so nothing stops at the end of the month
- Your own machine keeps Docker layers and package caches between jobs

**GitHub Actions at a flat price, unlimited minutes** Skipbox runs your GitHub Actions jobs on your own dedicated machine: $39 a month, however many minutes you run. Docker layers and dependency caches stay between jobs, so the next job starts right away.

A 4 vCPU runner, 20,000 minutes a month: GitHub $222 → Skipbox $39. You save $183 every month.

Moving takes one line: `runs-on: skipbox`.

[Start my 7-day free trial](https://app.skipbox.dev/sign-in?ref=g-github-actions-personal-account-private-repos-en)

## What a personal account gets

| | GitHub Free | GitHub Pro |
|---|---|---|
| Included a month, private repos | $12 | $18 |
| On `ubuntu-latest` | 2,000 minutes | 3,000 minutes |
| Machine | 2 cores, 8 GB | 2 cores, 8 GB |
| Larger runners | Not available | Not available |

The allowance is dollars, so Windows spends it at $0.010 a minute and macOS at $0.062. Each job rounds up to a whole minute. It resets at 00:00 UTC on the 1st and doesn't roll over.

When it runs out: no card on file means your jobs stop starting until the 1st; a card means every extra minute is billed at $0.006 on `ubuntu-latest`. Public repositories on standard runners are free, but client work and unreleased products can't go public.

## What staying on the free minutes costs you

Solo projects burn minutes faster than they used to:

- **Coding agents.** Hand a task to Claude Code or Copilot and every push it makes runs CI. 100 minutes a day spends GitHub Free's allowance in 20 days.
- **E2E tests.** Adding Playwright turns a 2-minute run into a 10-minute one.
- **2 cores, from scratch.** `ubuntu-latest` starts blank every time, so each run downloads dependencies and rebuilds images, and you pay for the waiting in minutes.

| | GitHub (`ubuntu-latest`) | Skipbox S |
|---|---|---|
| Machine | 2 cores, 8 GB | 4 vCPU, 16 GB |
| Minutes | 2,000 or 3,000 free, then $0.006 each | Unlimited |
| When the allowance runs out | Billed or blocked | Nothing happens |
| A month costs | Whatever the minutes add up to | $39 |

Against Pro's `ubuntu-latest`, Skipbox S costs less above about 9,500 minutes a month; on GitHub Free, sooner. Your own number is in the [calculator on the home page](https://skipbox.dev/?ref=g-github-actions-personal-account-private-repos-en#cost).

You can trim minutes by hand with `concurrency`, `paths-ignore` and `timeout-minutes`, and win back a fraction while staying on 2 cores. Or you can register your own PC as a self-hosted runner, and then keep it awake, patched and updated. Skipbox does that part for you.

## What changes on Skipbox

### No minutes to count

Jobs on Skipbox draw nothing from your GitHub allowance. Minutes are unlimited, with no usage charges.

| Plan | Machine | Per month |
|---|---|---|
| S | 4 vCPU, 16 GB | $39 |
| M | 8 vCPU, 16 GB | $79 |
| L | 16 vCPU, 32 GB | $149 |

Plans, prices and the trial are the same for personal accounts and organizations.

### Faster CI

Your machine stays yours between jobs. Docker images and build cache, npm and pip caches, and tools installed by setup-node are still there for the next run, with 7× or more GitHub's cache space and no cache keys to write.

### No PC to keep awake

Skipbox provisions the machine, updates the OS and tools, cleans up after every job, and health-checks and rebuilds it automatically.

## Moving is one line

```yaml
jobs:
  test:
    runs-on: skipbox # was ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npm ci && npm test
```

1. Sign in to Skipbox with GitHub.
2. Install the **Skipbox (personal)** app on your account and pick the repositories.
3. Change `runs-on` and push.

The next run is on Skipbox, on Ubuntu 24.04 with Docker, Node.js and Python. [Personal accounts and organizations](https://docs.skipbox.dev/accounts) explains which app goes where.

## Security

- Your machine is yours alone; no one else's jobs run on it.
- After every job, Skipbox wipes the runner's credentials, processes and containers. From 13 November 2026, your checkout and its build output (Cargo's `target/`) stay on your own machine for your next jobs; Clean every job gives each job a fresh machine.
- Code from people without write access (such as pull requests from forks) runs on a fresh, single-use machine.

## Try it on your own jobs

The trial needs no card and runs for 7 days or 3,000 job-minutes. Move your slowest test job to `runs-on: skipbox` and watch the second run skip the downloads the first one did.

## FAQ

### How many GitHub Actions minutes does a personal account get for private repositories?

$12 of compute a month on GitHub Free and $18 on GitHub Pro: 2,000 or 3,000 minutes on ubuntu-latest, a 2-core runner. Public repositories on standard runners are free. To run private-repo CI without counting minutes, Skipbox works on personal accounts for a flat $39 a month.

### What happens when a personal account runs out of Actions minutes?

Without a card on file, jobs on GitHub-hosted runners stop starting until the 1st of next month. With one, GitHub bills each extra minute at $0.006 on ubuntu-latest. Jobs on Skipbox use no GitHub minutes, so they keep running.

### Can a personal account use larger GitHub runners?

No. GitHub's larger runners are only for organizations on GitHub Team or Enterprise Cloud, so a personal account's private repositories top out at ubuntu-latest's 2 cores and 8 GB. Skipbox gives a personal account 4, 8 or 16 vCPU at a flat price.

### Can I use a self-hosted runner on a personal account?

Yes, registered per repository, and GitHub doesn't bill its minutes. Running it yourself means keeping a machine on and updated. Skipbox's personal-account app, Skipbox (personal), gives you a managed one instead.

### Is GitHub Pro worth it for more Actions minutes?

Pro raises the allowance from 2,000 to 3,000 ubuntu-latest minutes and keeps you on 2 cores. If you run past that, Skipbox gives you unlimited minutes on twice the cores for a flat $39 a month.

Updated 2026-11-11 · https://skipbox.dev/guides/github-actions-personal-account-private-repos