On This Page
This document describes how to find the available resources regarding credits with CircleCI. If you are on the legacy CircleCI Container-based plan, you may want to consider consulting the document on using containers. If you want to switch from using containers to using credits, please open a support ticket requesting so.
Credits are used on CircleCI’s Free, Performance, Scale, and Server plans. Each plan offers key CI/CD features, and some plans offer customization options depending on your needs.
The right plan for you and your team will depend on several factors:
- How many users are on your team
- How much support you need (community and free support, standard support, or premium support)
- If you want access to different machine-types and resource classes
- If you want a limited or unlimited number of self-hosted runners
You can view the Plan Overview page for more information, or if you would like more details on what features are available per plan, view the individual plan pages:
Consider taking a moment to look at the CircleCI Pricing page to learn more about how credits are distributed across different machine types and resource classes.
Managing credit usage
Properly managing network and storage usage can potentially lower the amount of credits used per month. If you would like to find out more about managing network and storage usage, please see the Persisting Data page.
Open source credit usage
Organizations on our Free plan receive a set amount of free credits per month for Linux open source builds. Using our Free plan and keeping your repository public will enable this for you. Open-source credit availability and limits will not be visible in the UI.
If you build on macOS, we also offer organizations on our Free plan a number of free credits every month to use on macOS open source builds. For access to this, contact our team at firstname.lastname@example.org.
Troubleshooting: Am I charged if my build is “queued” or “preparing”?
No. If you are notified that a job is “queued”, it indicates that your job is waiting due to a plan or concurrency limit. If your job indicates that it is “preparing”, it means that CircleCI is setting up or dispatching your job so that it may run.
If your jobs use the Docker executor and you find that they are “preparing” for quite some time, you may be able to reduce the delay by using more recent docker images. See Building Docker Images for more information.
Questions and comments
Help make this document better
This guide, as well as the rest of our docs, are open source and available on GitHub. We welcome your contributions.
- Suggest an edit to this page (please read the contributing guidefirst).
- To report a problem in the documentation, or to submit feedback and comments, please open an issue on GitHub.
- CircleCI is always seeking ways to improve your experience with our platform. If you would like to share feedback, please join our research community.
Our support engineers are available to help with service issues, billing, or account related questions, and can help troubleshoot build configurations. Contact our support engineers by opening a ticket.
You can also visit our support site to find support articles, community forums, and training resources.
CircleCI Documentation by CircleCI is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.