Security
Trust You Can Check
Operator keeps your work where you decide, asks before it acts, and writes down everything it does, so its work can be checked instead of taken on trust.
How Operator Keeps Work Safe
Your infrastructure, if you want it
In a private deployment the agents, the models and the data run on servers you own, through Exos Private Cloud or your own. None of it passes through Makina's cloud.
A computer for every agent
Each account's agent works on its own computer, so one person's files and screens never mix with another's.
Approvals before consequences
Anything that leaves the computer or cannot be undone waits for a person. A service can never decide an approval.
Takeover for sign-ins
Operator never asks for a password. When a site needs one, you hold the screen and type it yourself.
A sealed journal
Every step is appended to a journal whose SHA-256 chain breaks if any entry changes afterwards.
Signed receipts
Each consequential action carries a receipt signed with ECDSA P-256, with the signing keys in your settings.
A brake on spend
Every task stops at its budget, every day at your limit, and Operator never moves money.
Sign-in you already trust
Accounts sign in with Google or a one-time code by email, through WorkOS. Idle sessions end on their own.
Your work stays yours
We do not train models on your work, show advertising, or sell personal data.
The Services Behind Makina's Cloud
Each one receives only what its part needs. In a private deployment, these parts run on your infrastructure instead.
In Makina's cloud
- WorkOSSign-in
- StripePayments, on Stripe's own pages
- E2BThe agents' computers
- Fly.ioHosting and the database, United States
- TigrisFiles, screens and saved workspaces
- OpenAIThe default model
- OpenRouterThe other catalog models
- Temporal Cloud and UpstashCoordinating runs, identifiers only
Questions About Your Data
What Makina keeps, where it is kept, and who else handles it.
Read the privacy policy