Service Orchestration and Automation Platforms (Gartner)

Gartner published the 2026 Magic Quadrant for Service Orchestration and Automation Platforms on 5 August 2026, the fourth edition of a report the firm created in 2023 when it retired its workload automation quadrant. Twelve vendors were evaluated and seven were named Leaders: BMC, Redwood Software, IBM, Stonebranch, Broadcom, HCLSoftware and Beta Systems Software.

The report is credited to Hassan Ennaciri, Daniel Betts and Chris Saunderson. The five vendors that did not reach the Leader rung were Rocket Software, Resolve, Decisions, Absyss and JAMS.

The 2026 Magic Quadrant for Service Orchestration and Automation Platforms, and its seven-vendor Leader rung

Seven Leaders from a field of twelve is a wide rung. Published coverage of the results assigns each of the seven a position on both axes, and the positions run from first to last: Redwood first on vision, BMC first on execution, and Beta Systems and Broadcom at the bottom of both orderings. A buyer reading only the word Leader is reading a band that spans the whole chart.

The products behind the placements are older than the category. BMC's Control-M, IBM's Workload Automation, Broadcom's Automic Automation and Stonebranch's Universal Automation Center are all scheduling engines that predate the cloud, and the newer names on the rung, Redwood's RunMyJobs and HCLSoftware's Automation Orchestrator Suite, are competing for the same job: deciding what runs, where it runs, and what happens when it does not finish.

That is a narrow-sounding remit for a market that Gartner now describes as the place where infrastructure and operations teams design and implement end-to-end workflows. The gap between those two descriptions is the story of this quadrant.

Gartner retired the workload automation quadrant in 2023 and replaced it with this one

The predecessor report was the Magic Quadrant for Workload Automation, and it was retired rather than renamed in place. Gartner had published a Market Guide for Service Orchestration and Automation Platforms in 2021 to define the term, and the quadrant followed in 2023.

The reason given for the change was that scheduling tools had stopped matching what their buyers were doing. A job scheduler that ran the nightly batch on a mainframe was a complete product for a data center. The same buyer now runs workloads across on-premises systems, several clouds and a set of SaaS applications, and the orchestration problem is deciding the order rather than executing the step.

Gartner's definition of the category leans on three capabilities: workflow orchestration, workload automation and resource provisioning, extended across data pipelines and cloud-native architectures. The 2026 report adds a fourth concern that was not in the original framing, which is where agents fit.

BMC took execution and Redwood took vision, for the third year running

Three of the seven Leaders state that this is their third consecutive year on the rung: BMC, Redwood Software and Stonebranch. The stability is the message. Whatever Gartner changed when it retired the workload automation report, it did not change the top of the market.

Redwood's account of the placement is the most specific. It says Gartner positioned it furthest in Completeness of Vision for the third year in a row, and that it placed first in four of the five use cases in the companion Critical Capabilities report, tied for first in the fifth. BMC's account states the first place on Ability to Execute.

The two claims describe different things, and the difference is worth holding onto. First on execution is a statement about how the vendor performs today. Furthest on vision is a statement about where the analyst thinks the market is going. A vendor can hold one without the other, and these two have held opposite ones for three years without either displacing the other.

Stonebranch was placed third on execution and fourth on vision. IBM was third on vision and fourth on execution. HCLSoftware and Beta Systems filled the middle and lower reaches of the rung, and Broadcom, whose Automic Automation has been in enterprise scheduling for decades, was placed at the bottom of both orderings.

Seven Leaders out of twelve is a rung that has stopped sorting the field

A Leader band that contains more than half the evaluated vendors does less work than the label suggests. The common reading is that the market has a settled top and the analyst is declining to pick between near-equals. The less comfortable reading is that the boundary between a Leader and a non-Leader in this market has become thin enough that twelve vendors produced seven of one and five of the other.

Both readings argue for the same response from a buyer, which is to stop reading the rung as a ranking. The quadrant's own structure supports that: two axes, four quadrants and a Leader band that runs from first to seventh in published coverage. Everything a procurement team actually needs to discriminate between these vendors sits in the Critical Capabilities use cases, and those scores are the ones vendors quote least often.

That pattern is not unique to this market. It shows up wherever a mature category has a stable vendor set.

Five vendors outside the rung, and one that appears in Forrester's agentic market instead

Decisions is the interesting name in the second half of the field. It is evaluated by Gartner in this quadrant, outside the Leader rung, and it is also a confirmed participant in Forrester's Adaptive Process Orchestration Software Landscape, a report about a market that Forrester treats as distinct.

The same company appears in both documents because the two firms drew their boundaries differently. Gartner's SOAP quadrant covers the platform that decides what runs and in what order. Forrester's adaptive process orchestration covers platforms that run AI agents alongside deterministic control flows inside one process. Decisions sells into both descriptions, and so do several of the vendors that Gartner placed above it here.

For a buyer, the practical consequence is that the two documents cannot be read against each other. A vendor's absence from one is not evidence about the other, and a shortlist assembled from the Gartner rung will not contain the companies Forrester considers the category leaders.

Gartner's forecast puts agents at half of this platform's activity by 2030

The 2026 report carries two forecasts that reframe what an orchestration platform is for. By 2029, Gartner expects 75 percent of service orchestration and automation platform workflows to use generative AI, raising troubleshooting efficiency by 50 percent from a base of less than 20 percent in 2026. By 2030, it expects half of all platform activity to be initiated by AI agents, up from less than 5 percent in 2026.

Read those two numbers together and the shape is clear. The first describes an assistant inside the existing product. The second describes an inverted product, where the platform's main job is to receive work from agents and hold the record of what they did.

An earlier Gartner forecast in the same series is now a useful check on how these predictions age: by the end of 2025, 80 percent of organizations then delivering workload automation were expected to be using platforms of this kind to orchestrate workloads across IT and business domains. That number appeared in the marketing material of several vendors on the rung, which is what tends to happen to a forecast that flatters the reader.

The gap between 5 percent of activity today and half of it in 2030 is the most consequential figure in the report, because it is a claim about who initiates work rather than a claim about how fast the work goes.

Forrester folded the deterministic spine into its new category, and Gartner kept it here

The structural difference between the two firms is now visible in their category lists. Forrester's definition of adaptive process orchestration describes a platform that uses AI agents and nondeterministic control flows in addition to traditional deterministic control flows. Both execution models sit inside one category, and the load-bearing phrase is the one that says they coexist.

Gartner has two categories where Forrester has one. The deterministic spine lives here, in a quadrant whose vendors are scheduling engines, and the agentic consolidation layer lives in a separate report the industry calls business orchestration and automation technologies. Gartner's SOAP forecast, that agents will initiate half of platform activity by 2030, is the prediction that the two categories converge.

Which leaves this quadrant in an unusual position. It is being asked to evaluate a mature, stable vendor set against a definition that is quietly expanding underneath it, and its own Leader rung has not moved in three years. The vendors that manage the transition will look nothing like the vendors that do not, and the quadrant will not tell a buyer which is which until the transition is over.

What to ask before you buy an orchestration platform in 2026

Ask which use case you are actually buying for. A seven-name Leader rung and a companion Critical Capabilities report produce different pictures of the same vendors, and the scores in the second document are the ones that move with the shape of your workload.

Ask what the platform does with a workflow that an agent started. The forecast says half of the activity on these platforms will be initiated by something other than a person within five years, and the audit record for that work is a design decision rather than a feature.

Ask how the migration off a legacy scheduler is priced. Four of the seven Leaders sell a product whose installed base is the reason they are on the chart, and the cost of moving that base is not in the quadrant.

Ask whether the orchestration layer is being sold as a platform or as a capability of a larger suite. Several of these vendors appear in other Gartner quadrants with different products, and the version of the product that was scored here may not be the one in your renewal.

Ask what happens to the runbook. Orchestration platforms earn their place by holding the procedure for what to do when a job fails, and a platform that has automated the scheduling but not the recovery has moved the work rather than removed it.

Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.

Gartner's own boundary statement for this market is worth reading before the quadrant: service orchestration and automation platforms are described as complementary to, rather than replacements for, automation in other domains, infrastructure automation among them. Infrastructure Automation Platforms covers that neighbouring market, where the work is provisioning and configuring the estate rather than sequencing what runs on it. A buyer whose problem is that environments drift will not fix it by buying a scheduler, and a buyer whose problem is that the nightly chain breaks will not fix it by buying a provisioning tool.

Data pipelines were folded into Gartner's definition of this category rather than left to the integration market, and the report's own forecast leans on that: the workloads these platforms are expected to orchestrate as adoption grows are hybrid workloads and data pipelines. Data Integration Tools covers the other end of that boundary, where the question is how data moves rather than when the job starts. The two markets overlap in the middle and a shortlist for one will not surface the other.