For technical operations
Runbooks that run, and stop where you say.
Kaer runs routine checks and maintenance on its own computer, on a schedule, and pauses at the approval steps you put in. Each run keeps a record of what it did.
What ops teams hand over
Scheduled checks
Runs the checks you would otherwise run by hand, on a schedule, from its own computer, and reports what changed.
Waits for you: nothing. It reads and reports.
First look at an incident
Reads the logs and recent changes it has access to and posts a short summary of what it found for the person on call.
Waits for you: the Slack message, by default.
Routine maintenance
Dependency bumps and small fixes, made in your repository and opened as a pull request for your team to review.
Waits for you: the merge. Your team reviews the pull request.
Runbooks with a pause
Turn a runbook into a workflow and put an approval step before the part that matters. The run stops there until someone approves or rejects it.
Waits for you: the approval step you placed.
How you stay in control
Email, Slack and social posts
Kaer drafts and you approve or edit before anything goes out from Kaer Mail, Gmail, Slack or a social account. If you want, you can let routine replies go automatically.
Payments
A click its browser recognises as a payment is held until you approve it.
A record of every task
Each task keeps the steps it took and the tools it used, so you can see how a result was reached.
Access you can take back
You connect each tool yourself and can revoke any one connection without touching the others.
Start with the check nobody has time to run.
Workflows and the agent's browser come with paid plans.