Test the agents where they run,
and keep the people in the driving seat.

Why

A certified agent can still be catastrophic once it is strung into a workflow.

Agents are tested in labs, on the vendor's infrastructure, against scenarios the vendor saw. A workflow is several agents handing work to each other, under a company's own tools, data and limits, with people deciding in between. What matters there is behavioural: what the agents actually did, what they claimed, what it cost, which human saw which decision, and what happens when one parameter changes. That is only visible in situ, with a record, replay and someone reading the result.

The same discipline applies to us. Every number OneDroid publishes is listed with its evidence, and a verdict is never a score: passed, failed, errored or not applicable, per check, with the evidence attached.

For developers · in development · will be free and open source

One binary, on your machine, nothing leaves it.

Install one binary, run one command. It records every session of your coding agent (prompts, tool calls, results, model usage), writes the cost per model into each commit and sums it per branch and ticket, checks prompts and tool calls for credentials as they happen, and at the end of a session tells you what the agent actually did against what it said it did, with the receipt: files touched, commands and exit codes, tests that ran, test files edited, tools used, the diff, and beside every green line what the hooks could not see. The same binary runs a set of open basic checks against your agent, locally, with a pass list you can verify without an account.

Claude Code first, then Codex CLI and Gemini CLI. Open source under Apache 2.0, the basic checks included, with contributions by sign-off. Every open check is labelled a smoke test, not a certificate: a published check is something an agent can be tuned to pass, so it educates and catches the obvious, and nothing more is claimed for it.

What exists today: the open-source Argus runner (MIT) and a cost-per-commit tool we use ourselves. In development: the merged binary, the session verdict, the credential monitor and the open check set. It will be announced here and on the changelog when it can be installed.

For enterprises · in development · on your own estate

Every agent recorded, every workflow tested, nothing leaves your estate.

A recorder on every machine and agent runtime you run, feeding a store you own. Every prompt, tool call, result and model exchange, joined with the gateway's record of governed tool calls, on one id per agent, session and action. The full record of each session written to a private ledger you run, so that an agent cannot quietly rewrite its own history. One dashboard: which agents are alive, recording or silent; spend by team with budgets; anomalies against your own baselines; alerts under rules a person sets (token burn, rewrites, velocity, rejected submissions) with the time each took to reach a person; a pause button for any agent, the pause itself on the record; a queue where cases carry a label and only a named person moves them.

Tests run in situ: the runner on your estate, triggered from the Argus control plane, which receives verdicts, hashes and alerts and never the content. Workflow scenarios take several agents as the subject, replay a recorded run with one parameter changed, and ask whether the humans in the loop are doing the deciding: can every agent action be traced to a person, are decisions recorded as decisions, is a signal handled or treated as noise, can an action be appealed or reversed, is the delegation to agents explicit. The verdict on a workflow is a sentence, not a number: the agents are doing busy work, or they hold a key no human can see, stop or reverse, and here is the list.

What exists today: the Synapse gateway with its audit log, a recorder for Claude Code sessions in production on our own hubs, the Argus control plane and runner, and the ledger library. In development: the central store, the dashboards, the fleet alerts, the workflow scenarios and the replay. The first deployment is a lending workflow for a client, with its lender as the reader of the record. Pricing is by contact until that deployment is delivered.

The rules we build under

The human stays in the driving seat.

Three rules bind every product and every automation we build. The human stays in the driver's seat: nothing we ship offers to replace a person's judgement, test or decision, and nothing shifts responsibility to an AI. AI removes the work people do not want to do, not the people. And everything comes with a full record, replay, and a kill switch a person can pull at once, with the stop itself on the record.