Mindburn Labs
Founding Cohort
APACHE 2.0

몇 분 안에 첫 API 호출

HELM은 OpenAI 호환 프록시입니다. 한 줄만 변경하면 — base_url — 모든 도구 호출이 통제, 수령, 검증됩니다.

GitHub에서 보기 표준 읽기
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.

빠른 시작

5분 안에 배포

HELM은 프레임워크에 구애받지 않습니다.

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 경계

무료인 것. 아닌 것. 이유.

OSS는 HELM을 기본 런타임 경계로 만듭니다. HELM Enterprise는 대규모에서 해당 경계의 기본 운영 체제가 됩니다.

OPEN SOURCE

OSS Kernel

$0
  • 결정론적 제안 → 효과 파이프라인, 실패 시 차단 강제
  • 세션 앵커드 무결성을 갖춘 해시 링크 영수증 DAG
  • 작업당 구성 가능한 한도와 가스 미터링 실행
  • 암호화 증명이 포함된 휴먼 인 더 루프 체크포인트
  • 결정론적 JSON 출력의 L1/L2/L3 테스트 벡터
ENTERPRISE

HELM Enterprise

Custom
  • 취소 가능한 자격 증명의 교차 조직 신뢰 위임
  • 모델 벤치마킹 및 비용 최적화 분석
  • Salesforce, SAP, ServiceNow 네이티브 통합
  • 중앙 집중 정책 관리의 멀티 클러스터 배포
  • SOC 2, HIPAA, ISO 27001 컴플라이언스 자동화
  • 실리콘 수준 위변조 증거를 포함한 TEE 바인딩 실행
FAQ

Common questions

지금 거버넌스를 배포하세요

저장소를 클론하세요. 적합성 스위트를 실행하세요. 프로덕션에 배포하세요.

GitHub에서 보기 전체 문서