Skip to main content
Last updated: July 31, 2026Latest Frontend Version: 2.17.4

Concepts

tiCrypt's architecture differs from traditional shared computing environments in fundamental ways: encryption is per-resource rather than per-perimeter, compute happens inside ephemeral VMs rather than on shared nodes, and administrative access to infrastructure is structurally decoupled from access to research data. These pages bridge the gap between what you already know and how tiCrypt works.

Core Concepts in 60 Seconds​

tiCrypt uses five terms that sound similar but control different things. Skim these once before diving into the pages below:

  • System Role: Your permission level in the platform (User, Sub-Admin, Admin).
  • User Profile: Your individual feature access settings (Vault, VMs, data export).
  • VM Role: Your access level inside a virtual machine (VM User, VM Admin).
  • Team: Your organizational group with shared resource quotas.
  • Project: A security boundary that tags resources with compliance requirements.
PageWho it helpsWhat it covers
From Shared Computing Cluster to tiCryptResearchers and IT staff migrating from a shared computing or HPC environmentConcept-by-concept mapping table, dual Slurm architecture, data lifecycle, quick-start checklist
Institutional Role MappingPIs, lab managers, IT directors setting up tiCrypt for a research groupHow to compose system roles, user profiles, and VM roles to reproduce institutional personas
VM Roles and PermissionsAnyone working with tiCrypt virtual machinesHow Owner, Co-Owner, Manager, and User roles work inside a VM, independently from the main system