Governed execution infrastructure

The governed execution layer for AI agents, workflows and software.

RBEK controls how software and AI-driven workflows reach providers, execute capabilities, enforce policy and produce verifiable execution evidence.

Get Started How RBEK Works

Install stable CLI 0.2.0

curl -fsSL https://releases.rbekplatform.com/cli/stable/install.sh | bash

AI Agent / Software / Workflow

↓

RBEK

↓

Policy

Provider

Evidence

↓

Governed Execution

Why RBEK

Execution needs a control layer.

AI agents and software workflows can decide what they want to do. RBEK governs whether and how those actions are allowed to reach real systems.

Policy before execution

Define which providers and capabilities are allowed before execution can proceed.

Controlled providers

Route execution through explicit, registered provider boundaries instead of uncontrolled calls.

Evidence by default

Generate plans, gates, execution evidence, receipts and certification artifacts around execution.

How it works

From intent to governed execution.

Define the workflow

Describe the capability to execute and the provider responsible for that step.

Apply policy

RBEK checks whether the requested provider and capability are explicitly allowed.

Plan and gate

RBEK builds an execution plan, performs a dry run and evaluates the execution gate.

Execute through providers

Approved execution reaches registered provider boundaries instead of uncontrolled direct calls.

Generate evidence

Execution produces verifiable artifacts including evidence, receipt and certification.

Developer quickstart

Run your first governed execution in under 5 minutes.

Install RBEK, create a project, execute through an explicit governed path, then inspect the evidence produced around that execution.

Install RBEK

Install the current stable CLI directly from the official release channel.

Install

curl -fsSL https://releases.rbekplatform.com/cli/stable/install.sh | bash

Create your first project

Generate a local project containing a provider, workflow, policy and adapter SDK.

Create project

rbek-cli --output json quickstart customer-project --target ./my-rbek-project

Run governed execution

Execution is explicit. RBEK plans the execution, evaluates the gate, executes the provider and produces a verifiable receipt.

Execute

rbek-cli --output json quickstart customer-project --target ./executed-rbek-project --execute --acknowledgement I_ACKNOWLEDGE_RBEK_LOCAL_CONTROLLED_EXECUTION --message "Hello from RBEK"

Inspect the evidence

Review the artifacts produced around the governed execution.

Evidence

ls -la executed-rbek-project/.rbek/evidence/

Expected execution result

Plan READY

Gate AUTHORIZED

Execution PASS

Receipt PASS

Certification CERTIFIED

Evidence created by the execution

execution-plan.json dry-run.json execution-gate.json execution.json execution-receipt.json promoted-execution-certification.json

Telemetry is opt-in. It is disabled by default, does not use a persistent user identifier and can be enabled or disabled locally at any time.

Execution evidence

Know what executed, why it was allowed, and what happened.

RBEK produces execution artifacts around the complete governed execution lifecycle.

01 execution-plan.json

02 dry-run.json

03 execution-gate.json

04 execution.json

05 execution-receipt.json

06 promoted-execution-certification.json

Developer first

Built to be understood from the terminal.

RBEK exposes the execution lifecycle directly through the CLI so developers can inspect providers, workflow rules, policy decisions and execution evidence without depending on an opaque control plane.

Explicit execution

Execution requires an intentional command and governed provider path.

Local by default

The public quickstart demonstrates controlled local execution without requiring external APIs.

Inspectable artifacts

Workflow, policy, plans, receipts and evidence remain visible to the developer.

Start building

Add governance between intent and execution.

Install the current stable RBEK CLI and run the first governed execution locally.

Get Started

Real AI agent · Real Internet API

See RBEK govern a real AI agent.

A real OpenAI agent requests an external action. RBEK evaluates the policy, executes a real third-party HTTPS API call through a governed boundary, and produces a verifiable receipt and certification.

See the governed execution →

VERIFIED GOVERNED EXECUTION

REAL_AI_AGENT PASS

POLICY_AUTHORIZATION PASS

THIRD_PARTY_HTTPS PASS

EXECUTION_RECEIPT VALID

CERTIFICATION VALID

Developer proof

Run RBEK in seconds.

No API key is required for the default proof. See RBEK deny an unauthorized action, allow an authorized action and produce inspectable execution evidence.

Run the demo View GitHub Open in Codespaces

✓ Deterministic Execution Verified

Agent requests unauthorized action
        ↓
      DENY
        ↓
External execution = NO

Agent requests authorized action
        ↓
      ALLOW
        ↓
Governed path = PASS
Gate = AUTHORIZED
        ↓
Evidence

Zero-key proof

Real policy. Real evidence. No API key.

curl -fsSL https://releases.rbekplatform.com/cli/stable/install.sh | bash && \
curl -fsSL https://raw.githubusercontent.com/rbekplatform/rbek/main/examples/real-governed-agent/demo.sh | bash

Model inference: not required · Network execution performed: NO · RBEK policy enforcement: REAL · RBEK evidence: REAL

Live AI + Internet

OpenAI agent. Governed external action.

OpenAI agent
     ↓
weather.current
     ↓
RBEK policy admission
     ↓
controlled external execution
     ↓
Open-Meteo
     ↓
receipt + certification

The live example uses real model inference and a real Open-Meteo external action through the RBEK governed execution boundary.

See the live governed execution →

Public GitHub Actions installs the public CLI, runs the offline proof twice and verifies deterministic evidence identity.