Head to head · GPU compute · October 2026 research run

Replicate Deployments vs Runpod

Replicate Deployments scores 67 (B) on agent readiness against Runpod's 56.9 (C), and leads in 5 of 7 scored categories. Runpod leads on security & auth. Both do gpu compute.

Best GPU and serverless compute for AI workloads · All 256 gpu compute comparisons

Which one, for what

Replicate Deployments B

Best for Teams already calling Replicate's public models who want their own model behind the same API, MCP server and webhooks.

Ahead on

  • Reliability, 75 against 57
  • Agent ergonomics, 73 against 62
  • Payments & pricing, 45 against 30
  • Transparency & trust, 79 against 64

Also in its favour

  • Open source
  • No incidents deducted, where Runpod loses 6 points for them

Watch for

Private instances bill set-up and idle time, H100 at $5.49 an hour

Runpod C

Best for Cost-sensitive inference and batch work that wants the widest GPU choice, from consumer cards to B300, with an MCP control plane.

Ahead on

  • Security & auth, 67 against 40

Watch for

Data-centre outages of 6 to 24 hours in each of July, August and September 2026, per the 1 October check

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth Runpod +27

Replicate Deployments 40

Bearer tokens starting r8_, several per account, each can be disabled; no scopes or expiry, re-read on 2 November (20). No read-only or per-model token; every token can create, update and delete deployments (0). Returns your own model's output (10). No audit log or per-token usage view found; predictions are listed per account (5). Replicate scans public GitHub for leaked tokens, disables them and emails the owner. replicate.com/.well-known/security.txt answers 404, and no bug bounty or certification was found in the docs we read. OSV lists no advisory for the replicate packages, replicate-mcp or Cog (5). 20 + 0 + 10 + 5 + 5 = 40.

Runpod 67

API keys can be All, Read Only or Restricted per serverless endpoint, and can be disabled or deleted; the hosted MCP signs in with OAuth. The GraphQL docs still show the key as ?api_key= in the URL per 1 October, which costs 10 (20). Read-only keys and per-endpoint restrictions, and the REST v2 file names a read or write scope for each operation; no confirmation for destructive calls found (15). Runs your own containers and returns their output (10). REST v2 now lists GET /v2/audit-logs (scope audit:read), an account or organisation audit trail of who acted on which resource, with filters and a retention window; no per-call API request log (12). security.txt valid until 31 January 2027, and the trust centre lists SOC 2 Type 2, SOC 3, ISO 27001 and HIPAA, per 1 October; no bug bounty, and osv.dev lists no advisory for runpod (10). 20 + 15 + 10 + 12 + 10 = 67.

Reliability Replicate Deployments +18

Replicate Deployments 75

Replicate incidents post under a Replicate component on cloudflarestatus.com, and replicatestatus.com redirects to that page filtered to Replicate (20). The component's 90-day bars, read on 2 November, show 5 days with incidents, all in September 2026, and none since 28 September. Some third-party models couldn't scale out for 15 hours 41 minutes on 14 and 15 September, a Pruna-specific issue ran 20 hours on 17 September, backend services returned intermittent 500s for 1 hour 54 minutes on 24 September, and hot-swapped Flux models stuck for 17 minutes on 28 September. Each names a subset of models or intermittent errors, so each reads as partial, minor only (20). 600 prediction creates a minute, 3,000 a minute on other endpoints, and 6 a minute without a card, re-read on 2 November (15). A 429 body says when the limit resets ('resets in ~30s') and the error-code page gives retry advice per code, but there's no Retry-After header or idempotency guidance (10 of 15). No SLA found (0). Deployments are GA (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

Runpod 57

Better Stack page at uptime.runpod.io with per-service and per-region history, per the 1 October check, not re-read on 4 November (Runpod's terms bar automated access to runpod.io and its subdomains) (20). Incident line kept at 0. The 1 October reading counted several majors, among them US-IL-1 without power for 6 hours 10 minutes on 14 and 15 August and serverless API errors for 1 hour 25 minutes on 6 September. The window since 1 October is unread, so the recorded award stands (0). The REST v2 OpenAPI file, in the copy Runpod keeps in its MCP repository (synced with production on 27 October), says limits are per user across every /v2 route, with minute, hour and day windows, and gives "minute";q=180;w=60, "hour";q=3600;w=3600, "day";q=43200;w=86400 as the policy header (15). The same file documents 429 with Retry-After and RateLimit headers, and the Python SDK's error guide (2.1.0, 3 November) honours Retry-After, backs off with jitter and does not retry other errors because a failed response can follow a successful mutation. Safe-retry guidance with no idempotency keys (12). No SLA found (0). Serverless and REST v2 are GA; batch jobs are beta (10). 20 + 0 + 15 + 12 + 0 + 10 = 57.

Payments & pricing Replicate Deployments +15

Replicate Deployments 45

No machine payment protocol (0). Per-second prices for each hardware SKU published without a login, re-read on 2 November, now with a small CPU tier at $0.09 an hour and H200 SKUs on committed-spend contracts (20). Accounts without a card can run predictions at up to 6 a minute; private deployments still bill set-up and idle time (10 of 20). Signup is a browser flow (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Runpod 30

Per the 1 October check, not re-read on 4 November (terms bar automated access to runpod.io). No machine payment protocol (0). Per-second serverless and per-hour pod prices published without a login (20). No free tier; prepaid credit only (0). Signup is a browser flow; the MCP's OAuth still needs an account (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Transparency & trust Replicate Deployments +15

Replicate Deployments 79

Closed service; Cog is Apache-2.0 (20). API prediction inputs, outputs, files and logs are deleted after one hour by default, web predictions are kept until deleted, and a subprocessor page is published, per the 1 October check, not re-read on 2 November (22). Dated deprecations in the changelog (streaming default in July 2024, spend limits in July 2025) but no written policy (12). Subprocessors listed; data locations not stated in what we read (15). 20 + 22 + 12 + 15 = 69.

Runpod 64

Per the 1 October check, not re-read on 4 November (terms bar automated access to runpod.io). Closed service under Delaware terms; the Python SDK is MIT (20). Sync results are kept 1 minute and async 30 minutes, and the docs claim GDPR compliance for EU regions, but no retention periods for pod disks or volumes after deletion and the DPA sits behind trust-centre access (15). Dated notices, REST v1 retiring on 15 November 2026 (announced 18 August) and GraphQL in early 2027; one model endpoint got two weeks' notice (15). 31 regions named with data-centre codes; subprocessor list not found (10).

Agent ergonomics Replicate Deployments +11

Replicate Deployments 73

The MCP server exposes one tool per HTTP operation and has an experimental code mode that collapses them into two tools (search the SDK docs, run TypeScript) (20). List responses page with next and previous cursor URLs, the predictions list filters by created_after, created_before and source, and the models list sorts, but there is no page size or field selection (15 of 20; was 10, pagination not verified on 1 October). Coded errors with suggested fixes, detail messages on HTTP errors (15). No idempotency keys; Prefer: wait, a Cancel-After header, webhooks and cancel cut polling, and a failed run still bills its active time (8). Sensible defaults (min_instances 0 allowed) and official Python and JavaScript clients plus Cog (15). 20 + 15 + 15 + 8 + 15 = 73.

Runpod 62

Results can be streamed in chunks of up to 1 MB and polled by job ID, and include sizes some REST v2 responses (12). REST v2 list calls take an opaque cursor with limit (1 to 1,000, 100 for builds, 200 for audit logs) and filters such as actor, action and time on audit logs, per the OpenAPI file in Runpod's MCP repository (20). No error codes or messages documented for serverless operations, per 1 October (5). /retry, /cancel and /purge-queue give safe recovery for jobs, and the MCP server marks destructive tools. No idempotency keys (10). FlashBoot on by default, Python and JavaScript SDKs, the Flash SDK and an official MCP server (15). 12 + 20 + 5 + 10 + 15 = 62.

Score by category

CategoryWeightReplicate DeploymentsRunpodEdge
Reliability16%7557Replicate Deployments +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8581Replicate Deployments +4
Agent ergonomics13%7362Replicate Deployments +11
Security & auth14%4067Runpod +27
Payments & pricing10%4530Replicate Deployments +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7882Runpod +4
Transparency & trust7%7964Replicate Deployments +15
Negative events≤150-6
TotalB 67/100C 56.9/100

Facts side by side

FactReplicate DeploymentsRunpod
KindHTTP APIHTTP API
VendorReplicate (Cloudflare)Runpod
Hosted endpointhttps://api.replicate.com/v1https://api.runpod.ai/v2
TransportsHTTP, SSE (legacy), stdioHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPay per usePay per use
x402nono
LicenceApache-2.0MIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-192026-11-03
Terms last updated2026-04-012026-03-24
Privacy policy last updated2026-04-012025-08-07
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity9.5k stars, 634k npm/wk, 387k PyPI/wk314 stars, 22k npm/wk
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Replicate Deployments

OpenAPI file, llms.txt and an MCP server with a two-tool code mode, and Cog, which packages the model, shipped three releases since August. Private instances bill set-up and idle time, H100 at $5.49 an hour, and the changelog has been silent since April 2026.

Runpod

Per-second billing across more than a dozen serverless GPU classes, with a REST v2 contract that documents rate limits, 429 handling and cursor pagination. Data-centre outages ran 6 to 24 hours in July, August and September 2026, and two minor releases in late October and early November changed CLI and MCP behaviour without notice.

Before you call either

Replicate Deployments

  1. List GET /v1/hardware first and use the returned sku in the deployment body
  2. Set min_instances to 0 for bursty work; a warm H100 bills $5.49 an hour whether called or not
  3. Send Prefer: wait on deployment predictions to block instead of polling
  4. Copy outputs within an hour; API prediction data is deleted after that
  5. Wait for the reset time in the 429 body before retrying; prediction creates cap at 600 a minute

Runpod

  1. Create a Restricted or Read Only key per endpoint for the agent, not an All key
  2. Use REST v2 at api.runpod.io/v2 with a Bearer header; avoid GraphQL, which puts the key in the URL, and read quotas from the RateLimit-Policy header
  3. Fetch /run results within 30 minutes and /runsync results within 1 minute, or they're gone
  4. Call /retry on a failed job ID rather than submitting a duplicate job
  5. Check /health before relying on an endpoint idle for a week, since max workers drop to 0
  6. Set RUNPOD_API_KEY or pass --api-key when running rp login without a terminal; since runpod 2.1.0 it fails fast otherwise

Questions

Which is better for AI agents, Replicate Deployments or Runpod?

Replicate Deployments scores 67 (B) on agent readiness against Runpod's 56.9 (C), and leads in 5 of 7 scored categories. Runpod leads on security & auth.

Do Replicate Deployments and Runpod need an API key?

Replicate Deployments needs an API key. Runpod takes an API key or an OAuth sign-in.

Can an agent call Replicate Deployments and Runpod without installing anything?

Yes. Replicate Deployments has a hosted endpoint at https://api.replicate.com/v1 and Runpod at https://api.runpod.ai/v2.

Are Replicate Deployments and Runpod open source?

Replicate Deployments is open source (Apache-2.0). No open-source release is listed for Runpod.

Other comparisons with Replicate Deployments or Runpod

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.