Try our new research platform with insights from 80,000+ expert users
Automic Continuous Delivery Director [EOL] Logo

Automic Continuous Delivery Director [EOL] Reviews

Vendor: Broadcom
4.0 out of 5

What is Automic Continuous Delivery Director [EOL]?

Featured Automic Continuous Delivery Director [EOL] reviews

 
 
Key learnings from peers
Last updated Mar 26, 2026

Valuable Features

Room for Improvement

Pricing

 
Automic Continuous Delivery Director [EOL] Reviews Summary
Author infoRatingReview Summary
Group CEO at Flexsolutions3.0I have utilized Automic Continuous Delivery Director to automate our entire release process, integrating seamlessly with various tools and systems. Its scalability and extensive connectors are invaluable, though its development has paused, focusing only on maintaining the current product.
Senior Presales Engineer at a computer software company with 51-200 employees4.5I use Automic Continuous Delivery Director to orchestrate and release pipelines. Its UI, release planning, and tracking features are valuable, especially for managing freezes. However, it could improve by offering more integrations beyond the current 25 available.
DevOps Architect at a tech services company with 51-200 employees4.5I value CDD for its stable, easy pipeline design, fostering team autonomy and external integration. I'd like better Agile Central integration and improved UI for scale, plus integrated testing. The main challenge is the cultural shift, not the tool itself.
ALM DevOps Senior Consultant at a tech services company with 51-200 employees4.0I use this solution for business application delivery, empowering Agile/DevOps teams through coordinated software delivery. While stable and scalable, I find reporting, pipeline templates, and large pipeline navigation need improvement.
Principal Engineer - IT Quality and Release at a transportation company with 10,001+ employees4.0I value its deployment automation, visibility, and rollback clarity. However, it's frustrating that CDD and CA Release Automation aren't integrated, requiring separate strategies despite their complementary roles. Firewall issues hinder my implementation.