Automate the Tailscale admin work your team still does by hand.
Device approvals, ACL updates, and access reviews still happen by clicking through the admin console. StitchOps operates that console the way your engineer does, using browser automation and computer vision so the manual tailnet work finally runs on its own.

What StitchOps actually does for your tailnet
It does the console clicking so your team stops.
Point it at the Tailscale admin console, describe the job in plain language, and it signs in, navigates the tabs, reads the screen, and finishes the task. It runs the same approval and reconciliation work your engineers do by hand.

Operates the console directly
It signs into the admin console and clicks through the tabs, so no Tailscale API is required.

Survives a console redesign
Computer vision finds each control, so workflows keep running when the admin console changes its layout.

Reconciles across your whole stack
Read your IdP groups, drive the Tailscale console, and write the result back, all in one run.

Every action is logged
It records the named control it touched, so a reviewer sees exactly what ran in the console.
Built for the systems you already run







Why teams trust it to run unattended
Reliable enough to leave alone.
Automation that only works in a demo isn't worth deploying. StitchOps is built to run unattended and self-heal when the admin console shifts, with credentials that never leave your own vault.
BYOKV credential custody
Admin credentials stay in your own key vault. StitchOps never holds them and never persists them.
Runs in your environment
The agent executes inside your network with an outbound-only connection. No inbound ports.
Deterministic and auditable
Every console action is logged by the named control it touched, so any run is reviewable.
Compliance ready
SOC 2 Type 1 complete, Type 2 in progress, with HIPAA deployments supported via BAA.
See it run on your tailnet
Scope one admin console workflow and watch StitchOps run it live inside your own environment.
Before and after StitchOps
Trade the console checklist for a workflow.
Tailscale made the network simple. The admin work around it stayed manual and never scales. Here's what changes the day StitchOps operates the console for you.
From manual console to live automation
Start with one workflow prove it, then expand.
You don't buy a platform on faith. You pick the console workflow that hurts most, watch it run inside your own environment, and let the proof of value make the decision for you.
1. Pick the painful one
Name the console task that eats the most time. That's the workflow we scope.
2. Describe it in plain language
Tell the AI assistant the console steps. It builds a runnable workflow on a visual canvas.
3. Run it in your environment
The agent operates the console inside your network, pulling credentials from your own vault.
4. Measure, then expand
See hours recovered, then add the next console workflow as a sub-workflow.
What's your next move?
The console isn't going to automate itself.
It's been manual this long because the admin work lives behind a UI. The only real question left is whether you want to see it run, dig into the details first, or keep clicking through it for another quarter.