I/O MeshRead a sample record

How I/O Mesh decides

I/O Mesh is a self-hosted Go binary that decides whether an agent may use a named tool. Your harness asks before each call. I/O Mesh checks the department policy and the pinned card, answers allow or deny, and writes an audit record either way.

What happens on one call

  1. Your harness sends one HTTP request with the caller's OIDC token, the tool, the department, the card, the data class, the purpose, the autonomy tier, and the spend.
  2. Exact denials run first: a missing identity, an unregistered tool, a known deny, or, without a valid approve receipt, a tool tagged as money movement, production change, or customer-data export.
  3. Then the department policy runs. A request can only resolve to a card that is pinned in the caller's own department.
  4. An allow returns an endpoint string and a process id. Your systems make the call. I/O Mesh does not fetch the endpoint or hold tool credentials.
  5. A deny is a plain deny. The reason goes on the audit record, not back to the caller.
HarnessI/O MeshToolone HTTP request01Exact denials02department policy03an endpoint string04Your systems make the callplain deny05The reason goes onthe audit record
HarnessI/O MeshToolone HTTP request01Exact denials02department policy03an endpoint string04Your systems make the callplain deny05The reason goes onthe audit record

Pinning a card

A card describes one specialist: the tools it may use, its autonomy tier, and where it runs. A card moves from draft to pinned one stage at a time. A signed harness score gates evaluation. The last step needs a single-use pin receipt signed by a named approver in that department. The person who proposed the card cannot sign it.

Signed audit heartbeats

Every decision writes one audit record. A heartbeat is a signed digest of the records in one window. It links to the heartbeat before it and is signed with an auditor key you hold.

Heartbeats help you spot a missing heartbeat or an altered record. They do not catch changes made by someone who holds your auditor key, and they are not a certification.

Revoke and offboard

Revoke moves one card to revoked. Offboard revokes every live card in a department. Both take effect on the next resolve. A caller that already holds an endpoint is outside that decision, so keep your own way to stop a running process.

What I/O Mesh is not

  • Not a proxy. It does not sit in the path of the tool call.
  • Not the model. You pick the model and run it.
  • Not an identity provider. Callers authenticate with your OIDC issuer.
  • Not a compliance certification.

Human-approval tools

  • A call to a tool in the human-approval class is refused unless it presents a valid single-use Ed25519 approve receipt.
  • The receipt is signed out of band by a person registered as an approver for that department, who is not the caller.
  • It is bound to the department, tool, tool class, and caller, and is valid only within the time window it states.
  • A receipt is accepted only on an L1 request. A request that asks for L2 is refused even with a valid receipt.
  • A valid receipt does not by itself allow the call. The call must still pass the remaining checks and your card and department policy, and any of them can deny it.
  • A receipt can allow at most one call. A receipt that has already been spent is refused.
  • An allow made with a receipt is written to the audit log with that receipt's identifier.
  • The receipt does not bind call arguments or amounts.

Where it runs

On Linux hosts you control. It listens on localhost by default. A network listener requires TLS and OIDC. The binary does not contact us: no licence check, no update check, and no telemetry.

DevelopersPlatform and SRESecurityPricing