Try our new research platform with insights from 80,000+ expert users

Microsoft Azure DevOps vs Spinnaker comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 7, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Microsoft Azure DevOps
Ranking in Release Automation
1st
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
135
Ranking in other categories
Application Lifecycle Management (ALM) Suites (2nd), Enterprise Agile Planning Tools (1st)
Spinnaker
Ranking in Release Automation
8th
Average Rating
8.0
Reviews Sentiment
6.5
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2025, in the Release Automation category, the mindshare of Microsoft Azure DevOps is 33.0%, down from 40.5% compared to the previous year. The mindshare of Spinnaker is 1.7%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Release Automation
 

Featured Reviews

Ivan Angelov - PeerSpot reviewer
Facilitates agile transformation with potential for enhanced intuitiveness
What I liked about the solution is that it offers numerous features that are not available by default unless you are agile. Transitioning from the traditional Waterfall model to an agile methodology was challenging for us. Until 2020, our team predominantly worked with the Waterfall approach, using local tools like ServiceNow. We had a few team members who were familiar with Agile ISO, but none had experience with Azure. Therefore, we pursued Azure certification at the AZ-900 level. Our company organized a training session with a certified Azure expert, which was extremely beneficial for adopting best practices during the initial three months. This preparation helped us get accustomed to the new tool, as transitioning to a new system invariably requires time. Managing a pipeline of deliverables became significantly easier with this solution. We utilized it for stories and integrated change management with Azure DevOps. Eventually, everything related to the environment was organized there, enabling us to follow up and track progress with our technical engineers on an hourly, daily, or weekly basis. Reports were automatically generated and sent to management, offering them insights into our progress concerning the predefined roadmap.
Anurag Bandyopadhyay - PeerSpot reviewer
Useful to create custom pipelines
Regarding areas for improvement, one significant issue is the lack of maker-checker flows to ensure that newly created pipelines are accurate and tested. We currently use an in-house abstraction over Spinnaker to verify pipeline specs, environment variables, etc. It would be beneficial if Spinnaker could offer this functionality within their product.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"You can have test cases in DevOps but not in JIRA. And, DevOps has advantages in terms of executing those test cases."
"The most valuable feature is the ease of use and performance."
"We use all the DevOps features and services, like reports, Boards, Pipelines, Artifactory, etc. The interface is interactive and intuitive. The platform visuals and workflow are straightforward in Azure DevOps."
"The creation of test plans is valuable and I like the reporting features."
"It is good for the purpose it is designed for. It is good for maintaining a repository of application code, creating pipelines for deploying the code, building the code, and deploying the code. It can be easily used by developers. There are no issues."
"I like the entire tool because it is a one-stop-solution for DevOps."
"It's very user-friendly, and the documentation is good. The most valuable feature is backlog item creation, where we pick features and other things. The burndown chart created for projects to be maintained by the development teams is also useful."
"Some of the valuable features are the interface and the workflows are easy to learn and to manage."
"The tool's most valuable feature is its intuitive interface for converting existing Kubernetes specs into working pipelines. It's easy for anyone to deploy anything on any environment when they need to test or deploy for a specific merchant or use case. Instead of going into the specs and changing different variables, they can do it through the UI, which is very useful."
"The most valuable feature of Spinnaker is the rollback."
"Spinnaker is used for automating a variety of deployment tasks, infrastructure, provisioning tasks, and all kinds of things."
"There is a good community around the product that makes troubleshooting possible."
 

Cons

"The initial three months were particularly challenging, and without the help of an external consultant, adapting to the change in work processes would have been difficult."
"At times, our development work encounters issues, particularly when executing numerous CI/CD processes."
"It would be great if I could integrate with a human resource type of software that could control timesheets."
"While reporting in Azure DevOps is a robust capability, there's always room for enhancement, particularly in providing more granular reports."
"Templates could be improved."
"Non-functional testing such as security testing, log testing, and performance testing can be improved with a better visualization."
"Its interface could be more user-friendly. It could be simplified for users with no prior knowledge. There should also be better tutorials."
"The optimization feature in Microsoft Azure DevOps needs improvement. Control over multiple projects could also be improved."
"Regarding areas for improvement, one significant issue is the lack of maker-checker flows to ensure that newly created pipelines are accurate and tested. We currently use an in-house abstraction over Spinnaker to verify pipeline specs, environment variables, etc. It would be beneficial if Spinnaker could offer this functionality within their product."
"Spinnaker's configuration setup is too complicated and should be made easy."
"Log-wise, we need to understand why something has failed so that we can understand and try to fix it the moment the issue is reported. The solution could use more robust monitoring."
"Every time it goes to run a pipeline, it just generates a lot of data, and its database is not exactly tuned out of the box, meaning it is not tuned for high scalability."
 

Pricing and Cost Advice

"The solution is expensive."
"As the cost structure is per user, I would recommend paying the cost structure based on the amount of data you use rather than the number of users."
"I am not aware of any licensing subscriptions for the solution."
"Its pricing is reasonable for the number of features that you get and the functionality that you can utilize for the agile delivery, which is what we are using it for. I found it extremely cost-effective."
"There is a license for this solution."
"I don't know what we pay, but I do know what I've seen online. If we switched to JIRA, we will basically have to double our costs because we still have to pay for the DevOps licensing. We're probably spending $100 a month on it. It has only standard licensing fees."
"For the basic license, it is around five euros per month."
"Microsoft Azure DevOps is an expensive solution."
"Spinnaker is an open-source product. The tool is completely free for users."
"The solution is open-source."
"Spinnaker is a free-to-use, open-source solution."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
865,164 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
13%
Computer Software Company
12%
Financial Services Firm
11%
Government
9%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Which is better - Jira or Microsoft Azure DevOps?
Jira is a great centralized tool for just about everything, from local team management to keeping track of products and work logs. It is easy to implement and navigate, and it is stable and scalabl...
Which is better - TFS or Azure DevOps?
TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvements. In addition, TFS seems complicated to use and I don’t think it has a very fri...
What do you like most about Microsoft Azure DevOps?
Valuable features for project management and tracking in Azure DevOps include a portal displaying test results, check-in/check-out activity, and developer/tester productivity.
What do you like most about Spinnaker?
The most valuable feature of Spinnaker is the rollback.
What needs improvement with Spinnaker?
Regarding areas for improvement, one significant issue is the lack of maker-checker flows to ensure that newly created pipelines are accurate and tested. We currently use an in-house abstraction ov...
 

Also Known As

Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
No data available
 

Overview

 

Sample Customers

Alaska Airlines, Iberia Airlines, Columbia, Skype
Information Not Available
Find out what your peers are saying about Microsoft Azure DevOps vs. Spinnaker and other solutions. Updated: July 2025.
865,164 professionals have used our research since 2012.