Cedana is
GPU job migration
infrastructure
for increasing AI
revenue per MW.
┌──────────────────────────────────────┐ │ NODE-A · us-east-1c [FAILING] │ ├──────────────────────────────────────┤ │ GPU-7 B200 ████████████████ 88 GiB │ │ iteration 14,821 / 50,000 │ └──────────────────────────────────────┘ │ ··· awaiting checkpoint ··· │ │······································│ │······································│ │······································│ │[░░░░░░░░░░░░░░░░░░░░░░░░] 0% │ ┌──────────────────────────────────────┐ │ NODE-B · us-east-1d [STANDBY] │ ├──────────────────────────────────────┤ │ GPU-3 B200 ░░░░░░░░░░░░░░░░ 0 GiB │ │ awaiting checkpoint │ └──────────────────────────────────────┘
unlock() your scheduler.
Work with what you have
No rip-and-replace. No code changes. No disruption to your teams.
Kubernetes & SLURM
Built for AI and HPC. Native support for SLURM and Kubernetes.
First migration in <30 min
K8s helm chart or SLURM plug-in. No changes to your config.
AI workloads cannot move once running.
Cedana makes them liquid.
Four ways stranded compute drains budgets — and how Cedana resolves each, live and in place.
Idle GPUs
Valuable compute remains stranded while critical work is delayed.
Maximize throughput
Workloads shift to idle GPUs, reclaiming stranded capacity and maximizing cluster throughput.
Expensive failures
Failures and preemptions force workloads to restart from scratch — up to 65% of compute wasted.
Automated reliability
Workloads automatically migrate to healthy infrastructure and resume after failures.
Overprovisioned GPUs
Capacity is routinely over-provisioned by 10–50% just to maintain reliability and hit SLAs.
Eliminate overprovisioning
Automatic migration and recovery remove the need for large safety buffers to meet SLAs.
Rigid infrastructure
Schedulers cannot dynamically adapt to failures, demand, or changing priorities.
Adaptive infrastructure
Kubernetes and SLURM adapt workloads in real time to failures and demand.
The Cedana diff.
Same model. Same hardware.
21.7× faster to first token.
$ vllm serve zai-org/GLM-5.2-FP8 --tp=8INFO 00:00:03 spawning 8 workers · EP=8INFO 00:00:40 loading shards 12/94 …INFO 00:05:00 loading shards 40/94 …INFO 00:12:00 loading shards 78/94 …INFO 00:16:20 loading shards 94/94 …INFO 00:18:40 building cuda graph (×8)INFO 00:20:30 warming kv cache · vision towerINFO 00:21:30 jit compile attention
$ cedana resume glm-5.2-fp8 --from=snap.az-1[+] fetch snapshot :: ok (734 GiB · memlock)[+] verify hash :: ok (sha256: c4e1…9a)[+] restore cuda ctx :: ok (8× driver attached)[+] repopulate gpu mem :: ok (weights + KV)[+] thaw connections :: ok (sockets)[+] register endpoint :: ok (port 8000)READY 00:01:01 first token
Hardware fails.
Your training run doesn't.
$ python train.py --batch=64 --gpu=7INFO step 13 200/50 000 loss=2.41 lr=3e-5INFO step 14 050/50 000 loss=2.34 lr=3e-5INFO step 14 800/50 000 loss=2.31 lr=3e-5FATAL gpu-7 :: power_loss · pcie link downERR nvml :: device unreachable (-117)WARN cedana :: node-A flagged unhealthyWARN cedana :: snapshot @ step 14 832 secured
$ cedana watch --cluster=us-east-1INFO node-B :: idle (gpu-3 free)INFO node-B :: idle (gpu-3 free)[+] receive snapshot :: ok (96 GiB/s)[+] verify hash :: ok (sha256: 9f4c…e2)[+] map gpu pages :: ok (cuda-aware)[+] thaw kv cache :: ok (no jit)[+] restore optimizer :: ok (state matched)[✓] resume @ step 14 832/50 000 Δ 0.42sINFO step 14 900/50 000 loss=2.30 lr=3e-5
PERSISTENT