Companies that use AppVeyor

Source: Analysis of job postings that mention AppVeyor (using the Bloomberry Jobs API)

I found that AppVeyor buyers are primarily DevOps Engineers (35%), Backend/Full Stack Engineers (29%), and Site Reliability Engineers (18%). These are individual contributor roles, not leadership positions, which tells me AppVeyor purchasing decisions happen at the team level rather than from executive budgets. The hiring companies prioritize CI/CD pipeline automation, cloud infrastructure management, and continuous deployment capabilities. They're building modern software delivery systems across AWS, Azure, and GCP environments.

The day-to-day users are practitioners automating build and release processes. I noticed they're configuring secure CI/CD pipelines alongside tools like Jenkins, GitLab, Docker, and Kubernetes. These engineers handle everything from code compilation and testing to deployment automation across multiple environments. They work on containerization, infrastructure as code, and integrating security scanning tools into delivery pipelines.

The core pain point these companies face is reducing manual toil and accelerating software delivery. Multiple postings emphasized "automate tools to monitor system health," "streamline operations," and "enable teams to move faster." One posting explicitly stated the goal of "automating the manual tasks" while another highlighted building "CI/CD pipelines for continuous operation." Companies want self-service deployment capabilities and are migrating to modern architectures with serverless and containerized workloads, requiring robust automation tooling to support developer velocity.

Source: Analysis of Linkedin bios of 605 companies that use AppVeyor

I noticed that AppVeyor's users are predominantly software development companies, but not in the consumer app sense. These companies build infrastructure, tools, and technical platforms that other developers and enterprises use. I'm seeing a lot of open-source projects (Node.js, Golang, MariaDB Foundation), developer tool companies (Heroku, Mapbox, Snyk), and businesses creating specialized technical solutions like blockchain infrastructure, scientific computing platforms, and cybersecurity tools. Many are building what I'd call "developer-first" products or maintaining critical open-source ecosystems.

The maturity level varies widely, which is actually the pattern. I'm seeing everything from single-digit employee open-source foundations to companies like Flipkart and Tencent with tens of thousands of employees. However, the sweet spot appears to be companies in the 11-200 employee range, often with some funding (Seed to Series B is common) but not necessarily venture-backed. Many are profitable bootstrapped companies or established players in niche technical markets rather than hypergrowth startups.

Source: Analysis of tech stacks from 605 companies that use AppVeyor

I noticed that AppVeyor users are strongly committed to continuous integration and open source development practices. The overwhelming presence of multiple CI/CD tools like Travis CI, Github Actions, and CircleCI tells me these companies are building software products with complex testing needs, likely maintaining cross-platform compatibility or supporting multiple programming languages. They're typically developer tool companies, open source projects, or technical infrastructure providers with substantial public repositories.

The pattern of using multiple CI services simultaneously is particularly revealing. Companies pair AppVeyor with Travis CI and CircleCI because each service has strengths with different operating systems or build environments. AppVeyor historically excelled at Windows builds while Travis CI dominated Linux testing, so companies maintaining cross-platform libraries naturally adopted both. The high correlation with Dependabot and verified Github organizations reinforces this: these teams prioritize automated dependency management and establish credibility through official organizational presence on Github.

The tech stack reveals product-led companies in earlier growth stages. These aren't sales-led enterprises with traditional sales automation tools. Instead, they're shipping software to technical audiences who evaluate products through documentation, Github repositories, and community engagement. The emphasis on public CI badges, automated testing, and dependency updates suggests companies that compete on code quality and reliability. They grow through developer adoption rather than outbound sales teams.