How do the TheTranq work behind the scenes

What Happens to Your VM When It Visits the TheTranq 

Your Virtual Machine (VM) can “visit” our TheTranq environment whenever it needs extra performance, GPU acceleration, maintenance, or a deep clean.

This document explains — in simple technical terms — what actually happens during that process. 

Our system is designed to be safe, reversible, predictable, and efficient, with minimal downtime. 

1. Two Separate Environments Working Together 

Your VM moves between two places: 

Home Environment 

Where your VM normally runs.
This is your everyday compute environment. 

TheTranq Environment 

A highperformance zone equipped with: 

• ondemand GPUs (e.g., L40S, A100, H100) 

• strong CPU/memory capacity 

• isolated resources for intensive tasks 

The two environments are not directly connected.
Instead, they communicate through a secure backup-and-replication system. 

2. We Take a Snapshot of Your VM 

To move your VM, we first create a snapshot — a complete, consistent image of its disk and memory state. 

This step may involve stopping the VM for a brief moment, so the snapshot is perfectly clean.
Typical downtime: a few seconds to a couple of minutes, depending on the size of recent changes. 

This snapshot ensures: 

• no data is lost 

• disks remain consistent 

• your VM restarts exactly as it was 

3. The Snapshot is Backed Up to a Secure Server 

Your VM snapshot is then sent to our Proxmox Backup Server (PBS) — a specialized, encrypted backup system. 

PBS uses: 

• Deduplication (only stores unique data once) 

• Compression (minimizes size) 

• Incremental transfers (only sends changed blocks) 

This keeps the transfer fast, even if your VM is large. 

4. The Backup Replicates to the TheTranq Datacenter 

The PBS server inside the TheTranq datacenter automatically receives the replicated snapshot. 

Because the data is: 

• deduplicated 

• compressed 

• blocklevel incremental 

…the transfer is extremely efficient and works well even over long distances or slower WAN links. 

When the sync is complete, the TheTranq environment now has a readytorestore image of your VM. 

5. Your VM is Reconstructed Inside the TheTranq 

Next, your VM is restored inside the TheTranq cluster. 

The VM keeps: 

• the same OS 

• the same configuration 

• the same data 

• the same identity 

But now it runs on TheTranq hardware, with optional access to: 

• highend GPUs 

• much larger memory 

• faster storage 

• clean isolated compute nodes 

This is where the “TheTranq treatment” happens: 

• AI/ML workloads 

• rendering 

• processing 

• debugging 

• cleanup 

• deep maintenance 

Anything that requires heavy compute power thrives here.