Clockwork Targets GPU Cluster Downtime With New Fault-Tolerance Guarantee
The company is introducing a contractual reliability standard for AI training, aiming to eliminate the costly cycle of checkpoint-restarts in large-scale GPU deployments.

Large-scale GPU clusters operate under a constant state of hardware attrition where component failure is a statistical certainty rather than an anomaly. Clockwork is attempting to shift the industry standard for managing these interruptions with the launch of its YOCO Guarantee, a contractual commitment to resolve 90 percent of training failures without requiring checkpoint rollbacks or redundant recomputation.
The foundation of this service is TorchPass, a fault-tolerance framework that reached general availability in March. When a GPU or compute node encounters a failure, TorchPass migrates the in-memory state of the training job—including model weights, gradients, and optimizer states—to a healthy spare resource. This process, which the company likens to a virtual machine migration for GPUs, typically recovers the training run within minutes.
Dan Zheng, co-founder and chief business officer at Clockwork, characterizes the existing industry reliance on checkpoint-restarts as a significant drain on both time and capital. Teams currently lose hours of progress when a node fails, forcing them to pay for expensive compute cycles to redo work that was previously completed. TorchPass mitigates this by enabling live migration, either by utilizing dedicated standby nodes or by preemptively reclaiming resources from lower-priority jobs.
The system also incorporates predictive capabilities to address hardware degradation before a total failure occurs. If telemetry indicates that a GPU is exceeding thermal thresholds, TorchPass can migrate the job while the hardware remains operational. This proactive approach allows teams to preserve the integrity of the training run by moving the workload to stable infrastructure before the underlying component crashes.
Implementation of TorchPass is available in two distinct modes depending on the user’s requirements for integration. The model-aware mode requires minimal code modifications and enables recovery in tens of seconds by selectively grabbing necessary data. Alternatively, the model-transparent mode captures a system-level snapshot without requiring changes to the training code, though it involves moving a larger volume of data and results in slightly longer recovery times.
Clockwork acknowledges that its solution is not a panacea for all infrastructure issues, particularly when catastrophic network-wide outages occur. However, the company argues that the current industry model, which often results in clusters running at only 30 to 50 percent of their theoretical performance, is unsustainable. By shifting the burden of reliability from the infrastructure layer to the software layer, Clockwork aims to provide smaller enterprises with the same resilience typically reserved for large-scale AI labs.
The economic impact of these failures is substantial, with Clockwork estimating that restarts cost a typical 2,048-GPU H200 deployment more than $6 million annually. Independent testing conducted by SemiAnalysis supports the efficiency claims, with lead author Jordan Nanos noting that TorchPass outperformed existing open-source alternatives like Meta’s TorchFT in terms of tokens per second per GPU. The YOCO Guarantee serves to formalize these performance metrics into a contractual obligation, offering customers a 25 percent credit if the company fails to meet its reliability benchmarks.
The broader goal is to decouple the developer experience from the volatility of physical hardware. By abstracting the underlying node failures, researchers can focus on model architecture rather than managing infrastructure recovery. This shift mirrors the evolution of data center management, where software-defined layers have long shielded developers from the underlying instability of commodity hardware.
Future adoption will likely depend on how effectively these tools integrate into existing MLOps pipelines as training jobs grow in duration and scale. As the industry moves toward more intensive reinforcement learning and post-training tasks, the ability to maintain continuous uptime will become a critical differentiator for organizations lacking the massive engineering resources of major AI labs. Clockwork intends to continue refining its observability tools to further improve the speed and reliability of these transitions.


