What do you like best about the product?

The best part of using Progress Chef is that it doesn't depend on a single cloud infrastructure. We offer SaaS as well as Product as a Service. Given this, we provide infrastructure code and Docker images for applications to our customers. Therefore, we required a service that can manage both infrastructure code and application deployment, including the pipeline for future releases. In these terms, Progress Chef is the go-to solution for us, whether our customer is in AWS, Azure, or GCP.

What do you dislike about the product?

I would like it even more if I can get a managed service for using Progress Chef. The Infrastructure requirement for Progress Chef is a bit complex.

What problems is the product solving and how is that benefiting you?

The problems that are solved by Progress Chef are as follows:
1. It doesn't depend on cloud infrastructure. It can be used for AWS, Azure, GCP or On-Prem deployment as well.
2. Single software can be used for configuration management, CI/CD, IaC.
3. To deploy an entire application with infrastructure in a customer environment irrespective of the cloud provider they use, Progress Chef is the best solution available in the market.