Providers

A provider is somewhere a job can run. You can route jobs to some providers. The dashboard recognizes many more, so it can show where every job ran and what it cost.

Where jobs can be routed

A relay can send a job to any of these. Each has a step in your runner order.

• Self-hosted: machines you connect with the CLI, and runners your org already has.
• GitHub-hosted: GitHub’s own runners, billed against your plan’s minutes.
• Hosted providers: Blacksmith, Depot, Namespace, WarpBuild, Ubicloud and RunsOn, each through its own GitHub App.

Your accounts, your bills

You pay each hosted provider yourself. A routed job gets a label, and the provider runs it under your own account and bills you directly. You keep your plans, credits and discounts, and you can drop RelayRunner without changing who you pay.

Recognized providers

The dashboard reads where a job ran from its runs-on labels, including jobs you didn’t route. It recognizes these providers. Jobs with any other labels show up as Other. The dashboard’s Providers page shows how much of your CI ran on each, with cost estimates at list prices.

Provider	Labels	List price
Blacksmith Hosted runners for GitHub Actions.	blacksmith-*	$0.008/min
Depot Hosted runners for GitHub Actions.	depot-*	$0.006/min
Namespace Hosted runners for GitHub Actions, sized by runner profile.	namespace-profile-*, nscloud-*	—
WarpBuild Hosted runners for GitHub Actions.	warp-*	$0.004/min
Ubicloud Hosted runners for GitHub Actions.	ubicloud, ubicloud-*	$0.00125/min
RunsOn Runners started in your own AWS account.	runs-on=<run id>/runner=<type>	—
GitHub GitHub's own hosted runners, billed per minute in private repos.	ubuntu-*, windows-*, macos-*, or a larger runner's own name	—
Cloudflare RelayRunner's own runner, a Cloudflare Container started for each job.	relayrunner-container	—

To add another, see Add a provider.