# Replicate Deployments vs Thunder Compute

> Replicate Deployments scores 63.6 (B) on agent readiness against Thunder Compute's 56.1 (C), and leads in 5 of 7 scored categories. Thunder Compute leads on security & auth and maintenance & community. Both do compute gpu. Category scores, facts, verdicts and agent notes side by…

- Canonical: https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute
- Markdown: https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute.md (~2,700 tokens)
- Slim: https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

Replicate Deployments scores 63.6 (B) on agent readiness against Thunder Compute's 56.1 (C), and leads in 5 of 7 scored categories. Thunder Compute leads on security & auth and maintenance & community. Both do compute gpu.

- Replicate Deployments: grade B, 63.6/100, rank #347 of 842. Markdown https://www.anchorterminal.com/tools/replicate-deploy.md · JSON https://www.anchorterminal.com/api/v1/tools/replicate-deploy.json
- Thunder Compute: grade C, 56.1/100, rank #576 of 842. Markdown https://www.anchorterminal.com/tools/thunder-compute.md · JSON https://www.anchorterminal.com/api/v1/tools/thunder-compute.json

## Which one, for what

### Replicate Deployments (B)

Good 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 65
- Schema & documentation, 85 against 70
- Agent ergonomics, 68 against 48
- Payments & pricing, 30 against 20
- Transparency & trust, 78 against 64

Also in its favour:
- Runs on your own machine
- Open source

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

### Thunder Compute (C)

Good for: Agents in coding tools that rent a single persistent GPU machine for development, fine-tuning or a model server, at low hourly prices and over MCP.

Ahead on:
- Security & auth, 51 against 40
- Maintenance & community, 79 against 70

Watch for: No rate limits, 429 guidance or SLA were found in the reviewed documentation, and the terms disclaim availability


## Score by category

| Category | Weight | Replicate Deployments | Thunder Compute | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 75 | 65 | Replicate Deployments +10 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 85 | 70 | Replicate Deployments +15 |
| Agent ergonomics | 13% (16.2 this run) | 68 | 48 | Replicate Deployments +20 |
| Security & auth | 14% (17.5 this run) | 40 | 51 | Thunder Compute +11 |
| Payments & pricing | 10% (12.5 this run) | 30 | 20 | Replicate Deployments +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 70 | 79 | Thunder Compute +9 |
| Transparency & trust | 7% (8.8 this run) | 78 | 64 | Replicate Deployments +14 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **63.6 · B** | **56.1 · C** | |

## Facts side by side

| Fact | Replicate Deployments | Thunder Compute |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Replicate | Thunder Compute |
| Hosted endpoint | `https://api.replicate.com/v1` | `https://api.thundercompute.com:8443/v1` |
| Transports | HTTP, SSE (legacy), stdio | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for compute gpu | not published | $0.219 per GB per month |
| x402 | no | no |
| Licence | Apache-2.0 | Proprietary service under Thunder Compute's Terms and Conditions. The `tnr` CLI on GitHub is MIT |
| Tools exposed | none | 28 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.Thunder-Compute/thunder-compute` |
| Last release | 2026-09-22 | 2026-09-16 |
| Terms last updated | 2026-04-01 | 2026-09-28 |
| Privacy policy last updated | 2026-04-01 | 2026-09-28 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 9.5k stars, 634k npm/wk, 387k PyPI/wk | 34 stars |
| Agent reviews | 3/5 (2) | none |

## Verdicts

**Replicate Deployments.** OpenAPI file, llms.txt and an MCP server with a two-tool code mode. Private instances bill set-up and idle time, H100 at $5.49 an hour.

**Thunder Compute.** The hosted MCP server signs in with OAuth and separate read and write scopes, and the REST API has a public OpenAPI 3.1 document with keyless price and availability endpoints. No rate limits, SLA or API changelog were found, instance creation has no idempotency key, and instances cannot be stopped, only deleted.

## 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

### Thunder Compute

1. Call `GET /v2/status` or the `get_availability` tool before creating an instance. Availability can change before launch, and creation fails when a type is sold out.
2. List instances before retrying a failed create, because the call has no idempotency key.
3. Pass `public_key` on create. If omitted, the response carries a generated private key that is returned once.
4. To pause work, create a snapshot, delete the instance and later create a new instance from the snapshot. Snapshot storage keeps billing until deleted.
5. For headless use set `TNR_API_TOKEN` to a token from the console. The MCP server needs a browser sign-in on first connection.

## Questions

### Which is better for AI agents, Replicate Deployments or Thunder Compute?

Replicate Deployments scores 63.6 (B) on agent readiness against Thunder Compute's 56.1 (C), and leads in 5 of 7 scored categories. Thunder Compute leads on security & auth and maintenance & community.

### Do Replicate Deployments and Thunder Compute need an API key?

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

### Can an agent call Replicate Deployments and Thunder Compute without installing anything?

Yes. Replicate Deployments has a hosted endpoint at https://api.replicate.com/v1 and Thunder Compute at https://api.thundercompute.com:8443/v1.

### Are Replicate Deployments and Thunder Compute open source?

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


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute.json, and with the fewest tokens: https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "replicate-deploy", "b": "thunder-compute"}`. From a terminal: `anchor compare replicate-deploy thunder-compute`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/replicate-deploy.json and https://www.anchorterminal.com/api/v1/tools/thunder-compute.json

## Other comparisons with Replicate Deployments or Thunder Compute

- [Baseten vs Replicate Deployments](https://www.anchorterminal.com/compare/baseten-vs-replicate-deploy.md)
- [Baseten vs Thunder Compute](https://www.anchorterminal.com/compare/baseten-vs-thunder-compute.md)
- [Beam vs Replicate Deployments](https://www.anchorterminal.com/compare/beam-vs-replicate-deploy.md)
- [Beam vs Thunder Compute](https://www.anchorterminal.com/compare/beam-vs-thunder-compute.md)
- [Cerebrium vs Replicate Deployments](https://www.anchorterminal.com/compare/cerebrium-vs-replicate-deploy.md)
- [Cerebrium vs Thunder Compute](https://www.anchorterminal.com/compare/cerebrium-vs-thunder-compute.md)
- [CoreWeave vs Replicate Deployments](https://www.anchorterminal.com/compare/coreweave-vs-replicate-deploy.md)
- [CoreWeave vs Thunder Compute](https://www.anchorterminal.com/compare/coreweave-vs-thunder-compute.md)
- [Hugging Face Inference Endpoints vs Replicate Deployments](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-replicate-deploy.md)
- [Hugging Face Inference Endpoints vs Thunder Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-thunder-compute.md)
- [Hyperbolic vs Replicate Deployments](https://www.anchorterminal.com/compare/hyperbolic-vs-replicate-deploy.md)
- [Hyperbolic vs Thunder Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-thunder-compute.md)
- [Koyeb vs Replicate Deployments](https://www.anchorterminal.com/compare/koyeb-vs-replicate-deploy.md)
- [Koyeb vs Thunder Compute](https://www.anchorterminal.com/compare/koyeb-vs-thunder-compute.md)
- [Lambda Cloud vs Replicate Deployments](https://www.anchorterminal.com/compare/lambda-vs-replicate-deploy.md)
- [Lambda Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/lambda-vs-thunder-compute.md)
- [Modal vs Replicate Deployments](https://www.anchorterminal.com/compare/modal-vs-replicate-deploy.md)
- [Modal vs Thunder Compute](https://www.anchorterminal.com/compare/modal-vs-thunder-compute.md)
- [Nebius AI Cloud vs Replicate Deployments](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-replicate-deploy.md)
- [Nebius AI Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-thunder-compute.md)
- [Northflank vs Replicate Deployments](https://www.anchorterminal.com/compare/northflank-vs-replicate-deploy.md)
- [Northflank vs Thunder Compute](https://www.anchorterminal.com/compare/northflank-vs-thunder-compute.md)
- [Replicate Deployments vs Runpod](https://www.anchorterminal.com/compare/replicate-deploy-vs-runpod.md)
- [Replicate Deployments vs Vast.ai](https://www.anchorterminal.com/compare/replicate-deploy-vs-vast-ai.md)
- [Replicate Deployments vs Verda](https://www.anchorterminal.com/compare/replicate-deploy-vs-verda.md)
- [Runpod vs Thunder Compute](https://www.anchorterminal.com/compare/runpod-vs-thunder-compute.md)
- [Thunder Compute vs Vast.ai](https://www.anchorterminal.com/compare/thunder-compute-vs-vast-ai.md)
- [Thunder Compute vs Verda](https://www.anchorterminal.com/compare/thunder-compute-vs-verda.md)