Mindburn Labs
Founding Cohort
APACHE 2.0

Primeira chamada API em minutos

HELM é um proxy compatível com OpenAI. Mude uma linha — seu base_url — e cada chamada de ferramenta é governada, recebida e verificável.

Ver no GitHub Ler o padrão
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.

INÍCIO RÁPIDO

Implante em 5 minutos

HELM é 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 ↔ FRONTEIRA HELM

O que é grátis. O que não é. Por quê.

O OSS torna o HELM a fronteira de runtime padrão. O HELM Enterprise se torna o sistema operacional padrão para essa fronteira em escala.

OPEN SOURCE

OSS Kernel

$0
  • Pipeline determinístico de proposta → efeito com aplicação fail-closed
  • DAG de recibos hash-linked com integridade ancorada à sessão
  • Execução medida por gas com limites configuráveis por ação
  • Checkpoints human-in-the-loop com atestação criptográfica
  • Vetores de teste L1/L2/L3 com saída JSON determinística
ENTERPRISE

HELM Enterprise

Custom
  • Delegação de confiança cross-org com credenciais revogáveis
  • Benchmarking de modelos e analytics de otimização de custos
  • Integrações nativas Salesforce, SAP, ServiceNow
  • Implantação multi-cluster com gestão de políticas centralizada
  • Automação de conformidade SOC 2, HIPAA e ISO 27001
  • Execução vinculada a TEE com evidência de adulteração em nível de silício
FAQ

Common questions

Implante governança hoje

Clone o repo. Execute a suite de conformidade. Implante em produção.

Ver no GitHub Documentação completa