Actions run
only after approval.

AI can only run actions you've registered in advance. It picks the one that fits the situation, proposes it with a reason, and runs it after a person approves. The proposal, approval, execution, and result can be followed as a single record.

  • Only registered actions can run
  • Actions using the admin connection always require approval
  • Rollback steps are recorded alongside
Awaiting approvalcritical

Temporarily extend the payment retry interval

Runs the registered action "Change retry interval". Rollback uses the same steps to restore the original value.

Approve and runReject
Challenges

Sound familiar?

Letting AI write to the production database feels risky

Remediation steps exist only in people's heads

You can't trace who ran what, and when

What it does

Only the steps you define
ever run.

01

AI-written SQL is never executed

For actions that write, only the fixed SQL you registered can run. SQL generated by AI never goes through the admin connection.

02

Every proposal comes with a reason

Based on the investigation's conclusion, AI picks a fitting action from those registered and proposes it with a reason. Unregistered actions are never proposed.

03

Approval requests go to your channels

When an action needs approval, your registered notification channels are alerted. You can approve or reject from the incident page, and the rollback method is shown alongside.

04

Nothing runs without approval

If 24 hours pass without approval or rejection, the action is closed as expired without running.

Details

Actions you can register

Actions are registered per project. What may be run is decided by you, not by AI.

Fixed SQL

Runs SQL you've written in advance on the target connection. Whether to use the admin connection is also set per action.

External notifications

Sending to integrations such as Slack or Microsoft Teams can also be registered as an action.

Opt-in auto-run

Actions that are safe to run without approval can be explicitly set to run automatically. This can't be set for actions that use the admin connection.

Rollback steps

You can write rollback steps for each action. They're also shown on the approval screen.

Approval deadline

Actions left awaiting approval for 24 hours expire without running.

Execution record

Proposals, approvals, rejections, and results are kept on the incident timeline. Approvals and rejections are also recorded in the audit log.

How to use

How an action gets run

All you need is a database connection string or an account connection. Nothing to install on your servers.

  1. STEP 1

    Register actions

    Register the SQL and notifications that are allowed to run, together with their rollback steps.

  2. STEP 2

    AI proposes

    It proposes an action that fits the investigation's conclusion, with a reason.

  3. STEP 3

    Approve and run

    Review it and approve to run it; the result is recorded. You can also reject it.

Who it's for

Who it's for

  • You don't want AI writing to your production database
  • You have set procedures for common incidents
  • You want to move remediation forward just by approving, even at night
  • You want a record of who approved what
  • You want people who don't know databases well to make remediation calls
Use cases

Use cases

Payments

Temporarily lengthen the retry interval

If slow responses from the payment processor turn out to be the cause, AI proposes the registered "change retry interval" action. Approving runs it, and rolling back uses the same procedure to restore the original value.

Escalation

Make contacting the on-call person an action

Chat notifications and ticket creation can also be registered as actions. AI picks the destination that fits the situation and proposes it.

AI proposes,
people decide.

Only the procedures you register can run, and every approval and execution is kept on record.