


Chef and CloudBees compete in the automation and CI/CD space. CloudBees seems to have an upper hand with its enterprise-level CI/CD functionalities and support capabilities.
Features: Chef offers robust configuration management, provisioning, and automation capabilities alongside integration with third-party tools via Ohai. It supports infrastructure as code, facilitating streamlined operations. CloudBees provides scalability, advanced pipeline management, and strong security features. It integrates extensively with various tools and supports complex workflows efficiently.
Room for Improvement: Chef can improve its ease of use and integration, along with enhancing reporting and analytics capabilities. It also needs better container support. CloudBees faces challenges with plugin performance and occasional downtimes. It could benefit from a more intuitive user interface and enhanced third-party integration.
Ease of Deployment and Customer Service: Chef supports on-premises and cloud environments, relying on community and partner assistance. CloudBees also supports diverse deployment options but offers more robust enterprise support, albeit with some vendor dependency.
Pricing and ROI: Chef’s node-based pricing model can be complex, but it delivers considerable ROI by reducing administrative tasks. Although CloudBees is relatively expensive, its scalability and features justify the cost by boosting delivery efficiency and supporting enterprise environments effectively.
Everything we've gained from it makes my job easier day after day, and I see value in it as an engineer.
Microsoft Intune not only saves costs by reducing the number of personnel needed but also offers a comprehensive solution for managing laptops, applications, security, individual access, and enrollment.
With Microsoft Intune, tasks such as device provisioning, policy deployment, application delivery, and compliance enforcement require less manual effort than in more traditional management models.
The return has been far more hours saved than spent.
We have seen significant improvement in the time and the way we make changes to the infrastructure.
I have seen a return on investment with Chef because we definitely need fewer employees to manage infrastructure.
When a support ticket is submitted, it directly reaches someone with Intune support expertise.
When I contacted Microsoft, they had the same expertise, if not more, which is phenomenal because I felt heard and my problem was solved.
Sometimes, the support provided is excellent, and the representative is knowledgeable, while other times, the service needs improvement.
We usually work with the Chef teams and community support, who are always willing to assist.
The scalability of Microsoft Intune is ten out of ten.
Ideally, we want to automatically segregate devices based on user properties like primary use, but currently, dynamic groups seem limited to device properties.
It supports organizations with 200 endpoints and those with more than 15,000 endpoints.
We leverage both to achieve the best option possible for scaling.
Chef's scalability is evident as the public sector organization I work at serves a population of 5 million, and we have had no problems with scaling.
We have not experienced downtime, bugs, or glitches.
It appears Microsoft Intune undergoes changes without informing customers.
In my experience, Microsoft Intune is a stable platform as it is a cloud-based service, and updates are regularly delivered by Microsoft.
It is a good tool to work with, offering a strong developer experience and community support.
Chef is stable.
In my experience, Chef is quite stable most of the time.
The deployment can take a couple of hours or a couple of minutes.
Features like unlocking devices sometimes fail, and the support offered for other operating systems is insufficient.
There are communication issues, so you might start working with a feature without knowing if it will be deprecated six months from now.
Many third-party companies offer single-pane-of-glass reporting that shows you what your update environment looks like, how your patch is doing, application status, etc., but Intune's reporting is not intuitive.
On support, I think there should be more focus on how we can achieve AI automations in answering questions for beginners and addressing deep concerns without general manual management.
To improve Chef, making an interface with another language such as Python or Java that is well understood, as capable as Ruby, and even more widely adopted would demystify it a bit.
The learning curve is steep due to Chef's Ruby-based DSL and the complex components of cookbooks and recipes, which can be challenging for new users, especially those without programming backgrounds.
If possible, we could sort the logs so we can get the exact error on one page.
Introductory professional services, like a fast-track service, were included with our E5 membership, and there have been no additional costs.
The Intune suite and add-ons, such as batch management and remote help, are costly.
It costs approximately forty euros per user per month.
Licensing looks reasonable compared to the manual work of managing whole data centers with even 10,000 servers.
My experience with pricing, setup cost, and licensing is that we sidestepped it by using Cinc because none of the functionality that is exclusive to the paid version was actually in use in the organization.
Intune excels in configuration and compliance management for Windows 10, ensuring devices receive timely updates and adhere to organizational standards.
Dynamic groups allow us to set conditions for automatic membership, eliminating the need for user intervention or manual review and ensuring a seamless workflow.
Windows Autopatch is the most valuable because it removes the burden of patch management.
Security is a key aspect that Chef can automate, monitor new features that are available, and even do patches without you getting involved.
When you have infrastructure as code and you already have everything apart from the environment-specific config, which you can specify in variables, then it is not only more repeatable and reliable, it is faster.
Using Chef for automating infrastructure and applications in my organization has helped us reduce manual tasks by more than forty percent, thereby saving significant revenue for the client.
The integration part is good. We can use multiple things by integrating with CI/CD pipelines, and this is very feasible for us.



| Company Size | Count |
|---|---|
| Small Business | 149 |
| Midsize Enterprise | 60 |
| Large Enterprise | 177 |
| Company Size | Count |
|---|---|
| Small Business | 3 |
| Midsize Enterprise | 7 |
| Large Enterprise | 19 |
| Company Size | Count |
|---|---|
| Small Business | 1 |
| Midsize Enterprise | 3 |
| Large Enterprise | 18 |
Microsoft Intune is a cloud-based service designed for device management, security, and compliance. It supports automation and facilitates endpoint management for Windows, iOS, and Android devices, ensuring data protection and efficient policy enforcement.
Microsoft Intune offers seamless integration with tools like Windows Autopilot to automate device setup and deployment. Integrated with Azure Active Directory, it enhances policy management while providing robust reporting and analytics tools for compliance tracking. Despite its intuitive interface aimed at simplifying navigation and device security management, there are challenges such as compatibility issues with Linux and Mac, limited policy support for Android, and demands for better third-party integration. It's widely used for both corporate-owned devices and BYOD scenarios in dynamic IT environments.
What are the key features of Microsoft Intune?In industries such as finance and healthcare, Microsoft Intune is implemented to ensure data protection and compliance with regulatory standards. Manufacturing sectors utilize Intune for managing a distributed workforce across global locations, while educational institutions employ it to secure and manage devices in learning environments supporting both students and faculty.
Chef is a powerful automation tool designed for efficient infrastructure management across varied environments. With its environment-as-code model, Chef provides predictability and reliability in deployments, enhancing security compliance and reducing manual intervention.
Chef focuses on automating deployments and configurations, ensuring server consistency, managing scalable environments, and orchestrating service deployments. Its versatile recipe-writing and Ruby-based flexibility cater to large-scale operational needs. Chef’s integration with services like AWS and Azure enhances its versatility, while its idempotent deployments assure reliability. Despite its prowess, Chef requires improvements in feature offerings, especially regarding container orchestration and cloud technologies.
What are Chef's Key Features?Chef is implemented across industries to automate application deployments, manage CI/CD pipelines, provision infrastructure, and maintain compliance. Its recipes and cookbooks streamline workflows in application deployment, system updates, and orchestration of services, reducing errors and manual intervention in a variety of sectors.
CloudBees provides a highly scalable and secure platform that supports seamless integration and automation across multiple environments. It excels in managing Jenkins instances and offers flexible deployment options, enhancing efficiency for large teams.
CloudBees is recognized for its integration with Jenkins, SonarQube, and Ansible, allowing companies to leverage its robust automation capabilities for continuous integration and deployment. With its strong support for Docker and Kubernetes, teams benefit from streamlined code management and operational efficiency. Its scalable architecture, real-time feedback, and premium vendor support help manage large-scale applications and microservices. Despite its strengths, users report challenges with pipeline setup, service availability, and GUI accessibility, which suggest room for improvement in these areas.
What are the key features of CloudBees?
What benefits should users expect in reviews?
In tech and software industries, companies implement CloudBees for managing complex CI/CD pipelines. Its integration with DevOps tools facilitates automation and workflow optimization. Industries with large teams managing thousands of microservices use CloudBees to maintain high availability, streamline processes, and ensure security compliance, driving efficient production workflows.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.