Head to head · GPU compute · October 2026 research run
Koyeb vs Replicate Deployments
Replicate Deployments scores 67 (B) on agent readiness against Koyeb's 47.8 (D), and leads in 6 of 7 scored categories. Koyeb 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
Koyeb D
Best for Teams that want low-cost H100, H200 or B200 containers with scale to zero and an SLA, deployed from Git or an image.
Ahead on
- Security & auth, 50 against 40
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
Public changelog silent since 27 February 2026, so API changes surface only through CLI and SDK releases
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 50
- Schema & documentation, 85 against 31
- Agent ergonomics, 73 against 51
- Payments & pricing, 45 against 30
- Maintenance & community, 78 against 73
- Transparency & trust, 79 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
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.
Schema & documentation Replicate Deployments +54
Koyeb 31
No downloadable OpenAPI file. The API reference at koyeb.com/docs/reference/api renders only by script, and the generated docs in the Go and Python client repositories aren't a published contract (0, was 10). No llms.txt (www.koyeb.com/llms.txt and /docs/llms.txt both 404) and no Markdown twins (0). Guides on scale to zero and autoscaling say when to use each setting (10, held). Typed parameters with required bodies in the Go client's docs, but service types and statuses are free strings with no listed values (8, held). CLI examples throughout; no documented error responses found (5, held). /v1 paths, but the public changelog stopped on 27 February 2026 (8, held). 0 + 0 + 10 + 8 + 5 + 8 = 31.
Replicate Deployments 85
Public OpenAPI 3.1.0 at api.replicate.com/openapi.json with 36 operations on 26 paths covering deployments, hardware, models and predictions, re-read on 2 November (25). llms.txt with Markdown pages (10). Operation descriptions in the spec explain purpose with curl examples; deployment docs say when to use a deployment rather than a model version (16). Deployment fields are bounded (min_instances 0 to 5, max_instances 0 to 20, a 64-character version, a hardware SKU from GET /v1/hardware) (13). Examples throughout and 8 coded errors (E1001 out of memory, E6716 start timeout and others) with fixes; the HTTP error body format isn't described (11). Versioned /v1, but the public changelog's last entry is still 21 April 2026 (10). 25 + 10 + 16 + 13 + 11 + 10 = 85.
Reliability Replicate Deployments +25
Koyeb 50
Graded on the hosted lines for its platform API. Instatus page at status.koyeb.com with components (API, Control Panel, Build / Provisioning and one per region) and history back to 2022 in its feed (20). Since 7 August the feed holds nine incidents and one maintenance. The eight in September each name one region, one GPU type or some customers, or ran 6 to 52 minutes (8, 11, 15, 21, 22 and 23 September and two on 29 September). On 16 October Koyeb posted a separate incident, "The ongoing maintenance is causing API to fail with 500", on the API, Control Panel and Build components for 24 minutes, inside a maintenance window announced the day before for 07:00 to 08:00 UTC with "max 10m unavailability". The status page labels it an incident and the outage ran past the unavailability announced, so it counts as an incident, and the API failing with 500 is errors across the board, one major outage (10). No API rate limits found in the docs we could read (0). No 429 or backoff guidance found (0). The Scale plan lists a 99.9 per cent uptime SLA and Enterprise 99.99, with an SLA document at /docs/legal/sla setting service credits (10). Services and GPUs are generally available; light sleep is a preview (10). 20 + 10 + 0 + 0 + 10 + 10 = 50.
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.
Agent ergonomics Replicate Deployments +22
Koyeb 51
List endpoints take limit and offset plus filters on name, type, status, region and ID, per the Go client's docs (15). The same filters give pagination and output-size control (20). No error codes or messages documented that we could find (0, was 5 with nothing behind it). dry_run on create and update validates a service before anything deploys; no idempotency keys (8, held as partial). Sensible scale-to-zero defaults (5 minutes idle) and official clients in Go and Python, but required parameters weren't readable in the script-drawn reference (8, held as partial). 15 + 20 + 0 + 8 + 8 = 51.
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.
Payments & pricing Replicate Deployments +15
Koyeb 30
No machine payment protocol (0). Per-hour GPU and per-second CPU prices published without a login (20). Pro costs $29 a month with $10 of usage, Scale $299 with $100, and the pricing page lists no free compute plan; the only free item is 5 hours of Postgres (0). Signup is a browser flow (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
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.
Transparency & trust Replicate Deployments +15
Koyeb 64
The editorial half. Closed service under the French-law Master Services Agreement of 28 June 2024; the CLI and Go client are Apache-2.0 (20). An MSA and a DPA are published, the MSA deletes customer data at the end of the reversibility period, but the footer's privacy link points at the DPA and we found no separate privacy policy or retention periods (15). The Mistral agreement was announced on 17 February 2026, with Starter closed to new sign-ups, and no dated migration or end-of-life notice since (5, held). Regions are named on the status page (North America, Europe, Asia-Pacific); subprocessors not checked (10). 20 + 15 + 5 + 10 = 50.
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.
Security & auth Koyeb +10
Koyeb 50
Personal access tokens and organisation tokens sent as Bearer; no scopes found (20). RBAC only on Enterprise; no read-only token (5). Runs your own containers and returns their output (10). Audit logs only on Enterprise (10). ISO 27001 and SOC 2 listed on the pricing page for Enterprise; www.koyeb.com/.well-known/security.txt is 404 and no disclosure policy, SECURITY.md or bug bounty found, so a bare certification claim (5). 20 + 5 + 10 + 10 + 5 = 50.
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.
Score by category
| Category | Weight | Koyeb | Replicate Deployments | Edge |
|---|---|---|---|---|
| Reliability | 16% | 50 | 75 | Replicate Deployments +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 31 | 85 | Replicate Deployments +54 |
| Agent ergonomics | 13% | 51 | 73 | Replicate Deployments +22 |
| Security & auth | 14% | 50 | 40 | Koyeb +10 |
| Payments & pricing | 10% | 30 | 45 | Replicate Deployments +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 73 | 78 | Replicate Deployments +5 |
| Transparency & trust | 7% | 64 | 79 | Replicate Deployments +15 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 47.8/100 | B 67/100 |
Facts side by side
| Fact | Koyeb | Replicate Deployments |
|---|---|---|
| Kind | Platform | HTTP API |
| Vendor | Koyeb | Replicate (Cloudflare) |
| Hosted endpoint | https://app.koyeb.com/v1 | https://api.replicate.com/v1 |
| Transports | HTTP | HTTP, SSE (legacy), stdio |
| Auth | Token | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-20 | 2026-10-19 |
| Terms last updated | no date given | 2026-04-01 |
| Privacy policy last updated | no date given | 2026-04-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 72 stars | 9.5k stars, 634k npm/wk, 387k PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Koyeb higher, the other way from the total score.
| Reviewer | Koyeb | Replicate Deployments |
|---|---|---|
| LedgerCost analyst | 4/5 Two-fifty an hour for an H100, after a $29 plan fee | 3/5 Set-up and idle time bill at H100 rates |
| SprintLatency and reliability tester | 3/5 Three short major outages, rate limits unchecked | 3/5 Stated limits, and a 20-hour incident labelled minor |
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
Koyeb
Koyeb publishes per-second GPU prices without a login, from $0.50 an hour for an RTX 4000 SFF Ada to $2.50 for an H100, with an SLA document from the Scale plan. It has no downloadable OpenAPI file, documented rate limits or error codes, and no free compute plan, and its public changelog has been silent since 27 February 2026.
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
Koyeb
- Pass
dry_runon service create or update to validate the definition before anything deploys - Page service lists with
limitandoffsetand filter bystatusesinstead of fetching everything - Expect the first request after deep sleep to take 1 to 5 seconds and retry once with a timeout
- Set
--min-scale 0on GPU services so idle instances stop billing - Read the CLI's CHANGES.md and the Python SDK tags for API changes, since the web changelog stopped in February 2026
Replicate Deployments
- List
GET /v1/hardwarefirst and use the returnedskuin the deployment body - Set
min_instancesto 0 for bursty work; a warm H100 bills $5.49 an hour whether called or not - Send
Prefer: waiton deployment predictions to block instead of polling - Copy outputs within an hour; API prediction data is deleted after that
- 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, Koyeb or Replicate Deployments?
Replicate Deployments scores 67 (B) on agent readiness against Koyeb's 47.8 (D), and leads in 6 of 7 scored categories. Koyeb leads on security & auth.
Can an agent call Koyeb and Replicate Deployments without installing anything?
Yes. Koyeb has a hosted endpoint at https://app.koyeb.com/v1 and Replicate Deployments at https://api.replicate.com/v1.
Are Koyeb and Replicate Deployments open source?
No open-source release is listed for Koyeb. Replicate Deployments is open source (Apache-2.0).
Other comparisons with Koyeb or Replicate Deployments
- Baseten vs Koyeb
- Baseten vs Replicate Deployments
- Beam vs Koyeb
- Beam vs Replicate Deployments
- Cerebrium vs Koyeb
- Cerebrium vs Replicate Deployments
- CoreWeave vs Koyeb
- CoreWeave vs Replicate Deployments
- Crusoe Cloud vs Koyeb
- Crusoe Cloud vs Replicate Deployments
- GPUsMarket vs Koyeb
- GPUsMarket vs Replicate Deployments
- Hugging Face Inference Endpoints vs Koyeb
- Hugging Face Inference Endpoints vs Replicate Deployments
- Hyperbolic vs Koyeb
- Hyperbolic vs Replicate Deployments
- Koyeb vs Lambda Cloud
- Koyeb vs Massed Compute
- Koyeb vs Modal
- Koyeb vs Nebius AI Cloud
- Koyeb vs Nodus Compute
- Koyeb vs Northflank
- Koyeb vs Runpod
- Koyeb vs Thunder Compute
- Koyeb vs Together GPU Clusters
- Koyeb vs Vast.ai
- Koyeb vs Verda
- Lambda Cloud vs Replicate Deployments
- Massed Compute vs Replicate Deployments
- Modal vs Replicate Deployments
- Nebius AI Cloud vs Replicate Deployments
- Nodus Compute vs Replicate Deployments
- Northflank vs Replicate Deployments
- Replicate Deployments vs Runpod
- Replicate Deployments vs Thunder Compute
- Replicate Deployments vs Together GPU Clusters
- Replicate Deployments vs Vast.ai
- Replicate Deployments vs Verda
- Cloud Run GPUs vs Koyeb
- Cloud Run GPUs vs Replicate Deployments
Machine-readable
- This page as Markdown
/compare/koyeb-vs-replicate-deploy.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/koyeb.json·/api/v1/tools/replicate-deploy.json - From a terminal
anchor compare koyeb replicate-deploy(the CLI) - Over MCP
compare_tools {"a": "koyeb", "b": "replicate-deploy"}at/mcp, no key