Operations agents
Agents that carry a repeating process through the systems that hold it, and stop at the point a person must decide.
Take this request through the process and stop where an approval is needed.
Each step, what it read or wrote in which system, and the point where it stopped for a person.
What an operations agent is designed to do
A request arrives, and the process around it is known to everyone: check the record, check the entitlement, check the limit, write the outcome, tell the person. It is done a hundred times a week, in four systems, by people who did not join to do it.
The pack is designed to:
- move a request through the process in the order the procedure sets out;
- stop at the step that needs a decision, with everything the decision needs already gathered;
- leave a record of every system it read and every field it wrote.
Agents reach your systems through approved connectors — APIs, databases, applications — each with its own permissions.
The primitives it composes
An agent is a model, a set of approved skills, tools and a policy, applied to a scope.
Changes wait for human approval before they run.
Agents answer from your own regulations, documents and records, with the source attached.
What it runs on
Skills come from a signed vendor catalogue or your own uploads, and can be enabled or disabled per workspace.
Sign in with your own identity provider (OIDC with PKCE); no shipped default administrator password.
Every answer shows the exact commands that ran, their exit codes and output, per host.
The whole stack self-hosts with one command; an air-gap bundle ships every image.
Bring one question of your own.
Request a demo