One subscription, not a meter

A price you can predict

GitHub-hosted runners bill per minute, and the rate climbs with the size of the machine. A busy month is an expensive month, and a bigger runner is a decision someone has to justify.

Apex Actions is a subscription. You pick a plan that fits the size of your team and the amount of CI it runs, and that is the price: an allowance of standard minutes, overage at half GitHub's standard rate past it, larger runners that draw two or four times from the same allowance rather than a separate rate, and no charge per person. Across the teams we have modelled, that comes to about half the cost of the GitHub-hosted runner minutes they were paying for, at the usage each plan is sized for.

That comparison is worth being precise about, so it is written out in full — the rates, the date they were checked, and the cases where it does not hold — in how we compare. The short version: it measures runner minutes against a subscription, it excludes your GitHub seats because switching does not cancel any of them, and if your team runs inside GitHub's free allowance then GitHub charges you nothing for minutes and we will not pretend to beat that.

What the plan includes

• Your plan's included minutes on the standard runner, and overage at half GitHub's rate past them.
• Larger runners with no separate price: a minute on a 4-core runner counts as two standard minutes, and on an 8-core runner as four.
• Caching and artifacts, exactly as actions/cache and actions/upload-artifact expect them.
• Check runs, annotations and flaky-test warnings on every pull request, and the logs and run insight in the Apex dashboard.
• The apex CLI, on every plan and during the trial.

Nothing to run, nothing to operate

The subscription is hosted. Apex operates the runners, keeps them patched, and scales them to your queue. There is no agent to install, no fleet to size, and no second bill from anyone else.