Mindburn Labs
Founding Cohort
APACHE 2.0

Primera llamada API en minutos

HELM es un proxy compatible con OpenAI. Cambie una línea — su base_url.

Ver en GitHub Leer el estándar
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.

INICIO RÁPIDO

Despliegue en 5 minutos

HELM es agnóstico de framework.

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 ↔ LÍMITE HELM

Qué es gratis. Qué no. Por qué.

OSS hace de HELM el límite de runtime por defecto. HELM Enterprise se convierte en el sistema operativo por defecto para ese límite a escala.

OPEN SOURCE

OSS Kernel

$0
  • Pipeline determinista de propuesta → efecto con aplicación fail-closed
  • DAG de recibos hash-linked con integridad anclada a sesión
  • Ejecución medida por gas con límites configurables por acción
  • Checkpoints human-in-the-loop con atestación criptográfica
  • Vectores de prueba L1/L2/L3 con salida JSON determinista
ENTERPRISE

HELM Enterprise

Custom
  • Delegación de confianza cross-org con credenciales revocables
  • Benchmarking de modelos y analítica de optimización de costos
  • Integraciones nativas Salesforce, SAP, ServiceNow
  • Despliegue multi-cluster con gestión de políticas centralizada
  • Automatización de cumplimiento SOC 2, HIPAA e ISO 27001
  • Ejecución vinculada a TEE con evidencia de manipulación a nivel de silicio
FAQ

Common questions

Despliegue gobernanza hoy

Clonar el repo. Ejecutar la suite de conformidad. Desplegar en producción.

Ver en GitHub Documentación completa