Skip to main content

Local Enclave Staging

In SKR mode, production Kibo workloads run inside Intel TDX or AMD SEV-SNP enclaves with hardware-attested identity. For day-to-day development and CI against that mode, you do not want to call production endpoints (network latency, real charges, audit-log pollution) and you do not want to require every developer's laptop to have TEE-capable silicon. The right pattern is a local stand-in: the same SDK shape, the same wire contract, but backed by a local mock that simulates the TEE behaviour deterministically.

:::info Canonical command surface The local-enclave development substrate — the local mock packaging, container image, attestation-issuer endpoint, and audit-ledger-compatible streaming surface — is driven from the CLI. For the canonical command surface, see the CLI reference; for local-development specifics beyond this page, surface your needs to your account team. :::

What the local stand-in is for​

The platform's local-enclave pattern is designed to let you exercise the SDK contract, policy logic, and audit-ledger handling locally without needing TEE hardware. The local mock provides:

  • A local Kibo enclave that performs encryption/decryption with a deterministic in-memory key store
  • A local Gate that issues mock JWTs with a deterministic signing key
  • Mock TEE attestation documents that pass verification against a test root certificate
  • Full audit ledger emission compatible with the offline verification tool
SDK callslocal endpointsLocal stand-incontainerised, ephemeral by defaultLocal Kibo enclavedeterministic in-memory key storeLocal Gatemock JWTs, deterministic signing keyMock TEE attestationverifies against a test root certificateAudit ledger emissioncompatible with offline verificationOffline verificationsame tool as production
The SDK exercises the same calls against the local stand-in, and its ledger is verified with the tool used for production ledgers.

What the local stand-in is not​

A local mock is for development and CI. It is not a production-substitute. The local enclave:

  • Does not provide real TEE memory protection (it runs in a regular container)
  • Does not provide real hardware attestation (mock attestations are cryptographically distinct from production attestations)
  • Does not protect against the full production threat model

The point is to let you exercise the SDK contract, policy logic, and audit-ledger handling without needing TEE hardware locally. Production deployment runs against the real enclaves with the real attestation chain.

Operating pattern​

The operating pattern:

  1. Start the local stand-in (containerised, ephemeral by default)
  2. Point the SDK at the local endpoints via configuration
  3. Exercise tests against the local stand-in — same SDK calls, same wire contract, deterministic outcomes
  4. Verify the local audit ledger using the same offline verification tool that operates against production ledgers
  5. Tear down on completion

In CI (GitHub Actions, GitLab CI, etc.), the pattern is identical: bring up the local stand-in as a job-scoped service, run integration tests against it, verify the ledger, stop on completion.

Next​