Its own machine, its own disk
A machine is built for one coworker and one job. Nothing else is on it while it runs.
Cloud computer
A real machine in the cloud, with a browser, a shell and a disk of its own. It opens the app that has no API, clicks the button, reads the PDF.
Most business software was built for people. A coworker that can only call an API stops at the login screen.
The supplier portal
Sign in to Northwind Billing
No API. No export. Nothing to integrate.
What it does instead
Six moves a person makes every month. Nobody automated them, because there was nothing to call.
Three things, and they are the three a person uses.
A real Chrome it drives itself. It opens the page, reads what is on it, then clicks, types and chooses.
A bash prompt. It runs a script, converts a file, and reads what came back. Python and the PDF tools are already installed.
$python3 check_invoice.py NS-2048.pdf
Net £10,400 + VAT £2,080 = £12,480
exit 0
Its own disk, mounted at /workspace. What it saves this week is still there next week.
The machine is built for one job. When the job ends, the machine ends.
Nothing else runs on these machines. Not another coworker, not another company.
A machine is built for one coworker and one job. Nothing else is on it while it runs.
The token is attached to the request outside the machine. Nothing inside can read the value.
Every machine and every disk is keyed to one workspace. No other workspace can reach either.
The machine is destroyed the moment the job finishes. No machine lives longer than an hour.
Each one gets a browser, a shell and a disk. Give it the work nobody automated.