Frontend 2.17.10 is, above all, a repair release for the Management console. In 2.17.9, selecting a VM in Management > Running VMs produced an empty actions menu, so actions administrators rely on there, such as Power, View logs and Set project, were unavailable. Viewing a VM's users could also show a blank screen or an error. This release fixes both.

Alongside the repairs, bulk VM shutdown is back, every authorized user on a running VM now shows a copyable user ID, and eleven more fixes cover virtual machines, Vault storage, and layout across the interface.

Backend 3.14.1 is a storage and API release. The headline is that file garbage collection works again: files left behind by deleted users and removed directories have not been reclaimed on most deployments for a long time, and this release fixes the reason. Alongside it, the API gains multi-type tokens, ten read-only administration routes, and a capabilities endpoint that lets a client ask the backend what it supports rather than guess from a version number.

Nothing in this release reclaims storage on upgrade. The garbage collector ships disabled and in dry-run, and taking it live is a deliberate, staged decision documented in full below.

Two releases shipped on 30 September. 4.1.1 carries the substance: transfers are faster and no longer hang, Windows installs from an MSIX package that upgrades in place, and about thirty fixes land across deployments, cloud drives and SFTP. 4.1.2 adds a reworked Windows window frame.

Sites moving large datasets through SFTP inboxes reported a specific, frustrating pattern: a big transfer would complete, and then the next transfer would fail. Sometimes it took a single multi-gigabyte file, sometimes a directory with thousands of small ones. SFTP 1.5.1 fixes that, and rebuilds the upload pipeline underneath it.

tiCrypt research VMs are air-gapped by design. They have no outbound internet access, which is fundamental to the security model but creates a practical problem: researchers need Python packages, and pip install needs a network. This article explains how the offline PyPI mirror solves that problem, why the isolation model works the way it does, and what the download strategy looks like under the hood.

For step-by-step instructions, see the admin setup guide and the researcher usage guide.

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."