Automate the systems with no API.

An agent in your environment runs portals, desktop apps, and on-prem systems the way a person would, for IT, finance, compliance, and operations. Deterministic, credential-safe, logged step by step.

Book a free workflow audit Get a demo

Enterprise deployments with healthcare, technology, manufacturing, automotive and defense contractors. Works with Claude, ChatGPT, and Copilot.

Integrations and partners

Okta
Microsoft
Google Workspace
JumpCloud
Incode
Slack
ElevenLabs
1Password
Keeper
Veza

acme-dealers / offboard-closed-apps

Run

Triggerdirectory.user.disabled

Browser · openvendor-portal.example.com

Browser · login{{secrets.vendor.admin}}

Browser · find user{{input.email}}

Gateconfirm deactivate

Evidencecapture step 5

6 steps · validated against registry · v14

Completes the stack.

Your systems of record decide what should happen. APIs act where they exist. StitchOps does everything else.

Layer 1

Systems of record decide

Identity, HRIS, ERP, ticketing. What should happen.

Layer 2

APIs act where they exist

iPaaS and MCP tool servers cover the apps with an API.

Layer 3

StitchOps acts on the rest

Portals, desktop apps, terminals, on-prem directories.

Reach

Anywhere a person can log in and act.

Browser, Windows desktop, terminal, file, and Active Directory actions in one workflow, from an outbound-only agent on a worker VM inside your network.

See the platform →

acme-dealers / worker-01

Run

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

Governance

AI proposes. StitchOps executes.

The model picks from typed tools and named elements. The agent owns credentials and coordinates. Shell and arbitrary code are blocked. Destructive steps wait for confirmation.

Connect your assistant →

acme-dealers / AI assistants

Run

Offboard j.doe@example.com from the three portals SCIM doesn't cover and show me the evidence.

I found a saved workflow for this. Running it on worker-01.

tool call

workflow_offboard_closed_apps

{ "email": "j.doe@example.com" }

Confirmation required

Step 5 deactivates the user in vendor-portal. This cannot be undone by the workflow.

ConfirmCancel

completed in 5.2s

3 portals · 6 steps · evidence: step_05.png, step_11.png, step_17.png

Done. The user is removed from all three portals. Evidence is attached to run_01j8k.

Ask your assistant…

Evidence

Same inputs, same outputs. Every step logged.

An AI discovery session becomes a saved workflow that replays without a model in the loop. Each run records status, timing, and redacted inputs and outputs.

How security reviews go →

acme-dealers / Runs

Run

Run	Workflow	Trigger	Time	Status
run_01j8k	offboard-closed-apps	directory event	5.2s	ok
run_01j8h	rotate-portal-password	schedule	12.4s	ok
run_01j8f	access-review-monthly	schedule	188s	ok
run_01j8c	orphan-cleanup	assistant	41.0s	failed
run_01j89	oem-report-pull	schedule	58.3s	ok

Your assistant, with governed hands.

Claude, ChatGPT or Copilot decides what should happen. StitchOps is what makes acting on it safe.

Your assistant

Claude
ChatGPT
Copilot

Picks from typed tools. Never sees a credential.

MCP

The execution layer

StitchOps

·validates against the registry
·resolves secrets on the worker
·gates destructive steps
·logs every step

Deterministic. Same inputs, same outputs.

outbound only

TLS 1.2+

Your systems

Vendor portals
Desktop apps
Terminals
On-prem AD

Reached from a worker VM inside your network.

Connected, or simply operated.

Ten systems have a native connection. The hundreds of others your team logs into do not need one.

Native connections

Authenticated integrations built into the product.

Google Workspace

Slack

Microsoft 365

Okta

Entra ID

LDAP / Active Directory

1Password

Keeper

Veza

Google Ads

Run the way a person would

No API, no connector, no vendor cooperation required.

Automotive

DealerCONNECT
Dealertrack
CDK
Reynolds & Reynolds

Healthcare

Office Ally
Payer portals
Clearinghouses
EHRs

Financial services

Custodian portals
Fund admin portals
Core banking
Compliance tools

Accounting

QuickBooks Desktop
State tax portals
Bank portals
Expense platforms

Legal

Court e-filing
Practice management
Document management
Client portals

Enterprise IT

SAP GUI
Mainframe sessions
On-prem AD
Acquired-app consoles

MSPs

RMM
PSA
Vendor consoles
Per-client AD

Property

Utility portals
Municipal portals
Resident portals
Vendor portals

And anything else that sits behind a login, once a workflow has been scoped for it.

Four ways to build.

The same workflow underneath, whichever way you start.

Remove leavers from the OEM portal and capture evidence.

Drafted 6 steps · 1 confirmation gate
[Run] [Edit on canvas]

Describe it to Stitch

Plain language in, a runnable workflow out.

Triggerschedule · daily 06:00

Browser · login{{secrets.portal.admin}}

File · writereport.csv → share

Build on the canvas

Typed actions, validated before they run.

POST /v1/workflows/offboard-closed-apps/runs
{
  "inputs": { "email": "j.doe@example.com" },
  "confirm_destructive": true
}

202 { "run_id": "run_01j8k", "status": "queued" }

Call the API

Run workflows with typed inputs from your systems.

tools from StitchOps

workflow_searchread

workflow_offboard_closed_appswrite · confirm

workflow_run_statusread

flex_data_queryread

Ask your assistant

Claude, ChatGPT, or Copilot over MCP.

Every department has one.

The system nobody could automate. One agent and one workflow model, across the teams that still run on portals and thick clients.

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.