tiCrypt has no hardware vendor lock-in. It runs on commodity x86_64 servers, standard networking, and whatever storage you already have. But "hardware agnostic" does not mean "no requirements."
On June 18, 2026, tiCrypt gets its first major visual update in a few years. The redesigned front-end (v2.17.0) will be available from the Tera Insights repository, and this release is dedicated entirely to one thing: the experience.
We listened to feedback from researchers and administrators across our deployments and rebuilt the interface around how you actually work, while leaving everything beneath it untouched. There is no migration and nothing new to learn; every workflow, process, and security mechanism is exactly as it was.
What is new
What is next
This release is a starting point. As more researchers share feedback, we will continue to adapt and improve. This redesign also lays a long-term UX foundation for building much larger features.
Getting the update
Front-end v2.17.0 ships June 18, 2026, from the Tera Insights repository. Administrators can pull the latest release to roll it out across their deployment. For deployments that pull directly from the Tera Insights repository, users will automatically receive the update when they launch the application.
Compliance frameworks like CMMC 2.0 Level 2 do not treat audit logging as a best practice. They treat it as a requirement. The Audit and Accountability (AU) domain of CMMC, mapped directly from NIST SP 800-171 Revision 2, defines nine controls that govern how systems must create, retain, protect, correlate, and report on audit records. These controls exist for a reason: without a trustworthy audit trail, there is no forensics, no accountability, and no way to prove that CUI was actually protected.
tiCrypt was designed from the start with the assumption that every action must be recorded and that records must be resistant to tampering. This article explains how tiCrypt's audit system works, what it captures, how it supports forensic investigation, and how it maps to the CMMC AU controls that organizations are assessed against.
tiCrypt's security model is designed to protect data once it's inside the secure enclave. But in practice, the first question administrators and researchers ask is more immediate: how does data get in?
tiCrypt supports several ingress methods, each built for a different set of constraints, including dataset size, whether the sender has tiCrypt credentials, where the data needs to land, and who owns the process. This post breaks down each option and when to use it.