Runner sizes

A runner size is a label. ubuntu-latest resolves to the standard x64 runner, sized as GitHub sizes it; a different size is one change to runs-on. Every size is included in every plan.

jobs:
  build:
    runs-on: apex-4core-x64

arm64 is opt-in: reach it with a size label or arm64. There is no 8-core x64 size. Pinned labels such as ubuntu-24.04 or ubuntu-22.04 are not recognised, and no Apex runner picks up a job that names one.

A larger size draws more of the plan's included minutes: one 4-core minute counts as two standard minutes, and one 8-core minute as four. ubuntu-latest on a public repository runs on 4 cores and draws two.

Seeing your usage

Account → Usage in the Apex dashboard shows your Account's standard minutes per day over the last 7, 30 or 90 days, stacked by runner size, with the total for the period and the same figures as a table. Days are UTC days. It counts only the repositories you may read, and it is a measure of use, not a bill. Beneath it, the same days show your jobs by outcome — succeeded, cancelled or skipped, failed — and your repositories ranked by minutes, each with its share.

The same days download as CSV, by runner size or by repository: one row per day and group, with the standard minutes, ready for a pivot table. By repository, the twenty largest are named and the rest are summed as other.

Account → Dashboard is the Account at a glance: over the last 30 UTC days, your jobs, their success rate, your standard minutes, and how long jobs waited in the queue and ran (median and 95th percentile) — over the repositories you may read — and, now, the jobs queued and running and the runs waiting for an approval. If your role decides what the Account pays (Owner, Account Admin or Billing), it also shows each Organization's plan and billing period: minutes used against what the plan includes, and where the period is heading at its pace so far, with any overage that would come to. That projection is a straight line, not a forecast, and none is drawn in a period's first day.