Broadcom Nolio Release Automation

Name: Broadcom Nolio Release Automation
Brand: Broadcom
Rating: 4.2 (3 reviews)

Leader

Broadcom provides semiconductors and infrastructure software for global organizations’ complex, mission-critical needs

Est 1961|Valuation $1764B

LinkedIn 446K|Website|Web traffic 4.0M|FTEs 33,000|HQ Palo Alto, California, US

MarketsBusiness Process Management (BPM)Source Code Management (SCM)Continuous Integration & Continuous Delivery (CI/CD)

Broadcom Nolio Release Automation screenshot

Published Oct 9, 2026

01Common complaints

- Organizations that are primarily Kubernetes-native and GitOps-first may prefer Argo CD or Flux-style approaches instead of a model-driven enterprise release tool. - Teams seeking a quick, developer-led CI/CD setup may find platforms such as GitHub Actions or GitLab CI provide faster time-to-first-deploy with lower platform overhead. - Organizations that strongly prefer agentless automation may prefer Ansible to reduce operational burden compared with agent-based deployment tooling. - Organizations that require transparent, self-serve pricing and rapid procurement cycles may find the enterprise quoting model slows evaluation. - Environments with simple deployment needs may be better served by lighter-weight tools such as Octopus Deploy or simple scripted pipeline approaches.

Deal disqualifiers / poor fit

Small teams seeking lightweight CI/CD with minimal operational overhead.
Kubernetes-first organizations aiming for pure GitOps with minimal centralized tooling.
Organizations that are unwilling to invest in upfront modeling and implementation effort.

Vendor-acknowledged changes that can affect operations

Nexus repository bundling change: Broadcom knowledge base indicates that starting with Nolio Release Automation 6.9, Nexus repository is no longer bundled with the installer; fresh installs require a standalone Nexus 3. Previously bundled repositories remain supported but may not be updated. This change can add operational steps during upgrades or new installs.

Release/support lifecycle signals

Broadcom announced end-of-technical-support milestones for older releases: Nolio Release Automation 6.6 (end of technical support effective September 5, 2022) and 6.7 (end of technical support effective June 15, 2024).

Current release/patch signals

- Broadcom community communications (February 11, 2026) announced General Availability of Nolio Release Automation Patch 6.9.3, with vendor-stated improvements such as infrastructure stability improvements, faster user experience on design pages, restored compatibility with Nexus 3, multiple LDAP server support, and security library upgrades. These items are vendor claims and should be validated in target environments; confirm full release notes and compatibility statements with Broadcom.

Common limitations mentioned by users

UI complexity and perceived lag.
Documentation and onboarding gaps reported by some users.
Requests for improved integrations and enhanced Kubernetes/cloud support.

02Why they buy

Strengths observed in user feedback

Process and flow design capability: reviewers frequently noted the visual designer and workflow modeling as a core capability compared with some alternatives.
Deployment templates and parameterization: users described the ability to create templates that accept runtime parameters from CI servers such as Jenkins or TeamCity.
Reusable components and shared deployment building blocks that support standardization across teams.

Differentiation relative to alternatives

Emphasis on application and environment modeling combined with governance-oriented orchestration distinguishes the product from simpler pipeline or infrastructure automation tools.
Integration with Broadcom’s broader DevOps portfolio and related plugin ecosystem is relevant for organizations invested in that vendor stack.

Areas where competitors have clear advantages

Kubernetes- and GitOps-centric delivery approaches (Argo CD/Flux).
Unified DevSecOps workflow platforms that tightly integrate SCM, CI, and CD (GitLab/GitHub Actions).
Large community ecosystems and rapid module development (Ansible, Jenkins).

03Field reports

Review platform coverage caveat

- G2: the product has a limited number of reviews on G2 and the platform notes there are not enough reviews to provide broad buying insight. - Gartner Peer Insights: this research did not retrieve accessible Gartner Peer Insights review pages for Nolio Release Automation (results may be blocked or inaccessible in some tooling). - PeerSpot: PeerSpot contains a larger volume of reviews (for example, listings referencing multiple reviews); PeerSpot’s methodology is different from analyst firms and should be treated as directional data.

Positive review highlights (examples)

- G2 reviews praised scheduled and manual triggers, deployment templates with runtime parameters passed from Jenkins/TeamCity, reusable shared components, and email triggers for pre/post deployment steps (excerpts from older and more recent reviews were present in the sources reviewed). - One reviewer indicated that the product’s process/flow designer compared favorably to alternatives, while also noting occasional UI lag. - PeerSpot excerpts cited scaling to many applications and agents (older excerpts referenced supporting a very large deployment footprint, with performance considerations noted).

Negative review highlights / complaints (examples)

- Reviewers requested more standard components for specific deployment types (for example, integrations for particular enterprise tools like Informatica). - PeerSpot and G2 excerpts indicated UI complexity, insufficient error messaging, documentation and training gaps, and integration gaps (requests for improved Jenkins/Docker/Kubernetes integrations and additional plug-ins). - Stability and performance concerns were noted, particularly for older releases at very large scale.

Reasons customers selected the product (compiled from reviews and positioning)

Deployment modeling and orchestration capabilities.
Centralized release control with governance features (scheduling, approvals, and audit trails).
Reusable templates and components for enterprise standardization.

Reasons customers left / churn factors (inferred)

Direct churn narratives were limited; inferred churn drivers from complaints include:

UI and usability friction and associated learning curve.
Need for more modern integrations for cloud-native and Kubernetes workflows.
Upgrade and performance issues on older versions.
Consolidation of toolchains toward platforms that combine CI, artifacts, and deployments.

Example case study: Swisscom (referenced in case study directory)

A vendor case study directory lists a use case titled: "Swisscom Deliver Innovative, Cloud-based, Digital TV Services with Nolio Release Automation" with a named role (IPTV Core Team Lead). Critical evaluation and limitations: - The directory listing alone does not provide detailed metrics, methodology, or a complete narrative in the accessible snippet. - Vendor case studies are typically curated by the vendor; for evaluative purposes, request baseline and post-implementation metrics, time periods used, and whether independent validation exists.

What to request from Broadcom for case-study-grade validation

Request the following data when seeking independently verifiable case study evidence:

Deployment frequency before and after implementation.
Change failure rate and mean time to recovery (MTTR) impact.
Number of applications and environments modeled.
Details of rollout governance controls (approval steps, segregation of duties).

04Best fit

Company size

Most aligned with:

Large enterprises or complex organizations managing a large application portfolio.
Organizations with mature release governance requirements (approvals, audit trails, segregation of duties).

Industries

Telecom and large IT service providers.
Financial services and other regulated sectors.
Large enterprises operating hybrid environments (legacy systems and modern platforms).

Roles and personas

Release engineering and DevOps/platform engineering leaders.
Platform operations teams responsible for deployment processes.
Risk, compliance, and audit stakeholders.

Fit criteria

Requirement to standardize deployments across many heterogeneous applications.
Need for repeatable, parameterized release processes with approval controls.
Desire for a centralized release control point to replace dispersed scripts and processes.

05The pitch

What the product does (objective core value proposition)

Broadcom Nolio Release Automation (historically CA Release Automation or Nolio) is an enterprise release/deployment automation and orchestration product intended to standardize and automate application deployments across environments (dev/test/stage/prod). The product uses model-driven deployments (application/environment/process models) and a visual workflow/process designer, and provides scheduling, auditability, and governance features for complex, regulated enterprise release processes. The official product brief describes orchestration across the software development lifecycle (SDLC), centralized release control, dashboards, and a range of integrations. Primary use case category: Application Release Orchestration / Release Automation for enterprises with many applications/environments and a need for repeatable, governed deployments.

Target market and positioning

Target buyer: large enterprises and regulated organizations (financial services, telecom, government, large IT organizations) where release governance, repeatability, and auditability are principal requirements.
Positioning relative to modern CI/CD: Nolio generally operates downstream of CI tools (e.g., Jenkins/TeamCity) to orchestrate controlled deployments rather than replacing build pipelines.

Get a comprehensive analysis of Broadcom Nolio Release Automation including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 9, 2026

01Common complaints

Organizations that are primarily Kubernetes-native and GitOps-first may prefer Argo CD or Flux-style approaches instead of a model-driven enterprise release tool.
Teams seeking a quick, developer-led CI/CD setup may find platforms such as GitHub Actions or GitLab CI provide faster time-to-first-deploy with lower platform overhead.
Organizations that strongly prefer agentless automation may prefer Ansible to reduce operational burden compared with agent-based deployment tooling.
Organizations that require transparent, self-serve pricing and rapid procurement cycles may find the enterprise quoting model slows evaluation.
Environments with simple deployment needs may be better served by lighter-weight tools such as Octopus Deploy or simple scripted pipeline approaches.

Deal disqualifiers / poor fit

Small teams seeking lightweight CI/CD with minimal operational overhead.
Kubernetes-first organizations aiming for pure GitOps with minimal centralized tooling.
Organizations that are unwilling to invest in upfront modeling and implementation effort.

Vendor-acknowledged changes that can affect operations

Nexus repository bundling change: Broadcom knowledge base indicates that starting with Nolio Release Automation 6.9, Nexus repository is no longer bundled with the installer; fresh installs require a standalone Nexus 3. Previously bundled repositories remain supported but may not be updated. This change can add operational steps during upgrades or new installs.

Release/support lifecycle signals

Broadcom announced end-of-technical-support milestones for older releases: Nolio Release Automation 6.6 (end of technical support effective September 5, 2022) and 6.7 (end of technical support effective June 15, 2024).

Current release/patch signals

Broadcom community communications (February 11, 2026) announced General Availability of Nolio Release Automation Patch 6.9.3, with vendor-stated improvements such as infrastructure stability improvements, faster user experience on design pages, restored compatibility with Nexus 3, multiple LDAP server support, and security library upgrades. These items are vendor claims and should be validated in target environments; confirm full release notes and compatibility statements with Broadcom.

Common limitations mentioned by users

UI complexity and perceived lag.
Documentation and onboarding gaps reported by some users.
Requests for improved integrations and enhanced Kubernetes/cloud support.

02Why they buy

Strengths observed in user feedback

Process and flow design capability: reviewers frequently noted the visual designer and workflow modeling as a core capability compared with some alternatives.
Deployment templates and parameterization: users described the ability to create templates that accept runtime parameters from CI servers such as Jenkins or TeamCity.
Reusable components and shared deployment building blocks that support standardization across teams.

Differentiation relative to alternatives

Emphasis on application and environment modeling combined with governance-oriented orchestration distinguishes the product from simpler pipeline or infrastructure automation tools.
Integration with Broadcom’s broader DevOps portfolio and related plugin ecosystem is relevant for organizations invested in that vendor stack.

Areas where competitors have clear advantages

Kubernetes- and GitOps-centric delivery approaches (Argo CD/Flux).
Unified DevSecOps workflow platforms that tightly integrate SCM, CI, and CD (GitLab/GitHub Actions).
Large community ecosystems and rapid module development (Ansible, Jenkins).

03Field reports

Review platform coverage caveat

G2: the product has a limited number of reviews on G2 and the platform notes there are not enough reviews to provide broad buying insight.
Gartner Peer Insights: this research did not retrieve accessible Gartner Peer Insights review pages for Nolio Release Automation (results may be blocked or inaccessible in some tooling).
PeerSpot: PeerSpot contains a larger volume of reviews (for example, listings referencing multiple reviews); PeerSpot’s methodology is different from analyst firms and should be treated as directional data.

Positive review highlights (examples)

G2 reviews praised scheduled and manual triggers, deployment templates with runtime parameters passed from Jenkins/TeamCity, reusable shared components, and email triggers for pre/post deployment steps (excerpts from older and more recent reviews were present in the sources reviewed).
One reviewer indicated that the product’s process/flow designer compared favorably to alternatives, while also noting occasional UI lag.
PeerSpot excerpts cited scaling to many applications and agents (older excerpts referenced supporting a very large deployment footprint, with performance considerations noted).

Negative review highlights / complaints (examples)

Reviewers requested more standard components for specific deployment types (for example, integrations for particular enterprise tools like Informatica).
PeerSpot and G2 excerpts indicated UI complexity, insufficient error messaging, documentation and training gaps, and integration gaps (requests for improved Jenkins/Docker/Kubernetes integrations and additional plug-ins).
Stability and performance concerns were noted, particularly for older releases at very large scale.

Reasons customers selected the product (compiled from reviews and positioning)

Deployment modeling and orchestration capabilities.
Centralized release control with governance features (scheduling, approvals, and audit trails).
Reusable templates and components for enterprise standardization.

Reasons customers left / churn factors (inferred)

Direct churn narratives were limited; inferred churn drivers from complaints include:

UI and usability friction and associated learning curve.
Need for more modern integrations for cloud-native and Kubernetes workflows.
Upgrade and performance issues on older versions.
Consolidation of toolchains toward platforms that combine CI, artifacts, and deployments.

Example case study: Swisscom (referenced in case study directory)

A vendor case study directory lists a use case titled: "Swisscom Deliver Innovative, Cloud-based, Digital TV Services with Nolio Release Automation" with a named role (IPTV Core Team Lead).

Critical evaluation and limitations:

The directory listing alone does not provide detailed metrics, methodology, or a complete narrative in the accessible snippet.
Vendor case studies are typically curated by the vendor; for evaluative purposes, request baseline and post-implementation metrics, time periods used, and whether independent validation exists.

What to request from Broadcom for case-study-grade validation

Request the following data when seeking independently verifiable case study evidence:

Deployment frequency before and after implementation.
Change failure rate and mean time to recovery (MTTR) impact.
Number of applications and environments modeled.
Details of rollout governance controls (approval steps, segregation of duties).

04Best fit

Company size

Most aligned with:

Large enterprises or complex organizations managing a large application portfolio.
Organizations with mature release governance requirements (approvals, audit trails, segregation of duties).

Industries

Telecom and large IT service providers.
Financial services and other regulated sectors.
Large enterprises operating hybrid environments (legacy systems and modern platforms).

Roles and personas

Release engineering and DevOps/platform engineering leaders.
Platform operations teams responsible for deployment processes.
Risk, compliance, and audit stakeholders.

Fit criteria

Requirement to standardize deployments across many heterogeneous applications.
Need for repeatable, parameterized release processes with approval controls.
Desire for a centralized release control point to replace dispersed scripts and processes.

05The pitch

What the product does (objective core value proposition)

The official product brief describes orchestration across the software development lifecycle (SDLC), centralized release control, dashboards, and a range of integrations.

Primary use case category: Application Release Orchestration / Release Automation for enterprises with many applications/environments and a need for repeatable, governed deployments.

Target market and positioning

Target buyer: large enterprises and regulated organizations (financial services, telecom, government, large IT organizations) where release governance, repeatability, and auditability are principal requirements.
Positioning relative to modern CI/CD: Nolio generally operates downstream of CI tools (e.g., Jenkins/TeamCity) to orchestrate controlled deployments rather than replacing build pipelines.

Get a comprehensive analysis of Broadcom Nolio Release Automation including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →