CircleCI Free plan: how do 30,000 credits/month and up to 5 active users work, and what counts as an active user?

Most teams start on CircleCI’s Free plan to see how far they can get before they need to pay. The core pieces you get are 30,000 credits every month and up to 5 active users included, with no charge as long as you stay inside those limits. The key is understanding how credits are consumed and what “active user” actually means in day‑to‑day use.

Quick Answer: The CircleCI Free plan gives you 30,000 credits and up to 5 active users every month at no cost. Credits pay for platform usage (users, compute, and certain features), and an “active user” is anyone who causes a pipeline to run during the billing period (usually by pushing code or opening a PR).

The Quick Overview

What It Is: A usage‑based CI/CD plan that includes 30,000 credits/month and 5 active users, enough for smaller teams to run real pipelines without an upfront bill.
Who It Is For: Individual developers, small teams, and orgs evaluating CircleCI as their CI/CD and autonomous validation platform.
Core Problem Solved: Lets you validate and ship code with real pipelines—build, test, deploy, rollback—before you commit to a paid plan, while giving clear levers for how usage is counted.

How the Free Plan Works

CircleCI’s Free plan is built on the same usage‑based model as paid tiers. Instead of locking you into seats and fixed runners, you get a monthly pool of credits and a cap on included active users. As long as you stay within those, you pay $0.

Behind the scenes, CircleCI tracks:

Credits – the currency used to pay for:
- Monthly active users
- Compute time (every job that runs)
- Certain add‑on features (where applicable)
Active users – the people who actually trigger pipelines during the month.
Compute usage – minutes and resource types each job consumes.

When your usage (users + compute + add‑ons) stays within 30,000 credits and 5 active users in a month, your cost is $0.00. If you outgrow that, you move into paid usage with the same model, just with more credits.

1. Credits: Your CircleCI currency

Credits are the currency of CircleCI. You purchase them up front on paid plans; on Free, you simply receive 30,000 credits each month at no cost.

Credits are consumed in three main ways:

Monthly active users
- CircleCI charges for “monthly active users” using credits.
- This keeps you from being hard‑capped to a static number of users—if more people start shipping code, usage just scales with them.
- On the Free plan, up to 5 active users are included as part of your 30k credits, so you don’t see a separate seat line item.
Compute time
- Every resource type (Linux, macOS, Windows, resource_class size, etc.) has a credits‑per‑minute price.
- When a job runs in a pipeline, CircleCI debits credits in real time based on:
  - The runner type
  - The resource_class
  - How long the job takes (in minutes)
- Longer and heavier jobs consume more credits; shorter, right‑sized jobs consume fewer.
Add‑on features
- Some features have extra credit cost either per use or per minute.
- Think of this as paying a bit more when you turn on advanced capabilities, still deducted from the same credit pool.

2. What counts as an active user?

CircleCI defines an active user as:

Any user who causes a pipeline to run on CircleCI during the billing period.

Concretely, that typically means:

A developer who:
- Pushes a commit to a branch that’s wired to CircleCI
- Opens or updates a pull request that triggers a pipeline
- Manually reruns a workflow or job
- Triggers a pipeline via API or webhook using their identity
A bot/service account that:
- Is configured as a user and pushes code or triggers pipelines

Users who do not trigger pipelines during the billing period do not count as active. They can still:

View pipeline histories, logs, and job metadata
Comment on or review PRs in GitHub/GitLab/Bitbucket
Sit idle in the org without incurring active‑user cost

On the Free plan, you can have many people in your VCS repo, but only the first 5 unique users who actually cause pipelines to run in the month are covered at no cost.

3. Monthly cycle: How it resets

Every billing period (typically a calendar month):

Your 30,000 free credits reset
- Unused credits do not roll over.
- You start each month with a fresh 30k balance.
Active users reset
- The “active” count is recalculated each month based on who triggers pipelines in that period.
- Someone active one month but idle the next no longer counts as active in that new period.

This reset behavior is exactly what allows small teams to experiment heavily one month, then go quieter the next, without getting locked into a permanent seat count.

Features & Benefits Breakdown

Core Feature	What It Does	Primary Benefit
30,000 credits/month	Funds user activity, compute time, and certain add‑ons on the Free plan.	Run real build/test/deploy pipelines with no upfront cost.
Up to 5 active users	Includes 5 monthly active users in your free credit pool.	Let a small team ship code without worrying about seat licenses.
Usage‑based billing model	Uses credits in real time for compute and features; users scale with usage.	Grow from Free to paid without changing how you work or re‑architecting.

Ideal Use Cases

Best for small product or platform teams trialing CircleCI:
Because you can plug CircleCI into your GitHub/GitLab/Bitbucket repos, define a few pipelines, and have up to 5 engineers pushing code and triggering builds—without a billing conversation.
Best for solo maintainers and OSS projects:
Because a single maintainer or a small contributor group can run CI/CD for PRs, releases, and rollbacks using the 30k credits, treating CircleCI as their validation and delivery system for free.

Limitations & Considerations

Credit ceiling can be tight for heavy workloads:
30,000 credits are generous for light to moderate usage, but if you run:
- Many builds per day
- Long‑running test suites
- Larger resource_class machines
  you may hit the credit limit quickly. As soon as your usage pattern looks “team‑level” rather than “evaluation‑level,” you’ll want to look at a paid plan so pipelines don’t stall.
Only 5 active users included:
If more than 5 people regularly trigger pipelines, you’re operating beyond the Free plan’s intended scale. That’s where paid tiers and prepaid credits with volume discounts (up to 5% savings) make more sense for predictable spend.

Pricing & Plans

The Free plan is the on‑ramp into CircleCI’s usage‑based CI/CD:

Free plan:
- 30,000 credits/month included
- Up to 5 active users included
- Cost: $0.00 as long as you stay within that credit pool

When you outgrow Free:

You buy credits in advance for additional savings:
- 5–10M credits → 2% savings
- 10–41.7M credits → 3% savings
- 41.7–83.4M credits → 4% savings
- 83.4M+ credits → 5% savings
Those credits fund:
- Active users (beyond the free included amount)
- All your compute jobs across pipelines and workflows
- Any add‑on features you enable

CircleCI’s plan builder can estimate a recommended monthly credit amount based on:

Number of active users (for example, 5, 50, 100, 250, 500, 1k+)
Builds per month (for example, 50, 1k, 2.5k, 5k, 10k, 20k+)

For the baseline Free scenario:

Active users: 5
Builds per month: 50
Recommended credits: 30,000 (all included on Free)
Your cost: $0.00

From there, you can scale credits as your build volume grows, without changing pipeline definitions or workflows.

Free: Best for individuals and small teams needing to validate CircleCI with real workloads and minimal pipelines.
Paid (usage‑based): Best for growing teams and enterprises needing predictable, scalable CI/CD with more active users, higher build volume, and access to advanced capabilities.

Frequently Asked Questions

How do 30,000 credits on the CircleCI Free plan actually get used?

Short Answer: Your 30,000 credits fund every bit of CircleCI platform usage that month—active users, compute time, and certain add‑on features—until the pool is exhausted.

Details:
Credits are deducted in real time as pipelines run:

Every job that executes in a workflow uses credits per minute based on machine type and resource_class.
Active users (up to 5 on Free) are also paid for in credits, but on the Free plan this is effectively baked into your 30k allocation.
If you enable add‑on features with per‑use or per‑minute pricing, those debits also come from your credit pool.

If you stay within the 30,000 credits in a billing period, you pay $0. Once your usage exceeds that (e.g., sustained heavy compute or more active users on a paid plan), you’ll need additional credits—either as pay‑as‑you‑go or via a prepaid bundle with discounts.

What exactly makes someone an “active user” on CircleCI?

Short Answer: Any person who triggers a pipeline on CircleCI during the billing period is counted as an active user.

Details:
The definition CircleCI uses is:

Any user who causes a pipeline to run on CircleCI during the billing period.

That includes:

Pushing a commit to a branch that has CircleCI pipelines configured
Opening or updating a pull request that triggers workflows
Manually rerunning jobs or workflows in the CircleCI UI
Triggering pipelines via API or webhooks with their user identity

People who only view logs, check job metadata, or observe pipelines but never trigger a run are not counted as active for that month.

On the Free plan, up to 5 such active users are included. Additional people in your GitHub/GitLab/Bitbucket org who don’t trigger pipelines don’t consume active‑user capacity.

Summary

CircleCI’s Free plan is built to let you ship trusted code at AI speed without an upfront bill. You get 30,000 credits each month and up to 5 active users included, enough to set up real pipelines—build, test, deploy, and even rollback paths—and see how CircleCI fits your delivery flow.

Credits are the single currency for everything: users, compute, and add‑ons, deducted in real time as pipelines run. An active user is simply anyone who triggers a pipeline during the month. That combination gives you a clear, predictable way to understand your CI/CD footprint and an easy path to scale: when you’re ready, you just buy more credits; you don’t have to re‑platform your pipelines.

Next Step

Get Started