The product
The four vaults
Triplets, NoPII, and the Vault solve three different problems for three different teams. Underneath, they run on shared AI privacy infrastructure: the same encryption, the same tenant isolation, the same key management, and the same audit trail.
Triplets verifies what your AI says.
NoPII protects what your AI reads.
The Vault holds what you cannot afford to store.
Each product is bought, deployed, and justified on its own. Start where it hurts.
The compiler behind Continuous Trust Certification. Answers your head of AI.
Triplets compiles your evidence into certified knowledge, answers only what that evidence supports, and refuses the rest in writing.
The PII-tokenizing proxy for LLM APIs. Answers your engineering and compliance teams.
Sensitive data is tokenized before it reaches the model provider and restored when responses return.
Encryption and tokenization for stored data. Answers your CISO.
Cards, fields, files, and customer intake move into a certified vault, and your systems keep tokens that still work.
The foundation matters when you run more than one product. The token NoPII creates lives in the same vault your stored data does, under the same per-customer keys. The audit trail your compliance team reviews covers AI answers, AI traffic, and data custody in one format. Adding a second product later is a marketplace subscription, not a vendor evaluation.
The usual answer to these problems is a stack: a reliability tool, a privacy proxy, a tokenization vendor, an encrypted-storage tool, and a homegrown intake form. Five vendors who have never met, five integrations, five audits, and a gap hiding at every seam.
There is also a quieter mistake: the belief that you can prompt your way to reliable AI or mask your way to private AI. Both treat an infrastructure problem as an application problem.
| The stitched-together stack | Enigma Vault products |
|---|---|
| A different vendor for AI answers, PII, and stored data | A purpose-built product for each, from one company |
| Each tool has its own keys, logs, and audit format | Any combination shares one foundation and one audit format |
| Gaps live at the seams between tools | The seams were engineered out |
| Reliability and privacy bolted on at the app layer | Enforced as infrastructure, outside the application |
Per-customer AES-256 keys in a managed secrets store, rolled over after a specified time. No key is shared between customers.
Every verification, tokenization, and retrieval logged. Compliance reviews start from evidence.
The trust layer sits in your critical path. It is engineered like it.
On every API surface. No shared secrets in config files.
Built on the Enigma Vault, which is PCI DSS Level 1 and SOC 2 Type II.
Procured through the AWS account you already have. Free allowances are available for Card Vault, Data Vault, File Vault and NoPII. Customer Vault, Agent Vault and Triplets are priced by engagement. See pricing.
