Runledge

Review access. Verify records.

Control workspace access, choose approval quorums and verify recorded identity, time and export integrity.

Get early access See pricing

Who can act, who approved it, and what you can prove.

Workspace controls and evidence, with explicit boundaries for data and provider execution.

Access

  • Scoped API keys. Workspace action API keys are stored hashed, scoped and revocable. Provider keys stay in your executor or, if you choose, in the credential broker, which agents never read.
  • Workspace permissions. Customer roles govern access to policies, approvals, reports and evidence exports.
  • Pre-flight policies. The database evaluates enabled rules. Your integration must honor the returned decision before executing.
  • Your quorum. Each rule sets 1–5 distinct reviewers, and whether they must be administrators. Overrides bind the exact proposal.

Evidence

  • Action attribution. Records include the submitted agent, system, status, timestamps and idempotency key.
  • Proposal-bound approval. Approval overrides bind the exact proposal and enabled rule snapshot, with stale checks before use.
  • Signed receipts. Public keys verify recorded identity and time. Receipts do not sign the action body or independently confirm a provider result.
  • Signed export manifests. Audit bundles include file hashes and a signed manifest of the exported snapshot, not a Merkle chain.

Data and execution

  • Record deduplication. Reusing an action idempotency key returns the original record. Provider effects need separate idempotency controls.
  • Persisted workspace data. Submitted action metadata, proposals, policies and audit records are stored. There is no zero-retention mode today.
  • Caller-owned recovery. Your executor handles provider retries, compensation and reconciliation. Runledge does not automatically undo writes.
  • Customer-hosted prerequisites. Container source and Kubernetes manifests require your own compatible backend, auth and deployment validation.

Security & compliance

Built for the people who say no.

Give security and risk teams inspectable policies, configurable approvals and verifiable records.

Container packaging

Build the runtime from source into your own registry. Kubernetes manifests and an MCP sidecar are included.

In-VPC deployment

Run the runtime inside your own network, connected to a backend you control.

Signed action receipts

Each recorded action gets a receipt signed with a published public key, so anyone can verify it.

Scoped API keys

Workspace keys are stored hashed, limited by scope, and can be revoked at any time.

Your first check takes minutes.
Your last incident, hopefully, never.

The Developer plan is open now. No waitlist, no card. Sign up, get an API key and make your first check.

Start free

Enterprise

Need a security review, self-hosted deployment or a custom contract? Tell us where to reach you.