DevOps / CI/CD

Are GitHub Actions Self-Hosted Mac Runners Still Charged? 2026 Budget Review

Are GitHub Actions Self-Hosted Mac Runners Still Charged? 2026 Budget Review

A proposed self-hosted runner charge is creating uncertainty in your iOS CI budget.

Fast answer: GitHub has paused the announced change to self-hosted GitHub Actions billing. Do not budget the proposed platform fee as an active charge; reconcile your current Actions bill and Mac operating costs before choosing a runner model. GitHub’s announcement also says its hosted runner price reduction took effect on January 1, 2026. (GitHub’s billing announcement)

For finance, procurement, and IT leads, this review clarifies which costs belong on the current GitHub Actions bill.
For platform and DevOps leads, it provides a way to isolate real Mac build use from other workflow activity.
For technical decision-makers planning Mac capacity, it compares the cost and operating boundaries of hosted, self-hosted, and remote Macs.

Last updated October 13, 2026. Policy and billing references checked against GitHub’s official announcement, pricing, billing, and usage-report documentation. Confirm the latest status and account-specific charges before approving a budget.

What the announced change means for the current budget

For a budget review, distinguish a proposed policy change from a charge that has appeared on the account. GitHub says it paused the planned self-hosted Actions billing change for reassessment. That supports one practical decision: do not enter the proposed new platform fee as an active expense unless current official documentation and the account’s bill show that it applies. The pause is not a permanent cancellation.

That distinction matters because “self-hosted” describes where a runner machine is managed, not the full cost of operating it. A Mac bought or rented for CI still consumes budget. Someone must provision it, maintain its operating environment, manage credentials and access, and respond when a build node fails.

GitHub’s announcement separately states that the reduction to hosted runner prices took effect on January 1, 2026. Keep that change in the policy record, but verify the applicable runner type, account allowances, and current rates against the Actions runner pricing reference. Do not assume a price change affects every runner category or account in the same way.

Treat the announcement, the current pricing reference, and the company’s invoice as separate evidence. A policy announcement explains a change; the invoice and usage report show what your account incurred.

Finance and procurement: separate platform charges from Mac costs

GitHub Actions bills can contain different kinds of spend. The GitHub Actions billing documentation explains the platform’s billing model and the way usage, plan allowances, and overages are handled. For a review, classify each charge using the current account’s records rather than relying on a generic estimate.

Cost area What to verify Evidence for the review
Hosted runner use Runner category, billable usage, applicable allowance, and any overage Current pricing reference and account billing report
Larger hosted runners Whether the workflow used a larger runner and which rate applies Runner configuration, usage report, and current pricing page
Proposed self-hosted billing change Whether the announced change remains paused or has been updated Latest official announcement and current billing documentation
Self-hosted Mac resource Purchase, rental, hosting, or other actual resource expense Purchase records, invoices, or approved rental terms
Operations and idle capacity Maintenance, incident handling, and capacity kept available but unused Internal time and cost records

Use the GitHub billing reports reference to reconcile account-level charges with the finance system. Preserve the announced self-hosted billing adjustment as a policy-change record, separate from current line items. If an invoice does not clearly map to a usage category, raise that discrepancy with the account owner before classifying it as a Mac runner cost.

For procurement, the key question is not whether a runner is labelled “free” or “self-hosted.” It is whether the proposed budget includes all costs that will land inside the company’s accounting boundary. Hosted runner charges may be visible as platform usage. A self-hosted Mac’s maintenance time may sit in an engineering budget instead. Comparing only one department’s invoice can therefore make a more expensive operating model look cheaper.

CI and DevOps: turn workflow reports into Mac usage

An Actions total does not reveal how much capacity iOS builds actually consume. The organization’s GitHub Actions metrics documentation describes how to view organization-level workflow activity. Use those metrics alongside billing exports and internal runner records.

First, choose a period and preserve the raw exports

Use a billing period that finance can reconcile. Export the organization’s usage data and retain a copy before cleaning or grouping it. The billing report is the financial control; the workflow metrics help explain what activity drove it. If the two sources do not align, record the difference rather than silently adjusting one to fit the other.

Next, group runs by workload and runner type

Build a working view with repository, workflow, runner type, billing period, and usage. Identify macOS jobs that build, test, sign, or package Apple-platform software. Separate Linux or Windows jobs, even when they belong to the same pipeline. The relevant question is how much of the spend and operational load belongs to Mac work—not how much the organization spent on Actions overall.

The self-hosted runner documentation is also relevant when checking how self-hosted runners are configured and managed. Compare the documented setup with the company’s actual runner inventory. A workflow label alone may not be enough to establish which machine ran a job.

Then, distinguish useful work from avoidable consumption

Review retries, cancelled runs, duplicate triggers, and jobs that reserve capacity without producing a useful build result. Do not assume every failed or repeated run is waste: some retries may be required to diagnose flaky tests or recover from infrastructure failure. Label the reason so the team can distinguish necessary resilience from avoidable repeat work.

Finally, reconcile the grouped usage with the account bill and the Mac resource ledger. This provides a defensible monthly estimate for enterprise Mac CI cost without relying on a vendor example or assuming that every workflow minute represents a Mac build.

Platform engineering: count the work behind a self-hosted Mac

A self-hosted Mac runner shifts responsibility. It does not remove it. The organization controls the runner machine and its environment, but must plan how to keep that environment available, updated, and usable by the right workflows.

Use a cost worksheet with fields for:

  • Mac resource: purchase, lease, or rental charges supported by actual records.
  • Setup and maintenance: time spent preparing, updating, and validating the runner.
  • Incident response: engineering or IT effort to investigate an unavailable or unhealthy node.
  • Idle capacity: resources kept ready when demand falls, based on observed schedules and utilization.
  • Scaling: additional resources, provisioning effort, or delays when demand increases.
  • Security operations: access reviews, secret handling, network controls, and evidence needed for audits.

Mark each entry as either directly verifiable or requiring an internal estimate. Invoices and purchase records can substantiate resource cost. Staff time and incident effort may require a documented allocation method. Avoid counting the same maintenance work in both a central platform budget and a team CI budget.

This is where a remote Mac can enter the comparison. It may give a team access to a real Mac without requiring the team to purchase and host that machine itself. But a remote machine is not automatically equivalent to a fully managed CI service. The team still needs to verify how its workflows connect, who administers the build environment, how credentials are protected, and what response process applies when a job fails.

The ProxyMac billing information is a place to review service billing details. Use the terms applicable to the intended service and period as evidence in the worksheet. For operational questions about access and using the service, consult the ProxyMac help resources and confirm any requirements that apply to the team. No unverified rental amount, configuration, region, delivery commitment, or saving should be substituted for an actual quote or service record.

Security and IT: compare responsibility, not just the minute rate

Cost and operating responsibility belong in the same decision. A hosted runner, an internally managed Mac, and a remotely accessed Mac can place administration, network access, and incident response in different hands. Document who owns each task before comparing totals.

With a self-hosted runner, the company must decide how workflows reach the host, which repositories can use it, and how to protect any credentials or signing material available during a job. The runner’s isolation and cleanup behavior should match the sensitivity of the workload. The self-hosted runner reference provides GitHub’s guidance on the runner model; the organization still needs to assess its own access and threat requirements.

For hosted runners, confirm the runner category, available plan allowances, and charges against the current account. For remote Mac access, verify service terms and the organization’s own controls for source code, secrets, network routes, and operator access. Do not infer isolation or security guarantees from the word “remote.”

A useful review records both the owner and evidence for each responsibility:

  • Who provisions and updates the Mac environment?
  • Who can access the runner host and workflow secrets?
  • Which network routes are required, and who approves them?
  • Who investigates an interrupted or failed build?
  • What records demonstrate that the company’s security requirements are met?

A lower visible per-minute charge may still carry substantial engineering and support work. Conversely, paying for a managed platform does not eliminate the need to review credentials, workflow permissions, and account controls. The right model depends on what the team needs to control and what it can reliably operate.

Budget review: choose by workload and ownership

Use these conditions to turn the reconciled bill and responsibility review into a decision. The comparison should reflect actual workflows, not a general assumption that one model is always cheaper.

  • Keep hosted runners if their current account charges and allowances fit the workload, and the team prefers the provider to operate the runner machines. Recheck runner category and applicable pricing when approving the budget.
  • Use a self-hosted Mac if the company needs direct control of the machine or environment, can assign owners for updates and incidents, and has verified the full resource and operations cost. Do not include the paused proposed fee as an active charge without current evidence.
  • Consider a remote Mac if the team needs access to Mac build capacity but does not want to purchase and host another physical Mac. Proceed only after verifying the service’s actual terms and confirming that the connection, access controls, and operating model satisfy company policy.
  • Use a mixed model if the workload has distinct needs—for example, routine jobs that fit hosted runners and controlled or capacity-specific work that belongs on a Mac the organization manages or accesses remotely. Assign each workflow to an owner and billing category so mixed capacity does not become untracked capacity.

The decision record should include the usage export, invoice reconciliation, Mac resource worksheet, security ownership, and policy status checked at approval. When GitHub updates the paused change, hosted rates, allowances, or account rules, refresh the affected assumptions rather than carrying forward an old estimate.

FAQ: policy status and enterprise Mac CI costs

Is an extra GitHub platform fee currently applied to self-hosted Mac runners?

GitHub announced that it had paused the planned self-hosted Actions billing change for reassessment. Do not treat the proposed fee as a current charge unless updated official documentation and the account’s actual billing support that conclusion. This does not make operating a self-hosted Mac costless: resource, maintenance, idle-capacity, and incident costs remain part of the company’s own budget.

How should a team estimate Mac CI spend from Actions reports?

Export organization-level Actions metrics and billing reports for the period under review. Group activity by repository, workflow, runner type, and billing period. Identify Mac builds separately from non-Mac jobs, then inspect retries, cancellations, and duplicate triggers. Reconcile the grouped data against the invoice and add documented Mac resource and operating costs from internal records.

What belongs in a comparison of hosted, self-hosted, and remote Mac runners?

Compare like-for-like workloads and accounting periods. Include applicable GitHub charges and allowances for hosted runners; resource, maintenance, idle capacity, and incident response for self-hosted Macs; and verified rental terms plus retained team responsibilities for remote Macs. Then assess credentials, network access, administration, and recovery. A single runner rate cannot represent the full enterprise cost.

Does a paused billing change mean the announced charge is permanently cancelled?

No. A pause for reassessment means the announced change should not be represented as active without current evidence; it does not establish permanent cancellation. Check the official announcement and current billing pages during budget approval. Then confirm how the company’s account is charged by inspecting its actual billing and usage reports.

For a team currently relying only on hosted capacity, the main disadvantages may be less control over the runner environment and less ability to shape the machine’s operating model. Running a Mac in-house offers more direct control, but adds procurement, maintenance, security ownership, and idle-capacity risk. A remote Mac can be a middle option when the team needs Mac build access without taking on the same physical-host responsibilities, provided its service terms and controls fit the workload.

If the cost worksheet shows a need for additional or flexible Mac capacity, compare the actual workflow mix and ownership checklist with ProxyMac’s available service information before deciding. Keep hosted runners where they fit, and use a remote Mac only where its verified terms and operating model meet the team’s requirements.

FAQ

Does GitHub currently charge an extra platform fee for a self-hosted Mac runner?+
GitHub announced that it was pausing and reassessing the planned self-hosted Actions billing change. Do not add that proposed fee to the current budget as though it were active. A self-hosted Mac still has real costs, including hardware or rental, power or hosting where applicable, maintenance, and incident response. Check the current announcement and your account billing before approval.
How can a company estimate monthly Mac CI costs from GitHub Actions reports?+
Export organization-level Actions metrics and billing reports for the period your finance team is reviewing. Group runs by repository, workflow, runner type, and billing period, then separate Mac builds from non-Mac jobs, retries, and idle capacity. Reconcile report totals with the actual invoice. Add Mac resource and operational costs from internal records rather than substituting public examples.
How should a team compare hosted Mac runners, self-hosted Macs, and remote Mac rental?+
Compare the same workloads and accounting period. Include GitHub charges and included allowances for hosted runners; hardware or rental, maintenance, idle time, and response ownership for self-hosted Macs; and verified rental terms plus the team’s operating responsibilities for a remote Mac. Then assess credential boundaries, network access, and recovery needs. A per-minute comparison alone does not capture enterprise cost.
Has the announced self-hosted runner billing adjustment already taken effect?+
GitHub’s announcement says the planned self-hosted billing change was paused for reassessment. That is not the same as a permanent cancellation, and it does not establish that the proposed fee is currently active. Review the announcement and current billing documentation at budget sign-off, then confirm the account’s actual charges in its billing reports.

Run Your Mac CI Workloads on Dedicated M4 Hardware

Deploy a dedicated Mac mini M4 with a 10-core CPU, 16 GB of unified memory, and 1 Gbps dedicated bandwidth.
Connect by SSH, VNC, or browser and use ProxyMac for your self-hosted build workflows.