By RunPod
RunPod — 🐍 | Python library for Runpod API and serverless worker SDK. Listed under Serverless GPU in the Compute / Cloud layer. 4 of 6 comparison attributes are recorded, each with the page it was read from.
AI infrastructure with on-demand GPUs and serverless compute. Run training, inference, and batch workloads on the cloud with Runpod.
2 OF 4 SIGNALS HELD · MISSING LICENCE, REPOSITORY
What it runs on, and what runs on it
0 cited edgesComputed from the stack graph, both directions. Every cited edge links the page it was read from; a vendor-added one links the vendor’s own source — this is the reason to be here rather than on the vendor’s own site.
No edges on record for RunPod.
Nothing in the directory documents depending on it, and its own docs do not name what it runs on. An edge is only stored when a source states it.
Submit a documented integration →From RunPod? No claim is needed for this: a link to your docs that names what RunPod runs on is enough.
Open-source signals
A HOLLOW RING IS UNMEASURED, NOT ZERO · WE DO NOT SUBSTITUTE A PARENT COMPANY’S REPOSITORY FOR A PRODUCT THAT HAS NONE
Price
READINGS OVER 21 DAYS OLD ARE HIDDEN RATHER THAN SHOWN STALE, SO THIS TABLE CAN EMPTY OUT BETWEEN READS · MOVED COMPARES THE CHEAPEST READING WE TOOK ON EACH DAY, WHICH ON A MARKETPLACE IS A DIFFERENT HOST FROM THE ONE PRICED BESIDE IT — BOTH ENDS ARE SHOWN SO NOTHING HAS TO BE INFERRED · A MOVE IS A CHANGE IN OUR READING, WHICH IS NOT ALWAYS A CHANGE IN THE MARKET: A CORRECTED EXTRACTOR MOVES THE SERIES WITHOUT THE PRICE MOVING
Configurations
RunPod publishes no machine-readable catalogue of its instance types, so no configurations are recorded. The prices above were read from its pricing page; a configuration read the same way would be a guess about how many GPUs a price covers, which is the mistake this section exists to avoid.
CONFIGURATIONS ARE TAKEN ONLY FROM A VENDOR’S OWN CATALOGUE API · IF YOU WORK HERE AND PUBLISH ONE, TELL US AND IT WILL BE READ
What its categories ask
4 answered · 2 unanswered6 questions declared by Serverless GPU. Most rows across the directory read like these.
“All run on the same GPU catalog (H100 80GB HBM3, H100 NVL, A100, L40S, and more) accessible on-demand with no contracts or minimum commitments.”2026-09-12
“Deploy globally with a few clicks. Run workloads across 31 global regions worldwide, with low-latency performance and global reliability.”2026-09-12
“@Endpoint( name="batch-job", gpu=GpuType.NVIDIA_GEFORCE_RTX_4090, # Cost-effective GPU workers=(0, 5), # Scale to zero, controlled max idle_timeout=300, # 5 minutes - fast scale-down volume=NetworkVolume(name="my-volume") # Avoid re-downloading models ) ”2026-10-06
A ROW WITH NO ANSWER IS NOT A ROW WITH A “NO” · A VENDOR MAY ANSWER A BLANK ONE, MARKED VENDOR CLAIMED WITH ITS SOURCE · A DOCUMENTED VALUE IS DISPUTED, NOT OVERWRITTEN, AND STAYS VISIBLE WHILE WE RE-READ THE SOURCE
Practitioner reviews
Nobody has written one yet.
A review here is structured, not a star: hardware, scale band, what broke in production, and whether you would choose it again.
NO PERCENTAGE IS SHOWN UNDER FIVE REVIEWS · NO STAR RATINGS, EVER
Also in this category
6 products in Serverless GPU. Comparison defaults to within the category — pairing this with a GPU cloud would produce a page that means nothing.
USED BY = LISTED PRODUCTS DEPENDING ON IT, IN THIS DIRECTORY
Frequently asked
How much does RunPod charge for RTX-A4000-16GB?
Does RunPod offer scale to zero?
How current are RunPod's prices here?
What does a blank mean on the RunPod page?
Where do the RunPod figures come from?
Can RunPod change what this page says?
Something here is wrong — how do I fix it?
Is this listing run by RunPod?
Cite this page
A model that quotes us should quote us correctly. The reading and its date sit inside the citation rather than beside it, because a quotation carrying only a URL goes wrong the week the URL changes.
infratoapp, “RunPod — Serverless GPU”, read 27 October 2026. Price $1.79/gpu-hour as published at runpod.io. https://www.infratoapp.com/products/runpod
What RunPod can and cannot change here
Claiming RunPod lets its admins and editors change the tagline, description, logo, docs link and deployment model of every product that org owns — live, labelled as theirs, and logged. Answers to blank questions and dependencies go live too, marked as the owner’s and sourced; a documented answer cannot be overwritten. Everything else on this page is a stated fact with a dispute route: price, licence and OSS figures. Those columns are ungranted at the database level, so they are not a feature we withheld — they are a write that cannot happen. Name, category, website, pricing page and package names can be changed by the owner only through our review. A dispute never deletes a value; it marks it and publishes the correction.