Pricing¶

Cirrus CI is free for Open Source projects with some limitations. For private projects, Cirrus CI has couple of options depending on your needs:

For private personal repositories there is a very affordable $10 a month plan with access to Cirrus Cloud Clusters for Linux, Windows and macOS workloads.
Buy compute credits to access managed and pre-configured Cirrus Cloud Clusters for Linux, FreeBSD, Windows, and macOS workloads.
Configure access to your own infrastructure and pay $10/seat/month.

Here is a comparison table of available Cirrus CI plans:

User	Free Public Repositories	Private Personal Repository	Private Organization Repositories
Person	Free access to Cirrus Cloud Clusters for public repositories Bring your own infrastructure for public repositories Configure persistent workers for public repositories	Access to community clusters for public and private repositories Bring your own infrastructure for public and private repositories Configure persistent workers for public and private repositories	Not Applicable
Organization	Free access to Cirrus Cloud Clusters for public repositories Use compute credits to access community clusters for private repositories and/or to avoid the limits on public repositories Bring your own infrastructure for public repositories Configure persistent workers for public repositories	Not Applicable	Free access to community clusters for public repositories Use compute credits to access community clusters for private repositories and/or to avoid the limits on public repositories Bring your own infrastructure for public and private repositories Configure persistent workers for public and private repositories

Compute Credits¶

Sometimes configuring your own compute services isn't worth it. It takes time and effort to maintain them. For such cases there is a way to use the Cirrus Cloud Clusters for your organization.

1 compute credit can be bought for 1 US dollar. Here is how much 1000 minutes of CPU time will cost for different platforms:

1000 minutes of 1 virtual CPU for Linux platform for 3 compute credits
1000 minutes of 1 virtual CPU for FreeBSD platform for 3 compute credits
1000 minutes of 1 virtual CPU for Windows platform for 4 compute credits
1000 minutes of 1 Apple Silicon CPU for 15 compute credits

All tasks using compute credits are charged on per-second basis. 2 CPU Linux task takes 5 minutes? Pay 3 cents.

Note: orchestration costs are included in compute credits and there is no need to purchase additional seats on your organization's plan.

Works for OSS projects

Compute credits can be used for commercial OSS projects to avoid concurrency limits. Note that only collaborators for the project will be able to use organization's compute credits.

Benefits of this approach:

Use the same pre-configured infrastructure that we fine tune and constantly upgrade/improve.
No need to configure anything. Let Cirrus CI's team manage and upgrade infrastructure for you.
Per-second billing with no additional monthly fees for storage and traffic.
Cost efficient for small to medium teams.

Cons of this approach:

No support for exotic use cases like GPUs, SSDs and 100+ cores machines.
Not that cost efficient for big teams.

Buying Compute Credits¶

To see your current balance, recent transactions and to buy more compute credits, go to your organization's settings page:

https://cirrus-ci.com/settings/github/MY-ORGANIZATION

Configuring Compute Credits¶

Compute credits can be used with any of the following instance types: container, windows_container and macos_instance. No additional configuration needed.

amd64arm64

task:
  container:
    image: node:latest
  ...

task:
  arm_container:
    image: node:latest
  ...

Using compute credits for public or personal private repositories

If you willing to boost Cirrus CI for public or your personal private repositories you need to explicitly mark a task to use compute credits with use_compute_credits field.

Here is an example of how to enable compute credits for internal and external collaborators of a public repository:

task:
  use_compute_credits: $CIRRUS_USER_COLLABORATOR == 'true'

Here is another example of how to enable compute credits for master branch of a personal private project to make sure all of the master builds are executed as fast as possible by skipping free usage limits:

task:
  use_compute_credits: $CIRRUS_BRANCH == 'master'

Compute Services¶

Configure and connect one or more compute services and/or persistent workers to Cirrus CI for orchestrating CI workloads on them. It's free for your public repositories and costs $10/seat/month to use with private repositories unless your organization has Priority Support Subscription.

Benefits of this approach:

Full control of underlying infrastructure. Use any type of VMs and containers with any amount of CPUs and memory.
More secure. Setup any firewall and access rules.
Pay for CI within your existing cloud and GitHub bills.

Cons of this approach:

Need to configure and connect one or several compute services.
Might not be worth the effort for a small team.
Need to pay $10/seat/month plan.

What is a seat?

A seat is a user that initiates CI builds by pushing commits and/or creating pull requests in a private repository. It can be a real person or a bot. If you are using Cron Builds or creating builds through Cirrus's API it will be counted as an additional seat (like a bot).

For example, if there are 10 people in your GitHub Organization and only 5 of them are working on private repositories where Cirrus CI is configured, the remaining 5 people are not counted as seats, given that they aren't pushing to the private repository. Let's say Dependabot is also configured for these private repositories.

In that case there are 5 + 1 = 6 seats you need to purchase Cirrus CI plan for.