Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing AppVeyor vs Netlify, the Slant community recommends AppVeyor for most people. In the question“What are the best continuous deployment services?” AppVeyor is ranked 2nd while Netlify is ranked 4th. The most important reason people chose AppVeyor is:
AppVeyor is free for public GitHub repositories.
Specs
Question Ranking
Pros
Pro Free for open-source projects
AppVeyor is free for public GitHub repositories.
Pro Supports Windows build enviroment
AppVeyor has a build environment for Windows available.
Pro Clear, straight-forward user interface
Well I suggest you check it out for yourself, but what I like most is that it's simple yet effective: no bells and whistles, simple black/grey/light-blue/white color scheme, it's immediately clear where you have to go for each specific task, and build settings pages are like that as well. Getting a 'standard' build running literally took me a minute the first time I used it.
Pro Easy access to build VM
AppVeyor allows the user to login to the actual build VM.
Pro The initial setup is easy
There's practically no setup involved prior to working with AppVeyor: simply sign in, add the project, and start a new build.
Pro Netlify CDN
Pro Free one-click SSL
Pro Continuous deployment
Pro Custom domains
Pro Versioning and rollbacks
Pro Free tier
Netlify's PRO Plan now Free for Open-Source Projects
Pro Webhooks and integrations
Pro Redirect, rewrite and proxy rules
Pro Full featured CLI
Pro Custom HTTP headers
Pro Support simple forms
Pro Post processing
The post processing doesn't really work. It's a good idea, though!
Pro Functions
Can deploy aws functions without an aws account.
Pro Multiple environment support
Pro Atomic deploys
Pro RESTful API
Cons
Con Not free
This is open-source but not free.
Con Configuration is limited
AppVeyor's configuration (which is done from the .yaml file in the root of the project) is unfortunately very limited. The configuration is either tied to a branch or, in other cases, it's global. This limits the developer to a single build process.
However, since you can use arbitrary scripts for building, all those limitations can be overcome. Configuration can also be done from the web UI without a .yaml file.
