Runpod

HostedGPU cloud

The AI Developer Cloud

Homepage Docs Pricing Repository

Scanned 15 Oct 2026 · Schema v5 · features v21

From: —
Usage-based prepaid credits; enterprise post-paid contract option (beta); per-second compute, separate storage and request charges.
Free tier: No
No card required.
Isolation: Container
shares the host kernel
Regions: 16
Czech Republic · France · Netherlands · Romania · Sweden · Iceland +10
Capabilities: 21 / 61
6 partial · 29 fail · 0 not assessed
Agent readiness: 11/11 · 11/11
read · drive, pre-login surface

Advertised for

AI inference · AI training · Fine tuning · Distributed training · Batch jobs · Model serving

Built for

Developers, then technical

· Docker/GitHub workers, CLI, API v2, SDKs and agent plugins
· Per-second GPU and per-operation storage pricing

01 Pricing Usage-based prepaid credits; enterprise post-paid contract option (beta); per-second compute, separate storage and request charges.

Tier	EntryPods — On-demand GPU (Secure Cloud)	Serverless (flex/active workers)	Instant Clusters	TopReserved Clusters / Enterprise
Price	Secure Cloud listed examples: RTX A5000 $0.27/hr, RTX 4090 $0.89/hr, H100 PCIe $2.89/hr, H100 SXM $3.99/hr, H200 $5.29/hr, B200 $7.99/hr, B300 $8.99/hr	Serverless listed flex examples: 4090 $1.10/hr, A100 $2.72/hr, RTX 6000 Pro $3.49/hr, H100 $4.79/hr, H200 $5.93/hr, B200 $8.64/hr, B300 $9.98/hr	Multi-node, up to 64 GPUs, per-second: H200 SXM $4.31/hr, A100 SXM $1.79/hr; L40S / H100 SXM / B200 contact-sales	Contact sales — 1/3/6/12mo+ commitments, scale to 10,000+ GPUs, SLA-backed uptime, discounted rates
Includes	GPU container with optional persistent storage; SSH and HTTP/TCP connectivity; storage billed separately.	Autoscaling GPU endpoint; zero active workers allows scale-to-zero, with storage billed independently.	Launch multi-GPU clusters in minutes, no commitment; attach shared storage; pay only for what you use.	Dedicated clusters, guaranteed availability, custom configs, enterprise discounts, business invoicing.
GPU hours overage	$2.89/h	$4.79/h	$4.31/h	—
Storage overage	$0.07/GB	—	—	—

GPU-hour (per GPU type, billed per second); storage GB-month; Public Endpoints per token / per request / per character / per megapixel / per second·Card required: No·docs.runpod.io

Overages: Pods listed $0.27–$8.99/GPU-hour; Serverless listed $0.58–$9.98/GPU-hour. Storage and beta global-volume request charges separate; no data transfer fees.

02 Website design Desktop public website · assessed 15 Oct 2026

Complete assessment.

Dark purple marketing pages combine luminous calls to action and a platform diagram with spacious centered pricing copy. Documentation switches to a white, structured sidebar-and-card reading layout. All three desktop roles captured; cookie overlays remain visible.

Corporate
Technical illustration

Landing page: captured
Pricing: captured
Docs: captured

03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Containershares the host kernel

Persistence

Volume disk survives stop/restart but not Pod deletion; network volumes are independently persistent. Beta global volumes persist across Pod/worker deletion and are region-independent; object-backed, limited POSIX semantics.

Snapshots / forks

Resources & limits

Storage

Container/volume disk $0.10/GB-month running; stopped volume disk $0.20; standard network volumes $0.07/GB-month below 1TB and $0.05 above; high-performance $0.14. Beta global volumes also bill Class A $0.005/1000 and Class B $0.0005/1000 requests.

Limits & quotas

Default account spend cap $80/hour; new Pod needs at least one hour of selected configuration credits. Serverless operation-specific rate limits; job TTL and execution timeout max 7 days. Network volumes can be deleted on unpaid balance; global volume deletion after 15 days at $0. Cluster capacities differ by offering; enterprise page advertises 200+ on-demand / 10,000 reserved while pricing table still says 64.

GPU

Yes

Access

Deploy interface

container-imagedockerfilegit-pushclisdkapimcpdashboardtemplate

SDK languages

PythonJavaScriptGo

Network & secrets

Egress controls

Secrets

Runpod Secrets — securely store and manage API keys, passwords, and tokens; injected into Pods/endpoints as environment variables

Bring your own cloud

partial

Placement & use

Jurisdiction

31 global regions; customer-selectable placement; compliance varies by data center.

Advertised workloads

AI inferenceAI trainingFine tuningDistributed trainingBatch jobsModel serving

04 Capabilities 21 pass · 6 partial · 29 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 6/11

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Supported

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Not supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Not supported

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Supported

GPU computeGPU-backed instances available.

Supported

Multi-regionCompute placeable in more than one geographic region.

Supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Supported

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not supported

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not supported

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not supported

Networking & delivery 3/8

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Supported

Custom domainsBring-your-own domain via CNAME/DNS.

Not supported

Public preview URLsShareable per-deploy / per-branch URLs.

Partially supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not supported

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Not supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Supported

Email send / receiveSend and/or receive email from the workload.

Not supported

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Not applicable

Developer access 6/9

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Supported

SSH accessDirect SSH into workloads.

Supported

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Partially supported

Git deployDeploy from a Git repo / push-to-deploy.

Supported

Private container registryHosted private image registry.

Not supported

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not supported

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Not applicable

AI & agents 3/12

Built-in coding agentShips a first-party AI coding agent in the product.

Not supported

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Not supported

MCP serverExposes a Model Context Protocol server for agents.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Not supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Not supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Not supported

BYOK for LLMsBring-your-own LLM provider keys.

Not supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Not supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Not supported

Data 0/1

First-party databasePlatform-provided managed database.

Not supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Not applicable

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Not applicable

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not applicable

Platform & operations 1/6

Scheduled tasksCron / scheduled job primitive.

Not supported

Durable workflowsDurable execution / long-running workflow primitive.

Not supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Not supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not supported

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Not supported

Organisation & security 2/9

Built-in authPlatform-provided authentication / IAM for workloads.

Partially supported

SSO / SAMLEnterprise single sign-on.

Partially supported

Secrets managementFirst-class secrets storage / injection.

Supported

TeamsMulti-user team accounts.

Supported

SharingShare a running workload/resource via link (optionally gated).

Partially supported

BYOCRuns inside the customer's own cloud account.

Partially supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Not supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Not supported

Proposed, not verified

Capabilities the scan saw but the registry does not track yet. A key is admitted only once two distinct products exhibit it. These are not scored.

Hybrid Cloud owned-capacity orchestrationhybrid-compute-orchestration
“Your hardware first, Runpod cloud for overflow; limited access with annual management fees.” runpod.io

05 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

11/11

7 full · 4 partial · 100% of applicable checks

llms.txt
Supported
“Substantive apex llms.txt and 82KB docs llms.txt. Source: https://www.runpod.io/llms.txt; confidence: high.”
llms-full.txt
Supported
“Comprehensive 1,817,476-byte docs export retained as bounded POINTER. Source: https://docs.runpod.io/llms-full.txt; confidence: high.”
robots.txt AI policy
Partially supported
“User-agent: * Allow: / # Content Signals (https://contentsignals.org/): # allow search and AI assistant use of this content, disallow AI training. Content-Signal: search=yes, ai-input=yes, ai-train=no # Pagination variants (*_page params) are crawlable ON PURPOSE: # a head script serves noindex,follow for them so Google deindexes # the leaked variants. Do not re-add Disallow rules for *_page until # GSC "Indexed, though blocked by robots.txt" reaches 0. # LLM discovery file # For language model indexing, see: # https://www.runpod.io/llms.txt Sitemap: https://www.runpod.io/sitemap.xml Source: https://www.runpod.io/robots.txt; confidence: high.”
JSON-LD
Partially supported
“WebPage graph, ImageObject and breadcrumbs; no Product with offers. Source: https://www.runpod.io/; confidence: high.”
Sitemap
Supported
“215,856-byte sitemap with many URLs; bounded POINTER retained. Source: https://www.runpod.io/sitemap.xml; confidence: high.”
Meta tags
Supported
“Descriptive title, description and OpenGraph tags in homepage HTML. Source: https://www.runpod.io/; confidence: high.”
Markdown negotiation
Supported
“Accept: text/markdown returns clean markdown on docs API overview; apex still HTML. Source: https://docs.runpod.io/api-reference-v2/overview.md; confidence: high.”
Content efficiency
Partially supported
“Readable text bytes / raw HTML bytes = 11930/309251 = 3.858%. Source: https://www.runpod.io/; confidence: high.”
Docs discoverable
Supported
“Docs is a first-class header navigation link. Source: https://www.runpod.io/; confidence: high.”
Machine-readable pricing
Supported
“Structured GPU, Serverless, cluster and storage pricing tables; updated October 8, 2026. Source: https://www.runpod.io/pricing; confidence: high.”
No anti-bot wall
Partially supported
“Ordinary public fetches and rendered retries succeeded; apex Accept:text/markdown request returned HTTP 403, then foxcrawl retry succeeded. Intermittent/request-specific restriction. Source: https://www.runpod.io/; confidence: high.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

11/11

7 full · 4 partial · 100% of applicable checks

Public API
Supported
“REST API v2 documented; v1 retires November 15, 2026. Source: https://docs.runpod.io/api-reference-v2/overview.md; confidence: high.”
OpenAPI spec
Supported
“Fetchable valid OpenAPI v2 spec; 274,963 bytes retained POINTER. Source: https://api.runpod.io/v2/openapi.json; confidence: high.”
MCP server
Supported
“Hosted https://mcp.getrunpod.io/ and installable @runpod/mcp-server; docs MCP separately. Source: https://docs.runpod.io/get-started/mcp-servers.md; confidence: high.”
SDK packages
Supported
“Official Python, JavaScript and Go SDKs. Source: https://docs.runpod.io/serverless/sdks.md; confidence: high.”
Auth documented
Supported
“API keys, scopes, SSH and S3 credentials explicitly documented. Source: https://docs.runpod.io/get-started/credentials.md; confidence: high.”
Self-serve credentials
Partially supported
“Dashboard-issued API keys; hosted MCP OAuth requires browser sign-in/approval; no unattended issuance documented. Source: https://docs.runpod.io/get-started/mcp-servers.md; confidence: high.”
Webhooks
Partially supported
“Webhook job completion callback, 200 acknowledgment and retries documented; signing not evidenced. Source: https://docs.runpod.io/serverless/endpoints/send-requests.md; confidence: high.”
CLI tool
Supported
“Official runpodctl CLI documented with installation and resource management commands. Source: https://docs.runpod.io/get-started/agent-skills.md; confidence: high.”
Error model
Supported
“REST v2 errors use RFC 9457 title, status, detail and optional validation errors array. Source: https://docs.runpod.io/api-reference-v2/migrate-from-v1.md; confidence: high.”
Rate limits documented
Partially supported
“Operation-specific limits and dynamic worker-based limits; 429 documented, response headers not established. Source: https://docs.runpod.io/serverless/endpoints/send-requests.md; confidence: high.”
Agent config files
Partially supported
“Installable official skills/plugin, plus one-shot agent setup; no multiple distinct standard discovery surfaces proven. Source: https://docs.runpod.io/agent-setup.md; confidence: high.”

06 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 8

Claude Code Anthropic
Supported
“Supported clients: Claude Code, Codex CLI, Cursor, VS Code with Copilot, Windsurf, Cline, Gemini CLI.”
Source docs.runpod.io
Codex CLI OpenAI
Supported
“Supported clients: Claude Code, Codex CLI, Cursor, VS Code with Copilot, Windsurf, Cline, Gemini CLI.”
Source docs.runpod.io
Cursor Anysphere
Supported
“Supported clients: Claude Code, Codex CLI, Cursor, VS Code with Copilot, Windsurf, Cline, Gemini CLI.”
Source docs.runpod.io
GitHub Copilot GitHub
Supported
“Supported clients: Claude Code, Codex CLI, Cursor, VS Code with Copilot, Windsurf, Cline, Gemini CLI.”
Source docs.runpod.io
Windsurf Codeium
Supported
“Supported clients: Claude Code, Codex CLI, Cursor, VS Code with Copilot, Windsurf, Cline, Gemini CLI.”
Source docs.runpod.io
Cline Cline
Supported
“Supported clients: Claude Code, Codex CLI, Cursor, VS Code with Copilot, Windsurf, Cline, Gemini CLI.”
Source docs.runpod.io
Gemini CLI Google
Supported
“Supported clients: Claude Code, Codex CLI, Cursor, VS Code with Copilot, Windsurf, Cline, Gemini CLI.”
Source docs.runpod.io
OpenCode opencode
Supported
“Configure OpenCode to use Runpod Public Endpoints as the model provider.”
Source docs.runpod.io

Plausible compatibility 11

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

Aider
Amp
Antigravity
Devin
Droid
Goose
Hermes Agent
Kilo Code
Kiro CLI
Pi
Qwen Code

07 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 6

ISO/IEC 27001
certifiedhosted
“Runpod holds ISO/IEC 27001:2022”
Source trust.runpod.ioConfidence: high
SOC 2 Type II
certifiedhosted
“Runpod holds SOC 2 Type 2”
Source trust.runpod.ioConfidence: high
HIPAA
self-attestedhosted
“maintains active HIPAA and GDPR programs”
Source trust.runpod.ioConfidence: high
NIS 2
self-attestedhosted
“Documents: NIS2 Management Attestation Letter”
Source trust.runpod.ioConfidence: high
SOC 3
certifiedhosted
“Runpod holds SOC 3”
Source trust.runpod.ioConfidence: high
GDPR
self-attestedhosted
“maintains active HIPAA and GDPR programs”
Source trust.runpod.ioConfidence: high

Regions 16

Czech RepublicEU-CZ-1
FranceEU-FR-1
NetherlandsEU-NL-1
RomaniaEU-RO-1
SwedenEU-SE-1
IcelandEUR-IS-2
AustraliaOC-AU-1
CaliforniaUS-CA-2
GeorgiaUS-GA-1
GeorgiaUS-GA-2
IllinoisUS-IL-1
KansasUS-KS-2
North CarolinaUS-NC-1
TexasUS-TX-3
TexasUS-TX-4
WashingtonUS-WA-1

Homepage advertises 31 regions. Listed entries are the documented 17-data-center PRIVATE NETWORKING subset, not an exhaustive compute region inventory. Iceland is not an EU member.

Legal

Privacy notice Terms of service

08 Company & presence Facts only, not scored

Company

Headquarters: 329 Bryant St #4D, San Francisco, CA 94107 (published address; headquarters designation not explicit)
Founded: 2022 — co-founders Zhen Lu (CEO) and Pardeep Singh (CTO), ex-Comcast developers
Team size: Not disclosed
Hiring: Hiring; 31 roles displayed across six functions

Funding

2024-05Seed · $20M
2026-06-24Growth investment led by Summit Partners · $100M

Notable people

Zhen Lu (co-founder, CEO)
Pardeep Singh (co-founder)
Brian Erickson (CFO, appointed October 13, 2026)
Michael Medici (Summit Partners; joining board announced June 24, 2026)

Activity

Last release: 2026-10-13 docs.runpod.io
Last blog post: — runpod.io

Presence 4

Links found on the public surface scanned; not an exhaustive search.

09 Sources & method How this entry was produced

Public surface only

Everything here was read from runpod.io's unauthenticated pages, docs, pricing and repository on 15 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All GPU cloud products →