SpotWarp v3.3.3 Setup Guide

Get SpotWarp running in 1 minute

Three simple steps. Your credentials stay 100% local — zero cloud key uploads.

Install SpotWarp

1-line universal installer

Run the 1-liner installer or use standard pip. No root or sudo required.

Linux / macOS (1-Liner)

curl -fsSL https://gpu-action.com/install.sh | bash

Windows PowerShell (1-Liner)

irm https://gpu-action.com/install.ps1 | iex

Standard Python pip (Any OS)

pip install --upgrade spotwarp

Zero-Config Setup

100% local config

SpotWarp automatically detects your existing Vast.ai and RunPod keys from local CLI configs (~/.vast_api_key / ~/.runpod/config.toml). Or run the 1-minute setup wizard:

terminal (any OS)

spotwarp init

✨ Zero-Config Smart Sniffing: If you already use Vast.ai or RunPod CLI, you can skip spotwarp init entirely and jump straight to Step 3!

Start the Guard

instant protection

Run in the foreground or detach as a 24/7 background daemon with -d.

Option A: Foreground Live Console

spotwarp start

Option B: 24/7 Background Daemon

spotwarp start -d

💡 Training Auto-Resume: To automatically resume training on replacement GPUs, add:
spotwarp start --resume-cmd "python train.py --resume"

Daemon Management & Status

cli commands

Check Status

spotwarp status

Stop Daemon

spotwarp stop

Console Output Decoder

what you see

License Verified: Active

GoodYou're authenticated. Zero-downtime protection is live.

Found new active instance: …

GoodRented Spot GPU auto-detected. Continuous delta-sync active.

Monitoring 0 instances

NormalNo active GPU instance running on your Vast.ai account yet.

Triggering Failover Protocol

ActionEviction detected. SpotWarp is provisioning a replacement GPU and restoring files.

Troubleshooting

You see	It means
status 401	License key mistyped or concatenated with another key — re-copy it as one piece.
0 instances, GPU rented	`VAST_API_KEY` isn't set in this window — re-run step 3 here.
`export` error	You're in PowerShell — use `$env:` instead.
backups missing	Check `.\backups\<instance_id>\`, or your `--backup-dir` path.