Self-hosted runners are now available on CircleCI! You can choose which jobs run in the cloud and which run on your own infrastructure.
Read the blog for more info: Our cloud platform, your compute: introducing the CircleCI runner
Landing page: CircleCI self-hosted runners - CircleCI
Docs: CircleCI Runner Overview - CircleCI
Ask your questions and leave your feedback here!
How does the credit usage work with self-hosted runners?
Scale plan pricing is customized to fit the needs of customers’ workloads. Runner jobs incur a nominal use-based cost, similar to our hosted resource classes. If you’d like to get more specific pricing for self-hosted runners you can talk to our sales team.
Has there been any change in this now that runners are (at least according to the pricing page) available for the free plan as well?
I find it puzzling that you get charged the same amount for running your workloads on your selfhosted runners vs. circleci’s own runners!
Hi @JaneDoe!
There is no use-based cost for runners right now on the free plan. There are network and usage thresholds.
We’d love to know more about what we can do to improve this for you.
Hi @thekatertot
Are runners compatible to run on windows 10 & 11?
How much traffic will be generated and how does this influence your credits?
Yes the self-hosted runner can be deployed to a Windows Environment - as detailed here
CircleCI Runner Installation on Windows - CircleCI
I’ve been spending time trying to get the Linux runner going and currently the documentation is hard going as it has not been updated from when self-hosted runners were something that was only available to people with support contracts. I think they are beginning to receive feedback to indicate that this area needs work.
In terms of costs, using a self-hosted runner will change your cost structure. It removes the cost of using CircleCI provided nodes (but you have to remember not to use the docker node created by setup_remote_docker. It also removes the cost of egress traffic from the runner that is going somewhere other than CircleCI’s internal systems (your systems or say DockerHub).
Once CircleCi introduces it storage and egress charges you will still be charged for any storage of Persist data held at CircleCI and any data that is sent from the CircleCI system to your self-hosted runner.
As for how these costs influence credits - beyond the included small monthly amount of storage network traffic each GB of usage is going to be charged at 420 credits. So depending on how you use CircleCI you may have to change what you are doing. For my situation, self-hosted runners have become a necessity as I need to build rather blotted docker images and so would see very high egress charges.
If anybody is looking for a solution to run these on Kubernetes, I’ve made another thread here: Circleci-k8s-agent: Kubernetes scaling solution for self-hosted runners