Progress Chef vs. Spinnaker

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Progress Chef
Score 6.5 out of 10
N/A
Chef IT infrastructure automation suites were developed by Chef Software in Seattle and acquired by Progress Software in September 2020. The Chef Enterprise Automation Stack is an integrated suite of automation technologies presented as a solution for delivering change quickly, repeatedly, and securely over every application's lifecycle. The Chef Effortless Infrastructure Suit is an integrated suite of automation technologies to codify infrastructure, security, and compliance, as well as…N/A
Spinnaker
Score 7.9 out of 10
N/A
Spinnaker is an open source continuous delivery platform with a range of cluster management and deployment management features, originally developed at Netflix.N/A
Pricing
Progress ChefSpinnaker
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Progress ChefSpinnaker
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Progress ChefSpinnaker
Considered Both Products
Progress Chef

No answer on this topic

Spinnaker
Chose Spinnaker

• Pipeline Expressiveness

• Self-Service/Override

• Visibility of Client Teams

Top Pros
Top Cons
Best Alternatives
Progress ChefSpinnaker
Small Businesses
HashiCorp Terraform
HashiCorp Terraform
Score 8.5 out of 10
GitLab
GitLab
Score 8.9 out of 10
Medium-sized Companies
Ansible
Ansible
Score 8.9 out of 10
AWS CodePipeline
AWS CodePipeline
Score 9.1 out of 10
Enterprises
Ansible
Ansible
Score 8.9 out of 10
AWS CodePipeline
AWS CodePipeline
Score 9.1 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Progress ChefSpinnaker
Likelihood to Recommend
8.7
(18 ratings)
7.0
(3 ratings)
Usability
7.3
(1 ratings)
-
(0 ratings)
Performance
9.4
(5 ratings)
-
(0 ratings)
Support Rating
7.7
(3 ratings)
-
(0 ratings)
Contract Terms and Pricing Model
6.4
(1 ratings)
-
(0 ratings)
Ease of integration
9.6
(5 ratings)
-
(0 ratings)
Professional Services
9.1
(1 ratings)
-
(0 ratings)
User Testimonials
Progress ChefSpinnaker
Likelihood to Recommend
Progress Software Corporation
Chef is a fantastic tool for automating software deployments that aren't able to be containerized. It's more developer-oriented than its other competitors and thus allows you to do more with it. The Chef Infra Server software is rock-solid and has been extremely stable in our experience. I would definitely recommend its use if you're looking for an automation framework. And it also offers InSpec which is a very good tool for testing your infrastructure to ensure it deployed as intended.
Read full review
Netflix
Spinnaker suits well for applications which are stateless and can adapt to an immutable architecture of deployment. But for applications which are stateful and cannot afford to spin up new servers for every deployment doesn't go well with Spinnaker. It can handle only deployments which are VM based and cannot support deployments to serverless architecture like AWS Lambda etc.
Read full review
Pros
Progress Software Corporation
  • Chef is great at deploying code to both small and large groups of servers.
  • We use chef to standup new servers as well as deploy updated code to existing servers and it does this very well.
  • Being able to make a change and have it push manually or automatically to any subset of servers has changed the landscape of how our IT teams operate.
Read full review
Netflix
  • Fast deployments.
  • Can be integrated with a good variety of other products.
  • Also provides some insights from your environment.
Read full review
Cons
Progress Software Corporation
  • Chef could do a better job with integration with other DevOps tools. Our company relies on Jenkins and Ansible, which took some development and convincing for plug-ins to be created/available.
  • It would be nice if kitchen didn't only have a vagrant/virtual-box prerequisite. Our company one day stop allowing virtual-box to run without special privileges, and that caused a lot of issues for people trying to do kitchen tests.
  • Chef could use more practice materials for the advanced certification badges. There was not a lot of guidance in what to study or examples of certain topics.
Read full review
Netflix
  • It does NOT support CFN based deployments
  • Windows based systems finds it difficult to onboard to Spinnaker.
  • Pipeline level access authorisation is not there.
  • Support for EBS volume encryption is probably missing.
  • Attach/detach EBS volumes during deployments is difficult.
  • No support to deploy the artifacts without re-creating the servers. Only pure immutable deployment are allowed.
  • Open-source - so good and bad!
  • Spinnaker on its own has 10 underlying micro services. Managing Spinnaker needs a focussed platform approach.
  • User authentication is easy but authorisation management is not straight forward.
Read full review
Usability
Progress Software Corporation
The suite of tools is very powerful. The ability to create custom modules allows for unlimited potential for managing all aspects of a system. However, there is pretty significant learning curve with the toolset. It currently takes approx 3-4 months for new engineers to feel comfortable with our implementation
Read full review
Netflix
No answers on this topic
Performance
Progress Software Corporation
It loads quick enough for basically all our systems. Because we have this for local dev environments, speed isn't really a big issue here. Yes, depending on the system, sometimes it does take a relatively long time, but it's not an issue for me. One thing that is annoying is that if I want to make a small change to a cookbook and re-run the Chef client, I can't just make the change in the cache and run it. I have to do the whole process of updating the server.
Read full review
Netflix
No answers on this topic
Support Rating
Progress Software Corporation
Support for Chef is easily available for fee or through the open source community as most the issues you will face will have been addressed through the Chef developer community forums. The documentation for Chef is moderate to great and easily readable.
Read full review
Netflix
No answers on this topic
Alternatives Considered
Progress Software Corporation
We considered the three leading competitors in the field: Chef, Puppet and Ansible. Ansible is a very strong competitor and has a nice degree of flexibility in that it does not require a client install. Instead the configuration is delivered by SSH which is very simple. Puppet seems like it has fallen off the pace of the competition and lacked the strong community offered by Chef. We chose Chef because of the strong support by the company and the dynamic and deep community support.
Read full review
Netflix
• Pipeline Expressiveness • Self-Service/Override • Visibility of Client Teams • Operability of Client Teams - • High-Quality Integrations (AWS, IHP, Google) • Extensibility – (Ability to add code) • The maturity of Deployment Process • Speed/Ease of Onboarding
Read full review
Contract Terms and Pricing Model
Progress Software Corporation
The pricing seemed inline with our products in this space. Nothing out of the ordinary in contract, term, or pricing structure
Read full review
Netflix
No answers on this topic
Professional Services
Progress Software Corporation
The entire professional services team was great to work with. The curriculum was tailored to our specific use cases. The group we worked with were very responsive, listened to our feedback, was very easy to schedule and accommodate. I cannot say enough good things about our professional services experience
Read full review
Netflix
No answers on this topic
Return on Investment
Progress Software Corporation
  • Chef is a good tool for baselining servers. It will be a good ROI when there are huge number of servers. For less number of servers maintaining a master will be an over head.
  • One good ROI will be that the Operations Team also gets into agile and DevOps methodologies. Operational teams can start writing scripts/automations to keep their infra more stable and their application stack more reliable.
  • Implementation of Chef eliminates the manual mode of doing things and everyone aligns to automation mind set. It helps in change of culture.
Read full review
Netflix
  • By using Spinnaker we are able to deploy new versions of our product quickly.
  • A deployment takes in average 2 minutes.
  • Our investment on Spinnaker was just time learning it.
Read full review
ScreenShots