Broadcom Enterprise Automation

Name: Broadcom Enterprise Automation
Brand: Broadcom
Rating: 4.3 (37 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

MarketsIT Service Desk (ITSM)Business Process Management (BPM)Workflow Automation

Broadcom Enterprise Automation screenshot

Published Oct 9, 2026

01Common complaints

1) You require transparent, self-serve pricing and fast procurement. - Broadcom’s automation products are typically quoted; if rapid, predictable purchasing is a priority, consider vendors with published entry tiers. 2) Your primary use case is modern data pipeline orchestration (Airflow-like) rather than enterprise batch orchestration. - Broadcom’s positioning focuses on enterprise scheduling, governance, and hybrid orchestration rather than developer-focused pipeline ergonomics. 3) Your team lacks dedicated automation engineers or administrators. - Reviews indicate implementation effort and a learning curve; teams without specialist capacity may struggle. 4) Vendor support experience is a primary selection criterion. - Public community discussions describe variability in support experience; include reference checks and contractual service-level terms in procurement. 5) You require publicly posted compliance attestations (SOC 2/ISO) without an NDA. - Product-specific compliance artifacts were not consolidated in public sources; request these during procurement if required by policy.

Deal disqualifiers (poor fit)

Small teams seeking lightweight orchestration with minimal setup
Organizations preferring open-source or developer-first orchestration models
Environments where procurement friction and opaque pricing are unacceptable

Commonly mentioned limitations (from reviews and community input)

Learning curve and implementation workload (AutoSys reviewers).
GUI and UX improvement requests (AutoSys reviewers).
Risk of support and portal friction based on community discussions across Broadcom-acquired products.

Roadmap / future features

Broadcom publishes product update posts and release notes (for example, AAI version announcements). Specific forward-looking dates and commitments should be treated as non-binding unless included contractually.

Scale considerations

No definitive public "break point" specifications were found in the reviewed sources. Peer discussions suggest scale and reliability are areas of emphasis for the product; buyers should request sizing guidance, reference architectures, and customer references for comparable job volumes.

02Why they buy

1) Longstanding enterprise scheduling capabilities and cross-platform support. - AutoSys and Automic have a long history in scheduling for heterogeneous enterprise environments. 2) An analytics layer focused on automation observability and SLA management. - AAI is presented as an analytics component intended to aggregate job telemetry and support SLA management and forecasting across schedulers. 3) Documented integrations and usage in SAP environments. - Broadcom provides materials and integrations aimed at SAP operations and related workflows. Balance note: Competing products also offer SLA management and analytics; buyers should validate specific functional depth, integration ease, and operational requirements through demos and proofs of concept.

Why customers chose Broadcom automation (recurring reasons)

Recurring reasons in case studies and review excerpts include:

Dependency modeling and job monitoring for large estates.
Mature scheduling capability for legacy and hybrid environments.
SLA management and end-to-end visibility when paired with AAI.
Documented usage in SAP environments.

2) An analytics layer focused on automation observability and SLA management.

Key Differentiator

03Field reports

Review platforms (G2, TrustRadius, PeerSpot, Gartner Peer Insights)

#### G2 — AutoSys Workload Automation (examples) Positive themes noted in G2 excerpts: - Easy job monitoring - Clear job dependency information - Descriptive logs that aid troubleshooting Critical themes noted in G2 excerpts: - Implementation and learning: reviewers report that implementation can require significant effort and that the product has a non-trivial learning curve. - UI/UX: reviewers request GUI improvements and better session handling. - Session/UX annoyances: some reviewers describe session logout behavior that affects workflows. These quotes were extracted from visible portions of G2 product reviews and are representative rather than exhaustive. #### TrustRadius — AutoSys Workload Automation TrustRadius hosts a product review page for AutoSys Workload Automation. Detailed quotes were not fully accessible from snippets captured during this research session; consult TrustRadius directly for full verbatim feedback and segmentation by industry and role. #### PeerSpot — AutoSys and Automic PeerSpot contains review listings for both AutoSys Workload Automation and Automic Automation. PeerSpot content includes comparisons of reliability and scaling behavior versus alternative products. Buyers should treat these inputs as directional and validate claims with technical references and reference checks. #### Gartner Peer Insights — Automic Automation Gartner Peer Insights hosts reviews for Automic Automation. Full review text and detailed breakdowns may require authenticated access. Organizations with Gartner access should extract common strengths and weaknesses, including support experience and upgrade/stability commentary.

Community / social proof (Reddit, broader sentiment)

Community discussions often focus on Broadcom’s software support and licensing behavior; these discussions influence buyer risk perception for Broadcom enterprise software purchases. Common community themes: - Negative comments about Broadcom’s support portal and support experience. - Frustration with licensing and pricing processes in vendors acquired by Broadcom (examples in VMware-related threads). Counterpoint: community sentiment is mixed; at least one discussion reported a positive Broadcom support experience, indicating variability by account tier, entitlement, and support routing.

Why some customers leave / churn risk indicators

Direct churn anecdotes for Automic/AutoSys were not prominent in the sources captured. Relevant risk signals include:

Poor procurement or support experience, which can prompt customers to evaluate alternatives at renewal time.
Organizations seeking developer-first orchestration (CI/CD-native or data engineering-focused tools) may prefer alternatives such as Airflow, Prefect, or Dagster when enterprise governance is not a priority.

Broadcom-published case study: Large regional bank increasing Automic usage

Broadcom’s customer story describes a regional bank expanding Automic usage over multiple years and includes positive comments about enablement practices. What’s useful: - Illustrates that the product can expand footprint in regulated environments. - Describes operational enablement practices such as internal training. Critical gaps: - Metrics presented in vendor case studies are often qualitative; where quantitative claims exist, they are vendor-published and not independently audited. - Some vendor case study excerpts omit customer identifiers, limiting reference validation.

Vendor / sponsored whitepapers and eBooks

Broadcom publishes eBooks and whitepapers describing Automic and AAI value propositions.

Critical gaps:

These materials are marketing collateral; ROI methodologies may not be fully transparent.
They can be useful for framing vendor value propositions but should not replace independent references or POCs.

04Best fit

Company size

Generally suited to large enterprises; may also fit larger mid-market customers with complex, regulated operations, though total cost of ownership and operational overhead should be evaluated.

Industries

Financial services and banking
Insurance
Retail (batch processing such as replenishment)
Manufacturing and supply chain
Utilities and telecommunications
Any enterprise running SAP alongside heterogeneous workloads

Roles and personas

Decision makers:

VP/Director of IT Operations
Head of Infrastructure / Platform Engineering
Enterprise Architect (integration and governance)
CIO / CTO (for transformation and risk oversight)

End users:

Workload automation administrators
NOC / operations engineers
Application support teams
Release and change management teams

Pain points addressed

Fragmented schedulers and siloed automation tools
SLA misses due to limited end-to-end visibility
Manual interventions for job failures
Governance and audit requirements

Qualification criteria (good fit)

Need for cross-platform enterprise scheduling (not only data engineering pipelines)
High job volumes and complex dependencies
Requirement for SLA management, audit trails, and operational control

05The pitch

What the product does (objective value proposition)

Broadcom "Enterprise Automation" (often branded as Automation by Broadcom) is a portfolio of enterprise-focused automation products for workload automation/job scheduling, cross-application orchestration, and automation analytics/observability across hybrid environments (on-premises and multi-cloud). The portfolio includes Broadcom’s long-standing scheduler products (for example, AutoSys), expanded orchestration offerings (for example, Automic Automation and Automic SaaS), and an analytics layer (Automation Analytics & Intelligence, AAI) intended to provide SLA management, forecasting, and end-to-end automation visibility. Key portfolio elements frequently referenced by Broadcom include: - Automic Automation (and Automic SaaS) for workload automation and orchestration across heterogeneous environments, with multiple integrations and marketplace add-ons. - AutoSys Workload Automation for centralized job scheduling and monitoring across platforms. - Automation Analytics & Intelligence (AAI) as an analytics/observability layer for automation that integrates with multiple schedulers. Broadcom describes the portfolio as an enterprise control plane for scheduling and orchestration rather than a developer-first data pipeline orchestrator (for example, Airflow). The materials emphasize visibility, governance, SLA management, and integrations spanning ERP/SAP, cloud services, and legacy infrastructure. Evidence (official/analyst): Automic SaaS positioning and cloud marketplace presence; AAI described as analytics/observability for workload automation; Automic positioning for SAP environments.

Target market and market positioning

Suitable segments (inferred from product messaging and third-party reviews): - Large enterprises (commonly organizations with thousands of employees) running high-volume, business-critical batch workloads across mixed platforms (Windows/Linux/Unix, mainframe-adjacent ecosystems, ERP/SAP, and cloud services). - Industries where SLA adherence and auditability matter: finance, insurance, retail, manufacturing, utilities, and regulated sectors. Broadcom positions these tools as: - Oriented toward governance and SLA management rather than lightweight schedulers. - Framed as an enterprise control plane rather than a cloud-native single-purpose scheduler.

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

Download full report →

Published Oct 9, 2026

01Common complaints

You require transparent, self-serve pricing and fast procurement.
- Broadcom’s automation products are typically quoted; if rapid, predictable purchasing is a priority, consider vendors with published entry tiers.
Your primary use case is modern data pipeline orchestration (Airflow-like) rather than enterprise batch orchestration.
- Broadcom’s positioning focuses on enterprise scheduling, governance, and hybrid orchestration rather than developer-focused pipeline ergonomics.
Your team lacks dedicated automation engineers or administrators.
- Reviews indicate implementation effort and a learning curve; teams without specialist capacity may struggle.
Vendor support experience is a primary selection criterion.
- Public community discussions describe variability in support experience; include reference checks and contractual service-level terms in procurement.
You require publicly posted compliance attestations (SOC 2/ISO) without an NDA.
- Product-specific compliance artifacts were not consolidated in public sources; request these during procurement if required by policy.

Deal disqualifiers (poor fit)

Small teams seeking lightweight orchestration with minimal setup
Organizations preferring open-source or developer-first orchestration models
Environments where procurement friction and opaque pricing are unacceptable

Commonly mentioned limitations (from reviews and community input)

Learning curve and implementation workload (AutoSys reviewers).
GUI and UX improvement requests (AutoSys reviewers).
Risk of support and portal friction based on community discussions across Broadcom-acquired products.

Roadmap / future features

Scale considerations

02Why they buy

Longstanding enterprise scheduling capabilities and cross-platform support.
- AutoSys and Automic have a long history in scheduling for heterogeneous enterprise environments.
An analytics layer focused on automation observability and SLA management.
- AAI is presented as an analytics component intended to aggregate job telemetry and support SLA management and forecasting across schedulers.
Documented integrations and usage in SAP environments.
- Broadcom provides materials and integrations aimed at SAP operations and related workflows.

Balance note: Competing products also offer SLA management and analytics; buyers should validate specific functional depth, integration ease, and operational requirements through demos and proofs of concept.

Why customers chose Broadcom automation (recurring reasons)

Recurring reasons in case studies and review excerpts include:

Dependency modeling and job monitoring for large estates.
Mature scheduling capability for legacy and hybrid environments.
SLA management and end-to-end visibility when paired with AAI.
Documented usage in SAP environments.

2) An analytics layer focused on automation observability and SLA management.

Key Differentiator

03Field reports

Review platforms (G2, TrustRadius, PeerSpot, Gartner Peer Insights)

G2 — AutoSys Workload Automation (examples)

Positive themes noted in G2 excerpts:

Easy job monitoring
Clear job dependency information
Descriptive logs that aid troubleshooting

Critical themes noted in G2 excerpts:

Implementation and learning: reviewers report that implementation can require significant effort and that the product has a non-trivial learning curve.
UI/UX: reviewers request GUI improvements and better session handling.
Session/UX annoyances: some reviewers describe session logout behavior that affects workflows.

These quotes were extracted from visible portions of G2 product reviews and are representative rather than exhaustive.

TrustRadius — AutoSys Workload Automation

TrustRadius hosts a product review page for AutoSys Workload Automation. Detailed quotes were not fully accessible from snippets captured during this research session; consult TrustRadius directly for full verbatim feedback and segmentation by industry and role.

PeerSpot — AutoSys and Automic

PeerSpot contains review listings for both AutoSys Workload Automation and Automic Automation. PeerSpot content includes comparisons of reliability and scaling behavior versus alternative products. Buyers should treat these inputs as directional and validate claims with technical references and reference checks.

Gartner Peer Insights — Automic Automation

Gartner Peer Insights hosts reviews for Automic Automation. Full review text and detailed breakdowns may require authenticated access. Organizations with Gartner access should extract common strengths and weaknesses, including support experience and upgrade/stability commentary.

Community / social proof (Reddit, broader sentiment)

Community discussions often focus on Broadcom’s software support and licensing behavior; these discussions influence buyer risk perception for Broadcom enterprise software purchases.

Common community themes:

Negative comments about Broadcom’s support portal and support experience.
Frustration with licensing and pricing processes in vendors acquired by Broadcom (examples in VMware-related threads).

Counterpoint: community sentiment is mixed; at least one discussion reported a positive Broadcom support experience, indicating variability by account tier, entitlement, and support routing.

Why some customers leave / churn risk indicators

Direct churn anecdotes for Automic/AutoSys were not prominent in the sources captured. Relevant risk signals include:

Poor procurement or support experience, which can prompt customers to evaluate alternatives at renewal time.
Organizations seeking developer-first orchestration (CI/CD-native or data engineering-focused tools) may prefer alternatives such as Airflow, Prefect, or Dagster when enterprise governance is not a priority.

Broadcom-published case study: Large regional bank increasing Automic usage

Broadcom’s customer story describes a regional bank expanding Automic usage over multiple years and includes positive comments about enablement practices.

What’s useful:

Illustrates that the product can expand footprint in regulated environments.
Describes operational enablement practices such as internal training.

Critical gaps:

Metrics presented in vendor case studies are often qualitative; where quantitative claims exist, they are vendor-published and not independently audited.
Some vendor case study excerpts omit customer identifiers, limiting reference validation.

Vendor / sponsored whitepapers and eBooks

Broadcom publishes eBooks and whitepapers describing Automic and AAI value propositions.

Critical gaps:

These materials are marketing collateral; ROI methodologies may not be fully transparent.
They can be useful for framing vendor value propositions but should not replace independent references or POCs.

04Best fit

Company size

Generally suited to large enterprises; may also fit larger mid-market customers with complex, regulated operations, though total cost of ownership and operational overhead should be evaluated.

Industries

Financial services and banking
Insurance
Retail (batch processing such as replenishment)
Manufacturing and supply chain
Utilities and telecommunications
Any enterprise running SAP alongside heterogeneous workloads

Roles and personas

Decision makers:

VP/Director of IT Operations
Head of Infrastructure / Platform Engineering
Enterprise Architect (integration and governance)
CIO / CTO (for transformation and risk oversight)

End users:

Workload automation administrators
NOC / operations engineers
Application support teams
Release and change management teams

Pain points addressed

Fragmented schedulers and siloed automation tools
SLA misses due to limited end-to-end visibility
Manual interventions for job failures
Governance and audit requirements

Qualification criteria (good fit)

Need for cross-platform enterprise scheduling (not only data engineering pipelines)
High job volumes and complex dependencies
Requirement for SLA management, audit trails, and operational control

05The pitch

What the product does (objective value proposition)

Key portfolio elements frequently referenced by Broadcom include:

Automic Automation (and Automic SaaS) for workload automation and orchestration across heterogeneous environments, with multiple integrations and marketplace add-ons.
AutoSys Workload Automation for centralized job scheduling and monitoring across platforms.
Automation Analytics & Intelligence (AAI) as an analytics/observability layer for automation that integrates with multiple schedulers.

Broadcom describes the portfolio as an enterprise control plane for scheduling and orchestration rather than a developer-first data pipeline orchestrator (for example, Airflow). The materials emphasize visibility, governance, SLA management, and integrations spanning ERP/SAP, cloud services, and legacy infrastructure.

Evidence (official/analyst): Automic SaaS positioning and cloud marketplace presence; AAI described as analytics/observability for workload automation; Automic positioning for SAP environments.

Target market and market positioning

Suitable segments (inferred from product messaging and third-party reviews):

Large enterprises (commonly organizations with thousands of employees) running high-volume, business-critical batch workloads across mixed platforms (Windows/Linux/Unix, mainframe-adjacent ecosystems, ERP/SAP, and cloud services).
Industries where SLA adherence and auditability matter: finance, insurance, retail, manufacturing, utilities, and regulated sectors.

Broadcom positions these tools as:

Oriented toward governance and SLA management rather than lightweight schedulers.
Framed as an enterprise control plane rather than a cloud-native single-purpose scheduler.

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

Download full report →