Automic Release Automation Wins Best DevOps Commercial Solution DevOps Dozen Award
February 02, 2017

Automic Software has been recognized by the DevOps Dozen 2016 awards as a winner in the “Best DevOps Commercial Solution” category, beating out Electric Cloud, Puppet, and IBM Bluemix DevOps Services, among others.

The DevOps Dozen highlights the top movers and shakers in the rapidly growing DevOps space, with final winners selected by a community vote.

“Automic is thrilled to be a winner of the DevOps Dozen,” said Chris Boorman, CMO of Automic. “This accolade is a testament to our success in arming customers with the best automation tools for DevOps and providing organizations with the agility and speed they need in an era of Digital Transformation. We are delighted to have been selected by voters as their favorite DevOps commercial solution.”

Organized by DevOps.com, the award recognizes companies, products, and services across 12 categories. Final winners are selected by voters and are considered the best of the best within the DevOps movement.

“The DevOps Dozen awards really accelerated this year due to the tremendous competition among so many worthy finalists. The Best Commercial DevOps Solution was perhaps the most competitive category of the 12 offered,” said Alan Shimel, Editor-in-Chief, DevOps.com. “The fact that Automic was the choice of our voters is a testament to the great job they have done, not only building a great product but also building a great community.”

The Latest

September 18, 2017

Web development and web design are intertwined in such a way that there is not one without the other — not anymore at least. The following outlines 5 benefits of collaboration ...

September 14, 2017

Mastering modern software development by building a "Modern Software Factory" is at the heart of business success in the digital economy, according to the results of a survey of over 1,200 IT leaders released today by CA Technologies ...

September 13, 2017

IT-Business convergence is needed to deliver continuous change, but many of the current tools add complexity and fail to merge the two, according to the Panaya 2017 State of Functional Testing Report ...

September 11, 2017

Application Program Interfaces (API’s) represent an effective way to build and manage mobile services. By using APIs — a set of routines, protocols and tools for building software applications — application developers no longer have to buy technology software or hardware. Instead, they can simply plug into a growing open ecosystem of API-driven services. It is simple to integrate, and saves time and money for new developers ...

September 07, 2017

More than a quarter of enterprises globally have not built, customized or virtualized any mobile apps in the last 12 months, according to the latest mobile app survey by Gartner ...

September 06, 2017

The number of malware breaches (to use a generic term) are rising in near exponential numbers and, unless there are radical changes, this is set to continue unabated. Most pundits agree with this forecast ...

September 01, 2017

DevOps encourages communication and collaboration between development and operations teams. Achieving greater synergies between the Dev and Ops teams doesn't happen overnight, but it is possible to fast track the process with the right technologies in place. One such technology is IT automation ...

August 29, 2017

Newly released data shows that distributed denial of service (DDoS) and web application attacks are on the rise once again, according to the Second Quarter, 2017 State of the Internet / Security Report released by Akamai Technologies ...

August 28, 2017

Organizations that are actively managing the quality of open source components flowing into production applications are realizing a 28 percent improvement in developer productivity, a 30 percent reduction in overall development costs, and a 48 percent increase in application quality, according to the 2017 State of the Software Supply Chain Report from Sonatype ...

August 24, 2017

Being able to deploy distinct code elements quickly, matched with the ability to deploy the next release version or the previous version, facilitates moving forward, even on failure. The small program unit minimizes the production impact upon failure — maybe only a few people experience the problem instead of a large set of application users when large code deployments go wrong. Besides implementing small code segments, there are two additional reasons why fail forward has proven successful: continuous integration and testing ...

Share this