Platform

The Almure Enclave Platform

Three interlocking layers — Runtime, Attestation, Key Management — delivering a complete confidential-computing substrate for production AI workloads.

Request Access Read the Docs

Architecture

Three interlocking layers

Each layer addresses a distinct point in the workload lifecycle. Together they provide end-to-end confidentiality from the first byte entering the enclave to the last entry written to the attestation log — with hardware-grounded evidence at every step.

01

Enclave Runtime

The Almure Runtime loads your workload into a hardware-verified memory region, measures every byte before execution begins, and maintains the enclave boundary throughout the workload lifecycle. It supports Docker-compatible packaging with no code modification required. The runtime abstracts across Intel TDX, AMD SEV-SNP, and AWS Nitro Enclaves — presenting a unified execution API regardless of the underlying TEE implementation. Host-OS inspection is architecturally impossible: memory encryption happens at the CPU memory controller, not in software.

Enclave Runtime deep dive
02

Cryptographic Attestation

Every execution produces a hardware-signed attestation report containing the measurement hash (mrenclave), code version, and enclave configuration. The attestation chain runs from CPU firmware through the signing key service to a verifiable report your compliance team can treat as audit evidence. Almure maps each attestation record to a structured log entry with timestamp, workload ID, and policy version — making it straightforward to answer "what ran, on what data, inside what boundary, at what time" for any regulatory inspection.

Attestation deep dive
03

Sealed Key Lifecycle

Keys are derived inside the enclave during initialisation using the hardware's root sealing key and never exist in the clear outside the boundary. Sealing policy can be configured as measurement-bound (only the exact code version can unseal) or signer-bound (any version from the same signing key). Automatic rotation on a configurable schedule, HSM integration for the root of trust, and scoped key identities per workload mean that key compromise scenarios are contained by construction rather than by policy.

Key Management deep dive

Ready to evaluate the platform?

We scope each pilot to your specific workload and compliance requirements. Start with a 30-minute technical call.

Request Access Quickstart Guide