We detected 502 companies using CircleCI. The most common industry is Software Development (40%) and the most common company size is 2-10 employees (36%). We find new customers by discovering URLs with known URL patterns through web crawling or modifications to subprocessor lists.
Note: We track companies that use CircleCI on a public Github repo
๐ Who usually uses CircleCI and for what use cases?
Source: Analysis of job postings that mention CircleCI (using the Bloomberry Jobs API)
Job titles that mention CircleCI
i
Based on an analysis of job titles from postings that mention CircleCI.
Job Title
Share
Director of Engineering
17%
Director of DevOps
14%
Vice President of Engineering
10%
Senior DevOps Engineer
9%
I noticed that CircleCI's buyers are predominantly engineering leadership, with Directors of Engineering (17%), Directors of DevOps (14%), and VPs of Engineering (10%) making up the core purchasing decision makers. These leaders are hiring for transformation and scale, prioritizing CI/CD pipeline modernization, cloud infrastructure optimization, and platform engineering capabilities. Their strategic focus centers on accelerating software delivery velocity while maintaining security and reliability standards.
The day-to-day users are DevOps engineers, SREs, and platform engineers who embed CircleCI into their deployment workflows. They're building and maintaining automated pipelines, implementing infrastructure as code, orchestrating Kubernetes deployments, and managing multi-cloud environments across AWS, Azure, and GCP. Senior practitioners also drive automation initiatives to reduce manual toil and enable development teams to ship faster with confidence.
The job postings reveal companies are solving for speed and safety simultaneously. They want to "accelerate software delivery velocity" and "reduce time spent on data mechanics" while ensuring "secure, efficient software delivery." Multiple roles emphasize building "scalable, secure, and highly available" systems and creating "fast, safe, and confident" paths to production. The recurring theme is eliminating bottlenecks through automation, as one posting notes the need to "identify bottlenecks in the delivery pipeline using data insights and implement solutions to mitigate."
๐ฅ What types of companies use CircleCI?
Source: Analysis of Linkedin bios of 502 companies that use CircleCI
Company Characteristics
i
Shows how much more likely CircleCI customers are to have each trait compared to all companies. For example, 2.0x means customers are twice as likely to have that characteristic.
Trait
Likelihood
Funding Stage: Series B
58.9x
Funding Stage: Series A
33.5x
Funding Stage: Series unknown
25.8x
Industry: Software Development
19.3x
Industry: Information Technology & Services
12.0x
Industry: Technology, Information and Internet
8.3x
I noticed that CircleCI's users span a remarkably wide range, but they share a common thread: they're building software products, not just using software. These companies develop everything from mobile apps and web platforms to blockchain infrastructure, AI agents, and SaaS tools. Many are creating developer tools, fintech products, digital voting systems, or e-commerce platforms. What stands out is that even the non-tech companies like Flybondi (airlines) or Ergeon (construction) are fundamentally technology companies that happen to operate in traditional industries.
The maturity level varies dramatically. I see early-stage startups with 2-10 employees like TRMNL and Virta Labs alongside established players like Cloudera and Indiana University with thousands of employees. However, the majority cluster in the 11-200 employee range, suggesting growing companies in scale-up mode. Many have raised seed or Series A funding, indicating they're past proof-of-concept but still building. Even the larger organizations seem to operate with a startup mentality, emphasizing innovation and agility.
๐ง What other technologies do CircleCI customers also use?
Source: Analysis of tech stacks from 502 companies that use CircleCI
Commonly Paired Technologies
i
Shows how much more likely CircleCI customers are to use each tool compared to the general population. For example, 287x means customers are 287 times more likely to use that tool.
I noticed that CircleCI users are overwhelmingly developer-first companies with sophisticated engineering practices. The extreme correlation with tools like Dependabot, Github Advanced Security, and verified Github organizations tells me these are companies that treat code quality, security, and automation as core business priorities. They're likely building technical products where engineering velocity directly impacts revenue, and they're mature enough to invest in the full developer tooling ecosystem.
The pairing with Github Actions is particularly revealing. These companies aren't just using one CI/CD tool, they're running multiple automation platforms simultaneously. This suggests complex deployment workflows where different tools handle different parts of the pipeline. The strong correlation with Terraform makes perfect sense here too. If you're automating infrastructure as code and running sophisticated CI/CD, you need both. The presence of Dependabot and Github Advanced Security together shows these teams are proactive about maintenance, automatically updating dependencies and scanning for vulnerabilities rather than waiting for problems to emerge.
My analysis shows these are product-led companies in growth or mature stages. They've moved past scrappy startup phase where engineers manually deploy code. The verified Github organization status and security tooling indicate they're probably Series B and beyond, dealing with compliance requirements and institutional customers who care about security postures. They're not sales-led enterprises that might standardize on a single vendor suite. Instead, they're technical organizations that choose best-of-breed tools and integrate them together.
Alternatives and Competitors to CircleCI
Explore vendors that are alternatives in this category