Automation that asks before it acts.
Every consequential change waits on Decisions with its evidence, and scoped API keys let your own scripts read the fleet and act within limits.
Explore sample Invite-only ยท Sample data in preview
Routine work can run itself. Consequential changes should wait for a person.
Replacing, resting, reserving and retiring inboxes all queue on Decisions, grouped by kind and shown with the reason. Approve one, or approve a batch.
Queue the change
Doctor findings and your rules turn into proposals on Decisions.
Read the evidence
Each proposal shows why it was made and what it affects.
Approve
Approve one change, or a whole group at once.
Your tools, the same guardrails.
- Read keys
- Let a script or agent read fleet health and records.
- Act keys
- Allow actions, limited to one workspace.
- A rate-limited API
- An allowlisted set of endpoints with a request limit.