Head to head · GPU compute · October 2026 research run

Baseten vs Replicate Deployments

Replicate Deployments scores 67 (B) on agent readiness against Baseten's 65.2 (B), and leads in 3 of 7 scored categories. Baseten leads on reliability, security & auth, payments & pricing and maintenance & community. Both do gpu compute.

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

Which one, for what

Baseten B

Best for Teams that want one model behind a production endpoint with real autoscaling knobs, environments and scoped keys.

Ahead on

  • Reliability, 90 against 75
  • Security & auth, 82 against 40
  • Payments & pricing, 60 against 45
  • Maintenance & community, 90 against 78

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

H100 at $6.50 and A100 at $4.00 an hour, and start-up and idle replica time are billed

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

  • Agent ergonomics, 73 against 55
  • Transparency & trust, 79 against 67

Also in its favour

  • Runs on your own machine
  • No incidents deducted, where Baseten loses 11 points for them

Watch for

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

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 Baseten +42

Baseten 82

Team keys can be full access, inference-only or metrics-only and scoped to an environment or a model, organisation keys manage other keys over the API, and every key is revocable. Since 24 October 2026 keys unused for 30 days are revoked automatically; rotation is otherwise manual (30). Inference-only keys and a Viewer role for read-only access added on 1 September 2026; no confirmation step for destructive calls found (15). Returns your own model's output, no third-party content (10). Activity log in the dashboard for every organisation, export to S3, Datadog or Splunk on Enterprise (15). Coordinated disclosure to security@baseten.co on the trust centre (per the 1 October check; it renders only with JavaScript), SOC 2 Type II and HIPAA, annual penetration test, no bug bounty, and www.baseten.co/.well-known/security.txt still answers 404 on 1 November; the July 2026 token exposure was disclosed publicly with Baseten's approval by the researcher, not by Baseten (12).

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.

Agent ergonomics Replicate Deployments +18

Baseten 55

No field selection, limits or summaries found on list endpoints; responses are small resource objects (10). No pagination parameters on list endpoints such as /v1/models or /v1/secrets (5). The inference error page maps each code to a cause and says which to retry with exponential backoff (20). No idempotency keys; only per-deployment retry endpoints and async requests that can be polled (5). Sensible defaults (min_replica 0, max_replica 1) and official clients in Python (Truss, CLI 1.0.0) and JavaScript (performance client on npm) (15).

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.

Reliability Baseten +15

Baseten 90

Atlassian Statuspage at status.baseten.co with incident history (20). Its history pages list 27 incidents from 3 August to 1 November 2026, 7 of them labelled major, plus three scheduled database upgrades. Every one is scoped to one Model API model, one cluster or region, or a subset of models, the longest labelled major being the Kimi K3 Model API for 54 minutes on 20 September, so all read as partial and minor (20). The management API rate-limits page gives per-endpoint numbers (20 a minute for activate and deactivate, 10 a minute for retry, 30 a second for logs) and the async limit stays at 12,000 a minute per the 1 October check (15). 429 returns retry_after with an instruction to back off on it, and 529 honours Retry-After (15). A public Service Level Agreement, part of the Terms and dated 15 September 2026 in its body (15 September 2025 in the page header), commits to 99.9 per cent monthly availability for Dedicated Inference and Model APIs on Baseten-managed infrastructure, with service credits up to 40 per cent on request within 24 hours; the 1 October check missed it (10). Dedicated deployments are GA (10). 20 + 20 + 15 + 15 + 10 + 10 = 90.

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.

Payments & pricing Baseten +15

Baseten 60

No machine payment protocol (0). Per-minute GPU prices from $0.01052 (T4) to $0.16633 (B200) published without a login (20). New workspaces get credits and no payment method is needed until they run out, at which point models are deactivated (20). Signup is a browser flow (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

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.

Maintenance & community Baseten +12

Baseten 90

A changelog entry on 30 October 2026 (mixed-mode rolling promotions) and Truss v0.18.37 tagged on 29 October (30). In the 90 days from 3 August, 13 stable Truss tags (v0.18.25 on 3 August to v0.18.37) and 31 dated changelog entries from 14 August to 30 October (20). Truss had 9 open issues, the recent ones answered within days, but a 24 August request for a private security contact had one reply and two January 2026 deployment issues sat unanswered, per the 1 October check; GitHub's pages weren't readable on 1 November (18). Truss, the Baseten CLI (v1.4.1 on 22 October) and a JavaScript client are current (15). Release workflow runs in GitHub Actions and Truss supports Python 3.9 to 3.14, but an open issue reports the npm performance client shipping without its platform dependencies since 0.0.10, per the 1 October check (7). 30 + 20 + 18 + 15 + 7 = 90.

Replicate Deployments 78

Cog, the listing's repository, tagged v0.23.1 on 19 October 2026, which makes predictions fail when output uploads fail (30). Cog tagged v0.22.0 on 13 August, v0.23.0 on 22 September and v0.23.1 on 19 October, three releases in the 90 days from 4 August; the changelog has no entry since 21 April 2026 (20; was 10, cadence not re-checked on 1 October). Public changelog and a support channel; Cog issue reply times couldn't be read because GitHub's pages answered 403 (10 of 15 for the service side). Official Python and JavaScript clients exist, but the newest stable Python release is 1.0.7 (27 May 2025) with 2.0 betas to 18 December 2025, and the JavaScript client's newest tag is 1.4.0 (17 November 2025). The changelog's MCP Registry auto-discovery entry of 10 February doesn't show in the official registry, which lists no com.replicate server on 2 November (10 of 15; was 15). Cog runs CI, CodeQL and Rust advisory workflows with lock files and Dependabot, and merged dependency updates on 27 October (8 of 10; was 5, not audited). 30 + 20 + 10 + 10 + 8 = 78.

Transparency & trust Replicate Deployments +12

Baseten 67

Hosted service is closed under clear California terms; Truss, the packaging tool, is MIT (20). The docs say inputs, outputs and weights aren't stored by default, async inputs are kept only while processing, and the privacy policy hands customer content to a published DPA; retention periods are given as 'as long as necessary' and audit-log retention is 'contact support' (22). Model API deprecations carry dates, and a published policy promises 30 days' notice, but recent notices fell short of it (8 July for 24 July, 16 days; 13 September for 25 September, 12 days). No deprecation policy for dedicated deployments found (8). Regions can be listed over the API and EU transfers use SCCs, but no subprocessor list found (8).

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.

Score by category

CategoryWeightBasetenReplicate DeploymentsEdge
Reliability16%9075Baseten +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8485Replicate Deployments +1
Agent ergonomics13%5573Replicate Deployments +18
Security & auth14%8240Baseten +42
Payments & pricing10%6045Baseten +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9078Baseten +12
Transparency & trust7%6779Replicate Deployments +12
Negative events≤15-110
TotalB 65.2/100B 67/100

Facts side by side

FactBasetenReplicate Deployments
KindHTTP APIHTTP API
VendorBasetenReplicate (Cloudflare)
Hosted endpointhttps://api.baseten.cohttps://api.replicate.com/v1
TransportsHTTPHTTP, SSE (legacy), stdio
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-302026-10-19
Terms last updatedno date given2026-04-01
Privacy policy last updatedno date given2026-04-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity1.2k stars, 74k PyPI/wk9.5k stars, 634k npm/wk, 387k PyPI/wk
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Baseten higher, the other way from the total score.

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

Baseten

Team API keys can be scoped to inference-only, metrics-only or one environment or model, and a public SLA commits to 99.9 per cent. Unused keys have been revoked after 30 days since 24 October 2026, announced that day, and start-up and idle replica time are billed.

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.

Before you call either

Baseten

  1. Create a team key with inference-only permission for calling models and keep full-access keys out of the agent
  2. Sleep for retry_after seconds on a 429 from api.baseten.co; the activate and deactivate endpoints allow 20 calls a minute
  3. Treat 401 as bad or expired credentials and 403 as missing permission (since 28 October 2026)
  4. Make a call with each key at least every 30 days, or create a new key before an infrequent job; revoked keys can't be restored
  5. Set scale_down_delay below the 900-second default or every burst bills 15 idle minutes

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

Questions

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

Replicate Deployments scores 67 (B) on agent readiness against Baseten's 65.2 (B), and leads in 3 of 7 scored categories. Baseten leads on reliability, security & auth, payments & pricing and maintenance & community.

Do Baseten and Replicate Deployments need an API key?

Both need an API key.

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

Yes. Baseten has a hosted endpoint at https://api.baseten.co and Replicate Deployments at https://api.replicate.com/v1.

Are Baseten and Replicate Deployments open source?

Yes. Baseten is open source (MIT). Replicate Deployments is open source (Apache-2.0).

Other comparisons with Baseten or Replicate Deployments

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.