StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Continuous Integration
  4. Continuous Integration
  5. Appveyor vs Azure Pipelines

Appveyor vs Azure Pipelines

OverviewDecisionsComparisonAlternatives

Overview

Appveyor
Appveyor
Stacks123
Followers131
Votes94
Azure Pipelines
Azure Pipelines
Stacks2.3K
Followers457
Votes14

Appveyor vs Azure Pipelines: What are the differences?

# Introduction
This Markdown code provides a comparison between Appveyor and Azure Pipelines based on key differences.

1. **Pricing Model**: Appveyor follows a usage-based pricing model where you are charged based on the number of concurrent jobs, while Azure Pipelines offers a free tier for open-source projects and allows for unlimited build minutes with paid plans.
2. **Supported Platforms**: Appveyor primarily focuses on Windows-based applications, while Azure Pipelines provides support for a wider range of platforms including Windows, Linux, and macOS.
3. **Integration with Microsoft Ecosystem**: Azure Pipelines seamlessly integrates with other Microsoft services such as Azure DevOps, GitHub, and Visual Studio, providing a holistic development environment, whereas Appveyor offers integration with Git-based repositories but lacks the depth of integration seen in Azure Pipelines.
4. **Customization and Extensibility**: Azure Pipelines provides extensive customization options through YAML configurations, allowing users to define complex build pipelines, whereas Appveyor offers a more simplified approach with a user-friendly interface for configuring builds.
5. **Community and Support**: Azure Pipelines benefits from a larger user community and extensive documentation, making it easier to find resources and support, whereas Appveyor has a smaller community but provides personalized support for its users.
6. **Deployment Options**: Azure Pipelines offers a wide range of deployment options including Azure, Kubernetes, and third-party services, whereas Appveyor focuses primarily on deployment to cloud services such as Azure and AWS.

In Summary, this Markdown code highlights key differences between Appveyor and Azure Pipelines in terms of pricing, platform support, integration, customization, community support, and deployment options.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Appveyor, Azure Pipelines

Balaramesh
Balaramesh

Apr 20, 2020

Needs adviceonAzure PipelinesAzure Pipelines.NET.NETJenkinsJenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

663k views663k
Comments

Detailed Comparison

Appveyor
Appveyor
Azure Pipelines
Azure Pipelines

AppVeyor aims to give powerful Continuous Integration and Deployment tools to every .NET developer without the hassle of setting up and maintaining their own build server.

Fast builds with parallel jobs and test execution. Use container jobs to create consistent and reliable builds with the exact tools you need. Create new containers with ease and push them to any registry.

Scriptless, repetitive, one-click deployment of build artifacts to multiple environments;YAML configuration;Backed by Windows Azure platform;Built-in NuGet feeds with project artifacts;Build artifacts are stored in a highly-durable Geo-redundant cloud storage;
Any language, any platform; Containers and Kubernetes; Extensible; Deploy to any cloud; Open source; Advanced workflows and features
Statistics
Stacks
123
Stacks
2.3K
Followers
131
Followers
457
Votes
94
Votes
14
Pros & Cons
Pros
  • 20
    Github integration
  • 18
    Simple, reliable & powerful
  • 12
    Hosted
  • 11
    YML-based configuration
  • 10
    Nuget support
Cons
  • 1
    Poor documentation
  • 1
    Complex user interface
Pros
  • 4
    Easy to get started
  • 3
    Built by Microsoft
  • 3
    Unlimited CI/CD minutes
  • 2
    Yaml support
  • 2
    Docker support
Integrations
GitHub
GitHub
Bitbucket
Bitbucket
.NET
.NET
.NET Core
.NET Core
Slack
Slack
Python
Python
Ruby
Ruby
Kubernetes
Kubernetes
.NET
.NET
Node.js
Node.js
Linux
Linux
Microsoft Azure
Microsoft Azure
RxJava
RxJava

What are some alternatives to Appveyor, Azure Pipelines?

Jenkins

Jenkins

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Travis CI

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

TeamCity

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana