|
Key Takeaways
|
|
The recent announcement of Automic Automation V26 has generated a lot of well-deserved excitement across the industry. With its introduction of agentic AI capabilities, Model Context Protocol (MCP) orchestration, and an Intelligent Control Plane, it represents a structural shift in how enterprises govern and execute workload automation.
However, if you are an AutoSys customer, this major release might pose a very understandable question: Does this mean Broadcom is shifting focus or investment away from AutoSys?
The answer is a definitive no.
In fact, the innovations you are seeing in the market right now are the direct result of a strategic "shared factory" model under the Automation by Broadcom umbrella—a model designed to accelerate modernization across our automation portfolio, with AutoSys squarely in the roadmap.
Here is why the recent market noise is actually great news for the future of your AutoSys environment.
You might have noticed the specific version number attached to the recent Automic announcement: V26. This is not just an arbitrary product update; it represents a generational leap for the Automation by Broadcom portfolio.
Rather than building siloed, product-specific features, the Automation by Broadcom team has spent the last several years progressively unifying non-scheduler-specific capabilities—such as APIs, integrations, observability, and now AI and orchestration—into a shared set of core services.
Automic was simply the first product to showcase this new architectural foundation and adopt the V26 designation. But this shared factory was explicitly built to serve the broader Broadcom automation portfolio.
Leading industry analyst firm Enterprise Management Associates (EMA) recently validated this strategy in their independent Impact Brief on V26. As EMA noted:
"Rather than forcing convergence at the scheduler level, Broadcom has progressively unified non-scheduler-specific capabilities... into a shared set of core services... While this release is centered on Automic, the underlying architecture is not. It is designed to support a broader evolution in which multiple schedulers can participate in a common orchestration and AI-driven execution model."
This means the groundbreaking capabilities generating headlines today—such as the AI job type, MCP orchestration, bring your own model (BYOM) support, and AI-powered developer assistance—are not exclusive to one product. They are part of a shared foundation that AutoSys will directly inherit as we move forward. The initial V26.0 release will be the starting point for AI in AutoSys and these capabilities will expand in future releases.
The Intelligent Control Plane is the exact destination AutoSys is being built toward. The AutoSys V26 modernization effort is already actively running across three concrete areas:
Deployment modernization: AutoSys is being adapted for containers and Kubernetes. This will make your automation environment deployable, scalable, and operable in the exact way modern infrastructure teams expect.
User experience modernization: We are building a completely redesigned user interface aimed at reducing friction for automation developers and operators. The goal is simple: less time spent navigating tooling, and more time spent on the strategic work that matters.
AI and MCP capabilities: Drawing from the exact same architectural layer powering the rest of the V26 generation, AutoSys will gain MCP orchestration, AI job types, and AI-powered developer assistance. This will allow you to bring non-deterministic AI into governed, auditable AutoSys workflows.
Delivering transformative change responsibly means sequencing it in a way that protects the trusted, rock-solid reliability your organization depends on today. Because AutoSys powers some of the most complex workflows in the world, our roadmap is controlled by important customer commitments. This means AutoSys V26 is being delivered on a different timescale by design—ensuring you gain cutting-edge AI and orchestration capabilities without disrupting your existing operations.
If you are evaluating your automation strategy, the relevant question is not whether Broadcom is investing in AutoSys—it is how you can begin positioning your environment to take advantage of the Kubernetes-based deployment, revamped UX, and AI-assisted orchestration coming your way in the V26 generation.
We want to show you exactly how these changes map to your current environment and planning horizon.
Join us for The Future of AutoSys: Building the AI-Driven Control Plane for Your Enterprise, on April 23, 2026 at 11:00 a.m. ET, for an exclusive, deep-dive webinar in which AutoSys Product Management will walk you through the upcoming roadmap and showcase the new shared architecture.