The OS for coding agents — governed

Let agents move fast. Keep your org in control.

Everything in the cockpit, plus governance, tamper-evident audit, security enforced at the edge, and coordination across agents. Self-hostable. You always bring your own agents — we never resell tokens.

The control-plane spine is real and self-hostable today; some surfaces are still maturing. Each capability below names the subsystem it maps to so you can audit the claim.

Governance

Approvals, policy, and an audit chain you can prove.

Approvals on risky actions

Gate the actions you decide are dangerous. An approval that times out resolves to a deny — it fails closed, never open.

governance · approval-gateway

Deny-biased policy engine

Policy is evaluated before an agent acts. Forbidden auth and security paths resolve to deny by default, so the safe answer is the default answer.

governance · policy/engine

Tamper-evident audit chain

Governed decisions are sealed into a SHA-256 Merkle chain. Any entry's hash is verifiable, so a quiet rewrite of the record is detectable rather than silent.

governance · audit (merkle-verifier)

Security below the model

Trust is enforced at the edge, not in a prompt.

Authorization at the edge

Trust is enforced at the edge instead of in a prompt. An external authorization (Envoy ext-authz) check admits or rejects traffic ahead of the control plane.

network · ext-authz + envoy-config

Threat detection on agent traffic

Network and admission events feed detection rules (XDR) so anomalous agent or connector behavior is surfaced for review rather than silently allowed.

network · xdr/detections

Signed-envelope ingress

Inbound A2A envelopes are treated as untrusted until signature, identity, and policy are verified at the edge — designed to check HMAC and Ed25519 signatures before admission.

interop · signed-ingress-gate

Coordination & control

Work-locks, coherence, SSO, and self-host.

Work-locks

Work-locks are designed to keep two agents from editing the same file at once. Locks are held, reaped on expiry, and overlaps are detected before work collides.

coordination · locks

Coherence checks

Semantic checks catch the conflicts git can't see — a lock without a task, overlapping active locks — and escalate them.

coordination · coherence

SSO, seats & self-host

Single sign-on and per-seat management for your org, and the option to run the entire control plane inside your own infrastructure.

deploy · self-host stack

Talk to the team.

Tell us your team size, what you want to coordinate, and your governance requirements. The founders reply directly.

By submitting, you agree to our Privacy Policy. We'll only email you about this request.

Prefer email? Reach us at founders@recoder.xyz.