RunPod Cloud GPU

Cloud GPU processing via RunPod serverless.

RunPod Cloud GPU — Super Bowl-style launch ad (from the digitalsamba/claude-code-video-toolkit README)

From the digitalsamba/claude-code-video-toolkit README — shows the whole collection, not only this skill. · view on GitHub

How to use it

Claude Code
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/runpod.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit digitalsamba/claude-code-video-toolkit/.claude/skills/runpod#main ~/.claude/skills/runpod

For one project only, change the path to .claude/skills/runpod.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of RunPod Cloud GPU

Show the full text233 lines
namedescription
runpodCloud GPU processing via RunPod serverless. Use when setting up RunPod endpoints, deploying Docker images, managing GPU resources, troubleshooting endpoint issues, or understanding costs. Covers all 5 toolkit images (qwen-edit, realesrgan, propainter, sadtalker, qwen3-tts).

RunPod Cloud GPU

Run open-source AI models on cloud GPUs via RunPod serverless. Pay-per-second, no minimums.

Setup

# 1. Create account at https://runpod.io
# 2. Add API key to .env
echo "RUNPOD_API_KEY=your_key_here" >> .env

# 3. Deploy any tool with --setup
uv run tools/image_edit.py --setup
uv run tools/upscale.py --setup
uv run tools/dewatermark.py --setup
uv run tools/sadtalker.py --setup
uv run tools/qwen3_tts.py --setup

Each --setup command:

  1. Creates a RunPod template from the Docker image
  2. Creates a serverless endpoint with appropriate GPU
  3. Saves the endpoint ID to .env (e.g. RUNPOD_QWEN_EDIT_ENDPOINT_ID)

Available Images

All images are public on GHCR — no authentication needed.

Tool Docker Image GPU VRAM Typical Cost
image_edit ghcr.io/conalmullan/video-toolkit-qwen-edit:latest A6000/L40S 48GB+ ~$0.05-0.15/job
upscale ghcr.io/conalmullan/video-toolkit-realesrgan:latest RTX 3090/4090 24GB ~$0.01-0.05/job
dewatermark ghcr.io/conalmullan/video-toolkit-propainter:latest RTX 3090/4090 24GB ~$0.05-0.30/job
sadtalker ghcr.io/conalmullan/video-toolkit-sadtalker:latest RTX 4090 24GB ~$0.05-0.15/job
qwen3_tts ghcr.io/conalmullan/video-toolkit-qwen3-tts:latest ADA 24GB 24GB ~$0.01-0.05/job

Total monthly cost: Rarely exceeds $10 even with heavy use.

How It Works

All tools follow the same pattern:

Local CLI → Upload input to cloud storage → RunPod API → Poll for result → Download output
  1. File transfer: Tools use Cloudflare R2 when configured (R2_ACCOUNT_ID, R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY, R2_BUCKET_NAME), falling back to free upload services
  2. RunPod API: Tools call the /run endpoint, then poll /status/{job_id} until complete
  3. Cold vs warm start: First request after idle spins up a worker (~30-90s). Subsequent requests are fast (~5-15s)

Endpoint Management

Workers
workersMin: 0    — Scale to zero when idle (no cost)
workersMax: 1    — Max concurrent jobs (increase for throughput)
idleTimeout: 5   — Seconds before worker scales down

Across all endpoints, you share a total worker pool based on your RunPod plan. If you hit limits, reduce workersMax on endpoints you're not actively using.

Checking Endpoint Status

Each tool stores its endpoint ID in .env:

Tool Env Var
image_edit RUNPOD_QWEN_EDIT_ENDPOINT_ID
upscale RUNPOD_UPSCALE_ENDPOINT_ID
dewatermark RUNPOD_DEWATERMARK_ENDPOINT_ID
sadtalker RUNPOD_SADTALKER_ENDPOINT_ID
qwen3_tts RUNPOD_QWEN3_TTS_ENDPOINT_ID
Disabling an Endpoint

To free worker slots without deleting the endpoint, set workersMax=0 via the RunPod dashboard or GraphQL API.

RunPod API Reference

Use these to query and manage endpoints programmatically. RunPod disables GraphQL introspection, so these field names are verified and must be exact.

Authentication

All API calls require Authorization: Bearer $RUNPOD_API_KEY.

  • GraphQL: POST https://api.runpod.io/graphql
  • REST (Serverless): https://api.runpod.ai/v2/{endpoint_id}/...
GraphQL Queries

List all endpoints:

query { myself { endpoints { id name gpuIds templateId workersMax workersMin } } }

Current spend rate:

query { myself { currentSpendPerHr spendDetails { localStoragePerHour networkStoragePerHour gpuComputePerHour } } }

List pods:

query { myself { pods { id name runtime { uptimeInSeconds } machine { gpuDisplayName } desiredStatus } } }

Common mistakes: Field names are camelCase with full words — localStoragePerHour not localStoragePerHr. Endpoints are endpoints not serverlessWorkers. spending is not a field — use currentSpendPerHr and spendDetails.

GraphQL Mutations

Update endpoint GPU or config:

mutation { saveEndpoint(input: {
  id: "endpoint_id",
  name: "endpoint-name",
  templateId: "template_id",
  gpuIds: "AMPERE_24",
  workersMin: 0,
  workersMax: 1
}) { id gpuIds } }

saveEndpoint requires name and templateId even for updates — query first to get current values.

REST API (Serverless)
Action Method URL
Submit job POST /v2/{id}/run
Check status GET /v2/{id}/status/{job_id}
Cancel job POST /v2/{id}/cancel/{job_id}
List pending GET /v2/{id}/requests
Health/stats GET /v2/{id}/health

Health response includes job counts and worker state:

{
  "jobs": { "completed": 16, "failed": 1, "inProgress": 0, "inQueue": 2, "retried": 0 },
  "workers": { "idle": 0, "initializing": 1, "ready": 0, "running": 0, "throttled": 0 }
}

Note: /requests only returns pending/queued jobs. Completed job history is not available via the API — check the RunPod web console for logs.

GPU Type IDs
ID GPU VRAM Typical Cost
AMPERE_24 RTX 3090 24GB ~$0.34/hr
ADA_24 RTX 4090 24GB ~$0.69/hr
AMPERE_48 A6000 48GB ~$0.76/hr
AMPERE_80 A100 80GB ~$1.99/hr

Availability note: ADA_24 (4090) is frequently throttled/unavailable on RunPod. Always configure endpoints with multiple fallback GPU types (comma-separated) to avoid jobs getting stuck in queue indefinitely:

gpuIds: "AMPERE_24,ADA_24"   # Try 3090 first, fall back to 4090

All toolkit tools also enforce a 5-minute queue timeout — if no GPU is available within 300 seconds, the job is automatically cancelled to prevent runaway billing from failed initialization cycles.

Cloudflare R2 via AWS CLI

R2 uses the S3-compatible API but requires --region auto:

AWS_ACCESS_KEY_ID="$R2_ACCESS_KEY_ID" \
AWS_SECRET_ACCESS_KEY="$R2_SECRET_ACCESS_KEY" \
aws s3api list-objects-v2 \
  --bucket "$R2_BUCKET_NAME" \
  --endpoint-url "https://${R2_ACCOUNT_ID}.r2.cloudflarestorage.com" \
  --region auto

Common mistake: Omitting --region auto causes InvalidRegionName error. R2 valid regions: wnam, enam, weur, eeur, apac, oc, auto.

Troubleshooting

Force Image Pull

When you push a new Docker image version, RunPod may still use the cached old one. To force a pull:

  1. Update the template's imageName to use @sha256:DIGEST notation
  2. Wait for the worker to restart
  3. Revert to :latest tag after confirming
Cold Start Too Slow
  • qwen3-tts: ~70s cold start, ~7s warm
  • sadtalker: ~60s cold start, ~10s warm
  • image_edit: ~90s cold start, ~15s warm

If cold starts are a problem, set workersMin: 1 (costs money when idle).

Job Fails with OOM

The model needs more VRAM than the GPU provides. Options:

  • Use a larger GPU tier
  • For dewatermark: reduce --resize-ratio (default 0.5 for safety)
  • For image_edit: reduce --steps
"No workers available"

You've hit your plan's concurrent worker limit. Either:

  • Wait for a running job to finish
  • Set workersMax=0 on endpoints you're not using
  • Upgrade your RunPod plan

Docker Images

All Dockerfiles live in docker/runpod-*/. Images use runpod/pytorch as the base to share layers across tools.

Building for RunPod (from Apple Silicon Mac):

docker buildx build --platform linux/amd64 -t ghcr.io/conalmullan/video-toolkit-<name>:latest docker/runpod-<name>/
docker push ghcr.io/conalmullan/video-toolkit-<name>:latest

GHCR packages default to private — you must manually make them public for RunPod to pull them. Go to GitHub > Packages > Package Settings > Change Visibility.

Cost Optimization

  • Keep workersMin: 0 on all endpoints (scale to zero)
  • Only deploy endpoints you actively need
  • Use workersMax=0 to disable idle endpoints without deleting them
  • Qwen3-TTS is significantly cheaper than ElevenLabs for voiceovers
  • Check the RunPod dashboard for usage and billing
1---
2name: runpod
3description: Cloud GPU processing via RunPod serverless. Use when setting up RunPod endpoints, deploying Docker images, managing GPU resources, troubleshooting endpoint issues, or understanding costs. Covers all 5 toolkit images (qwen-edit, realesrgan, propainter, sadtalker, qwen3-tts).
4---
5 
6# RunPod Cloud GPU
7 
8Run open-source AI models on cloud GPUs via RunPod serverless. Pay-per-second, no minimums.
9 
10## Setup
11 
12```bash
13# 1. Create account at https://runpod.io
14# 2. Add API key to .env
15echo "RUNPOD_API_KEY=your_key_here" >> .env
16 
17# 3. Deploy any tool with --setup
18uv run tools/image_edit.py --setup
19uv run tools/upscale.py --setup
20uv run tools/dewatermark.py --setup
21uv run tools/sadtalker.py --setup
22uv run tools/qwen3_tts.py --setup
23```
24 
25Each `--setup` command:
261. Creates a RunPod **template** from the Docker image
272. Creates a serverless **endpoint** with appropriate GPU
283. Saves the endpoint ID to `.env` (e.g. `RUNPOD_QWEN_EDIT_ENDPOINT_ID`)
29 
30## Available Images
31 
32All images are public on GHCR — no authentication needed.
33 
34| Tool | Docker Image | GPU | VRAM | Typical Cost |
35|------|-------------|-----|------|-------------|
36| image_edit | `ghcr.io/conalmullan/video-toolkit-qwen-edit:latest` | A6000/L40S | 48GB+ | ~$0.05-0.15/job |
37| upscale | `ghcr.io/conalmullan/video-toolkit-realesrgan:latest` | RTX 3090/4090 | 24GB | ~$0.01-0.05/job |
38| dewatermark | `ghcr.io/conalmullan/video-toolkit-propainter:latest` | RTX 3090/4090 | 24GB | ~$0.05-0.30/job |
39| sadtalker | `ghcr.io/conalmullan/video-toolkit-sadtalker:latest` | RTX 4090 | 24GB | ~$0.05-0.15/job |
40| qwen3_tts | `ghcr.io/conalmullan/video-toolkit-qwen3-tts:latest` | ADA 24GB | 24GB | ~$0.01-0.05/job |
41 
42**Total monthly cost:** Rarely exceeds $10 even with heavy use.
43 
44## How It Works
45 
46All tools follow the same pattern:
47 
48```
49Local CLI → Upload input to cloud storage → RunPod API → Poll for result → Download output
50```
51 
521. **File transfer:** Tools use Cloudflare R2 when configured (`R2_ACCOUNT_ID`, `R2_ACCESS_KEY_ID`, `R2_SECRET_ACCESS_KEY`, `R2_BUCKET_NAME`), falling back to free upload services
532. **RunPod API:** Tools call the `/run` endpoint, then poll `/status/{job_id}` until complete
543. **Cold vs warm start:** First request after idle spins up a worker (~30-90s). Subsequent requests are fast (~5-15s)
55 
56## Endpoint Management
57 
58### Workers
59 
60```
61workersMin: 0 — Scale to zero when idle (no cost)
62workersMax: 1 — Max concurrent jobs (increase for throughput)
63idleTimeout: 5 — Seconds before worker scales down
64```
65 
66Across all endpoints, you share a total worker pool based on your RunPod plan. If you hit limits, reduce `workersMax` on endpoints you're not actively using.
67 
68### Checking Endpoint Status
69 
70Each tool stores its endpoint ID in `.env`:
71 
72| Tool | Env Var |
73|------|---------|
74| image_edit | `RUNPOD_QWEN_EDIT_ENDPOINT_ID` |
75| upscale | `RUNPOD_UPSCALE_ENDPOINT_ID` |
76| dewatermark | `RUNPOD_DEWATERMARK_ENDPOINT_ID` |
77| sadtalker | `RUNPOD_SADTALKER_ENDPOINT_ID` |
78| qwen3_tts | `RUNPOD_QWEN3_TTS_ENDPOINT_ID` |
79 
80### Disabling an Endpoint
81 
82To free worker slots without deleting the endpoint, set `workersMax=0` via the RunPod dashboard or GraphQL API.
83 
84## RunPod API Reference
85 
86Use these to query and manage endpoints programmatically. RunPod disables GraphQL introspection, so these field names are verified and must be exact.
87 
88### Authentication
89 
90All API calls require `Authorization: Bearer $RUNPOD_API_KEY`.
91 
92- **GraphQL:** `POST https://api.runpod.io/graphql`
93- **REST (Serverless):** `https://api.runpod.ai/v2/{endpoint_id}/...`
94 
95### GraphQL Queries
96 
97**List all endpoints:**
98```graphql
99query { myself { endpoints { id name gpuIds templateId workersMax workersMin } } }
100```
101 
102**Current spend rate:**
103```graphql
104query { myself { currentSpendPerHr spendDetails { localStoragePerHour networkStoragePerHour gpuComputePerHour } } }
105```
106 
107**List pods:**
108```graphql
109query { myself { pods { id name runtime { uptimeInSeconds } machine { gpuDisplayName } desiredStatus } } }
110```
111 
112> **Common mistakes:** Field names are camelCase with full words — `localStoragePerHour` not `localStoragePerHr`. Endpoints are `endpoints` not `serverlessWorkers`. `spending` is not a field — use `currentSpendPerHr` and `spendDetails`.
113 
114### GraphQL Mutations
115 
116**Update endpoint GPU or config:**
117```graphql
118mutation { saveEndpoint(input: {
119 id: "endpoint_id",
120 name: "endpoint-name",
121 templateId: "template_id",
122 gpuIds: "AMPERE_24",
123 workersMin: 0,
124 workersMax: 1
125}) { id gpuIds } }
126```
127 
128`saveEndpoint` requires `name` and `templateId` even for updates — query first to get current values.
129 
130### REST API (Serverless)
131 
132| Action | Method | URL |
133|--------|--------|-----|
134| Submit job | POST | `/v2/{id}/run` |
135| Check status | GET | `/v2/{id}/status/{job_id}` |
136| Cancel job | POST | `/v2/{id}/cancel/{job_id}` |
137| List pending | GET | `/v2/{id}/requests` |
138| Health/stats | GET | `/v2/{id}/health` |
139 
140**Health response** includes job counts and worker state:
141```json
142{
143 "jobs": { "completed": 16, "failed": 1, "inProgress": 0, "inQueue": 2, "retried": 0 },
144 "workers": { "idle": 0, "initializing": 1, "ready": 0, "running": 0, "throttled": 0 }
145}
146```
147 
148> **Note:** `/requests` only returns pending/queued jobs. Completed job history is not available via the API — check the RunPod web console for logs.
149 
150### GPU Type IDs
151 
152| ID | GPU | VRAM | Typical Cost |
153|----|-----|------|-------------|
154| `AMPERE_24` | RTX 3090 | 24GB | ~$0.34/hr |
155| `ADA_24` | RTX 4090 | 24GB | ~$0.69/hr |
156| `AMPERE_48` | A6000 | 48GB | ~$0.76/hr |
157| `AMPERE_80` | A100 | 80GB | ~$1.99/hr |
158 
159**Availability note:** `ADA_24` (4090) is frequently throttled/unavailable on RunPod. Always configure endpoints with **multiple fallback GPU types** (comma-separated) to avoid jobs getting stuck in queue indefinitely:
160 
161```graphql
162gpuIds: "AMPERE_24,ADA_24" # Try 3090 first, fall back to 4090
163```
164 
165All toolkit tools also enforce a 5-minute queue timeout — if no GPU is available within 300 seconds, the job is automatically cancelled to prevent runaway billing from failed initialization cycles.
166 
167### Cloudflare R2 via AWS CLI
168 
169R2 uses the S3-compatible API but requires `--region auto`:
170 
171```bash
172AWS_ACCESS_KEY_ID="$R2_ACCESS_KEY_ID" \
173AWS_SECRET_ACCESS_KEY="$R2_SECRET_ACCESS_KEY" \
174aws s3api list-objects-v2 \
175 --bucket "$R2_BUCKET_NAME" \
176 --endpoint-url "https://${R2_ACCOUNT_ID}.r2.cloudflarestorage.com" \
177 --region auto
178```
179 
180> **Common mistake:** Omitting `--region auto` causes `InvalidRegionName` error. R2 valid regions: `wnam`, `enam`, `weur`, `eeur`, `apac`, `oc`, `auto`.
181 
182## Troubleshooting
183 
184### Force Image Pull
185 
186When you push a new Docker image version, RunPod may still use the cached old one. To force a pull:
187 
1881. Update the template's `imageName` to use `@sha256:DIGEST` notation
1892. Wait for the worker to restart
1903. Revert to `:latest` tag after confirming
191 
192### Cold Start Too Slow
193 
194- **qwen3-tts:** ~70s cold start, ~7s warm
195- **sadtalker:** ~60s cold start, ~10s warm
196- **image_edit:** ~90s cold start, ~15s warm
197 
198If cold starts are a problem, set `workersMin: 1` (costs money when idle).
199 
200### Job Fails with OOM
201 
202The model needs more VRAM than the GPU provides. Options:
203- Use a larger GPU tier
204- For dewatermark: reduce `--resize-ratio` (default 0.5 for safety)
205- For image_edit: reduce `--steps`
206 
207### "No workers available"
208 
209You've hit your plan's concurrent worker limit. Either:
210- Wait for a running job to finish
211- Set `workersMax=0` on endpoints you're not using
212- Upgrade your RunPod plan
213 
214## Docker Images
215 
216All Dockerfiles live in `docker/runpod-*/`. Images use `runpod/pytorch` as the base to share layers across tools.
217 
218Building for RunPod (from Apple Silicon Mac):
219```bash
220docker buildx build --platform linux/amd64 -t ghcr.io/conalmullan/video-toolkit-<name>:latest docker/runpod-<name>/
221docker push ghcr.io/conalmullan/video-toolkit-<name>:latest
222```
223 
224GHCR packages default to **private** — you must manually make them public for RunPod to pull them. Go to GitHub > Packages > Package Settings > Change Visibility.
225 
226## Cost Optimization
227 
228- Keep `workersMin: 0` on all endpoints (scale to zero)
229- Only deploy endpoints you actively need
230- Use `workersMax=0` to disable idle endpoints without deleting them
231- Qwen3-TTS is significantly cheaper than ElevenLabs for voiceovers
232- Check the RunPod dashboard for usage and billing
233 

Discussion

Alternatives

Also in Cloud & infraSee all 533 in Development →
Docker MCP gatewayDocker's own CLI plugin: run any server from the Docker MCP Catalog in its own container, behind one connection, with secrets kept out of env vars.Coding · MITTechnical Codebase Discovery & Onboarding PromptA prompt designed to guide a deep technical analysis of a code repository to accelerate developer onboarding. It instructs an AI to analyze the entire codebase and generate a structured Markdown document covering architecture, technology stack, key components, execution and data flows, integrations, testing, security, and build/deployment, serving as a technical reference guide.Coding · CC0-1.0NextflowBuild, run, and debug Nextflow data pipelines and nf-core workflows end to end. Use whenever the user mentions Nextflow, nf-core, .nf files, nextflow.config, DSL2, processes/channels/operators, samplesheets, or wants to run a community pipeline (e.g. nf-core/rnaseq, nf-core/sarek), write or test a module/subworkflow with nf-test, configure executors/containers (Docker, Singularity/Apptainer, Conda, Wave), scale a workflow to HPC/SLURM or cloud (AWS Batch, Google Batch, Azure, Kubernetes), or debug a failed/-resume run. Make sure to use this skill for any reproducible scientific/bioinformatics workflow work even if the user does not say the word "Nextflow", and for authoring nf-core-compliant pipelines, modules, configs, and linting.Science · MITCloud Cost OptimizationOptimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.Infrastructure & ops · MIT