Workato

Workato's pitch changed shape over the last year. It still sells an iPaaS — the recipe engine, 17,000+ connectors per its homepage, Data Hub/MDM, B2B/EDI, IDP, low-code apps — but the homepage now leads with the argument that every team is building its own agents with its own access and one-off code, producing sprawl, silos, and blind spots. That framing is accurate for large orgs, and Workato's answer is to put both the governance layer and the execution layer on one runtime. The governance side is more concrete than most vendor agent-governance messaging. The September 2026 MCP release scopes access per tool and per user group, so a single server can carry read tools for everyone and write or destructive tools only for roles that need them — that is an unusual level of granularity. The control plane also covers model routing, so you're not locked to one model provider, plus the audit, masking, and residency controls enterprises ask for. The builder side has caught up meaningfully. Undo/redo arrived in the recipe editor in September 2026 and covers AIRO-made changes on the same stack, which matters once agents start editing your recipes. Event Streams raised message size from 512KB/1MB to 10MB with recipes batching to 50MB, and native SOAP services plus XML streaming to 200MB address the SAP IDoc and EDI workloads that used to require middleware. Workato Resources turns WSDLs, XSDs, and XSLTs into versioned governed assets rather than pasted snippets. Where it doesn't fit: small teams and startups. There is no published self-serve pricing, and this is a platform with an implementation and an owner. If you need three one-to-one app connections, you're paying enterprise overhead for a solved problem. Workato itself says cheaper workflow tools win on time-to-first-automation, which is an honest concession. The other honest caveat is that breadth is a learning curve — agent building, orchestration, MCP gateways, API management, IDP, and data orchestration is a lot of surface area for one person to own.