Your model can change. Your rules should not.
Keep workspace rules and approval decisions outside the model’s reasoning loop through REST or OAuth MCP.

About Runledge
Runledge checks proposed agent actions against your rules, routes exceptions to human reviewers and records reported outcomes.
Why we exist
Moving from an answer to an action changes everything. A write can change a customer account, a payment, a cloud resource or a physical process. Better reasoning alone does not define who may act, what needs approval or how the business reviews the result.
Runledge brings action policies, human decisions and recorded outcomes into a shared workspace—with REST and MCP access for agents, and clear reporting for the people responsible.
Keep workspace rules and approval decisions outside the model’s reasoning loop through REST or OAuth MCP.
Bind approvals to exact proposals and versioned rules before your integration executes an allowed action.
Give engineering action records, finance departmental reports and auditors verifiable identity-and-time receipts.
The platform question
Model providers have the talent and resources to build governance. We don’t base our case on what they cannot do. We base it on what customers need: a consistent place for policies, approvals and business records as their models and agent frameworks change.
Our defensibility must be earned through integration depth, useful policy workflows, durable customer records and measurable operational value. Today’s capabilities are a foundation—not a claim that the moat is already won.
Competitive scorecard
Choose the layer you’re evaluating. Compare what it is built to do—not a wall of checkmarks.
Reasoning, tool use and agent development
Your models will change. Your business rules and audit trail shouldn’t. Runledge sits between any model and your tools.
Deterministic pre-flight checks
Database-evaluated workspace rules and versioned YAML. The caller must honor the decision before executing.
Proposal-bound, configurable quorums
Each rule sets how many distinct reviewers approve (1–5) and whether they must be administrators; overrides bind the exact proposal and enabled rule snapshot.
Signed receipts & export manifests
Public verification keys support integrity checks. Receipts cover recorded identity and time, not action contents or independently verified outcomes.
Departmental showback
Reported model cost, estimated labor value and risk exposure are separated. Shared platform cost is counted once.
Customer-owned execution
Your executor runs allowed calls and handles recovery, or the optional broker holds credentials and calls their bound provider host.
Container source packaging
Docker and Kubernetes definitions include an MCP transport sidecar. A customer-operated backend/auth service is required; this is not a validated air-gapped appliance.
Keep the model platform for reasoning. Add Runledge when a separate policy, approval and business record is useful.
The Developer plan is open now. No waitlist, no card. Sign up, get an API key and make your first check.
Start freeEnterprise
Need a security review, self-hosted deployment or a custom contract? Tell us where to reach you.