Dimitri Cabete Jorge, Co-founder & CTO · Last updated: August 2026 · Facts verified: August 2026
TL;DR verdict: CircleCI earns its price on pipeline mechanics its competitors leave out: Docker layer caching, test splitting by historical timing, and SSH access into a failed build container. The billing model is where it loses teams, because credits are consumed by resource class instead of by the minute, and infrastructure failures burn them even when the fault is CircleCI's. Worth it for engineering teams running pipelines across more than one Git host. If your code already lives on GitHub and the pipelines are simple, start with GitHub Actions.
Ratings: G2: 4.4/5 (511 reviews) · Gartner Peer Insights: 4.3/5 (24 ratings), verified August 2026
What Is CircleCI?
CircleCI is a cloud-based CI/CD platform that automates the build, test, and deployment pipeline for every code change a team commits. Its 2026 positioning is autonomous validation, built around Chunk, an AI agent that works at the pipeline layer instead of in an editor.
Founded in 2011 and headquartered in San Francisco, CircleCI raised $100 million in a Series F round in May 2021 at a $1.7 billion valuation. That round brought its total raised to $315.5 million, and no round has been announced since. CircleCI puts its user base at 2 million+ developers.
Its analyst credentials are dated. CircleCI was named a Leader in the Forrester Wave for cloud-native continuous integration tools in Q3 2019, credited for its range of execution environments and its enterprise compliance certifications. That placement is seven years old. CircleCI also says it was the first CI/CD tool to receive FedRAMP authorization, in 2018.
What Is CircleCI Used For?
CircleCI's core job is to run automated pipelines whenever code changes. It catches failures before they reach production and deploys working builds without a human in the loop. Teams choose it over other top CI/CD platforms when a pipeline needs more than a linear sequence of steps.
- Automated testing on every commit: CircleCI runs tests before changes merge, with support for Jest, Mocha, pytest, JUnit, Selenium, and XCTest. Iterable used it to raise its build success rate fivefold.
- Multi-platform mobile builds: iOS and Android both run natively. Android uses pre-configured Docker images, and iOS uses macOS virtual machines with Xcode. Espresso, UI Automator, XCTest, and XCUITest are all supported.
- Containerized deployments: The platform automates deployments across cloud providers with customizable strategies. A Procurify SRE reported deployment time falling from 1 hour 40 minutes to 10 minutes.
- Monorepo pipeline management: Dynamic Config lets teams isolate pipeline instructions inside individual feature branches, which is how SevenRooms handled its compliance work.
- Scheduled maintenance jobs: Anything that needs to run on a cadence instead of on commit can be scripted and scheduled. Netguru wrote a maintenance script, wired it into CircleCI, and set it on a monthly schedule.
- LLM and AI application testing: CircleCI documents testing LLM-powered applications with AIConfig and pytest inside continuous integration. Its own Q2 2026 delivery data drew on 20 million workflows run in March 2026. Feature-branch throughput rose 7.7% year over year while main-branch throughput stayed entirely flat, and that gap is the bottleneck this tooling targets.
- SOC 2 compliance pipeline automation: Kajabi scaled one pipeline setup to 80 concurrent containers and 250 parallel tests. SevenRooms reached SOC 2 compliance using the Jira, Slack, and TestRail orbs alongside Dynamic Config.
Key Features of CircleCI
CircleCI's 2026 feature set centers on autonomous pipeline validation and flexible compute, with releases as recent as July 2026.
- Chunk, the autonomous CI/CD agent: Chunk launched in September 2025 as an always-on agent that runs at the pipeline layer. It fixes flaky tests on a schedule and keeps dependencies current. Since June 2026 it commits changes and opens pull requests during a run, and it reruns pipelines that fail on transient infrastructure errors, so a flaky night stops becoming a morning of triage.
- Chunk sidecars and microbuilds: Announced in May 2026, sidecars run a CI-like microbuild inside the coding agent's own loop, before code reaches CI at all. CircleCI reports an average 27-second microbuild and 78% faster feedback than a full pipeline run, captioned on its own page as early results from internal testing and early access customers. Sidecars are free on every plan and work with any coding agent, Claude Code and Codex included. This is CircleCI's only 2026 release with no GitHub Actions counterpart.
- Self-hosted runner autoscaling: Runner Provisioner is a Kubernetes controller that auto-scales runner VMs with KubeVirt. It polls CircleCI for pending tasks and adjusts pool replica counts to match. A July 2026 release added time-based scaling schedules and hot-reload of configuration and secrets, so a self-hosted fleet picks up a change without a restart.
- MCP server and agent-tuned CLI: The MCP Server connects AI assistants directly to pipelines and gives IDE-based tools access to build logs and pipeline status. A new CLI entered beta on June 29, 2026 with an MCP server built in and explicit tuning for agents like Claude Code.
- Orbs registry: The public registry holds roughly 3,800 orbs, reusable configuration packages that wire integrated DevOps tools into a pipeline without hand-written YAML. The most widely adopted are circleci/node and circleci/aws-cli, each active in thousands of organizations.
- Executors and resource classes: Docker on x86 or Arm, Linux VM, macOS, Windows, GPU, and Arm VM are all available as execution environments. The resource_class key sets CPU and RAM per job, from Docker Small at 1 CPU and 2 GB RAM up to GPU Large on an Nvidia Tesla V100. macOS M4 Pro requires Performance or Scale.
- Generation matters as much as size: Linux VM classes ship in three generations at different rates. Gen 3 Medium costs 7 credits per minute against Gen 1 Medium's 10, for the same 2 CPU. Picking the wrong generation costs about 30% more for identical compute.
- Configuration-as-Code: The whole pipeline lives in a config.yml file inside a .circleci folder at the project root, on config version 2.1. CircleCI also ships a TypeScript config generator and a policy engine that enforces config rules through Open Policy Agent before execution.
- Native Docker Layer Caching: CircleCI caches individual image layers and reuses the unchanged ones on later runs. Docker Layer Caching (DLC) costs 200 credits per job run. GitHub Actions has no native equivalent.
- SSH debugging: Engineers can SSH into a running or failed build container and debug interactively. Commands get validated at the point of failure, with no full rerun required.
- Security and compliance: As of CircleCI's published security and trust pages in August 2026, the platform holds FedRAMP LI-SaaS (FedRAMP Tailored) authorization, first granted in 2018, and SOC 2 Type II compliance. Its Trust Center lists CSA STAR Level 1, the CSA AI Trustworthy Pledge 2025, and EU-US, Swiss-US and UK Extension Data Privacy Framework certification.
CircleCI Pros & Cons
CircleCI's pipeline features are ahead of its main competitor's and its billing model is behind, which is most of the evaluation in one sentence.
What Users Say
What users consistently praise:
- SSH debugging: Treated as a concrete differentiator, and named repeatedly as the feature engineers miss after moving to another platform.
- Test parallelism and automatic splitting: Consistently praised. Teams report suite times cut by more than half after splitting across workers, with no hand-tuning of which tests land where.
- Docker and container-based execution: A clean container per job, with full control of the image, is credited with reproducible builds and no infrastructure work.
- Git host integration: Described as straightforward and reliable, with CI triggering dependably on pull requests and no missed commits.
- Resource class flexibility: Setting CPU and RAM per job inside the config file is credited with controlling build cost at the job level.
What users consistently complain about:
- Credit billing unpredictability: The most consistent criticism. Docker Layer Caching and IP ranges are seen as expensive without active tuning, and the pricing page itself gets called confusing. Four-figure monthly bills come up repeatedly as the trigger for evaluating alternatives.
- No per-job cost visibility: Reviewers report being unable to tell what a specific job or workflow actually costs, which makes the credit model hard to govern, not just expensive.
- Platform outages that consume credits: Infrastructure failures, OOM errors and connectivity drops among them, draw down credits when the fault lies with CircleCI. Outages are described as frequent enough to affect planning, and support during an outage is a separate complaint from support generally, which reviewers rate well.
- YAML configuration scale: Config files become unmanageable on large projects, growing to thousands of lines with no native multi-file structure.
- The move toward per-user charging: Reviewers name recent pricing-model changes, and the per-user component in particular, as the reason they started evaluating other vendors.
Where reviewers diverge:
- Structured review scores against practitioner forums: Buyer-review platforms hold positive aggregate scores, where pricing is a noted weakness that does not collapse the rating. One platform records 91 positive and zero negative reviews out of 93. Forums run markedly more negative, with individual practitioners reporting order-of-magnitude cost differences against self-hosted alternatives and treating CircleCI as a platform teams graduate away from. Self-selection accounts for most of the gap, since the engineers with cost-comparison data are the ones who post it.
- Which scores rest on real volume: The strongest marks sit on the thinnest samples. The pipeline-specific dimensions that flatter CircleCI most were rated by roughly two dozen reviewers each, while the middling scores for ease of use and support carry several hundred. Read the high numbers as directional, not settled.
- Whether CircleCI is still a primary choice: It turns up as a considered alternative for teams that GitHub Actions or GitLab CI cannot serve, not as a default first pick. Even its defenders frame it as the stronger product carrying unresolved cost limitations.
CircleCI Pricing
One credit works out to $0.0006, derived from CircleCI's own block rate of $15 per 25,000 credits, and every figure below follows from that multiplied by the CPU and RAM each job requests. So which resource class do your slowest pipelines actually run on? That answer moves your bill more than the plan you pick.
Rates come from CircleCI's pricing page and price list. All pricing information verified August 2026.
Gotchas:
- CircleCI advertises up to 6,000 free build minutes, a figure that only holds on Docker Small at 5 credits per minute. At Linux Medium (10 credits/min), 30,000 credits buys 3,000 minutes, not 6,000. CircleCI uses that exact example on its own pricing page.
- Additional credits on Performance are sold in blocks of 25,000 for $15.
- Bulk prepaid credits are sold at 1 million for $600 and 5 million for $3,000. Both work out to $0.0006 per credit, the same rate as the standard block, so the advertised volume discount does not appear at either published price point.
- Users beyond the five included cost 25,000 credits per user per month on Performance, and 40,000 on Scale.
- Auto-refill is the default purchase option on Performance. When credits run out, the account refills to 25% of the monthly purchase amount, with a minimum refill of 25,000 credits, which produces charges nobody approved that month.
- Purchased credits roll over month-to-month and expire 12 months after purchase. The 30,000 credits included with Performance do not roll over, and Free plan credits reset monthly.
- GPU instances, Nvidia Tesla P4 through V100, are Scale-only at 160 to 1,000 credits per minute depending on class.
- Docker Layer Caching costs 200 credits per job run, roughly $0.12, on every plan. Three parallel Docker build jobs draw 600 credits per run.
- IP ranges cost 450 credits per GB and are unavailable on Free.
- Network and storage carry a monthly allowance before anything is billed: 1 GB network on Free, 5 GB on Performance, 50 GB on Scale. Beyond the allowance, both bill at 420 credits per GB, or $0.252. Egress applies to self-hosted runners only, and CircleCI does not pass on egress from its own cloud executors.
- Self-hosted runner concurrency is capped at 5 concurrent tasks on Free and 20 on Performance, and is unlimited on Scale. CircleCI charges no per-build-minute fee on self-hosted runners.
- macOS is capped at 1 concurrent job on Free against 15 on Performance, and macOS M4 Pro (Medium and Large) is not available on Free.
- Free leaves out more than credits. Flaky test detection stops at 5 tests. SSO and config policies are absent from both Free and Performance, and appear only on Scale.
- Open source projects on the Free plan can access up to 400,000 credits per month, equivalent to 80,000 build minutes, for Linux, Arm, and Docker. Open source Windows and macOS builds, and private repositories, get only the standard 30,000.
- Eligible startups can apply for up to $20,000 in compute credits and up to 24 months of free access, including Starter Support valued at $249 per month. The gate is narrow: new to CircleCI or on Free, Pre-Seed through Series A, founded within the last five years, and backed by a recognized accelerator or VC, or able to show $500,000 raised.
- Scale requires an annual contract and is quote-only through sales. There is no self-serve path onto it.
Is CircleCI Worth It?
CircleCI delivers pipeline capabilities that justify its pricing for teams that use them. The credit model punishes teams that do not actively manage usage.
Yes, if:
- Your builds are slow because of Docker image rebuilds or a test suite that runs serially, and you want caching and splitting working without plugin configuration.
- You build for iOS, Android, or both, and GitHub-hosted runner equivalents have not held up.
- Your code is spread across more than one Git host and you need one CI system covering all of it.
- You run under roughly 3,000 build-minutes a month at Medium compute, which the Free plan's credits cover outright.
- You operate in a regulated environment where FedRAMP LI-SaaS and SOC 2 Type II are procurement requirements.
- You want an agent inside the CI loop that fixes flaky tests and opens pull requests on its own.
Look elsewhere if:
- Your codebase already lives on GitHub and nobody on the team wants to maintain a second CI system. GitHub Actions is the shorter path.
- You would rather answer to one vendor and one bill for version control, CI, and deployment. GitLab CI/CD covers that ground.
CircleCI vs GitHub Actions
These are the two platforms most teams end up choosing between, and the decision usually comes down to where your code lives and whether pipeline-specific features matter more than native GitHub integration.
Where CircleCI wins:
- Docker Layer Caching: CircleCI has native DLC and GitHub Actions does not. Its absence is the most-cited reason developers report slower builds on GitHub Actions.
- Test parallelism: Automatic test splitting by historical timing data is built in, with no native GitHub Actions equivalent. CircleCI also supports up to 80 concurrent jobs on Performance.
- SSH debugging: CircleCI lets engineers SSH into a running or failed build container. Practitioners regularly cite this as the thing they miss after migrating.
- Resource class precision: CPU and RAM are set per job, which prevents overpaying for lightweight tasks and opens GPU and Arm options that standard GitHub Actions runners do not offer.
- Build speed at high concurrency: CircleCI's own head-to-head analysis, published February 2025, replayed 24 hours of React commits on both platforms at a matched 500-job concurrency limit. It measured CircleCI pipelines running 40.29% faster at the median, with queue times under 30 seconds against median waits above 22 minutes on GitHub's larger runners. It is a vendor benchmark, not an independent one. The finding worth testing against your own workload is the concurrency ceiling: GitHub Actions never exceeded roughly 124 simultaneous jobs despite a 500-job allowance.
Where GitHub Actions wins:
- Native GitHub integration: Pull requests, deployments, security scanning, and secrets are first-class in one UI. CircleCI's GitHub integration is webhook-based and lives on a separate dashboard.
- Marketplace size: The Actions Marketplace carries several times the number of reusable components in CircleCI's orbs registry.
- Cheaper and simpler compute: GitHub Free provides 2,000 minutes and 500 MB of storage per month on private repositories, and Pro and Team provide 3,000. Public repositories run unmetered. A per-minute rate is also easier to forecast than a credit multiplier that changes with resource class and generation.
- A rate that moved in the buyer's favor: GitHub cut hosted-runner prices by up to 39% on January 1, 2026. Linux 2-core went from $0.008 to $0.006 per minute. The cost gap that already drove CircleCI migrations widened on that date.
- OIDC and cloud federation: Federation to AWS, GCP, and Azure ships out of the box.
CircleCI Alternatives
Teams that leave CircleCI go in one of two directions, and the pipeline features are rarely the reason.
GitHub Actions: Pick this if the second CI bill is the thing you want gone. Actions charges $0.006 per minute after the free tier with no credit multiplier to model, and it removes a separate platform from the stack entirely.
GitLab CI/CD: Pick this if you would rather consolidate than integrate. GitLab ships version control, CI, security scanning, a container registry, and deployment under one contract, which turns CircleCI's CI-only scope into a gap you have to fill with something else.
How CircleCI Works With Siit
Siit does not integrate directly with CircleCI. CircleCI runs at the code pipeline layer, outside the scope of Siit's AI Service Desk, which handles internal IT, HR, Finance, and Operations requests for employees.
The overlap sits around the pipeline, not inside it, in the requests engineers raise while working there. Siit connects natively to the code hosts CircleCI builds from, through Siit's GitHub integration or Siit's GitLab integration. A repository or project access request can be tracked where the rest of the work already runs. Both integrations sync data into Siit and do not drive CircleCI itself.
The requests that actually stall engineers are access requests. Password resets and application assignments run through Okta. Device actions like lock and wipe are triggered by an admin from the request side panel, without opening the MDM console. Employee data is read from connected HRIS systems on a one-way sync. Routing those as automated access requests is what removes the waiting.
Requests arrive in Slack or Microsoft Teams, where routing and approvals run automatically. That is the adoption problem DevOps ITSM platforms usually lose to, because developers do not open portals. Handling the request where the developer already is means nobody gets chased and nobody waits on a queue they cannot see.
