Railpane
ENTERPRISE CONTROL PLANE FOR AUTONOMOUS AGENTS

Control what agents can do before they do it. Prove why they were allowed.

Railpane is authorization, runtime security, identity, and governance infrastructure for autonomous AI agents — coding, DevOps, MCP, infrastructure, financial, browser, and support agents.

Core promise: control what autonomous agents can do before they do it, prove why they were allowed to do it, and retain verifiable evidence of what actually happened.
coding agentsDevOps agentsMCP agentsinfra agentsfinancial agentsbrowser agents

Sign up for the waitlist

Pilots are capped cohorts. Leave your work email and we will reach out when your use case opens — starting with coding and DevOps agents.

No spam. One email when pilots open, one when generally available. Unsubscribe anytime.

What Railpane is

Authorization gateway

Every consequential action passes through identity, delegated authority, policy, approval, guarded execution, and tamper-evident receipts:

Agent → Railpane → Policy / Authority / Approvals → Tool / MCP / API

ALLOWDENYREQUIRE_APPROVALALLOW_WITH_CONSTRAINTS

Not another agent

Railpane is not an LLM, a chat UI, a coding agent, a generic agent framework, an orchestrator, a mere observability dashboard, or a wrapper script. The commercial value is the central trust/control plane connecting the open-source engines.

Deterministic policy before probabilistic judgment. LLM output never silently overrides DENY. Fail closed.

Architecture

RAILPANE Identity Plane │ Delegated Authority │ Session / Task Context │ ▼ Authorization Gateway │ Policy Engine (Seal) │ ┌────────────────┼────────────────┐ │ │ │ ▼ ▼ ▼ Paldron Rift MCP / APIs Runtime Semantic External Enforcement Review Actions │ │ │ └────────────────┼────────────────┘ │ Decision Engine ALLOW / DENY / REQUIRE_APPROVAL │ Action Binding → Credential Broker → Execute │ Annalist evidence + Signed Receipt → Console

Open-source engines

Railpane is built on mature open-source components with distinct responsibilities. Each stays useful standalone. Railpane is the control plane that connects them.

SettleAgent — authorization backend

Identity, principals, orgs, ALLOW/DENY/REQUIRE_APPROVAL, transactions, saga compensation, MCP proxy, receipts, Postgres.

Docs & usage →

Paldron — runtime enforcement

Command gate, filesystem/network/binary policy, Landlock/seccomp sandbox, fail-closed. Exits 0 allow, 2 deny, 1 broken.

Docs & usage →

Rift — semantic code review

Git diff analysis, symbol changes, importance scoring, task-vs-change verification, CI gates. Deterministic, evidence-first.

Docs & usage →

Annalist — execution evidence

Flight recorder for agent runs: observed changes, content-addressed versions, diffs, rewind, portable bundles.

Docs & usage →

Seal — policy compiler

One seal.toml compiles to Annalist + Paldron policies so they cannot drift apart. Stamp + verify receipts.

Docs & usage →

Ballast — parallel workspaces

Tasks → isolated git worktrees → one-command runners → changesets → overlap checks → approve/integrate.

Docs & usage →

Reeve → reference agent / test client (not Railpane). Full docs →

Demo: task-scope violation

Task: "Increase session timeout from 30 to 60 minutes."

  1. Agent authenticates to Railpane. Session tied to task.
  2. Agent changes timeout file — and also touches auth + payments + schema.
  3. Paldron applies host restrictions. Annalist records the run.
  4. Rift evaluates changes, detects scope mismatch + high-risk edits.
  5. Railpane converts evidence to REQUIRE_APPROVAL.
  6. Human sees agent, task, diff, Rift evidence, policy rule — approves or rejects.
  7. Approval binds to the exact action digest. Credential broker issues scoped temp creds.
  8. Signed receipt links Rift evidence + Annalist session + policy version + approval + result.

OSS vs commercial

Open source (stays useful)

Paldron, Rift, Annalist, Seal, SettleAgent local runtime, Ballast local orchestration, SDKs/protocols. No crippling.

Railpane commercial

Orgs, fleet, identity, delegation, credential broker, policy distribution/inheritance/rollback/simulation, central approvals (Slack/Teams), SSO/OIDC/SCIM, signed provenance, SIEM, retention, compliance exports, MCP gateway, hosted plane, anomaly detection, SLA.

Get access

Design partners: tell us what your agents spend and touch. If it is a fit, first governed action live within two weeks.