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

If you’re trying to validate CircleCI on a new project or standardize CI/CD across a small team, the Free plan is designed to get you real pipelines running—not just a demo. The headline details are simple: you get 30,000 credits every month and up to 5 active users included. The nuance is in how credits are consumed and what “active user” actually means when your repos are busy.

Below is how the plan really works in day‑to‑day use, and how to forecast whether 30,000 credits and 5 active users are enough for your team.

---

The Quick Overview

• What It Is: CircleCI’s Free plan is a usage-based CI/CD tier that includes 30,000 credits and up to 5 active users every month at no cost.
• Who It Is For: Small teams, early‑stage startups, and platform engineers validating CircleCI pipelines before rolling out to a wider org.
• Core Problem Solved: It lets you run real build, test, and deploy pipelines—with governance patterns you’d use in production—without committing budget or guessing user counts up front.

---

How the Free Plan Works

CircleCI pricing revolves around credits and active users:

• Credits are the currency that pays for:
  • Monthly active users
  • Compute time (each executor type has a credits‑per‑minute rate)
  • Some add‑on features (charged per use or per minute)
• Active users are people who actually cause pipelines to run in a given billing period.

On the Free plan:

• You get 30,000 credits per month included.
• You get up to 5 active users per month included.
• Your cost for that bundle is $0.00.

Those 30k credits cover both the user activity and the compute you consume. When your pipelines run, CircleCI deducts credits in real time; when nobody’s pushing changes and no pipelines are running, you’re not spending anything.

If you outgrow the Free plan, you can move into paid usage, buy additional credits, or prepay for discounts—but the mechanics stay the same. You’re still paying in credits for active users, compute time, and any add‑ons.

---

What Counts as an Active User?

This is the part most teams over‑complicate. On CircleCI, an active user is:

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

In practice, that means:

• Any commit that triggers a pipeline
  If a developer pushes code or merges a PR into a branch where CircleCI is configured and that action runs a pipeline, that person is an active user.

• Manual pipeline triggers and reruns
  If someone clicks “Rerun workflow,” kicks off a pipeline manually, or triggers it through the CircleCI app/API with their user identity, they’re an active user.

• Applies across all connected VCS repos
  It doesn’t matter whether it’s GitHub, GitLab, or Bitbucket, or which repo they touch—if they cause a pipeline to run in your CircleCI org during that billing period, they’re active.

Equally important is what doesn’t create extra active users:

• Bots and service accounts
  If you centralize automation through a bot account that is the one “causing” pipelines to run, that bot will count as one active user. People whose commits don’t directly trigger CircleCI won’t be counted as active users for that period.

• Team members who don’t trigger pipelines
  Read‑only observers, managers, or SREs who just inspect logs and job metadata in the UI but never push code or trigger pipelines don’t become active users.

Because active user billing is tied to credits, not a fixed seat limit, CircleCI emphasizes flexibility:

• You pay for monthly active users in credits, so your org is never locked into a static seat count.
• On the Free plan, you get up to 5 active users included within that 30k credit bundle.

If a sixth engineer starts pushing changes that trigger pipelines regularly, you’re now above the “up to 5 active users included” range and into a profile where you should expect to move beyond the Free tier.

---

How Credits Work on the Free Plan

Credits are the meter on your CI/CD engine. On the Free plan, you start every billing period with 30,000 credits at no cost. Those credits are used for:

1. Monthly Active Users

   • Each active user has an associated credit cost in paid plans.
   • On Free, you don’t see a separate charge line—your first 5 active users are simply included inside the 30k credit bundle.

2. Compute Time

   • Every resource type (e.g., Docker executors, machine executors, larger or smaller CPU/RAM configurations) has a credits‑per‑minute rate.
   • When a job runs in a workflow, credits are deducted in real time based on:
     • The executor type
     • The duration of the job
     • Any premium features attached to that job

3. Add‑On Features

   • Some higher‑level capabilities have additional credit costs, either:
     • Per use (for an event or operation), or
     • Per minute (for extended runtimes or special workflows).
   • Charges are deducted from the same credit pool.

On the Free plan, once your organization uses up the 30,000 free credits in a billing period:

• Pipelines may be blocked or throttled unless you upgrade or purchase credits, depending on current product behavior.
• In practice, if you’re hitting that limit regularly, you’re behaving more like a small production team than a test account—at that point, you’ll want the uptime guarantees and scale controls of a paid tier.

---

Typical Flow with 5 Active Users and 30k Credits

Here’s how this plays out for a small engineering squad:

1. Connect your VCS repos

   • You hook up GitHub/GitLab/Bitbucket to CircleCI.
   • You add a .circleci/config.yml that defines your pipelines—jobs, workflows, contexts, approvals, policy checks.

2. Engineers start pushing changes

   • Up to 5 engineers can actively commit and merge code that triggers pipelines without you leaving the Free plan.
   • Each time a pipeline runs, CircleCI:
     • Logs a new usage event.
     • Deducts credits for the compute resources and features used in that pipeline.

3. Credits burn down as real work happens

   • Long test jobs, heavier machine executors, and frequently rerun builds will consume more of your 30,000 credits.
   • If you’re just getting started with a couple of services and modest pipelines, that monthly 30k cushion is usually enough to:
     • Ship multiple times a day
     • Run standard build + test workflows
     • Explore rollbacks, approvals, and policy checks without worrying about immediate cost

4. If you grow beyond Free

   • More frequent deployments or more repos will increase credit usage.
   • Adding more than 5 contributors who actively trigger pipelines will push you into a usage profile where you’ll want a paid plan.
   • You can 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

   Prepaid credits are about governance at scale—they keep your teams moving at AI speed while Finance sees a predictable commitment.

---

How “Up to 5 Active Users” Plays with Real Teams

If you’re a platform engineer or team lead, here’s how to think about the 5‑user limit:

• Small team, single service
  A 3–5 person team owning one or two services can usually operate comfortably on the Free plan while you:

  • Set up golden‑path pipelines
  • Establish policy checks before execution
  • Wire up approvals and rollback workflows

• Platform validation phase
  If your real goal is to standardize CI/CD across dozens of repos, the Free plan is an ideal sandbox for:

  • Building reusable pipeline components
  • Validating test selection (e.g., Smarter Testing) and parallelization strategies
  • Proving you can ship safely at AI speed before onboarding the rest of the org

• Contractors and bots
  If you rely on contractors or service accounts:

  • Contractors who push code and trigger pipelines count as active users.
  • You can funnel certain automated triggers through a small number of service accounts to keep your active user count predictable, while still enforcing approvals and policy checks where needed.

In every scenario, remember: your billing exposure is tied to credits, not a hard seat count. The Free plan just gives you a generous, zero‑cost starting point—30k credits and 5 active users.

---

When to Move Beyond the Free Plan

From my experience running CI/CD platforms, you’ll know it’s time to graduate from Free when:

• You’re consistently bumping into the 30k credit ceiling, and:
  • Builds are getting longer or more frequent.
  • You’ve rolled out pipelines to more than a couple of repos.
• You have more than 5 engineers regularly triggering pipelines across your org.
• You want to lock in prepaid credits for cost savings and governance:
  • Finance wants predictable spend.
  • You want to guarantee that production rollbacks and hotfix pipelines never stall.

When you hit that point, you can move into a paid plan where:

• You still use credits as the billing unit.
• You can scale active users and pipelines without rethinking your pipeline design.
• You can keep the same validation and rollback patterns you established during your Free‑plan experiments.

---

Summary

The CircleCI Free plan is built for real work, not toy examples. You get:

• 30,000 credits every month, free
• Up to 5 active users included, defined as anyone who causes a pipeline to run during that billing period
• A single, consistent mechanism—credits—covering:
  • Monthly active users
  • Compute time (credits per minute per executor)
  • Add‑ons (credits per use or per minute)

For a small team, that’s more than enough to build out serious CI/CD pipelines with approvals, policy checks, and rollback workflows—so you can prove that you can ship trusted code at AI speed before you ever send a PO.

---

Next Step

Get started with a Free plan and see how far 30,000 credits and 5 active users can take your pipelines:
Get Started