Product
eMCP
vHSM
Garnet
Dyneemes
Buckypaper
Sylica
Nitride
Vault
SYLICA · CONFIDENTIAL VIRTUAL MACHINE FIRMWARE

Confidential computing has a gap: firmware you cannot verify.

Sylica closes it.

Enterprise firmware for confidential VMs on AMD SEV-SNP and Intel TDX. Reproducible builds mean your security team and auditors can verify it.

BUILT ON EDK2 · FULLY UEFI COMPATIBLE
AMD SEV-SNP · INTEL TDX · STANDARD VMS
REBUILDABLE FROM PUBLISHED SOURCE
SIGNED RELEASES · SBOM · SECURITY ADVISORIES

Minimize what must be trusted. Verify what was built. Verify what is running.

Minimize what must be trusted

Less firmware means less to attack, less to review and less to maintain. Sylica ships only what a confidential VM needs to boot.

SMALLER ATTACK SURFACE · SMALLER TCB

01
Verify what was built

Stop taking the vendor’s word. Your team or your auditor rebuilds the release from its published source and confirms it matches what runs in production.

SOURCE → BINARY, INDEPENDENTLY VERIFIED
02
Verify what is running

Keys and secrets are released only to a VM whose firmware measurement matches the published value. Attestation becomes a policy decision, not a leap of faith.

ATTESTATION → POLICY → KEY RELEASE
03

Why not just upstream OVMF?

REQUIREMENT
OVMF
SYLICA
Trusted computing base
General-purpose firmware with many optional features
Reduced to what secure VM boot requires: smaller attack surface, easier review
Reproducible builds
Possible, not a primary project goal
Core design principle: anyone can rebuild a release and compare it with what shipped
Measurements
Generated by the platform
Deterministic and documented: a known-good value for attestation policy
Supply chain
Build tools only
Signed releases, SBOM, provenance and documented advisories with every release
Lifecycle
Community releases, distribution dependent
Continuous CVE monitoring, validated releases, long-term support

One architecture, three targets

sylica-x86
STANDARD VMS

The same reduced, reproducible firmware for conventional x86 VMs, so one firmware standard covers the whole fleet.

sylica-sev
AMD SEV-SNP

The firmware measurement is part of the SEV-SNP attestation report, so the VM’s start state can be checked before it receives a key.

sylica-tdx
INTEL TDX

The firmware runs inside the Trust Domain and is part of its measured start state, covered by the same check.

Where teams use it

01
Prove firmware integrity in an audit

Signed releases, SBOMs and documented measurements turn “we trust our provider” into evidence an auditor can check. Built for the CISO who owns the trust chain.

02
Keep the root of trust under your control

Cloud-provider firmware is a dependency you cannot inspect. Sylica gives the CIO one enterprise-controlled firmware standard across every cloud and on-premises, and strengthens digital sovereignty.

03
Regulated workloads

Finance, healthcare, government and defence run sensitive data on confidential VMs with a firmware foundation they can reproduce and defend to a regulator.

04
Confidential AI

Models and training data are only as protected as the firmware beneath them. Verify it before the first key is released.

05
Policy-based key release

Release keys only to VMs whose firmware measurement matches the published value. Zero trust, down to the first code that runs.

06
Cloud and sovereign cloud providers

Offer confidential VMs and multi-tenant confidential Kubernetes on firmware your customers can independently verify, backed by enterprise advisories and long-term supported releases.

Get started

Verify the firmware. Then trust the workload.

Security begins before the operating system starts. Talk to us about bringing Sylica to your SEV-SNP and TDX fleet: enterprise support, security lifecycle, attestation policy and a verification walkthrough with your security team.

Certifications & security
Certified ISO/IEC 27001
IT Security made in Germany — TeleTrusT