tiCrypt

Ready for CMMC Level 3

A complete, scalable on-prem solution. Proven in production.

End-to-end encrypted

Unlimited sub- enclaves for subcontractors

Replaces fragmented tech stack

Reduced compliance burden

GPU

Integrated GPU support

End-to-End Encrypted Compute Environments

tiCrypt is a product of Tera Insights and the University of Florida Research Computing. It is a single, fully integrated platform for regulated workloads designed to exceed NIST 800-171/CMMC Level 2 requirements.

NIST 800-171/CMMC Level 2 Compliant
NIST 800-172/CMMC Level 3 Ready
Tera Insights LogoUF Logo

Proven in Production

tiCrypt is an on-premises, end-to-end encrypted platform for secure data workflows.

10 years

Operating in production environments

9

Successful external NIST SP 800-171 / CMMC Level 2 assessments

HPC

Deployed at major research universities in supercomputing environments

Our current customers, large research institutions, are successfully meeting CMMC Level 2 requirements using tiCrypt as a core part of their environment.

The tiCrypt architecture, based on end-to-end encryption, is designed to support the enhanced protection requirements associated with CMMC Level 3. While tiCrypt has not yet been deployed in a Level 3 environment, it provides a strong technical foundation for organizations preparing to meet those requirements.

Partner with Us

We are looking to partner with prime contractors who value:

A single on-prem solution that can replace a fragmented stack of tools.

Reduced compliance burden.

Native support for cryptographically isolated sub-enclaves, enabling secure collaboration across grants and subcontractors.

Integrated GPU support for high-performance and specialized workloads.

Extensive operational experience supporting large-scale institutional and supercomputing environments.

Learn More

Explore our resources to better understand tiCrypt and CMMC-aligned secure compute environments.

  • For our CMMC Level 2 site, see cmmc-level2.com.
  • For an overview of system architecture, see Architecture.
  • Why we plan to integrate CACs for hardware-backed security, see CAC.