What Infrastructure Does InferTrust™ Require?

InferTrust™ requires a lightweight SDK installed in your inference environment and access to a hardware-backed keystore (TPM, Secure Enclave, or Android Keystor

Minimal Infrastructure Footprint

InferTrust™ is designed to operate with the infrastructure you already have. The core requirements are:

• The InferTrust™ SDK, installed alongside your inference code. This is a lightweight library, not a separate service or daemon.
• A hardware-backed keystore for cryptographic signing. Modern devices and servers include these by default: Apple devices have Secure Enclave, Android devices have Keystore/StrongBox, and most server hardware includes a TPM 2.0 module.
• Local storage for the append-only decision log. The storage requirements are modest because each decision record is small (a structured set of fields plus a cryptographic signature).

What You Do Not Need

InferTrust™ does not require a blockchain, distributed consensus network, separate database server, or custom hardware. It does not require always-on network connectivity. It does not require modifications to your AI model, training pipeline, or data processing infrastructure.

Sync Server (Optional)

For organizations that want centralized visibility across multiple devices or deployment locations, InferTrust™ provides an optional sync server that aggregates signed records from edge devices. The sync server verifies signatures on receipt and provides a consolidated audit view. But the cryptographic integrity of each record is established at the device level, not at the server level.