Enclave Runtime

How enclave initialisation works

When Almure launches a workload, the Runtime performs a cryptographic measurement of the entire execution context before the first instruction executes. This measurement — the mrenclave hash — captures the workload binary, configuration, runtime libraries, and initial memory state. Any modification to any of these components produces a different measurement, making it impossible to silently substitute code or data.

The hardware-enforced isolation means the host OS, hypervisor, and cloud provider's management plane have no read or write access to the enclave's memory region. Memory pages are encrypted by the CPU's memory-encryption engine before they leave the die, using ephemeral keys that exist only inside the hardware and are never exposed to software.

Workload packaging

The Almure Runtime accepts standard Docker-compatible containers without code modification. You package your workload as you normally would, configure the enclave policy (memory limit, attestation requirements, sealing scope), and pass it to the Almure SDK. The Runtime handles:

• Loading the container filesystem into the enclave's measured memory region
• Establishing encrypted communication channels for input data and result output
• Injecting sealed key material at runtime for data decryption
• Generating the attestation report on workload completion

Enclave launch sequence

The following output is representative of an Almure enclave launch using the CLI:

Supported hardware

Almure is hardware-agnostic at the API level. The runtime adapts to the underlying TEE implementation: