TPM HSM is an open-source HSM platform that gives you hardware-backed key management, multi-party signing, remote attestation, and complete PKI — using the TPM 2.0 chip already in your machine.
Hardware-grade key protection with the flexibility of software. No proprietary hardware required.
Private keys are generated inside or securely imported into the TPM. Keys never leave the chip in plaintext. Client-side wrapping with RSA-OAEP + AES-128-CFB ensures keys are encrypted before they ever touch the network.
TPM PolicySigned and PolicyAuthorize enforce who can sign. Require a specific YubiKey, a file key, or multi-party approval. The TPM itself refuses unauthorized signing — even if the server is compromised.
Create M-of-N threshold keys stored in the TPM. Signing requires approval from a quorum of key holders. Each member authenticates with their own YubiKey or file key. No single person can sign alone.
Verify that a TPM is genuine hardware — not emulated or simulated. EK certificate chain validation against manufacturer root CAs (Intel, Infineon, STMicro, Nuvoton, AMD). PCR quotes prove system integrity.
Use YubiKeys as hardware-bound policy signers. Verify keys were generated on-device via Yubico attestation chain. Sign TPM operations with YubiKey PIV slots for two-factor hardware authentication.
Register public keys and create verification certificates. Build cryptographic trust graphs with hop-distance visualization. All trust validation is client-side — the server is a dumb store.
Store certificates and chains. Generate PKCS#10 CSRs from TPM-protected keys with full subject and SAN support. Associate certificates with HSM keys. Build a complete public key infrastructure.
Generate a self-contained pre-wrap script that creates and encrypts keys without any TPM or network access. Transfer the wrapped key later for import. Secure key provisioning for disconnected environments.
Native desktop app (Windows, macOS, Linux) with a modern dark-themed UI. Browser-based web mode with client-side crypto. Same features everywhere — choose your deployment model.
From code signing to IoT device identity, TPM HSM covers the full spectrum of HSM and PKI use cases.
Sign software releases, container images, and firmware with TPM-protected keys. Require multi-party approval so no single developer can push a signed release alone. Full audit trail via verification certificates.
Run your own CA with hardware-backed root and intermediate keys. Generate CSRs, manage certificate chains, and issue X.509 certificates — all protected by TPM 2.0. Replace expensive commercial CA HSMs.
Store SSH and TLS private keys in the TPM so they never exist on disk. Use hardware-enforced policies to control which users or services can sign. Rotate keys without downtime.
Protect high-value signing keys with M-of-N threshold policies. Require approval from multiple stakeholders for financial transactions, cryptocurrency custody, or legal document signing.
Provision unique TPM-bound identities for IoT devices at manufacturing. Use remote attestation to verify device integrity before granting access. Detect firmware tampering via PCR quotes.
Bind machine identities to TPM hardware. Attest that servers and workstations are running authorized software before granting network access. Build hardware-rooted trust for mTLS and SPIFFE/SPIRE.
Digitally sign legal documents, contracts, and compliance artifacts with non-repudiation. Threshold signing ensures critical documents require multiple authorized signatories.
Use TPM attestation and sealed keys to bootstrap secrets management systems like Vault. Prove machine identity with hardware before releasing secrets. No shared passwords or tokens.
Meet FIPS 140-2, PCI DSS, SOC 2, and eIDAS requirements for hardware key protection. Verification certificates create a cryptographic audit trail. Attestation proves keys never left hardware.
Sign build artifacts in CI/CD with TPM-bound keys. Attest build server integrity before signing. Threshold policies prevent a compromised pipeline from signing alone. Integrate with Sigstore and Notary.
Export keys with TPM2_Duplicate using hardware-enforced policies. Re-wrap keys for backup TPMs or disaster recovery. Duplicate policy keys ensure only authorized parties can initiate export.
Store S/MIME private keys in the TPM. Sign and encrypt emails with hardware-protected keys. Generate CSRs for S/MIME certificates from your private CA. Keys are non-exportable by default.
TPM HSM is designed to be simple to deploy and operate.
Run the gRPC server on any Linux machine with a TPM 2.0 chip. Docker, bare metal, or cloud VM — your choice. One command to start.
Launch the desktop app or open the web UI. Connect to your server over mTLS. Verify the TPM is genuine with remote attestation.
Import existing keys with client-side wrapping or generate new ones. Set signing policies: single signer, multi-party threshold, or YubiKey-bound.
Request signatures through the API or UI. The TPM enforces your policies before signing. Keys never leave the chip.
See how TPM HSM stacks up against commercial and cloud HSM offerings.
| Capability | TPM HSM | Cloud HSM | Hardware HSM | Software Keystore |
|---|---|---|---|---|
| Hardware key isolation | ✓ | ✓ | ✓ | ✕ |
| Multi-party threshold signing | ✓ | ✕ | Varies | ✕ |
| Remote attestation | ✓ | ✕ | ✕ | ✕ |
| YubiKey integration | ✓ | ✕ | ✕ | ✕ |
| Web of Trust | ✓ | ✕ | ✕ | ✕ |
| Air-gapped key generation | ✓ | ✕ | ✓ | ✓ |
| Open source | ✓ | ✕ | ✕ | Varies |
| Per-key / per-operation fees | $0 | $$$$ | $$$$ | $0 |
| Keys stay on your hardware | ✓ | ✕ | ✓ | ✓ |
| X.509 / PKI support | ✓ | Varies | ✓ | Varies |
Every security property is enforced by hardware or cryptographic proof — not promises.
Private keys never leave the TPM in plaintext. RSA-OAEP client-side wrapping ensures keys are encrypted before transmission. Only the target TPM can decrypt.
Server compromise cannot extract keys. Even with full server access, the TPM refuses to release key material. Hardware enforces the boundary.
TPM genuineness is verifiable. Remote attestation with EK certificate chains proves the TPM is real hardware from a known manufacturer.
Signing policies are hardware-enforced. Direct PolicySigned keys bake authorization into the TPM. The server cannot override or bypass the policy.
YubiKey origin is attestable. Chain verification against Yubico's root CA proves keys were generated on-device, not imported.
Trust validation is client-side. The web of trust and verification certificates are verified locally. The server stores data but cannot forge trust relationships.
Get started with TPM HSM in minutes. Open source, zero cost, hardware-grade security.