Enigma Hub
Execution Layer
- • Hardware execution infrastructure
- • Final arbitration and execution adjudication
- • Hardware-enforced execution boundary
- • The only layer with execution authority
Execution System
A Hardware-Enforced Execution Control System
Execution is not trusted in software.
It is enforced at a physical boundary.
Execution is enforced by system architecture.
System Components
Execution authority is physically separated across independent layers.
A physical trust boundary separates decision from execution.
Bletchley
Decision Layer
- • Cloud decision and governance layer
- • Policy, risk, and approval evaluation
- • Dual control path for execution gating
- • Has no execution authority
Enigma Pass Key
Identity Layer
- • Identity and authorization anchor
- • Defines who can initiate execution
- • Intent-bound initiation for high-risk operations
- • Cannot trigger execution
Deployment Models
Different deployment forms. Same execution model.
Security properties remain identical across all deployments.
Enigma Hub Mini
Individual and small teams
Local execution with lightweight policy control.
Enigma Hub Pro
Production environments
Multi-layer policy and automation-ready execution control.
Enigma Hub Enterprise
Private infrastructure organizations
On-prem deployment and cluster-level execution control.
Execution Definition
Execution is not a feature.
It is not a product.
It is a system property.