StitchOps vs Make
Make stops where the API stops.
Keep Make for visual data transformation across APIs. Add StitchOps for the rest.
Two different jobs.
Make
Make gives you a visual canvas for moving and transforming data between APIs, with fine control over each step and good handling of arrays and branches.
StitchOps
StitchOps is the runtime for the steps Make cannot reach: the portal that has no API, the Windows thick client, the on-prem directory. The agent runs inside your environment and returns typed results Make can keep working with.
Side by side.
| Make | StitchOps | |
|---|---|---|
| Apps with an API | Strong. Visual API scenarios. | Supported through API actions, so one workflow can cross both kinds. |
| Systems with no API | Not supported. | Browser and desktop automation from an agent on a worker VM in your environment. |
| Desktop and terminal apps | Not supported. | UI Automation, image, OCR, and terminal actions in the same workflow as the portals. |
| Credentials in your vault | Stored in Make. | Referenced from 1Password, Keeper, or the StitchOps vault. Resolved on the worker. Never shown to the model. |
| Evidence per step | Execution history per scenario. | Step-level status, timing, redacted inputs and outputs, and evidence references on every run. |
The difference
An agent inside your network.
Browser, desktop, terminal and directory actions run from a worker VM in your environment, with credentials referenced from your vault and every step logged. That is the part no API-shaped tool reaches.
How it executes →Worker
worker-01 · connected
- Windows Server 2022 · signed installer
- outbound only · TLS 1.3 · 0 inbound ports
- unattended session · dedicated VM
Capabilities
- browser
- desktop
- terminal
- file
- ldap / ad
Systems reached today
- DealerCONNECTbrowser14
- Dealertrackbrowser9
- DMS thick clientdesktop6
- On-prem ADldap22
- Report sharefile3
Secrets
31 references resolved on worker · 0 values sent to control plane
Better together.
Keep Make for data transformation across APIs. Call a StitchOps workflow for the step that lands in a portal or a desktop app, and continue the scenario with the result.
Make and StitchOps, asked directly.
Can StitchOps replace Make?
No. Make is good at visual data transformation across APIs. StitchOps is the runtime for the step that lands in a portal or a desktop app. Use both and pass typed results between them.
How does a Make scenario call StitchOps?
With an HTTP module against the StitchOps REST API. The workflow runs on your worker VM and returns a typed result the scenario keeps working with.
Does StitchOps run on-prem systems Make cannot reach?
Yes. The agent runs on a dedicated worker VM inside your network and reaches on-prem directories, thick clients, and internal portals over an outbound-only connection.
Start with one workflow that never had an API.
Fifteen minutes on your top three manual processes. We tell you which one to run first.