Approval gates
Sending, paying, publishing, cancelling and merging all stop and wait for a person, with the full thing attached. You choose what else joins that list; the agent cannot remove anything from it.
It stops before
it costs you anything.
An agent that can send email, move money and publish pages needs to be wrong safely. Kaer's answer is structural: consequential actions wait for a person, every run is isolated, access is scoped and revocable, and everything that happened is recorded.
How a mistake is kept cheap.
Isolation per run
Work happens on isolated machines with nothing shared between jobs — its own disk, its own browser session, destroyed when the run ends.
Scoped, revocable access
Each connection carries the narrowest scope that completes the task, granted by you and revocable one tool at a time. Kaer never escalates its own permissions or asks for admin.
An audit trail you own
Every action the agent took and every approval a person gave is timestamped and attributable. Export it, or query it from your own systems.
Two ways in, one set of rules
A browser session is not a loophole.
Kaer reaches some services through a native connector and the rest by signing in and using the web app. That distinction changes how access is scoped — not whether the gates apply. A payment made in a browser stops for approval exactly like one made through an API.
- Native connections: explicit API scopes, revocable individually
- Browser sessions: isolated machine, destroyed at the end of the run
- Same approval gates, same audit trail, either way
Your data
Not training material.
Your correspondence, documents, customer records and code are the context the agent works from. They are not used to train models. Enterprise adds private compute options and retention controls on top.
- No training on your content — code, mail or documents
- Retention controls and private compute on Enterprise
- SSO, SCIM and role-based access for larger organisations
Security, answered.
Are you SOC 2 or ISO 27001 certified?
Not today, and we are not going to imply otherwise on this page. If a formal certification matters for your procurement, tell us where you are in that process and we will be straight with you about our timeline rather than about our status.
Can the agent send email as me without approval?
No. Replies are drafted and held. You can turn on specific routine sends once you have seen them work, and anything involving money, cancellation or publishing stays gated regardless of what else you automate.
What happens to the machine a job ran on?
It is destroyed when the run ends. Nothing is shared between jobs, and there is no residual access once a job closes.
How do I revoke access?
Per tool, at any time, from the connectors screen. Revoking one connection leaves the others intact, and any job that needed it stops rather than working around it.
How do I report a vulnerability?
Email [email protected]. We will acknowledge it and tell you what we are doing about it — we would much rather hear it from you first.
Bring your
security team.
We would rather answer the hard questions before you buy than after. Book thirty minutes and ask them.
or email us