Use cases
What People Hand to Operator
Work that needs a computer: a browser, a terminal and files. Operator does it on a computer of its own, asks before anything leaves it, and keeps a journal of every step.
Real work, on a real computer. Each of these runs on Operator’s computer, with you in the loop for anything that matters.
Research Across Sites
It reads across many sites and comes back with the answer and the links it used.
What you hand it
A question that takes an afternoon of tabs: terms, prices, opening hours, policies, specifications.
What it does
It opens each site in its own browser, reads what matters and keeps notes in its files as it goes.
Where it stops for you
It works on its own; reading needs no approval. If a site wants a sign-in, you take over and type it.
What you get back
A table or a brief, with a link for every fact, and the journal of every page it opened.
Back-Office Work in Web Apps
It works through the web tools your team already uses, and asks before it saves.
What you hand it
The updates nobody has time for: records to correct, addresses to change, entries to copy from one tool to another.
What it does
It works in the web app the way a person would, in its own browser, one record at a time.
Where it stops for you
It asks before saving a change to another system. You take over the screen to sign in.
What you get back
The work done, with each change and each approval in the journal.
Data Pulls and Reports
It gathers figures from pages and files into a spreadsheet and a summary.
What you hand it
Figures scattered across dashboards, exports and documents, and the report they belong in.
What it does
It collects the numbers, puts them in a spreadsheet on its computer and writes up what changed.
Where it stops for you
Nothing leaves its computer without you. Sending the report is an action that waits for your yes.
What you get back
The spreadsheet and the summary to download, and the sources it read.
Dev Chores in a Terminal
It clones, upgrades, runs the tests and reports, in a terminal of its own.
What you hand it
The chores between real work: dependency upgrades, test runs, release notes, a broken build to look into.
What it does
It works in the terminal on its own computer: clones the repository, makes the change, runs the tests.
Where it stops for you
Pushing a branch leaves its computer, so it asks first. Signing in to a code host is yours to do.
What you get back
A report of what changed and what broke, and the branch, once you allow the push.
Monitoring, With Approvals
It checks what changed since last time, and asks before it acts on it.
What you hand it
Pages to keep an eye on: prices, stock, policies, a competitor's announcements.
What it does
Its computer keeps last time's notes, so each check compares against them. Start it when you like, or from your own scheduler through the API.
Where it stops for you
When something moved, it drafts what should happen next and waits for your approval.
What you get back
What changed, with links, and nothing done that you did not allow.
Support and Operations
It works the queue, looks things up and drafts replies for you to approve.
What you hand it
A queue of requests in your help desk or operations tool, and the systems where the answers live.
What it does
It reads each request, looks up the order or the account in the tools you use, and drafts the reply.
Where it stops for you
Every reply waits for your approval before it is sent, and any change to an order does too.
What you get back
Replies ready to go, each one approved by a person, all of it on the record.
Forms and Applications
It fills in the long forms from your documents and stops before it submits.
What you hand it
Renewals, registrations and applications, with the documents that hold the answers.
What it does
It reads your files and fills in the form field by field, in its own browser.
Where it stops for you
It stops before submitting, accepting terms or paying, and it never moves money.
What you get back
A finished form waiting for your yes, and the journal of every field it filled.
Work That Cannot Leave
On a private deployment, confidential work stays on your own servers from start to finish.
What you hand it
Contracts, records and internal systems that may not be sent to anyone else's cloud.
What it does
Agents work on computers inside your infrastructure, with open-weight models on your own GPUs.
Where it stops for you
Your people answer every approval, by your rules, and the journal is kept on your servers.
What you get back
The work done where the data already lives. Nothing passes through Makina's cloud.
What Every Task Has
Whatever the work, the same four things are behind it.
- A computer of its ownA browser, a terminal and files, on a desktop that is nobody else's.
- Your approval before anything that leavesSending, submitting, buying, deleting: it asks first, and never moves money.
- Takeover when it needs your handsYou hold the screen to sign in. Operator never asks for a password.
- A journal of every stepSealed as it happens, with a signed receipt for every consequential action.
Some work cannot leave your servers. Run the same agents on your own infrastructure, with your own models, and we help you build the workflows.
Private deployments