for your security team

Trust the hardware.Not the host.

eCora runs your workload in encrypted memory on verified hardware, and only releases the keys once the hardware proves what it is running. This page covers the mechanism, what you still have to trust, and what is not covered.

how it runs

What's Actually Happening at Runtime

CPU-Level Memory Encryption

AMD SEV-SNP encrypts the guest's memory at the CPU level, so the hypervisor and host administrators can't read it.
technical details
Memory encryption: AMD SEV-SNP · Launch measurement checked at attestation · Each workload runs as its own guest VM

Hardware Root of Trust

The key broker releases an image key only to a guest whose hardware evidence matches expected values.
technical details
Evidence: AMD SEV-SNP report or AWS NitroTPM PCRs · Checked against reference values before key release

Scan, Then Encrypt

Images you publish are scanned for vulnerabilities, then encrypted before delivery.
technical details
Quarantine registry · Vulnerability scan · OCI image encryption · Promotion to the deployable registry

Audit Records

Control-plane actions are recorded in an append-only audit log.
technical details
Storage: Append-only records
attestation and access

How trust is established, and how access ends.

Infrastructure

AMD SEV-SNP · AWS NitroTPM attestation
Confidential guest VMs attest their hardware and launch measurement before they receive keys or identity. The host is not trusted; the attestation is.

Software

AMD SEV-SNP · Hardware-attested workload identity
Each workload runs in a CPU-encrypted guest VM and receives its identity only after the guest passes attestation. Images are scanned and then encrypted, and their keys are released only to attested guests.

Grants and revocation

Per-workload grants · Attestation-gated key release
Vendors grant a customer access to a workload and can revoke the grant, or cap its instances and set an expiry. A revoked customer can't start or scale new instances, and running instances lose their platform identity when it next renews.
threat coverage

What each protection defends against.

Threat
Result
How
Host or cloud administrator reads memory
Protected
The processor encrypts the guest's memory, so the host cannot read it.
Someone copies the delivered image
Protected
The image is encrypted, and keys go only to hardware that passes attestation.
Software starts on unverified or modified hardware
Blocked
Keys are released only if the hardware evidence matches the expected values.
A revoked customer starts or scales new instances
Blocked
Access is checked before keys are released, and running instances lose their platform identity when it next renews.
Hardware side-channel or physical attacks
Not fully covered
No hardware is a guarantee against every attacker. See what you still have to trust, below.
trust and limits

What you still have to trust.

What eCora holds

eCora scans and encrypts the images you publish, and runs the key service that releases keys. Keys go only to hardware whose attestation matches the expected values.

What your customer gets

Their data stays in their own cloud account. They can check hardware-signed evidence of what is running, and the host administrators cannot read the workload's memory.

Who you still trust

Hardware protection narrows who you have to trust, but does not remove trust. You rely on AMD for the processor and its firmware, on AWS for the attestation chain (and on Microsoft for workloads that run on Azure), and on eCora for the key service.

What is not covered

Researchers have published attacks on confidential computing hardware, so no hardware is a guarantee against every attacker. Workloads run on AWS today, with Azure in development. On-premises and edge environments are not supported.
compatibility

What it runs on today.

Deployment Types

  • Containerised workloads
  • Existing applications
  • AI and ML systems
  • Data pipelines
  • Web services and APIs
  • Microservices

Where workloads run

  • AWS
  • Azure (in development)

Hardware Support

  • AMD SEV-SNP
  • AWS NitroTPM attestation
  • Additional TEE architectures planned
how this differs

What eCora adds to other approaches.

Software-only controls and plain confidential VMs each cover part of the problem. eCora builds on the hardware protection and adds what a software vendor needs to ship into customer environments.

Capability
Software-only controls
Confidential VM on its own
eCora
Memory encrypted while in use
No
Yes
Yes, at the CPU level
Keys released only to verified hardware
No — policy and certificate based
You build it yourself
Built in
Sealed delivery to each customer
No
Not provided
Image encrypted before delivery
Per-customer limits, expiry and revoke
No
Not provided
Yes
Evidence your customer can check
Logs and reports
Raw evidence you must interpret
Hardware-signed evidence of what is running

Questions from your security team?

Tell us what they need to see. We review every request personally and will be in touch within two business days.

Status: workloads run on AMD SEV-SNP hardware on AWS, with Azure in development.