Skip to main content
For technical operations

Automated ops with a
human kill-switch.

Kaer runs your runbooks end-to-end — health checks, migrations, deploys — and pauses the moment any action needs sign-off. Nothing risky executes without a human in the loop.

A server cabinet with a large emergency stop button on top
Fig. 14 · Kill-switch
Workflows — HubRuns
Workflow run history: counts of active, queued and completed runs with the latest activity
010
risky actions without sign-off
021-tap
to approve or hold any action
03Full audit
who, what, when — attributable
04Revocable
pull any scope, any time
Scoped permissions

Every token ships with an explicit, revocable scope list.

Kaer never requests admin. Each integration token carries exactly the scopes the task needs — granted automatically for low-risk reads, gated behind a one-tap approval for anything that writes to production. Revoke any single scope without touching the others.

  • Auto-granted: deploy:staging, metrics:read, logs:read, config:pull
  • Approval-gated: db:write, deploy:production
  • Admin-only, never auto-requested: iam:manage
Settings — Security
Account security settings: password, two-factor and active session controls
A workshop owner at a cluttered desk working through a stack of paperwork on a laptop
Access
Scoped per tool
Trail
Exportable
Who this is for

The runbook nobody has time to run.

The checks, the chasing and the month-end reconciliation that stay on a list until something breaks. Each one runs on a schedule with a scoped, revocable token, and stops at the step that would cost you something if it were wrong.

How it works for ops

Automation that knows when to stop.

01

Nothing risky runs unwatched

Every action outside your approved scope pauses and waits for a one-tap sign-off. Kaer never escalates its own permissions.

Human-in-the-loop
02

Scope-matched, not admin

Tokens ship with the narrowest scope that completes the task. Deploy staging never implies deploy production — ever.

Least-privilege
03

Audit trail you own

Every action, approval and scope grant is timestamped and attributable. Export it as CSV. Query it from your SIEM.

Exportable
Runbook execution

One tap to unblock. Nothing slips through.

Kaer runs the whole runbook end-to-end — until it hits a gate. It pauses at the exact step that needs a human decision, explains what it needs, and resumes the rest automatically the moment you approve.

  • Health-checks, traffic drains and config pulls run automatically
  • The production migration pauses for sign-off
  • Row-count verification and rollback plan run after approval
Operator — QuoteAwaiting
A quote the agent priced from the rate card, held for approval before it is sent

Attributable actions, all the way down.

Every step Kaer takes — and every approval your team grants — is timestamped, named, and written to the audit log.

Every agent action carries the scope it used; every human approval records who signed off, when, and exactly what they permitted. Export it as CSV, push it to your SIEM, or query it directly. The trail is yours.

Ops that moves fast
without breaking things.

Kaer runs the repetitive parts of your runbooks automatically, pauses for every decision that matters, and leaves a full trail your team and your auditors can read. Safe by default — not by accident.

A server cabinet with a large emergency stop button on top
Fig. 14 · Kill-switch