Choose a plan for your action volume. Pre-flight policies, approvals and signed records are available across plans.
Everything you need to build and ship your first agent.
For teams putting agents in front of customers.
For agents that run the business, around the clock.
In your VPC, on your terms, under your controls.
Need more actions? Team and Growth never stop at the limit: extra actions are $0.40 per 1,000. Change plans any month.
Over your allowance? $0.40 per 1,000 extra actions on Team and Growth. No hard stop.
Over the 10,000 free actions
Within allowance
Within allowance
Estimate only, before taxes. Switch plans any month. Above 10M actions or need in-VPC? Talk to us about Enterprise.
Enterprise
The same pre-execution runtime, deployed where your data lives, backed by a contract your risk team signs off on.
Build the Runledge runtime from source into your own container registry and run it in your VPC or Kubernetes cluster, with an MCP sidecar beside it.
Uptime, support response and escalation terms written into your contract, sized to the workflows your agents actually run.
High-risk actions wait until the approval quorum you configure signs off on the exact proposal. Approval decisions are recorded; action receipts attest to recorded identity and time.
Pricing is set per contract. Tell us the workflows and volume you have in mind.
Keep your framework and models. Runledge evaluates proposed tool calls, coordinates human approvals and records outcomes through REST or OAuth MCP. Your executor honors those decisions and calls the provider.
Runledge stores submitted action metadata, approval proposals, policies and audit records. It does not need your model prompts or provider credentials for pre-flight checks. Send only the fields needed for your policies; zero-retention processing is not currently available.
No. Your executor owns provider calls, retries, compensation and reconciliation. Runledge records the outcomes you report; it does not automatically roll back writes or guarantee exactly-once provider effects.
Create an account, confirm your email and create a workspace. Configure a policy, then use a workspace API key for REST or authorize a remote MCP client through OAuth. Check before calling your provider and record the confirmed outcome afterward. No enabled rules means proposals are allowed, so configure your policies first.
The source includes a container build and Kubernetes manifests with an MCP transport sidecar. Customer-hosted deployment requires a compatible, independently operated backend and auth service, runtime secrets and release validation. It is not currently an air-gapped appliance or a published container image.
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.