Usage-based
Pricing

GB-hours are the spending unit for storage. Technically, it is the amount of data stored multiplied by the time it is kept. For example, a sandbox with 10 GB of disk kept for 30 days consumes 7300 GB-hours.

The pipeline cache includes the filesystem with downloaded dependencies and generated artifacts, cached Docker layers, and data from services attached to builds. The Free plan includes 1 GB of pipeline cache.

GB-minutes are the spending unit for memory. Technically, it is the amount of RAM assigned to the pipeline or sandbox multiplied by the execution time. For example, a pipeline with 3GB of RAM running for 10 minutes consumes 30 GB-minutes.

The base cost per GB-minute is $0.00024. For pipelines, a multiplier is applied depending on the action type:

For example, a pipeline with 3GB of RAM with a Node build running for 5 minutes and an iOS build running for 3 minutes consumes 69 GB-minutes in total:

• 5 min x 3GB x 1 [container] = 15 GB-minutes
• 3 min x 3GB x 6 [macOS VM] = 54 GB-minutes

CPU-minutes are the spending unit for processing power. Technically, it is the number of vCPUs assigned to the pipeline or sandbox multiplied by the execution time. For example, a pipeline with 2 vCPU running for 10 minutes consumes 20 CPU-minutes.

Every CPU-minute costs $0.00024, regardless of the action type. CPU-minutes are billed on top of GB-minutes, so a container build with 4GB of RAM and 2 vCPU running for 10 minutes costs (40 GB-minutes + 20 CPU-minutes) x $0.00024 = $0.0144.