by CircleCI · circleci.com ↗
CI/CD platform for automating builds, tests, and deployments across cloud and self-hosted environments.
CircleCI is a CI/CD platform built to help teams validate code changes, automate testing, and control deployments across a wide range of environments. Its messaging centers on speed, confidence, and flexibility: teams can run jobs in Docker, Linux, Windows, macOS, Arm, GPU, or on self-hosted runners, while using credits to pay for compute, users, and add-ons as usage changes over time. That makes CircleCI a practical fit for organizations that want to start small, then scale into more advanced concurrency, compliance, and infrastructure needs as their delivery footprint grows.
For buyers, the main appeal is the combination of broad execution support and a pay-for-what-you-use model. The Free plan gives teams a low-friction entry point, while Performance and Scale expand compute, concurrency, support, and control for larger workflows. CircleCI also emphasizes features that matter in day-to-day delivery work, including Docker layer caching, flaky test detection, deploy controls, and self-hosted runners. The result is a platform aimed at reducing queue times, improving feedback cycles, and helping engineering teams ship with more confidence.
The supplied materials also show a product that is designed for modern development workflows, not just traditional build pipelines. CircleCI highlights autonomous validation, smarter testing, rollback support, and tooling for AI agents and other role-based users. That positioning suggests the product is meant for teams that need CI/CD to keep up with fast-changing codebases, mixed environments, and increasingly automated software delivery practices.
CircleCI’s pricing model is built around credits, which are used to pay for users, compute, and certain add-on features. The platform offers multiple plan tiers, including Free, Performance, Scale, and Server, so teams can start small and increase capacity as usage grows. Documentation also explains refill behavior, prepaid billing, and how credits roll over or expire depending on the plan. This makes the billing model especially relevant for teams that want predictable usage tracking with room to scale.
CircleCI says credits are used for platform usage in real time, including monthly active users, compute time, add-on features, and additional network and storage use. The company also notes that credits are purchased in packages and can be managed through the plan overview in the app.
The pricing pages describe Free, Performance, and Scale tiers, with Server available for on-premises use. Free is the entry point, Performance adds more compute and support, and Scale is built for unlimited scale and enterprise controls.
CircleCI documents both monthly and prepaid billing options for Performance plan customers, including automatic refills when credits run low. The pricing FAQ also explains that prepaid billing is discounted by volume and that paid credits have a defined expiration window.
CircleCI supports a broad set of execution environments, which helps teams standardize CI/CD across different application types and infrastructure choices. The pricing and product pages list Docker, Linux VM, Arm, Windows VM, macOS VM, remote Docker, and GPU options. The plans overview also highlights access to larger machine sizes, concurrency, and self-hosted runners as teams move up-tier. This breadth is useful for organizations with mixed workloads, mobile builds, or specialized compute requirements.
The platform supports Docker, Linux VM, Arm VM, Windows VM, macOS VM, and GPU resource classes, with different availability depending on plan tier. That range makes it practical for teams shipping everything from containerized services to mobile apps and specialized workloads.
CircleCI describes concurrency as running multiple jobs at the same time to reduce queue times and shorten feedback cycles. Higher tiers add more concurrent job runs, and the Scale plan allows custom concurrency limits.
CircleCI supports self-hosted runners so teams can execute jobs on their own infrastructure. The docs note that runner capacity is plan-dependent, with unlimited self-hosted runners available on Scale.
CircleCI emphasizes features that reduce feedback time and help teams ship with confidence. The product and plan pages call out Docker layer caching, flaky test detection, deploys, private orbs, and support for incremental release workflows. The site also highlights autonomous validation, smarter testing, and the ability to run only the tests that matter. These capabilities are aimed at teams trying to reduce wasted compute and improve release reliability.
CircleCI documents Docker Layer Caching as a way to save image layers created during jobs so future builds can reuse them. The plans overview calls out DLC as a feature available on all plans, while pricing shows it as a paid add-on in usage credits.
The plans overview says flaky test detection is included, with more advanced insights available on higher plans. CircleCI positions this as a way to reduce wasted time from failed workflows and improve troubleshooting.
CircleCI describes deploys as a way to visualize and control deployments, including support for Kubernetes. The product page also emphasizes rollback, incremental releases, and release orchestration as part of the delivery workflow.
CircleCI’s own materials position the product for developers, platform engineers, security engineers, engineering managers, business leaders, and AI agents. The company overview and product pages emphasize validated change, fast feedback, and enterprise-grade confidence, while the plans overview frames Free as a fit for individual developers and small teams and Scale as a fit for large organizations with advanced compliance and infrastructure requirements. The product can serve teams that need modern CI/CD across multiple languages, environments, and deployment patterns. It may be less compelling for buyers who want a simple fixed-price package without usage-based billing or who do not need multi-environment execution.
CircleCI explicitly calls out developers, platform engineers, security engineers, engineering managers, business leaders, and AI agents as intended users. That suggests the platform is designed for cross-functional teams rather than only build-and-release specialists.
The plans overview says Free is designed for individual developers and small teams, Performance for growing teams, and Scale for large organizations with advanced compliance and infrastructure needs. This indicates a clear progression from experimentation to enterprise adoption.
CircleCI offers startup credits and documents separate open-source credit usage on the Free plan. That can make the platform attractive to teams building publicly or trying to get started without immediate upfront spend.
Evaluates CI/CD strategy, developer productivity, and release confidence across teams.
Owns pipeline reliability, execution environments, and infrastructure fit.
Reviews governance, access patterns, and deployment controls for the CI/CD system.
CircleCI is a CI/CD platform focused on validating code changes, running tests, and supporting deployments across cloud and self-hosted environments. Its product and pricing materials emphasize autonomous validation, credit-based billing, broad execution-environment support, and plan options that range from free entry usage to enterprise-scale deployment.
The platform offers Free, Performance, Scale, and Server plan options.
CircleCI supports Docker, Linux, Windows, Arm, macOS, GPU, and self-hosted runners.
The product site emphasizes validation, test orchestration, and deploy confidence.
CircleCI says credits are the unit of compute consumption and are used for users, compute, and add-ons.
CircleCI’s pricing is built around credits rather than a simple per-seat subscription. That matters because the amount you pay is driven by what your pipelines actually consume: active users, machine size, runtime, storage, network transfer, and optional add-ons can all affect the final bill. The public plan structure is straightforward at the top level — Free for getting started, Performance for teams that want more scale and flexibility, and Scale for enterprise customers who need custom limits, premium support, and annual billing. The official pages also make clear that CircleCI’s pricing is meant to expand with usage, so a small team can begin on the free tier and then move into paid credit packages as workflows grow. Publicly disclosed pricing is available for Free and Performance, while Scale is quote-only. For buyers, the practical takeaway is that CircleCI can start at $0, but real spend depends on how many people build, how long jobs run, which resource classes they use, and whether they add support or other metered features.
Measured context shows CircleCI discussed alongside GitLab, Jenkins, Buildkite, Harness, Octopus Deploy, Semaphore, Travis CI, Spinnaker, and Bazel in the CI/CD category. In the material supplied here, CircleCI is positioned as a usage-based platform with broad environment support and strong automation features, while the site also includes direct comparison navigation against GitHub Actions, Harness, Buildkite, Jenkins, and Bitrise. That suggests CircleCI is competing in a crowded CI/CD market where execution flexibility, pricing model, and workflow automation are key differentiators.
These candidates come from measured co-mentions or source-backed alternatives. A full comparison is published only after both products have supporting evidence.
CircleCI is presented across the supplied sources as a CI/CD platform built for teams that need automation without boxing themselves into a single environment or a single pricing style. The official pricing materials emphasize a free entry point, a usage-based Performance plan, and an enterprise-oriented Scale plan, while the third-party marketplace snippets reinforce that buyers can start small and move up as needs expand. That combination is a recurring signal in the documents: CircleCI is aimed at teams that want to automate builds, tests, and deployments while keeping room for growth across Docker, Linux, Windows, Arm, macOS, GPU, and self-hosted runner workloads.
The review and comparison snippets in the provided set do not include star ratings, but they do supply useful buyer signals through review counts and pricing-oriented context. Capterra references 93 reviews, and TrustRadius references 80 verified user reviews and ratings, suggesting meaningful market visibility even though the actual score values are not included in the supplied text. The strongest consistent themes are flexibility, scalable concurrency, and broad environment support. On the downside, the same usage-based model that makes CircleCI adaptable can also make costs less predictable, especially for larger workloads or teams that rely on add-ons, premium support, or high-cost resource classes.
For buyers, that means CircleCI appears best suited to engineering organizations that value control and scale over fixed-price simplicity. Teams with parallel pipelines, mixed infrastructure needs, or a desire to begin on a free plan and expand gradually should find the product fit appealing. Teams that require a simple flat fee, bundled high-touch support, or tightly predictable spend may want to evaluate the credit model carefully before standardizing on the platform.
Examples of how assistants answer real buyer questions in this category.
View all CI/CD prompts →If you need CI/CD platforms that support self-hosted runners or on-prem agents, the strongest mainstream options are: 1. GitHub Actions — supports self-hosted runners; GitHub also documents Actions Runner Controller for Kubernetes-based autoscaling of those runners. ([docs.github.com](https://docs.github.com/en/actions/reference/runners/self-hosted-runners?utm_source=openai)) 2. GitLab CI/CD — supports self-managed runners you install and manage in your own infrastructure, and GitLab documents GitLab Runner for self-managed use. ([docs.gitlab.com](https://docs.gitlab.com/runner/?utm_source=openai)) 3. Azure Pipelines — supports self-hosted agents in Azure Pipelines and Azure DevOps Server. ([learn.microsoft.com](https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/agents?tabs=browser&view=azure-devops&utm_source=openai)) 4. CircleCI — supports self-hosted runners for running jobs on your own infrastructure. ([circleci.com](https://circleci.com/docs/guides/execution-runner/runner-overview/?utm_source=openai)) 5. Jenkins — classic on-prem model with distributed agents under your control, which makes it a natural fit for on-prem execution. Quick buyer take: - For modern SaaS + self-hosted execution, start with GitHub Actions, GitLab, Azure Pipelines, or CircleCI. - For fully on-prem / highly controlled environments, Jenkins and GitLab Self-Managed are often the best fits. If you want, I can also narrow this to the best option for Kubernetes-only, air-gapped, or regulated enterprise environments.
I'll search for current information about CI/CD platforms that support self-hosted runners and on-premises agents.Based on current information, here are the major CI/CD platforms that support self-hosted runners and on-premises agents: ## Top Recommendations GitHub Actions - Runners can be self-hosted or GitHub-managed, making it the most popular choice for teams already on GitHub. Note that GitHub Actions introduced per-minute fees for private self-hosted runners in March 2026, though public repositories remain free. GitLab CI/CD - Self-hosted runners are completely free with no per-minute fees, making it an excellent option if you want to avoid usage-based pricing. GitLab offers both cloud and self-managed deployment options. Buildkite - You run the agents on your own infrastructure (your AWS, your data center), Buildkite orchestrates the pipeline. This hybrid model is particularly strong for teams that need infrastructure control. Buildkite continues to offer unlimited free self-hosted agents. CircleCI - Pipelines are defined in YAML and can run on CircleCI's cloud runners or on self-hosted runners, with autoscaling for self-hosted runner fleets. Jenkins - Jenkins uses a controller-agent architecture that supports distributed builds across multiple agent nodes. It's fully self-hosted and open source, best for organizations that need complete control. Azure DevOps/Pipelines - Cloud-hosted and self-hosted agents with strong integration into the Microsoft ecosystem. TeamCity - JetBrains TeamCity is a powerful CI/CD server, with a polished and user-friendly interface, and offering both hosted and on-premises options. Travis CI - Travis CI supports cloud-hosted builds and self-hosted deployments via Travis CI Server. Harness - Harness supports deployment to Kubernetes clusters, cloud providers, and on-premises infrastructure, with enterprise-grade governance features. For cost optimization, GitLab CI and Buildkite stand o
Many leading CI/CD platforms offer robust support for self-hosted runners and on-premise agents, providing organizations with greater control over their build environments, security, and compliance. Top platforms that support self-hosted runners and on-prem agents include: * Jenkins is an open-source automation server widely recognized for its extensive plugin ecosystem and flexibility, making it a cornerstone for self-hosted CI/CD. It uses agents that can be deployed on-premise or in the cloud, giving administrators full control over the environment. * GitLab CI/CD provides self-managed runners that users can install, configure, and manage on their own infrastructure. This allows for customized environments and is available across all GitLab installations. GitLab also offers a self-hosted edition for the entire DevOps stack. * GitHub Actions supports self-hosted runners, enabling users to customize the hardware, operating system, and software tools used for workflows. These runners can be physical, virtual, containerized, on-premises, or in the cloud. * Azure DevOps (Azure Pipelines) allows for self-hosted agents that users set up and manage. These agents can be utilized with both Azure Pipelines (cloud) and Azure DevOps Server (on-premises), offering control over dependent software and machine-level caches. * CircleCI offers self-hosted runners that enable jobs to run on an organization's own infrastructure. This is beneficial for privileged access, specific compliance needs, or unique compute requirements, with options for machine or container runners. * TeamCity provides both cloud and on-premises options, with its self-hosted edition supporting build agents that can be installed on dedicated machines for customized environments. * Travis CI offers an "On-premises Server" version, known as Travis CI Enterprise, which can be deployed behind a firewall for complete data control and compliance, supporting private cloud or on-premise in
Several CI/CD platforms offer robust support for self-hosted runners and on-premise agents, enabling teams to run jobs on their own infrastructure for security, compliance, or cost reasons.[ ](https://www.legitsecurity.com/blog/securing-your-ci/cd-pipeline-exploring-the-dangers-of-self-hosted-agents)[ ](https://www.nops.io/blog/cost-optimizing-ci-cd-pipelines-with-spot-integrated-asgs/)[ ](https://nespon.com/blog/learn-the-differences-between-on-premise-vs-cloud-ci-cd/)[ ](https://www.harness.io/blog/ci-cd-tools-the-basics) Major CI/CD Platforms Supporting Self-Hosted/On-Premise Agents - [GitHub Actions](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners): Supports self-hosted runners on Linux, macOS, Windows, ARM, and GPU. These runners can be deployed on-premise or in private clouds. - [GitLab CI/CD](https://docs.gitlab.com/runner/): Offers strong, deeply integrated support for self-hosted GitLab Runners that can be installed on-premise or via Docker/Kubernetes. - [ Azure DevOps Pipelines](https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops): Provides agents that can be hosted on-premise or in any cloud environment. - [CircleCI](https://circleci.com/docs/runner-overview/): Supports self-hosted runners for specific hardware, security, or network requirements, allowing you to run jobs behind a firewall. - [Buildkite](https://buildkite.com/): A hybrid CI/CD platform where you host the agents on your own infrastructure, while Buildkite manages the control plane. - [Jenkins](https://www.jenkins.io/): As a self-hosted, open-source automation server, it is designed for running build agents on-premise or in your own virtual machines. - [TeamCity](https://www.jetbrains.com/teamcity/): Offers on-premise or cloud-based server options with robust support for bui
Use Slate to monitor CircleCI over time, understand the source and positioning gaps that influence recommendations, and prioritize what to improve next.
