You move a Runpod training job to Nodus by running the same container image and script with nodus run , with datasets in a Nodus Volume and checkpoints written to /nodus/state . Nodus saves that directory while the job runs and restores it on a new machine if capacity is lost, so most single-node jobs need one changed path and one command. Serverless endpoints and multi-node Instant Clusters are the parts to leave on Runpod for now.
Runpod is still written RunPod in many older guides and searches; we use its current spelling. We build Nodus, so weigh our view accordingly. If you are still deciding whether to move, read Nodus vs RunPod or the RunPod alternatives list first. This post covers only the move, and every Nodus command in it is copied from our docs.
What does each Runpod concept become on Nodus?
A Runpod Pod used for a training run becomes a Nodus Job, and almost everything around it has a direct counterpart.…