Mindburn Labs
Founding Cohort
APACHE 2.0

Erster API-Aufruf in Minuten

HELM ist ein OpenAI-kompatibler Proxy. Ändern Sie eine Zeile — Ihre base_url. Jeder Tool Call wird durch das Guardian-Policy-Gate geleitet und erzeugt kryptographische Quittungen.

Auf GitHub ansehen Standard lesen
ARCHITECTURE

Governed Execution Pipeline

Every AI action flows through three trust boundaries — from proposal to cryptographic receipt. Click any stage to see its invariant and proof output.

External BoundaryAgent sends structured proposals — never raw execution
Kernel — Fail-ClosedEvery proposal is validated, policy-checked, then executed under governance
Proof SurfaceReceipts chain into an offline-verifiable evidence bundle
Hover or click any stage to see its invariant and proof output
ExternalKernel boundaryProof surface
Full architecture docs
INPUT → GOVERNANCE → PROOF

From proposed action to verifiable proof

HELM turns policy inputs into deterministic execution records and offline-verifiable evidence without letting raw tool calls slip around the boundary.

Fail-closed runtimeOffline verificationMCP-native
HELM OSS execution latticeTyped policies, regulations, and permissions flow into the HELM core engine, which executes inside a fail-closed sandbox and emits audit trails, cryptographic proofs, and deterministic action records.POLICY SURFACESPROOF SURFACESTYPED GUARDRAILSPOL-01PoliciesJURISDICTION RULESREG-02RegulationsHUMAN APPROVALSPERM-03PermissionsFAIL-CLOSED KERNELHELMCore execution authorityCPI • PEP • WASI SANDBOX • RECEIPTSAudit TrailsCrypto ProofsCompleted Actions
Inputs arrive as typed constraints, not raw execution.HELM enforces policy before any side-effect is allowed.Outputs exit as receipts and proofs that can be checked offline.
Input Surface

Policies, rules, approvals

Governance starts with typed constraints from policy files, regulatory rules, and human permission checkpoints.

Kernel Boundary

Deterministic execution

The core validates, policy-checks, executes in a sandbox, and fails closed whenever the boundary cannot prove it is safe.

Proof Surface

Artifacts anyone can inspect

Every action leaves an auditable trail: receipts, proof structures, and completed action records that survive outside the runtime.

SCHNELLSTART

In 5 Minuten deployen

HELM ist Framework-agnostisch. Wenn Ihr Code OpenAI, Anthropic oder eine kompatible API aufruft, brauchen Sie nur BASE_URL zu ändern.

1
Clone the repo
$ git clone https://github.com/Mindburn-Labs/helm-oss.git
2
Build the kernel
$ cd helm-oss && go build ./cmd/helm-proxy
3
Start the proxy
$ ./helm-proxy --config config.yaml
4
Point your agent
$ export OPENAI_BASE_URL=http://localhost:8420/v1
Full quickstart guide
MCP ECOSYSTEM

Works with every MCP client

HELM is MCP-native. Any client that speaks the Model Context Protocol can use HELM as its execution authority — no adapters, no shims.

FRAMEWORK COMPATIBILITY

Framework-agnostic by design

Change one URL — every framework gets receipts, policy enforcement, and offline verification.

Full compatibility matrix
OSS ↔ HELM-GRENZE

Was kostenlos ist. Was nicht. Warum.

OSS macht HELM zur Standard-Laufzeitgrenze. HELM Enterprise wird zum Standard-Betriebssystem für diese Grenze im großen Maßstab.

OPEN SOURCE

OSS Kernel

$0
  • Deterministische Proposal → Effect Pipeline mit Fail-Closed-Durchsetzung
  • Hash-verknüpfter Quittungs-DAG mit Session-verankerter Integrität
  • Gas-gemessene Ausführung mit konfigurierbaren Limits pro Aktion
  • Human-in-the-Loop-Checkpoints mit kryptographischer Attestierung
  • L1/L2/L3-Testvektoren mit deterministischer JSON-Ausgabe
ENTERPRISE

HELM Enterprise

Custom
  • Organisationsübergreifende Vertrauensdelegation mit widerrufbaren Credentials
  • Modell-Benchmarking und Kostenoptimierungsanalyse
  • Salesforce, SAP, ServiceNow native Integrationen
  • Multi-Cluster-Deployment mit zentralem Policy-Management
  • SOC 2, HIPAA und ISO 27001 Compliance-Automatisierung
  • TEE-gebundene Ausführung mit Silizium-Level-Manipulationsnachweis
FAQ

Common questions

Governance heute ausliefern

Repository klonen. Konformitätssuite ausführen. In Produktion bereitstellen.

Auf GitHub ansehen Vollständige Dokumentation