A comparative assessment run for the group’s parent company under a signed statement of work: Itential and Gluware, each set against traditional automation methods, and each actually built out on virtualized topologies in the practice lab rather than assessed from a datasheet.
Why building it was the method
Orchestration platforms all demonstrate well. What separates them is what happens on a topology that resembles a client’s — the device coverage that turns out to be shallow, the workflow that needs an exception on the third try, the thing the platform assumes about your source of truth that is not true of anyone’s. None of that is visible in a feature matrix, and all of it decides whether the platform survives contact with an estate.
Keeping traditional automation in the comparison as a baseline was deliberate for the same reason. The question worth answering is not which platform wins but whether a platform beats scripts and change control for this organization’s actual work — and sometimes the honest answer is that it does not yet.
The procurement part
The track stalled inside procurement, and I worked the blockage myself rather than reporting it as a dependency. It closed with an Itential master services agreement in place.
That is a small thing to record and a real one. An evaluation that produces a recommendation and then dies in a purchasing queue has produced nothing, and an architect who treats the commercial path as somebody else’s problem has done half the job. The governance principle underneath it is the one that runs through all of this work: automation multiplies the blast radius of a mistake, so the decision about which platform holds the keys is worth doing properly and worth finishing.
Outcome
An Itential master services agreement in place, on evidence from a build rather than a vendor comparison chart.