How am I charged for Self Hosted Runner?


Teams that are migrating some of their workloads to CircleCI's Self-Hosted Runner might be curious to know if there are any charges for it. 


How you will be charged

Any Network Egress to CircleCI will be charged. At this current time, this includes CircleCI Caches, Workspaces, and Artifacts and will be charged at the normal rate according to your Usage Controls.

The only network traffic that will result in billing is accrued through restoring caches and workspaces to self-hosted runners. Retention of artifacts, workspace, and cache objects will result in billing for storage usage.


Since your builds will not be running on CircleCI's Infrastructure, you will not be charged compute credits, but please make note that this cost is shifted to whatever hosting service you use. (i.e. AWS, GCP, Nutanix, etc.)


Why isn't my build starting on a Self-hosted Runner?

CircleCI utilizes a different set of concurrency for self-hosted runners and you may be hitting that limit. Please review the Key Features tab on our Pricing page to verify your limit. Your concurrency limit for self-hosted runners is also defined in your "Runner" Tab for your organization.

Please note you may need to refresh your entire page for the "Concurrency Usage" to update.


In some cases, you may have run out of credits on CircleCI and want to continue to build on CircleCI using self-hosted runners. To use a self-hosted Runner you must have a minimum number of credits to make sure you have enough credits for any of the above-mentioned things CircleCI Charges for. 


If neither of these options applies to you, please view our Troubleshoot Self-Hosted Runner page in our documentation or our Troubleshooting Section in our Support Portal.

Additional Resources

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.